Oh I misunderstood that. I thought the tnc had that configurable with a
jumper installed by default.
--
bkw
On 9/27/23 19:37, Jesse Bertier wrote:
I agree that the m100 has unique circuitry contributing to the problem -
perhaps only 5 volts to work with , perhaps the choice in the resistor
I agree that the m100 has unique circuitry contributing to the problem -
perhaps only 5 volts to work with , perhaps the choice in the resistor values
chosen on the inputs and outputs, or perhaps when they changed to 330 ohm
values in that TSB.
Agreed it’s perfectly legit to loop back in
Hi Alex,Yes, I’ve noticed the lcd dimming on the model 100 sometimes as there was higher current drain or voltage drain from the RS-232 port.I suspect hardware flow control lines is a big contributor to that power drain - anything that pushes the hardware flow control input pins high (I believe
On 9/27/23 16:01, Jesse Bertier wrote:
Fellow M100 Enthusiasts:
I kept at it, trying all the various suggestions from the group. I
finally solved the issue - the TNC had a loopback connection from DTR to
DSR. The problem disappeared entirely when I removed that loopback
connection the TNC
Jesse,
I feel like I ran into that exact problem before a couple years ago when I
was using my '102 for packet radio. Something also about poor battery life
from the laptop while the TNC was plugged in as well? I didn't keep good
notes, and I was testing several TNCs (two KPC-3s, a KPC-2, and a
Fellow M100 Enthusiasts:
I kept at it, trying all the various suggestions from the group. I finally
solved the issue - the TNC had a loopback connection from DTR to DSR. The
problem disappeared entirely when I removed that loopback connection the TNC
was doing.
If interested, I posted
On 9/9/23 00:10, Jesse Bertier wrote:
I wanted to follow up with this issue - As it turns out, the TNC itself
seems to be the culprit, at least with the M100. Even small text strings
get garbled, with software flow control enabled on both sides. That TNC
works fine with a PC, just not the
I wanted to follow up with this issue - As it turns out, the TNC itself seems
to be the culprit, at least with the M100. Even small text strings get
garbled, with software flow control enabled on both sides. That TNC works fine
with a PC, just not the M100. Next time I have the scope out,
Yes. Since the data is processed at the hardware level that makes sense.
The garbling I usually see is because of the software level getting behind
and dropping portions of multibyte characters (UTF-8) or unprocessed escape
sequences (ANSI escapes, x terminal stuff)
But that may be specific to my
Thanks John, my next test(s) will be transferring programs to/from the M100,
and I believe I read somewhere that zmodem would work well. It’s been decades
since I’ve used it, reminds me of BBSes, and that DOS terminal program,
TERMINATE (I believe that’s what it was back in the day).
> On Jul
For sure, flow control is key also. I noticed that the TNC was a mismatch with
this Model 100, as my PC and other rig have no issues, no garbled characters,
same baud rate — if I hit it hard with a large chunk of text, the M100 drops
some chars, but it does not get garbled (odd ASCII chars).
July 10, 2023 12:57 PM
> To: m...@bitchin100.com <mailto:m...@bitchin100.com>
> Subject: Re: [M100] Intermittent problem at higher baud rates on RS-232
> interface
>
> Hi Jeff,
>
> Thank you - I noted my serial # was after the 30601 mark, and verified
> the
" TPDD uses 9600 and 19200 reliably only because it operates in small
packets and no screen updates."
TPDD drives and emulator file services work with no flow control at high
speeds because of the half duplex, request/response nature of the TPDD
protocol... it's client driven, and the client is
The receive buffer on m100 is small and tge screen updates in telcom take
so much time that, even with xon/off enabled, you can't go over 600 baud
reliably. The in-band software flow control has a minimum round trip time
that means that by the time the 100 sends the "stop sending" and the other
further corrosion. I have done a few videos on M100 recapping describing the
process.
Jeff
From: M100 On Behalf Of Jesse Bertier
Sent: Monday, July 10, 2023 12:57 PM
To: m...@bitchin100.com
Subject: Re: [M100] Intermittent problem at higher baud rates on RS-232
interface
Hi Jeff
n:
>
> https://youtu.be/KPFnwv_nDD8
>
> Jeff Birt
>
> *From:* M100 *On Behalf Of *Gregory
> McGill
> *Sent:* Sunday, July 9, 2023 5:40 PM
> *To:* m...@bitchin100.com
> *Subject:* Re: [M100] Intermittent problem at higher baud rates on RS-232
> interface
>
>
stat 98n1,e
On Sun, 9 Jul 2023 at 15:40, Gregory McGill wrote:
> there's no hardware flow control on the 100 with telcom
> use a better terminal and hardware flow control at any baud rate over 2400
>
>
> On Sun, Jul 9, 2023 at 3:19 PM Jesse Bertier wrote:
>
>> First time getting my hands on a
What about software flow control?
On Sun, 9 Jul 2023 at 15:40, Gregory McGill wrote:
> there's no hardware flow control on the 100 with telcom
> use a better terminal and hardware flow control at any baud rate over 2400
>
>
> On Sun, Jul 9, 2023 at 3:19 PM Jesse Bertier wrote:
>
>> First time
n Behalf Of Gregory McGill
> Sent: Sunday, July 9, 2023 5:40 PM
> To: m...@bitchin100.com <mailto:m...@bitchin100.com>
> Subject: Re: [M100] Intermittent problem at higher baud rates on RS-232
> interface
>
> there's no hardware flow control on the 100 with
And of course I didn't see my mistake until seconds after hitting send..
The settings to enable flow control are STAT 88N1E - sorry about that.
On Mon, Jul 10, 2023 at 7:02 AM Brian Brindle wrote:
> Hey Jesse - congrats on getting the model T! They make great packet
> stations for sure. The
Hey Jesse - congrats on getting the model T! They make great packet
stations for sure. The issue you are describing sounds like a flow control
one. Depending on what TNC you are using you should be able to activate
XON/XOFF. On my old Timewave I think the command is XFLOW ON.
Then just ensure
Probably peer is overrunning m100's receive buffer.
-- John.
On Sun, Jul 9, 2023, 3:20 PM Jesse Bertier wrote:
> First time getting my hands on a model T. I am attempting to connect to a
> TNC at 9600 baud. I have both matched for 8,N,1 and 9600 baud. TNC works
> with other PCs. I’m using
Subject: Re: [M100] Intermittent problem at higher baud rates on RS-232
interface
there's no hardware flow control on the 100 with telcom
use a better terminal and hardware flow control at any baud rate over 2400
On Sun, Jul 9, 2023 at 3:19 PM Jesse Bertier mailto:berti...@gmail.com
there's no hardware flow control on the 100 with telcom
use a better terminal and hardware flow control at any baud rate over 2400
On Sun, Jul 9, 2023 at 3:19 PM Jesse Bertier wrote:
> First time getting my hands on a model T. I am attempting to connect to a
> TNC at 9600 baud. I have both
First time getting my hands on a model T. I am attempting to connect to a TNC
at 9600 baud. I have both matched for 8,N,1 and 9600 baud. TNC works with
other PCs. I’m using TELCOM and set the parameters correctly. What happens at
9600 baud is the text coming into the m100 is garbled mostly
25 matches
Mail list logo
