Multiply issues with new 6HC

yagodajm

@Phaedrux Good Morning, here is the requested information.

M122

12/28/2023, 7:44:02 AM	M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.5.0-rc.2 (2023-12-14 10:32:22) running on Duet 3 MB6HC v1.02 or later (standalone mode)
Board ID: 0JD4M-958L1-M2NSW-6JTD4-3S46S-T0KPW
Used output buffers: 1 of 40 (18 max)
Error in macro line 13 while starting up: Failed to add SSID to remembered list: WiFi module is disabled
=== RTOS ===
Static ram: 154844
Dynamic ram: 120660 of which 12 recycled
Never used RAM 67620, free system stack 200 words
Tasks: NETWORK(1,ready,39.0%,161) ETHERNET(5,nWait,0.1%,321) HEAT(3,nWait,0.0%,328) Move(4,nWait,0.0%,339) CanReceiv(6,nWait,0.0%,942) CanSender(5,nWait,0.0%,334) CanClock(7,delaying,0.0%,343) TMC(4,nWait,7.7%,59) MAIN(1,running,52.9%,103) IDLE(0,ready,0.1%,30), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:01:51 ago, cause: power up
Last software reset at 2023-12-27 19:22, reason: User, Gcodes spinning, available RAM 67620, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044a000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
MCU temperature: min 14.4, current 26.4, max 26.4
Supply voltage: min 24.4, current 24.5, max 24.6, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.1, current 12.2, max 12.4, under voltage events: 0
Heap OK, handles allocated/used 99/2, heap memory allocated/used/recyclable 2048/76/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min n/a, mspos 8, reads 26989, writes 17 timeouts 0
Driver 1: standstill, SG min n/a, mspos 8, reads 26989, writes 17 timeouts 0
Driver 2: standstill, SG min n/a, mspos 8, reads 26989, writes 17 timeouts 0
Driver 3: standstill, SG min n/a, mspos 8, reads 26989, writes 17 timeouts 0
Driver 4: standstill, SG min n/a, mspos 8, reads 26989, writes 17 timeouts 0
Driver 5: standstill, SG min n/a, mspos 8, reads 26989, writes 17 timeouts 0
Date/time: 2023-12-28 07:44:00
Slowest loop: 10.29ms; fastest: 0.07ms
=== Storage ===
Free file entries: 20
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 5.6ms, 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, 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 0 -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 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
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 1000, received 0, lost 0, errs 523778, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 50 (min 50), ts 557/0/0
Tx timeouts 0,0,556,0,0,442 last cancelled message type 30 dest 127
=== Network ===
Slowest loop: 10.64ms; fastest: 0.03ms
Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 2 of 8
= Ethernet =
Interface state: active
Error counts: 0 0 0 1 0 0
Socket states: 5 2 2 2 2 0 0 0
=== WiFi ===
Interface state: disabled
Module is disabled
Failed messages: pending 0, notrdy 0, noresp 0
Socket states: 0 0 0 0 0 0 0 0
=== Multicast handler ===
Responder is inactive, messages received 0, responses 0

M98

12/28/2023, 7:46:20 AM	M98 P"config.g"
HTTP is enabled on port 80
Error: Failed to add SSID to remembered list: WiFi module is disabled
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Error: Unknown pin name '"io2.in"'
Error: invalid Z probe index
Error: in file macro line 58 column 10: M950: expected a string expression
Warning: Heater 0 predicted maximum temperature at full power is 321°C

I was able to get the heated bed working, so right now it is just the WiFi and homing the axises.

Thanks,
Justin

yagodajm

Ok so I am still having issues with the WiFI and getting anything to home properly.

First the WiFi, I worked on this all day today. I have the Module and server firmware installed. I keep getting an error that the WiFi is disabled. I ran a M552 I1 S0 and got a green box saying it was accepted. I then ran a M552 I1 S1 and also got a green box saying it was accepted. Under Machine-Specific it shows the server version, but I still can get it to connect to my network. I ended up wiping the board and reloading all the firmware, I read this may fix the issue. However, after reinstalling the firmware, I am still having the same issues. Should there be any indicator LEDs on the module? I read something about green and blue but did not see when these should happen. I see a quick LED flicker green when I first boot the board, but that is the only time I see the light. I am at a complete loss.

I am also still having issues getting anything to home correctly. I even went back and did the whole config setup in the older version of RRF. I was thinking maybe some of the settings were not correct. That still did not work.

Any help would be greatly appreciated, I am pulling my hair out.

Thanks,
Justin

jay_s_uk

@yagodajm which wifi server version are you running? Have you tried 2.1b6?

droftarts

@yagodajm did you follow the instructions here? https://docs.duet3d.com/Duet3D_hardware/Duet_3_family/Duet_3_Mainboard_6HC_Hardware_Overview#wifi-module-installation-and-setup
Particularly:

Note that the wifi module is the second network interface on the 6HC (the ethernet interface is the first one) so all M552 commands need to contain "I1" to indicate they are for the wifi module interface.

So make sure you have M552 I1 S1 in your config.g, the config you posted earlier only has M552 S1. Also remove M587 in your config.g; you do not need to keep setting WiFi SSID and password.

Post your current config and homing macros. What motors do you have on the axes?

Ian

yagodajm

@jay_s_uk Good evening, Yes, I am using 2.1b6. I am using the one from this repository. https://github.com/Duet3D/WiFiSocketServerRTOS/releases DuetWiFiServer_32S3.bin

Thanks,
Justin

yagodajm

@droftarts Good Evening, Here are my current config and homing files. I am using StepperOnline motors. I have these on my other printer and they work great. They are Bipolar 2.0 A. I added the line in my config for the WiFi, I just don't think the server is starting up automatically like it should, If I do a M552 I1 S1 and look on the Machine_ specific page it shows the firmware number. I still never get any lights on the wifi module itself.

Thanks,
Justin

; Configuration file for RepRapFirmware on Duet 3 Main Board 6HC
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.5.0-rc.2 on Sat Dec 30 2023 14:39:37 GMT-0600 (Central Standard Time)

; General
M550 P"Duet 3" ; set hostname

; Network
M552 P0.0.0.0 S1 ; configure Ethernet adapter
M586 P0 S1 ; configure HTTP
M552 I1 S1

; Smart Drivers
M569 P0.0 S1 D3 V2000 ; driver 0.0 goes forwards (X axis)
M569 P0.1 S0 D3 V2000 ; driver 0.1 goes backwards (Y axis)
M569 P0.2 S1 D3 V2000 ; driver 0.2 goes forwards (Z axis)
M569 P0.3 S1 D3 V2000 ; driver 0.3 goes forwards (Z2 axis)
M569 P0.4 S1 D3 V2000 ; driver 0.4 goes forwards (Y2 axis)
M569 P0.5 S0 D3 V2000 ; driver 0.5 goes backwards (extruder 0)

; Motor Idle Current Reduction
M906 I30 ; set motor current idle factor
M84 S30 ; set motor current idle timeout

; Axes
M584 X0.0 Y0.1:0.3 Z0.2:0.3 ; set axis mapping
M350 X16 Y16 Z16 U16 V16 I1 ; configure microstepping with interpolation
M906 X1000 Y1000 Z1000  ; set axis driver currents
M92 X80 Y80 Z400  ; configure steps per mm
M208 X0:300 Y0:300 Z0:300  ; set minimum and maximum axis limits
M566 X900 Y900 Z12  ; set maximum instantaneous speed changes (mm/min)
M203 X6000 Y6000 Z180  ; set maximum speeds (mm/min)
M201 X500 Y500 Z20  ; set accelerations (mm/s^2)

; Extruders
M584 E0.5 ; set extruder mapping
M350 E16 I1 ; configure microstepping with interpolation
M906 E1000 ; set extruder driver currents
M92 E420 ; configure steps per mm
M566 E120 ; set maximum instantaneous speed changes (mm/min)
M203 E3600 ; set maximum speeds (mm/min)
M201 E250 ; set accelerations (mm/s^2)

; Kinematics
M669 K0 ; configure Cartesian kinematics

; Probes
M558 K0 P9 C"""io2.in""" H5 F120 T6000 ; configure BLTouch probe via slot #0
G31 P500 X0 Y0 Z0.7 ; set Z probe trigger value, offset and trigger height
M950 S0 Cio2.out ; create servo #0 for BLtouch

; Endstops
M574 X1 P"io0.in" S1 ; configure X axis endstop
M574 Y1 P"io1.in" S1 ; configure Y axis endstop
M574 Z1 S2 ; configure Z axis endstop

; Mesh Bed Compensation
M557 X25:275 Y25:275 S40:40 ; define grid for mesh bed compensation

; Sensors
M308 S0 P"temp0" Y"thermistor" A"Heated Bed" T100000 B4725 C7.06e-8 ; configure sensor #0
M308 S1 P"temp1" Y"thermistor" A"Nozzle" T100000 B4725 C7.06e-8 ; configure sensor #1

; Heaters
M950 H0 C"out0" T0 ; create heater #0
M143 H0 P0 T0 C0 S140 A0 ; configure heater monitor #0 for heater #0
M307 H0 R2.43 D5.5 E1.35 K0.56 B1 ; configure model of heater #0
M950 H1 C"out1" T1 ; create heater #1
M143 H1 P0 T1 C0 S285 A0 ; configure heater monitor #0 for heater #1
M307 H1 R2.43 D5.5 E1.35 K0.56 B0 ; configure model of heater #1

; Heated beds
M140 P0 H0 ; configure heated bed #0

; Fans
M950 F0 C"out3" ; create fan #0
M106 P0 S0 L0 X1 B0.1 ; configure fan #0
M950 F1 C"out4" ; create fan #1
M106 P1 S0 B0.1 H1 T45 ; configure fan #1

; Tools
M563 P0 D0 H1 F1 ; create tool #0
M568 P0 R0 S0 ; set initial tool #0 active and standby temperatures to 0C

; homeall.g
; called to home all axes
;
; generated by RepRapFirmware Configuration Tool v3.5.0-rc.2 on Sat Dec 30 2023 14:39:41 GMT-0600 (Central Standard Time)

; lift Z
G91 ; relative positioning
G1 H2 Z5 F6000 ; move Z relative to current position to avoid dragging nozzle over the bed
G90 ; absolute positioning

; home XY
var xTravel = move.axes[0].max - move.axes[0].min + 5 ; calculate how far X can travel plus 5mm
var yTravel = move.axes[1].max - move.axes[1].min + 5 ; calculate how far Y can travel plus 5mm
G91 ; relative positioning
G1 H1 X{-var.xTravel} Y{-var.yTravel} F600 ; coarse home in the -X and -Y directions
G1 H2 X5 Y5 F6000 ; move back 5mm
G1 H1 X{-var.xTravel} Y{-var.yTravel} F300 ; fine home in the -X and -Y directions
G90 ; absolute positioning

; home Z
var xCenter = move.compensation.probeGrid.mins[0] + (move.compensation.probeGrid.maxs[0] - move.compensation.probeGrid.mins[0]) / 2 - sensors.probes[0].offsets[0]
var yCenter = move.compensation.probeGrid.mins[1] + (move.compensation.probeGrid.maxs[1] - move.compensation.probeGrid.mins[1]) / 2 - sensors.probes[0].offsets[1]
G1 X{var.xCenter} Y{var.yCenter} F6000 ; go to bed centre
G30 ; probe the bed


M98 P"homeU.g" ; home U axis
M98 P"homeV.g" ; home V axis

; homex.g
; called to home the X axis
;
; generated by RepRapFirmware Configuration Tool v3.5.0-rc.2 on Sat Dec 30 2023 14:39:42 GMT-0600 (Central Standard Time)

; lift Z
G91 ; relative positioning
G1 H2 Z5 ; move Z relative to current position to avoid dragging nozzle over the bed
G90 ; absolute positioning

; home X
var maxTravel = move.axes[0].max - move.axes[0].min + 5 ; calculate how far X can travel plus 5mm
G1 H1 X{-var.maxTravel} F600 ; coarse home in the -X direction
G1 H2 X5 F6000 ; move back 5mm
G1 H1 X{-var.maxTravel} F300 ; fine home in the -X direction
G1 H2 Z-5 F6000 ; lower Z again

; homey.g
; called to home the Y axis
;
; generated by RepRapFirmware Configuration Tool v3.5.0-rc.2 on Sat Dec 30 2023 14:39:42 GMT-0600 (Central Standard Time)

; lift Z
G91 ; relative positioning
G1 H2 Z5 ; move Z relative to current position to avoid dragging nozzle over the bed
G90 ; absolute positioning

; home Y
var maxTravel = move.axes[1].max - move.axes[1].min + 5 ; calculate how far Y can travel plus 5mm
G1 H1 Y{-var.maxTravel} F600 ; coarse home in the -Y direction
G1 H2 Y5 F6000 ; move back 5mm
G1 H1 Y{-var.maxTravel} F300 ; fine home in the -Y direction
G1 H2 Z-5 F6000 ; lower Z again

; homez.g
; called to home the Z axis
;
; generated by RepRapFirmware Configuration Tool v3.5.0-rc.2 on Sat Dec 30 2023 14:39:42 GMT-0600 (Central Standard Time)

; lift Z
G91 ; relative positioning
G1 H2 Z5 ; move Z relative to current position to avoid dragging nozzle over the bed
G90 ; absolute positioning

; home Z
var xCenter = move.compensation.probeGrid.mins[0] + (move.compensation.probeGrid.maxs[0] - move.compensation.probeGrid.mins[0]) / 2 - sensors.probes[0].offsets[0]
var yCenter = move.compensation.probeGrid.mins[1] + (move.compensation.probeGrid.maxs[1] - move.compensation.probeGrid.mins[1]) / 2 - sensors.probes[0].offsets[1]
G1 X{var.xCenter} Y{var.yCenter} F6000 ; go to bed centre
G30 ; probe the bed

yagodajm

@yagodajm Good evening, Ok I got all the motors wired up and double-checked everything. I still can't get anything to home correctly with the home files above. When I do home all or home each one, it acts like it will home and just stops and the axis turns blue like it has been homed. I can move that axis, but only in one direction.

I finally got the WiFi to connect. I was in the DWC and ran a M552 I1 S0, M552 I1 S1, and a M587 with the WiFi network and password. I got a green LED and it connected. Do I just have to add the M552 I1 S1 to the config file for it to connect every time?

I will continue to got through Home files to see what I am missing. One not, this printer is one where the bed raises up and down and the Y and X move back and forth. Do I have to do a different config? I also have two motors on Z on two separate axis, two motors on Y on two separate axis, and X by itself. Would it just be better to tie the two Z and two Y to one driver?

Thanks for all of you help so far.

Justin

yagodajm

@yagodajm Ok, I got X and Y to home correctly, I had to set the endstops to Low. Those now home properly. I am still having an issue with Z and the BL touch probe.

This is what the configurator tool created.

; Probes
M558 K0 P9 C"""io2.in""" H5 F120 T6000 ; configure BLTouch probe via slot #0
G31 P500 X0 Y0 Z0.7 ; set Z probe trigger value, offset and trigger height
M950 S0 Cio2.out ; create servo #0 for BLtouch

I get this error on start-up Error in start-up file macro line 49: Unknown pin name '"io2.in"'

My question is what are there 3 sets of " around the io2.in pin? And why are there now around io2.out?

If I remove the " from the io2.in and add a set to io2.out, then the on homing after x and Y home, the hotend will move to the center of the bed and I get this error. Error: line 12 column 135: meta command: array index out of bounds
Error: Failed to home axes Z

I looked through the documentation, but Can't find any answers.

Thanks,
Justin

jay_s_uk

@yagodajm you should have 1 set of " around the io pin

yagodajm

@jay_s_uk I tried that I still get this error, Error: line 12 column 135: meta command: array index out of bounds
Error: Failed to home axes Z. I have tried every combination so far. I also noticed that when I try and test my BLTouch nothing happens. When I first turn on my printer it does a double click and it is red, so I know it works.

fcwilt

@yagodajm said in Multiply issues with new 6HC:

@jay_s_uk I tried that I still get this error, Error: line 12 column 135: meta command: array index out of bounds
Error: Failed to home axes Z. I have tried every combination so far. I also noticed that when I try and test my BLTouch nothing happens. When I first turn on my printer it does a double click and it is red, so I know it works.

Why are you trying to find xCenter, etc using move.compensation.probeGrid.mins[0] and so forth?

Frederick

yagodajm

@fcwilt This is the file that the RRF Config tool made. I think everything is different with the 3.5 config tool now. My other printer is running on 3.4.6 so the files are all different. I can't use those files for a comparison.

fcwilt

@yagodajm said in Multiply issues with new 6HC:

@fcwilt This is the file that the RRF Config tool made. I think everything is different with the 3.5 config tool now. My other printer is running on 3.4.6 so the files are all different. I can't use those files for a comparison.

The error you mentioned suggests that the lines that are setting xCenter and yCenter are attempting to index into values that do not exist.

As a test set xCenter and yCenter directly to values that you compute by hand and see if the error goes away.

Frederick

yagodajm

@fcwilt Good afternoon, Ok I finally got a chance to make changes to the home file. I just set X150 Y150. That worked, the error went away and the z axis homed. I am not sure why the RRF is making the home files like that now, it is very confusing.

One last question, my hotend fan comes right on when I start up my printer. I changed that line every which way and can't get it to shut off. It should only come on when the hotend gets to 45c. It is just a regular 2 wire fan.

I have it wired on out4 GND and V_outLC1.

M950 F1 C"out4" ; create fan #1
M106 P1 S0 B0.1 H1 T45 ; configure fan #1

Any ideas?

Thanks,
Justin

fcwilt

@yagodajm said in Multiply issues with new 6HC:

I am not sure why the RRF is making the home files like that now, it is very confusing.
It's a very bad idea because it relies on values that may not be set when homing Z, as you have found.

One last question, my hotend fan comes right on when I start up my printer. I changed that line every which way and can't get it to shut off. It should only come on when the hotend gets to 45c. It is just a regular 2 wire fan.

I have it wired on out4 GND and V_outLC1.

It should be wired to OUT4 instead of OUT4 GND.

Frederick

yagodajm

@fcwilt thank you, that worked. The part fan should be wired the same way, correct.

Thanks,
Justin