How does the generic serial controller transmit data? One byte at a time, a chunk at a time, or perhaps a full frame in one write operation? The reason that I ask is that I have a controller with a (relatively) fast PIC24 and a DLP-USB245 USB->parallel module. With that setup I'm able to transfer data at about 10Mbps if the host is sending data as one large block (i.e. a write command of 9210 bytes = 3072 pixels + header/footer), but I suspect that the transfer rate would be much less if the host sent data one byte at a time.
Generic serial is sent as fast as possible. Header + Data + Footer. As few gaps in the data stream as possible. For example, Gaps between frames usually try to maintain a frame rate of 40 frames per second or less.
What does 'as fast as possible' mean? Can it transmit a 9216-byte frame in under 8mS, for example into an unthrottled USB->USB serial link if the other end can input the data that fast??
For ESPS V4, the controller has a buffer that holds all channel data (received in >1MB bursts over Ethernet). It then transmits the frame through the serial port at the wire rate with ideally no gaps between the bytes. There is an artificial limit enforced that will not send a small frame more often than once every 25ms. If a frame is greater than 25ms in length, then the frames will be sent with a teany tiny gap as the pointers get reset between frames.
On a PC, Vixen schedules the frame through the USB adapter. The adapter uses flow control to ensure it has data to send at the communications data rate so it can transmit without gaps. It is possible (but very unlikely) the PC could get a bit behind and the USB adapter will underrun and cause a gap between bytes in the data stream. As long as the Serial port rate is less than the USB max transfer rate and the PC can keep up, then you will have no gaps in the data stream. I cant say how long it will take to send a 8KB frame without knowing the data rate.
OK, thanks, that answers my question.
Using a DLP-USB245 adapter, a PIC24HJ128GP202 clocked at 40 Mhz reading as fast as it can and a Linux program sending 9K frames at max rate it takes just over 8 mS to send that much data.
Edit: make that 80Mhz clock for a 40Mhz instruction rate.
