VIN under-voltage event (9.5V) Duet2 Wifi
-
Hello all,
When doing maintenance on my SeeMeCNC Artemis (relubing the ball joints) on power up and homing all steppers I am met with a "VIN under-voltage event (9.5V)" warning message. This will happen about 90% of the time when homing the steppers from power up and after some time being on. After the "VIN under-voltage event (9.5V)" error message, a warning message saying that the motor phase A and B may be disconnected. When viewing other posts about the same problems they resolved the problem with either a power supply replacement or finding a poorly crimped/connected wire and replacing.
When following some of the steps in the other posts, verifying the output voltage of the supply with a multimeter is good at around 13V. This is both true at the output of the supply and at the VIN screw terminal of the Duet2 Wifi. When measuring the voltage of the VIN terminal and trying to home the axis to measure the voltage during the event there is still no change.
Running the M122 command gives back (power good: yes) before and after the event. Below is the first M122 command on power up.
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2.2 running on Duet WiFi 1.02 or later
Board ID: 08DGM-917DA-G4MS4-6JTDG-3SJ6R-98XM9
Used output buffers: 3 of 24 (7 max)
=== RTOS ===
Static ram: 23460
Dynamic ram: 72960 of which 80 recycled
Never used RAM 15580, free system stack 119 words
Tasks: NETWORK(ready,217) HEAT(blocked,294) MAIN(running,125) IDLE(ready,20)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:04:48 ago, cause: power up
Last software reset time unknown, reason: User, GCodes spinning, available RAM 15580, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
MCU temperature: min 16.9, current 24.3, max 24.5
Supply voltage: min 10.4, current 14.1, max 15.3, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: position 169258, standstill, SG min/max 0/432
Driver 1: position 169268, standstill, SG min/max 0/452
Driver 2: position 169446, standstill, SG min/max 0/432
Driver 3: position 0, standstill, SG min/max not available
Driver 4: position 0, standstill, SG min/max not available
Driver 5: position 0
Driver 6: position 0
Driver 7: position 0
Driver 8: position 0
Driver 9: position 0
Driver 10: position 0
Driver 11: position 0
Date/time: 2023-05-10 09:47:01
Cache data hit count 357901610
Slowest loop: 13.83ms; fastest: 0.21ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 1.2ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, maxWait 60986ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 4, completed moves 4, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 15.97ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8- WiFi -
Network state is active
WiFi module is providing access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.25
WiFi MAC address 86:0d:8e:b2:f1:45
WiFi Vcc 3.36, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 22360
WiFi IP address 10.10.10.10
Connected clients 2
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
After trying to home the axis which triggers the under-voltage event and running M122 again the output is below:
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2.2 running on Duet WiFi 1.02 or later
Board ID: 08DGM-917DA-G4MS4-6JTDG-3SJ6R-98XM9
Used output buffers: 3 of 24 (18 max)
=== RTOS ===
Static ram: 23460
Dynamic ram: 72960 of which 80 recycled
Never used RAM 15580, free system stack 107 words
Tasks: NETWORK(ready,217) HEAT(blocked,294) MAIN(running,125) IDLE(ready,20)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:06:29 ago, cause: power up
Last software reset time unknown, reason: User, GCodes spinning, available RAM 15580, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
MCU temperature: min 24.1, current 24.9, max 25.3
Supply voltage: min 7.7, current 14.5, max 15.3, under voltage events: 108, over voltage events: 0, power good: yes
Driver 0: position 320258, standstill, SG min/max 0/282
Driver 1: position 320268, standstill, SG min/max 0/327
Driver 2: position 320446, standstill, SG min/max 0/277
Driver 3: position 0, standstill, SG min/max not available
Driver 4: position 0, standstill, SG min/max not available
Driver 5: position 0
Driver 6: position 0
Driver 7: position 0
Driver 8: position 0
Driver 9: position 0
Driver 10: position 0
Driver 11: position 0
Date/time: 2023-05-10 09:48:43
Cache data hit count 480779124
Slowest loop: 16.93ms; fastest: 0.15ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 1.1ms, write time 4.5ms, max retries 0
=== Move ===
DMs created 83, maxWait 270125ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 7, completed moves 7, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 199.69ms; fastest: 0.10ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8- WiFi -
Network state is active
WiFi module is providing access point
Failed messages: pending 0, notready 0, noresp 1
WiFi firmware version 1.25
WiFi MAC address 86:0d:8e:b2:f1:45
WiFi Vcc 3.37, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 22928
WiFi IP address 10.10.10.10
Connected clients 2
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
In between the before and after M122 commands are the warnings for the motor phase A and B being disconnected shown below:
Warning: VIN under-voltage event (9.4V)
Warning: motor phase A may be disconnected reported by driver(s) 0 1 2
Warning: motor phase B may be disconnected reported by driver(s) 0 1 2Warning: motor phase A may be disconnected reported by driver(s) 0 1 2
Warning: motor phase B may be disconnected reported by driver(s) 0 1 2Error: G0/G1: insufficient axes homed
Warning: VIN under-voltage event (9.5V)Error: over temperature shutdown reported by driver(s) 2
Warning: VIN under-voltage event (9.4V)This seems like a new power supply is needed but not sure since the output voltage of the supply is good and also the VIN to the board is steady when the event occurs.
Help is appreciated!
- WiFi -
-
Sounds like a new power supply would be the most likely solution.
Have you been able to measure VIN with your meter when one of these warnings has occurred?
-
@Caveman-0 first check that the VIN terminal block screws on the Duet are still tight.
-
Thank you both for the quick response!
@Phaedrux Yes, I have been able to measure VIN when the error and warnings occur and the voltage does not drop (stays around 13V). Not sure if it is because the event happens too quick and the meter cannot see the drop, if one is happening.
@dc42 VIN terminal block screws were checked to make sure that they were making good contact and were redone but still having the same warnings.
-
@Caveman-0 what VIN voltage does M122 report?
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 Just powered on the printer and ran M122, current is 14.4.
-
@Caveman-0 either something is causing the PSU voltage to drop as reported, or something is causing the 3.3V rail to rise to about 4.5V. The 3.3V rail is used as the reference voltage for measuring VIN, so an increase in the 3.3V rail voltage will cause the reported VIN voltage to drop.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 Is there anyway that I can test to see if the 3.3V rail is jumping up 4.5V during the event? Would it be beneficial to make the power supply output exactly 12V with the potentiometer?
I also discovered that I get the same warning message when setting the temperature on the heater.
-
@dc42 Was testing some controls within the web browser and it seemed to be acting like it should. Just completed a 1 hour print completely fine. No errors or warnings throughout the print. Even after turning the printer off and back on no errors when heating the extruder or homing the printer.
Would it still be wise to go ahead and get a new power supply?
Could this supply be on the way out which is why the 3.3V rail is unstable or could it be a problem with the board itself?
-
What kind of power supply is it?
If the problem happens again, it might not be a bad idea to swap out the supply. If it solves the problem, great, if not, then there may be an issue on the board with the reference voltage.
Fairly cheap and easy to swap for troubleshooting and you have a spare after. -
@Phaedrux The supply in it now seems to be a non-branded supply (KL-350-12) that came with the printer originally. SeeMeCNC now supplies new printers with genuine MEAN WELL power supplies and in my case the LRS-350-12. I've got one on order and will see if that fixes the problem. If not then ill grab another board and continue troubleshooting.
-
@Phaedrux Do you have any recommendations for troubleshooting the 3.3V reference voltage on the board to see if it is increasing during the event?
-
@Caveman-0 said in VIN under-voltage event (9.5V) Duet2 Wifi:
@Phaedrux Do you have any recommendations for troubleshooting the 3.3V reference voltage on the board to see if it is increasing during the event?
I do not, but @dc42 may.
-
@Phaedrux @dc42 I was able to test the voltage regulator output on U2 and it is supplying 3.3V even during the voltage event. I have a new power supply on the way but I am a little skeptical on if a new supply will fix the problem as the output of the supply seems to be fine. Is there any possible troubleshooting that is recommended before moving forward with a new board?
-
@Caveman-0 So would you able to find out is it the power supply or the board? Since I am having issues with Over-voltage and causing board to shut down. And hence wondering if it is the board that I need to replace or the power supply.
