I couldn't easily find documentation on how to enable flow control on the beaglebone side so I chose to add a CRC32 checksum to each line. The data now looks like:
102.04541 125 1186 3665238047 102.04588 125 1273 3232659341 102.04635 125 1273 3345150538 102.04708 125 1245 4074941927 102.04756 125 1245 943190513 102.04803 125 1303 526161833 102.04850 125 1274 3970916767 102.04898 125 1273 472341404 102.04970 125 1100 2928958186 102.05018 125 1244 2418030567 102.05066 125 1187 2253189159 102.05113 125 1157 1456340796 102.05161 125 1273 258216438 102.05234 125 1012 3972342546 102.05282 125 1214 2310087250 102.05329 125 1274 2579294272 102.05377 125 1215 1325398437 This means that corrupted lines are easy to detect. I then deal with data being missing later on in the analysis pipeline. >> Here is my reading algorithm from c lib on linux it detects a pause in the transfer Unfortunately the code I am writing on the PC side is called too infrequently for this to help. The 12k buffer can occasionally fill up and lose data in the gap between two calls. I could make a seperate thread regularly poll the windows API to see if there was new data but a checksum was simpler to implement as I am not familiar with threading. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/6ae68cf8-3eae-41c2-be5f-2e78a77652f5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
