Styx
Active Member
I have a project where I am reading and writing to the COM's port
All was going well, got a nice GUI showing the status of a FPGA's internal registers as well as being able to modify them.
We had an idea to provide a logging function so that we could capture a load of data and basically plot it.
Sounds good... Problem is we can only display reasonably waveforms of around 30Hz. Concidering we were hoping for around 500Hz...
I have the baud set at 115200 and if we probe at the pins data does come in at around that rate, but the next read request there is a 20ms delay...
effectively the program goes
read address
read address
...
Since I am coding via the Windows API to access the COM's port does anyone know of any extra overhead that windows imposes? (the data goes at the correct baud, its just the time between packets)
I am tempted to boot a linux CD to give it a try (with code modifications of course)
All was going well, got a nice GUI showing the status of a FPGA's internal registers as well as being able to modify them.
We had an idea to provide a logging function so that we could capture a load of data and basically plot it.
Sounds good... Problem is we can only display reasonably waveforms of around 30Hz. Concidering we were hoping for around 500Hz...
I have the baud set at 115200 and if we probe at the pins data does come in at around that rate, but the next read request there is a 20ms delay...
effectively the program goes
read address
read address
...
Since I am coding via the Windows API to access the COM's port does anyone know of any extra overhead that windows imposes? (the data goes at the correct baud, its just the time between packets)
I am tempted to boot a linux CD to give it a try (with code modifications of course)