Advanced Search

Vie viel stepper treiber sind benutzt?

Liegt vermutlich nicht am Controller sondern eher an der hal programmierung.

Im Gegensatz zu 'HALFILE' wird für 'POSTGUI_HALFILE' nur ein Eintrag in der INI berücksichtigt. Wenn du mehrere postgui halfiles laden willst dann musst du eine neue Datei anlegen (zb 'postgui_call_list.hal') mit diesem Inhalt:

Dann in der ini diese 2 Zeilen:
mit dieser ersetzen:

Zur Fehlersuche kannst du dann mal eine Zeile in der 'postgui_call_list.hal' auskommentieren um den Fehler ev. auf eine der zwei hal Files einzugrenzen.

Does Mesa have 5V power?
Measure that also.

Okay, damit werfe ich meinen Controller weg (ich mag ihn so sehr).

Ich habe jetzt getestet und ca. 10 Starts und Referenzfahrten gemacht, bisher ohne Fehlermeldung.
Ich werde das noch ein paar Tage so lassen und schauen, ob der Fehler wieder auftaucht.
Wenn nicht, liegt es am Controller.

You don't _need_ it, those are simply used to define the pose for (x,y,z,a,b,c)=(0,0,0,0,0,0).

[edit]

Actually I just noticed that you are not getting an 'axis' limit error but a 'joint' limit error. So the issue is that you have to adjust your 'MIN_LIMIT' , 'MAX_LIMIT' values in the [JOINT_1] section of your ini file. Note that joint1=0 has the upper arm in the horizontal forward pose as that is what is used in the genserkins model so you may need to adjust the limit values accordingly.

www.linuxcnc.org/docs/2.9/html/sv/motion/dh-parameters.html

 

Benb wrote:

Attached is a step by step pdf file that I use to install linuxcnc rip, The procedure assumes you have installed clean Debian 12 in your computer.
 
 

Much thanks Benb, I have installed "LinuxCNC_2.9.2-amd64.hybrid" updated to 2.9.3 thru synaptic package. Can i follow the steps in PDF for this install?

Hallo zusammen, Ich habe noch einen kleinen China Laser den ich jetzt gerne parallel an meiner Fräse betreiben möchte. Ich verwende ein Mesa796S zu Steuerung der Maschine und als Gui AXIS und Probebasic.Mit Pncconf Wizard habe ich die Maschine eingerichtet und habe dort die Firmware 796S_d ausgewählt. Die Maschine läuft sehr gut und Störungsafrei. Wenn ich jetzt den TTL gesteuerten Laser über den Befehl M67 einschalten möchte benötige ich einen 2 PWM Kanal, den ich zum Beispiel auf den Ausgang 3 legen möchte um den Laser in der Leistung zu steuern.. Kann mir bitte jemand erklären wie ich einen 2 PWM einrichte, oder wo kann ich eine Firmware für 2 PWM runterladen? Vielleicht mache ich ja auch einen Denkfehler? Gruß Rainer

Tightening the gibs has reduced (but not eliminated) the error. Pulling on the table to prevent the rocking improved it a little more but resulted in the 45 degrees being different.

As I understand it, 'iocontrolv2' has been removed in master:
github.com/LinuxCNC/linuxcnc/pull/2497

Using a remap seems to be the suggested alternative.

rc.local is absent.

However, I somehow managed it.

In case someone need to do the same, steps are given below.

1. Find out Interrupt number for network device by 'watch -n1 -d cat /proc/interrupts'. in my case it is 32.
2. Check your last CPU number. In my case it is CPU1, so 'echo 2' to be set. This link may be helpful: bitsum.com/tools/cpu-affinity-calculator/
3. create two file as attached in my post above dated 14 Oct 2024 12.33. Put them to respective directory as mentioned. chmod a+x for both files.
4. go to 'Setting', then 'Session and Startup', then under 'Application Autostart' tab, click 'Add'
5. under command, type "sudo systemctl start irq32affinity.service", Trigger 'on login', save.
6. go to '/etc' directory, open terminal, type 'sudo geany sudoers'
7. add '<user name> ALL=(ALL) NOPASSWD: /usr/bin/systemctl' at the bottom. putting in middle may not work.
8. save and close geany.
9. restart and check IRQ affinity.

Note1: Basically sudo password is deactivated for 'systemctl' command.
Note2: It is done on LCNC2.9.3/ Debian
Note3: Any change in last CPU number/ network hardware Interrupt number will require reconfiguration of .sh file.
Note4: No need to enable irq32affinity.service by 'systemctl enable' command.
 

The recommended Linux distribution is Debian which is very similar to Ubuntu. I'd recommend doing a clean install of Debian and selecting the lightweight xfce user interface during the installation.

A Debian ISO file including LinuxCNC is available here: linuxcnc.org/downloads/

Once installed you have to run a latency test to see if the computer in question is suitable for LinuxCNC or not. Usually this involves some BIOS and/or Linux tweaks in order to try and get the best results.

 

Try using just fast probe and zero out slow probe fr in the parameters page of probe basic, sometimes to slow of a break causes issues

My first post.

started a project building a CNC Router and have been studying which board and G-Code sender to use for it.  After some study I’m leaning toward using LinuxCNC.

Unfortunately, I have very little experience with Linux so I have a couple of questions:

- I brought home an old, tiny footprint industrial PC (IPC) from work that has Ubuntu 20.04.4 LTS installed.  What version of Ubuntu would you recommend for running LinuxCNC?

- This tiny IPC is fanless, no internal power supply, & has a solid state drive.  However, it has an Intel Atom CPU 3845 @ 1.91GHz x 4.  Is this enough processing power to run LinuxCNC with no processor issues?

Thanks for your help.

Lcvette wrote:

Check the stickies, big changes that require config updates, the sim folder has the files with all the changes and a libido to the docs page. All subs require an update, var file, yaml file, ini file, post gui hal file
 

I did see that, and overwrote all my old subs, var, etc. when I reinstalled everything a month or so ago.

With the most recent cal_round_pocket sub installed the calibration routine started working.

Unfortunately, the erratic probing is still happening.  Fiddling with debounce from 2 all the way up to 25 didn't seem to make much difference, although at 25 it was doing single-touches at every point.

Started halscope to see if the input - upstream of the debounce - was acting flakey... nope.  The input signal was clean and not jumping or fluttering.

Changed the radio channel on the receiver and that stopped a couple of complete disconnects.  But still didn't resolve the erratic behavior described in my first post.

So I'm still stumped.

Check the stickies, big changes that require config updates, the sim folder has the files with all the changes and a libido to the docs page. All subs require an update, var file, yaml file, ini file, post gui hal file