@Exerqtor RRF in standalone mode supports only one active transfer connection. If you want to transfer multiple files, make sure to apply this setting in your FTP client before you attempt it.

@Basil said in Duet 3 Mini 5+ Firmware with SBC:

Silence and quiet means also an answer.

Well we do have to sleep occasionally.

When you say update complete, did you verify that the firmware was updated this time with M122?

@Basil said in Duet 3 Mini 5+ Firmware with SBC:

@Basil
Duet board has no any sd card conected

What does this mean? Is an SD card inserted into the slot on the board?

@vrakaslabs said in Mini5+/Toolboard CoreXY does not properly home axis:

Someone should put a note on the Github Release page.

Done.

@RogerPodacter thank you

@breed I use a euclid in mine. The chamber hits around 55 degrees

@Phaedrux lowered Z speed. Sounds better now.
Thanks.

Just got my refund > Superslicer is the way

@jay_s_uk thanks a lot

@dsela thanks for updating us. Let us know if it starts happening again. If the Status light stops blinking again, please check whether the blue VIN and red 5V lights are still lit.

@chrishamm thanks for the reply. Works great, I owe you a beer.

Yes you figured out the stutter with the Z jerk.

I would seriously consider sticking with x16 microstepping with interpolation enabled.

@markz Good morning, I am so sorry, you are right, I meant 192.168

@Phaedrux said in Z Offset calculation and Height Map inconsistent:

@TheDragonLord said in Z Offset calculation and Height Map inconsistent:

I've made a trial and phisically lowered the BLTouch by about 1mm....well, after that the nozzle raises from the plate about of another 1mm....it looks like the Z offset is "added" rather than "subtracted" from the nozzle height or that the BLTouch gives an "inverted" value....I think I've made some stupid typing error somewhere but I can't realize where

The BLtouch should be mounted such that the base of the probe body is approximately 8mm above the nozzle tip. This should lead to a trigger height of ~2mm. This is the range recommended by Antclabs themselves to ensure accurate probing and clearance of the pin.

Increasing the probe offset moves the nozzle closer to the bed, reducing it moves it farther away.

Did you try the M558 P0 trick?

@Phaedrux said in Z Offset calculation and Height Map inconsistent:

@TheDragonLord said in Z Offset calculation and Height Map inconsistent:

I've made a trial and phisically lowered the BLTouch by about 1mm....well, after that the nozzle raises from the plate about of another 1mm....it looks like the Z offset is "added" rather than "subtracted" from the nozzle height or that the BLTouch gives an "inverted" value....I think I've made some stupid typing error somewhere but I can't realize where

The BLtouch should be mounted such that the base of the probe body is approximately 8mm above the nozzle tip. This should lead to a trigger height of ~2mm. This is the range recommended by Antclabs themselves to ensure accurate probing and clearance of the pin.

Increasing the probe offset moves the nozzle closer to the bed, reducing it moves it farther away.

Did you try the M558 P0 trick?

Hi, no I didn't, I had few time today and I've mainly focused on try to understand how to solve the problem with the BLtouch...in the end I had to re-mount the vinda because I couldn't get rid of the error and the vinda works in terms of z offset....I didn't know about the 8mm I've always used it with almost 3-5mm...tomorrow I'll see if I have enough vertical room to mount it at about 8mm from the nozzle...thanks!

Either way you choose to go is fine by me. We just want a happy customer.

@o_lampe I do see it that way.... after I ram the nozzle into my bed. The issue is that after a month or two of not using my 3D printer I forget this lesson and end up repeating my mistake. After breaking three glass beds I figured I should ask for this feature.

@jdandcoke P defines the tool number in M563 eg:

M563 P0 S"hemera" D0 H1 F0

T[number} selects the tool eg:

T0

Ian

@dc42 Thank you! I found it 🙂

@T3P3Tony I must have looked at those files 10 times... I was looking for a picture not a link. Thanks to both of you for helping.

Thank you for that reference.

I did go through the forums before I posted here, and I found several posts, including a few linking to the Arduino -> RepRap transition. The core problem is that the manufacturer will not share anything about the F430's settings. None of the posts documented what folks learned during the transition. I was hoping to learn where the pitfalls are before I do something which fries the unit.