Thanks for the write-up and the machine tests. I am not a G71 expert either, so take this as “what I changed”, not gospel.

I am targeting native LinuxCNC 2.9** only (`G71 Q… D… I… R…`). In those docs, D is remaining distance to the profile (finish stock) and I is the cutting increment** (DOC). PathPilot uses a different letter set, so the two will not match; this tool follows the 2.9 page, not PathPilot.

On G7: I do not think diameter mode should halve D/I/R. In my view DOC is still DOC in G7 or G8 — the rest is just a display issue. Logical in my view is that depth of cut reduces diameter by DOC*2. G71’s increment is radius-based as well. Treating G7 as “divide the cycle words by two” also dragged in a lot of other mistakes (G72, retract, mixed scaling). I am not taking that path unless someone can convince me this is the way to go.

v1.1.0 is out with:

- G71/G72 letters swapped to that 2.9 meaning (UI labels too: DOC is I, stock left is D).
- L-shaped rapids instead of a diagonal `G0 X… Z…`.
- An explicit retract between G71/G72 and G70, so finish should not cut a corner through stock.
- Start/retract X now includes G2/G3 bulge past the endpoints, not just min/max of the points.
- Retract X is separate from a user Start X (so a bore start is not used as the pull-out).

I did not adopt G7 `/2` on D/I/R, cutter comp, or “finish only, skip G71”.

I have not had time to run this on a real machine yet, so treat it as untested on iron. Dry-run / sim first. If someone who lives on native 2.9 `G71 Q` can sanity-check the D/I mapping, that would be very welcome.

Profiler 1.1 is here

Just took a look at your drive manual, and it's... really sparse.

I don't know of anything in lcec or cia402 that constantly polls the drive(s) for communication status, but I had an idea that might be worth exploring...

What I was thinking is to use one of the drive's digital outputs as a tattle-tale.  It's not clear in the manual if the DOs reset on loss of communication, but on my Stepperonline A6's that's an option only found in the tuning software.

I can program my drives' digital outputs to either retain the last state or turn off if communication is lost.

If you can set yours to turn off, then you could create DO hal pins in xml file.  Those pins are then turned on in HAL whenever LCNC is running.  The DO is then connected to an LCNC input - a DI on a different drive or other Ethercat slave device.  That input is connected to motion.external-fault-NN - and it all acts like a drive communication estop.

If the drive is unplugged, the DO turns off... then input then turns off, which triggers an external fault in LCNC.

It all depends if you can set the outputs to non-latching in the drive tuning software and you have a spare input somewhere.

Reminds me I need to test my own system for an Ethercat cable failure.

I hope I’ve managed it now; it’s a bit tricky without the hardware

please set back to 16 values, update dev and try again

oh, no, my fault, i send number of bytes, not number of registers

i think the problem is, your device returns 4 bytes, not the requested 2 ?!?!



you need to pull dev to incrase the values, with my simulation it works, but it's a workaround,
i will write a fix, to read the values in the right order and ignore the last 16bit's

You can use mesaflash's --readhmid option to show the TB3 MPG encoder pinout:


 

I ran a couple of tests, and the raw Modbus data makes sense. The board's response is OK, and the data corresponds to the DIs that are ON.
Seems that the mistake is in the LinuxCNC HAL config.

IN1
> MODBUS_TX(mbus0): 1 3 0 192 0 2 196 55
 MODBUS_RXmbus0: 1 3 4 0 1 0 0 171 243

IN2
> MODBUS_TX(mbus0): 1 3 0 192 0 2 196 55
 MODBUS_RXmbus0: 1 3 4 0 2 0 0 91 243

IN1 + IN2
>MODBUS_TX(mbus0): 1 3 0 192 0 2 196 55
 MODBUS_RXmbus0: 1 3 4 0 3 0 0 10 51

new dev update:

go to mbus plugin-config and set the new debug flag

hope that help's

Hi Meister, I updated to the dev branch, but I don't see any difference. Is there any way to sniff the Modbus network?

@Oxbown please try dev branch, i hope it works now, have no hardware to test.
and please set the Register address to 192.

Hallo pcw,
das man die 2 MPGs anschließen kann hattest Du ja schon geschrieben, aber ich habe nicht auch nur die kleinste Ahnung wie?
Hans

Hi,
I am using Fuson 360 and QtPlasmaC. 
I am having the start radius - end radius errors that I see others have but don't know or understand the remedy. As far as I know I am using the second PP on the list below as when I go to import it, is says it already exists and do I want to cancel or replace. 
Clicking of the first link to QtPlacmac PP does not take we to a file for downloading. Is this PP somewhere and the link needs correcting?

Can someone help with a PP. or with instructions for a dummy on how to not get the errors
Kind regards  Trevor

phillc54 wrote:

This thread is for user donated post processors for CAM software that has no native post processer for QtPlasmaC/PlasmaC.
I will make this sticky and unlocked and just keep current versions here.
If there are posted comments or corrections I will delete them after they have been actioned.

Current PP's:

• Fusion360 - QtPlasmaC
• Fusion360 - PlasmaC (AXIS & GMOCCAPY)
• ProNest 2019
• SOLIDWORKS (CAMWorks)
• Inkscape
• PeddiNest

There are no third party PP's here for SheetCam, use the PlasmaC PP included with SheetCam for both QtPlasmaC and Plasmac.

PP creators need to be aware of the following:

• LinuxCNC does not allows analog/digital input or output while cutter compensation (G41) is active.
• QtPlasmaC disables G92 offsets.

All work product by the author is provided ​“AS IS”. The Author makes no other warranties, express or implied, and hereby disclaims all implied warranties, including any warranty of merchantability and warranty of fitness for a particular purpose.

Here are link of detailed explanation how to do it.

There is Lathe mode if you use Axis screen, follow video and select you machine propertis 





 

In what kind of way can i do it?

You can use pncconf wizard to build your hal