Advanced Search

For some time now I've enjoyed a stable system created using the LinuxCNC 2.8.2 Debian 10 PREEMPT-RT ISO.   But now that I've upgraded to Debian 12 (I wanted to install a package unrelated to LinuxCNC, and the Debian 10 repository is no longer supported), things have fallen apart.  After the transition, LinuxCNC was still present, but it would not launch.  I assumed that this was because it had run in kernel space in my original system and so was treated specially (e.g. executable not in "bin").  Was this so?  In any case I installed linux-uspace.  It launches as expected, but unfortunately produces a string of error pop-ups:  "Smart Serial Port 0: Dolt not cleared from previous servo thread", "Error finishing read", and so on.

The hardware and BIOS are exactly as they were when things worked perfectly. LinuxCNC is 2.9.5 and the kernel is 6.1.0_39_rt_amd64.  Pinging the Mesa card gives consistent times of .125msec.  The latency looks generally  reasonable, but the histograms show a significant number of extreme outliers (???).

 

Can anybody help?  I feel that its probably a case of some option not being set correctly (i.e. the kernel isn't really pre-empting, LinuxCNC doesn't have the highest priority, or something such).  What might be missing somewhere in some configuration file?

There's also a little matter of the Axis window not maximizing, but this is a relatively minor concern.

 

Okay, so would the equivalent allow it to become operational?
Do you have a little more guidance as to what I'm looking for, because I still don't really understand what I'm looking at or for. I have a list of seemingly all of this drives pdos/sdos and their descriptions.
The manual says the drives conform to CiA402, but I don't know what all that standard includes-I assume based on your comment that the registers are separate from the standard?

Thanks Rod

When AI reports info from a post of mine on the forum, you know it at best is only superficial.
There is an example in the docs on a mpg using an encoder. It is easy to convert to a Mesa MPG encoder input but I think on the 7i96s you need extra firmware from mesa web site and forgo some I/O pins.

With a safety relay, usually you would implement a momentary latch button to enable the relay.
Then a  pin on the relay should be connected to  iocontrol.0.emc-enable-in to tell linuxcnc the machine is enabled.
You will still need to press the machine on button in axis.

Also, if you don't have the external latch button, you can use iocontrol.0.user-request-enable instead. COnnect to the pilz latch. It sends a momentary latch signal to the relay when you enable linuxcnc
 

LinuxCNC-RIO - Mesa 7c81 - 7.14 KHz loop - 4x400W AC-Servos

www.youtube.com/shorts/DAJdqbjLjDQ

0x2000 and 0x2011 seem to just not exist
This could be correct as these are from a manufacturer specific range so not CIA402 registers. . You need to review the manual for your drive
 

Bonjour,
Je suis trés intressé pour la création d'un post pro full 5 axes sous NX . 
Existe il plus de documentation pour cela .

Merci

OK, the problem was my understanding (or lack thereof) of HAL I/O pins.

I was able to resolve this particular issue by using the custom component passthru from this post: forum.linuxcnc.org/forum/24-hal-componen...id-pin-problems#6489

It looks like I could have also used the existing component TRISTATE_BIT as well.

I guess I don't understand what the purpose of a HAL pin for a dialog box is, if that dialog box can't be set within HAL. Is the idea that the dialog box should only be opened by a Python file?

As for the probe error routine handler function - is there any way to prompt a user and wait for input from within a running python routine?

I just tried this and it works fine

That would have to be done in your custom Python code using the sliders valueChanged() signal to trigger a call to your function and use the setMinimum() function of the slider to change the minimum set point.

JT

Hi, 

​​​​​​JT thanks for your reply.
additional for this situation question. I have two sliders. Usong Slider1 user may choose value 10..20. slider2 could be 0..100 . But if slider1 is more than 15, Slider2 could be only 80..100.
How i may realise this?

Thanks in advance.

jpg wrote:

Spumco hasn't said anything since... 

I've been on an LCNC hiatus for 6 months due to some other work eating up all my free time.

I've still not gotten the new spindle motor completely hooked up and tested, much less tried Aciera's fix.  Hoping to get back to it in the next month or so now that the outside work has finished.

I found the probe signal problem and got the EasyProbe screen to come up.
Something is still wrong - clicking any probe button gives an error:
EOF in file: /usr/share/axis/images/axis.ngc seeking o-word: 0<probe_x_minus> from line: 0
I also do not have the Probe Signal LED working. So, my "fix" of the probe input error must have broken something that does not cause an error message on startup.

It also gives the following error when I press the home button:
"emc/task/taskintf.cc 976: Error on joint 0, command number 74"
if that helps at all...