nevermind, I just read some more and SBC (I thought SBC standed for single board computer aka standalone mode, I was wrong) is the RPi mode and the SD card isn't supposed to be in for the RPi mode.

I ain't a reference, but i'm using 3.1.1 on my 3x Duet 3 6HC boards and it has been flawless.

(Railcore II 300ZL, Tronxy X5SA-500 Pro, Ender 3 Pro)

@engikeneer Homeall.g, all homes and bed.g are all clean.

I could not get my BL touch to work at all on ports IO6 and IO7. Only when plugged on IO5 did it work.

I'd try that first, easy swap.

First one in Canada?!

My Ender 3 Pro will be happy! The last of my FDM printers not in Duet!

@droftarts What would be the best line to add to my start gcode to tell it to reheat to the slicer's defined heat and wait for temp reached then proceed?

Can I simply add:

M116 H0 S5

after the homing?

Wow I was approaching this totally the wrong way...

All I have to do, as per your recommandations, is to set in relative mode, and add 100 to Z...

I was WAYYYYYYY overthinking this...

Thanks guys

Just bought 2 WyzecamV2 just for this.

Turns out I can't connect to them (either of them).

The app works well, I see the RTSP feed via VLC, but I cannot connect to it through either ssh or www (http://xxx.xxx.xxx.xxx nor https://xxx.xxx.xxx.xxx)

Any idea? I did extract all files to a microSD, edited the files on it as per instructions (wpa file, not the network).

as mentioned, works well in the app, VLC, even coupled to my Synology NAS, but can'T get it to work...

in your home (either homeall or homez) macro, do you have a g92? I had that for Z for some reason and it reset its position and I could not figure it out.

works perfectly so far!

@infiniteloop Thanks! That's the answer i was looking for!

I have tweaked my resurrect-prologue.g to home XY and hope that Z stays where it was. It is on a Railcore Core XY, so it's tricky to rehome Z.

I have a dumb question regarding resume after power failure..

Does the printer have to re-home? If so, how do you home Z when there's a partial print on the bed?

@deckingman Thanks, I checked all possible screws and they are all tight.

I put acceleration much slower and so far so good with 4 prints. Will keep you posted, that might have been the culprit!!

Thanks!

Oh and running 3.4.5

Hello ladies and gents. Having a weird issue..

My Railcore is skipping steps once in a while. Not all the time. I can do 3-4 prints, no issues, then the next one, it will skip steps a bunch up to the point where either X or Y will hit the sides.

Specs:

Railcore II 300ZL
LDO motors
Nova Hotend 100W 0.5mm starforged
0.2mm layer height
200mm/s print speed
500mm/s non print moves
Duet 3 6HC

my config.g:

; Configuration file for Duet 3 (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.1.3 on Mon Jul 06 2020 18:01:42 GMT-0400 (EDT)

; General preferences
G90                                                ; send absolute coordinates...
M83                                                ; ...but relative extruder moves
M550 P"Railcore SCR"                               ; set printer name
M669 K1                                            ; select CoreXY mode
M918 P1 E4 F2000000                                ; configure direct-connect display

; Network
M552 P192.168.1.45 S1                              ; enable network and acquire dynamic address fixed IP
M553 P255.255.0.0								   ; Set netmask
M554 P192.168.1.254								   ; set gateway
M586 P0 S1                                         ; enable HTTP
M586 P1 S0                                         ; disable FTP
M586 P2 S0                                         ; disable Telnet

; Drives
M569 P0.0 S0                                       ; physical drive 0.0 goes backwards
M569 P0.1 S1                                       ; physical drive 0.1 goes backwards
M569 P0.2 S1                                       ; physical drive 0.2 goes forwards
M569 P0.3 S1									   ; physical drive 0.3 goes forwards
M569 P0.4 S1									   ; physical drive 0.4 goes forwards
M569 P0.5 S1                                       ; physical drive 0.5 goes forwards
M584 X0.1 Y0.0 Z0.2:0.3:0.4 E0.5                   ; set drive mapping
M350 X16 Y16 Z16 E16 I1                            ; configure microstepping with interpolation
M92 X200.00 Y200.00 Z1600.00 E839                  ; set steps per mm
M566 X400 Y400 Z100 E1500                          ; set maximum instantaneous speed changes (mm/min)
M203 X30000.00 Y30000.00 Z1100.00 E3600.00         ; set maximum speeds (mm/min)
M201 X6000.00 Y6000.00 Z200.00 E5000.00            ; set accelerations (mm/s^2)
M906 X1600 Y1600 Z1000 E1200 I60                   ; set motor currents (mA) and motor idle factor in per cent
M84 S30                                            ; Set idle timeout


;Leadscrew locations
M671 X-10:-10:333  Y22.5:277.5:150 S15  ;Front left, Rear Left, Right  S15 is the max correction - measure your own offsets, to the bolt for the yoke of each leadscrew

; Axis Limits
M208 X0 Y0 Z0 S1                                   ; set axis minima
M208 X300 Y290 Z310 S0                             ; set axis maxima

; Endstops
M574 X1 S1 P"io1.in"                               ; configure active-high endstop for low end on X via pin io1.in
M574 Y1 S1 P"io2.in"                               ; configure active-high endstop for low end on Y via pin io2.in

; Z-Probe
M558 P9 C"io7.in" H4 R1 F200 T6000 A5 S0.02 B1     ; set Z probe type to bltouch and the dive height + speeds
M950 S0 C"io7.out"                                 ; create servo pin 0 for BLTouch
G31 X-2 Y42 Z2.04 P25 							   ; Probe position and offset

; Mesh Grid
M557 X5:270 Y5:295 S20                             ; define mesh grid

; Paneldue 5i config
M575 P1 B57600 S1 								   ; Set auxiliary serial port baud rate and require checksum (for PanelDue)

; Filament monitor
M591 D0 P5 C"io3.in" R1:500 E10 S0

; Heaters
M308 S0 P"temp1" Y"thermistor" T100000 B3950       		; configure sensor 0 as PT1000 on pin temp1
M950 H0 C"out0" T0                                 		; create bed heater output on out0 and map it to sensor 0 
M140 H0                                            		; map heated bed to heater 0
M308 S1 P"temp0" Y"pt1000"    							; configure sensor 1 as pt1000 on pin temp0 (old: T100000 B4725 C7.06e-8)
M950 H1 C"out1" T1                               		; create nozzle heater output on out1 and map it to sensor 1 
M570 H1 P5 T15 S180				                        ; Hot end may be a little slow to heat up so allow it 180 seconds
M143 H1 S500											; max temp for the hotend
M143 H0 S110											; max temp for the bed


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

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


; Miscellaneous
; M572 D0 S0.02
M501											   ; load config-override.g
M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss
T0                                                 ; select first tool
M106 P1 S0										   ; Turn off parts fan on boot
G29 S0 P"heightmap.csv" 						   ; Load Bed leveling

As far as I can tell, there is no loose wires. Motors get hot, but not so much that it's uncomfortable to hold them. Also, does this on long or short prints. Failing prints do tend to have longer moves from what I noticed.

Printer is on a battery backup. same thing without.

Anyone has a clue?

@MintyTrebor Sorry for the late reply, I was away!

Running Mac os Ventura 13.1 on multiple different computers.

I have the same issue on 2 different printers (Duet 3 6HC and Duet 3 mini 5+) both running 3.4.5

I'll try a different browser and let you know.

@Phaedrux I did, on 2 machines.

Running 3.4.5 on both. Duet 3 and Duet 3 mini 5+.

I get a file missing when i start release manager. (check image)

Anyone with same issue?

@sgk Make sure you do a G28 AFTER you play with the bed leveling, but before you do G29/G32. ALWAYS do a G28 first, as it denotes the start position for the sensor. That's why your heatmap seems all red/orange.

I wish there was a "completed" state that way I could get a message sent when the printer goes to that state.