Advanced Search

I'm afraid ChatGPT will just be a time-sink here.

I suspect the easiest current path would be to make a pncconf  QTPlasmac/THCAD configuration
for a 7I95T (This requires updating to the very latest LinuxCNC master as 7I95T support was just added
about 1 week ago) This configuration will match as far as encoders, inputs, and outputs go (though will show
more inputs than the 7I97T has, so just don't use any inputs beyond input 15)

When creating the 7I95T configuration, setup step/dir axis.  and encoder feedback. This will create the
basic PID loop structure  required for changing over to the 7I97T PWM/analog axis configuration.

When this is done, you will have a step/dir configuration for a 7I95T and QTPlasmac/THCAD.
Next you will need to change the card name in the ini file to "7i97".

then the created hal file will need to be edited to change the PID feedback input from stepgen
position to encoder position and the PID output from stepgen velocity to PWM value.

There are also enables and some PWM setup needed. I can help with these when you get a basic
hal file setup. 

You can use this example of basic 7I97/7I97T PWM hal file setup:

 



 

I start the program with an external button.

Well, yes but what hal pin do you use to start the program?
I presume 'halui.program.run'

pippin88 wrote:

Suggestion / request:
Overrides
When starting a program running (cycle start): user is prompted that an override (rapid, feed, or spindle) and asked whether they want to continue with override, or want to reset to 100%

I could imagine make an optional warn dialog with a settable limit. For all overrides? Feed, rapid and spindle?

Maybe a stupid question, but how do you use the relay on those cheap MACH3 BOBs with the 7c81?

For the inputs to work I need to enable the pullups on the 7C81.
But enabling the pullups makes the relay close as soon as the BOB is powered.

Ideally I would want the relay to be open until linuxcnc is started and I tell linuxcnc to close the relay.

But the relay closing by default due to the pullups makes it unusable, or did I miss something?

I cut a lot of thicker material that needs a ramp pierce.  I am thinking of adding ramp pierce parameters to the material database along with adding ramp pierce to the conversational area of QTplasmac.   My purpose for this would be to keep all the cut info in one place and to be able to use the conversational on thicker parts vs having to CAM simple things.   Just thought I would see if there was interest in this from others and/or other thoughts on it.

Normally you would use a NC switch for Estop and the you would use the true (no -not)
input to sense it. This is so that when Estop is not activated (switch = closed circuit),
iocontrol.0.emc-enable-in will be true so no Estop. Then when Estop button is activated
(switch= open circuit), iocontrol.0.emc-enable-in goes false, signaling an estop event.

Did you verify that estop-ext changes state when you change the Estop button from on to off?

This time, the spindle didn’t stop. However, when exiting the editor, the graphical interface shows that the program is not running

youtube.com/shorts/axVyF3tfrcw?si=d6pKXhjEwYUU1QWp

youtube.com/shorts/ay-Nz62fcPs?si=QHA_4l6xV2o7P6Ro

Thank you, the wiring is making much more sense and less challenging now.  

Im using linuxcnc_2.9.4-amd64.hybrid.iso that I downloaded here.  It installed qtplasmac 2.9.  Is it recommended to install 2.10?

What is the easiest way to configure a 7i97t and a couple thcad2 for plasma?  I dont see 7i97t as an option in pncconf and in mesact there isnt an option for qtplasmac.

I asked chatgpt to create a quick ini for qtplasmac and a 7i97t and it came up with this pretty quick: