Posts made 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.

@jay_s_uk using move.axis[2].machine position, I was able to get the value I was looking for. This is a huge step to getting this working.
However, I am now running into a new issue. Once var z_height is loaded from a file, trying to update that variable returns an error saying that the variable already exist. I am not an expert coder, but when I have programmed in other languages the past, you could just call up the variable and give it a new value. Do you know how to give an existing variable a new value?

@jay_s_uk type in M114 in the console and look at your results. I just finished a print an mine currently says X:300.000 Y:290.000 Z:7.060 E:0.000 E0:6993.7 Count 24000 23200 2782 Machine 300.000 290.000 7.110 Bed comp -0.155

I want to be able to take the 7.060 number and set that to a variable

@jay_s_uk I am not looking for the stored position of the the trigger height as I set that with the G31 commend. I am looking to extract the Z component of the tool position.

I used a 0.5 gauge and I have to hard code my offset anytime I change the nozzle. However, If I set my offset 1.0 initially and set it to a variable z_height. Then I adjust my z height to my gauge, and my tool height returns 0.3. I want to have a scripts that does z_height = z_height + tool position - 0,5 (gauge thickness).

Whenever I swap nozzles, I find that I need to adjust my offsets each time. I use a gauge to get my height and then I update my G31 command accordingly to adjust for the difference but this is a pain.

I would like to make a script that pulls my current Z height, compares it to my known height from my gauge and my stored offset, then adjusts the stored offset automatically. I could see this able being very helpful if you have multiple printheads. I know how to set a variable, and save a variable to a file. But I can't seem to figure out how to pull just my z height. Using M114 pulls everything. Is there a way to parse the sting and save just the Z component to a variable? It would be nice if something like "M114 Z" would return just Z, but that doesn't seem to work.

@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.

Would it make sense to replace M291 with the following 2 lines?

M950 J1 C"e1stop"
M577 S1

@fcwilt M291 with S1 allows you to pause your gcode and wait for an input before continuing. The code seems to work out well, but I have to go back to my computer and it would be better to hold the filament in the extruder and push a button the printer.

@jay_s_uk I don't have S in any of the G1 line of my homing files. I don't specifically call out H0 because H0 is supposed to be the default, but do I need H0 in each of the G1 lines?

As a follow-up I get the following error "M98 P"0:/macros/Filament Change"
Warning: Obsolete use of S parameter on G1 command. Use H parameter instead."

This is the GCode for that macro, but I don't use the S or H on the G1 commands.
M104 S230 ; set extruder temp
G28 ; Home Bed
G1 X80 Y80 Z50 ;Move to Center
M109 S230 ; wait for extruder temp
G1 E10 F500
G1 E-100 F6000
G92 E0
M291 P"New Filament Loaded?" S2
G1 E150
G92 E0
G1 E-0.5 F500 ; Retract a little
M104 S0 ; turn off temperature
M84 ; disable motors

Darning prints, I get a lot of error/warning codes. Things such as "Warning: Obsolete use of S parameter on G1 command. Use H parameter instead." or "Error: invalid input type". Request that these events also note the file name and line that triggered this event.

I am using motor stall for X & Y and a probe for Z which leaves all my endstops open for reuse. I have also setup a macro for filament swaps. I have the hotend move to a specific area above the build plate, heat to 230, extrude a little then retract a lot. Then I use M291 P"Click ok" S1 to wait, then I have it extrude enough to clear the old filament out and have clean filament out the nozzle, then shut down.
I would like to use an endstop as a trigger to continue from M291 instead of having to trigger from my computer/phone. Is this possible?

@bot I got it working. Thank you.

@bot I am running DWC 3.4.0-rc2 and PrusaSlicer-n8-2.5.0-alpha0. Send the gcode over and still not showing up. What am I missing?

@jay_s_uk my understanding is that PrusaSlicer 2.2 and up have the image generation, but maybe I am missing a setting somewhere.

@phaedrux I am using PrusaSlicer 2.4 and upload directly from the slicer.

@jay_s_uk I installed 3.4RC2 onto one of my printers but the images don't show up. Is there a setting I need to change?

Feature request: image preview from slicer in Files > Jobs page.
I see lots of people asking for this within PanelDue, but nowhere within the web interface.

@nathan116 Did you ever resolve the issue of it not updating the image? I have the same issue.

@the_dragonlord I'm driving the LEDs directly from the board so that I can control the brightness. But if you are driving a MOSFET, then the fan is a better option I guess.