Redirected com port handshake fail

Post a reply

Smilies
:D :) :( :o :shock: :? 8) :lol: :x :P :oops: :cry: :evil: :twisted: :roll: :wink: :!: :?: :idea: :arrow: :| :mrgreen:

BBCode is OFF
Smilies are ON

Topic review
   

Expand view Topic review: Redirected com port handshake fail

Re: Redirected com port handshake fail

by aka » Tue May 17, 2011 11:32 pm

Hello smurfjesse,

do you got any good news for us? :wink:

Re: Redirected com port handshake fail

by aka » Fri Apr 29, 2011 10:01 am

Sorry, not yet. We're working on your problem.

Re: Redirected com port handshake fail

by smurfjesse » Tue Apr 26, 2011 12:59 pm

Hello aka,

do you got any good news for us?

Re: Redirected com port handshake fail

by aka » Tue Apr 05, 2011 5:21 pm

The file you sent us was quarantined as virus. May be send it as rar-archive?

Re: Redirected com port handshake fail

by aka » Tue Apr 05, 2011 10:44 am

Re: Redirected com port handshake fail

by smurfjesse » Mon Apr 04, 2011 12:19 pm

Yes,

please give us your email address.

i can send you a schedule how you can make a simple test machine. i also will send you a vbs script wich works the same as the counter on our machines.

regards,

jesse

Re: Redirected com port handshake fail

by aka » Sat Apr 02, 2011 2:06 pm

May be if we could perfrom tests on this device by ourselves? Is it possible to send us device?

Re: Redirected com port handshake fail

by smurfjesse » Thu Mar 31, 2011 9:44 pm

Hello

Thats to bad cause if this is solved we want to buy +/- 200 licences.

regards,

jesse

Re: Redirected com port handshake fail

by aka » Thu Mar 31, 2011 7:15 pm

Sorry, we have no ideas :(

Re: Redirected com port handshake fail

by smurfjesse » Thu Mar 31, 2011 4:45 pm

is there something we can do about this?
maybe progam it our self.

redirect it?

or use different ports like ps2 or parrelel?

show us some options

regards,

jesse

Re: Redirected com port handshake fail

by aka » Thu Mar 31, 2011 1:58 pm

WTware does not handle pin communication properly. We've already made several tries to fix it remotely without success. But we need the device to perfrom many tests. Unfortunately, every hardware I know that communicates through pins requires some kind of production plant to work.

Redirected com port handshake fail

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

Top