-
Notifications
You must be signed in to change notification settings - Fork 272
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
Error Correction for Unit/Source ID in LCW #39
Comments
Yes, the whole LCW is protected by Hamming and Reed-Solomon codes. If no error is detected the source ID is likely correct. LCW shows up in "LDU1" (voice) and "TDU with link control info" units. Not sure which field to refer by "Unit ID," if you mean the "data unit ID" on the network identifier (NI), yes, it's also error protected. Kind regards, Ed |
That is great! I was just referring to the Source ID, I had also seen it I am capturing the Source that is generated at line 149 of p25_lcw.c . If I Thanks again for adding in all the error correction! On Sun, Jun 8, 2014 at 11:41 PM, EdFuentetaja notifications@github.com
|
To answer my own question - it looks like you can use irrecoverable_error to determine whether the Source ID is good or not. |
Is the Unit ID / Source ID covered by any error correction or detection? I am getting some really weird values for Source. I have been logging them, and I am getting a bunch of Source IDs that are high and only show up in a single LCW message.
Is there another P25 Message that also contains Source ID and is covered by error correction or detection?
The text was updated successfully, but these errors were encountered: