3.1.0 it came up as

@lifeform Some ideas: Do these issues also appear if you do not activate serial communication on Duet, i.e. comment out M575? Is your PanelDue inside a case that by chance might put pressure on the screen? This might result in random taps. Also can you please restate your current issues. I feel they changed along the course of this thread and I lost track what is still left.

Chimera clone, Volcano clone hot end. The extruder is a BMG clone. The printer is a highly modified Creality S5

@Phaedrux Yes

You can make cross roller bearings with a 3d printer. I've made a few with steel rollers and they came out nicely. Of course they're not going to compare to metal ones so their usage is a bit questionable. Might be just easier to print mounts for normal ball bearings since you're not going to overload them anyway. https://www.instructables.com/Create-a-Parametric-3d-printable-Slew-Bearing-With/

Feel free to post what you've changed as a sanity check. Once you see your existing M584 command in config.g it should be apparent on how it works. Choosing a new drive letter and assigning a driver number to it.

@Phaedrux it seems so far...

@bdelia It looks like it is wired for 12V. Connecting to 24V makes 4x the power, that is why You had to lower the max pwm so much.

That's an odd one. Have you gone back to 3.1.1 to confirm it works properly there? (sorry for having to jump through so many hoops!) If you send M98 P"config.g" in beta 4 do you see any error messages? Can you send M906 by itself when the motor is skipping to verify what the current is actually set to at that time?

@chrishamm I'm not sure that I can be helpful here. I'm not able to identify any strange things here, but my filter on my "/dev/input/eyes" not traind for DCS logs. So here is the full dump. The timezone of the pi is "GMT" -- Logs begin at Tue 2020-12-01 17:17:01 GMT, end at Tue 2020-12-01 18:50:33 GMT. -- Dec 01 17:17:04 Blimy systemd[1]: Started Duet Control Server. Dec 01 17:17:08 Blimy DuetControlServer[392]: Duet Control Server v3.2.0-beta4 Dec 01 17:17:08 Blimy DuetControlServer[392]: Written by Christian Hammacher for Duet3D Dec 01 17:17:08 Blimy DuetControlServer[392]: Licensed under the terms of the GNU Public License Version 3 Dec 01 17:17:10 Blimy DuetControlServer[392]: [info] Settings loaded Dec 01 17:17:10 Blimy DuetControlServer[392]: [info] Environment initialized Dec 01 17:17:10 Blimy DuetControlServer[392]: [info] Connection to Duet established Dec 01 17:17:10 Blimy DuetControlServer[392]: [info] IPC socket created at /var/run/dsf/dcs.sock Dec 01 17:17:11 Blimy DuetControlServer[392]: [info] Starting macro file config.g on channel Trigger Dec 01 17:17:12 Blimy DuetControlServer[392]: [warn] Discarded msg src=1 typ=4510 RID=4095 exp 1 Dec 01 17:17:13 Blimy DuetControlServer[392]: [error] M584: Response timeout: CAN addr 1, req type 6042, RID=1 Dec 01 17:17:13 Blimy DuetControlServer[392]: [warn] Discarded msg src=1 typ=4510 RID=4095 exp 2 Dec 01 17:17:14 Blimy DuetControlServer[392]: [error] M350: Response timeout: CAN addr 1, req type 6042, RID=2 Dec 01 17:17:14 Blimy DuetControlServer[392]: [warn] Discarded msg src=1 typ=4510 RID=4095 exp 3 Dec 01 17:17:15 Blimy DuetControlServer[392]: [warn] Discarded msg src=1 typ=4510 RID=4095 exp 4 Dec 01 17:17:15 Blimy DuetControlServer[392]: [error] M92: Response timeout: CAN addr 1, req type 6042, RID=3 Dec 01 17:17:16 Blimy DuetControlServer[392]: [error] M906: Response timeout: CAN addr 1, req type 6043, RID=4 Dec 01 17:17:16 Blimy DuetControlServer[392]: [warn] Discarded msg src=1 typ=4510 RID=4095 exp 5 Dec 01 17:17:17 Blimy DuetControlServer[392]: [warn] Lost connection to Duet (Timeout while waiting for transfer ready pin) Dec 01 17:17:17 Blimy DuetControlServer[392]: [info] Connection to Duet established Dec 01 17:17:17 Blimy DuetControlServer[392]: [error] M591: Response timeout: CAN addr 1, req type 6046, RID=5 Dec 01 17:17:17 Blimy DuetControlServer[392]: [info] Starting macro file config-override.g on channel Trigger Dec 01 17:17:17 Blimy DuetControlServer[392]: [info] Finished macro file config-override.g Dec 01 17:17:17 Blimy DuetControlServer[392]: [warn] M307: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to Dec 01 17:17:17 Blimy DuetControlServer[392]: [warn] M307: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to Dec 01 17:17:17 Blimy DuetControlServer[392]: [info] Finished macro file config.g Dec 01 17:43:29 Blimy DuetControlServer[392]: [info] System time has been changed Dec 01 17:43:30 Blimy DuetControlServer[392]: [info] Starting macro file 0:/macros/20_Z-Level on channel HTTP Dec 01 17:43:30 Blimy DuetControlServer[392]: [info] Starting macro file bed.g on channel HTTP Dec 01 17:43:30 Blimy DuetControlServer[392]: [info] Starting macro file homeall.g on channel HTTP Dec 01 17:43:30 Blimy DuetControlServer[392]: [info] Starting macro file 0:/sys/homex.g on channel HTTP Dec 01 17:43:53 Blimy DuetControlServer[392]: [info] Finished macro file 0:/sys/homex.g Dec 01 17:43:53 Blimy DuetControlServer[392]: [info] Starting macro file 0:/sys/homey.g on channel HTTP Dec 01 17:44:01 Blimy DuetControlServer[392]: [info] Finished macro file 0:/sys/homey.g Dec 01 17:44:01 Blimy DuetControlServer[392]: [info] Starting macro file 0:/sys/homez.g on channel HTTP Dec 01 17:44:02 Blimy DuetControlServer[392]: [info] Starting macro file deployprobe.g on channel HTTP Dec 01 17:44:03 Blimy DuetControlServer[392]: [info] Finished macro file deployprobe.g Dec 01 17:44:05 Blimy DuetControlServer[392]: [info] Starting macro file retractprobe.g on channel HTTP Dec 01 17:44:05 Blimy DuetControlServer[392]: [info] Finished macro file retractprobe.g Dec 01 17:44:07 Blimy DuetControlServer[392]: [info] Starting macro file deployprobe.g on channel HTTP Dec 01 17:44:07 Blimy DuetControlServer[392]: [info] Finished macro file deployprobe.g Dec 01 17:44:12 Blimy DuetControlServer[392]: [info] Starting macro file retractprobe.g on channel HTTP Dec 01 17:44:12 Blimy DuetControlServer[392]: [info] Finished macro file retractprobe.g Dec 01 17:44:13 Blimy DuetControlServer[392]: [info] Finished macro file 0:/sys/homez.g Dec 01 17:44:13 Blimy DuetControlServer[392]: [info] Finished macro file homeall.g Dec 01 17:44:16 Blimy DuetControlServer[392]: [info] Starting macro file deployprobe.g on channel HTTP Dec 01 17:44:16 Blimy DuetControlServer[392]: [info] Finished macro file deployprobe.g Dec 01 17:44:16 Blimy DuetControlServer[392]: [info] Finished macro file deployprobe.g -- Logs begin at Tue 2020-12-01 17:17:01 GMT, end at Tue 2020-12-01 18:50:33 GMT. -- Dec 01 17:17:04 Blimy systemd[1]: Started Duet Control Server. Dec 01 17:17:08 Blimy DuetControlServer[392]: Duet Control Server v3.2.0-beta4 Dec 01 17:17:08 Blimy DuetControlServer[392]: Written by Christian Hammacher for Duet3D Dec 01 17:17:08 Blimy DuetControlServer[392]: Licensed under the terms of the GNU Public License Version 3 Dec 01 17:17:10 Blimy DuetControlServer[392]: [info] Settings loaded Dec 01 17:17:10 Blimy DuetControlServer[392]: [info] Environment initialized Dec 01 17:17:10 Blimy DuetControlServer[392]: [info] Connection to Duet established Dec 01 17:17:10 Blimy DuetControlServer[392]: [info] IPC socket created at /var/run/dsf/dcs.sock Dec 01 17:17:11 Blimy DuetControlServer[392]: [info] Starting macro file config.g on channel Trigger Dec 01 17:17:12 Blimy DuetControlServer[392]: [warn] Discarded msg src=1 typ=4510 RID=4095 exp 1 Dec 01 17:17:13 Blimy DuetControlServer[392]: [error] M584: Response timeout: CAN addr 1, req type 6042, RID=1 Dec 01 17:17:13 Blimy DuetControlServer[392]: [warn] Discarded msg src=1 typ=4510 RID=4095 exp 2 Dec 01 17:17:14 Blimy DuetControlServer[392]: [error] M350: Response timeout: CAN addr 1, req type 6042, RID=2 Dec 01 17:17:14 Blimy DuetControlServer[392]: [warn] Discarded msg src=1 typ=4510 RID=4095 exp 3 Dec 01 17:17:15 Blimy DuetControlServer[392]: [warn] Discarded msg src=1 typ=4510 RID=4095 exp 4 Dec 01 17:17:15 Blimy DuetControlServer[392]: [error] M92: Response timeout: CAN addr 1, req type 6042, RID=3 Dec 01 17:17:16 Blimy DuetControlServer[392]: [error] M906: Response timeout: CAN addr 1, req type 6043, RID=4 Dec 01 17:17:16 Blimy DuetControlServer[392]: [warn] Discarded msg src=1 typ=4510 RID=4095 exp 5 Dec 01 17:17:17 Blimy DuetControlServer[392]: [warn] Lost connection to Duet (Timeout while waiting for transfer ready pin) Dec 01 17:17:17 Blimy DuetControlServer[392]: [info] Connection to Duet established Dec 01 17:17:17 Blimy DuetControlServer[392]: [error] M591: Response timeout: CAN addr 1, req type 6046, RID=5 Dec 01 17:17:17 Blimy DuetControlServer[392]: [info] Starting macro file config-override.g on channel Trigger Dec 01 17:17:17 Blimy DuetControlServer[392]: [info] Finished macro file config-override.g Dec 01 17:17:17 Blimy DuetControlServer[392]: [warn] M307: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to Dec 01 17:17:17 Blimy DuetControlServer[392]: [warn] M307: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to Dec 01 17:17:17 Blimy DuetControlServer[392]: [info] Finished macro file config.g Dec 01 17:43:29 Blimy DuetControlServer[392]: [info] System time has been changed Dec 01 17:43:30 Blimy DuetControlServer[392]: [info] Starting macro file 0:/macros/20_Z-Level on channel HTTP Dec 01 17:43:30 Blimy DuetControlServer[392]: [info] Starting macro file bed.g on channel HTTP Dec 01 17:43:30 Blimy DuetControlServer[392]: [info] Starting macro file homeall.g on channel HTTP Dec 01 17:43:30 Blimy DuetControlServer[392]: [info] Starting macro file 0:/sys/homex.g on channel HTTP Dec 01 17:43:53 Blimy DuetControlServer[392]: [info] Finished macro file 0:/sys/homex.g Dec 01 17:43:53 Blimy DuetControlServer[392]: [info] Starting macro file 0:/sys/homey.g on channel HTTP Dec 01 17:44:01 Blimy DuetControlServer[392]: [info] Finished macro file 0:/sys/homey.g Dec 01 17:44:01 Blimy DuetControlServer[392]: [info] Starting macro file 0:/sys/homez.g on channel HTTP Dec 01 17:44:02 Blimy DuetControlServer[392]: [info] Starting macro file deployprobe.g on channel HTTP Dec 01 17:44:03 Blimy DuetControlServer[392]: [info] Finished macro file deployprobe.g Dec 01 17:44:05 Blimy DuetControlServer[392]: [info] Starting macro file retractprobe.g on channel HTTP Dec 01 17:44:05 Blimy DuetControlServer[392]: [info] Finished macro file retractprobe.g Dec 01 17:44:07 Blimy DuetControlServer[392]: [info] Starting macro file deployprobe.g on channel HTTP Dec 01 17:44:07 Blimy DuetControlServer[392]: [info] Finished macro file deployprobe.g Dec 01 17:44:12 Blimy DuetControlServer[392]: [info] Starting macro file retractprobe.g on channel HTTP Dec 01 17:44:12 Blimy DuetControlServer[392]: [info] Finished macro file retractprobe.g Dec 01 17:44:13 Blimy DuetControlServer[392]: [info] Finished macro file 0:/sys/homez.g Dec 01 17:44:13 Blimy DuetControlServer[392]: [info] Finished macro file homeall.g Dec 01 17:44:16 Blimy DuetControlServer[392]: [info] Starting macro file deployprobe.g on channel HTTP Dec 01 17:44:16 Blimy DuetControlServer[392]: [info] Finished macro file deployprobe.g Dec 01 17:44:16 Blimy DuetControlServer[392]: [info] Starting macro file deployprobe.g on channel HTTP Dec 01 17:44:16 Blimy DuetControlServer[392]: [info] Finished macro file deployprobe.g Dec 01 17:44:17 Blimy DuetControlServer[392]: [info] Starting macro file retractprobe.g on channel HTTP Dec 01 17:44:17 Blimy DuetControlServer[392]: [info] Finished macro file retractprobe.g Dec 01 17:44:22 Blimy DuetControlServer[392]: [info] Starting macro file deployprobe.g on channel HTTP Dec 01 17:44:23 Blimy DuetControlServer[392]: [info] Finished macro file deployprobe.g Dec 01 17:44:24 Blimy DuetControlServer[392]: [info] Starting macro file retractprobe.g on channel HTTP Dec 01 17:44:24 Blimy DuetControlServer[392]: [info] Finished macro file retractprobe.g Dec 01 17:44:29 Blimy DuetControlServer[392]: [info] Starting macro file deployprobe.g on channel HTTP Dec 01 17:44:29 Blimy DuetControlServer[392]: [info] Finished macro file deployprobe.g Dec 01 17:44:30 Blimy DuetControlServer[392]: [info] Starting macro file retractprobe.g on channel HTTP Dec 01 17:44:30 Blimy DuetControlServer[392]: [info] Finished macro file retractprobe.g Dec 01 17:44:32 Blimy DuetControlServer[392]: [info] Finished macro file bed.g Dec 01 17:44:32 Blimy DuetControlServer[392]: [info] Finished macro file 0:/macros/20_Z-Level Dec 01 17:44:49 Blimy DuetControlServer[392]: [info] Selected file /opt/dsf/sd/gcodes/CFFFP_Stringing.gcode Dec 01 17:44:49 Blimy DuetControlServer[392]: [info] Starting file print Dec 01 17:44:49 Blimy DuetControlServer[392]: [info] Starting macro file tpre0.g on channel File Dec 01 17:44:49 Blimy DuetControlServer[392]: [info] Finished macro file tpre0.g Dec 01 17:44:49 Blimy DuetControlServer[392]: [info] Starting macro file tpost0.g on channel File Dec 01 17:44:49 Blimy DuetControlServer[392]: [info] Finished macro file tpost0.g Dec 01 17:45:55 Blimy DuetControlServer[392]: [info] Starting macro file homeall.g on channel File Dec 01 17:45:55 Blimy DuetControlServer[392]: [info] Starting macro file 0:/sys/homex.g on channel File Dec 01 17:46:14 Blimy DuetControlServer[392]: [info] Finished macro file 0:/sys/homex.g Dec 01 17:46:14 Blimy DuetControlServer[392]: [info] Starting macro file 0:/sys/homey.g on channel File Dec 01 17:46:22 Blimy DuetControlServer[392]: [info] Finished macro file 0:/sys/homey.g Dec 01 17:46:22 Blimy DuetControlServer[392]: [info] Starting macro file 0:/sys/homez.g on channel File Dec 01 17:46:24 Blimy DuetControlServer[392]: [info] Starting macro file deployprobe.g on channel File Dec 01 17:46:24 Blimy DuetControlServer[392]: [info] Finished macro file deployprobe.g Dec 01 17:46:25 Blimy DuetControlServer[392]: [info] Starting macro file retractprobe.g on channel File Dec 01 17:46:25 Blimy DuetControlServer[392]: [info] Finished macro file retractprobe.g Dec 01 17:46:27 Blimy DuetControlServer[392]: [info] Starting macro file deployprobe.g on channel File Dec 01 17:46:27 Blimy DuetControlServer[392]: [info] Finished macro file deployprobe.g Dec 01 17:46:32 Blimy DuetControlServer[392]: [info] Starting macro file retractprobe.g on channel File Dec 01 17:46:32 Blimy DuetControlServer[392]: [info] Finished macro file retractprobe.g Dec 01 17:46:33 Blimy DuetControlServer[392]: [info] Finished macro file 0:/sys/homez.g Dec 01 17:46:33 Blimy DuetControlServer[392]: [info] Finished macro file homeall.g Dec 01 17:46:34 Blimy DuetControlServer[392]: [info] Height map loaded from file heightmap.csv Dec 01 17:47:48 Blimy DuetControlServer[392]: [info] Starting macro file pause.g on channel HTTP Dec 01 17:47:48 Blimy DuetControlServer[392]: [info] Job has been paused at byte 5145, reason User Dec 01 17:47:50 Blimy DuetControlServer[392]: [info] Finished macro file pause.g Dec 01 17:54:17 Blimy DuetControlServer[392]: [info] Starting macro file tfree0.g on channel HTTP Dec 01 17:54:17 Blimy DuetControlServer[392]: [info] Finished macro file tfree0.g Dec 01 18:01:02 Blimy DuetControlServer[392]: [info] Aborted job file Dec 01 18:01:03 Blimy DuetControlServer[392]: [warn] Emergency stop Dec 01 18:01:03 Blimy DuetControlServer[392]: [warn] Resetting controller Dec 01 18:01:03 Blimy DuetControlServer[392]: [info] Application has shut down Dec 01 18:01:03 Blimy systemd[1]: duetcontrolserver.service: Succeeded. Dec 01 18:01:08 Blimy systemd[1]: duetcontrolserver.service: Service RestartSec=5s expired, scheduling restart. Dec 01 18:01:08 Blimy systemd[1]: duetcontrolserver.service: Scheduled restart job, restart counter is at 1. Dec 01 18:01:08 Blimy systemd[1]: Stopped Duet Control Server. Dec 01 18:01:08 Blimy systemd[1]: Started Duet Control Server. Dec 01 18:01:09 Blimy DuetControlServer[5172]: Duet Control Server v3.2.0-beta4 Dec 01 18:01:09 Blimy DuetControlServer[5172]: Written by Christian Hammacher for Duet3D Dec 01 18:01:09 Blimy DuetControlServer[5172]: Licensed under the terms of the GNU Public License Version 3 Dec 01 18:01:10 Blimy DuetControlServer[5172]: [info] Settings loaded Dec 01 18:01:10 Blimy DuetControlServer[5172]: [info] Environment initialized Dec 01 18:01:11 Blimy DuetControlServer[5172]: [info] Connection to Duet established Dec 01 18:01:11 Blimy DuetControlServer[5172]: [info] IPC socket created at /var/run/dsf/dcs.sock Dec 01 18:01:11 Blimy DuetControlServer[5172]: [info] Starting macro file config.g on channel Trigger Dec 01 18:01:13 Blimy DuetControlServer[5172]: [warn] Discarded msg src=1 typ=4510 RID=4095 exp 1 Dec 01 18:01:14 Blimy DuetControlServer[5172]: [warn] Discarded msg src=1 typ=4510 RID=4095 exp 2 Dec 01 18:01:14 Blimy DuetControlServer[5172]: [error] M584: Response timeout: CAN addr 1, req type 6042, RID=1 Dec 01 18:01:15 Blimy DuetControlServer[5172]: [warn] Discarded msg src=1 typ=4510 RID=4095 exp 3 Dec 01 18:01:15 Blimy DuetControlServer[5172]: [error] M350: Response timeout: CAN addr 1, req type 6042, RID=2 Dec 01 18:01:16 Blimy DuetControlServer[5172]: [warn] Discarded msg src=1 typ=4510 RID=4095 exp 4 Dec 01 18:01:16 Blimy DuetControlServer[5172]: [error] M92: Response timeout: CAN addr 1, req type 6042, RID=3 Dec 01 18:01:17 Blimy DuetControlServer[5172]: [error] M906: Response timeout: CAN addr 1, req type 6043, RID=4 Dec 01 18:01:17 Blimy DuetControlServer[5172]: [warn] Discarded msg src=1 typ=4510 RID=4095 exp 5 Dec 01 18:01:18 Blimy DuetControlServer[5172]: [warn] Lost connection to Duet (Timeout while waiting for transfer ready pin) Dec 01 18:01:18 Blimy DuetControlServer[5172]: [info] Connection to Duet established Dec 01 18:01:18 Blimy DuetControlServer[5172]: [error] M591: Response timeout: CAN addr 1, req type 6046, RID=5 Dec 01 18:01:18 Blimy DuetControlServer[5172]: [info] Starting macro file config-override.g on channel Trigger Dec 01 18:01:18 Blimy DuetControlServer[5172]: [info] Finished macro file config-override.g Dec 01 18:01:19 Blimy DuetControlServer[5172]: [warn] M307: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted t Dec 01 18:01:19 Blimy DuetControlServer[5172]: [warn] M307: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted t Dec 01 18:01:19 Blimy DuetControlServer[5172]: [info] Finished macro file config.g Dec 01 18:01:39 Blimy DuetControlServer[5172]: [info] Starting macro file tpre0.g on channel HTTP Dec 01 18:01:39 Blimy DuetControlServer[5172]: [info] Finished macro file tpre0.g Dec 01 18:01:39 Blimy DuetControlServer[5172]: [info] Starting macro file tpost0.g on channel HTTP Dec 01 18:02:49 Blimy DuetControlServer[5172]: [info] Finished macro file tpost0.g I have to mention again that systemd sucks. I hope that helps somehow. Cheers, Chriss

@vasparshin said in G30, G32 Issues on Duet WiFi CoreXYU with inductive probe: M558 P5 C"zprobe.in" H5 F600 G31 P999 X0 Y0 Z0.2 ; set Z probe trigger value, offset and trigger height P5 the offset of X0 Y0 can not be correct for a npn probe. the probe has to have an offset also you are probing very fast Switch to P8, but also consider lowering the probing speed. can you try with 3.1.1? that is the latest stable.

that make zero sense. G28 Z should establish Z=0 using G30. G29 getting a different offset would mean that the trigger point is different.

Works perfectly now https://youtu.be/tdl2iDNiC9Q What did the line "G1 Z15.0 F1000; short move" that has now been removed? Btw, I think it's really remarkable that you can remember all those codes

Thanks, the printer is not at the office, I'll test tomorrow, and post the results.

@astrn said in Does M574 S4 work ?: I wonder if this one works now? I encountered a similar problem with S4 command on my triple motor Z axis bed. I have tested M574 X1 S4 on a Duet WiFi with 3 X motors connected, and it is working as intended.

@alankilian said in Inconsistent results with optical encoder wheel filament sensor: @JohnOCFII said in Inconsistent results with optical encoder wheel filament sensor: I figured out my issue with non-movement related false alarms Gravity sucks! Indeed! I'ts been a really fun ride watching you build/diagnose/deal-with-it and then show success with this project. Happy to share. I figure someone out there might benefit, so why not share? Thanks for sharing your journey with us housebound folks. I'd be nowhere without you and @arhi and of course, the great design from @fractalengineer!

Oops.. my bad... I gave the command m997 S1 on the panaldue... Will try again tomorrow

sudden drops or spikes indicate a wiring problem. check the crimping on the cable. or move the cables by hand

retractprobe.g homeall.g deployprobe.g config.g bed.g Thank you

@dc42 Thank you! Helps a lot. Really appreciate the fast answers

@dc42 It's like you can read my mind! I'll update as soon as I can - still on beta3.2. In case anyone is following this thread, this is implemented by - G1 H1 E moves (stopping on motor stall).

here are my heater definitions in config.g. Note from the M122 above it states "Heater 1 is on".. but Heater 1 is my Extruder heater, and it was not on.. ;== Extruder Heater ========================== M308 S1 P"20.temp0" Y"thermistor" T500000 B4723 C1.196220e-7 M950 H1 C"20.out0" T1 M307 H1 B0 S1.00 ;== Bed Heater =============================== M308 S0 P"temp0" Y"thermistor" T100000 B3950 M950 H0 C"0.out1" T0 M307 H0 B0 S1.00 M140 H0 M307 H0 A241.5 C374.3 D1.8 S1.0 V24.0 B0 ;== Enclosure Heater ========================= M308 S2 P"temp1" Y"thermistor" T100000 B3950 M950 H2 C"0.out2" T2 M307 H2 B1 A90 C700 D200 M141 H2

N561 Also I think your code N561 is wrong. I think it should be M561: Set Identity Transform

Currently the way to do this would be to use "temperature" as a analogue for either "pressure" or "flow rate" (depending on what you were sensing/controlling) then you would set the pump control as a heater. You would then need to work out what linear analog sensor "temperature" related to what pressure/flow and then set that temperature. No doubt you would need to adjust the PID parameters so that the POID loop worked properly. @DC42 mentioned that an additional complication is that "temperatures <40C are counted as "off" by RRF so you would need to scale your sensor to be working at a higher temperature. I am going to move this into the firmware wishlist category as something to consider for the future.