Toolboard Heater Tuning and Fan Error

Frederik

@Veti the second extruder is for my "fast switching" bowden - direct drive setup.

I used the so-called EVA mod for my printhead, I only have to change 2 screws and 1 piece of plastic to convert my setup from direct to Bowden and vice versa. the Extruder is driven from the Toolboard stepper driver.

This Toolhead can be used for a Hemera, volcano, mosquito or dragon Hotend, standard or Idex, and with BMG or Titan extruders.

when in Bowden mode: the duet 3 mainboard drives it

but I don't want to switch config... only hardware changes

at the moment I´m looking for a solution on how to properly mount the tool board when I use the Bowden setup.

when in direct drive I've mounted it on the backside of the Nema with a printed holder.

its a really nice design,

https://pkucmus.github.io/EVA/

Frederik

@Veti Z-Probe 0

and the red and blue lights are constantly on.

when doing a standard homeZ. it works fine.

but when i try to do a mesh with 20mm spacing, it stops with the same error message after a random number of points.. sometimes 40 spots , sometimes only 15 spots

Veti

a lot of the bltouch problems come from bad wiring.

Frederik

@Veti perhaps this one is software related.

when i restart the printer without touching the head, it works perfekt....sometimes up to 10 times in a row ..

Frederik

@Veti and when the error occurs, the bltouch is blinkin red and in the dwc i can read z-probe 1000

Veti

have you updated the bootloader?

https://forum.duet3d.com/topic/19211/bltouch-and-duet-3-tool-board/22

Frederik

@Veti

19.12.2020, 14:47:20	

m122 b121

Diagnostics for board 121:
Duet TOOL1LC firmware version 3.2-beta4.1 (2020-12-03)
Bootloader ID: not available
Never used RAM 4180, free system stack 84 words
HEAT 50 CanAsync 89 CanRecv 83 TMC 54 MAIN 218 AIN 64
Last reset 00:24:45 ago, cause: VDD brownout
Last software reset data not available
Driver 0: position 0, 830.0 steps/mm, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 12, reads 21603, writes 12, timeouts 0, DMA errors 0
Moves scheduled 0, completed 0, in progress 0, hiccups 0
No step interrupt scheduled
VIN: 24.1V
MCU temperature: min 43.5C, current 43.6C, max 46.0C
Ticks since heat task active 54, ADC conversions started 1479264, completed 1479263, timed out 0
Last sensors broadcast 0x00000002 found 1 58 ticks ago, loop time 0
CAN messages queued 18185, send timeouts 0, received 13832, lost 0, free buffers 36

Veti

the bootloader not the firmware. please read the thread.

jay_s_uk

Is it to do with the BLtouch being on the toolboard but the z drivers being on the main board?
I believe the restriction is still in place about the probe being in a different board

Frederik

@Veti yes , but it says bootloader not available, and i cant find the file. i Have to update via can, do i need the ToolLc1 firmware also or only the bootloader file ?

Veti

whats the error message when you issue the bootloader update?

the bootloader files are here as its written in the documentation.
https://github.com/Duet3D/Duet3Bootloader/releases

Frederik

@Veti bootloader not found

I looked again in the toolboard documentation, but i cant find the link to the bootloader, there is only a link to GitHub with the step files....

do i need only the samc21.bin or the .elf file also?

any additional files needed?

i added the 3 lines for the workaround also to the end of my config.g

i will test if now the mesh completes without errors

Frederik

@Veti the samc21 from your link worked.

m997 b121 s3

Board 121 starting bootloader update

19.12.2020, 15:45:56 Datei Duet3Bootloader-SAMC21.bin erfolgreich nach 0s hochgeladen

now, i´m really curious what the bltouch does

Frederik

@Veti
after the update :

m122 b121
Diagnostics for board 121:
Duet TOOL1LC firmware version 3.2-beta4.1 (2020-12-03)
Bootloader ID: SAMC21 bootloader version 2.1 (2020-11-03b2)
Never used RAM 4668, free system stack 96 words
HEAT 50 CanAsync 89 CanRecv 83 TMC 54 MAIN 338 AIN 64
Last reset 00:02:38 ago, cause: software
Last software reset data not available
Driver 0: position 0, 80.0 steps/mm, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 22, reads 13732, writes 9, timeouts 0, DMA errors 0
Moves scheduled 0, completed 0, in progress 0, hiccups 0
No step interrupt scheduled
VIN: 24.1V
MCU temperature: min 42.0C, current 42.0C, max 42.3C
Ticks since heat task active 85, ADC conversions started 158578, completed 158577, timed out 0
Last sensors broadcast 0x00000000 found 0 88 ticks ago, loop time 0
CAN messages queued 16, send timeouts 0, received 1436, lost 0, free buffers 36

Is that the right combination of firmwares ?
i am using DWC 3.2.0beta4

m122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.2-beta4.1 running on Duet 3 MB6HC v1.01 or later (SBC mode)
Board ID: 08DJM-956BA-NA3TN-6J9DL-3S46S-99AUT
Used output buffers: 1 of 40 (11 max)
=== RTOS ===
Static ram: 123292
Dynamic ram: 139216 of which 140 recycled
Never used RAM 129544, free system stack 126 words
Tasks: Linux(ready,101) HEAT(blocked,272) CanReceiv(blocked,829) CanSender(blocked,352) CanClock(blocked,352) TMC(blocked,20) MAIN(running,669) IDLE(ready,19)
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:23:02 ago, cause: power up
Last software reset at 2020-12-19 15:22, reason: User, none spinning, available RAM 129752, slot 0
Software reset code 0x0012 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0xffffffff Task Linu
Error status: 0x00
MCU temperature: min 27.7, current 31.2, max 42.6
Supply voltage: min 24.0, current 24.1, max 24.3, 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
Driver 0: position 72800, standstill, reads 18438, writes 31 timeouts 0, SG min/max 0/248
Driver 1: position 4000, standstill, reads 18439, writes 31 timeouts 0, SG min/max 0/244
Driver 2: position 6400, standstill, reads 18440, writes 31 timeouts 0, SG min/max 0/246
Driver 3: position 0, standstill, reads 18440, writes 31 timeouts 0, SG min/max 0/245
Driver 4: position 0, standstill, reads 18441, writes 31 timeouts 0, SG min/max 0/244
Driver 5: position 0, standstill, reads 18459, writes 14 timeouts 0, SG min/max 0/0
Date/time: 2020-12-19 15:51:23
Slowest loop: 182.07ms; fastest: 0.09ms
=== Storage ===
Free file entries: 10
SD card 0 not detected, interface speed: 37.5MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
FreeDm 375 (min 372), maxWait 436239ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 49, completed moves 49, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], 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 = 3 -1 -1 -1
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP* is doing "M122" 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.
=== Filament sensors ===
Extruder 0: no data received
=== CAN ===
Messages queued 5738, send timeouts 0, received 12611, lost 0, longest wait 3ms for reply type 6049, free buffers 47
=== SBC interface ===
State: 0, failed transfers: 0
Last transfer: 19ms ago
RX/TX seq numbers: 47923/47924
SPI underruns 0, overruns 0
Number of disconnects: 0, IAP RAM available 0x209d8
Buffer RX/TX: 0/0-0
=== Duet Control Server ===
Duet Control Server v3.2.0-beta4
Code buffer space: 4096
Configured SPI speed: 8000000 Hz
Full transfers per second: 30.23

Frederik

@Veti the bootloader doesent make a big difference

this time, it completes perhaps 40% of my build area bevor it stops and starts blinking.

the workaround lines of code are also in place....

Stephen6309

@Frederik You could try a lower speed in M558. I use 6000.

Frederik

@Stephen6309 i will try, moment

Veti

you could also try adjusting the grub screw on the top of the bltouch.

Frederik

@Stephen6309 speed to 6000 - same error

@Veti one moment , i will try

Frederik

@Veti i changed the mesh size from 20mm to 75mm and it completed the whole area without error.