Topics created by omni

@fcwilt, agreed. I go down to 50% of my normal speed and small features are reduced another 50% (molasses in the high artic moves faster)

@omni @SDJ
you can see work has begun here https://github.com/supermerill/SuperSlicer/commits/nightly_dev

@omni said in Switching from bang-bang to pid for a dual zone 1500w AC heater:

Then when I do the calibration, I should add the calibration parametars to M307?

Or just use M500 to save them to config-override.g and add M501 to the end of your config.g.

@mfs12

Flashed RC6, tested - seems to have been solved. Thank You! 🙂

I was able to solve the problem myself - so this is for anyone who might stumble upon the same problem in the future.

The problem was the inertia (momentum) of the filament spool. The filament spool is held by the famous "Universal filament spool holder" that uses two ball bearings at each end and is extremely easy to move. So when the extruder has faster moves - it pulls the spool and it's inertia pushes the filament a bit more through the sensor than it is actually going into the extruder since the filament can bend and straighten - hence it all makes sense - that sometimes there is more, sometimes less filament going through the sensor - but the average is always exactly the amount that went into the extruder.

The solution is to constrain the filament path before and after the sensor - either by a tighter PTFE tube on both sides or maybe by a sponge filament cleaner at the entrance of the sensor.

If you are using the "Universal filament spool holder" - you can also put two PTFE washers on the sides of the ball bearings and squeeze them a bit with a locking hex nut - that would prevent the spool from rolling more than requested, but would still roll nicely.

Now my readings are normal.

Hope it helps someone having the same problem with the laser filament sensor.

@mfs12 Thank you. Looking forward to the release.

@phaedrux
UPDATE :

Your suggestion of replacing M226 with M600 manually in gcode - actually worked! 🙂

The printer paused correctly, inserted the nuts and resumed the print.... 🙂

Guess this is a workaround for now, until I figure out why M226 is not working.

Thanks again!

I had issues with one of these, and it turned out my belt was too heavily tensioned. These motors have very long shafts, so require support at the end if you are going to tension them to more than a loose fit. I got around it by redesigning the mounts to include an enclosed 608 bearing which the end of the motor shaft slides into - since doing that no issues with grinding or over heating. Hope this helps!

@omni

It is the first time I fitted a filament out to my duet wifi and found the same problem , pause retracts 10mm of filament and resume put it back , but if you change filament and push filament until you see the new filament come out you get a 10mm big blob on resume.
So I now retract 10mm before I resume .

I am just now dipping my toes into this as well as an option for our machines. I think there are various ways to accomplish the same thing here and do remember reading how important the S parameter is for any and all commands when running a laser - so my assumption is adding the S parameter on the G1 moves will work, but I haven't yet tried it..

We have a copy of Vectric VCarve Pro that I recently upgraded with their laser plugin. One of the defaults is for the OozNest Duet (I know right? OozNest and oozeBot.. small world). They are using the Duet 2 as the controller for their hobby CNC machines and have instructions to add a laser on their website. Here is a sample of the code their Vectric post-processor generates:

T1 G17 G21 G90 G0Z20.320 G0X0.000Y0.000 G0X34.827Y38.358Z5.080 G1Z0.000S0F762.0 M3 M3S1000 G1Y62.302 G1X56.947Y53.139 G1Y29.196 G1X34.827Y38.358 G0Z5.080 G0X56.946Y60.322 G1Z0.000S0F762.0 M3 M3S1000 G1X33.370Y67.705 G1X56.946Y55.533 G1Y60.322 G0Z5.080 G0Y62.716 G1Z0.000S0F762.0 M3 M3S1000 G1Y67.505 G1X31.194Y75.779 G1X56.946Y62.716 G0Z5.080 G0Y74.688 G1Z0.000S0F762.0 M3 M3S1000 G1X29.013Y83.873 G1X56.946Y69.899 G1Y74.688 G0Z5.080 G0X81.279Y69.398 G1Z0.000S0F762.0

This is very similar to the gCode produced for our other laser engraver.. but again, I have not yet tested any of this.

And FYI, while I wait on our new Opt Laser head to arrive, I'm working on our own post-processor for Vectric we'll be releasing. I'll pick up a copy of Lightburn here soon to do the same as we understand most people won't be able justify the cost of Vectric's solution.

Hm,

i can remember when i got the board (new with duet) i just tried upgrading to the newest firmware and it failed. The i started reading.
Thats how man do... break stuff and read the instructions after 😂
Then i updated to 3.0 then to 3.1.1 as it should be.
Maybe something got mixed up trying to update to 3.1.1 directly.

Greets DerGulli

For tilt correction to work well you first need to ensure the bed itself is actually level in relation to the frame. To do this you might need to manaully adjust the gantry relative to the top bar and then level the bed to that. going forward the tilt correction should be good after a few passes so you might need to do G32 2 or 3 times to get it to converge.

Also, for your homez, you should probe the center of the bed, not a corner.

G1 X0 Y0 F6000 ; go to first probe point
G30 ; home Z by probing the bed

Also, slow your bltouch probing down a bit.