Kurt, I have that PC COM <---> TPDD working now also using standard cables. no loopbacks on CTS/RTS or DTR/DSR. Just as you suggest.
I think the source of my problem was DISABLING CTS/RTS flow control. Those signals have to be working. Also, I am using a USB FTDI adapter and I also agree with you that it is more tolerant of the low swing coming out of the TPDD. ( I think!) My sniffer config is now M100 <-----> COM1 (std port) COM2 (USB) <----> TPDD At the M100 RS-232, I think I have DTR looped back, and also CTS/RTS. Does that make sense? TS-DOS seems to need the DTR loopback. On Sat, Jan 9, 2021 at 1:21 PM Kurt McCullum <[email protected]> wrote: > Steve, > > I have done the M100 <---> PC COM1 (sniffer program) PC COM2 <---> TPDD2 > and just used regular cables for swapping the signals. I did have all lines > wired including RTS/CTS DTR/DSR. I used a USB to serial adapter on the PC > which had 2 serial and 1 parallel ports. That may have been more forgiving > of signal levels than a built in serial port on the PC. > > Kurt > > On Sat, Jan 9, 2021, at 6:24 AM, Stephen Adolph wrote: > > Question for the crowd, > > Is there any issue with the signal levels on the TPDD not being truly > RS-232, and so it isn't able to signal on the line to the right levels and > hence cannot connect to a PC properly? > > What I am trying to do, since VirtualT seems to be unable to receive any > data (still can't get that to work), I've reverted to this > > M100 <------> PC COM1 (sniffer program) PC COM2 <------> TPDD > > I have the M100 <---> COM1 working > > I have COM2 <-----> NADSbox working > > But I cannot get COM2 <-----> TPDD working! > > > I have a feeling it is the non-RS-232 signal levels of the TPDD. > > thx > Steve > > >
