Duet 3 6HC Rev. 1.01 Faulty
-
So just to confirm, changing to jumper wires has made it worse?
-
@Phaedrux it seems so far...
-
In the main time i setted up the DuetPi with a Fresh image.
10min ago i changed everything to SBC Operation and started the printer,
after everything started up i had the Same issue on the DWC...
connection to duet lost, (no header).. and several seconds later, Connection established... and so on and so on...
maybe it's the Pi itself?! i ordered a new Pi4 anyway...i don't tried it yet but before if i tried to update the Firmware via pi+ribboncable
the Duet FW gets corrupted and i have to erase all and do the FW over USB..... (see 1. Post) -
Having another Pi available to test with would help troubleshoot the issue.
-
The symptoms you mentioned sound like there is a wiring issue between the Duet and the Pi. I assume if you look into the DCS log via
journalctl -u duetcontrolserver -eyou'll see lots of checksum errors, too. If there are no checksum errors, it's probably a good idea to try out a different Raspi.Just to be sure: You don't use another SPI device with the Pi, do you?
Duet software engineer
-
Thanks,
the Pi tells following...
Dec 02 15:47:46 duet3 DuetControlServer[373]: [warn] Restarting transfer because a bad header response was received (0x00000032)
Dec 02 15:47:47 duet3 DuetControlServer[373]: [warn] Restarting transfer because a bad header response was received (0x80ffff13)
Dec 02 15:47:47 duet3 DuetControlServer[373]: [warn] Restarting transfer because a bad data response was received (0xffffff7d)
Dec 02 15:47:47 duet3 DuetControlServer[373]: [warn] Restarting transfer because a bad header response was received (0x00001f00)
Dec 02 15:47:47 duet3 DuetControlServer[373]: [warn] Restarting transfer because the Duet received a bad response (header)
Dec 02 15:47:49 duet3 DuetControlServer[373]: [warn] Bad data checksum (expected 0x8707, got 0x6fc0)
Dec 02 15:47:50 duet3 DuetControlServer[373]: [warn] Bad data checksum (expected 0x07c5, got 0xc7e3)
Dec 02 15:47:51 duet3 DuetControlServer[373]: [warn] Bad data checksum (expected 0x7881, got 0x7060)
Dec 02 15:47:54 duet3 DuetControlServer[373]: [warn] Bad data checksum (expected 0x9358, got 0xbc71)
Dec 02 15:47:54 duet3 DuetControlServer[373]: [warn] Bad data checksum (expected 0xfb8f, got 0x11a2)
Dec 02 15:47:54 duet3 DuetControlServer[373]: [warn] Restarting transfer because a bad header response was received (0x000000a8)
Dec 02 15:47:55 duet3 DuetControlServer[373]: [warn] Restarting transfer because a bad data response was received (0xffffff67)
Dec 02 15:47:55 duet3 DuetControlServer[373]: [warn] Restarting transfer because a bad data response was received (0xffffff67)
Dec 02 15:47:55 duet3 DuetControlServer[373]: [warn] Bad data checksum (expected 0xe458, got 0x1b24)
Dec 02 15:47:55 duet3 DuetControlServer[373]: [warn] Note: RepRapFirmware didn't receive valid data either (code 0x00000004)
Dec 02 15:47:55 duet3 DuetControlServer[373]: [warn] Bad data checksum (expected 0xe458, got 0xca19)
Dec 02 15:47:55 duet3 DuetControlServer[373]: [warn] Restarting transfer because the Duet received a bad response (data response)
Dec 02 15:47:57 duet3 DuetControlServer[373]: [warn] Restarting transfer because a bad header response was received (0xffffff15)
Dec 02 15:47:58 duet3 DuetControlServer[373]: [warn] Restarting transfer because a bad header response was received (0xffffff67)i orderer a 40 to 26 Ribboncable from Pimoroni
-
you could try reducing the SPI frequency while waiting for new ribbon cable; /opt/dsf/conf/config.json (or something like that)
-
@bearer i used 50% of the value (100000)
interesting thing: if i do the Heater Tuning M303 the Connection loss
failures getting worse than before, but the Tuning are correctly till the end (seen from the Paneldue)MCU Temperature after 2 hours Continious running about 42°C
-
@chrishamm sorry, no i have no additional spi device running on the pi
-
Update: with the New Pi 4 it's still the same Problem... keep all my hopes to the
Ribboncable...another Question, i'm using 2 Filamentsensors, although when i want to start a Gcode
the Problem is i need all 2 Filamentsensors to be OK, but i just want to use 1 Hotend...
how can i manage that without disabling? -
@NeueKlasse said in Duet 3 6HC Rev. 1.01 Faulty:
how can i manage that without disabling?
How to disable without disabling? hmm..
Since you can configure on the fly, disabling is probably the best way to go.
Perhaps have it disabled by default and add the enable code to the second extruder start code?
-
I thought when i just use one extruder i don't need the other one for that specific Print.
You Think about M591 D0/D1 P0 C"in5/in6" ?, maybe it would be handy in a future DWC to
have Buttons to enable/disable configured Filament Sensors. -
Well if you create a macro with that commands it basically shows up as a button.
-
@Phaedrux hm, ok i thought about that... so last time i tested everything it don't lets me start any gcode file because it needs both fil. sensors to be OK...
maybe i delete everything from the config file and set it separately over the Slicer/S3D Post processing.... -
Today i've got the New Ribboncable,
attached Everything. first it was working fine, Homing, Mesh Bed Leveling,
Speed and Acceleration Tests with 300mm/s...
a few minutes without anything...after i turned on the Heaters (Bed Heater to 60degree) (Powered direct from Supply
over original Mosfets) Control via Heater 0 connector....
and 2 Nozzleheaters from the Board (50W each)after Turning on the Heaters => Board lost connection, no header... timeouts, DCS not started... etc... when the heaters are off i have no problems at all (not like before the cable swap)
After Some tests i can confirm that the Board Lost Connection faults only occure when i set the Bed Temperature higher than +10degree (when i heat up from 30 to 40 it's not a problem... but when i heat up to 60 degree i get errors instantaniously..
I can Heat up both nozzles (together or alone to 180 degree without error)....
What's the problem?
-
Update... it doesn't matter what i try i also cant update the Firmware to another
than 3.1.1... with all others DWC says: DCS not started...While Updating over DWC the PanelDue says: ERROR: Operation 3 failed after 5 retries....
i don't know either...
i bought the Duet Board to have a reliable Printer... now i'm disappointed from it....
-
Can you post some photos of your setup so we can see what your wiring looks like?
@NeueKlasse said in Duet 3 6HC Rev. 1.01 Faulty:
Update... it doesn't matter what i try i also cant update the Firmware to another
than 3.1.1... with all others DWC says: DCS not started...
While Updating over DWC the PanelDue says: ERROR: Operation 3 failed after 5 retries....Can you be more specific about what exactly you've tried to do?
Did you ever get the board working in standalone mode?
-
This post is deleted! -
What i tried to do:
- Update Firmware via SBC sudo apt update / upgrade ... with "no Header" Errors while updating.
- Directly over DWC (file Upload, Version 3.2beta 1 to beta 4), Problem is that after i
acknowledge that i want to update the Firmware the Paneldue says ERROR: Operation 3 failed after 5 retries
and DWC shows me that it is updating... still after 1 hour.... when i reset the printer the
Firmware is corrupt and i need to erase it and update it via USB Cable and Bossa!
and when i don't Use Firmware 3.1.1 it doesn't connect to the PI SBC and DWC says... DCS not started.
After i installed V3.1.1 it seems to be OK... but while heating up the bed i get
connection losses (no header etc.)Oh not to mention... if the sudo apt get upgrade runs till the error it wont reconnect to the Board till i set up the DuetPi with a new Image....!!!!!
Wiring:
Driver 0 = X
Driver 1 = Y
Driver 2 = Z1
Driver 3 = Z2
Driver 4 = E1
Driver 5 = E2Out1 = (Heater 0) to Bed Mosfet
Out2 = Heater 1
Out3 = Heater 2Out7 = Extruder Fans
Out8 = Part Cooling FansPower IN = 25V
Only 1 Jumper on Int 5V En
IO0 = PanelDue 5i
IO3 = X Endstop
IO4 = Y Endstop
IO7 = BlTouch V3.1IO6 = 5V Cabinet Fan
Temp0 = Bed Thermistor
Temp1 = E1 Temp
Temp2 = E2 Tempphysically Wiring itself should not be the Problem
-
@Phaedrux
Yes the Board works in Standalone mode.. see above
