Advanced Search

Try and use the pin 'hm2_7i76e.0.7i76.0.0.input-29' in your hal instead of 'hm2_7i76e.0.gpio.029.in_not'

i have made the changes to the static IP and now i have a much smaller latency (about 0.100, 0.150)

i can "torch pulse" how many times i want and it will never have problems with the plasma ON.
i even have done "torch pulse" piercing the material, moving left, piercing again with torch pulse, etc.
i can run the G-Code how many times i want, without any problems, with "torch OFF".
i can run the G-Code how many times i want, without any problems, with "IGNORE OK", and "TORCH ON", and the plasma source itslef OFF, so the relay fires but there's no arc.

if i have "torch ON", and the plasma source ON, when i run a g-code, it will pierce the first time, and at the second time to pierce, it will give me a joint following error and "Error finishing read! Iter (...) "

my next attempt is to replace the mesa board and the relay..
 

Using LINIXCNC 2.9.2 on Debian 12 in combination with a Mesa card 7i76e. Both limit switches of each ache are setup in parallel (LJ12A3-4-Z/BX  like NPN) with a pull-up resistor of 100k ohm. My Aches are attached to mesa digital in X => 27, Y => 28, Z => 29. The signal has to be inverted because is up if the limit switch is not used. So far so good. Now configuring my LINIXCNC to have a shared both limit and home together.net both-home-z     <=  hm2_7i76e.0.gpio.029.in_not
net both-home-z     =>  joint.2.home-sw-in
net both-home-z     =>  joint.2.neg-lim-sw-in
net both-home-z     =>  joint.2.pos-lim-sw-in
 The INI contains this settings for the Z-archesHOME_OFFSET = 0.0
HOME_SEARCH_VEL = 2.000000
HOME_LATCH_VEL = 0.500000
HOME_FINAL_VEL = 0.000000
HOME_USE_INDEX = NO
HOME_IGNORE_LIMITS = YES
HOME_IS_SHARED = YES
HOME_SEQUENCE = 1
 Now to the issue, if I home the machine the limit switches get ignored. This applied to all aches. To simplify the troubleshooting I focus on Z-aches only. If I use a piece of metal and hold it in front of the limit switch the mesa digital in 29 acts as expected, but not the chained signals.

Any advice are welcome.

Here you go:

In essence: BLDC component in "qi" mode, ferror set at 5000 mm and belt removed. I can jog the motor back and forth with D = 1, but it immediately runs away as soon as set D = 4 and press "test".

I have attached INI and HAL files

What's missing from my HAL file. I cannot do protection if the requested RPM of the spindle do not follow the current RPM from the encoder.

 

 

The problem is that the machine should automatically stop if the pump is not working.  The spindle is large and if left without lubrication the bearings will break.
 

Please see the attached photos. It should be here!

 

 


I would be happy if you could share pictures of your electrical cabinet. And results from the first chip!
Have you measured the accuracy of the machine (90 degrees X and Z  , 90 degrees Y/Z , Linear deviation along X)

Die Signale der Homeschalter sind in der HAL nicht verknüpft.

in deiner HAL ändere diese Zeilen:
zu:

I have the same io card. I have configured digital input and output, analog input and output, counter input and pwm output. Now the only thing left is the encoder. The encoder of this io card outputs the count value without abz phase. How to convert the count value to abz phase?

Hallo Norbert,

Die Verfahrgeschwindigkeit geht jetzt. Danke
Endschalter in hal überprüft, sie funktionieren.
Beim auslösen der home-sequenz, endschlater in z wird überfahren.
Maschine not aus ausgelösst...

Anhang: ini und hal

Hi, I have a problem setting the probe. I updated the .ini file (which I attach) following the guide. the program does not start, there is the following error:
Traceback (most recent call last):
  File "/usr/share/qtvcp/screens/qtdragon/qtdragon_handler.py", line 700, in slider_rapid_changed
    rapid = (float(value) / 100) * self.factor
                                   ^^^^^^^^^^^
AttributeError: 'HandlerClass' object has no attribute 'factor'
 

3 years is a long time in this space.
I would try installing the Raspberry pi 5 image on the downloads page and then follow these instructions
forum.linuxcnc.org/ethercat/45336-etherc...-how-to-step-by-step

The ethercat repositories should be installed for you already so hopefully, you will find there is no need to build from source if iGh supports the pi5 now.
 

Hi Hakan,
I am using Raspberry pi5. I build Linuxcnc from source code .now i started installing ethercat from source code following your notes but now i am facing some issues in etherlab master build ($make dkms_build) in this line.
i also attached output log. is there any other way for RP5 ..?    

I added a few more properties that can be set from stylesheets to the gauge and LED widgets

Thanks,spumco.I quite agree that "LCNC has a steep learning curve".I'm been learning the linuxcnc about 2-3 months,so far by now,I can only configure a simple lathe or a simple mill machine,knowing a little about the hal ,maybe able to connect the general hardware by writing hal,using qtvcp to write a custom UI ,and invoke the linuxcnc 's action with python.

But for the advanced configuration such like making one servo motor both as spindle and C-axis,I've no clear map about this.I've read many topics related to this ,but due to the lacking of the strong basic knowledge,I can only understand some.Generally ,the solution seemed to use the spindle orient component to achive it (of couse,need to using other component like encoder/abs/mux2 etc.) ,it's a little complex for and the key barrior for me is that I can only controll or configure the hardware using Ethercat, and the solution seems not workable for Ethercat servo motor.but some hardware using PWM or VFD,which is unfamilar to me .

So,at the current stage,considering my poor basic knowledge about the linuxcnc.it's better to have a solution using Ethercat controlled servo motor,which can let me switch the mode from spindle to C-axis or from C-axis to Spindle ,at least I 've not found it yet . If there is a workable and mature PWM or VFD solution ,I'll also have a try .I head of that using spindle and C-axis as one is very simple in Mach3,I dont know if it is true because I never used Mach3, hope to find a good solution in linuxcnc to achive this functionality.

Perfect, that would be an excellent example for the plasmac docs now you've written it!
It shows how to support a third party CAM without any changes to the post processor and it includes a few enhancements to the existing examples.
Plus its a real life example (for Hypertherm Nestmaster)