@Phaedrux said in Mesh bed compensation warning:

Try moving your homing position to place the probe at the center of the bed.

Are you using G32 (bed.g) to start the mesh probing?

Ok for homing position.
I use G29.

@Phaedrux said in Mesh bed compensation warning:

Have you redone your mesh lately?

Five minutes ago.

homez.g homeall.g config.g bed.g

hello everyone, I'm having a problem probing my bed with a smart ir on a duet2 wifi.

Warning: the height map has a substantial Z offset. Suggest use Z-probe to establish Z=0 datum, then re-probe the mesh.

I use this version:
Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 2.05.1 (2020-02-09b1)

This is the portion of config.g with endstops and z-probe:

; Endstops
M574 X1 Y1 S1 ;
M574 Z1 S2 ;

; Z-Probe
M558 P1 H5 F300 T4800 ;
M557 X10:270 Y0:235 P07:07 ;
G31 P500 X4 Y-0.5 Z2.45 ;

In homez.g:
G91 ;
G1 H2 Z5 F4800 ;
G90
G1 X20 Y0 F4800 ; go to first probe point
G30 ;

Where could be the origin of this warning?

@dc42 said in Runoff 3.3V on expansion socket:

My impression is that you have purchased one of the few relay boards that doesn't have optically isolated inputs; but I can't be certain form the photos you have posted. Please provide a link to the datasheet or seller's page for that relay module.

Hello, I finally choosed a simple relay board optically isolated as written in other posts here.

BTW, this is the link of the object in aliexpress

https://it.aliexpress.com/item/32974992635.html?spm=a2g0s.9042311.0.0.27424c4dYNXVMk

Hi to all, I bought a pcb relay board as this attached. It runs ok, but I'd like to runoff the psu (so the relais) at end of a print job or remotely instead of by a hand switch on 3.3V wire.
I check with M81 but it seems that the only way to runoff the relais is putting off the 3.3V. Is there a way, via gcode, to cut 3.3V on expansion socket?
Anyway, I don't know why this board wants also the ps_on wire.

Any ideas?

@droftarts said in Runout filament sensor - microswitch:

@bigsub Your command looks correct for an active low TriangleLabs filament runout sensor.

I'd suspect poor wiring or interference is giving you false triggering. Because the Duet is expecting 0V when filament is present and the switch is triggered, any voltage that is being picked up makes it look like the switch has been released, and there's no filament present. Check the wiring for bad contacts, loose and/or poorly crimped crimps, or the wires running close to other high current wires, eg stepper motor wires. It's also possible that the filament bumping over a particularly sensitive microswitch switch is generating enough movement to create a false reading occasionally.

Ian

Ok many thanks, I'll check.

@dc42 said in Runout filament sensor - microswitch:

@bigsub said in Runout filament sensor - microswitch:

The problem is, that also if the filament is present (reported by M591 D0), the printing job is paused as there isn't filament.

Is it paused immediately, or after some time?

It's paused after some instructions printed.

Hello everyone,
I'm having a problem with a runout filament sensor. I'm using a Trianglelab.
I use M591 and I connect it to E0 endstop:

M591 D0 P2 C3 S1

I don't specify anything in M574 for E0 endstop.
The problem is, that also if the filament is present (reported by M591 D0), the printing job is paused as there isn't filament.
After pause, if I check with M591 D0, it says filament present.
Another info, I'm running 2.05.1 firmware on duet 2 wifi.

What could be the problem?

Hello everyone,
I'm trying to setup a trianglelab runout filament sensor. This is a normal microswitch with 3 wires and LOW for presence and HIGH for absent.

So I setup M591 in this way on the config.g (I use E0 endstop)

M591 D0 P2 C3 S1

It seems to work perfectly but sometime it goes unexpectedly in pause with runout message.

I check the wires and endstop state but I don't able to find the solution. Is it necessary to configure other files?