I guess. I bought an FTDI based cable and I'll be darned. Setting the custom port rate in Linux seems like a nightmare.
76800 is harder than it sounded. In windows it seems like you edit a file called FTDIport.inf and change a few values. But you need to ALIAS the port setting. meaning you take a selection like 128000 and make it operate as 76800. but the entry stays as 128000. I was really hoping that there would be some way of setting this up. my BCR port is looking more user friendly after all. On Sun, Apr 26, 2020 at 11:52 AM Mike Stein <mhs.st...@gmail.com> wrote: > So, BCR port for video at 57600 and RS-232 at 76800 for data transfer? > > ----- Original Message ----- > *From:* Stephen Adolph <twospru...@gmail.com> > *To:* m...@bitchin100.com > *Sent:* Sunday, April 26, 2020 11:32 AM > *Subject:* Re: [M100] speed benchmark! > > no as I have said, bit banging the BCR port is limited to 57600. so it > makes sense to use 76800 and a suitable usb RS232 port > > On Sun, Apr 26, 2020 at 11:29 AM Mike Stein <mhs.st...@gmail.com> wrote: > >> No problem using the RS-232 port at 76800 but can you bit bang the BCR >> port at that speed? That was one of the main points after all. >> >> ----- Original Message ----- >> *From:* Stephen Adolph <twospru...@gmail.com> >> *To:* m...@bitchin100.com >> *Sent:* Sunday, April 26, 2020 9:03 AM >> *Subject:* Re: [M100] speed benchmark! >> >> I'm going to take back this comment: " I myself have passed characters >> between two m100 at 76800 by manually coding, but It was flakey because of >> how you have to set up the UART." >> >> For some reason I thought I recalled that the UART stopped using 16x >> clock for RX sampling at 76800. Wrong! It always uses 16x clock. So the >> UART should not have any problem with 76800. >> >> So, when used with an RS232 system that can support 76800 that's the best >> option. >> >> >> >>>
