Topics created by kaoshihchuan

@kaoshihchuan said in Segmentation with M669:

@dc42

I was pulling machinePosition from object model.
But looks like the segmentation is not working for firmware 3.3

According to https://github.com/Duet3D/RepRapFirmware/wiki/Changelog-RRF-3.x, segmentation support for kinematics that are not usually segmented was implemented in RRF 3.3; however M669 with no parameters did not report the current segmentation until version 3.4.0.

I'm not exactly sure what you're trying to do.

In short, there is no real way to have multiple endstops for a single axis. Once the axis is homed to one end, the length of the axis is enforced. Endstops are not active during a job either, only during a homing move. So you don't really gain anything anyway. It is possible to configure the endstops to act as an emergency stop in case the axis skips steps and loses position and a crash on the frame would be damaging.

Regardless, it's far easier to configure things in RRF3 than in RRF2, so probably a good time to upgrade as well.

@kaoshihchuan said in Printer head current position:

But I would like to know where it actually is at that moment.

Well without an encoder you can't really get an accurate idea of where exactly it is in a timely way.

You could try experimenting with segmentation to break up moves into smaller moves meaning you get more endpoints for position.

https://duet3d.dozuki.com/Wiki/Gcode?revisionid=HEAD#Section_Parameters_for_Cartesian_CoreXY_CoreXZ_CoreXYU_CoreXYUV_MarkForged_kinematics_RRF_2_03_and_later_only

@kaoshihchuan said in Duet Web control for rr_"commands":

@stuartofmt

Do I have the right format for the code I sent?

I'm not the best to ask on this as my projects so far have been "blind" as it relates to sending gcode to an SBC. I have relied on others to report back any issues.

Ultimately - when GET is used , all parameters end up being encoded into the URL as query string parameters. With POST, the data is in the message body.

My GUESS would be that the correct form is something like this:

command = 'G0 X300 Y300' r = requests.post('http://192.168.168.144/machine/code', data=command) or maybe with command = {'gcode':'G0 X300 Y300'}

Edit: Please let me know what works as I have a bit of POST code in one of my Duet related projects and I'm not sure if it works or not 🙂

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

You can have a max of 441 points.

How are you defining the Z0 point? The firmware will display the heightmap in reference to how Z0 was set.

I suppose that could be possible. You'd just have to figure out a way to merge your new height data into the heightmap.csv. Could be done manually I suppose.

When the print is paused, you should be able to use G29 S1 P"filename" to load your newly modified map and then resume the print.

@kaoshihchuan the following two links will help you understanding the new object model of RepRapFirmware version 3 (RRF3):
https://duet3d.dozuki.com/Wiki/Object_Model_of_RepRapFirmware
https://duet3d.github.io/DuetSoftwareFramework/api/DuetAPI.Machine.MachineModel.html#properties

In the first link is explained, how the Duet can be accessed and explaining of the json structure.
You should use the current RRF version (today: 3.1.1).