Strange startup
-
@dorro1971 said in Strange startup:
As a work around i've set the bed to 55 degrees in the last line of config.g.
Does that really solve the problem?
The M408 response that you posted:
M408
{"status":"O","heaters":[42.6,36.6],"active":[0.0,55.0],"standby":[0.0,55.0],"hstat":[0,0],"pos":[0.000,0.000,0.000],"machine":[0.000,0.000,0.000],"sfactor":100.00,"efactor":[100.00],"babystep":0.000,"tool":-1,"probe":"1000","fanPercent":[30.0,100.0,100.0,0.0,0.0,0.0,0.0,0.0,0.0],"fanRPM":0,"homed":[0,0,0],"msgBox.mode":-1}was taken when your Duet had 5V power (perhaps from USB) but no VIN power - that's what status "O" means. So I assumed the problem you were getting was because you were not applying VIN power. If you still get the problem when VIN power is applied, please run M408 again when the PanelDue is failing to connect but you have VIN power applied (and without that extra line in config.g of course).
-
Duet is powered all the time from startup, no usb input.
if i set bed temp to 55 or more it goes to idle if i then set bed temp to 0 everything still works.
only power source is Vin 24v...(actually 27.5)..maybe a litlle high?
and yes that solves my problem I just don't like not knowing why..
panel duet says "disconnected" but still reports temperature changes...so it must be connected right?...it won't read memory card until i do the bed temp thingy...
a real puzzler...
also if i pause and canccel a print, when i restart it it homes but hangs..this may be a slicer issue but the first run is fine and if i do a second after completion it's fine...only a problem if cancelled...
-
This post is deleted! -
when my current print is complete i'll double check......
-
Ok, initial power on..24v only, last line of config removed.
M408
{"status":"O","heaters":[44.0,54.9],"active":[0.0,55.0],"standby":[0.0,55.0],"hstat":[0,2],"pos":[0.000,0.000,0.000],"machine":[0.000,0.000,0.000],"sfactor":100.00,"efactor":[100.00],"babystep":0.000,"tool":0,"probe":"1000","fanPercent":[30.0,100.0,100.0,0.0,0.0,0.0,0.0,0.0,0.0],"fanRPM":0,"homed":[0,0,0],"msgBox.mode":-1}after m140 s55 issued
M408
{"status":"I","heaters":[52.2,55.0],"active":[55.0,55.0],"standby":[0.0,55.0],"hstat":[2,2],"pos":[0.000,0.000,0.000],"machine":[0.000,0.000,0.000],"sfactor":100.00,"efactor":[100.00],"babystep":0.000,"tool":0,"probe":"1000","fanPercent":[30.0,100.0,100.0,0.0,0.0,0.0,0.0,0.0,0.0],"fanRPM":0,"homed":[0,0,0],"msgBox.mode":-1}Checked wiring,..all good..is it worth re updating duet and panel duet?
Any ideas...thank you..
-
Before you send the M140 command, please send M122 and check the reported VIN voltage.
-
I'll do that...I wonder if the voltage is under low load. switching the bed on causes current draw and the psu to step up?
It's printing now, I'll try that tomorrow..i'll also drop a volt test on it...
Thank you.
-
19:48:06
M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 2.01(RTOS) running on Duet Ethernet 1.02 or later
Board ID: 08DGM-956GU-DJMSN-6J1DJ-3S86L-K9R3G
Used output buffers: 3 of 20 (13 max)
=== RTOS ===
Static ram: 28476
Dynamic ram: 95932 of which 16 recycled
Exception stack ram used: 272
Never used ram: 6376
Tasks: NETWORK(ready,328) HEAT(blocked,1324) MAIN(running,3564)
Owned mutexes:
=== Platform ===
Last reset 00:01:02 ago, cause: software
Last software reset at 2018-10-15 19:47, reason: User, spinning module GCodes, available RAM 6140 bytes (slot 0)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 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 28.3, current 29.0, max 29.1
Supply voltage: min 27.6, current 27.7, max 27.8, under voltage events: 0, over voltage events: 0
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: 2018-10-15 19:48:06
Slowest loop: 6.17ms; fastest: 0.07ms
=== 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 = 0 -1 -1 -1, chamberHeaters = -1 -1
Heater 1 is on, I-accum = 0.0
=== GCodes ===
Segments left: 0
Stack records: 2 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: 6.22ms; fastest: 0.03ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8
Interface state: 5
=== Expansion ===still says disconnected until i issue M140 S(>55)...
I'll uncomment the last line of config for now...
Voltage test with meter did not show anything wrong....
PUZZLE....
-
tried it with ethernet disconnected just in case...still no difference...
-
Your VIN voltage read by the Duet is above the recommended maximum normal voltage of 25V and quite close to the shutdown point of 29V. What does your multimeter show the VIN voltage to be?
-
my meter shows 27.85..off load!!!..ill drop it back to 25..and retry...
-
I am so very sorry!
I lowered the supply down to 25v and now its reliable on start up..I guess the load from the bed current dropped the voltage just enough, although i doubt the cpu was in shutdown.
I have also had a horrible thought...I had wifi issues earlier in the year, random disconnects and connection failures...I wonder uif they were related.........
I might re graft the wifi board and try again...
Once again, please accept my apologies i missed this one by a mile,...if it's any consolation,...I really like using the duet.
I now have three machines running it and will spread the word, you support is second to none!
-
I'm glad we solved it, but I'm surprised that the M122 report didn't show one over-voltage event. The over voltage protection kicks in at 29V and resets when the voltage falls below 27.5V.
The over voltage protection should not affect the WiFi subsystem.
-
Hmmm...ok..
Thank you for your assistance anyhow,..one for the memory banks...
