Advanced Search

What we need is a way to "link" the two joints (example: X and X-slave)... Am I correct, currently we tell both to home and just expect them to go?

If one isn't ready, or simply fails to move, we would prevent both from moving.

What if CIA402 component had some pin, maybe an io pin to monitor, and any drive connected to it could set it, causing them all to halt?

net gantry-halt-interlock   <=> J1.cia402.halt
net gantry-halt-interlock   <=> J2.cia402.halt
If a drive is commanded to move, try clearing the pin just once. If a drive is faulted and sees this pin got cleared, set it again.

Or maybe a better way, (or additionally?) monitor both joint positions, if the difference exceeds some value, stop both?

Just throwing the idea out there. Maybe I'm just making noise.

There are many missing connections in the hal file:

As a start I would uncomment the high-lighted commands
##net x-index-enable <=> pid.x.index-enable
##net x-enable => pid.x.enable
##net x-pos-cmd => pid.x.command
##net x-pos-fb => pid.x.feedback
##net x-output <= pid.x.output

##################TEST#############################
# joint-0 enable chain
net joint-0-index-enable <=> pid.x.index-enable
net joint-0-index-enable <=> joint.0.index-enable
net joint-0-index-enable <=> hm2_7i97.0.encoder.00.index-enable

net joint-0-enable <= joint.0.amp-enable-out
net joint-0-enable => pid.x.enable
net joint-0-enable => hm2_7i97.0.pwmgen.00.enable
###################################################

# ---PWM Generator signals/setup---

##setp hm2_7i97.0.pwmgen.00.scale [JOINT_0]OUTPUT_SCALE
##setp hm2_7i97.0.pwmgen.00.output-type 1
##setp hm2_7i97.0.pwmgen.00.offset-mode true

##net x-output => hm2_7i97.0.pwmgen.00.value
##net x-pos-cmd <= joint.0.motor-pos-cmd
##net x-enable <= joint.0.amp-enable-out
##net x-enable => hm2_7i97.0.pwmgen.00.enable


 

What do you suggest?
Creating a new .hal file?

From your hal file:
Looks like a chemically castrated hal file, so what am i missing as that can not work.

Hey mark 
From memory no the run away doesn’t happen when I disconnect the axis from the masa board. Which may mean I should be able to use f2 to latch the relay!! Will try this.

yes I have the manual  and I haven’t done this as the drives were working perfectly before the controller died.  

You hardly have a close up of your 7i77?

Just to clarify I should be connecting the differential inputs E1 and E2 to Aout0 and Gnd? 

What you are expected to do is for example:

Setup the number of stepgens and pwmgens and encoders you need:

 

Then select which axis are connected to which stepgens etc:

 
 

Intéressant, testez si pin 1 (et n'importe quelle entre 10 et 17) fonctionne comme entrée. Dans ce cas, la carte fonctionne en mode X (j'utilise ce mode fréquemment).
C'est rare, mais j'avais une carte double port qui ne fonctionnait que comme ça, si un seul port était configuré.

Robert

depronman wrote:

I didn’t spot it in the bios but equally wasn’t looking for it. Is it normally in the same area of the bios screen that legacy mode and secure boot reside ?

 

That sounds like it... Trusted computing. Boot priority. Those are some areas I'd think of checking. If it is nowhere, then it probably does not have CSM.

One naughty bios in one of my systems a while back showed: CSM = disabled. It could not be enabled. The manual said it can be enabled if you install a graphics card. I tried that and it worked. Which was a problem because it had only one PCIe slot and I wanted something else in it; I had no need for a graphics card on that system.

We created a file using the proconf Wizard.
We compared it to ours because ours was created with an older version.
We noticed some differences.
Then we imported the differing lines into our HAL file, which successfully removed the errors, but the axes still move slowly automatically.
In the HAL file, we marked the sections we took from the other configuration with #####Test######
Items we commented out are marked with two ##.

depronman wrote:

Can’t find anything in the bios related to csm

Not all bios seem to have that.

If bios has CSM and it is turned off, I have no luck booting anything in legacy bios mode, I get:
"No boot media found"

My hazy memory is slowly refreshing. It seems I manually created a small bios boot partition (legacy mode) or efi partition (uefi mode). I never investigated why I had to do that; whether:
1. The automatic partitioner failed to create it, or
2. Some option I had selected prevented it from creating it automatically.

Posting a screenshot of what it is creating at the stage it asks you to confirm the partitioning might be helpful. I'm not sure whether there is an easy way to take a real screenshot of that, you might have to snap a photo of it.

Hallo zusammen,

ich suche Unterstützung beim Aufbau und der Inbetriebnahme eines LinuxCNC-Systems – nicht nur ehrenamtlich, sondern gerne auch gegen Bezahlung (€).

Kurz zu meinem aktuellen Stand:
Ich habe bereits ein 4-Achs-System aufgebaut (ohne Spindel), betrieben mit Mesa-Hardware und Schrittmotoren. Das System läuft grundsätzlich, jetzt möchte ich jedoch eine Nummer größer planen und perspektivisch auf EtherCAT mit Servomotoren umsteigen.

Je mehr ich mich allerdings einlese und anschaue, desto klarer wird mir, dass ich das wahrscheinlich nicht komplett alleine sauber umgesetzt bekomme. Daher suche ich jemanden, der mich beim Konfigurieren und der Inbetriebnahme von LinuxCNC mit EtherCAT-Servos unterstützt.

Geplanter Ablauf:

• Aktuell bin ich noch bei der Auslegung der Motoren und der Auswahl der passenden Servoregler
• Sobald die Hardware da ist, möchte ich zunächst ein Testsystem am Desktop aufsetzen
• Ziel ist:
  • Motoren, Endschalter und Homing-Schalter korrekt in LinuxCNC einbinden
  • Eine saubere Dokumentation, wie die Motoren später kalibriert werden müssen
  • Sicherstellen, dass die Verfahrwege exakt stimmen, sobald die Mechanik fertig ist

Der Zeitrahmen für das Projekt liegt bei ca. 3–6 Monaten.

Örtlich & Zusammenarbeit:
Ich komme aus dem Großraum Stuttgart.

• Bei Nähe: Gerne persönliche Zusammenarbeit, Hardware kann ich bei Bedarf vorbeibringen
• Bei größerer Entfernung: Remote-Setup ist für mich völlig okay (VPN / Remote-Zugriff auf den Linux-Rechner + Videoübertragung)

Aktuell ins Auge gefasste Anbieter (EtherCAT-Servos):

• OMC Stepperonline – A6 Serie
  • www.omc-stepperonline.com/de/1000-w-ethe...67-a6-ec1000h2b1-m17
• JSS Motor – JSS715N Serie
  • www.jssmotor.com/de/jss715n-series-1000w...otor-and-servo-drive
• Koco Motion – EL8 Serie
  • www.kocomotion.de/produkt/el8-series-eth.../?tab=technical-data
• Leadshine – EL8 Serie
  • www.leadshine.com/products/servo/servo-drive/el8-series.html

Meine Frage an euch:

• Hat jemand Lust und Zeit, mich bei diesem Projekt zu unterstützen?
• Oder könnt ihr mir jemanden empfehlen, der Erfahrung mit LinuxCNC + EtherCAT + Servos hat?

Ich freue mich über jede Rückmeldung.

Viele Grüße
Muecke

Can’t find anything in the bios related to csm

Not wanting to derail the original topic but my work around of installing 2.9.7 and then using the package manager to update to 2.9.8 failed

2.9.7 install from the iso ok other than a slight problem with a profile error on the desktop package. This did not affect anything
connected WiFi ok
apt package manager reported broken packages that needed fixing before linuxcnc would update to 2.9.8
fix broken packages didn’t work
so I’m some what stuck with my workaround

Thanks for the reply NWE
I’ve downloaded the iso 5 or 6 times and burned it to many different pen drives using various versions of Rufus and bletcher (I think that’s what called)
My friend also downloaded the same iso and burned it to a pen and installed onto a NUC without issue. He lent me the pen and that one failed at the same point
Also tried on numerous PC’s and numerous hard drives both ssd and mechanical hdd

I’ll give your theory on partitions a try tomorrow
Thanks

Paul

I'm sorry
I think you misunderstood me.
I am using the component and trying to understand how the process works from a control technology perspective.
Are the servos initialized and their status checked first, and then the homing process started, or is the homing process started without checking?
What happens if a servo is not ready?
What happens if a servo does not start the homing process or starts it with a long delay (watchdog)?
How is monitoring performed if a coupled axis on a gantry does not start moving during homing?
Since Linuxcnc has no control over this type of homing, these error cases should be monitored, otherwise the machine could be damaged.

In my opinion, the homing process should be initialized first.
Then check whether all servos are in the correct operating mode.
Then start the homing process.
During the homing movement, monitor whether the axes are synchronized (gantry).