If I've done my research correctly, it looks like you have basically two options for retrieving waypoint data:
1. Do a single read, and get the entire string of data and then parse through it in LabVIEW.
2. Do multiple reads, and get the individual elements piece by piece in LabVIEW.
It really depends on how confident you feel with your LabVIEW string manipulation skills which one you choose. I would probably recommend that you use the second option, simply because you can specify how many bytes of data you want for each piece. Here's what I was able to find:
| Description | # of bytes to read |
| Start of message | 1 |
| Waypoint record ID | 1 |
| Number of message bytes to follow | 1 |
| Waypoint ID | 6 |
| Latitude | 4 |
| Longitude | 4 |
| Time waypoint stored | 4 |
| Waypoint comment | 40* |
| Checksum | 1 |
| Message terminator | 2 |
*where the number of bytes that your read for the waypoint comment is determined by the following formula:
Number of message bytes to follow - Waypoint ID bytes - Latitude bytes - Longitude bytes - Time waypoint stored bytes
As you read each element you can then take the data that's returned and use the string to number conversion functions in LabVIEW as needed. There may still be more to this, but let me know what you are able to do with this information, or if any of the information is incorrect.
Logan S.
