trying to see why when i home x and y they only go half way.

frnknstn518

my config file

; Configuration file for Duet 3 MB 6HC (firmware version 3.3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.3.16 on Sat May 13 2023 19:27:15 GMT-0400 (Eastern Daylight Time)

; General preferences
M575 P1 S1 B57600                            ; enable support for PanelDue
G90                                          ; send absolute coordinates...
M83                                          ; ...but relative extruder moves
M550 P"Duet 3"                               ; set printer name
M669 K1                                      ; select CoreXY mode
G4 S2                                        ; Wait for expansion boards to start

; Network
;M552 S1                                      ;Enable network
;M586 P0 S1                                   ;Enable HTTP
;M586 P1 S0                                   ;Disable FTP
;M586 P2 S0                                   ;Disable Telnet

; ----Z Drive Map----

,    ------+------
,    | 0.2 | 0.3 |
,    |-----+-----|
,    | 0.1 | 0.4 |
,    ------+------
,        FRONT
; Looking at the printer from the top
	
; Drive directions
M569 P1.0 S1                                 ; physical drive 1.1 goes forwards Y DRIVE
M569 P1.1 S1                                 ; physical drive 1.0 goes forwards X DRIVE
M569 P0.1 S1                                 ; physical drive 0.1 goes forwards FL Z DRIVE
M569 P0.2 S0                                 ; physical drive 0.2 goes forwards RL Z DRIVE
M569 P0.3 S1                                 ; physical drive 0.3 goes forwards RR Z DRIVE
M569 P0.4 S0                                 ; physical drive 0.4 goes forwards RF Z DRIVE
M569 P0121.0 S0                              ; physical drive 0.0 goes forwards EXTRUDER DRIVE

; Motor mapping and steps per mm
M584 X1.1 Y1.0 Z0.1:0.2:0.3:0.4 E121.0       ; set drive mapping
M84 S3600                                    ; motor idle timeout
M350 X16 Y16 Z16 E16 I1                      ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z400.00 E690.00            ; set steps per mm

; Drive currents and speeds
M566 X900.00 Y900.00 Z60.00 E300.00          ; set maximum instantaneous speed changes (mm/min)
M203 X6000.00 Y6000.00 Z180.00 E7200         ; set maximum speeds (mm/min)
M201 X500.00 Y500.00 Z20.00 E3000.00         ; set accelerations (mm/s^2)
M906 X1600 Y1600 Z1200 E500 I70              ; set motor currents (mA) and motor idle factor in per cent
M84 S120                                     ; Set idle timeout

; Axis Limits
M208 X0 Y0 Z0 S1                             ; set axis minima
M208 X350 Y350 Z350 S0                       ; set axis maxima

; endstops
M574 X2 S1 P"121.io0.in"                     ; X min active high endstop switch
M574 Y2 S1 P"io5.in"                         ; Y min active high endstop switch
M574 Z1 S1 P"io6.in"                         ; Z min active low endstop switch

; Z-Probe
M558 K0 P8 F600:120 C"!121.io2.in" H2 R0.1 F240:120 T6000 A30 S0.0035                  ;Klicky probe

; Z probe offset (Probe behind Revo quickchange)
;G31 P1000 X0 Y20                                                                      ;Klicky probe

; Bed leveling params
M671 X-65:-65:365:365 Y0:395:395:0 S20                         ; Define Z belts locations (Front_Left, Back_Left, Back_Right, Front_Right)
M557 X30:270 Y30:270 P5                                        ; Define bed mesh grid (inductive probe, positions include the Y offset!)

; Heaters
M308 S0 P"temp0" Y"thermistor" T100000 B3950 A"BedTemp"        ; configure sensor 0 as thermistor on pin temp0
M950 H0 C"out1" T0 Q10                                         ; create bed heater output on out0 and map it to sensor 0
M307 H0 R4.843 K1.017:0.000 D1.55 E1.35 S1.00 B0               ; disable bang-bang mode for the bed heater and set PWM limit
M140 H0                                                        ; map heated bed to heater 0
M143 H0 S120                                                   ; set temperature limit for heater 0 to 120C

M308 S1 P"121.temp1" Y"thermistor" T100000 B4725 A"NozzleTemp" ; configure sensor 1 as thermistor on pin temp1
M950 H1 C"121.out0" T1                                         ; create nozzle heater output on 121.out0 and map it to sensor 1
M307 H1 R5.006 K0.971:0.000 D1.64 E1.35 S1.00 B0 V23.9                             ; disable bang-bang mode for heater  and set PWM limit
M143 H1 S280                                                   ; set temperature limit for heater 1 to 280C

; Fans
M950 F0 C"121.out1" Q500                                       ; create fan 0 on pin 121.out1 and set its frequency
M106 P0 S0 H-1                                                 ; set fan 0 value. Thermostatic control is turned off
M950 F1 C"121.out2" Q500                                       ; create fan 1 on pin 121.out2 and set its frequency
M106 P1 S1 H1 T45                                              ; set fan 1 value. Thermostatic control is turned on


; Tools
M563 P0 D0 H1                                                  ; define tool 0
G10 P0 X0 Y0                                                   ; set tool 0 axis offsets
G10 P0 R0 S0                                                   ; set initial tool 0 active and standby temperatures to 0C

T0
; Custom settings are not defined

My homex file

; homeX.g
; called to home the X axis



M400                     ; Wait for current moves to finish
M913 X70 Y70             ; Drop motor current to 70%
M400
G91                      ; Relative positioning
G1 H2 Z5 F6000           ; Lift Z relative to current position
G1 H1 X355 F1800         ; Move quickly to X axis endstop and stop there (first pass)
G1 X-5 F6000             ; Go back a few mm
G1 H1 X355 F360          ; Move slowly to X axis endstop once more (second pass)
G1 H2 Z-5 F6000      ; Lower Z again
G90                   ; Absolute positioning
M400
M913 X100 Y100        ; Return current to 100%
M400

and my homeY file

; homeY.g
; called to home the Y axis


M400                      ; Wait for current moves to finish
M913 X70 Y70              ; Drop motor current to 70%
M400
G91                       ; Relative positioning
G1 H2 Z5 F6000            ; Lift Z relative to current position
G1 H1 Y355 F1800          ; Move quickly to X axis endstop and stop there (first pass)
G1 Y-5 F6000              ; Go back a few mm
G1 H1 Y355 F360           ; Move slowly to X axis endstop once more (second pass)
G1 H2 Z-5 F6000           ; Lower Z again
G90                       ; Absolute positioning
M400
M913 X100 Y100            ; Return current to 100%
M400

any help is greatly appreciated.

deckingman

@frnknstn518 Assuming that you don't get any error messages and also assuming that you've checked the end stops and their wiring, and also assuming that you start the move close to the maximum for both axes, then one possibility might be that your steps per mm are incorrect for the motor/pulley combination you are using. I note that you have set 80 steps per mm for X and Y which would be normal for 1.8 degree motors and 20 tooth pulleys. Might it be that your motors are actually 0.9 degree? i.e 400 full steps per revolution rather than the more usual 200 steps and that you should therefore be using 160 steps per mm?

dc42

@frnknstn518 said in trying to see why when i home x and y they only go half way.:

M92 X80.00 Y80.00 Z400.00 E690.00 ; set steps per mm

Are you sure those X and Y values are correct? If you are using 0.9deg stepper motors then most likely the values should be 160 not 80.

frnknstn518

@dc42 ill check. i am pretty sure the z are 1.8 and the xy are .9. i will adjust the xy.

frnknstn518

@frnknstn518 that was it. but i do get this now

Error: M913: Board 1 received unknown msg type 47
Board 1 received unknown msg type 47

frnknstn518

@frnknstn518 my x and y are on board 1

Phaedrux

Can you send M122 and M122 B# where # is the canbus address of your additional boards? I suspect your expansion board firmware doesn't match your mainboard.

frnknstn518

M122 B1

m122 B1
Diagnostics for board 1:
Duet EXP3HC firmware version 3.3 (2021-06-15 16:12:41)
Bootloader ID: SAME5x bootloader version 2.3 (2021-01-26b1)
Never used RAM 159104, free system stack 4387 words
Tasks: Move(notifyWait,0.0%,125) HEAT(delaying,0.0%,104) CanAsync(notifyWait,0.0%,69) CanRecv(notifyWait,0.0%,80) CanClock(notifyWait,0.0%,71) TMC(notifyWait,7.4%,29) MAIN(running,91.3%,396) IDLE(ready,0.0%,39) AIN(delaying,1.3%,263), total 100.0%
Last reset 00:34:54 ago, cause: software
Last software reset data not available
Driver 0: position 0, 160.0 steps/mm,  standstill, reads 30248, writes 27 timeouts 0, SG min/max 0/116, steps req 228800 done 99199
Driver 1: position 225600, 160.0 steps/mm,  standstill, reads 30249, writes 27 timeouts 0, SG min/max 0/113, steps req 228800 done 99199
Driver 2: position 0, 80.0 steps/mm,  standstill, reads 30266, writes 11 timeouts 0, SG min/max 0/0, steps req 0 done 0
Moves scheduled 6, completed 6, in progress 0, hiccups 0, step errors 0, maxPrep 43, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
Peak sync jitter -7/6, peak Rx sync delay 180, resyncs 0/0, no step interrupt scheduled
VIN: 24.1V, V12: 12.3V
MCU temperature: min 37.7C, current 40.4C, max 40.7C
Ticks since heat task active 228, ADC conversions started 2095141, completed 2095141, timed out 0, errs 0
Last sensors broadcast 0x00000000 found 0 233 ticks ago, loop time 0
CAN messages queued 45, send timeouts 0, received 27202, lost 0, free buffers 37, min 37, error reg 0
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 411, adv 36840/37068

frnknstn518

@frnknstn518 M122

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-DJMSS-6JKD0-3S46M-9UFZ8
Used output buffers: 1 of 40 (12 max)
=== RTOS ===
Static ram: 152760
Dynamic ram: 67108 of which 240 recycled
Never used RAM 130492, free system stack 154 words
Tasks: SBC(ready,0.6%,436) HEAT(notifyWait,0.0%,322) Move(notifyWait,0.0%,256) CanReceiv(notifyWait,0.0%,774) CanSender(notifyWait,0.0%,336) CanClock(delaying,0.0%,339) TMC(notifyWait,7.9%,57) MAIN(running,91.4%,923) IDLE(ready,0.1%,30), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:33:06 ago, cause: software
Last software reset at 2023-05-19 12:45, reason: User, GCodes spinning, available RAM 130564, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044a000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 134
MCU temperature: min 44.1, current 46.3, max 46.4
Supply voltage: min 23.9, current 23.9, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.0, current 12.0, max 12.1, 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 8, reads 1214, writes 11 timeouts 0
Driver 1: standstill, SG min 0, mspos 520, reads 1206, writes 19 timeouts 0
Driver 2: standstill, SG min 0, mspos 520, reads 1206, writes 19 timeouts 0
Driver 3: standstill, SG min 0, mspos 520, reads 1206, writes 19 timeouts 0
Driver 4: standstill, SG min 0, mspos 520, reads 1206, writes 19 timeouts 0
Driver 5: standstill, SG min 0, mspos 8, reads 1215, writes 11 timeouts 0
Date/time: 2023-05-19 13:18:41
Slowest loop: 29.38ms; fastest: 0.03ms
=== 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 33535ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 10, completed 10, 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 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
Heater 1 is on, I-accum = 0.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 17892, received 39656, lost 0, boc 0
Longest wait 3ms for reply type 6053, peak Tx sync delay 267, free buffers 50 (min 47), ts 9931/9930/0
Tx timeouts 0,0,0,0,0,0
=== SBC interface ===
Transfer state: 5, failed transfers: 0, checksum errors: 0
RX/TX seq numbers: 13506/13506
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: 39.86, max time between full transfers: 129.3ms, max pin wait times: 67.0ms/23.9ms
Codes per second: 0.04
Maximum length of RX/TX data transfers: 3072/724

frnknstn518

@frnknstn518 how do i update the EXP3HC
looks like it is 3.3
and the main is 3.4.5

frnknstn518

@frnknstn518 sweet. i updated it and no more warnings. you guys are life savers
now i have to get the klicky right

Phaedrux

Since it appears you are using the SBC, the way to update is to use the Pi terminal and send sudo apt update && sudo apt upgrade

Then check the firmware versions again. If it still hasn't updated, you can manually force an update by sending M997 B1 in the Duet gcode console.

Do you also have a toolboard a can address 121? You should check that one as well.

frnknstn518

@Phaedrux i ran them but now my nozzle temp went to 2000 and is offline and my graph has lines going straight up

frnknstn518

@frnknstn518 nevermind i reset and it went back to normal

Phaedrux

Which did you run? You may need to reboot after updating the pi.

Did you check the firmware was updated?

frnknstn518

@Phaedrux i updated both the boards. then i rebooted. all went to normal thank you

dc42

@frnknstn518 thanks, I'll mark this as solved then.