Topics created by ericlmccormick

I ended up solving this with a few lines of code and it works really well.
Step 1.Created a file called saved_var.g with a single line in it

global z_offset = 1

Step 2. Added the following line to the end of config.g

M98 P"saved_var.g" ;Load saved z offset

Step 3. In homez.g, I replaced my G31 code with

G31 P1000 X-32 Y0 Z{global.z_offset}

Step 4. I made a Marco with the following

set global.z_offset = global.z_offset - move.axes[2].machinePosition + 0.5 echo >"saved_var.g" "global z_offset = " ^ global.z_offset

Step 5. Reboot, Home All, bring the nozzle to the correct height using my gauge. Then run the macro.

Note: I used a metal ruler that happens to be exactly 0.5mm. If you use something else, then you need to replace the 0.5 with whatever thickness gauge you use.

@dc42 The filename would be already very helpful.

https://forum.duet3d.com/post/332495

I would not expect that there are tons of duplicate file names in real live. And it would be acceptable to go trough 5 files. But going trough more than 50 is a nightmare. And I had the problem that RRF was complaining about spaces and widespaces in one line. There is almost no way to grep for that. A "debug mode" maybe? You can free up some memory by dropping a lot of things, I guess that 90% of the problems appear before the actual g-code gets executed. So why not simulating the entire process with more debug info?

Or just store the filename in a variable and print it out with the error message. Just something which gives us a better hind. I add M118s to every file at the moment to trace down the location of the "typo".

Cheers, Chriss

@fcwilt I have 24V LED strips 2 of my 3 printers, but easy to add it to my 3rd. I use E1 heater for the LEDs, putting them on a fan output cause voltage drop on the fans.

But since I have the hotend shoot out a little filament before a retraction, having the hotend in a given place above the build plate with a little filament under would signal it has done what it needs and needs me to swap out the filament and hit the button to continue the process.

I have also setup a macro for replacing my nozzle and this would be a good way to tell the machine I am done with the nozzle swap and to start cooling off or go into a stand-by state.

I will have to check out this code a little later today.

@bot I got it working. Thank you.

@ericlmccormick said in Duet with Hotend breakout boards:

Any chance of a header that gives the Duet2wifi and Duet2Maestro CAN ability so that the toolboard can be used on those systems?

No unfortunately not.

@bearer yeah, just a pop-up in the duet control page.

@ericlmccormick It looks like you were initially adding a new SSID, M587 S"9762" P"[Password]. However, you're using firmware 3.01-beta2. This has a bug in it that does not store the wifi password. See first bug fix here https://github.com/dc42/RepRapFirmware/blob/v3-dev/WHATS_NEW_RRF3.md#reprapfirmware-301-rc1
Update firmware to 3.01 RC1 or later.

Ian

The M540 reporting issue on the Duet WiFi will be fixed in the next 3.01 beta. I have also added the MAC address to the object model.

The online configuration tool doesn't cover everything that RRF can do, it's meant to get you started.

@dc42 I'll rather stay at V3 codebase.
Reverting back to 2.05 requires re-setting too many things (endstops, laser control, etc..)