Posts made by ericlmccormick

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

@the_dragonlord but I recommend you use a heater and not a fan

@the_dragonlord your problem is you have m106 P2 S1 H-1 and you should have m106 P2 S0 H-1

@the_dragonlord can you share your config.g file?

Make sure the M42 code is in the slicer startup code and NOT in config.g

I put M32 in my slicer start code which calls beg.g and M0 in my slicer end code which runs stop.g

Then I have M42 P2 S255 in my bed.g and M42 P2 S0 in stop.g and cancel.g

In config. g
;LED Strip
M950 P2 C"e1heat"
M307 P2 A-1 C-1 D-1

Then add the following to change power output
M42 P2 Sxxx