@t3p3tony said in Connection issues between 6HC and Pi 3B:
M115 B121
Thanks Tony! You are my saviour, it was actually running 3.1. I didn't realise I needed to run a M997 to get the firmware to update. Now its 3.3 and is extruding 
Super satisfying to see the 1.2mm noodle.
@t3p3tony said in Connection issues between 6HC and Pi 3B:
M115 B121
Thanks Tony! You are my saviour, it was actually running 3.1. I didn't realise I needed to run a M997 to get the firmware to update. Now its 3.3 and is extruding Super satisfying to see the 1.2mm noodle.
@t3p3tony said in Connection issues between 6HC and Pi 3B:
M98 P"0/sys/config.g"
M98 P"0/sys/config.g"
Error: M584: Board 121 received unknown msg type 6042
Error: M350: Board 121 received unknown msg type 6042
Error: M92: Board 121 received unknown msg type 6042
Error: M906: Board 121 received unknown msg type 6043
Error: M308: Board 121 received unknown msg type 6031
Error: M950: Pin 121.out0 is not free
Error: M307: Heater 1 not found
Error: M143: Heater 1 does not exist
Heater 1 is the bed and is direct from the duet, so don't worry about that.
Yep it was a CAN wiring issue, thanks for that! it now flashes in time with the mainboard and is receiving packets when M122 is run. Unfortunately I am yet to be able to make the Toolboard actually drive anything or receive sensor inputs. Fans etc, heaters, thermistor etc. isn't working or reporting any value at all. May well be a configuration issue though and I have attached the current config as downloaded from DWCconfig.g
Additionally with homing I am having a lot of trouble getting the axis to move more than the say 5mm back off distance that is set, it simply just moves 5mm and stops each time, irrespective of the switch or not.
Currently I have my limit switches wired NO between the IN and GND of the respective IO ports.
Fun times and a lot of learning
Just continous, which matches with the no CAN communication error code.
Firmware is in firmware directory and is visible by DWC.
Wiring wise, I have a RJ11 cable up to the tool distribution board which is receiving 24v power and then a 4 pin cable to the toolboard. Distribution board is mounted above the extruder, so will move obviously but because minimising mass isn't critical seemed like a good way to do the wiring especially as my current requirements for the hotend are more than that toolboard can supply etc so need a SSR anyway.
I have the two jumpers removed from port 1 that it is wired to.
Seems to be working now, I obviously can't nail it down completely but I switched to a Pi 4B instead of the 3B and reimaged the same microSD with DuetPi-lite. I used the exact same wpa_supplicant file I previously made and I can now access it via Duet3.local
Making some progress in the config but still can't seem to get the toolboard talking which is a little frustrating. Just the constant red flashing indicator light. I have held both button 1 and 2 down from before I power it on until its fully booted but as soon as I release them it begins flashing again with no comms.
Learning to write the firmware is pretty fun!
Yes I did have it in that instance as I have been moving between the two trying to get something to work, after I removed it and rebooted with just the SBC microSD it remained in standalone according to the M122(as well as becoming completely unresponsive to the PanelDue, so I just reimaged the SBC microSD to have a "clean" DuetPi install. Then restarted the system with that reimaged SD in the SBC and nothing in the Duet 3, both HDMI output and the duet.local web interface just say failed to connect to duet3.local.
Doing the M122 readout again it does seem to be in SBC mode now, but obviously no functionality at all.
=== Diagnostics ===<LF>RepRapFirmware for Duet 3 MB6HC version 3.3 (2021-06-15 21:45:47) running on Duet 3 MB6HC v1.01 or later (SBC mode)<LF>Board ID: 08DJM-9P63L-DJ3T8-6JKD6-3SD6S-1U4M8<LF>Used output buffers: 1 of 40 (1 max)<LF>=== RTOS ===<LF>Static ram: 150904<LF>Dynamic ram: 59980 of which 0 recycled<LF>Never used RAM 143308, free system stack 200 words<LF>Tasks: SBC(ready,4.2%,606) HEAT(delaying,0.0%,405) Move(notifyWait,0.0%,352) CanReceiv(notifyWait,0.0%,944) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,339) TMC(notifyWait,7.0%,93) MAIN(running,88.8%,1272) IDLE(ready,0.0%,29), total 100.0%<LF>Owned mutexes: USB(MAIN)<LF>=== Platform ===<LF>Last reset 00:05:00 ago, cause: power up<LF>Last software reset time unknown, reason: User, GCodes spinning, available RAM 109240, slot 0<LF>Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044a000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a<LF>Error status: 0x00<LF>Step timer max interval 14997<LF>MCU temperature: min 14.4, current 23.3, max 23.5<LF>Supply voltage: min 23.8, current 23.9, max 23.9, under voltage events: 0, over voltage events: 0, power good: yes<LF>12V rail voltage: min 12.1, current 12.2, max 12.2, under voltage events: 0<LF>Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0<LF>Driver 0: position 0, standstill, reads 45558, writes 11 timeouts 0, SG min/max 0/0<LF>Driver 1: position 0, standstill, reads 45558, writes 11 timeouts 0, SG min/max 0/0<LF>Driver 2: position 0, standstill, reads 45558, writes 11 timeouts 0, SG min/max 0/0<LF>Driver 3: position 0, standstill, reads 45558, writes 11 timeouts 0, SG min/max 0/0<LF>Driver 4: position 0, standstill, reads 45558, writes 11 timeouts 0, SG min/max 0/0<LF>Driver 5: position 0, standstill, reads 45559, writes 11 timeouts 0, SG min/max 0/0<LF>Date/time: 1970-01-01 00:00:00<LF>Slowest loop: 0.12ms; fastest: 0.00ms<LF>=== Storage ===<LF>Free file entries: 10<LF>SD card 0 not detected, interface speed: 37.5MBytes/sec<LF>SD card longest read time 0.0ms, write time 0.0ms, max retries 0<LF>=== Move ===<LF>DMs created 125, maxWait 0ms, bed compensation in use: none, comp offset 0.000<LF>=== MainDDARing ===<LF>Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1<LF>=== AuxDDARing ===<LF>Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1<LF>=== Heat ===<LF>Bed heaters = -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1<LF>=== GCodes ===<LF>Segments left: 0<LF>Movement lock held by null<LF>HTTP is idle in state(s) 0<LF>Telnet is idle in state(s) 0<LF>File is idle in state(s) 0<LF>USB is ready with "m122" in state(s) 0<LF>Aux is idle in state(s) 0<LF>Trigger is idle in state(s) 0<LF>Queue is idle in state(s) 0<LF>LCD is idle in state(s) 0<LF>SBC is idle in state(s) 0<LF>Daemon is idle in state(s) 0<LF>Aux2 is idle in state(s) 0<LF>Autopause is idle in state(s) 0<LF>Code queue is empty.<LF>=== CAN ===<LF>Messages queued 1502, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 49 (min 49), ts 1502/0/0<LF>Tx timeouts 0,0,106,0,0,0 last cancelled message type 30 dest 127<LF><LF>=== SBC interface ===<LF>State: 0, failed transfers: 1, checksum errors: 0<LF>Last transfer: 271128ms ago<LF>RX/TX seq numbers: 0/1<LF>SPI underruns 0, overruns 0<LF>Disconnects: 0, timeouts: 0, IAP RAM available 0x2c83c<LF>Buffer RX/TX: 0/0-0<LF>ok<LF>
Something I have noticed is that when using BalenaEtcher it always seems to say imaging failed just before finishing the verification process, but when I use the Win32 Disk Imager there are no error notices etc. It is a 16GB SanDisk Class 10 microSD, but I have had it a while.
@jay_s_uk I'm blind 
, too many M115's
This is the full readout:
=== Diagnostics ===<LF>RepRapFirmware for Duet 3 MB6HC version 3.3 (2021-06-15 21:45:47) running on Duet 3 MB6HC v1.01 or later (standalone mode)<LF>Board ID: 08DJM-9P63L-DJ3T8-6JKD6-3SD6S-1U4M8<LF>Used output buffers: 1 of 40 (2 max)<LF>=== RTOS ===<LF>Static ram: 150904<LF>Dynamic ram: 91128 of which 64 recycled<LF>Never used RAM 112096, free system stack 192 words<LF>Tasks: NETWORK(ready,12.1%,548) HEAT(delaying,0.0%,403) Move(notifyWait,0.0%,352) CanReceiv(notifyWait,0.0%,944) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,339) TMC(notifyWait,7.5%,93) MAIN(running,79.8%,1114) IDLE(ready,0.6%,29), total 100.0%<LF>Owned mutexes: USB(MAIN)<LF>=== Platform ===<LF>Last reset 00:16:58 ago, cause: power up<LF>Last software reset time unknown, reason: User, GCodes spinning, available RAM 109240, slot 0<LF>Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044a000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a<LF>Error status: 0x00<LF>Aux0 errors 0,0,0<LF>Step timer max interval 125<LF>MCU temperature: min 19.7, current 23.4, max 23.6<LF>Supply voltage: min 23.8, current 23.9, max 23.9, under voltage events: 0, over voltage events: 0, power good: yes<LF>12V rail voltage: min 12.1, current 12.2, max 12.3, under voltage events: 0<LF>Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0<LF>Driver 0: position 0, standstill, reads 47642, writes 14 timeouts 0, SG min/max 0/0<LF>Driver 1: position 0, standstill, reads 47642, writes 14 timeouts 0, SG min/max 0/0<LF>Driver 2: position 0, standstill, reads 47642, writes 14 timeouts 0, SG min/max 0/0<LF>Driver 3: position 0, standstill, reads 47645, writes 11 timeouts 0, SG min/max 0/0<LF>Driver 4: position 0, standstill, reads 47645, writes 11 timeouts 0, SG min/max 0/0<LF>Driver 5: position 0, standstill, reads 47645, writes 11 timeouts 0, SG min/max 0/0<LF>Date/time: 1970-01-01 00:00:00<LF>Slowest loop: 1.98ms; fastest: 0.05ms<LF>=== Storage ===<LF>Free file entries: 10<LF>SD card 0 detected, interface speed: 25.0MBytes/sec<LF>SD card longest read time 9.5ms, write time 0.0ms, max retries 0<LF>=== Move ===<LF>DMs created 125, maxWait 0ms, bed compensation in use: none, comp offset 0.000<LF>=== MainDDARing ===<LF>Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1<LF>=== AuxDDARing ===<LF>Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1<LF>=== Heat ===<LF>Bed heaters = -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1<LF>=== GCodes ===<LF>Segments left: 0<LF>Movement lock held by null<LF>HTTP is idle in state(s) 0<LF>Telnet is idle in state(s) 0<LF>File is idle in state(s) 0<LF>USB is ready with "M122" in state(s) 0<LF>Aux is idle in state(s) 0<LF>Trigger is idle in state(s) 0<LF>Queue is idle in state(s) 0<LF>LCD is idle in state(s) 0<LF>SBC is idle in state(s) 0<LF>Daemon is idle in state(s) 0<LF>Aux2 is idle in state(s) 0<LF>Autopause is idle in state(s) 0<LF>Code queue is empty.<LF>=== CAN ===<LF>Messages queued 5098, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 49 (min 48), ts 5092/0/0<LF>Tx timeouts 0,0,5,0,0,0 last cancelled message type 30 dest 127<LF><LF>=== Network ===<LF>Slowest loop: 0.28ms; fastest: 0.00ms<LF>Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions<LF>HTTP sessions: 0 of 8<LF>- Ethernet -<LF>State: disabled<LF>Error counts: 0 0 0 0 0<LF>Socket states: 0 0 0 0 0 0 0 0<LF>ok<LF>
SBC is idle in state? Not sure if that means that the Duet is connected to it, but I can't get anything via the DWC when viewing the Pi HDMI output.
Thanks for the help! If I have the USB plugged into the Duet and give the M112 command via YAT I get "Emergency Stop! Reset the controller to continue." Not sure about SBC connection?
As an aside, I tested a much shorter RJ11 for the CAN but issue remains. Really appreciate the CAN status LEDs, great idea.
Thanks guys, I'm not really sure why the config file would make a difference? Would that actually affect connection between the two via the cable?
I was planning to do the config after I got them talking, as it would put less wear and tear on the little microSD but I did a basic config using the reprap config tool and put it on the SD card( it should be attached) I still couldn't get them to talk. There are a lot of tweaks I need to make obviously for a fully custom, very large printer like this and taking the microsd in and out is already getting old.
I've also replaced the cable as well and hasn't solved it.
Kind of given up on the SBC for now, luckily from my understanding it doesn't really change the config. So just moving on with trying to get all the firmware written so I can start making spaghet
Can't get the 6HC to talk nicely to the Toolboard either over CAN unfortunately, the cable is 5 meters( can't be much less than this haha) and is a good quality, well made RJ11 urgh. I know the default CAN ID for the toolboard should be 121 and I do have that in my config. Both LEDs on as they should be on the Toolboard but no movement and CAN warnings on the PanelDue as expected.config_v4_wPi.g
Hi guys, having a lot of trouble getting my Duet 3 6HC talking to the SBC Pi. Really causing me a bit of a headache, been trying for nearly two days haha
Duet works with the Paneldue with a microsd in the Duet, and can move axis around using move functions, but once I remove the microsd from the duet, add the Pi with the cable it doesn't talk to it. Just says failed to connect to duet3 and failed to start Duet Control Server.
I have looked at trying to run it without, but would need to get a ethernet to wifi thingo as well and I need this up and running ASAP. It is also a very large printer, with 4 Z axis motors, a Toolboard, bltouch, lots of fans etc. so i would likely benefit from the easier firmware tweaks that the SBC would provide.
Not many posts on here which actually explain a solution to the issue, I do not have a case which interfers with the pins, just the provided ribbon cable plugged straight in( the correct way) also have both powered separately for now.
I have updated the Duet to V 3.3(from 3.1 that it was shipped with), confirmed via M115 in YAT
and the Pi 3B is running the latest DuetPi from github