Error: Board 121 does not have input handle 1000

Frederik

@dc42 Wow, thanks for this information, do you think R0.5 is sufficient enough?

Kindly Regards
Frederik

dc42

@frederik, try it and see! I've made a note to do some tests to see whether I can reproduce this, and whether adding additional capacitance will help. I do know that on my test system at least, the BLTouch can go through the self-test sequence without causing a brownout.

When is the hardware version number of your tool board? It will be either 0.6 or 1.0.

Frederik

@dc42 thats the same on my machine

every command on its own is working, even as fast as i can send them.

also the self test

Strange is, that a single G30 , sometimes generates the same error, even if there was 5 minutes no other probing movement.
i added the R0.5 to mybltouch m558 command.

No testing if it works

Frederik

@dc42 amazing , seems to work

I re-startet my printer twice, run my normal startup routine and the error didnt occur till now

Damn, the third time trying , error is there again

i did again the diagnose :

m122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.3beta2 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: 148476
Dynamic ram: 62124 of which 40 recycled
Never used RAM 143552, free system stack 123 words
Tasks: Linux(ready,147) HEAT(delaying,303) CanReceiv(notifyWait,798) CanSender(notifyWait,374) CanClock(delaying,350) TMC(notifyWait,58) MAIN(running,923) IDLE(ready,19)
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:04:43 ago, cause: software
Last software reset at 2021-04-12 11:53, reason: User, none spinning, available RAM 143552, slot 2
Software reset code 0x0012 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0444a000 BFAR 0x00000000 SP 0x00000000 Task Linu Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Aux1 errors 0,0,0
MCU temperature: min 35.3, current 36.2, max 51.3
Supply voltage: min 24.0, current 24.1, max 24.2, 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 92658, standstill, reads 18869, writes 21 timeouts 0, SG min/max 0/249
Driver 1: position 37346, standstill, reads 18869, writes 21 timeouts 0, SG min/max 0/244
Driver 2: position 5272, standstill, reads 18869, writes 21 timeouts 0, SG min/max 0/140
Driver 3: position 0, standstill, reads 18869, writes 21 timeouts 0, SG min/max 0/132
Driver 4: position 0, standstill, reads 18870, writes 21 timeouts 0, SG min/max 0/135
Driver 5: position 0, standstill, reads 18877, writes 14 timeouts 0, SG min/max 0/0
Date/time: 2021-04-12 11:57:45
Slowest loop: 174.21ms; fastest: 0.04ms
=== 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 ===
DMs created 125, maxWait 158161ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 57, completed moves 57, 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 = 2 -1 -1 -1
Heater 0 is on, I-accum = 0.1
Heater 1 is on, I-accum = 0.0
=== 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 2659, send timeouts 0, received 3601, lost 0, longest wait 2ms for reply type 6049, peak Tx sync delay 6, free buffers 49 (min 48)
=== SBC interface ===
State: 4, failed transfers: 0
Last transfer: 1ms ago
RX/TX seq numbers: 10284/10284
SPI underruns 0, overruns 0
Number of disconnects: 0, IAP RAM available 0x2d52c
Buffer RX/TX: 0/0-0
=== Duet Control Server ===
Duet Control Server v3.3-b2
Code buffer space: 4096
Configured SPI speed: 8000000 Hz
Full transfers per second: 36.64
Codes per second: 0.87
Maximum length of RX/TX data transfers: 2884/836

m122 b121
Diagnostics for board 121:
Duet TOOL1LC firmware version 3.3beta2 (2021-03-10 10:06:22)
Bootloader ID: SAMC21 bootloader version 2.2 (2021-01-16b1)
Never used RAM 3564, free system stack 0 words
Tasks: Move(notifyWait,152) HEAT(delaying,77) CanAsync(notifyWait,59) CanRecv(notifyWait,79) CanClock(notifyWait,67) TMC(delaying,56) MAIN(running,348) AIN(delaying,63)
Last reset 00:04:46 ago, cause: software
Last software reset time unknown, reason: OutOfMemory, available RAM 15440, slot 0
Software reset code 0x01c0 ICSR 0x00000000 SP 0x20003638 Task MAIN Freestk 796 ok
Stack: 20000d10 00012407 20000d10 0001e7d9 00000000 00004008 20000d10 0001e74d 20000d0c 00004000 a5a5a5a5 a5a5a5a5 00000000 0001e615 00004000 000193a1 a5a5a5a5 000193bd a5a5a5a5 00012255 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5
Driver 0: position 0, 859.0 steps/mm, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 23, reads 11924, writes 11, timeouts 0, DMA errors 0, steps req 0 done 0
Moves scheduled 0, completed 0, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
Peak sync jitter 4, peak Rx sync delay 214, resyncs 3, no step interrupt scheduled
VIN: 23.6V
MCU temperature: min 48.7C, current 51.4C, max 51.5C
Ticks since heat task active 48, ADC conversions started 284927, completed 284926, timed out 0
Last sensors broadcast 0x00000002 found 1 53 ticks ago, loop time 0
CAN messages queued 3657, send timeouts 0, received 2685, lost 0, free buffers 36, min 36, error reg 0
dup 0, oos 0, bm 0, wbm 0
=== Filament sensors ===
Interrupt 4 to 9us, poll 8 to 689us
Driver 0: pos 0.00, errs: frame 3 parity 0 ovrun 0 pol 0 ovdue 0

also the duet laser filament sensor didnt register any movement, its only blinking like normal green / blue , but didnt recognise the filament, only when im manual wiggling it without bowden on top, then it recognoses the movement

dc42

@frederik said in Error: Board 121 does not have input handle 1000:

the third time trying , error is there again

Which error: the input handle error, or another one?

Frederik

@dc42 z probe not triggered on the last probing spot

Frederik

@dc42 ill try with a longer R value.

if setting again from 2.5mm to 10mm it works.

i also will try if 5mm probing height would work too

dc42

@frederik, I just tested a BLTouch connected to a version 1.0 tool board, and there doesn't appear to be any problem with the 5V rail. So my theory about the capacitor appears to be wrong. Here are some other possibilities:

Poor connection in the power wiring to the tool board;
Faulty BLTouch;
Faulty tool board;
Something else connected to the tol board dragging down the 5V supply.

Frederik

@dc42 Good Morning,

i have also tested different scenarios.

With 5mm dive height, it worked also flawless

2.3mm dive height not working
2.3mm dive height not working + M558 option R0.5 - not working

Since yesterday it works with 5mm dive height without errors

My toolboard is nearly fully occupied.

1x optical sensor
1x bltouch
1x duet laser filament sensor
1x65W heater
1xrtd 1000 Sensor
1x5015 blower
1x40mm sunon for the mosquito magnum

I checked the cabling since it happened quite often. there only max 10 cm long, without splices and correct crimping, + heatshrinks

the terminals are all tighten really well and no cable breaks on the blank ends.

Everything looks fine

Kindly Regards
Frederik

dc42

@frederik, is your tool board also version 1.0? The early boards we shipped were version 0.6.

Frederik

@dc42 its Revision 1.0 with the new socket for temp1 (micro jst)

dc42

@frederik, please can you test it with the optical sensor disconnected. I am wondering whether the additional current draw of that sensor is contributing to the problem.

Frederik

@dc42 i can test that

i´m back at my printer tomorrow and will let you know what are the results