Solved Toolboard 1LC V1.2 will not connect

[jay_s_uk]

@Jimok post an output of M122 and M122 B121.
Can you also post a photo of your wiring at both ends?

[Jimok]

@jay_s_uk ,
Mate, thanks for your reply, don't take too much notice of some of the other stuff you see here as I am still getting everything sorted!

Cable used for CAN is 1 twisted pair, shielded drag chain cable.
The yellow and white wires shown in the photos at the toolboard end are not connected, simply tucked into the heatshrink.
The polarity of the Can cable is good (CAN-H, CAN-L).
I have checked the resistance of the cable and although I can't remember the numbers off the top of my head, it was good.
The pad for the 120 ohm jumper has been soldered and tested ok.
The same eror message as M121 also comes up on the paneldue on power up.
The only other thing I have done is connect a ground on the toolboard with a 100K resistor to the metalwork of the hot end. There is no change when this is disconnected.

I'm wondering if I don't have the correct firmware on the mainboard?

M122,

07/02/2023, 20:04:27 M122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.4.4 (2022-10-20 16:18:28) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: VT6JG-F196U-D65J0-40KM0-NG03Z-ZLKP6
Used output buffers: 1 of 40 (40 max)
=== RTOS ===
Static ram: 103684
Dynamic ram: 109788 of which 72 recycled
Never used RAM 28168, free system stack 196 words
Tasks: NETWORK(notifyWait,13.8%,223) HEAT(notifyWait,0.0%,358) Move(notifyWait,0.0%,363) CanReceiv(notifyWait,0.0%,817) CanSender(notifyWait,0.0%,336) CanClock(delaying,0.0%,348) TMC(notifyWait,0.7%,115) MAIN(running,78.6%,411) IDLE(ready,6.1%,30) AIN(delaying,0.8%,265), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:04:08 ago, cause: power up
Last software reset at 2023-02-06 11:47, reason: User, GCodes spinning, available RAM 27860, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x04
Aux0 errors 0,0,0
MCU revision 3, ADC conversions started 248749, completed 248749, timed out 0, errs 0
Step timer max interval 1488
MCU temperature: min 26.2, current 36.2, max 36.2
Supply voltage: min 24.4, current 24.5, max 24.6, under voltage events: 0, over voltage events: 0, power good: yes
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, read errors 0, write errors 0, ifcnt 9, reads 13061, writes 9, timeouts 0, DMA errors 0, CC errors 0
Driver 1: standstill, SG min 0, read errors 0, write errors 0, ifcnt 11, reads 13059, writes 11, timeouts 0, DMA errors 0, CC errors 0
Driver 2: standstill, SG min 0, read errors 0, write errors 0, ifcnt 11, reads 13059, writes 11, timeouts 0, DMA errors 0, CC errors 0
Driver 3: standstill, SG min 0, read errors 0, write errors 0, ifcnt 11, reads 13059, writes 11, timeouts 0, DMA errors 0, CC errors 0
Driver 4: standstill, SG min 0, read errors 0, write errors 0, ifcnt 9, reads 13061, writes 9, timeouts 0, DMA errors 0, CC errors 0
Driver 5: not present
Driver 6: not present
Date/time: 2023-02-07 20:04:24
Cache data hit count 440142668
Slowest loop: 13.89ms; fastest: 0.13ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 3.3ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], 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, chamber heaters -1 -1 -1 -1, ordering errs 0
=== 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
=== CAN ===
Messages queued 2217, received 1990, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 6, free buffers 18 (min 17), ts 1244/1243/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 21.41ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 1 of 8
= WiFi =
Network state is active
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.27
WiFi MAC address f0:08:d1:03:82:5d
WiFi Vcc 3.44, reset reason Power up
WiFi flash size 2097152, free heap 25976
WiFi IP address 10.0.0.78
WiFi signal strength -39dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0

M122 B121,

M122 B121
Error: M122: Response timeout: CAN addr 121, req type 6024, RID=15

Photos,

[jay_s_uk]

@Jimok
your photos appear to show yellow and white at the mainboard end connected to the can header rather than the red and black wires.
are you able to confirm this?
I suggest checking against this image here https://docs.duet3d.com/en/Duet3D_hardware/Duet_3_family/Duet_3_Toolboard_1LC#can-connection-1

[Jimok]

@jay_s_uk

Oh.... Poo

It appears that the cable that came with my toolboard may have been wired differently to the cable in the documentation?

My blue, I should have looked more closely at the instructions

I will rewire in the morning and have another go.....

[dc42]

@Jimok it doesn't matter whether you use the 2 wires at one end of the connector or the two wires at the other; but you do need to get CANH and CANL the right way round. Try swapping the red and black wires. You can use fine tip tweezers to lift the plastic barb in the connector and slide the pin out. Do that for both pins, then re-insert them swapped over.

[Jimok]

@Jimok
Thanks.
It appears that in the documentation that the connector is inverted from the way it actually plugs in. I made my cables on the bench and just made it as per the photo, and red, black.
I did check the resitance across the yellow and white wires to confirm the integrity of my soldering and the resistance is 120 Ohms. I'm assuming that the resistance across the other two wires is the same then?
Hopefully this will be a simple fix and I can grow back some of whatever hair I have left!

[dc42]

@Jimok on the TOOL1LC pins 1 and 3 of that socket are connected together, and pins 2 and 4 are connected together.

[Jimok]

Good Morning,
I have been through and checked every thing again and still the same issue, "M122 B121
Error: M122: Response timeout: CAN addr 121, req type 6024, RID=15"
I believe I had it wired correctly in the first place. CAN-H on the mainboard to CAN-H Pin 4 onthe Toolboard, CAN-L on the mainboard to CAN-L pin 3 on the toolboard.
I also connected to pins 1 and 2 with the same result.
I have checked contrinuity of the cable from the back side of the mainboard to the back side of the toolboard to rule out connector issues and all good.
Resistance on both wires on the cable is 1 Ohm.
On the toolboard, Pins 1 & 3, and 2 & 4 are connected together and the resistance across each pair is 120 Ohms.
I have a new toolboard coming from the dealer in Melbourne and hopefully it will be here on Friday. (I am right at the other end of the country!).

[dc42]

@Jimok you haven't shown how the read and black wires connect to the orange/white wires f the CAN cable, so I can't check that they are connected the right way round.

Does the Status LED on the Duet blink once a second, and the Status LED on the tool board blink faster than that?

[Jimok]

@Jimok
Good Evening dc42,
I can assure you that the red wire is connected to the orange wire of the CAN cable and the black wire is connected to the white wire of the CAN cable.
As a diesel fitter by trade, I have some experience with CANBUS systems in automotive, mining, industrial and agricultural eqipment and a better than average understanding of AC and DC electrical systems. Firmware and g-code is something I am still learning. I have had four 3D printers, including 2 that I built myself, albeit with proprietary code, (Flashforge, Lerdge), so this is really my first foray into open source.
I have checked the wiring multiple times and can assure you that CAN -H is connected to CAN-H and CAN-L is connected to CAN-L.
If you need more photos, I can get them tomorrow as I have shut the shed up for tonight.
As best my tired old eyes can tell, the LED's on the mainboard and the Toolboard are flashing in sync, approximately once a second, with maybe a slight lag on the toolboard.
The only time the LED's are not in sync is if I attempt to do a factory reset by pressing both buttons on the toolboard at power-up, and this only lasts for a few seconds.
Always comes back to the timeout error as in my previous post.
I have wired the DUET board to run the extruder etc. in the conventional manner and whilst not having printed anything yet, is running as expected.

[jay_s_uk]

@Jimok have you tried resetting the toolboard by holding both buttons down when powering it up?

[dc42]

@Jimok said in Toolboard 1LC V1.2 will not connect:

As best my tired old eyes can tell, the LED's on the mainboard and the Toolboard are flashing in sync, approximately once a second, with maybe a slight lag on the toolboard.

If they are flashing in sync then the CAN connection is working. If you unplug the CAN cable (at the Duet is easiest) then you should see the LED on the tool board flashing much faster.

Does M115 B121 also return a CAN timeout message?

Perhaps the tool board is not at address 121. If you send M409 K"boards" does the response list just board 0 (the Duet main board) or does it list the tool board too?

[Jimok]

@jay_s_uk yep, seems like hundreds of times!

[Jimok]

@dc42 said in Toolboard 1LC V1.2 will not connect:

If they are flashing in sync then the CAN connection is working. If you unplug the CAN cable (at the Duet is easiest) then you should see the LED on the tool board flashing much faster.

It is only the "STATUS" LED that is flashing. I have not once once seen the "ACT" LED (Green?) light up. I will try disconnecting the cable at the DUET board tommorow.

@dc42 said in Toolboard 1LC V1.2 will not connect:

Does M115 B121 also return a CAN timeout message?

Yes, every time.

@dc42 said in Toolboard 1LC V1.2 will not connect:

Perhaps the tool board is not at address 121. If you send M409 K"boards" does the response list just board 0 (the Duet main board) or does it list the tool board too?

I will try this tomorrow as well.

[Jimok]

Good Evening,
I think I can gladly report that this issue is solved.
As suggested by dc42..

@dc42 said in Toolboard 1LC V1.2 will not connect:

Perhaps the tool board is not at address 121. If you send M409 K"boards" does the response list just board 0 (the Duet main board) or does it list the tool board too?

Well it did recognise the board and its address was 20.
So looking back through the documentation and specifically,

Set the CAN address
Send command M115 B# to verify that the main board can communicate with the Toolboard, where # is the original CAN address (normally 121)
Send command M952 B# A## where ## is the new address you want to use. We suggest you use addresses starting at 20 for Toolboards. So for the first Toolboard, if your new CAN board was at address 121, send M952 B121 A20.
Power the system down and up again, or send M999 B121. This will cause the Toolboard to restart with the new address.
Send command M122 B20 (or whatever address you chose) to verify that you can communicate with the Toolboard at its new address
You can now power up the next Toolboard and commission it in the same way, choosing a different CAN address for it.

Thinking back, I would have followed the documentation and changed the address to 20 and then promptly forgot that I had done it.
This led to countless hours of trying to sort the problem out, the cost of another toolboard and taking up others time to try and solve a problem of my own making!

Anyway, thanks to dc42 and jay-s-uk for the help and please dont curse me too much!

[jay_s_uk]

@Jimok no cursing here, just glad you got sorted!