ve.bus:ve.bus_network_interference
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
ve.bus:ve.bus_network_interference [2024-02-06 03:15] – guy_stewart | ve.bus:ve.bus_network_interference [2024-02-06 22:59] (current) – [Impact of these errors] mvader | ||
---|---|---|---|
Line 5: | Line 5: | ||
This guide should be followed as a pre-cursour to escalation and potential RMA of the GX device and/or the Inverter/ | This guide should be followed as a pre-cursour to escalation and potential RMA of the GX device and/or the Inverter/ | ||
- | ===== Addressing | + | ===== Physical and EM Interference ===== |
Use Manufactured Cables! Always use manufactured cables rather than crimping them onsite. A lot happens at the point of contact. Attempting to crimp cables on site will increase the odds of these issues. The amount of noise to signal goes up dramatically on a less than perfect crimp that visually looks fine and tests ok for continuity. | Use Manufactured Cables! Always use manufactured cables rather than crimping them onsite. A lot happens at the point of contact. Attempting to crimp cables on site will increase the odds of these issues. The amount of noise to signal goes up dramatically on a less than perfect crimp that visually looks fine and tests ok for continuity. | ||
Line 30: | Line 30: | ||
The network quality counters in the VE.Bus system track the number of frame retransmissions required after a VE.Bus device receives an invalid frame. These counters can be accessed via VRM by adding / | The network quality counters in the VE.Bus system track the number of frame retransmissions required after a VE.Bus device receives an invalid frame. These counters can be accessed via VRM by adding / | ||
+ | {{: | ||
===== Key Points on the Counter ===== | ===== Key Points on the Counter ===== | ||
Line 38: | Line 39: | ||
===== Impact of these errors ===== | ===== Impact of these errors ===== | ||
- | **Small Systems:** In smaller setups with a single unit, delays and retransmissions from a Multi to a GX device may not even have noticeable effects. However, there is a known bug that can cause energy meter counts to stop that will be addressed in a future firmware update. | + | **Small Systems:** In smaller setups with a single unit, delays and retransmissions from a Multi to a GX device may not even have noticeable effects. |
**Large Systems:** In larger configurations with numerous VE.Bus devices, the impact of errors grows exponentially, | **Large Systems:** In larger configurations with numerous VE.Bus devices, the impact of errors grows exponentially, | ||
Line 55: | Line 56: | ||
===== Ferrite core cable clips ===== | ===== Ferrite core cable clips ===== | ||
- | The use of Ferrite core noise suppressing cable clips can also help filter out noise. These are a widely available part and available very cheaply. Some Ferrite core clips are supplied with GX devices and should be attached to the GX power supply | + | The use of Ferrite core noise suppressing cable clips can also help filter out noise. These are a widely available part and available very cheaply. Some Ferrite core clips are supplied with GX devices and should be attached to the GX cables to reduce in-line noise and interference. The GX power supply ferrite can be installed with a loop to keep it secure. |
+ | While not normally necessary, if VE.Bus network errors persist install ferrites on each communications cable in the system at each point of connection. This includes the comms cables between each inverter, between the master inverter and the GX, and the battery comms cables. | ||
+ | {{: | ||
===== VE.Bus network topology ===== | ===== VE.Bus network topology ===== | ||
The VE.Bus network is a bus topology, not a ring or any other configuration. | The VE.Bus network is a bus topology, not a ring or any other configuration. |
ve.bus/ve.bus_network_interference.1707185712.txt.gz · Last modified: by guy_stewart