VDM99 and Lantronix UDS-10/100

[+OLD CS1]

Now I have VDM99 working with a USB serial adapter, I decided I wanted a little more flexibility and make this setup network-based. Sure, I could use a USB-over-IP device but the Lantronix network serial port is so much more sexy.

 

The Lantronix Port Redirector is used to install the UDS-10 or UDS-100 as a native COM port in Windows. During prior trials with VDM I found that it does not like to use COM ports over COM4, so I assigned the discovered device as COM4.

 

I tested this setup by connecting to the console port of my firewall. All good. Now is time to connect to the TI with my convoluted cabling for null-modem and a Bruce Jenner connector.

 

UDS-10 settings for COM4

 

And the settings on the UDS-10 itself

 

VDM settings:

 

On the TI I go to E/A option 3, and for the file name I enter: RS232.BA=9600.EC

 

LPR Monitor watching the RS232 hook being uploaded to the TI:

 

Now the sticky part. The upload goes fine, but the scan not so well.

 

Section of the scan showing where it queries CRU >1100, and the response from the TI:

 

and the resulting notice from VDM99:

 

Here it becomes nearly obvious the the problem is in getting information back from the TI. In some trials the responses for every one of VDM's queries are >F7, sometimes >7F, sometimes >71, etc. It is clear that the hook on the TI is getting data since it gets uploaded in the first place, and when I issue "unhook" the TI behaves exactly as with the standard serial (in my case, video corruption and lock-up.) To demonstrate the problem more I typed in a short program in BASIC and sent it to the serial with LIST "RS232.BA=9600.EC"

 

Definitely a problem getting data from the TI. I have tried making changes to some of the DTR, CTS, and DCD settings, and I will keep trying until I can get a usable data stream from the TI. I would appreciate any ideas or words of wisdom anyone else may have. BTW, VDM99 will not open the COM port if the UDS port is set for RFC-2217 (TruPort.)

[+InsaneMultitasker]

 

Definitely a problem getting data from the TI. I have tried making changes to some of the DTR, CTS, and DCD settings, and I will keep trying until I can get a usable data stream from the TI. I would appreciate any ideas or words of wisdom anyone else may have. BTW, VDM99 will not open the COM port if the UDS port is set for RFC-2217 (TruPort.)

 

Your LIST "RS232.BA=9600.EC" most likely generates the garbage as you are not specifying a few other parameters, namely DA=8 and PA=N (data bits 8, Parity None). The RS232 default without these parameter switches is 7O1 (7 data bits, Odd parity, 1 stop bit). Try: LIST "RS232.BA=9600.DA=8.PA=N.EC"

 

I found a link to the RS232 manual. See page 12. http://maben.homeip.net/static/s100/TI/TI%20994/hardware/TI%20994%20RS232%20expansion%20PHP1220.pdf

 

Make sure both the TI and PC match 8N1. Also try dropping the speed to 4800 just to rule out buffer overrun.

[+OLD CS1]

 

Your LIST "RS232.BA=9600.EC" most likely generates the garbage as you are not specifying a few other parameters, namely DA=8 and PA=N (data bits 8, Parity None). The RS232 default without these parameter switches is 7O1 (7 data bits, Odd parity, 1 stop bit). Try: LIST "RS232.BA=9600.DA=8.PA=N.EC"

 

I found a link to the RS232 manual. See page 12. http://maben.homeip.net/static/s100/TI/TI%20994/hardware/TI%20994%20RS232%20expansion%20PHP1220.pdf

 

Make sure both the TI and PC match 8N1. Also try dropping the speed to 4800 just to rule out buffer overrun.

 

Oooooh,,, shoot... using my internal Rolodex of information, I just knew that 8N1 is the default. Need to throw that card out. I am about to try this out.

[+OLD CS1]

Works as advertised at 9600,8N1. Now I just need to figure out what the problem is with the VDM hook communicating back.

 

[+OLD CS1]

What I find really aggravating is how this is alternating between being unable to use the COM port (that clear com error I reported in another thread) and getting back data, but seemingly senseless data and getting "No DSKx DSR" from VDM.

 

 

What I find really fun is that I am doing this through my VPN while up at the bar watching a game

 

Once I get this working or not, I will most likely bite the bullet and get an HDX setup in place and try my hand at that, too.

[+OLD CS1]

Looking through the source code of the serial hook, I see where it tests DTR whereas the DTR is not tested during the hook upload. I am following Thierry's guidelines on handshaking, but I wonder if the problem is that I am going from DCE-to-DCE rather than DTE-to-DTE and maybe the null-modem cable is not geared toward this particular task. If the problem is handshaking, I need to determine if the problem is the cable or how the UDS is handshaking with the TI.

[+OLD CS1]

I made a little more progress by turning off the echo in the UDS, connection mode C6. I am spent for the night. Have to go recover a severely corrupt 8GB ufs filesystem.