Fix for parsing failure on some track lines #3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For some reason, the following line fails to parse when getting tracks
G20 FF 60200 005000 780 383 1239 -4107668 43 14220 24 25 18 123 -10 75 -4 75 -4 16 0 0 L3P 05
when trying to get the checksum value.
Line 411 panics not finding the characters.
It must have to do with formatting hex doing some weird stuff which I have no clue about.
Simplifying this to just get the string works fine since the actual checksum check is commented out anyway, and converting to hex can be done then if needed