I am experiencing a critical issue with my Victron Lynx Shunt VE.Can 1000.
After performing a Battery Voltage Calibration in VictronConnect, the voltage reading has become stuck at 0.00V. Since then, the shunt no longer reports the correct battery voltage.
I have already tried the following steps:
Performed the calibration multiple times with the correct battery voltage.
Fully powered down the system and reconnected.
Downgraded firmware to v1.08 and repeated calibration, then upgraded again to v1.10.
Performed Reset to defaults.
Verified with a multimeter that the correct voltage is present at the Lynx Shunt terminals.
Despite all attempts, the Lynx Shunt still shows 0V.
Could you please advise if there is a way to restore the calibration values (e.g. a service tool or special firmware), or is an RMA / replacement required?
Were you able to find a solution? I’m having the same issue and have tried just about everything without success. It’s been frustrating to say the least. Appreciate your feedback.
No, unfortunately I don’t know the solution. Everything was working perfectly. But I tried clicking the Start button (Battery voltage calibration). I entered a more precise voltage value on the bus. And after that, my Lynx Shunt turned into a brick. Now it always shows 0V, and on top of that it doesn’t display the SOC anymore.
I tried setting a different SOC value, synchronizing to 100%, and starting the calibration procedure again. But the voltage is still 0V, and the SOC resets again. At the moment, the Lynx Shunt only shows the current, with 0V voltage and 0W power.
But the SOC changes after synchronization or manual setting, so maybe the algorithm does not use the voltage to determine SOC, but only the current and the duration of that current.
Appreciate the reply, Andrew. The exact same thing happened to me. I installed the Lynx Shunt on Friday and it worked great, except for the inaccurate voltage reading, until yesterday when I tried the “Voltage Start Calibration” to correct a 0.75v difference (a big deal for this particular installation). After going through the process, the voltage was arbitrary set to 0.00v. Battery bank was fully charged with a stable voltage and current. Now when I try to go through the process again, the +/- are grayed out and when I enter a value manually it reverts back to 0.00v no matter what I do.
I tried resetting the unit, downgraded firmware to v1.08 then upgraded again to v1.10, shut down the entire system for 10 minutes and nothing helped. Like you, I now have a shunt that only measures current and soc. It’s such a shame because I’ve used the much cheaper Victron Smart Shunt for years with absolutely no issues.
Fortunately for me, this is a brand new unit so I’m getting a replacement Wednesday. I’m now concerned about how reliable these expensive units are (I’ve seen people online calling them very expensive fuse holders with inaccurate voltage values) and having to worry that the unit is going to “destroy itself“ each time I change a setting or perform a firmware upgrade is totally unacceptable in a production environment. I love Victron products and I’ve used them for a while. I’m actually surprised that Victron has released a product with obviously buggy firmware.
Sorry for the rant and thanks again for getting back with me.
I don’t have a new device, but everything happened exactly as you described. It is clear that this is a shortcoming and most likely a bug either in the firmware or in the VictronConnect app. Victron representatives can easily verify this. Since there are already at least two identical cases – yours and mine – this is no longer a coincidence, it’s a pattern.
I have a large system and unfortunately I cannot replace the Lynx Shunt with any other device. That’s why I really hope Victron will fix this bug soon. I’m confident they will, and other users will not face the same issue.
By the way, if someone still has their Lynx Shunt under warranty, this might be a “unique” way to render it inoperative and get a replacement with another model. The service would replace it, and even the manufacturer might not immediately realize what exactly caused the failure. Thanks to me sharing my problem here and you confirming it, Victron can now see the pattern. Otherwise, other users would keep bricking their devices and Victron would just keep replacing them.
I’m also concerned whether a special service utility will now be required to bring the device back to life. That’s why I believe once Victron representatives read our discussion, they will understand that this bug must be fixed urgently to avoid huge losses.
I hope someone from Victron reads this post and understands the urgency on this and the implications of not having this issue addressed promptly. I forgot to share something interesting (attached screenshot). After resetting all the historical data, the battery voltage is now showing negative values. Something is definitely wrong with the firmware and/or VictronConnect app. I also verified with a multimeter that the correct voltage is present at the Lynx Shunt terminals. Hope this helps Victron representatives addressing this particular issue.
