Topics created by monster

@monster said in Switching from Stable to Unstable versions:

by the way is "move.axes[0].max" is available in RC7 ?

Yes.

Also is there way to define own constants? E.g. I could define X Y coordinates at witch magnet for Z endswitch is locates and refer to those constants in homing g files.

Not yet, this is scheduled for firmware 3.02.

@jens55 said in Seeking an advise on what Z sensor to go with:

I found that the BLTouch was very sensitive to probing speed. If you run it too fast then the measurements will fluctuate. I also found that multi probing (measure the same point until two successive readings are within tolerance) is pretty much required to get a good result.

BLTouch is sensitive to magnetic fields. The impression I have is that mostly this isn't a problem, but some bed heaters generate enough magnetic field to affect it. That's why we provide the B1 parameter in the M558 command, to make RRF turn off the bed heater temporarily during the bed probing move. Might that have been the reason for your inconsistent results, or were you already using the B1 option?

I also just noticed that when Pause print pressed - pause.g isn't seem executed...

Yes, go to https://github.com/dc42/RepRapFirmware and click on Watch.

https://duet3d.dozuki.com/Wiki/Using_mesh_bed_compensation

That's exactly what mesh compensation is good at.. compensating for.

@Phaedrux said in How to calculate feed rate?:

Is that with 6500 or 650? If this is correct, then your steps per mm is correct.

Something else is wrong in Cura.

with 6500

M92 X87.40 Y87.40 Z1060.00 E6500.00:6500.00:6500.00 ; set steps per mm

Yes you could run a slicer on the pi, but it will be a bit slower than on your PC and I don't think it would solve any of your problems.

Quick glance and wild guess says 30-40% of the PRs get merged when looking at the github pages; so yeah I'd say if its usefull and follows the conventions you've got good odds for getting changes merged.

You grasp the concept perfectly; the online tool gets you started, and you edit from there.

Also, most config commands will tell you their active state if you enter just the command in the console. Example: M906 with nothing else will show all currents.

Some commands you need to specify one parm as an identifier. Example: M569 P0