-
Notifications
You must be signed in to change notification settings - Fork 100
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
SIS messages? #38
Comments
@itdaniher SIS message type 4 would need to be implemented here: Lines 122 to 124 in 12d9526
Note that SIS parsing is only on the experimental branch currently; it hasn't been merged to master yet. The format is described in http://www.nrscstandards.org/SG/NRSC-5-C/1020sI.pdf section 4.4. |
Brilliant, thanks! I'm actually starting with processing time transmissions (MSG ID 0b0111 / first few indexes) / SIS Parameter Messages first, but it looks like doing so will require introducing state in the PIDS parsing to accumulate time metadata. I haven't looked enough at the code yet to figure out how to most elegantly do so - maybe define relevant structs in pids.h? Cheers! |
Yep, storing state in a structs would make sense. There are other places that's done already. |
#79 implements most of the remaining pieces, apart from Universal Short Station Name. |
I'm going to close this off now, since nearly all SIS messages are now decoded. |
I'm interested in trying to use the SIS Parameter Message and possibly station location from the SIS PDU Messages to establish a crude time / location for a distributed sensing project, but it looks like this information isn't decoded right now. It looks like I'd need to start with
frame.c
- maybe inframe_process
but I'd appreciate any pointers in the interim.Cheers!
The text was updated successfully, but these errors were encountered: