> The crux is that I am interfacing it with an embedded PC using the
> RS-232 port which runs at 115.2kbps. Of course there is a bottleneck,
> but it's ok because the data being sent is generated less often then
> what would be needed to max out the DMX output.
>
> Here are my current thoughts on a solution:
>
> - 2 PICs connected together with either parallel or I2C
> - a PIC with 2 UARTs (but the only ones are 64TQFP, not nice
> to solder)
> - a PIC controlling a 16550 UART

DMX is send only, so why not use the hardware UART for the PC
communication, and generate the DMX asynch in software? Check the UART
between each sent character and buffer anything received, processes it
later during the gap between DMX frames. Now you just need a PIC with at
least 512 bytes RAM to buffer the DMX data :)

Wouter van Ooijen

-- -------------------------------------------
Van Ooijen Technische Informatica: www.voti.nl
consultancy, development, PICmicro products

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.