Hi yes, I have a cut chart for the cutter. BUT it does not specify a variable air pressure chat such as the one you have presented. So I think this could be useful. Thanks.

Separately, I was concerned about the configuration settings: mostly about the arc voltage etc... I read somewhere about a need to set the config of the THCAD2 into the settings of the Software based on a frequency... Cant remember where I saw that but the config setting are my main concern at the moment. The other thickness settings are in line with the cut charts for the machine.

That being said, I have literally never used a cutter, so have zero experience on how this should be set up. I live in Melb, AU. So if anyone local, would put on beers coffee or whatever for some localised help. 

Thanks Tommylight.
-Set up the THC, any fine tuning without it is useless when THC is active.
Ok. Will note

-25A for 5mm thick is way to low, roughly 10A/mm is OK
Yes this is already set to 40A in the 5mm profile

-with working THC, you need to fine tune air pressure (exclusively while the air is ON), voltage=cut height, feed rate
Ok. This I have definitely NOT looked at. Will do. Thanks.

-cut quality will vary based on air moisture, material being cut, nozzle type and wear, so use new nozzle for fine tuning and after you have things working properly
I have a three stage Breathing Dryer rig from when painting, + a standard dryer, so dry air should not be a problem. But the rest of it I will need to work through. Thanks.

My main concern was the settings in the Configuration setting, specifically arc voltage setting etc... Any thoughts on this? Do you have some that you may be using?

Yup, that's noise. Your scope settings are so "zoomed in" in time and voltage you probably can't see the real signals.

• Set your scope's Y axis (voltage) range to more like 1V/division. More if the signals are (eg) 24V.
• Set a trigger on a rising or falling edge, with a threshold of something in the middle of your signal voltage range. Eg, if it's a 5V system, set the trigger at 3V or some such.
• Change your X axis (time) to much longer. This depends on how fast you're moving the motor, but 25 ns is way too fast to see the signals you probably care about. Something more in the 100 us or 1 ms range probably makes much more sense.

If you do the above, you'll probably see step/direction signals, or quadrature, or something. Either way, it's very likely something LinuxCNC supports "out of the box". Engineers are lazy and generally don't invent new protocols if they don't have toimage missing /media/kunena/emoticons/smile.png

Thank you for all of your help Peter, I have finished all of my testing now the conclusion is clear.

Not able to help here but this is a continuation of the deprecation of Python 2.7 back when Debian Bullseye (v 11) was released. You need to convert your handler to Python 3. 

Update:
i have copied the "working" fies from page 1 into my axis.sim folder, removed the date in their names and put the Basic.hal to be called in the axis.ini file. now the axis.sim does not start and i get this error log: 
Print file information:
RUN_IN_PLACE=no
LINUXCNC_DIR=
LINUXCNC_BIN_DIR=/usr/bin
LINUXCNC_TCL_DIR=/usr/lib/tcltk/linuxcnc
LINUXCNC_SCRIPT_DIR=
LINUXCNC_RTLIB_DIR=/usr/lib/linuxcnc/modules
LINUXCNC_CONFIG_DIR=
LINUXCNC_LANG_DIR=/usr/lib/tcltk/linuxcnc/msgs
INIVAR=inivar
HALCMD=halcmd
LINUXCNC_EMCSH=/usr/bin/wish8.6
LINUXCNC - 2.9.8
Machine configuration directory is '/home/christian/linuxcnc/configs/sim.axis'
Machine configuration file is 'axis.ini'
INIFILE=/home/christian/linuxcnc/configs/sim.axis/axis.ini
VERSION=1.1
PARAMETER_FILE=sim.var
TPMOD=
HOMEMOD=
TASK=milltask
HALUI=halui
DISPLAY=axis
COORDINATES=X Y Z
KINEMATICS=trivkins
Starting LinuxCNC...
Starting LinuxCNC server program: linuxcncsvr
Loading Real Time OS, RTAPI, and HAL_LIB modules
Starting LinuxCNC IO program: io
Starting HAL User Interface program: halui
linuxcnc TPMOD=tpmod HOMEMOD=homemod EMCMOT=motmod
Found file(lib): /usr/share/linuxcnc/hallib/core_sim.hal
Found file(lib): /usr/share/linuxcnc/hallib/sim_spindle_encoder.hal
Found file(lib): /usr/share/linuxcnc/hallib/axis_manualtoolchange.hal
Found file(lib): /usr/share/linuxcnc/hallib/simulated_home.hal
Found file(lib): /usr/share/linuxcnc/hallib/check_xyz_constraints.hal
Found file(REL): ./cooling.hal
Found file(REL): ./Basic.hal
Shutting down and cleaning up LinuxCNC...
Removing HAL_LIB, RTAPI, and Real Time OS modules
Removing NML shared memory segments

Debug file information:
Note: Using POSIX realtime
trivkins: already exists
./Basic.hal:3: waitpid failed /usr/bin/rtapi_app trivkins
./Basic.hal:3: /usr/bin/rtapi_app exited without becoming ready
./Basic.hal:3: insmod for trivkins failed, returned -1
2381
Stopping realtime threads
Unloading hal components
Note: Using POSIX realtime

Hi maruf1777,

I’m an engineer with Teknic and I came across your thread. There are a lot of good recommendations from other users, and it looks like you’ve got some solid next steps to test. If you want direct help from Teknic, feel free to contact us at 585‑784‑7454 or www.teknic.com/contact/ and one of our engineers will be happy to assist.

Also to build on dbtayl’s quadrature note: when ClearPath is set to quadrature input, it treats each edge transition on the A and B signals as a count. So if you keep the same command resolution (counts/rev), the required signal rate on each line is actually 1/4 the pulse frequency you'd need when using step & direction. If your Mesa card supports quadrature output, you can set ClearPath’s Input Format to Quadrature in ClearPath‑MSP, which can help if you’re running into pulse‑rate limits or signal‑integrity issues.

Best regards,
Nick D. - Teknic Servo Systems Engineer

Stimmt das ist Pflicht 

thank you for this very helpfull hint!! it´s back online!!

the grandixximo repo did it!

cheers

miniwini

 

OK if you have +24V on TB1 pin 5 relative to TB1 pin 8
and no red LED above TB1 when LinuxCNC is not running,
The 7I76EUs field I/O section has failed or been damaged.

Lcvette wrote:

Maybe send as screen shot of your roster settings and probe page settings as well as your z travel.

Attached. I think this is what you were asking for.

Also have you edited your var file and added all of the parameter numbers shown in the probe basic docs so the settings are persistent?

Yes, my ini includes a ref to the var file. Settings are persistent across executions of LinuxCNC. Or at least I think so.

github.com/kello711/linuxcnc/blob/main/c...ntnc/probe_basic.var

Lcvette wrote:

Where is your zero home in z

Zero is at the top of travel with -6.3 at the bottom.