by smurfjesse » Wed Mar 30, 2011 3:11 pm
Hello,
In our production plant, we want to replace all fat windows client by thin clients.
Now I'm testing some solutions, and I like WTware the most.
But we experience 1 problem:
Al our production machines have sensors.
These sensors are connected to the COM port of the PC.
On the PC there is a datacollection program running which measures the machine status and speed.
The sensors are not communicating via the RX/TX pins but they use the handshake pins CTS, DSR or CD.
When we redirect the COM port in WTware, the counters on the datacollection program do not react on signals from the sensors.
Sending data vi RX/TX works fine. (hyperterm connection via nullmodem cable)
When we start mstsc on the fat client, redirect the COM port in mstsc, and connect to the terminal server then the
datacollection program does react correct on the signals from the sensors.
So it seems that WTware does not interface the handshake signals to the terminal server.
Am I right or is there some setting where we can manage this problem ?
Thanks,
Jesse
Hello,
In our production plant, we want to replace all fat windows client by thin clients.
Now I'm testing some solutions, and I like WTware the most.
But we experience 1 problem:
Al our production machines have sensors.
These sensors are connected to the COM port of the PC.
On the PC there is a datacollection program running which measures the machine status and speed.
The sensors are not communicating via the RX/TX pins but they use the handshake pins CTS, DSR or CD.
When we redirect the COM port in WTware, the counters on the datacollection program do not react on signals from the sensors.
Sending data vi RX/TX works fine. (hyperterm connection via nullmodem cable)
When we start mstsc on the fat client, redirect the COM port in mstsc, and connect to the terminal server then the
datacollection program does react correct on the signals from the sensors.
So it seems that WTware does not interface the handshake signals to the terminal server.
Am I right or is there some setting where we can manage this problem ?
Thanks,
Jesse