Advanced Search

Yes i am, i have 3 or 4 of those in daily use, 1 with Proma THC150 and others with Mesa THCAD.
I also have a china one with same electronics and pilot arc, the HF type, i intentionally wired the THCAD10 to the main terminals with 1MOhm resistors on each side, still in daily use for nearly a year, no issues.
The thing is, with correct wiring and grounding and shielding, it works fine, but any wiring error will result in burnt electronics the first time the torch fires, hence i refrain from advising such things.

Maybe this thread would get you going in the right direction.

forum.linuxcnc.org/subroutine-library/51...asic?start=10#336942

It works now...
I have two network adapter. One intern and one USB. My Internet was connected to the USB adapter. This doesn´t work. I switched to the intern adapter and now itś fine...

Are you sure, Tommy? It got HF start.

www.linuxcnc.org don´t work
Reddit    don´t work
Youtube work
Google  work

My Windows Laptop (WLAN) and my Smartphone (WLAN) have no problems

Works here.
Can you access google or youtube or www.linuxcnc.org ?

Nilres wrote:

All Stahlwerk Cutters have a build in THC Connector.

Black ones, maybe, the white ones not all for sure.
They are good and have a few years warranty, but aim for 70A at least, the exact one that Hakan proposed.

Hi everyone,I’m currently using Probe Basic UI on a 3-axis milling machine. Tool setting and probing are working perfectly — kudos to everyone who made that process so smooth.However, I ran into a potential issue. I noticed that the .ngc file generated from Fusion360 only prompts for a tool change (e.g.) without performing any actual tool change or probing routine. That’s risky — I almost started a job without realizing it wouldn’t automatically run the tool-length probing cycle after each change.I’d like to make the workflow safer and more automated. Ideally:

• Whenever a tool change (

  M6

  ) is called, the machine should automatically go to the tool probe and measure the tool length before continuing.
• No manual pause/resume or separate probe command should be required — it should just happen as part of the

  M6

  sequence.

Would this be best handled by:

• A custom M6 remap in the HAL/INI file, or
• A modified Fusion360 post processor (.cps) that inserts probing commands automatically after each tool change?

Also, I noticed another small issue:
The spindle starts cutting immediately after thecommand, without waiting for it to reach full speed. I know I can tweak ramp or lead-in settings in Fusion, but I’d prefer a permanent spindle-speed wait in the HAL or remap (something like a delay or “wait-for-at-speed” check).For testing, I’ve been running with the spindle disabled and using a pencil in place of the endmill — so nothing dangerous, just making sure all the logic works before real cutting.Any guidance or examples of how others have integrated automatic tool probing and spindle speed waits into Probe Basic or LinuxCNC would be much appreciated!Thanks in advance

I started looking into to this and while I haven't been able to pinpoint the cause yet I found these lines of code in vtk_backplot.py

 

The lines highlighted red and yellow seem to be duplicates of each other and the ones marked green don't seem to be used anywhere.


Digging a bit further it seems that the path_offset_start_point dictionary where the KeyError comes from only gets written to in one location (marked orange below).

 

So I assume that the dictonary is supposed to be populated with values via the VTKCanon class.