Advanced Search

Your errors show that there are some missing file paths. There are probably defined in your ini file.
The most likely issue is you are using a new user name.

However, also Python V 2.7 used in 2.8 was deprecated. Later versions of Debian use Python 3
I thought there was also a python syntax error so you may need to convert your script to Python 3.

Estley wrote:

I swapped computers for a i5 and now it all works fine, thanks!!

Perfect!

Hello,
I try to use a machine, which was flawlessly working under LinuxCNC 2.8.4 (LinuxMint 19.3), in LinuxCNC 2.9.8 (LMDE6), but no success.
It is a basic Milling Machine (GMOCCAPY), with added support for VistaCNC-P4S and some python scripts and macros for tool touch off.

I tried the full featured ISO for Debian 13 Trixie with LinuxCNC 2.9.8, getting the exact same result (error).
I tried setting up a new machine using PNCconf, wich works fine. As soon as I add the necessary lines for either the VistaCNC-pendant OR the lines for the touch off, I am getting the attached error down below.
while starting the machine, I can hear the relais clicking, but the GUI never shows, the error prompts before.
I tried using the the new python scripts from the sim directory, but no success.

Can somebody sparky shine a light here? what exactly changed between LinuxCNC 2.8 and 2.9 to make those machines incompatible?

My Installation:
-LMDE6-ISO, checksum checked.
-sudo apt-get update / upgrade
-sudo apt install linuxcnc-uspace -> gave me 2.9.0 wich threw the same error and was not wanted.
-downloaded linuxcnc-uspace_2.9.8_amd64.deb from linxCNC.org
-sudo apt install mesaflash
-copying files for VistaCNC-P4S and "make install".

Any help appreciated! Many thanks!
Cheers.
Martin.

 

I swapped computers for a i5 and now it all works fine, thanks!!

I'm having a problem where after I zero-out the Z axis, some of the time, it seems to be "forgotten" when I run the program. Before running the program, I can jog to (0, 0, 0) and the tool tip is in the right place, but when I run the program, the tool either cuts way above (annoying, but no harm) or way below where it should (crash, piece ruined). I can't quite put my finger on workarounds like re-setting Z, re-loading the program, etc. Often the second time I run the program is works fine. The X and Y setting is always fine.
What could be going on here?
What can I do to get to the root cause?
All ideas are welcome. Thanks
 

It's not a laptop, it's an i3 mini PC, I'll swap it for a i5 I have laying around and see what happens.

I'm a huge fan of your videos, I was actually watching one of them when you replied!!

The Mesa configuration tool does not generate bitfiles, it uses existing bitfiles
If you need a 7I97+7I89 configuration I can build that but it may require dropping some
encoders. Do you need all 14 high speed encoders?

On the watchdog timeout, what error do you get from LinuxCNC?

(Easiest way to log these error is to start LinuxCNC from the command line
all error will be printed there.
 

7I80HD configurations (both -16 and -25) for 7I48+7I52

 

No PktUART support not sure if you expected MODBUS support on this
I can add this later if desired

Congratulations! Your work is appreciated.

Dear Chris,

i wanna thank you for your help at first.Ive put your file in the given path under the name vacuum_popup_handler.py as i thought its a own handler data for the popup, qtdragon_hd_handler.py is already the main handler data for the whole programm or did you mean to add it in the main code? Then i did the EMBED Part like

DISPLAY = qtvcp -d qtdragon_hd
EMBED_TAB_NAME = vacuum_popup
EMBED_TAB_COMMAND = qtvcp vacuum_popup
EMBED_TAB_LOCATION = DIALOG

I think this is the way u meant it. Ive also safed the vacuum_popup.ui under qtvcp/panels/vacuum_popup/vacuum_popup.ui.Ive posted the crash code. It tells me a TypeError "Wrong base class"

There are many factors that can cause your issue, often due to periodic background processes. Normally I would say set the coalescing settings but that seems to be OK from your data.
I did a video series on tuning the RT Kernel including network optimisation.This should fix it. 
youtube.com/playlist?list=PLG0NtQtZPZyo1...&si=XD8x3y7Zi9gPbya4

Tak jak w tytule po instalacji Debian 13 nie mam języka Polskiego.
Jak mogę to naprawić ?

This PC may not be suitable. Is it a laptop? If so, replace it with a desktop.
There is no simple fix as it is a culmination of things required to tune the RT Kernel.
But before you give up, follow the steps in this playlist
youtube.com/playlist?list=PLG0NtQtZPZyo1...&si=XD8x3y7Zi9gPbya4

Hallo

Seit langen wieder eine Frage.
Meine aktuelle Eckdaten.
-Lenovo W520 
-Linuxcnc 2.9.8  auf Debian Trixi
-Mesa 7i76e

Ich habe folgendes Problem.

Meine Servo thraed schiesst  sporadisch in die Höhe und es führt zum Abbruch von Linuxcnc.

Meiner Meinung scheint der Netzwerk Controller Intel 82579LM sporadisch zu aussetzer von rund 1Sekunde.

Jetzt ein paar Fragen.

1.Welcher Treiber wird von Debian Trixi  für Netzwerk Controller Intel 82579LM benutzt?
   - e1000e ???
2. Wie soll ich folgende Abfrage "ethtool -c enp0s25" interpretieren  ?

Ausgabe:
3.Warum werden nicht alle Einstellungen angezeigt?
4.Kann man den Netzwerk Controller Intel 82579LM so einstellen, das ich die Aussetzer weg bekomme?

Ich hoffe mir kann einer von Euch was zu diesem Thema sage.

Gruß Califax


 

Hi,

Using soft vs hardware SPI was not the point here. You are free to use soft or hardware SPI for the TMC; both repo use software SPI, but I ported the tmc module to a rp2040 using hardware SPI.

The important point was, as cakeslob mentioned, that those two SPI function cannot use the same pins, as once it is a slave (comms) and once a master (tmc). So, if you want to use tmc module on the Octopus pro, you will have to connect the Rpi on a different SPI port, using different pins. Again, I don't have a board but according to the manual, SPI channel 3 is exposed on J74 connector and could be used for comms.