Topics created by Stephen6309

@droftarts No wonder I didn't find it. The search function needs to read your mind. 🙂

Deut 3 6HC
Duet-3-6HC.jpg
Duet 3 Mini 5+
Duet-3-Mini-5+.jpg

Solved and no problem with 3.5.0 beta2 and PrusaSlicer 2.5.0 👍

@dc42 I haven't set up a start.g file. But that's a good idea.

@gloomyandy @phaedrux
That fixed it. It works correctly in standalone mode with M669 S1, but not with the PI, strange.

Now on beta7+7. Printing fine for the last four hours. Y driver 37C.

Update: Mouser just emailed: Production Issues Reported - Delivery Unknown for the hirose connectors.

So, I made one to use the regular PI4. Waiting for the boards to test.

@Stephen6309, BTW best way to update is to use all parameters

M997 S4 P"filename"

If you omit P parameter the P-parameter will default to "PanelDueFirmware.bin".

@jay_s_uk Dang computers. 😲 Removing the : fixed it.

@phaedrux Yes, it working normally. X is X and Y is Y.

This finally works. 🙂
Lights up 4 red leds when above 40C, green <=40
Bed and T0 heater are set to 4 leds each.

Make sure each if and elif M150 conmmend has a beginning space

; dameon.g ; Adafruit #1426 8 led neopixel G4 P500 ; 500ms delay if heat.heaters[0].current > 40 ; temp M150 R255 P10 S4 F1 ; set first 4 red elif heat.heaters[0].current <= 40 M150 U255 P10 S4 F1 ; set first 4 green if heat.heaters[1].current > 40 ; temp M150 R255 P10 S4 F0 ; set second 4 red, and done elif heat.heaters[1].current <= 40 M150 U255 P10 S4 F0 ; set second 4 green and done

This is in my config.g to make sure the NEOPixels are off

M150 R0 U0 B0 P5 S8 F0 ; shut off neopixel

@dc42 I've seen that, but I thought the one on the 4.3 screen would work. Haven't had a real need to use a seperate sd card.

I've got a fix ready for this, it won't happen again in future versions.

you can change the directory DSF uses in /opt/dsf/conf/config.json i believe. point it to /boot instead of /opt/dsf/sd and give the permissions a once over. (note not tried it myself!)

After a shutdown, reinstalling the extruder assembly back on the printer. Fired it up and it still can get to 220C, no errors.

@dc42 From your comment, I checked and it turn out to be bad connection between the the female XT30 connector and out0. Replaced the wires, connector and ferrules and it now heats up. The problem did let me find a bug. 🙂

It was a bad solder connection to the XT30.

@Phaedrux That tool list is from my config file. The CAN ID for the tool board was edited to 121, the boards default. The M582 and M522 are commented since the SBC complains about them. The PWM output was changed to 121.io0.out due to the config tool only allows temp0 and temp1. The config.json has been edited with the IO changes, so that the tool board IO comes up blank on the config tool.

config.g
config.json

@dc42 It would do a double tap on the bed. It would do it when homing Z, and doing the G29.

Watching it do it, the moment it would hit the bed, it would fully retract, but it would imediately redeploy and trigger again.

Watching the 3.1, it would trigger and not rectract completely, the full retract was delayed,

@Stephen6309 said in Conditional on G29 S0 or S1:

G29 S1
if result > 1
G29
It works with no errors

I was just playing with this.
Since I have a heated bed and also use the filaments/config.g to set different bed temps depending on the filament loaded - the bed heights could vary, but I haven't really seen that in real life. With that being said, I always do G29 with the bed heated to the filament's config.g settings. So depending on the different filaments in the DWC profiles, bed warp-age could vary - so not one bed height.csv for all. Hence this:

G29 S1 [P{move.extruders[0].filament^".heightmap.csv"}] if result > 1 G29 G29 S3 [P{move.extruders[0].filament^".heightmap.csv"}]

Will yield:

G29 S3 [P{move.extruders[0].filament^".heightmap.csv"}] Height map saved to file 0:/sys/PETG.heightmap.csv