Regular Member
Joined: 27/04/2012
Location: AustraliaPosts: 42
| Posted: 10:35pm 19 Jun 2024 |
OK, I see you need the extra overhead because your packets vary in size.
My application has fixed packet sizes - each of 3 PICOs sends its 4 channel ADC data as 8 bytes (2 per ADC), little-edian format to PICO#0. Each PICO has a slight delay before sending to make sure there's no overlap of data. PICO#0 has its own 8 bytes so it appends the 24 bytes received from the others and then sends the 32 byte packet to the computer. I'm running the ADCs at 360 samples per second so that's why I need the high speed to transfer data.
So as I mentioned I found that a byte is randomly dropped when transferring data to PICO#0 so to eliminate problems with multi-drop, timing, etc I setup 2 PICOs with a hardwired connection from Tx on PICO#1 to RX on PICO#0 as shown in my first post. And that's what surprised me - a byte still gets dropped randomly during data transfer. I slowed down data transfer to ten packets per second but the problem still occurs even at 1 transfer per second except you have to wait longer to see it.
My conclusion is that there must be a bug in the INPUT$ command.
Matherp - could this be the case?