Hi together,
may i introduce...
Since nearly 6 months I am working on this machine and its still "work in progress"

Build: Hypercube HEVO, Dual Z, 300x300x400
Board: DUET3 + SBC Raspberry Pi4
Firmware: RRF3 Beta 3
Extruder: Zesty Nimble
Z-Sensor: Orion Piezo
X-Min, Y-Min: optical Endstops
DHT22: for chamber temperature

Webcam: RPI-Cam and RPICamControl -> https://elinux.org/RPi-Cam-Web-Interface

Power Control and Monitoring: Sonoff POWR2 with Tasmonta 8.0.1

LEDs: Control WS2812B RGB LEDs with an ESP8266 over WiFi! -> https://github.com/Aircoookie/WLED

Dashboard: Homeassistant

same topic,
I disconnected the SBC for the moment to have a more reliable environment.
hope this will be fixed soon.

i am using the Fisheye Raspicam together with "RPICamcontrol"-Software on the same RPi.
works so far...

if your probe is on the left, shouldn't the X-offset be negative?

@elliott-griffiths it’s frustrating.
After setting it up from scratch.
Means... downloading the current image, and setup a new sd...
still issues.
Stand-alone with SD, no problem.

But the SBC version.
After starting with the new image the sbc connects to the duet. So far so good.
DWC is able to acces the virtual SD with all folders.
But after uploading the config.g to the sys folder and rebooting,
the system has problems to access to the virtual SD with a lot of error messages .
It’s not able to read and access any folder of the virtual SD

It’s so frustrating

I made 2 print with 5 hours print time each, with the SBC connected.

the system is updated to the RC7 and the new DSF Framework, DWC

the system runs stable, no reconnects anymore.

looks good so far for me.

have to test some macros and other topics were i had issues...

thanks to @dc42 , @chrishamm

@droftarts that’s why i am asking the question in this firmware-beta category my friend

@PCR i know, that’s my workaround

As is understood G29 on an SBC setup needs a /sys/mesh.g because the command will be handled by the DWC .

I am using a SBC setup, therefore it would be great to understand how the mesh.g should be used.

I didnt found any doc's or infos.

@chrishamm i am using a piezo and i had never used deployprobe/retracprobe.

the mesh-grid size in this config is only for testing because of the described issue.

;M550 P"hypercube" ; set printer name
;M552 S1 ; enable network
;M586 P1 S1 ; Enable FTP
;M586 P2 S1 ; Enable Telnet

; General preferences
M555 P2 ; Set Marlin-style output
G21 ; Set dimensions to millimetres
G90 ; Send absolute coordinates...
M83 ; ...but relative extruder moves
M667 S1 ; select CoreXY mode

; Debugging
;M111 S0 ; Debug off
;M929 P"eventlog.txt" S1 ; Start logging to file eventlog.txt

; Drives
M569 P0.0 S1 ; physical drive 0.0 goes forwards
M569 P0.1 S1 ; physical drive 0.1 goes forwards
M569 P0.2 S1 ; physical drive 0.2 goes forwards
M569 P0.3 S1 ; physical drive 0.2 goes forwards
M569 P0.4 S1 ; physical drive 0.4 goes forwards
M584 X0.0 Y0.1 Z0.2:0.3 E0.4 ; set drive mapping

M671 X-50:330 Y150:150 F2 S2 ; leadscrews at left and right of X axis
M208 X0:290 Y0:275

M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation

M92 X80.00 Y80.00 Z400.00 E2700 ; set steps per mm (E1800 für Nimble v")
M566 X500.00 Y500.00 Z400.00 E100.00 ; set maximum instantaneous speed changes (mm/min)
M203 X18000.00 Y18000.00 Z2000.00 E6000 ; set maximum speeds (mm/min) (E100 war gut)
M201 X500.00 Y500.00 Z500 E500.00 ; set accelerations (mm/s^2)
M906 X900 Y900 Z750 E500 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

; Axis Limits
M208 X-10 Y-30 Z0 S1 ; set axis minima
M208 X280 Y280 Z350 S0 ; set axis maxima

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

M574 Z1 S2 ; configure Z-probe endstop for low end on Z

; Z-Probe
M558 P5 I0 R1 C"!io3.in+io3.out" H5 F320 T3000 ; set Z probe type to effector and the dive height + speeds
G31 P1000 X0 Y0 Z-0.05 ; set Z probe trigger value, offset and trigger height (old Z-0.15)
M557 X45:235 Y45:235 S190 ; define mesh grid

;M557 X15:265 Y15:265 S250 ; define mesh grid

; Heaters
M140 H0 ; map heated bed to heater 0
M308 S0 P"temp0" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin temp0
M950 H0 C"out0" T0 ; create bed heater output on out0 and map it to sensor 0
M143 H0 S95. ; set temperature limit for heater 0 to 120C
M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit

M308 S1 P"temp1" Y"thermistor" T100000 B4725 ; configure sensor 1 as thermistor on pin temp1
M950 H1 C"out1" T1 ; create nozzle heater output on out1 and map it to sensor 1
M143 H1 S260 ; set temperature limit for heater 1 to 260C
M307 H1 B0 S1.00 ; disable bang-bang mode for the nozzle heater and set PWM limit

M308 S10 P"spi.cs1" Y"dht22" A"Chamber Temp" ; define DHT22 temperature sensor
M308 S11 P"S10.1" Y"dhthumidity" A"Chamber Hum[%]" ; Attach DHT22 humidity sensor
M308 S2 A"MCU-Temp" Y"mcu-temp" ; Create Sensor for MCU-Temp

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

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

; Miscellaneous
M915 X Y S2 F0 R0 ; stall detection on X,Y
M302 S150 R150 ; Allow extrusion

M575 P1 S1 B57600 ; PanelDue

M501
T0
;G29 S1 ; load saved parameters from non-volatile

Hi,
@chrishamm

after updating to DWC/RRF 3.1.1 the height map will not be saved if you use the menu item from the DWC.
I have to enter G29 S3 in the console in addition to save the map.
....bug or feature?

this is going in a similar direction

https://forum.duet3d.com/topic/14134/duet-buddy-a-proof-of-concept-remote-monitor

@dc42 yep we can close it, thanks

@dc42 seems my problem was the config-override.g. My parameters out of the config-override where not loaded.

@dc42 yes it has

@gtj0 yep