Duet 3: "Attempt to move motors when VIN is not in range" @ 30V
-
It's a bug. That code should be active for the Duet WiFi/Ethernet build but not for the Duet 3 build of RRF. I will fix it in the next beta.
-
-
I've updated to the latest firmware version, and this issue persists.
If it helps, the web app is reporting these versions:
Board: Duet 3 version v0.6 (MB6HC) DSF Version: 1.1.0.5 Firmware: RepRapFirmware for Duet 3 v0.6 3.0beta11 (2019-10-21b1)I don't want to be a jerk, but...any ETA? It's been a month now.
-
Are you certain that it isn't fixed? I put the fix in the source code well before beta 11.
-
@dc42 the current v3-dev still has
https://github.com/dc42/RepRapFirmware/blob/v3-dev/src/Platform.cpp
constexpr uint16_t driverOverVoltageAdcReading = PowerVoltageToAdcReading(29.0); // voltages above this cause driver shutdown
-
@Veti said in Duet 3: "Attempt to move motors when VIN is not in range" @ 30V:
@dc42 the current v3-dev still has
https://github.com/dc42/RepRapFirmware/blob/v3-dev/src/Platform.cpp
constexpr uint16_t driverOverVoltageAdcReading = PowerVoltageToAdcReading(29.0); // voltages above this cause driver shutdown
This
constexprneeds to stay for Duet 2 (and possibly other boards as well) - it's the place where it is used that seems to fail for Duet 3 to do the right thing. -
but should there not be a constexpr for the duet3 over voltage where it shuts down?
-
I am sorry, there were two places where maximum VIN was enforced, and I only changed one of them. New firmware build coming soon.
-
Awesome -- thanks, @dc42!
-
You can try the new firmware at https://www.dropbox.com/sh/3azy1njy3ayjsbp/AACquxr2m00eV568RZg5QG5wa?dl=0 if you like. This isn't an official beta, but it's running OK on my test setup.
-
Just tried the firmware from dropbox, and it works like a charm. Thanks for taking the time to put this out on a weekend!
Also -- and I'm sure you get this a lot -- but I can't get over how easy the firmware update was. Kudos.
