ToolBoard: 2 wires fan, heater fault and how to extrude ?
-
@Veti said in ToolBoard: 2 wires fan, heater fault and how to extrude ?:
you can find the error messages in the console or in the popup at the bottom right when they occur.
I just tested but I don't have any error message (I checked the console and there is no pupop when it stop working)
-
are you on duet web control 3.1.1 as well?
-
@Veti said in ToolBoard: 2 wires fan, heater fault and how to extrude ?:
are you on duet web control 3.1.1 as well?
I think yes, what is the command to check ?
-
on the general tab
-
@Veti ok, yes it both version 3.1.1
-
@Veti I tried to update the toolBoard but I go this error:
02/12/2020 à 18:23:25 Upload of Duet3Firmware_TOOL1LC.bin successful after 1s 02/12/2020 à 18:23:27 M997 B122 Board 122 starting firmware update 02/12/2020 à 18:23:37 M997 S Error: Failed to switch off remote heater 2: Board 122 does not have heater 2 02/12/2020 à 18:23:39 Error: Failed to switch off remote heater 2: Board 122 does not have heater 2 02/12/2020 à 18:24:06 Connection established -
I seem to have update it.. no error. But the version it's still 3.1.0 (on the toolboard 1LC). but I download the 3.1.1 (git hub)
-
3.1.0 is correct there is no 3.1.1 for the toolboard.
-
@Veti said in ToolBoard: 2 wires fan, heater fault and how to extrude ?:
3.1.0 is correct there is no 3.1.1 for the toolboard.
ah ok. Have you an idea then for the fault state ?
-
@Pseud3mys said in ToolBoard: 2 wires fan, heater fault and how to extrude ?:
Error: Failed to switch off remote heater 2: Board 122 does not have heater 2
do you still get this error message?
-
@Veti no, when I update it now it just put "2000°C" and offline on the web site but he is still connected with the CAN bus
-
post the output of
M122 B121
and
M122 B122 -
-
you power down the system after the firmware update?
also power the normal M122 output
-
@Veti yes, what is the M122 output ?
-
i meant provide the m122 output
-
@Veti said in ToolBoard: 2 wires fan, heater fault and how to extrude ?:
i meant provide the m122 output
it was not this ?
@Pseud3mys said in ToolBoard: 2 wires fan, heater fault and how to extrude ?:
-
no just send M122. that will provide the output for the duet 3
-
@Veti ah okay, the popup say "response too long, see console"
02/12/2020 à 19:08:20 M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.1.1 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 (23 max)
=== RTOS ===
Static ram: 154604
Dynamic ram: 162588 of which 36 recycled
Exception stack ram used: 224
Never used ram: 75764
Tasks: NETWORK(ready,292) ETHERNET(blocked,436) HEAT(blocked,1248) CanReceiv(suspended,3404) CanSender(suspended,1488) CanClock(blocked,1436) TMC(blocked,204) MAIN(running,4520) IDLE(ready,76)
Owned mutexes: LwipCore(NETWORK)
=== Platform ===
Last reset 00:00:54 ago, cause: software
Last software reset at 2020-12-02 19:07, reason: User, spinning module GCodes, available RAM 75728 bytes (slot 2)
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0444a000 BFAR 0x00000000 SP 0xffffffff Task MAIN
Error status: 0
MCU temperature: min 36.6, current 37.0, max 37.6
Supply voltage: min 12.2, current 12.3, 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: standstill, reads 6703, writes 0 timeouts 0, SG min/max not available
Driver 1: standstill, reads 6704, writes 0 timeouts 0, SG min/max not available
Driver 2: standstill, reads 6702, writes 0 timeouts 0, SG min/max not available
Driver 3: standstill, reads 6702, writes 0 timeouts 0, SG min/max not available
Driver 4: standstill, reads 6702, writes 0 timeouts 0, SG min/max not available
Driver 5: standstill, reads 6701, writes 0 timeouts 0, SG min/max not available
Date/time: 2020-12-02 19:08:18
Slowest loop: 6.33ms; fastest: 0.22ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 2.2ms, 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 CDDA state: -1
=== AuxDDARing ===
Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 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: 5.59ms; 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 sent 59, longest wait 0ms for type 0
=== Linux interface ===
State: 0, failed transfers: 0
Last transfer: 54276ms ago
RX/TX seq numbers: 0/1
SPI underruns 0, overruns 0
Number of disconnects: 0
Buffer RX/TX: 0/0-0
- Ethernet -
-
hmm can communication seems to be working.
can you update to the latest beta as the diagnostic has been improved.
