Advanced Search

LinuxCNC 2.9.8 has been released.This is a minor update release, mainly of interest to those using the hal_gpio HAL driver (mainly Pi users)Changelog:

• backport #3516 to fix #3679
• Only initialize python if not yet initialized.
• hal_gpio: Adapt to use libgpiod3 or libgpiod2 according to what is installed
• Merge pull request #3671 from smoe/docs_image_handling
• core-components.adoc remove duplicate descriptions
• Merge pull request #3642 from LinuxCNC/2.9_#2460
• Update LinuxCNC RTAI Install instructions
• Merge pull request #3555 from smoe/lintian_warnings
• Merge pull request #3588 from f355/2.9
• [ci] publish releases with artifacts
• debian: Addressed lintian warnings
• axis.py: restore mdi queuing provision #2460

The main driver for the release was the change in API for the gpiod driver. This resulted in the hal_gpio driver not being built under Trixie.As of this release the default Debian version for the ISO for both PC and Pi has been updated to Trixie. The LinuxCNC repositories have been updated for Buster, Bullseye, Bookworm, Trixie and Sid.Note that released debs are also now available on the LinuxCNC GitHub under “Releases”: www.github.com/https://github.com/LinuxCNC/linuxcncAs always, thanks to all the developers who make this possible, and for this release especially:Bertho Stultiens
Dewey Garrett
Konstantin Tcepliaev
Robert Schöftner
Steffen Möller

I finally put together a short YouTube video to introduce the project
(even though I’ve already been working on it for about a year ).

I’ll add more videos in the near future.

I have checked the power and the cable, that look fine. (FieldA (24V) or FieldB (5V) power on 7I84)

This is the load line in the hal file:
Do I have to add anything if the 7i84 is connected via a daughter card?
 
 

Hello All,

things are slowly getting serious. I have reduced the size of the machine’s rear panel, repainted it, and mounted it again. I also cleaned up the wiring and repaired a few things, including the rotary window and the external fan of the spindle servo. In addition, I have started building the control cabinet and some parts are already wired.


 



Current hardware setup: a Beckhoff AX5125 for the spindle servo. I am still struggling a bit with TwinCAT and the parameterization. Beckhoff EL1100 via EtherCAT, various I O modules. some encoder modules, and the drives for X and Y are still missing. Some of the I O is already working and I am starting to like EtherCAT a lot. :)For the gearbox shifting with ratios 4:1 and 1:1 and for lubrication I have already found some very good examples and I think I can handle that.

With other topics I am still a bit unsure and would appreciate some advice. Any links to documentation or things to read and learn would be very helpful.

First, spindle and C axis. What is currently the best way to approach this? I have already found a lot of information on the topic, but the solutions are sometimes very different and often seem not fully resolved. Are there any proven approaches or experiences you can share?

Second, the machine has a Multifix tool holder at the front, meaning a standard front tool setup with manual tool changes. I plan to install a tool turret at the rear, meaning a back tool automatic tool changer, which should be relatively easy to integrate using a carousel. Is mixed operation even possible? From a purely mechanical point of view there is nothing preventing this. For example, doing some operations with tools from the turret and others with the Multifix. Can LinuxCNC handle this so that some tool changes are automatic and machining continues, while for others it moves to a manual tool change position and prompts the user to insert the correct holder? Visualization is also an issue. As far as I can tell, it is not possible to switch between front and back tools or use both at the same time in the display.
To make things more complex, I am planning to mount the turret on a kind of quick change plate so that it can be parked very quickly in the rear right area of the machine. This is necessary to machine large workpieces with a steady rest using only the Multifix. I would like to disconnect the turret using a Harting connector. Is it possible to tell the machine via an input pin that no turret is installed so that the machine operates in front tool mode and does not attempt to use the ATC ? I would find it a shame if I had to treat this as two separate machines and could only use one type of tooling at a time.

Thank you very much for your feedback.

Greetings
Tom

Hi trisa, "Turns out if you try reading an ethercat adress that the drive doesn`t have, nothing works."
Is it mandatory to change those error sdo/pdo errors:
0x1703:01, 0x1B03 ?
 

Google translation:
Over the holidays, I worked on configuring my Mesa cards and familiarized myself a bit with the Mesa CT. Since I'm not very experienced in writing things off the cuff, I wanted to help you with Mesa CT. However, I only see and recognize my main card, the 7i97t, and the bitfile I loaded is the one for the 797t and 7i74, which is what I want to use via the expansion port. Furthermore, the card combination is to be expanded with a 7i73 for the panel and a 7i84u. Now to my questions: Can I connect the two cards to my 7i74 using a Cat 6 cable, or is it better to run something else through the smart serial port on the card? I've already plugged everything in, and they're getting power; the LEDs light up. But when I use the `halcmd show pin` command, I only see the 7i97t listed. What's going on? How do I proceed, or what do I need to do differently? I've been getting so frustrated with this for days. I did have a small success, though, because I'm hoping to gain a better understanding of the whole thing. I managed to control an LED with a resistor through the 797t, which I was very happy about. But the rest is a complete mystery to me. Thanks, Tom. I look forward to your answers, and please explain the technical terms a bit more simply, as I'm a complete beginner in this area.

If you already have a RealTek card you can try with r8125-dkms or r8168-dkms driver depending on the model.
Often this is will give full network performance. "sudo apt install r8168-dkms"

If you are looking to buy a PC, buy one with an Intel card. You can also buy a PciE Intel card afterwards.

:02
You set micro-stepping in SDO 0x2001:0 which is number of steps per motor revolution.
Then you need to match that in cia402.0.pos-scale which is number of steps per mm/inch.
github.com/dbraun1981/hal-cia402/tree/main/example
 
 

Hello Experts,

Doubt:01

It is found that using onboard LAN Driver is not at all good for Ethercat Communication.
We would encounter connection drops and other inconsistencies If it is Realtek.

Should I buy a PCIe Network card or Can I use Realtek?

Doubt:02
 
     I am Planning to Replace my Pulse Driver DM556 with Ethercat Stepper Driver ECR86 from Rtelligent.
How is the micro stepping configured ? My setting was 1600 steps per revolution. (Aprox 83.5 Pulse per millimeter)

 

Hallo zusammen und Frohes neues erstmal , ich habe mich über die feiertage an die Konfiguration meiner mesa karten gesetzt und habe mich ein weni mit dem mesa ct vertraut gemacht da ich nicht so wirklich bewandert bin die hal frei schnautze zu schreiben wollte ich mit mit mesa ct weiterhelfen , jedoch ist es so dass ich dort nur meine hauptkarte die 7i97t sehe und erkenne und das bitfile welces ich drauf geladen habe ist das welches für die 797t und 7i74 ist welches ich auch so über den expansion port nutzen möchte desweiteren soll die kombination der karten noch mit einer 7i73 fürs panel und einer 7i84u erweitert werden . Jetzt zu meinen fragen kann ich die beiden karten per cat 6 kabel an meine 7i74 anschließen oder ist es besser da noch was über den smart serial anschluss über die karte laufen zu lassen bzw ich habe das ganze schonmal angesteckt die bekommen auch strom bzw die leds leuchten aber bei dem befehl halcmd show pin sehe ich nur einzig und allein die 7i97t aufgeführt und wie ist das wie geht man da vor oder was muss ich da anders machen ich bin da die tage schon so verzweifelt dran . einen kleinen Erfolg gab es zwar schon da ich mir damit dann ein wenig Verständnis in der ganzen Geschichte verschaffen möchte und zwar hab ich es geschafft eine Led mit einem widerstand zwischen über die 797t anzusteuern da hab ich mich sehr drüber gefreut aber das andere ist mir echt ein Rätsel . Gruß Tom und ich freue mich über die antworten , und bitte die antworten ein wenig einfacher mit beschrieben Fachbegriffen erstellen da ich noch kompletter Neuling in was das angeht .

I've added the following line to hal_input, and it get's me 90% of what I want.

diff --git a/src/hal/user_comps/hal_input.py b/src/hal/user_comps/hal_input.py
index 87c90e716d..3e0a720384 100644
--- a/src/hal/user_comps/hal_input.py
+++ b/src/hal/user_comps/hal_input.py
@@ -165,6 +165,7 @@ class HalInputDevice:
print("Unexpected event", ev.type, ev.code, file=sys.stderr)
continue
if ev.type == 'EV_KEY':
+ subprocess.call(["xdotool", "key", "Control_L"])
if ev.value:
self.set(code, 1)
self.set(code + "-not", 0)

  Das auch noch 

Gesundes neues Jahr 

Ich bekomme es nicht hin kann mir jemand helfen bei der oder Bedingung 
 

Thank you for your help. I will look in to the availability of these cards and then i am going to decide. But the 7i97T looks promising.

Next week i will recive the electrical manual and then I can determin the exact number of I/Os and wich signal they need.

How can I adjust this?
I searched for this because it seems that other users had the same problem.
It was recommended to set the value HOME_ABSOLUTE_ENCODER = 2 and omit HOME_SEARCH_VEL; HOME_LATCH_VEL.
So I set the following.
HOME = 0.0                            
FERROR = 1000                        
MIN_FERROR = 1000            
MAX_VELOCITY = 100            
MAX_ACCELERATION = 750               
MIN_LIMIT = -1800                    
MAX_LIMIT = 100                        
HOME_OFFSET = 0.0
# Sequence for homing Start at 0                     
HOME_SEQUENCE = 0                     
HOME_SEARCH_VEL            = 1     
HOME_LATCH_VEL            = 1     
HOME_IGNORE_LIMITS        = YES
HOME_ABSOLUTE_ENCODER = 2
CIA402_HOMING_ENABLED = 1
CIA402_HOMING_METHOD=4
CIA402_HOMING_SEARCH_VELOCITY=100000
CIA402_HOMING_LATCH_VELOCITY=50000
CIA402_HOMING_ACCELERATION=131072

This now works for at least one axis, but all the others still malfunction.

 

Er87.1 is "One-time excessive position reference increment". It sounds like your drives are trying to move from $home to the last commanded target position in one CSP period.

Try commanding the drive to find home using its CIA402 home method, and immediately (before the homing sequence finishes) set the target position to 0.