PlasmaC encoder .00.velocity question

I am wondering if I am connecting to encA+ and encA- on the 7i76 TB3, why I would reference 7i92.0.encoder.0.0.velocity.

Where is the connection between that signal and 7i92.0.7i76.0.0.enc0 which is where I am connected?

I am a bit confused with this as I am ready to pull the trigger to do the PlasmaC config. Everything is connected and working even thcad is connected but not tested.I just need to know if I put 7i92.0.encoder.0.0.velocity in as Arc Voltage for mode 1 it will connect somehow to enc0 which is where my thcad is connected.

hm2_7i92.0.encoder.00.velocity would be correct

7i92.0.7i76.0.0.enc0 would be MPG encoder count 0

PCW wrote:

hm2_7i92.0.encoder.00.velocity would be correct

7i92.0.7i76.0.0.enc0 would be MPG encoder count 0

So, enc0 and enc1 has nothing to do with encA on TB3 of 7i76?

No, they are associated with the MPG encoders on field inputs 16,17,18,19

snowgoer540 wrote:

bevins wrote:

I am a bit confused with this as I am ready to pull the trigger to do the PlasmaC config.

Have you considered doing a QtPlasmaC config instead? Development has now stopped on PlasmaC. All new work will be done to the QtPlasmaC project.

It also has a lot of new features that were not possible with PlasmaC being on top of Axis or Gmoccapy.

Here's a link to the manual: linuxcnc.org/docs/devel/html/plasma/qtplasmac.html

When does the madness end? This is a customers machine that needs to be delivered in a week and a half.
The machine is working and I am able to draw files with a pen. I just did PlasmaC config and that seems to be working although I didn't do any plasma testing or anything.

Is it worth going the QT route? I have had issues with QT before and it was very quirky and I was never able to get it going on one machine.

I am running on linuxmint 19.3. I am wondering if it is worth it or not. I have nightmares about QT....

snowgoer540 wrote:

bevins wrote:

snowgoer540 wrote:

bevins wrote:

I am a bit confused with this as I am ready to pull the trigger to do the PlasmaC config.

Have you considered doing a QtPlasmaC config instead? Development has now stopped on PlasmaC. All new work will be done to the QtPlasmaC project.

It also has a lot of new features that were not possible with PlasmaC being on top of Axis or Gmoccapy.

Here's a link to the manual: linuxcnc.org/docs/devel/html/plasma/qtplasmac.html

When does the madness end? This is a customers machine that needs to be delivered in a week and a half.
The machine is working and I am able to draw files with a pen. I just did PlasmaC config and that seems to be working although I didn't do any plasma testing or anything.

Is it worth going the QT route? I have had issues with QT before and it was very quirky and I was never able to get it going on one machine.

I am running on linuxmint 19.3. I am wondering if it is worth it or not. I have nightmares about QT....

What madness? Did I miss something?

If it's a customer's machine and you're happy and they're happy...then let 'er eat. In this case maybe it's best to get more miles under the QtPlasmaC belt via other people's use.

I didn't mean to give you nightmares, just wanted you to be aware since you said you were making a new config.

Madness meaning never ending changes......

Yeah, Is it ready for prime time?

Also is sheetcam being used for CAM with PlasmaC and QTPlasmaC? Any issues I need to know. Is there any setup to do I need to know that is documented somewhere?