Statusmeldung:
Unser Test war nict erfolgreich!
Was haben wir getestet:
Vom Steuerrechner das Parallelportkabel abgezogen.
Daran einen Adapter mit Schraubanschlüssen gesteckt.
Die pins für Takt und Richtung für eine Achse angaschlossen.
Den neuen Steuerrechner mit der Mesa verbunden.
Geprüft ob die steuerbefehle ankommen. drücken der Z+ oder Z-
Ergebnis 1 => umschalten ok 5V Pin high oder low
Ergebnis 2 => schrittsignal ok

Adapter mit bestehnder Steuerkarte verbunden.
Keine reaktion der Motoren.
(Ich schreibe dies aus dem Gedächnis, kann mich nicht mehr sicher an alle m
Messungen und Zustände der LED auf der verbauten p-karte erinner)

Aktuell sind wir etwas Ratlos....
Vorschläge was wir untersuchen sollten?

Bonjour,

Linux CNC 2.9.8 sous Debian 13 Trixie
Axis avec custom pannel.
Les bouttons apparaissent sur le coté de Axis 5 Jog X Y Z +&-
mais ne marche  pas ( avec vitesse de jog a plus que zero)
Home marche bien.
Pas de message d' erreurs au démarage de Axis.

Quelqu'un pour regarder mes fichiers svp ?

Merci

Hallo tommylight,
Der Titel stimmt fast ganz nur das s ist mir entwischt.
Korrekt nennt sich die MESA 7i96s.
Da das s ist nur ergänzend für einen analogen Ausgang, zum steuern einer Frässpindel.
Das sollte auf die Fragestellung keinen Einfluss haben.

Hi,

In order to help you, we need more information.
First of all, have you read through this thread? 

Stepperonline A6

Here you will find a lot of valuable information about setting up, operating, and homing Ethercat servo drives.
You should also provide the following information:
- What type of servo drives are they and are they CIA402 compatible?
- What type of network card are you using?
- Your ethercat.xml > basic Ethercat configuration
- Your maschinen.hal > required for loaded modules and links
- Your maschinen.ini > required for your machine configuration.
Please do not embed the files as code, but attach them instead.
 

Oh there must be so much to change i just didnt see the other slider

Thanks a lot guys your awsome!

Hallo zusammen , ich habe eine mesa config mit einer 7i97t =>7i74 und an der 7i74 hängt eine 7i73 und 7i84  nun hab ich gestern ca 5 stunden lang versucht die 7i73 in den mode 1 ( encoder+analog in ) zu bekommen das hat nicht funktioniert ich habe das mit dem ändern von  sserial_0=0100 versucht und verschiedenste Foren Beiträge gelesen bin aber zu keinem Ergebnis gekommen eventuell weiß ja wer von euch mehr oder wie gehe ich da vor ? Wenn ich in das terminal eingebe Halcmd show pin  dann werden mir die Pins so angezeigt = hm2_ 7i97.0.7i73.0.7.input00 beispielsweise . Die config läuft aber ich weiß nicht wo der Fehler ist oder was ich anders machen muss damit das funktioniert . Gruß Tom 

Danke schonmal für die tollen Antworten,  ich werde das heute mal anwenden und berichten über das ergebnis , ich hoffe es klappt . Gruß Tom  

wheeeee

According to the manual, a 24V switching power supply must be used for power.

I have three machines (lathe, mill, router) that I'd like to update from vfd communication (one GS2, two CommanderSK VFDs). They all work with user mode RS232/RS485 idrivers but I implemented Andy's automatic gear detection on the mill and lathe and the vfd motor speed doesn't update fast enough to track the gear ratio during acclel and decel. 

All three machines are running LCNC 2.9.8.

Lathe uses a 7i96 with 7i85S and a G540 - 7i96p1_7i85dsdi.bit
Mill uses a 7i92 with 7i85S and 7i75 daughtercards, 7i92_7i85sx1sdid.bit 
Router uses a 7i92T with a 7i75 and a G540 7i92t_g540d.bin

I believe the Mill and Lathe are custom built firmware, The router is stock. I don't sse any mention of pktuart in any of the --readhmid files?

My understanding is the 7i96 on the lathe should be RS485 compatible? Hoping this is just a firmware update?
Can I use the Mill's 7i85S RS422 with a RS485 VFD?  Ok if I need to use a TTL/RS485.
Can I use gpio with a TTL/RS485 adapter (solution for Mill and Router).


After initialization, I only need to write 2 registers and read 3 registers and I could block these up. Looks like hm2_modbus would be perfect for what I need if the hardware I have supports it.

 

yes I like that better.

Marcos DC wrote:

Hi Rod,

 Once you start talking about pushing the host loop into the few-hundred-microsecond range, things like DC setup, cycle stability, NIC behavior (EEE, IRQ coalescing, etc.) and jitter stop being details and become the main engineering problem. That was the point I wanted to make.

When I said Mesa tends to be more “KISS”, I meant it in an architectural sense, not as a value judgment. EtherCAT is a full industrial fieldbus: multi-vendor, DC, flexible topologies, designed for distributed systems — that’s a big strength. The hm2-eth approach is intentionally simpler and focused on talking to the card, with the time-critical I/O timing living in the FPGA. Different tools, different trade-offs.
 

EEE, IRQ etc are really at the operating system level so they effect networking for both Ethercat and Mesa. But I think Ethercat is less affected.

In the RT community, the need to optimize/tune the kernel is well understood. Here at LinuxCNC we have only just been forced to come to grips with this since we adopted Bookworm. We skipped deployments on Bullseye but let me assure you the issues were there then.  I agree that users should never need to understand how to apply these settings, it should be done for them. Yesterday, I delivered a custom Linuxcnc installer that sets the system up for optimal RT performance in a networked environment and installs and configures ethercat. The customer just needs to install his linuxcnc config. Ultimately, I will build a more generic installer but I have to first recover from the brain-hurt this project inflicted on me!

open a terminal and type in:

editvcp probe_basic

it will open the editor so you can see the properties. here is an image of them for reference:

 

 



Follow the sim hal and postgui hal to see the connections. note the pinbasename properties for the in gui button and the led and how the connections flow in postgui hal:

# *** Probe graphic simulation trigger push probe tip ***
net probe-in  =>  qtpyvcp.probe-in.out
net probe-in  <=  qtpyvcp.probe-led.on

those wires look too long and too loose. you will need to shorten them for sure and tighten them up a big
shorter is better, keep it as short as possible
edit do you mean 8inches and not 8cm? 8cm is the length of the rpi board