@fcwilt Thanks for your input.

A couple of comments on the define in a separate file route. This indeed is a clever workaround to having to duplicate values. At the same time it does strike me as kind of ugly (athough less then what I am doing now 🙂 ). I am not a big fan of spreading around configuration commands in different files though.
You reference mesh.g and after searching the forum I have found a couple of mentions about is, but I have never known this file to exist. It also doesn't not seems to be mentioned in the documentation, nor does it appear among the system files on my printer. What am I missing here? Assuming mesh.g is similar to bed.g, it's existence would be essential to use the above technique. Otherwise I wouldn't be able to introduce my own gcode before and after the G29 command.

The global variable route is an option as well. To me this is less 'dirty' then the separate file. I might look into this while/if my idea get implemented.

@phaedrux I reinstalled the files on the SD card and that seems to have fixed the issue. Not sure what was wrong with the card. Thank you.

@chrishamm

Here you go, two more M122 dumps, taken from my laptop connected via USB.

M122<CR> === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3 (2021-06-15 21:44:54) running on Duet WiFi 1.0 or 1.01 Board ID: 08D6M-91AST-L23S4-7JTD0-3S86K-1NX1K Used output buffers: 1 of 24 (20 max) === RTOS === Static ram: 23876 Dynamic ram: 74668 of which 24 recycled Never used RAM 15848, free system stack 134 words Tasks: NETWORK(ready,78.8%,244) HEAT(delaying,0.6%,330) Move(notifyWait,1.5%,303) MAIN(running,18.9%,443) IDLE(ready,0.2%,29), total 100.0% Owned mutexes: WiFi(NETWORK) USB(MAIN) === Platform === Last reset 13:24:33 ago, cause: software Last software reset at 2021-07-31 22:17, reason: User, GCodes spinning, available RAM 15848, slot 0 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 Aux0 errors 0,0,0 Step timer max interval 0 MCU temperature: min 29.4, current 29.7, max 42.3 Supply voltage: min 23.8, current 24.2, max 25.0, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0 Driver 0: position 195079, standstill, SG min/max 0/447 Driver 1: position 195010, standstill, SG min/max 0/464 Driver 2: position 194953, standstill, SG min/max not available Driver 3: position 0, standstill, SG min/max 0/479 Driver 4: position 0, standstill, SG min/max not available Driver 5: position 0 Driver 6: position 0 Driver 7: position 0 Driver 8: position 0 Driver 9: position 0 Driver 10: position 0 Driver 11: position 0 Date/time: 2021-08-01 11:41:44 Cache data hit count 4294967295 Slowest loop: 6.87ms; fastest: 0.17ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Storage === Free file entries: 10 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest read time 1.3ms, write time 0.0ms, max retries 0 === Move === DMs created 83, maxWait 44916359ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 4, completed moves 4, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === AuxDDARing === Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1 Heater 1 is on, I-accum = 0.0 === GCodes === Segments left: 0 Movement lock held by null HTTP is idle in state(s) 0 Telnet is idle in state(s) 0 File is idle in state(s) 0 USB is ready with "M122" 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 Daemon is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty. === Network === Slowest loop: 17.09ms; fastest: 0.00ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions HTTP sessions: 1 of 8 - WiFi - Network state is active WiFi module is connected to access point Failed messages: pending 0, notready 0, noresp 0 WiFi firmware version 1.26-D WiFi MAC address a0:20:a6:16:ec:ed WiFi Vcc 3.36, reset reason Turned on by main processor WiFi flash size 4194304, free heap 22944 WiFi IP address 192.168.178.30 WiFi signal strength -52dBm, mode 802.11n, reconnections 0, sleep mode modem Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0 ok WiFi: Conns: 0:closePending 80, 59705, 192.168.178.27, 1:free, 2:free, 3:free, 4:free, 5:free, 6:free, 7:free WiFi: IP xmit: 44326 recv: 9906 fw: 0 drop: 848 chkerr: 0 lenerr: 0 memerr: 0 rterr: 0 proterr: 0 opterr: 0 err: 0 cachehit: 0 WiFi: TCP xmit: 62257 recv: 24835 fw: 0 drop: 95 chkerr: 0 lenerr: 0 memerr: 0 rterr: 0 proterr: 95 opterr: 0 err: 0 cachehit: 22789 WiFi: MEM UDP_PCB avail: 6 used: 4 max: 4 err: 0 WiFi: MEM TCP_PCB avail: 8 used: 1 max: 8 err: 0 WiFi: MEM TCP_PCB_LISTEN avail: 4 used: 1 max: 1 err: 0 WiFi: MEM TCP_SEG avail: 16 u<DEL>MEM PBUF_REF/ROM avail: 10 used: 0 max: 0 err: 0 WiFi: MEM PBUF_POOL avail: 4 used: 0 max: 0 err: 0 M122 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3 (2021-06-15 21:44:54) running on Duet WiFi 1.0 or 1.01 Board ID: 08D6M-91AST-L23S4-7JTD0-3S86K-1NX1K Used output buffers: 1 of 24 (20 max) === RTOS === Static ram: 23876 Dynamic ram: 74668 of which 24 recycled Never used RAM 15848, free system stack 134 words Tasks: NETWORK(ready,14.2%,243) HEAT(delaying,0.0%,330) Move(notifyWait,0.1%,303) MAIN(running,85.6%,423) IDLE(ready,0.0%,29), total 100.0% Owned mutexes: WiFi(NETWORK) USB(MAIN) === Platform === Last reset 13:39:20 ago, cause: software Last software reset at 2021-07-31 22:17, reason: User, GCodes spinning, available RAM 15848, slot 0 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 Aux0 errors 0,0,0 Step timer max interval 0 MCU temperature: min 29.4, current 30.1, max 30.8 Supply voltage: min 24.1, current 24.2, max 24.5, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0 Driver 0: position 195079, standstill, SG min/max not available Driver 1: position 195010, standstill, SG min/max not available Driver 2: position 194953, standstill, SG min/max not available Driver 3: position 0, standstill, SG min/max not available Driver 4: position 0, standstill, SG min/max not available Driver 5: position 0 Driver 6: position 0 Driver 7: position 0 Driver 8: position 0 Driver 9: position 0 Driver 10: position 0 Driver 11: position 0 Date/time: 2021-08-01 11:56:31 Cache data hit count 4294967295 Slowest loop: 14.32ms; fastest: 0.17ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Storage === Free file entries: 10 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest read time 1.3ms, write time 0.0ms, max retries 0 === Move === DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 4, completed moves 4, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === AuxDDARing === Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1 Heater 1 is on, I-accum = 0.0 === GCodes === Segments left: 0 Movement lock held by null HTTP is idle in state(s) 0 Telnet is idle in state(s) 0 File is idle in state(s) 0 USB is ready with "M122" 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 Daemon is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty. === Network === Slowest loop: 200.67ms; fastest: 0.08ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions HTTP sessions: 1 of 8 - WiFi - Network state is active WiFi module is connected to access point Failed messages: pending 0, notready 0, noresp 1 WiFi firmware version 1.26-D WiFi MAC address a0:20:a6:16:ec:ed WiFi Vcc 3.36, reset reason Turned on by main processor WiFi flash size 4194304, free heap 26096 WiFi IP address 192.168.178.30 WiFi signal strength -54dBm, mode 802.11n, reconnections 0, sleep mode modem Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0 ok WiFi: Conns: 0:free, 1:free, 2:free, 3:free, 4:free, 5:free, 6:free, 7:free WiFi: IP xmit: 57117 recv: 25483 fw: 0 drop: 864 chkerr: 0 lenerr: 0 memerr: 0 rterr: 0 proterr: 0 opterr: 0 err: 0 cachehit: 0 WiFi: TCP xmit: 7106 recv: 39465 fw: 0 drop: 95 chkerr: 0 lenerr: 0 memerr: 0 rterr: 0 proterr: 95 opterr: 0 err: 0 cachehit: 36781 WiFi: MEM UDP_PCB avail: 6 used: 4 max: 4 err: 0 WiFi: MEM TCP_PCB avail: 8 used: 4 max: 8 err: 0 WiFi: MEM TCP_PCB_LISTEN avail: 4 used: 1 max: 1 err: 0 WiFi: MEM TCP_SEG avail: 16 used: 0 max: 14 err: 0 WiFi: MEM ARP_QUEU<DEL>MEM PBUF_REF/ROM avail: 10 used: 0 max: 0 err: 0

@adrian52 I'm printing 2 cubes, one with stable and one with the beta. I'm mid second print and seems that same PA value (0.04) gives different results with the beta... i'll try to post detailed photos of the outcome once it's finished.

I hear less noise from the extruder than latest beta, still there is some there. More noticeable at higher printing speed.

3.3 Stable:
20210801_125556.jpg

3.4 Beta:
20210801_125608.jpg

Unluckily i have to dry the filament buut it's the only glossy filament that i have atm and is easier to shot to seeartifacts. As you can see there is something wrong on the edges of beta print. Seems that more PA is needed than 3.3.

Printed with the same g-code with the same settings.

M122 B1 report:

M122 B1 === Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.0beta2-inputshaping (2021-08-01 00:01:15) running on Duet WiFi 1.02 or later + DueX5 Board ID: 0JD0M-9P61A-J8PS8-6JTD2-3SJ6R-9USUU Used output buffers: 3 of 24 (24 max) === RTOS === Static ram: 23932 Dynamic ram: 76624 of which 12 recycled Never used RAM 7456, free system stack 106 words Tasks: NETWORK(ready,14.8%,217) HEAT(delaying,0.0%,326) Move(notifyWait,0.0%,285) DUEX(notifyWait,0.0%,24) MAIN(running,85.2%,441) IDLE(ready,0.0%,29), total 100.0% Owned mutexes: WiFi(NETWORK) HTTP(MAIN) === Platform === Last reset 00:47:14 ago, cause: software Last software reset at 2021-07-30 17:52, reason: User, GCodes spinning, available RAM 11316, slot 2 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x0c Aux0 errors 0,0,0 Step timer max interval 0 MCU temperature: min 41.5, current 43.0, max 43.5 Supply voltage: min 23.7, current 23.9, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/890/890, gc cycles 0 Driver 0: position 28800, standstill, SG min/max not available Driver 1: position -27200, standstill, SG min/max not available Driver 2: position 120000, standstill, SG min/max not available Driver 3: position 0, standstill, SG min/max not available Driver 4: position 0, standstill, SG min/max not available Driver 5: position 0, standstill, SG min/max not available Driver 6: position 0, standstill, SG min/max not available Driver 7: position 0, standstill, SG min/max not available Driver 8: position 0, standstill, SG min/max not available Driver 9: position 0, standstill, SG min/max not available Driver 10: position 0 Driver 11: position 0 Date/time: 2021-08-01 13:01:42 Cache data hit count 4294967295 Slowest loop: 6.30ms; fastest: 0.17ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Storage === Free file entries: 10 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest read time 0.6ms, write time 0.0ms, max retries 0 === Move === DMs created 83, segments created 50, maxWait 0ms, bed compensation in use: mesh, comp offset 0.000 === MainDDARing === Scheduled moves 59750, completed moves 59750, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === AuxDDARing === Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1 === GCodes === Segments left: 0 Movement lock held by null HTTP is ready with "M122 B1" 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 Daemon is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty === DueX === Read count 0, 0.00 reads/min === Network === Slowest loop: 202.82ms; fastest: 0.10ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions HTTP sessions: 1 of 8 - WiFi - Network state is active WiFi module is connected to access point Failed messages: pending 0, notready 0, noresp 1 WiFi firmware version 1.24 WiFi MAC address 48:3f:da:79:65:eb WiFi Vcc 3.34, reset reason Power up WiFi flash size 4194304, free heap 27144 WiFi IP address 192.168.1.230 WiFi signal strength -21dBm, mode none, reconnections 0, sleep mode modem Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0

@engikeneer said in Adding additional points to bed mesh?:

@leckietech think it needs to be a complete grid to work... however, you can just edit it in Excel. That way you can manually measure the points of interest, then just linearly interpolate the others and get a much more detailed map in half the time 🙂
I've done this before to edit out a couple of dodgy probe points from my mesh

What could possibly go wrong - those points didn't count anyway. 😉

Frederick

@jens55 said in Help with apparently too hot printing:

@fcwilt said in Help with apparently too hot printing:

The difference between 300x300 and 500x500 is very significant. Y axis drive system may not be robust enough.

Oh yeah .... a significant difference! The Y axis is robust but that isn't going to help in the overall vibration issue.

Well it's hard to tell from the picture but it looks like it is belt driven using one belt - perhaps 9mm. And it may have some sort of belt tensioning device.

Given there may be 1000mm or more of belt that represents a pretty good spring which means accurately positioning a heavy bed (at speed) is going to be somewhat of a challenge.

Without any hands-on experience I would suspect that 70 mm/sec is rather optimistic.

Frederick

@engikeneer said in A bit confused about Tools positioning:

@the_dragonlord said in A bit confused about Tools positioning:

esteps are perfectly tuned for both the extruders,

In that case, just measure your filament diameter with calipers and run with that. As you print with both heads you'll probably find you want to set the extrusion multiplier a bit below 1 to prevent any exccess material on the top which the other noxxle will scrape and leave a mark. I prefer to tune that by just printing objects and seeing though so not very scientific...

RE pressure advance, the script in the PA wiki page isn't a python script you run, you put it straight into your slicer. I use PrusaSlicer and there's an option for 'Custom G-code' to be inserted at various points (start/end of print, before/after layer change, before/after tool change etc).
4fc99fa2-6b9d-4e63-88b2-db0e7a4e0799-image.png

It has built-in place-holder names which you can call to do things with (there's some documentation on their website, but I've found it's a bit of trial and error at times to get the syntax right if you try developing your own...)

Anyways, that will put the PA commands into the print file at the right points. Other slicers will probably have something similar though I've not tried

Alternatively, just set the cube going without that and change the PA on the fly be sending M572 D0 Sxxxvia the console in DWC, let it run a few layers and adjust again. TBH, this is how I've gone about adjusting/tuning most parameters on my printers because it means you can keep running the same file and tweaking things, rather than having to readjust the slicer, reslice, reupload etc...

In this post: https://forum.duet3d.com/topic/6181/tuning-macros-menus-accel-jerk-retraction-pressure-advance, Phaedrux shared some macros that can be quite useful when tuning accel, jerk, retraction and PA. They basically just call the relevant gcode to change the machine parameters (like M571 D0 Sxxx). They made my life a lot easier when doing this!

I use Ideamaker as slicer and it doesn't accept conditional expressions unfortunately....I copied and adapted the macros you suggested me...

PS - I've just discovered that LinuxCNC supports an extended version of G10 in which P0 is allowed and means use the current coordinate system. That's not currently supported by RRF, but I can add it in the next 3.4 beta release.

@dc42 said in Duet 2 vs Duet 3?:

@baird1fa currently the only supported way to run external drivers from Duet 3 is to use the external driver boards. We have some developments under way that may be of interest, if you can wait long enough:

We are also looking and ways to provide a separate 48V motor power input to a future version of the MB6HC

I have seen this pop up on the forums sporadically for a while now. Is there any indicative timeline for the 48V version?

@handymanpa54 DWC is hosted on the Duet, so if you reboot it will drop connection, but should reconnect within a few seconds. Is that what you're seeing?

@nurgelrot to add to what the others have said, tha max number of probe points in RRF is 441. Think that's based on a hardware limit from the Maestro, but applies to all boards. There was talk of potentially increasing it further for the D3 family, but don't think it's happened.

In general a well mounted bltouch on a decent printer and the right settings should be repeatable to within 5um, so definitely not lost in the error! My experience is that the BLTouch is probably a little more repeatable than the IR sensor (I use both on different printers).

I use a 20x20 grid on my 300mm x 300mm corexy on a Duet WiFi with a BLTouch with no problems. It's been months since I had to redo it though so I don't worry about how long it takes. My x-gantry sags a bit meaning I get a pringle shaped heightmap, so having that many points means I get a smoother compensation curve. It kinda depends on how level/flat you're printer is as to whether you need this though. Might be worth doing a big map and seeing, then you can dial it back if not needed?

If you're getting error messages or struggling with probe repeatability, then give some more details and I'm sure someone can give some suggestions to help 🙂

@ccs86 yes, the wiring is as you have indicated.

@dc42 i will test thank you

@gnydick
I had the same when I also added the fan# to my tool definition. I simply confused heatsink fan with part cooling fan.

@lake with no 3.3V LED, it looks like the 3.3V regulator has failed. This is U2 on the PCB, near the CE mark. Hard to say, but it doesn’t look quite right to me. How old is the Duet, and where did you buy it from? Have you connected any wiring to to the board, or has it been previously working? Some explanation of what happened before the failure would be useful.

Ian

@dhusolo it sounds to me that tuning has over estimated the M307 R parameter. Try reducing it by 25%.

@kb58 said in How do I enable the hot end heater:

@fcwilt I may add in several print statements to see what the tool state is, but obviously that's not a fix, but would still be curious where or how it's not happening.

I wish the DWC had a means to search all files which would make finding errant code bits easier.

Yes I can download everything into my standalone editor which will do such a search but I tend to avoid doing it.

Frederick

@luke-slaboratory said in Can the XY travel speed between G30 test points be changed?:

@fcwilt

I'm pretty sure this is the original reason I split it out into moves then probes - RRF3+SBC has been rough, and I prefer explicit commands to implicit.

Well using the SBC and all bets are off. It lags behind RRF "SD mode".

I'll have to test the T parameter on my SBC setup. If it works there is no reason to not use it.

Frederick

@dc42 thank you !

@phaedrux @phaedrux Well thank you so much, that worked. It looks like in the reprap configuration tool I had left a part cooling fan, and as you said I don't have one hooked up at the moment (I need to print a new mount and air duct first). In subsequent configurations I haven't had the problem, it now reads F0 instead of F-1 by default, so I think it was my fault all along. Are there any resources you recommend for learning more about the g code commands, particularly the diagnostic commands? It looks like knowledge in that area is going to be important moving forward with a duet controlled printer.

Right, thanks a ton for waiting lol.

The output of the M115 command is as follows:

FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.3 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2021-06-15 21:45:03

My config file is as follows:
.
; Configuration file for Duet WiFi (firmware version 3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.2.3 on Tue May 25 2021 23:51:34 GMT-0500 (Central Daylight Time)

; General preferences
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"*****" ; set printer name

; Network
M551 P"*****" ; set password
M552 S1 ; enable network
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet

; Drives
M569 P0 S0 ; physical drive 0 goes backwards
M569 P1 S0 ; physical drive 1 goes backwards
M569 P2 S1 ; physical drive 2 goes forwards
M569 P3 S1 ; physical drive 3 goes forwards
M584 X0 Y1 Z2 E3 ; set drive mapping
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z1590.00 E420.00 ; set steps per mm
M566 X90.00 Y90.00 Z60.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X8000.00 Y8000.00 Z180.00 E1200.00 ; set maximum speeds (mm/min)
M201 X50.00 Y50.00 Z20.00 E250.00 ; set accelerations (mm/s^2)
M906 X1100 Y2200 Z800 E700 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

; Axis Limits
M208 X0 Y0 Z0 S1 ; set axis minima
M208 X640 Y540 Z1000 S0 ; set axis maxima

; Endstops
M574 X1 S1 P"xstop" ; configure active-high endstop for low end on X via pin xstop
M574 Y1 S1 P"ystop" ; configure active-high endstop for low end on Y via pin ystop
M574 Z1 S1 P"!zstop" ; configure active low endstop for low end on Z via pin zstop
; M574 Z1 S2 ; configure z to use a probe at the min

; Z-Probe
;M558 P9 C"^zprobe.in" H3 F100 T2000 ; specify probe and input pin, also enable pullup resistor
;M557 X15:20 Y15:195 S20 ; define mesh grid
;G31 P100 X10 Y10 Z2 ; define offset and sensitivity for bltouch
;M950 S0 C"exp.heater3" ; create servo pin index

; Heaters
M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp
M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0
M307 H0 B1 S1.00 ; enable 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"e0temp" Y"pt1000" ; configure sensor 1 as thermistor on pin e0temp
M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
M143 H1 S280 ; set temperature limit for heater 1 to 280C
M307 H3 A-1 C-1 D-1 ; unbind heater pin 3 for use in bltouch

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

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

; Custom settings are not defined

; Miscellaneous
M575 P1 S1 B57600 ; enable support for PanelDue

I'm still learning a lot, so let me know if I've botched the configuration.

Thanks

@dc42 said in Error: Bad command: macros:

@leckietech although officially M98 requires quotes around the filename in RRF3, unofficially it still works without them in standalone mode. So I wonder whether S3D does something special with the forward-slash character. Have you checked what the generated GCode file contains?

when you and I were talking about this the other day, I never did get a proper output using additional quotes from S3D. I also saw on simplify's forums that many others were having the same trouble since 2018 with no solution. After you suggested making my own M codes, since then I have been using this and my own custom G110 and G111 firmware retraction codes with much success, it simply works flawlessly. I've made a dozen of my own custom codes and am in the works of adding these to all the printers in our farm! Opens the door to so much flexibility!

As a side note, this board reminds me of a similar project by egon.net https://forum.duet3d.com/topic/21680/designing-a-pwm-to-analog-mini-board-for-fans

Whew..... 😂

IMG_0565.jpeg