@dc42 Thank you!

That was it. M204 defaults to 20'000 mm/s^2. Starting to lose steps at 24'000 mm/s^2. Not bad for an Ultimaker 2 that's close to 10 years old.

@darkuncle33

Your M665 H value is way to high for a Q5.
with a stock q5 it should be no more than 220.

See here for tuning a heater.

https://docs.duet3d.com/en/User_manual/Connecting_hardware/Heaters_tuning

Be sure to save the results after running the M303 command to tune the heater, either with M500 to save it to config-override.g (and you must add M501 to the end of your config.g to load it at startup), or you must manually enter the resulting M307 command in your config.g

@Sindarius said in Voron 2.4 Quad Z drive levelling issues:

z5:6:4:3

thank you!!! that was it!

7ddf132c-86e7-499d-8a4e-1b556df1801a-image.png

@Jarery driving Neopixels from Duet 2 requires motion to be paused while the data is sent to the Neopixels, because their timing requirements are strict, so step pulses cannot be generated at the same time.

Duet 3 main boards have a dedicated output for LED strips so that motion does not need to be interrupted.

M574 Z1 S2 P"zprobe.in" ; Z-probe configuration

Yes, you should delete that line.

@Dizzwold

Remember that magnetic force decreases with the (IIRC) square of the distance, so the blind holes are cool, but decrease the force a little.
The beds I built I just used through holes and superglue, 305x305mm and 25 magnets of similar size to the ones you are thinking of using (the ones by the edge are set back ~12mm). The critical thing for any glue is getting the surfaces really clean.

The only issues were if the glue failed, but those ( a couple IIRC pulled out) I just scraped out the old glue and re-glued.

The beds are now several years old and still work just fine.

@deckingman Thank you.

Usually when the mesh isn't being applied as expected it's due to mechanical issues causing the mesh to vary from reality. Usually probe tilt that varies with XY position or skew in the XY axis.

A cracked arm holding the bed is a good candidate.

@Proschi78
With this command you switch the axis limit on or off.
https://docs.duet3d.com/en/User_manual/Reference/Gcodes#m564-limit-axes
However, the project should be treated with caution!

@OwenD
I have my bed temp for each filament type set in the filament config file. I use a conditional code that will run a start heating bed macro if the firmware sees that there is a current print job. however, I have not attempted dual extruding prints yet.

what would be a good object model to check for as a condition so the firmware knows it is heating the bed for the first layer of any given print?

I will put this into the tpost#.g file so it will check to make sure that the following layer is the first layer for a print before applying the bed temp and evoking a start heating bed macro. otherwise of the conditions aren't met, it will ignore that portion of the tpost#.g script and move on to only heating tool to the mounted filament's config.

below is my tpost:

m703 G4 s1 if {job.file.fileName != null} && {job.build.currentObject = -1} M98 P"/sys/PRINTCODE/startbedtemp.g" ;evoke startbedtemp.g to warm bed m568 P2 A2 ;then set T2 to active temp g4 s5 M116 P2 ; Wait for set temperatures to be reached ; if file name exist amd no current object

@MaxGyver the warning will only appear in response to an M307 command. You may get it on power up on a Panel Due if the command to configure the Panel Due comes before the M307 command? But if you are seeing it repeatedly it suggests you have other M307 commands in your files somewhere
My toolchanger used to have them in the tool change files, but I got rid of them as the didn't really do much!

@Phaedrux Got it working now! it was my fault for not reading your directions currently!

Thanks to the both of yous!

@Dizzwold said in Twin Z axis Motors and MBLA:

Tronxy heater and bed.

Well 70c for that bed heater is probably the limit.

@dc42 said in M303 "F" parameter highlight:

The default speed is 0.7 in an attempt to get reasonable accuracy over the range 0.4 to 1.0 using extrapolation and interpolation, rather than good accuracy at 1.0 and poor accuracy at low speeds.

If you configure your slicer to use full fan PWM whenever the fan is on (which might be appropriate when printing PLA) then 1.0 would be better.

Thanks for the explanation. Personally, I usually only use the fan for bridges and/or very short layer times, so I'll stick to using 100% when PID tuning.

@Phaedrux
I don't actually remember, I don't remember seeing anything unusual.

May be best to do it again, also if you look at my bed compensation in the following thread;
https://forum.duet3d.com/topic/30383/twin-z-axis-motors-and-mbla/9?_=1668068238105

@o_lampe
It was a wire. I really didn't think so because it is a relatively new machine and the timing of it, but I tested and replaced the wire with success.

@davidewen said in Strange Blobbing on Layer Change:

Seam is still there, but greatly improved.

Have you tune pressure advance yet? That's the remaining piece of the puzzle.

https://docs.duet3d.com/en/User_manual/Tuning/Pressure_advance

@ianborg As well as your wiring issue, it sounds like your part cooling fan might be too aggressive in that too much air is being directed at the nozzle/heater block. That would explain why you have problems PID tuning the tool, rather than just the heater. Unless you fix that, you could potentially get heater faults when the fan comes on during a print.

@ianborg This is indeed a duplicate post and I've replied to your first one.