Advanced Search

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.  

hi, i interesting order this aliexpress 92 mesa clone board but how this setting, i want first flat cable connections use all output pins to stepper drivers and relays, and second connection must be setting all pins to input pin all limit, home, pendant,probe,ATC, etc. but how this make ? need something software or can linuxcnc change pin configuration new ? and then how wiring optocouplers all pins input, need chematic, what resistors need use and optocouplers and what all need, i think build own opto board input pins, and output connection make cheap paraller port card BOB can use 4-5 motors drivers. basic need cnc 4 motor and if want later build 4th axis lathe addon need 5th motor. but important understand how setting/config all pins new, and what need doing, second if pns has all setting need hardware schematic all input pins how i made this opto input safety own card. i have working cnc machine can carwing PCB to input card. but need shematic and part list what need made safety input card. and can this aliexpress 40$ mesa 7i92 board setting own pin configuration. and can linuxcnc add this all pins and port working. or need write new hall code or ini file code (what i not understand anythink and not know how write codes.

Hi @cakeslob nice to see you again.
I understand that. He was explaining that in case of h7xx they are using software spi for tmc and hardware spi for comms. But in case f4xx they are using same for both.
But after comparing both repos, I found that both are using software for spi for tmc and hardware for comms. So that is not the case.

NC program.
square with parameterizable size and corner radius.
with G10 L2 R can be rotated around the C axis.
I don't have the knowledge to create an NC program with any number of corners and G2/G3 radiuses