Flakey Behaviour from Duex 5
-
I have upgraded to 2.02 (RTOS) and Web Version 1.22.6 and still have the same problem.
E2_STP is not being seen by the board. The light on the board is changing state, but the screen under Settings->Machine Settings is not changing state when I move my carriage over and back.
-
Is it just E2_STP not working, or all of the DueX endstop inputs? Are the DueX fans working?
-
I appears to be all the end stops on and the fan outputs on the Duex. I confirmed the sensors used and fans used to test work on the Duet. I used M106 and M107 to turn the fans on and off on fan 0 then moved that fan to fan 7 and 8 and could not get them to turn on.
The endstops are working on the main board and then moved to the Duex and the lights come on on the board, but the state does not change on the Settings page on the web interface.
The 3 extruder fans that are acting up are also on the Duex (not on the main board).
So I am gathering that I have a Duex that is goosed, correct? But the main board seems to be functioning properly.
-
@dougjones said in Flakey Behaviour from Duex 5:
Sometimes the board powers up and does not recognize the Duex. Under the settings screen, it does not say Duet Ethernet + Duex 5, just Duet Ethernet.
If it doesn't recognise the DueX then the DueX endstops and fans will not work.
-
When it does connect, This is happening.
The stepper drivers appear to work thermister inputs work. The Endstops and Fan outputs do not seem to be working.
-
@dougjones said in Flakey Behaviour from Duex 5:
When it does connect, This is happening.
The stepper drivers appear to work thermister inputs work. The Endstops and Fan outputs do not seem to be working.
That indicates that I2C comms between the Duet and the DueX has broken down, even though it must have been working well enough when the DueX was recognised at startup. If you run M122, I expect you will see a lot of I2C errors reported.
-
I cannot seem to get the Duet to reliably start. Meaning, the red diag led by the ethernet just blinks and I cannot connect to the web interface.
When it does start sometimes it finds the duex 5 board and sometimes not.
When the board is found it almost never shows the endstops changing state.
That said, after a whole lot of screwing around tonight, removing and re-seating connectors, checking contacts and replacing cables. I got it to all connect properly and the drivers were working, endstops functioning, I even homed the machine. I re-taught my z-probe height (un-related by i had removed my bracket and needed to reset zero position).
Everything was grand, decided to power cycle the machine again and double-check to make sure I had fixed it. And nope, same set of problems, won't detect Duex or devices on Duex won't respond.
I checked M122 and am getting nak errors. No other IIC errors reported.
-
@dougjones said in Flakey Behaviour from Duex 5:
I cannot seem to get the Duet to reliably start. Meaning, the red diag led by the ethernet just blinks and I cannot connect to the web interface.
Possible causes:
- Power supply problem
- Problem reading the SD card
- The blinking LED could indicate that the Duet is in a reboot loop. Next time you succeed in starting it, run M122 and check the software reset data.
-
I have replaced the Duex5 and the unit fired up the first time.
See below for reset details from M122.
Software reset code 0x4033 HFSR 0x40000000 CFSR 0x00008200 ICSR 0x0041f803 BFAR 0x43910046 SP 0x2000464c Task 0x4e49414d
Stack: 00420831 00421220 21000000 20000168 200001c8 20004954 00000000 0000008d 20013da0 a5a5a5a5 00452ff7 200001c8 00000000 0000000a 00000035 2000ac10 004236cf 2000ac10 20004954 00000000 2000ac10 20009aa8 2000ac10 -
Update: I rebooted and the unit would not restart. The red Diag light just blinked. It took me 10 power cycles before the controller would boot properly and I could re-connect to the web interface.
Note that all the power leds come on but no interface lights on the rJ45 connector.
I have received a new Duet Wifi and I am going to pull this board off the machine and set it up on the bench until I can figure out what is wrong.
-
Update:
I have removed the Duet Ethernet and put in a brand new Duet Wifi. Everything seems to go fine, until I put in my config file. I could not get the web interface to start, similar to the previous board after I copied my old config files over. So, I wiped the config file down to basics and added line by line the config file items and traced the problem down to the chamber heater.
If I leave the code below out, the system boots up just fine every time. If it is included, it fails to boot. This doesn't seem like it should be an issue, but I have confirmed the problem about a dozen times. I can't see what about the chamber heater code could be the problem. Note: my chamber heater is a little underpowered, hence the long D value for the M307 settings. This was not previously a problem on prior firmware versions.
This new wifi board is 2.02 (RTOS) out of the box I had recently upgraded the Ethernet board to 2.02 (RC2) and I am wondering if this explains some of the booting problems on both boards (granted, I might still have an I2C problem on either the old ethernet board/old duex5 board).
By omitting the offending code below, everything seems to be running just fine. I've got the new unit powered up, homing and doing a small test print.
What are your thoughts? I do need to get the chamber heater running again.
; Chamber Heater M141 H5 ; heater 5 is the chamber heater M305 P5 R4700 T100000 B3950 ;heater 5 is monitored by a 100K thermistor with B=3950 and a 4.7K series resistor M307 H5 A21.5 C171.8 D60 ; Setup Heater PID Settings M307 H5 B1 ; setup bang-bang control] -
It sounds like either a firmware bug or running out of memory. Please can you post the complete config.g file that makes it fail to boot.
When the board failed to boot prior to you getting that software reset data report, which firmware version was it running?
-
Scratch that, I've just found the bug in the chamber heater setup code. It will be fixed in the forthcoming 2.03beta3 release, which I am aiming to do later today.
Thanks for your help in pinning this down. The software reset data you posted located the problem.
