venus-os:mfd-raymarine
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
venus-os:mfd-raymarine [2021-12-09 09:49] – [7. NMEA 2000] mvader | venus-os:mfd-raymarine [2021-12-09 19:21] – [7. NMEA 2000] mvader | ||
---|---|---|---|
Line 87: | Line 87: | ||
=== Raymarine only: data instances need to made unique === | === Raymarine only: data instances need to made unique === | ||
- | If there are more than 1 (for example) SmartShunts in the NMEA2000 network, or a Solar Charger and a SmartShunt, then the Data instances of the Victron | + | If there are more than 1 (for example) SmartShunts in the NMEA2000 network, or a Solar Charger and a SmartShunt, or any other device that transmits the same type of PGNs, then the Data instances of those PGNs need to changed to make each data instance unique. |
+ | |||
+ | Typically this concerns the Battery instance, used in the Battery Status and DC Detailed PGNs. | ||
See here for how to do that: [[https:// | See here for how to do that: [[https:// | ||
**Note**: this requirement of data instances being globally unique for a PGN is specific to Raymarine. Other brands do not require this. And, although perhaps besides the point, also the NMEA2000 standard does not require it. More specifically, | **Note**: this requirement of data instances being globally unique for a PGN is specific to Raymarine. Other brands do not require this. And, although perhaps besides the point, also the NMEA2000 standard does not require it. More specifically, |
venus-os/mfd-raymarine.txt · Last modified: 2023-06-22 19:32 by sloges