I recently downloaded a trial version of Serial Port Splitter to use along with a program called CME 2.
I needed to split the port the program was using to communicate with my hardware, so that I could open up CME 2 twice (so it could take two different measurements).
I split the Com4 port into ports Com5 and Com6, and then opened CME 2. The first copy of the program detected Com4 and connected to it. The second copy however, considered Com4, as well as both Com5 and Com6 used, and therefore unavailable for measurements.
Since that part of the software wasn't working for me, I decided to try and share Com4. This didn't work either, with both copies of CME 2 not recognizing that Com4 was an available port.
Is there a way around this? The software perfectly describes what I need to accomplish, but does not allow for two versions of CME 2 to both use the same port. Is there a way to make this work?
Thank you, FlintG
IP Logged
Sergey_Jarovski FabulaTech Forum Moderator
FabulaTech Forum God
Gender: Posts: 559
Re: Unable to Share/Split a Port Reply #1 on: Jul 23rd, 2015, 8:40am
Hi ! Please do the following: - check the availability of your physical COM4 port. Use your app CME2 for this purpose; - split COM4 to COM5 and COM6 according to this instruction: http://www.fabulatech.com/serial-port-splitter-help/serial-port-splitting.html - run your app and use COM5/COM6 ports. You must see the changing of ports status "Read/Write" in the SPS GUI (for example, com3-physical, com4/5-virtual: http://www.filedropper.com/sps Let me know your test results.
Hi ! Please make three screenshots: - run your app CME 2 and use COM4 port (screenshot of MCE 2); - run your app CME 2 and use COM5/COM6 ports (screenshot of SPS GUI and MCE 2). Thanks in advance.
The problem has been resolved. The way CME communicates with the COM ports is no allowing for port splitting. From my understanding, this is not supported in CME at all.
However, we found a workaround with the use of CAN BUS.
Serial Port Splitter was performing exactly how it should have been, and it was not an issue with the software at all.
Thank you for your support throughout this troubleshooting process; it was very much appreciated!!