| Author |
 Topic  |
|
|
sprezzatura
Canada
14 Posts |
 Posted - 02/06/2020 : 12:13:41
|
When my program sends a "<SPIR...>>" command, I get a burst of 224 (sometimes 288) bytes immediately.
Then, there is a 24-second delay, and I get about 2,560 more bytes.
Finally, a total of 4096 bytes after 42 seconds. That's the equivalent of about 878 Baud... on a 115,200 Baud line? What on earth is it doing?
878 Baud = 4096 * (8 data bits + 1 stop bit) / 42 seconds.
So what you're saying is that the only way to determine that the entire log has been transmitted, is to perform a loop asking for a preset amount of data at each iteration (ex: 4096), and sit there and wait for a minute or more, each time, until nothing more is received?
There's gotta be a better way :o) |
|
| Reply #1
EmfDev
2250 Posts |
Posted - 02/06/2020 : 12:59:48
|
| There is probably something wrong with your software. The EMF-PRO software is using SPIR commands to get 4096 bytes of data each request and it doesn't take that long. |
 |
|
| Reply #2
sprezzatura
Canada
14 Posts |
Posted - 02/07/2020 : 10:02:30
|
Looks like you're right: the GQ Pro software downloads 177,717 bytes in 2:22 min, which is 11,263 Baud (bits per second). Although that's still pretty slow.
My software is generic USB/Serial protocol. It just sends a <SPIR>> and sits there and waits. |
|
|
| |
Topic |
|
|
|
Why is GQ-390 data download so slow?
