Yet another extruder not working
-
I confirmed that the CAN jumpers are off the tool distribution board for the affected tool and that the termination jumper on the tool distribution board is present.
-
BTW, I am assuming that as long as phase A wires are connected to one coil and phase B wires are connected to the other coil, polarity doesn't matter and just ends up turning in the wrong direction.
Is this assumption correct or do I need to worry about polarity of the individual phases and how they are connected to the coils ?
-
@arnold_r_clark, I poked around some more and actually pulled the pins from the connector on the 1LC and two pins popped off the wire. I was very happy, figuring that this is it ... alas, once new crimp connectors were installed, the situation is exactly as before
-
I programed a new 1LC tool board with the correct CAN address and used it to replace the original board. This was to see if maybe the tool board was defective.
Nope, exactly the same result -
@jens55 said in Yet another extruder not working:
Duet 3 MB6HC version 3.2.2
I would suggest updating the mainboard and all toolboards to 3.3.
Also try adding a G4 S4 pause command to the start of your config.g to allow the toolboards time to startup before configuration commands are sent to them.
Also please send M98 P"config.g" in the gcode console and report the results.
-
@phaedrux, hmmm, I could have sworn I was on 3.3. I upgraded the tool boards and they both came back with version 3.3
I will look into it, THANKS! -
@phaedrux, I use G4 S1 in config.g, I will update that to S4. I will also upgrade to 3.4b2
Thanks! -
@phaedrux, for some reason my upgrade did not work - I downloaded Duet2CombinedFirmware.bin for 3.4b2 and then did an "upload system files". The system file Duet2CombinedFirmware.bin shows the new file date but none of the other (extracted) files show the new date.
M122 still shows version 3.2.2
What am I doing wrong ? -
This is the result of M98 P"config.g" but note that there currently is only one tool board connected (21) which is why there are all the errors.
2021-08-05, 8:50:01 p.m. Error: Response timeout: CAN addr 24, req type 6027, RID=109
Error: Fan number 6 not found
Error: Response timeout: CAN addr 24, req type 6027, RID=111
Error: Fan number 7 not found
Error: Response timeout: CAN addr 22, req type 6044, RID=115
Error: Response timeout: CAN addr 23, req type 6044, RID=116
Error: Response timeout: CAN addr 24, req type 6044, RID=117
Warning: Macro file config-override.g not found
2021-08-05, 8:50:00 p.m. Error: Response timeout: CAN addr 24, req type 6027, RID=109
Error: Fan number 6 not found
Error: Response timeout: CAN addr 24, req type 6027, RID=111
Error: Fan number 7 not found
Error: Response timeout: CAN addr 22, req type 6044, RID=115
Error: Response timeout: CAN addr 23, req type 6044, RID=116
2021-08-05, 8:49:59 p.m. Error: Fan number 4 not found
Error: Response timeout: CAN addr 23, req type 6027, RID=107
Error: Fan number 5 not found
Error: Response timeout: CAN addr 24, req type 6027, RID=109
Error: Fan number 6 not found
Error: Response timeout: CAN addr 24, req type 6027, RID=111
Error: Fan number 7 not found
Error: Response timeout: CAN addr 22, req type 6044, RID=115
2021-08-05, 8:49:58 p.m. Error: Fan number 4 not found
Error: Response timeout: CAN addr 23, req type 6027, RID=107
Error: Fan number 5 not found
Error: Response timeout: CAN addr 24, req type 6027, RID=109
Error: Fan number 6 not found
Error: Response timeout: CAN addr 24, req type 6027, RID=111
Error: Fan number 7 not found
2021-08-05, 8:49:56 p.m. Error: Fan number 4 not found
Error: Response timeout: CAN addr 23, req type 6027, RID=107
Error: Fan number 5 not found
Error: Response timeout: CAN addr 24, req type 6027, RID=109
Error: Fan number 6 not found
2021-08-05, 8:49:54 p.m. Error: Response timeout: CAN addr 22, req type 6027, RID=101
Error: Fan number 2 not found
Error: Response timeout: CAN addr 22, req type 6027, RID=103
Error: Fan number 3 not found
Error: Response timeout: CAN addr 23, req type 6027, RID=105
Error: Fan number 4 not found
Error: Response timeout: CAN addr 23, req type 6027, RID=107
Error: Fan number 5 not found
2021-08-05, 8:49:51 p.m. Error: Response timeout: CAN addr 24, req type 6026, RID=93
Error: Heater 4 does not exist
Error: Heater 4 not found
Error: Response timeout: CAN addr 22, req type 6027, RID=101
Error: Fan number 2 not found
Error: Response timeout: CAN addr 22, req type 6027, RID=103
Error: Fan number 3 not found
Error: Response timeout: CAN addr 23, req type 6027, RID=105
2021-08-05, 8:49:45 p.m. =87
Error: Heater 2 does not exist
Error: Heater 2 not found
Error: Response timeout: CAN addr 23, req type 6031, RID=89
Error: Response timeout: CAN addr 23, req type 6026, RID=90
Error: Heater 3 does not exist
Error: Heater 3 not found
Error: Response timeout: CAN addr 24, req type 6031, RID=92
Error: Response timeout: CAN addr 24, req type 6026, RID=93
Error: Heater 4 does not exist
Error: Heater 4 not found
2021-08-05, 8:49:44 p.m. Error: Response timeout: CAN addr 22, req type 6042, RID=78
Response timeout: CAN addr 23, req type 6042, RID=79
Response timeout: CAN addr 24, req type 6042, RID=80
Warning: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 614C
Warning: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 614C
Error: Response timeout: CAN addr 22, req type 6031, RID=86
Error: Response timeout: CAN addr 22, req type 6026, RID=87
Error: Heater 2 does not exist
Error: Heater 2 not found
Error: Response timeout: CAN addr 23, req type 6031, RID=89
Error: Response timeout: CAN addr 23, req type 6026, RID=90
Error: Heater 3 does not exist
Error: Heater 3 not found
Error: Response timeout: CAN addr 24, req type 6031, RID=92
2021-08-05, 8:49:40 p.m. Error: Response timeout: CAN addr 22, req type 6042, RID=78
Response timeout: CAN addr 23, req type 6042, RID=79
Response timeout: CAN addr 24, req type 6042, RID=80
Warning: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 614C
Warning: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 614C
Error: Response timeout: CAN addr 22, req type 6031, RID=86
Error: Response timeout: CAN addr 22, req type 6026, RID=87
Error: Heater 2 does not exist
Error: Heater 2 not found
Error: Response timeout: CAN addr 23, req type 6031, RID=89
2021-08-05, 8:49:34 p.m. Error: Response timeout: CAN addr 22, req type 6042, RID=70
Response timeout: CAN addr 23, req type 6042, RID=71
Response timeout: CAN addr 24, req type 6042, RID=72
Error: Response timeout: CAN addr 22, req type 6042, RID=74
Response timeout: CAN addr 23, req type 6042, RID=75
Response timeout: CAN addr 24, req type 6042, RID=76
2021-08-05, 8:49:30 p.m. Error: Response timeout: CAN addr 22, req type 6042, RID=70
Response timeout: CAN addr 23, req type 6042, RID=71
Response timeout: CAN addr 24, req type 6042, RID=72
2021-08-05, 8:49:27 p.m. Error: Response timeout: CAN addr 22, req type 6043, RID=66
Response timeout: CAN addr 23, req type 6043, RID=67
Response timeout: CAN addr 24, req type 6043, RID=68
2021-08-05, 8:49:24 p.m. Error: Response timeout: CAN addr 22, req type 6042, RID=58
Response timeout: CAN addr 23, req type 6042, RID=59
Response timeout: CAN addr 24, req type 6042, RID=60
Error: Response timeout: CAN addr 22, req type 6018, RID=62
Error: Response timeout: CAN addr 23, req type 6018, RID=63
Error: Response timeout: CAN addr 24, req type 6018, RID=64
2021-08-05, 8:49:24 p.m. Error: Response timeout: CAN addr 22, req type 6042, RID=58
Response timeout: CAN addr 23, req type 6042, RID=59
Response timeout: CAN addr 24, req type 6042, RID=60
Error: Response timeout: CAN addr 22, req type 6018, RID=62
Error: Response timeout: CAN addr 23, req type 6018, RID=63
2021-08-05, 8:49:23 p.m. Error: Response timeout: CAN addr 22, req type 6042, RID=58
Response timeout: CAN addr 23, req type 6042, RID=59
Response timeout: CAN addr 24, req type 6042, RID=60
Error: Response timeout: CAN addr 22, req type 6018, RID=62
2021-08-05, 8:49:21 p.m. Error: Response timeout: CAN addr 22, req type 6042, RID=58
Response timeout: CAN addr 23, req type 6042, RID=59
Response timeout: CAN addr 24, req type 6042, RID=60
2021-08-05, 8:49:15 p.m. M98 P"config.g"
FTP is disabled
TELNET is disabled -
ok, I downloaded and installed the .bin files for the 6HC and 1LC boards separately as well as the DWC zip file and we seem to be on the right track. Still need to upgrade the tool board and test things ...
-
We have progress !!!
I actually got extruder rotation although extremely weak.
m122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.0beta2 (2021-08-03 12:42:33) running on Duet 3 MB6HC v1.01 or later (standalone mode)
Board ID: 08DJM-9P63L-DJ3T0-6J9F0-3SN6L-TU37A
Used output buffers: 3 of 40 (26 max)
=== RTOS ===
Static ram: 151128
Dynamic ram: 94032 of which 0 recycled
Never used RAM 105368, free system stack 152 words
Tasks: NETWORK(ready,30.8%,212) ETHERNET(notifyWait,0.2%,167) HEAT(delaying,0.0%,338) Move(notifyWait,0.0%,261) CanReceiv(notifyWait,0.0%,557) CanSender(notifyWait,0.0%,373) CanClock(delaying,0.0%,340) TMC(notifyWait,9.0%,59) MAIN(running,60.0%,924) IDLE(ready,0.0%,29), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:13:46 ago, cause: software
Last software reset at 2021-08-05 20:58, reason: User, GCodes spinning, available RAM 105684, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044a000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Step timer max interval 136
MCU temperature: min 32.6, current 33.7, max 33.7
Supply voltage: min 23.7, current 23.8, max 23.9, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.1, current 12.1, max 12.2, under voltage events: 0
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Driver 0: position 53340, standstill, reads 22813, writes 3 timeouts 0, SG min/max 0/312
Driver 1: position -51980, standstill, reads 22813, writes 3 timeouts 0, SG min/max 0/74
Driver 2: position 4323, standstill, reads 22813, writes 3 timeouts 0, SG min/max 0/315
Driver 3: position 0, standstill, reads 22813, writes 3 timeouts 0, SG min/max 0/536
Driver 4: position 0, standstill, reads 22813, writes 3 timeouts 0, SG min/max 0/242
Driver 5: position 0, standstill, reads 22813, writes 3 timeouts 0, SG min/max 0/237
Date/time: 2021-08-05 21:12:00
Slowest loop: 16.90ms; fastest: 0.05ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 0.8ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, segments created 6, maxWait 649244ms, bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves 44, completed moves 44, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 5], 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 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== 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
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty
=== CAN ===
Messages queued 6521, received 2138, lost 0, longest wait 1ms for reply type 6025, peak Tx sync delay 48856, free buffers 49 (min 47), ts 2338/2326/0
Tx timeouts 0,0,12,0,0,7 last cancelled message type 30 dest 127
=== Network ===
Slowest loop: 11.04ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions
HTTP sessions: 2 of 8- Ethernet -
State: active
Error counts: 0 0 1 0 0
Socket states: 5 2 2 2 2 0 0 0
Error: Response timeout: CAN addr 22, req type 6044, RID=134
Error: Response timeout: CAN addr 23, req type 6044, RID=135
Error: Response timeout: CAN addr 24, req type 6044, RID=136
Warning: Macro file config-override.g not found
2021-08-05, 9:14:39 p.m. Error: Response timeout: CAN addr 22, req type 6044, RID=134
Error: Response timeout: CAN addr 23, req type 6044, RID=135
2021-08-05, 9:14:38 p.m. Error: Response timeout: CAN addr 22, req type 6044, RID=134
2021-08-05, 9:14:37 p.m. Error: Response timeout: CAN addr 24, req type 6027, RID=126
Error: Fan number 6 not found
Error: Response timeout: CAN addr 24, req type 6027, RID=128
Error: Fan number 7 not found
2021-08-05, 9:14:37 p.m. Error: Response timeout: CAN addr 24, req type 6027, RID=126
Error: Fan number 6 not found
Error: Response timeout: CAN addr 24, req type 6027, RID=128
Error: Fan number 7 not found
2021-08-05, 9:14:33 p.m. Error: Response timeout: CAN addr 22, req type 6027, RID=118
Error: Fan number 2 not found
Error: Response timeout: CAN addr 22, req type 6027, RID=120
Error: Fan number 3 not found
Error: Response timeout: CAN addr 23, req type 6027, RID=122
Error: Fan number 4 not found
Error: Response timeout: CAN addr 23, req type 6027, RID=124
Error: Fan number 5 not found
2021-08-05, 9:14:31 p.m. Error: Response timeout: CAN addr 22, req type 6027, RID=118
Error: Fan number 2 not found
Error: Response timeout: CAN addr 22, req type 6027, RID=120
Error: Fan number 3 not found
Error: Response timeout: CAN addr 23, req type 6027, RID=122
Error: Fan number 4 not found
2021-08-05, 9:14:29 p.m. Error: Response timeout: CAN addr 22, req type 6027, RID=118
Error: Fan number 2 not found
Error: Response timeout: CAN addr 22, req type 6027, RID=120
Error: Fan number 3 not found
2021-08-05, 9:14:25 p.m. Error: Response timeout: CAN addr 23, req type 6031, RID=104
Error: Response timeout: CAN addr 23, req type 6026, RID=106
Error: Heater 3 does not exist
Error: Heater 3 not found
Error: Response timeout: CAN addr 24, req type 6031, RID=108
Error: Response timeout: CAN addr 24, req type 6026, RID=110
Error: Heater 4 does not exist
Error: Heater 4 not found
2021-08-05, 9:14:21 p.m. D=102
Error: Heater 2 does not exist
Error: Heater 2 not found
Error: Response timeout: CAN addr 23, req type 6031, RID=104
Error: Response timeout: CAN addr 23, req type 6026, RID=106
2021-08-05, 9:14:10 p.m. Error: Response timeout: CAN addr 22, req type 6042, RID=83
Response timeout: CAN addr 23, req type 6042, RID=84
Response timeout: CAN addr 24, req type 6042, RID=85
Error: Response timeout: CAN addr 22, req type 6042, RID=87
Response timeout: CAN addr 23, req type 6042, RID=88
Response timeout: CAN addr 24, req type 6042, RID=89
2021-08-05, 9:14:07 p.m. Error: Response timeout: CAN addr 22, req type 6042, RID=83
Response timeout: CAN addr 23, req type 6042, RID=84
Response timeout: CAN addr 24, req type 6042, RID=85
2021-08-05, 9:14:04 p.m. Error: Response timeout: CAN addr 23, req type 6018, RID=76
Error: Response timeout: CAN addr 24, req type 6018, RID=77
Error: Response timeout: CAN addr 22, req type 6043, RID=79
Response timeout: CAN addr 23, req type 6043, RID=80
Response timeout: CAN addr 24, req type 6043, RID=81
2021-08-05, 9:14:01 p.m. Error: Response timeout: CAN addr 23, req type 6018, RID=76
Error: Response timeout: CAN addr 24, req type 6018, RID=77
2021-08-05, 9:14:00 p.m. Error: Response timeout: CAN addr 23, req type 6018, RID=76
2021-08-05, 9:13:59 p.m. Error: Response timeout: CAN addr 22, req type 6042, RID=71
Response timeout: CAN addr 23, req type 6042, RID=72
Response timeout: CAN addr 24, req type 6042, RID=73
Error: Response timeout: CAN addr 22, req type 6018, RID=75
2021-08-05, 9:13:58 p.m. FTP is disabled
TELNET is disabled
Error: Response timeout: CAN addr 22, req type 6042, RID=71
Response timeout: CAN addr 23, req type 6042, RID=72
Response timeout: CAN addr 24, req type 6042, RID=73
2021-08-05, 9:13:51 p.m. M98 P"config.g"
FTP is disabled
TELNET is disabled - Ethernet -
-
I have no clue what is going on but after another reset, I now have full extruder power ?!?!?!?
-
@phaedrux, when I upgrade, should I not be able to just get the 'combined' bin file to upload to my Duet instance and be done ?
I have no idea why the extruder went from maybe 10% power to 100% power with a restart.
I will consider both weirdness's related to beta software .... -
I think you probably should have gone to 3.3 via the full zip file first. In 3.3 a /firmware folder is created that will get all the bin files going forward to keep the /sys folder tidier and for config files only.
Going straight from 3.2.2 to a 3.4 beta probably wasn't destined to be the smoothest.
I think the main problem was the mismatch between mainboard and toolboard firmware.
[Duet 3 + expansion/tool boards] You must update the expansion and/or tool board firmware to 3.3 also, otherwise movement and some other functions will not work. If you accidentally end up with firmware 3.3 on a tool or expansion board and 3.2.x on the main board then the tool/expansion board will not achieve CAN sync with the main board; however it will still respond to some commands including M115, M122 and M997.
-
I am answering my own question here in case anybody else runs into this issue.
The file I was expecting to upload is Duet2and3Firmware-3.4.xxx.zip or something like that. It has all the other files in it and is different from the file that I actually uploaded which was Duet2CombinedFirmware.bin which wasn't the right file and therefore did not unzip or install correctly.
The zip file that has everything in it is not available for the 3.4.beta2 version.
As far as the other oddities I encountered - I suspect this was due to being early in the life of the software when bugs and weird things tend to show up.
I did sync up the tool boards to the 6HC firmware that I was running at the time so who knows if it was 3.2.2 as reported by M122 or 3.3 as reported by the tool boards after they were synced.
I do not know if the RRF road map includes some sort of self check to verify that the expansion card and main controller software are matching but I hope that is in the works. There are just too many ways that the user can screw this up if it is something that is left for the user to do/verify. -
@phaedrux said in Yet another extruder not working:
I think you probably should have gone to 3.3 via the full zip file first. In 3.3 a /firmware folder is created that will get all the bin files going forward to keep the /sys folder tidier and for config files only.
Going straight from 3.2.2 to a 3.4 beta probably wasn't destined to be the smoothest.
I think the main problem was the mismatch between mainboard and toolboard firmware.
[Duet 3 + expansion/tool boards] You must update the expansion and/or tool board firmware to 3.3 also, otherwise movement and some other functions will not work. If you accidentally end up with firmware 3.3 on a tool or expansion board and 3.2.x on the main board then the tool/expansion board will not achieve CAN sync with the main board; however it will still respond to some commands including M115, M122 and M997.
Thanks! That is a good point! The 1LC board seemed to be synced based on the regular flashing of the red light. It never occurred to me that part of the functions could work and other functions wouldn't work. I was also under the mistaken belief that if I upgraded the tool board, that it would be synced with the software on the 6HC board which is why I was sure to upgrade the tool boards as soon as they were installed. I figured that the files on the 6HC were all from the same release and since the tool boards reported 3.3 then everything would be 3.3 including the 6HC.
Well I am glad that things seem to finally work as expected. I will put the tool back into one piece tomorrow and see if everything still works (knock on wood)
Thanks again for your help, I would not have been able to resolve this without your help! -
I should have included the link to the 3.3 zip file and told you to upload that and it would likely have "just worked".
https://github.com/Duet3D/RepRapFirmware/releases/download/3.3/Duet2and3Firmware-3.3.zip
Beta releases don't get the full zip file treatment. As a general rule with most software I'd say it's a good idea to avoid beta releases unless you either have a working system and want to test the new changes, or you know there is a fix to a specific problem only available there. Jumping into a beta release during commissioning or troubleshooting is a recipe for chaos.
@jens55 said in Yet another extruder not working:
I do not know if the RRF road map includes some sort of self check to verify that the expansion card and main controller software are matching
Maybe. In the meantime you can do this today by creating a macro with M115, M155 B0, etc for all your boards and run it after a firmware update to see if they are all updated.
-
@jens55 said in Yet another extruder not working:
I do not know if the RRF road map includes some sort of self check to verify that the expansion card and main controller software are matching but I hope that is in the works. There are just too many ways that the user can screw this up if it is something that is left for the user to do/verify.
...even if there was a selftest, DWC wouldn't show errors unless the user runs M98 P"config.g" after connecting to DWC.
I'm not familiar with Duet 3 family, but there should be another sign of warning (beeper or flashing LED) -
@o_lampe, with a single tool board hooked up things are quite manageable if you know what to look for (big 'if') but I can easily see a big pile of poo happening once you got expansion cards, tool boards and who knows what else all hooked up in a big machine.
-
@jens55
one thing to avoid is bad crimping. You (and others) have experienced it. I always solder after crimping to be on the safe side.
