My 6HC seems to think I have a CAN connected which I do not
-
@darylprice please don't use AI to generate the config! You can use our config tool as a start point.
https://configtool.reprapfirmware.org/
Where are you seeing the CAN errors? A screen shot may help.
-
In the M122 command. When I use M122 B1 I get: CAN response timeout: board 1, req type 6024, RID 0
It is looking for a board that has never existed -
@darylprice
I am assuming that is why my status LED keeps blinking -
-
Just a few minutes later and it is:
-
@darylprice the response from M122 B1 is as expected because there is no board on your bus.
The red led blinking is normal operation.
With those lines I asked you to remove out of your config.g, what does M122 report after a reset?
-
-
I am wondering if I have a bad board?
-
My X,Y , and Z axis' all work. The endstops do not. They are setup for NC.
Any help would be appreciated
-
When and where did you purchase the 6HC?
Is this a new build? Has it ever worked correctly?Can you send M122 and M98 P"config.g" in the gcode console of DWC and copy and paste the results here?
-
@Phaedrux
M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.5.3 (2024-09-18 11:27:36) running on Duet 3 MB6HC v1.02 or 1.02a (SBC mode)
Board ID: 0JD2M-9P9DA-F0PSD-6J1F6-3S46Q-14SM2
Used output buffers: 1 of 40 (17 max)
=== RTOS ===
Static ram: 155352
Dynamic ram: 87412 of which 0 recycled
Never used RAM 103228, free system stack 214 words
Tasks: SBC(2,ready,0.3%,841) HEAT(3,nWait 6,0.0%,353) Move(4,nWait 6,0.0%,335) CanReceiv(6,nWait 1,0.0%,939) CanSender(5,nWait 7,0.0%,334) CanClock(7,delaying,0.0%,336) TMC(4,nWait 6,9.1%,67) MAIN(2,running,89.5%,444) IDLE(0,ready,1.1%,29), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:00:54 ago, cause: power up
Last software reset at 2025-01-29 19:40, reason: User, Gcodes spinning, available RAM 103228, slot 0
Software reset code 0x6003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a
Error status: 0x00
MCU temperature: min 21.3, current 31.0, max 31.0
Supply voltage: min 24.2, current 24.2, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.1, current 12.3, max 12.5, 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 n/a, mspos 8, reads 39186, writes 14 timeouts 0
Driver 1: standstill, SG min n/a, mspos 8, reads 39186, writes 14 timeouts 0
Driver 2: standstill, SG min n/a, mspos 8, reads 39187, writes 14 timeouts 0
Driver 3: standstill, SG min n/a, mspos 8, reads 39187, writes 14 timeouts 0
Driver 4: standstill, SG min n/a, mspos 8, reads 39190, writes 11 timeouts 0
Driver 5: standstill, SG min n/a, mspos 8, reads 39190, writes 11 timeouts 0
Date/time: 2025-01-29 22:23:42
Slowest loop: 1.62ms; fastest: 0.08ms
=== Storage ===
Free file entries: 20
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 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, max steps late 0, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 0.00
no step interrupt scheduled
Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0
=== DDARing 0 ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== DDARing 1 ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
=== GCodes ===
Movement locks held by null, 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
File2 is idle in state(s) 0
Queue2 is idle in state(s) 0
Q0 segments left 0, axes/extruders owned 0x0000000
Code queue 0 is empty
Q1 segments left 0, axes/extruders owned 0x0000000
Code queue 1 is empty
=== CAN ===
Messages queued 275, received 0, lost 0, errs 261140, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 50 (min 50), ts 275/0/0
Tx timeouts 0,0,274,0,0,0 last cancelled message type 30 dest 127
=== SBC interface ===
Transfer state: 5, failed transfers: 0, checksum errors: 0
RX/TX seq numbers: 1297/1297
SPI underruns 0, overruns 0
State: 5, disconnects: 0, timeouts: 0 total, 0 by SBC, IAP RAM available 0x24d04
Buffer RX/TX: 0/0-0, open files: 0
=== Duet Control Server ===
Duet Control Server version 3.5.3 (2024-09-19 12:16:06, 64-bit)
HTTP+Executed:Executing M122
Code buffer space: 4096
Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0
Full transfers per second: 0.13, max time between full transfers: 66.8ms, max pin wait times: 43.4ms/3.7ms
Codes per second: 0.00
Maximum length of RX/TX data transfers: 4359/688The M98 command ran and the block truned green. I assumed it worked correctly
-
This is a new build, so it has never functioned. I purchased in December from :
https://www.filastruder.com/collections/electronics
I sent the files you requested. I am currently away from the machine and will not be back at the shop until tomorrow morning. USA,Oregon PST time -
@darylprice ignore the CAN errors, they just mean that the time sync messages being broadcast at regular intervals are not being acknowledged because there are no devices connected to the CAN bus.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 thanks, I created a new config.g with the config tool. I will be able to test tomorrow about 11:00am.
