I can take a look at the Windows version. I’m not sure how to submit
changes on SF, tho.
On Sat, Jan 9, 2021 at 5:04 PM John R. Hogerhuis wrote:
> Based on what you say it sounds like the bug is that it only opens the
> port when the emulation starts. So if the configuration changes then it
>
Based on what you say it sounds like the bug is that it only opens the port
when the emulation starts. So if the configuration changes then it would
have no effect, particularly if the port was no configured at all at
startup.
Probably needs to (try) close and reopen the serial device after any
Yeah, Virtual T's serial interface is a bit buggy. On my system, it won't
shut down properly if the serial interface is active. (So make note of
that.)
If I finally build my Pi-100, I'm going to have to visit that code and
figure out what's going on there.
Tom Wilson
wilso...@gmail.com
It took me quite a bit of time to figure that out a last year when I was
working with Virtual-T and a real TPDD2. I'm not sure why that method works,
but it proved to be a consistent work around to the bug. Glad it helped.
On Sat, Jan 9, 2021, at 2:50 PM, Stephen Adolph wrote:
> son of a gun,
son of a gun, that did it Kurt! Nice!
I was pulling what is left of my hair out!
On Sat, Jan 9, 2021 at 5:30 PM Kurt McCullum wrote:
> Here is what I have had to do to get Virtual-T in Windows to work properly.
> 1) Start Virtual-T with no emulation for a COM port
> 2) Select Use Host Port
Here is what I have had to do to get Virtual-T in Windows to work properly.
1) Start Virtual-T with no emulation for a COM port
2) Select Use Host Port and pick your COM port
3) Exit Virtual-T. If you don't do this, it won't work.
4) Re-Start Virtual-T and you are good to go.
That's the only way
You've fully checked out the equipment?
A simple thing to do is loopback TX/RX on USB-serial device with a db9
connector and a paperclip. Confirm you get your characters back when
running a Windows terminal program.
Then try the same thing from Virtual T.
-- John.
Update, back to the subject of this thread. Getting VirtualT to accept
input characters from serial ports.
After all this experimentation, and success with the sniffer configuration,
I still cannot get VirtualT to receive a byte from a serial port.
Nothing seems to make a difference; regardless
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
I do have it working now for sniffer config.
Not sure it was absolutely necessary, but I did have to make an adapter
that put a resistive load on the TxD line out of the TPDD.
I may fiddle some more and see if it really was necessary.
thanks all
steve
On Sat, Jan 9, 2021 at 1:29 PM Scott
Fantastic, welcome Jim!
I’m pretty new around here too, just got my first T102 late-spring and have
been having a blast. This community is nothing short of amazing and I learn
stuff every single day.
> I'd greatly appreciate hearing anyone's experiences with serial-to-WiFi
> converters
Hi everyone,
I just joined the flock and I'm an Original Flavor owner of a 32 KB M100
when they were going for $399 (worth $964.98 today) in the mid-1980s, and
now I can add nine more to my collection for that much in
inflation-adjusted value! I would have waited for that price decrease, but
Wait….
http://tandy.wiki/TPDD
Cable
The "RS-232C" interface to the TPDD is actually 5v TTL (0v to +5v), while
RS-232 serial ports use -12v to +12v. So the cable isn't just a cable, it has
electronics inside the DB25 plug to convert the signal levels between TTL and
RS-232.
According to
Steve,
Is it possible that the TPDD has a damaged RS232 driver or reciver? Probably a
SN75188 or MC1488? Is it working with a real M100?
From: Stephen Adolph
Sent: Saturday, January 9, 2021 9:25 AM
To: m...@bitchin100.com
Subject: [M100] connect TPDD to standard PC COM port
Question for the
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
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
16 matches
Mail list logo
