0

Terminal Software Crashing w/GC-100

JP Hare

May 26, 2012 00:33

None

Follow

I'm using PuTTY to interface with my GC-100, and I'm successfully issuing basic commands (i.e. getdevices, setstate, version, etc.) However, after a few minutes, PuTTY crashes, and I have to relaunch and reconnect.  One interesting observation: after every command, I get error code 14.  So it seems that something extra is being sent with my commands.  I also notice that I have to send the SETSTATE twice to a relay port before it actuates, and then works fine (i.e. turns on and off by command) until the software crashes. 

I tried iTest.exe with similar results.  After a few minutes of successful interaction with the unit, I lose connection.  Sometimes the software crashes, but usually, I have to "disconnect" and "reconnect."

So long story short:

1.) Does anyone recongize the issue I'm having?   I suspect I have a PuTTY setting conflict, but I haven't been able to isolate it.

2.) Does anyone know why my connection seems to "time out?"

TIA

JP

 

 

 

• Facebook
• Twitter
• LinkedIn

4 comments

• 0
  
  JP Hare May 26, 2012 00:34

  BTW, I have version 3.2-12.

• 0
  
  Broc Atkinson June 01, 2012 23:08

  We have never had a problem wherein a unit would force reconnects due to a badly formatted command, so more than likely your problem is on the side of the software. A way to check is to use software such as Wireshark, which is a network packet analyzer. This would allow you to see the actual packets going to and from the unit to see what is happening at a byte by byte level. Let me know if you have any further questions or continue to have problems.

  www.wireshark.org

• 0
  
  Josh Sherman July 03, 2012 15:54

  It is possible that another piece of software is attempting to connect to the unit. Since there is only one available connection, an idle connection can be stolen by a new attempt to connect to the unit, so make sure that any other software which might be trying to connect to the unit is turned off before continuing testing to see if this makes a difference.

• 0
  
  JP Hare July 05, 2012 15:08

  BINGO!  Thank you Josh.  That was the problem.  I turned my controller off, and my terminal connection stays up.  I'm still getting error code14 appended to every reply, but I think I can fix that by changing the terminal settings (e.g. I may be supplying extra Line Feed and/or Carriage Returns.)