Web Gui Error - error in action: Exception: libodrive error 8

I recently purchased my ODrive so I’m very new to this all. I have my ODrive S1 connected with a USB isolator and a Lipo 6s. Yesterday, I had it working on the web GUI.

Whenever I go to the web GUI now, it still detects it, I can look at current voltage, etc. so it’s communicating properly with the ODrive, however whenever I try doing anything in the “Apply and Calibrate” tab, it throws me an error:

“error in action: Exception: libodrive error 8”

It instantly disconnects the ODrive, and then kind of reconnects it again? Sometimes it does, sometimes it doesn’t reconnect. However, it happens exactly like this, the error will only occur once I try to do that, or update firmware.

I don’t know what’s going on, it’s not even attempting to calibrate or anything, its as if anytime I try getting the usb to communicate to the odrive, it glitches

But it’s confusing because the ODrive is communicating to my computer completely fine. The battery is properly powered, all the wires are straight, not tangled, and I’ve tried multiple browsers and USB ports.

I also got the same problem today. It is like yesterday, everything works fine. However, today when I tried to play the board, it popped up libodrive error 8. Hope there is someone who can provide the solution.

Oh wow, really hoping it’s just a problem on O-Drives side then… super worried I messed my S1 up or something otherwise. If you happen to find out a solution please let me know!

Same here, it was working on Monday morning, then I had the same error on Monday afternoon.
Trier with different boards/cables/computers/browsers, I always get the same error.

Sorry for this problem!

This is a bug that was accidentally introduced in a GUI update yesterday. I rolled back the bad release around 4.5h ago. If you’re still experiencing the issue you can try shift+reload, and then it should work normally again.

Meanwhile we fixed the issue in the newer release and we’ll be doing some more internal testing before deploying it again.

Thanks to all for reporting and sorry for any downtime this has caused!