Using Duet WiFi 1.04 with M3D-style config...something not right

NoSkillzEngineer

I built an Ender 3 for a friend who is a teacher and I chose to swap the GARBAGE board for a Duet Maestro, had issues that were probably due to one line of code, but changed to a Duet WiFi anyway. I used the Promega config files as a template since I am building it for someone else that does not know 3D printing and I thought it looked more professional and was easier to understand and troubleshoot if she has any issues with it in the future.

I am pretty much all ready to calibrate it, however, there is one issue that is frustratingly preventing me from doing proceeding. There is a file "machine_zendstop.g" that is used on the Promega to give the actual Z-Endstop a precise location (which I imagine is more of a soft limit than the "M208 Xn Yn Zn Sn ; Set axis minima/maxima" command which I am guessing is the hard limit).

I decided to go this route so I could put the macros M3D uses for the Promega in an attempt to make calibrating the Z idiot-proof, or at the very least less prone to errors due to a syntax error in the config.g:

https://github.com/PrintM3D/Promega/tree/devel/SD Card Structure/Compound/macros

I have looked through every file and every g-code file and the only thing I can fathom would be that maybe I need to "call up" the file in my config.g in order for it to show up?? ¯_(ツ)_/¯

The original sys files for the Promega are found here, should anyone be curious:

https://github.com/PrintM3D/Promega/tree/devel/SD Card Structure/Compound/sys

This is a link to my Google Drive folder that I created for this post, but probably where I'll leave the final config files as well as Github when I have finished them. The "config.zip" is what I get when I download all the system files via zip. The "sys.zip" is directly off the SD card, pulled from the board just after I downloaded the files from the DWC, via a thumbdrive-style microSD card adapter. Notice "machine_zendstop.g" is present in the "sys" folder, but not in the "config" folder. It also does not show up on the DWC, despite having created it within the DWC. I even just tried deleting it and redoing it normally in windows as a .txt file then changing it to a .g file.

https://drive.google.com/open?id=1xIKeUJMTSl3EvcLhJU8AvNvLaFAtZnxy

What am I missing??

M115
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 2.03beta1 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2019-02-03b3

Firmware Name: RepRapFirmware for Duet 2 WiFi/Ethernet
Firmware Electronics: Duet WiFi 1.04
Firmware Version: 2.03beta1 (2019-02-03b3)
Web Interface Version: 1.20

Don't laugh at the messy and redundant files, I am not deleting anything as I am still testing, so I am aware it isn't as tidy as it should be.

Any and all help is greatly appreciated.

nhof

It looks like the machine_zendstop.g file just has one G92 command in it (which resets the Z position to the given value). The only time it is called is during the z homing routine.

The script would be called using M98 like so:
M98 Pmachine_zendstop.g

You might be able to try that in the console manually to see if you get errors. IF the file is still messed up you could just take the G92 command from it and put it into homez.g instead.

NoSkillzEngineer

@nhof said in Using Duet WiFi 1.04 with M3D-style config...something not right:

It looks like the machine_zendstop.g file just has one G92 command in it (which resets the Z position to the given value). The only time it is called is during the z homing routine.

The script would be called using M98 like so:
M98 Pmachine_zendstop.g

You might be able to try that in the console manually to see if you get errors. IF the file is still messed up you could just take the G92 command from it and put it into homez.g instead.

Yeah, that did it.

; homez.g 	updated 04.20.2019
; called to home the Z axis
;

; ============= PRE-HOMING =====================

; Ignore Machine boundaries
M564 H0 S0

; Turn off bed leveling during homing
G29 S2 ; Does the same as M561!
G29 S2 ; Do it twice because once just isn't enough
; Switch to Origin Tool
T0
; Relative positioning
G91

; ============ HOME Z ==============

; Rapid Z until limit switch triggers
G0 Z220 F1500 S1
; Back off to release limit switch
G0 Z-5 F1500
; Slow advance to trigger limit switch
G0 Z10 F120 S1
;M98 Pmachine_zendstop.g ; Set Z Endstop height
G92 Z190.5 ; With solid bed mounts
M98 Pmachine_zprobe.g   ; Set Z Probe distance

; ============ Post-Homing ==============

; Revert to absolute coordinates
G90
; Re-enable mesh leveling
G29 S1
M98 Pmachine_axisdimension.g ; Set Axes Limits
; Stop movement across limits, enable boundaries, homing requirement
M564 H1 S1

commented out the subroutine and wrote the code out. Works perfectly. Not sure why it would be an error, that shouldn't be a problem. It does what I need it to, I'll just edit where the macro says to edit the file. I was just trying to keep things consistent with M3D's repo.

Thanks again!

chas2706

Hi I was curious so looked at the config,g setup based on the Promega that you are using.

If any changes are made on the fly to the sub-g code files i.e. machine_zprobe.g or machine_extruder_extruderstep.g etc would the changes take effect instantly or only after a firmware re-start?

Phaedrux

@chas2706 said in Using Duet WiFi 1.04 with M3D-style config...something not right:

would the changes take effect instantly or only after a firmware re-start?

Any changes to a macro will only take effect the next time the macro is invoked. At startup, config.g is invoked automatically. Any macros linked within config.g with M98 will also be invoked.

NoSkillzEngineer

@chas2706

Yeah, hopefully, the way I use them is not going to cause an unnecessary issue. I'll admit, that has been a fear that has not left the back of my mind. As long as I put them where they should be, it shouldn't be much of an issue.

chas2706

Thank you both for your answers.
Ive had a couple of experiences when I my duet has lost internet connection in the middle of me making changes to config.g and when reconnected config.g has gone missing.
I thought the M3D style config may reduce the severity but could also cause the other issues raised.