-
Notifications
You must be signed in to change notification settings - Fork 313
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Display CRC bytes? #358
Comments
Look in hdlc_rec.c. Somewhere around line 562, depending on the exact version you have.
#if TEST Delete the two lines beginning with "#" then rebuild. |
WONDERFUL!! Thank you so much! |
Thank you again for pointing me to the file where the 'fcs' bytes can be printed. I have tried positioning that print statement in numerous places above & inside of those 'if' statements, but nothing results in the expected printout. This is a fresh 'git clone' of the latest MASTER branch. One example of my edit is: ... but after deleting the /build folder and completely rebuilding/reinstalling, the output is not changed: ... did I do that incorrectly? Thanks so much! -Scott |
Found a work-around! If I understand correctly, that entire section of code was controlled by a flag called "OLD_WAY", which was not set. I commented that out, along with a couple of corresponding lines farther down, and then found a place that will print the CRC bytes with each valid frame (don't know why they print 9 times, but that's ok) ... and my output: ... so that will do the job until / unless you have time one day to provide a more proper method. This is extremely useful for examining packets in regard to what is 'really' being transmitted over-the-air. Thanks very much! -Scott |
Good day!
Is there any way to actually DISPLAY the CRC bytes that were transmitted by a sender?
The question is not whether a packet's CRC is correct - but rather a tool is needed here to actually VIEW the CRC bytes so that we can confirm which CRC calculation is being included with outgoing packets.
Many thanks!
-Scott, K4KDR
The text was updated successfully, but these errors were encountered: