Solved 1LC Toolboard

[joe92]

hello I've checked the wiring and config since yesterday, but I don't see any errors in general. the board seems to be connected but nothing works. does anyone recognize the problem? I have the command m122 b121 here.

[jay_s_uk]

@joe92 maybe post some details about what you're trying to do, what commands don't work etc

[joe92]

@jay_s_uk the 1lc is on and connected to the duet 3 but the hotend thermistor is not working and none of the fans spin up. the x stop is not connected according to m119. So the main problem is that the canbus signal doesn’t forward the signals, but if I swap the H L cables, the error message comes up at startup that board 121 is not connected

[jay_s_uk]

@joe92 best post the config.g that you're trying to use as just saying things don't work really doesn't give any more information

[joe92]

@jay_s_uk

[jay_s_uk]

@joe92 you know you can copy and paste the config right? makes it so much easier to read than looking at a photo.
it seems odd that you're using a temperature sensor input for a zprobe.

can you post the output of M122 and M98 P"config.g"

Its also strange that your M122 B121 output doesn't report an accelerometer and yet you have a v1.1 or later revision board. Can you post a photo of your toolboard and its wiring?

I also suggest you update the bootloader on the toolboard. https://docs.duet3d.com/User_manual/RepRapFirmware/Updating_bootloader

[joe92]

@jay_s_uk Well, a klickyprobe is planned later, so I thought that the temp 1 should also fit because it's just a simple switch, but later I just set it to io2. I'll send the m122 and m98 later because I'm not at home right now. I'll just copy them in and won't send any photos

[gloomyandy]

@joe92 It is recommended that you have a short delay (about 4 seconds) at the start of your config.g file to allow time for the CAN boards to connect and synchronise with the main board. So try adding G4 S4 at the start of config.g

[droftarts]

@joe92 This:

@gloomyandy said in 1LC Toolboard:
It is recommended that you have a short delay (about 4 seconds) at the start of your config.g file to allow time for the CAN boards to connect and synchronise with the main board. So try adding G4 S4 at the start of config.g

Ian

[dc42]

@joe92 here are some issues I can see in that config.g file:

• No delay near the start to give the tool board time to start up (see the response from @gloomyandy)
• In the M558 command to configure the Z probe, type P5 is not supported on the tool board. If you run M98 P"config.g" then you should see an error message about this. Use P8 instead, and don't use a "temp" input, use an "io" input instead. The usual choice on a tool board is io0.in.

HTH David

[joe92]

m122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.5 (2022-11-30 19:35:23) running on Duet 3 MB6HC v1.01 (SBC mode)
Board ID: 08DJM-9P63L-DJ3S0-7J1F8-3SD6N-TVJV9
Used output buffers: 1 of 40 (40 max)
=== RTOS ===
Static ram: 152760
Dynamic ram: 67452 of which 68 recycled
Never used RAM 130320, free system stack 144 words
Tasks: SBC(ready,259.2%,468) HEAT(notifyWait,5.5%,322) Move(notifyWait,0.9%,259) CanReceiv(notifyWait,9.5%,774) CanSender(notifyWait,0.0%,336) CanClock(delaying,2.5%,339) TMC(notifyWait,3567.3%,57) MAIN(running,41023.7%,923) IDLE(ready,10.0%,30), total 44878.5%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 01:35:39 ago, cause: power up
Last software reset at 2023-02-14 06:40, reason: User, GCodes spinning, available RAM 130608, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a
Error status: 0x04
Aux0 errors 0,0,0
Step timer max interval 134
MCU temperature: min 15.1, current 28.7, max 29.0
Supply voltage: min 24.0, current 24.1, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.1, current 12.2, 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
Events: 0 queued, 0 completed
Driver 0: standstill, SG min 0, mspos 792, reads 32278, writes 19 timeouts 0
Driver 1: standstill, SG min 0, mspos 248, reads 32278, writes 19 timeouts 0
Driver 2: standstill, SG min 0, mspos 8, reads 32278, writes 19 timeouts 0
Driver 3: standstill, SG min 0, mspos 8, reads 32281, writes 16 timeouts 0
Driver 4: standstill, SG min 0, mspos 8, reads 32281, writes 16 timeouts 0
Driver 5: standstill, SG min 0, mspos 8, reads 32281, writes 16 timeouts 0
Date/time: 2023-02-14 20:10:20
Slowest loop: 33.14ms; 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, segments created 3, maxWait 29244ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 40, completed 40, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 25], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed 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, chamber heaters 2 -1 -1 -1, ordering errs 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
=== CAN ===
Messages queued 51586, received 114539, lost 0, boc 0
Longest wait 2ms for reply type 6026, peak Tx sync delay 278, free buffers 50 (min 49), ts 28698/28697/0
Tx timeouts 0,0,0,0,0,0
=== SBC interface ===
Transfer state: 5, failed transfers: 0, checksum errors: 0
RX/TX seq numbers: 30205/30205
SPI underruns 0, overruns 0
State: 5, disconnects: 0, timeouts: 0 total, 0 by SBC, IAP RAM available 0x2ad48
Buffer RX/TX: 0/0-0, open files: 0
=== Duet Control Server ===
Duet Control Server v3.4.5
Code buffer space: 4096
Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0
Full transfers per second: 4.82, max time between full transfers: 491.8ms, max pin wait times: 80.7ms/11.7ms
Codes per second: 0.00
Maximum length of RX/TX data transfers: 3116/1380

[joe92]

I adjusted the config and the toolboard is now responding. Thanks to all