Advanced Search

phillc54 wrote:

You should have SheetCam set up to either use the materials that are in QtPlasmaC or to create the materials as required.
If you have something like below in the G-code file:

(o=0, nu=2, na=5mm Mild Steel 40A, ph=3.1, pd=0.1, ch=0.75, fr=3000)
then SheetCam is creating the materials.
http://linuxcnc.org/docs/devel/html/plasma/qtplasmac.html#plasma:magic-comments

The default material in QtPlasmaC is set on the SETTINGS tab.

 

.....
Thinking about it more with your comment, I think maybe the machine is moving the correct amount, but the position reported back to LinuxCNC isn't correct or isn't stable, for some reason. How can I look into this further? If it were just floating point rounding error, once the iceshield had arrived at the correct position, shouldn't the reported position then be stable at the rounded value, instead of flicker? My X axis is very coarse, so I am comfortable with it not having high precision, but the flickering reported value (shown in the DRO) is very odd given that it's a stepper.

Do I need to re-flash with each change of scale, or is modifying it in the .ini sufficient?

For reference, 
config: github.com/digiexchris/6x11-sg-grinder-l...reconfig/config.json
generated ini: github.com/digiexchris/6x11-sg-grinder-l...eld/LinuxCNC/rio.ini

but I have changed the scale to 11.64 (yes, very coarse) for the X axis but that's what was required to get 10mm of movement from G1 X10 with a surface grinder table driven off of the normal handwheel (it's quite a large movement per handwheel turn)


I think I'll change the microstepping up to 32k so I can get the scale number higher and see what effect that has on the stability of the reported position.

if i set the deadband to :
DEADBAND           = 0.0001

my DRO shows the exact position like 10.000 or 0.000
 
 

POSITION_FEEDBACK = COMMANDED