[Coco] RS232 to WiFi/Ethernet

[phil pt]

Hello

I checked the Rs232 Pak manual and the Windows Sock Library files. It
should be possible to forward data to the Rs232 pack from the winsock
connection and also detect if carrier is present.

Use the carrier detect and update the memory address on the rs232 pack
since Winsock and detect new and lost connection.

Setup a buffer area for the incoming and outgoing data on the windows
machine for the winsock.data

Use either the build in timer or the winsock data arrive event to check if
data needs to be sent and received and also checks the current amount of
data is currently in the rs232 pack buffer.

Winsock supports:

1 When a new connection is established.
2 When the current connection is lost.
3 Data arrive event

This should work:

01 The program startups on the windows machine

     Sets:

     Empty the incoming windows receive and winsock buffer
     Sets the carrier detect to false on the Rs232 pack,
     Use timer event so incoming data being sent to the rs232 does not
exceed 9600 baud.

02. Connection is established on the winsock connection
03  The carrier detect memory address is updated to true
04  Timer event is enabled to control the incoming flow of data being sent
to the rs232 pack to 9600 baud.
05  Check and any new data being received or needs to be sent.

Data being sent from the winsock to the rs232 pack will also check to see
if the rs232 pack buffer is full or not.

Again all incoming data is controlled and handled using 9600 buard by using
timer events.




,



On Tue, Jan 30, 2018 at 7:21 PM, Allen Huffman <alsplace at pobox.com> wrote:

> > On Jan 30, 2018, at 6:16 PM, Mark D. Overholser <marko555.os2 at gmail.com>
> wrote:
> >
> > Something that would help tremendously on the Bit Banger Port would be a
> > Hardware Buffer for Incoming, ( and Outgoing ) Data...  Since the CoCo
> > needs to Focus ALL of its TIME on the Bitbanger Port, having a Buffer
> > would help prevent Data Loss.  The Microchip/Atmel AVR 1284 has 16K of
> RAM.
>
> These ESP8266s appear to do that. You can connect at 1200 baud to a remote
> system sending data much faster than that. I don’t know the details of how
> big the buffer is, though.
>
> > 2) A cartridge option for folks who don’t have MPI and/or RS232 pak.
> >> Bitbanger would be okay, but lousy under OS-9, and can’t do the
> >> 115200 baud that the RS232 pak can do.
> >
> > There is a lot to be said about a dedicated ACIA, even the "damaged” 6551
>
> Yes. It has to be a 6551 workalike otherwise we will have zero software
> that works for it.
>
> >
> >> And really, if someone just provides TTL pins (3.3v for the ESP
> >> module, ot 5V for other modules) on a header, we could just plug in
> >> modules.
> >
> > There are some CoCo Board designs that these headers could be added to…
>
> Until someone wants to do a hardware project, I’ll offer the plans to
> “hook up four wires” and be online. That’s at least a start.
>
> > The ESP32 is looking pretty cool...  I have a few of them, and I am
> looking into a Ethernet/WiFi/Bluetooth adapter…
>
> I haven’t gotten my development board yet. Does it do master and slave?
>
> > There is about 5 things that could get added to the CoCoSDC….
>
> At some point, we’ll just stick an Arduino or similar thing on there, with
> header connectors. Then we can add on sound chips, WiFi, Bluetooth, etc. to
> this “smart” cartridge and not have to worry about anything.
>
>                 — A
>
>
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> https://pairlist5.pair.net/mailman/listinfo/coco
>