Thanx, I'll check out the Ctrl-z!
My USB adapter is a CH340. Let me check for buffering...
It does have an option for buffering. I'll try disabling that.
Well, tried that an 9 (19,200) didn't work. I'll play with it a bit more.
I am thinking maybe an FTDI chipset USB-serial adapter might be mroe compatible...
As for the 2 stopbits, I think it was just the setting I was using when I finally got a good transfer at 600 baud. So I stuck with that.
I tend to use 8n1 generally.
Yeah, I am using Xon/Xoff...
And I am not sure what the phrase "bootstrap into Teeny" means (I know what bootstrapping is in general, but not in this context).
So, off for some googling!!!
Thanx!
Sent: Sunday, August 30, 2020 at 4:12 PM
From: "John R. Hogerhuis" <[email protected]>
To: [email protected]
Subject: Re: [M100] PC file transfer fun..
From: "John R. Hogerhuis" <[email protected]>
To: [email protected]
Subject: Re: [M100] PC file transfer fun..
On Sun, Aug 30, 2020 at 11:50 AM Desi Villaescusa <[email protected]> wrote:
Been working on transferring files over serial to my M100's.I have 2. My original has 8k, 1 key needs work (I have to have a small rubber band on it to work) and there is a horizontal row that is having issues (I thought it was blank, but now (before???) it does appear to be there, just lighter...). So I was looking on ebay for a parts M100 possibly, and found a 24k M100 in good shape at a great price. So now I have 2.Anyway, I was working on serial transfers to my M100.Not having great luck, although I am thinking that might be my cheap USB serial adapter.I seem to be able to get it to work at 600 baud pretty well.Also, it seems like after I transfer a file, I have to kill my PC program (either Putty or Teraterm) and restart it to reconnect.Also, I have taken to adding a single "." as the last line on my BASIC programs. So when it is done transferring (using the LOAD "COM:47N2E" method), I get an error and know it is done.There is probably a better character to add than that???
Hello Desi,
Yes there is a proper character for that, what used to be called the "EOF" character
I think, Ctrl-Z or hex 1A
Try 98N1E should work but maybe you have to go a little slower for the tokenizer. I don't remember.
Why 2 stop bits?
I don't think it was 600 baud slow though.
Do you have software flow control turned on on your terminal?
As far as the USB, if the driver has settings, attempt turn off any USB buffering. USB packets are like 64 bytes which is the size of the entire receive buffer on the Model 100. So Windows and the USB driver are conspiring against you, building up fairly big messages (for efficiency sake, usually a good thing) and hitting you with more data at once than is ideal. Of course, no matter how much it buffers it ends up getting funnelled down to 1 byte at a time on the serial line. When it buffers, it is providing a constant stream of data. And, depending on circumstances, not detecting flow-off from the Model T until it's too late.
You basically want to get it to send one ASCII character per USB packet and not buffer them up.
Do you know the chipset of the USB-Serial adapter? And what advanced settings are available if any?
Also if you can bootstrap into TEENY then you will be in a whole new world quick and reliable transfers because then you can save/load tokenized files that are significantly more compact and don't have to be re-tokenized (which is compute intensive on the T).
-- John
