Advanced Search

Personally I would suggest tp use the .comp format:

linuxcnc.org/docs/2.9/html/man/man9/userkins.9.html

But regardless,
Forward kinematic uses the joint positions to calculate the cartesian coordinate positions 
Inverse kinematic uses the cartesian coordinate positions (ie the position commands of the motion planner) to calculate the joint positions (ie basically the commands that get sent to your motor drives)

One needs to be the mathematical inverse of the other (otherwise the values will run off and you will get limit violation errors)

I was able to check the connection yesterday, you were right, [GND pulse - dir -] I had them bridged. !!

I always connected them, I understand that it's wrong! I like to learn because the board can get burned with this connection. I thought that the ground from both the driver and the board should be connected.

thank you!!!

I just checked and I was actually on LinuxCNC 2.9.4. QtPlasmaC version is v2.9-238.315. Is that version effected by the bug you mentioned? I'm going to assume so since the gcode works for you.

I've also just deployed a new version of MetalHeadCAM to metalheadcam.alan-gibson.workers.dev/. I'd really appreciate your feedback on it as I'm specifically targeting QtPlasmaC.

The basic workflow is:
- Click the hamburger menu and then Tools so you can add your tool parameters
- Import a DXF file on the Import stage
- Skip the Edit stage for now as it doesn't do much yet
- Click the topmost Apply button on the Prepare stage
- Add operations to parts and shape chains on the Program stage, making sure to select what you want to cut in the Apply To dropdown.
- Simulate the program on the Simulate stage or just skip it
- Download gcode on the Export stage

Hi All,
I've just released an update that provides improved lead in/out support. Any feedback is of course appreciated.
 

qtdragon.probe-error pin is an I/O pin not an input pin.

I'll have to think more on the best way to add external error checking/handling.
It's a problem spot for linuxcnc.