ToolBoard: 2 wires fan, heater fault and how to extrude ?
-
I have:
Error: M997: In-application programming binary "Duet3_SDiap_MB6HC.bin" not found
but there is not this file in the repository ? (git hub ) -
find that file here
https://github.com/Duet3D/RepRapFirmware/releases/tag/3.0 -
This post is deleted! -
M122 B121 command (for the tool board):
02/12/2020 à 19:29:11 M122 B121
Diagnostics for board 121:
Duet TOOL1LC firmware version 3.2-beta4 (2020-11-26)
Bootloader ID: not available
Never used RAM 4700, free system stack 96 words
HEAT 42 CanAsync 88 CanRecv 82 TMC 48 MAIN 341 AIN 64
Last reset 00:03:22 ago, cause: software
Last software reset data not availableDriver 0: position 0, 80.0 steps/mm, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 19, reads 35710, writes 9, timeouts 0, DMA errors 0
Moves scheduled 0, completed 0, in progress 0, hiccups 0
No step interrupt scheduled
VIN: 12.2V
MCU temperature: min 22.6C, current 25.2C, max 25.2C
Ticks since heat task active 46, ADC conversions started 202540, completed 202539, timed out 0
Last sensors broadcast 0x00000000 found 0 50 ticks ago, loop time 0
CAN messages queued 16, send timeouts 0, received 1906, lost 0, free buffers 36 -
and for the mainboard:
02/12/2020 à 19:34:16 M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.2-beta4 running on Duet 3 MB6HC v1.01 or later (standalone mode)
Board ID: 08DJM-956BA-NA3TJ-6J1D2-3SD6M-9B9LT
Used output buffers: 1 of 40 (12 max)
=== RTOS ===
Static ram: 123212
Dynamic ram: 168576 of which 752 recycled
Never used RAM 99652, free system stack 200 words
Tasks: NETWORK(ready,171) ETHERNET(blocked,110) HEAT(blocked,317) CanReceiv(blocked,852) CanSender(blocked,371) CanClock(blocked,356) TMC(blocked,54) MAIN(running,1127) IDLE(ready,19)
Owned mutexes:
=== Platform ===
Last reset 00:00:46 ago, cause: software
Last software reset details not available
Error status: 0x00
MCU temperature: min 37.9, current 39.0, max 39.3
Supply voltage: min 12.2, current 12.2, max 12.3, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 11.4, current 11.4, max 11.5, under voltage events: 0
Driver 0: position 0, standstill, reads 35416, writes 14 timeouts 0, SG min/max 0/0
Driver 1: position 0, standstill, reads 35417, writes 14 timeouts 0, SG min/max 0/0
Driver 2: position 0, standstill, reads 35418, writes 14 timeouts 0, SG min/max 0/0
Driver 3: position 0, standstill, reads 35422, writes 11 timeouts 0, SG min/max 0/0
Driver 4: position 0, standstill, reads 35423, writes 11 timeouts 0, SG min/max 0/0
Driver 5: position 0, standstill, reads 35424, writes 11 timeouts 0, SG min/max 0/0
Date/time: 2020-12-02 19:34:15
Slowest loop: 5.81ms; fastest: 0.15ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 2.4ms, write time 0.0ms, max retries 0
=== Move ===
Hiccups: 0(0), FreeDm: 375, MinFreeDm: 375, MaxWait: 0ms
Bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed moves 0, StepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 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.
=== Network ===
Slowest loop: 15.69ms; fastest: 0.03ms
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: 1 of 8- Ethernet -
State: active
Error counts: 0 0 0 0 0
Socket states: 5 2 2 2 2 0 0 0
=== CAN ===
Messages queued 171, send timeouts 0, received 896, lost 0, longest wait 2ms for reply type 6031, free buffers 47
- Ethernet -
-
duet 3 is also updated?
any info on the heating now?
-
@Veti still no error, but now it show "fault" 1 second and after the web interface lost the board (2000°C and offline), but the M115 command still return that the can bus is connected
-
02/12/2020 à 19:42:27 M122 B122
Diagnostics for board 122:
Duet TOOL1LC firmware version 3.2-beta4 (2020-11-26)
Bootloader ID: not available
Never used RAM 4700, free system stack 96 words
HEAT 42 CanAsync 88 CanRecv 82 TMC 48 MAIN 341 AIN 70
Last reset 00:01:20 ago, cause: software
Last software reset at 2020-12-02 19:41, reason: HardFault, available RAM 4360, slot 0
Software reset code 0x0060 ICSR 0x00000003 SP 0x200011c0 Task
Stack: 20001014 00000011 0001d3e3 00000000 20000928 0001757d 000184fe 01000000 000202a8 000203a2 20001210 200032d8 00000020 00017d11 20004668 00000000 20001300 000086e5 000202a8 20004678 000203a2 4200af00 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5
Driver 0: position 0, 80.0 steps/mm, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 19, reads 40161, writes 9, timeouts 0, DMA errors 0
Moves scheduled 0, completed 0, in progress 0, hiccups 0
No step interrupt scheduled
VIN: 12.3V
MCU temperature: min 30.8C, current 30.8C, max 30.9C
Ticks since heat task active 127, ADC conversions started 80370, completed 80369, timed out 0
Last sensors broadcast 0x00000000 found 0 131 ticks ago, loop time 0
CAN messages queued 22, send timeouts 0, received 732, lost 0, free buffers 36it seem than the borad restart..
-
same thing happens on the first board?
-
@Veti yes, even with no heater connected
-
ok this is one for dc42 what the hardfault means.
-
but when there are no target temperature this not happen.
I checked, the board reset.
I would also like to add than I didn't load filament, I put the temperature by hand. -
@Veti said in ToolBoard: 2 wires fan, heater fault and how to extrude ?:
ok this is one for dc42 what the hardfault means.
sorry, I didn't understand ? what is dc42 ?
-
just for testing execute
M307 H2 A597.2 C231.1 D12.5 S1.00 B0
and try heating again
-
@Veti
raise this:
02/12/2020 à 19:50:36 M307 H1 A597.2 C231.1 D12.5 S1.00 B0
Warning: M307: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 622C -
the question would be. who is @dc42
https://forum.duet3d.com/user/dc42but can you heat afterwards? i thought you are trying heater 2
-
@Veti ah okay.
I tried, heater keep running a little bit longer but the same issues appear. -
@dc42 Hello, I have a fault with my heater (on Tool 1LC), with no error message. After a fews seconds when I start to heat, the heater pass in fault statement and in beta4 the tool board reset one second after the fault statement.
Can you help me ? -
What does your heater graph look like when you get the fault?
What shows up in the gcode console? -
The graph start just ascend (like 10/20°c) and then the heater change to fault state and the graph start slowly getting down.
And I have nothing on the console, no error just the heater with "fault" under it.
