venus-os:v2.60
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
venus-os:v2.60 [2020-06-29 22:12] – created mvader | venus-os:v2.60 [2020-12-15 16:49] (current) – mvader | ||
---|---|---|---|
Line 3: | Line 3: | ||
This draft manual contains notes and/or new texts for the various sections that need changing after releasing v2.60. | This draft manual contains notes and/or new texts for the various sections that need changing after releasing v2.60. | ||
- | ===== Multiple GX Devices for increasing number of tank inputs ===== | + | ===== A) For in chapter 1.4 - Multiple GX Devices for increasing number of tank inputs ===== |
+ | |||
+ | (or to be put in a separate chapter) | ||
==== Introduction ==== | ==== Introduction ==== | ||
The number of tank inputs of a GX Device, such as the Cerbo GX and the Venus GX can be expanded by connecting multiple GX devices together in a VE.Can network. | The number of tank inputs of a GX Device, such as the Cerbo GX and the Venus GX can be expanded by connecting multiple GX devices together in a VE.Can network. | ||
- | Make sure to designate one GX device to be the " | + | Make sure to designate one GX device to be the " |
More details regarding the Main unit versus Secondary units: | More details regarding the Main unit versus Secondary units: | ||
Line 14: | Line 16: | ||
- Only connect the main GX device to the Ethernet network - do not connect the others. For example the MFD App on Marine MFDs is not designed to work with multiple GX devices on one Ethernet network. | - Only connect the main GX device to the Ethernet network - do not connect the others. For example the MFD App on Marine MFDs is not designed to work with multiple GX devices on one Ethernet network. | ||
- (optional - only when using ModbusTCP protocol): only enable ModbusTCP on one of the GX Devices | - (optional - only when using ModbusTCP protocol): only enable ModbusTCP on one of the GX Devices | ||
- | - Only connect the main GX Device to VRM | + | - Only connect the main GX Device to VRM; it will also transmit tank levels received from the secondary units. |
- | - And so forth. | + | - We recommend to connect all VE.Bus and VE.Direct products to the main GX Device. Connecting the via a secondary device will work, but has limitations. For example that Remote configuration doesn’t work, DVCC control will not work, and neither will remote firmware updates. Expanding the VE.Direct ports through USB does give full functionality, |
==== Steps to configure ==== | ==== Steps to configure ==== | ||
Line 32: | Line 34: | ||
- Assign each GX Device its own unique number. Use the test feature when to make sure all went well | - Assign each GX Device its own unique number. Use the test feature when to make sure all went well | ||
+ | Lastly, on the main GX Device, check if all sensors show up in the Device list and work well. | ||
+ | |||
+ | ===== B) Changes to the NMEA2000-out chapter ==== | ||
+ | |||
+ | Many wording changes: "Send data to VE.Can" | ||
+ | |||
+ | Also there is now a menu to change the VE.Can/N2K Device Instances. | ||
+ | |||
+ | Which means that this document needs amending as well: https:// | ||
+ | |||
+ | ===== C) Tank input configration ==== | ||
+ | |||
+ | tbd. Include the new min /max, as well as ten point calibration and so forth. Include screenshots. | ||
+ | |||
+ | ===== D) Reset button seems to have gone missing in Cerbo manual ==== | ||
+ | (make sure to also check Venus GX new manual!!) | ||
+ | |||
+ | https:// | ||
+ | |||
+ | ===== E) Add frequencies to the manual, (required by some countries) ===== | ||
+ | < | ||
+ | Operating Frequencies: | ||
+ | Frequency Range Power Output | ||
+ | 2.402-2.48 GHz | ||
+ | 2.402-2.48 GHz | ||
+ | 2.412-2.462 GHz 2.4 GHz WiFi 88.1 mW | ||
+ | </ |
venus-os/v2.60.1593461569.txt.gz · Last modified: 2020-06-29 22:12 by mvader