Advanced Search

  Hi,

I have now created another configuration for 1 axis and tested it on each servo. Each servo is responsive and the pdo mapping is now correct. Now I have created the complete configuration and am getting the following error 
HAL: ERROR: duplicate variable 'lcec.0.A6.control-word'
LCEC: exporting pin lcec.0.A6.control-word failed
LCEC: failure in proc_init for slave 0.A6

Where am I going wrong?
 

That worked but ultimately what I'm trying to do is add that line to my custom_postgui.hal file. 
My glade file works good but there is one LED that I can't get working. 

glade.pdt_motion_control.hal_led1
And
pdt_motion_control.hal_led1

As used in the picture in custom_postgui.ha,  neither will boot Linux CNC and both give message pin doesn't exist

Thanks
Kent

Thank you, Andy, and sorry for pestering.

tommylight wrote:

Am i understanding this correctly:
A software solution was implemented in LinuxCNC for a hardware problem/issue ?
It does seem like it, or what am i missing?

Not really. The problem was that LinuxCNC was setting the status to "not probing" before the end of the deceleration stage of a probe move. In cases where the probe triggers more than once (as many will) this led to a "non probe move" error during a probe move. 
Discussion here:
github.com/LinuxCNC/linuxcnc/pull/3534
In response to this bug report:
github.com/LinuxCNC/linuxcnc/issues/2926

 

Can you upload a back of your configuration made from clicking BACKUP CONFIG on the settings tab inside of qtplasmac please?

hi
Machine reaches the requested speed while cutting. 1000
I have all the default settings on the Parameters Page.
Tried with VAD 60%. still does not work.
Also M3 $0 S1 does not work.

Does the machine reach the requested speed while cutting?
If it does not, it will not turn height control on.
What are the settings on the Parameters page?
Set the VAD to 60% first and try again.

hi,

The Z axis DRO will not move in spite of the following in Raspi 4/5:
a. torch on
b. THC enabled setting
c. HALSHOW is showing move up and even.
d. After trying the changed settings mentioned previously on proma.
e. Mode is 2 for the external THC
Please help as I have been trying to do the same for few weeks now and let me know if any settings need to be added in the HAL or ini.

# ---JOINT ASSOCIATED WITH THE Z AXIS---
net plasmac:axis-position joint.3.pos-fb => plasmac.axis-z-position


 

I rejoiced too soon. After 17,000 measurements 2.9.7, the error forum.linuxcnc.org/38-general-linuxcnc-q...bing?start=10#338958

this won't work either in sim mode or in reality, I tried something via chatgpt but I know that it doesn't work, it can't create a routine. here is my configuration if anyone is free to look at where the error is and what needs to be added in Hal eventually. Tx m6 works but will not return the tool to its pocket when you give it another tool, it also reports in the bottom line that there is no tool even though in reality it took it. each pocket has its own active high sensor on inputs 16-21 and the spindle has a sensor for ``flush'' input 10 the tool is in the spindle, input 12 reports that there is no tool in the spindle. Thanks 

youtube.com/shorts/CXxlm92xtt8?si=KCv1wBtX9AL_1eM2

 

Perhaps due to the language barrier, we are misunderstanding each other.
1. There was a bug in version 2.8.4, which was fixed in 2.9.7.
2. Instead of fixing the bug that was interfering with the operation, they created a new one for which there is no solution.

However! First, I used a steel probe (before electrical contact) as a probe. Then I bought a Chinese Probe sensor (a so-called center finder). It did not suit me for a number of reasons:
1. Unacceptably high operating force (“out of the box” 450 grams, with my processing “with a file” (and a hammer) about 220 grams.
2. speed of operation
In version 2.8.4, I got 50,000-80,000 continuous sequential measurements at a rate of 5,000-6,500 per hour. But in version 2.9.7, the usual error for 2.9.7 appeared

And the other day I made my own version of such a sensor. The actuation force is 15 grams. The operating speed is higher (to such an extent that during G0 movements, the vibration sensor is triggered). But in version 2.8.4, I haven't exceeded 10,000 continuous measurements yet. In version 2.9.7, I got up to 12,000 measurements per hour, and now (tests are being conducted right now) more than 13,000 measurements without errors.

Conclusions: it is quite possible that version 2.9.7 works adequately with high-quality sensors.

Edit:
i just realized that I probably have the same problem as @dschultz.
I just don't know how to switch to variable PDO mapping?

I believe the real issue was the drive didn't like the PDOS I had in the xml.
Even though my original settings were one of the "Fixed PDO mapping" options from the manual (1704 & 1B02).
Anyway, I switched it to the "Variable PDO mapping" 1600 & 1A00 and the drive goes to OP mode and comes alive when I enable the machine!

Has anyone had success with setting up the CIA402 homing mode?

Very cool. That little lapping machine is awesome.

andypugh wrote:

The updates in 2.9.7 fix (hopefully) a bug where the "probe triggered during non-probe move" error was raised when the machine was actually probing (due to probe contact bounce). 

Am i understanding this correctly:
A software solution was implemented in LinuxCNC for a hardware problem/issue ?
It does seem like it, or what am i missing?

AkkiSan wrote:

It kinda improved, but the „probe triggered“ fault is still happening.
I was not able to finish even shorter milling programs (<5 mins).

The updates in 2.9.7 fix (hopefully) a bug where the "probe triggered during non-probe move" error was raised when the machine was actually probing (due to probe contact bounce). 

If you are seeing the message when _not_ actually probing (and you refer to a 5 minute milling cycle, with no mention of probing) then that is a different issue.