I hooked up my Lynx Shunt in reverse. Works fine except the current is showing the wrong sign and % is counted down instead of up when charging. First upgraded the firmware to 1.10 but that did not change anything. I did not know this was not supposed to work (found all the mentioned information below after I noticed the problem) otherwise I would not have bought this. All I wanted was a more accurate percentage left because my 4 Pace 16S200something BMSes have accuracy issues with low currents and make 10-15% jumps to 100% when the batteries get full.
Whiile investigating I found a video from Andy from TheOffGridGarage for his Lynx Shunt settings and compared my settings to his. I looked in my Victron Connect App on iOS, from Device List I connected through VRM, then Devices to the Lynx Shunt and found this option “Current measuring direction” but it does not do anything and the setting is forgotten when you close the app or change between VRM portal entries. The option is sort of new I guess, Andy’s video was from 2 years ago and it did not show this option yet.
My question: Is this a bug or is this option not supposed to be there? I can always do the hack of changing the 5 wires as described in multiple posts here and in the old forum but I’d rather not void my warranty with that unless this option will not be fixed.
The VictronConnect changelog for the current version 6.18 only mentions that feature for the BMV-712 and SmartShunt, the Lynx Shunt isn’t mentioned there.
So I guess it’s a bug that this option is even shown in the settings of the Lynx Shunt.C
Can you add a screenshot please?
(The current FW 1.10 for the Lynx Shunt is over 1,5 years old)
But you can modify the internal wiring of the Lynx Shunt to reverse the measurement.
Just flip the small wires connected to the shunt.
(It’s not officially supported but I did it a few times without problems)
I have a temporary 200A Adler fuse in there because the Lynx Shunt does not come with the massive metal bar… Is it possible to order that metal bar separately?
If this is a bug that it is not supposed to be shown here, how do I make Victron aware of this issue? Open a support issue? Or do you have a better way to inform them?
Yeah the app is fixed now but disappointed that there is no official solution except modify the hardware and lose warranty, when all that needs to be done is modify the charged/discharged Ah value by multiplying it by -1 or just inverting the highest bit, the error is minor with 1- vs 2-complement. Oh well, my fault for not investigating this properly before buying.
Anyway topic can be closed, thanks everyone for the input!
I don’t think there would be any loss of warranty for swapping the two leads over on the shunt, its not a sealed unit. When Matthias said its not officially supported that doesnt mean its completely forbidden just not a supported configuration.
Personally I’d like the firmware to be adjusted so that a system with a lynx shunt and “has dc system” selected would show that dc load as consumption in VRM, just like a smart shunt does. Instead it complete ignores that for consumption tracking. Just doesnt make sense.
So I’ve had to go for a Victron energy meter to attach to my rosie inverter so I can actually see consumption again in VRM. $350 for lynx shunt, $200 or so for a 3P75T and 0.5A breakers, versus what a $100 smartshunt can do out of the box…
Example can see when I switched from smartshunt to lynx shunt…
You are right, it is unknown whether Victron will actually be enforcing the loss of warranty on a unsupported modification or not but consumers have to assume Victron will do the same as almost every other manufacturer out there does because they can’t guarantee proper functioning with this modification.
I fully agree with the firmware modification you mention, it is something that is needed but if even Andy from Off Grid Garage Australia can’t get anything to happen in this direction I doubt us discussing it here will change anything. I saw several threads regarding that topic here all without a response from Victron. Oh well…
