-
Notifications
You must be signed in to change notification settings - Fork 71
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
Allow configuration of display & DSC bits #76
Comments
I believe this flag in message 18 indicates whether the transponder itself is equipped with a DSC receiver for frequency management. Could be wrong, of course. |
I think it doesn't matter if the display/dsc is a separate physical device if they both operate under same MMSI? |
Look at the fields in the message descriptor here: https://www.navcen.uscg.gov/?pageName=AISMessagesB and here: http://vislab-ccom.unh.edu/~schwehr/software/noaadata/ais-messages/ais_msg_18.html What do you make of these? To me, all those flags in that section indicate whether the unit can be switched outside of the default AIS channels, via message 22 and DSC transmissions. Can you locate a more thorough explanation? |
I checked them before and saw that the description speaks of "this device". But if I have two devices right next to each other and the other has display and DSC, (also AIS receiver but that is irrelevant) and the other is sending AIS class B messages, for all intents and purposes they are basically the same device? |
Not from the AIS perspective. The question this flag answers is: "Does this unit contain either a dedicated or time shared DSC receiver so it can listen for frequency management messages on channel 70 and thus change its frequency of operation?" The answer for MAIANA's current design is always "no". |
Here is a bit more context (this is a length doc): https://www.navcen.uscg.gov/pdf/AIS/AIS_ChMgmt_(view%20bookmarks).pdf |
I understand that from MAIANA's point of view. But like I said, if the vessel has a separate receiver that fulfils that requirement for the same MMSI, MAIANA should be able to be configured to advertise it. They are in the same vessel, using same MMSI. If for some reason MAIANA had two different microcontrollers in separate PCBs, other dedicated for DSC and other for AIS, would it set the bit on? I think yes. In my point of view what I'm asking is exactly the same, the only difference is that the microcontrollers just happen to be physically located in different case / PCB. |
In order for this flag to be "yes", MAIANA should have:
Are you saying that you plan to augment its functionality with this capability based on your existing setup? |
No, I am saying that I have a device that has:
What the device is not doing is sending AIS Class B messages, which is the job of MAIANA. |
OK, now I get it. Still though, MAIANA is not capable of automatically (or manually) switching its operating frequency right now. So even though it might advertise the capability you're proposing, it will keep operating at the default channels anyway. Now, if you want to implement a mechanism by which you can use your other AIS receiver to control MAIANA's operation, then that's interesting. |
I was thinking about this (and also to implement a parser for receiving GPS / heading related NMEA messages), but instead of USB I would rather use the nmea2000 interface so I'm waiting for that. |
First N2K boards should be coming this evening, so I will know by tomorrow if it's finally ready. That said, the N2K code (which I haven't released to Github yet) does not register as a consumer for any N2K messages, it's only a node, so that would need to be changed for bidirectional interaction. Would this be done using a custom PGN? I'm not aware of any AIS frequency management PGNs. |
Yes, custom PGN would be the way to go |
but in any case, the display bit should be straightforward and it would be just enough to set it to user configurable. |
Agreed on the display bit |
The vessel might have a separate VHF DSC/AIS receiver that has a display and supports DSC, so advertising them should be configurable in message 18
The text was updated successfully, but these errors were encountered: