Pause button ghosted

Kulitorum

@wilriker Nice catch, thank you.

dc42

Status "Off" means that the VIN monitor thinks the input voltage is below 9.5V. Normally the printer wouldn't be able to run at this voltage, but of course you are using all external drivers and no heaters. Were you powering the Duet from USB or other external 5V power only?

wilriker

@kulitorum I also noticed that you are still running a release candidate (RC3) of 2.02. I think you should update to final 2.02 as this might already fix the issue.

Kulitorum

@dc42 But as you can see, the input voltage is 27.9v.... Maybe I just burned the input regulator-thingy?

dc42

No, the voltage sensing used to set the state is the same voltage sensing used to display the max/min input voltage.

Which firmware version are you using? You said 2.02 earlier, but your M122 report shows 2.02RC3.

Kulitorum

So.....I guess my Vin could have passed 30v for a while, and burned the input voltage measurement circuit, making the duet think that its underpowered and causing the board?

Than again, the M211 command reports : Supply voltage: min 27.8, current 27.9, max 27.9, under voltage events: 0, over voltage events:

So....?

Kulitorum

Kulitorum

@kulitorum said in Pause button ghosted:

M122

Updated firmware, same result:

4:21:08 PMM122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.02(RTOS) running on Duet Ethernet 1.02 or later
Board ID: 08DGM-917NK-F23T0-6J1DD-3SJ6K-9Z8WG
Used output buffers: 3 of 20 (13 max)
=== RTOS ===
Static ram: 25524
Dynamic ram: 98064 of which 0 recycled
Exception stack ram used: 272
Never used ram: 7212
Tasks: NETWORK(ready,544) HEAT(blocked,912) MAIN(running,3868) IDLE(ready,200)
Owned mutexes:
=== Platform ===
Last reset 00:01:24 ago, cause: software
Last software reset at 2019-02-04 16:12, reason: User, spinning module GCodes, available RAM 7180 bytes (slot 0)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0440f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
Error status: 0
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest block write time: 0.0ms, max retries 0
MCU temperature: min 36.8, current 37.0, max 37.4
Supply voltage: min 27.8, current 27.8, max 27.9, under voltage events: 0, over voltage events: 0, power good: no
Driver 0: ok, SG min/max not available
Driver 1: ok, SG min/max not available
Driver 2: ok, SG min/max not available
Driver 3: ok, SG min/max not available
Driver 4: ok, SG min/max not available
Date/time: 2019-02-04 16:21:04
Cache data hit count 159807234
Slowest loop: 3.65ms; fastest: 0.06ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0
=== Move ===
Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm: 240, MaxWait: 0ms, Underruns: 0, 0
Scheduled moves: 0, completed moves: 0
Bed compensation in use: none
Bed probe heights: 0.000 0.000 0.000 0.000 0.000
=== Heat ===
Bed heaters = -1 -1 -1 -1, chamberHeaters = -1 -1
Heater 0 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Stack records: 1 allocated, 0 in use
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
serial is idle in state(s) 0
aux is idle in state(s) 0
daemon is idle in state(s) 0
queue is idle in state(s) 0
autopause is idle in state(s) 0
Code queue is empty.
=== Network ===
Slowest loop: 4.20ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8
Interface state 5, link 100Mbps full duplex

Kulitorum

And its still "OFF"

dc42

M122 only shows you the min/max voltage since you last ran M122, or since power up if you haven't run it yet.

I suspect that the voltage reached 29V, which caused the firmware to switch the drivers off to help protect them. They won't be switched on again until the voltage drops to below 27.5V. Since your minimum is 27.8V, that won't happen, so the printer remains in the Off state..

Kulitorum

@dc42 said in Pause button ghosted:

M122

You were right. Taking the voltage down to 26v fixed the problem. thanks.

Kulitorum

Maybe add a warning message to the "!" in the top left corner?

Kulitorum