Dynomotion Forum

You don't need the conversion. Tom was highlighting what the 0.017xxx number was doing.

All you should need is

turbothis wrote: ↑

Mon Jan 22, 2024 11:46 pm

ok
what is the (PI/180) ?

Pi/180 = 0.0174533
It's how you convert between Degrees and Radians.

Thanks Tom, that looks like the correct function. I've just spent this evening doing the ground work for dual state controls (aka controls that can change depending on a bit status), and my head is now burst from trying to remember LinQ, however I now have a filtered list of controls that now just n...

Tom, I'm not sure that's the right function, as that only appears to handle the main DROs, and Spindle Speed/Feedrate, not the DROlabels (one's that can be set to monitor a Var, with a C program on the Kflop being able to output to them). Although that has reminded me I need to add the spindle and f...

Noticed I created a bug that prevented the File and Thread from being saved for User Buttons, so I've deleted the file from the previous post and attached the latest version to this one. Tom, how are DRO Labels handled? I've tried searching the KMotionCNC code for them, but I'm struggling to find th...

This is the latest version. It's only the basic .exe, so you'll need to combine it with the previous download to get all the additional files. DRO set buttons can now be added/removed/edited, although the popup is currently hardcoded (I do appear to have a bug with setting/zeroing the Z axis, but I'...

Thanks Tom.

I'll add it to the list of things to think about, as although I'm not using Action Indexes for my own user buttons, I can see the benefit of replicating that functionality in some form.

I've just finished adding the code to control bits, and was making some checks with KMotionCNC. As part of executing programs with a User Button, I noticed KMotionCNC allows you to set a Var. Is this ever used with a User Button, as I can't think of how it'd actually be used, given I don't think a u...

Just realised what I've been doing wrong. I've been writing the values to the DROs before calling ConvertAbolsuteToInterpreterCoord/Machine(), so I was writing the absolute values to the DROs, and as I use the same variables for reading the absolute values and writing to the DROs, I was only getting...

I'm back looking at the core functionality, and have already fixed a big bug I introduced in the DRO colours, but I'm struggling with the DRO values and I can't remember if this is something I've had an issue with before or not. If I enable my test machine, the DROs start at 0. If I then jog say 1mm...