Advanced Search

The link.www.communica.co.za/products/hkd-5-axis-...riant=31916110839881 

Here is the files that were posted for it.

 

That was easy to do, and it works exactly as desired. It is important for me to lock out this kind of potential risks.
Thank you for providing this information.

Hi all,

I've been working on a design for the control cabinet of my Maho MH400E.
I initially planned a relatively simple retrofit using Mesa cards, but after running into issues with the servo motors and spending quite some time trying to understand what was going wrong, the scope of the project gradually grew.

Along the way I ran into a few challenges:

1. I'm not an electrical engineer, so there was (and still is) a lot to learn.
2. Cost: this kind of hardware isn't cheap. Given the scope of the project, I deliberately chose components from vendors with strong documentation and long-term availability, to reduce risk during commissioning and future maintenance.
3. Time — or perhaps more accurately: patience.

After some frustrating attempts with QElectroTech, I ended up using SolidWorks Electrical. It certainly wasn't trivial either, but I do think it pays off in terms of built-in consistency, cross-references between components and wiring, and the ability to generate reports directly from the design.
This isn't meant as an endorsement, just my personal experience.

At this point the SWE license has expired and I want to move on to the actual build, once the remaining mechanical designs (servo motor mounts in particular) are finished.

Given my limited experience, I'm reasonably happy with the result so far, while fully expecting that there are still issues and blind spots.

What I ended up with:

1. An EtherCAT-based setup using Beckhoff I/O modules
2. Delta servo drives and a VFD with EtherCAT support
3. Replacing the original Heidenhain 1 Vpp → TTL encoder cards with Beckhoff 1 Vpp encoder modules
4. Schneider Electric and Phoenix Contact components for relays, power supplies, circuit breakers, etc.
5. Reuse of the original 400 V → 110 V transformer, the cabinet itself (with heat exchanger), the hydraulics pump and the lubrication pump

Still TODO (design-wise):

1. Control cabinet layout
2. Mechanical design for the servo motor mounts

At this stage I'm mainly looking for a sanity check on the overall architecture and safety-related choices. If anyone with experience in industrial control cabinets or LinuxCNC + EtherCAT setups would be willing to point out potential blind spots or "this will bite you later" issues, I'd really appreciate that.

I'm not looking to optimize for cost or replace major components at this point, but I am very interested in feedback on correctness, robustness, and failure modes — especially regarding EtherCAT behavior under LinuxCNC.

Due to forum size limits the attached PDF is a flattened version without internal cross-references. I do have a fully cross-referenced version available and can share it privately if someone wants to take a deeper look.

The problem is most likely related to the issue with  LWR and LRD/LRW modes that was discussed earlier.
You must at least get that fixed before you can rely on that error message.

automata has a solution. You cannot run lcec with those drives. automata attached
the code for another component to use with the Yaskawa drive.
attached as C file with a Makefile. Download and compile the code.
Use it as a component in hal.
I know it can be a handful to do this, I would foresee some experimentation to get this right.
Edit: I looked in the code and that isn't a ready-to-use component.
There is a lot of work needed to get this to work.

Frankly tar_san, I understood you have the drives on lone for evaluation, right?
Do yourself a favor and return them and get some other servo drives.
I can not spend that much time in getting this going. Hopefully someone else can.

Do you have a link to the manual for the HKD breakout?

Also make sure you do not have cable power enabled on the 5I25.

Hi,
Please excuse me for asking more questions.

The following parameters for homing are specified in Collin Bardini's .ini file.

HOME_SEARCH_VEL            = 15.625
HOME_LATCH_VEL            = 15.625
HOME_IGNORE_LIMITS        = YES

CIA402_HOMING_ENABLED = 1
CIA402_HOMING_METHOD=-2
CIA402_HOMING_SEARCH_VELOCITY=20000
CIA402_HOMING_LATCH_VELOCITY=7000
CIA402_HOMING_ACCELERATION=131072

Which of the two parameters determines the homing speed and acceleration? 
If the parameters are valid for CIA402, what units are they?

Thank you in advance.
 

7I43 SVST4_4 pinout  (created with mesaflash) is:


 


 

github.com/linuxcnc-ethercat/linuxcnc-ethercat/pull/461

There is a bug in the linuxcnc-erhercat if you just set the negative option

Thank you, I'll keep that in mind.

To have a button with an object name of state_stop_pb be disabled when the estop is on and enabled when the estop is off.
To have a button with the object name of state_on be off when the power is off
And to answer your question to have a button disabled when a program is running add the object name to the following dictionaries
JT

Good to hear that you are making progress.

[edit]
I would be interested to know how tool offsets are handled in the tool table for lathe tooling in the milling spindle on such a mill-turn machine. On a lathe the tool offset is different to a mill in the sense that the length of the tool is an X-offset as opposed to a Z-offset. That is why I have made two different TCP (mill / lathe) modes in this sample config. I wonder if that is actually necessary or if lathe tool offsets are handled just like milling tools.
 

Hi Folks,

im still living. Wanna give you a status update:

1. The spindle taper is fixed (Needed to be Laserwelded and reground)
2. New spindle bearings
3. I scraped the geometry of the Y axis. Which was a major step, and im not satisfied with the bearing points. (Geometry is excellent) When it gets warmer in Germany i want the moglice all the guide ways. Epoxy is already ordered.
4. I reassembled the B axis. In january i hope to reassemble the spindle and mount it to the B axis. I need the spindle and B axis ready and mounted to the X axis slide to check and scrape (even for moglice scraping is needed) the geometry.

Kind regards and happy new year,
Jochen

At this stage, I would bypass the contactors so the Indramat is on when the power is connected to the machine (maybe through estop chain) without LCNC and manually give an analog signal to the indromat using a 1.5V AA battery. If the Z axis moves, you can continue to troubleshoot the following error. If it does not, then the indramat is dead.

Hallo zusammen,

melde mich wieder nach langer Zeit aus der Versenkung.
Ich habe neues zu berichten. Meine alte Konfiguration mit SEW-Servos und analoger Ansteuerung über die Mesa 7i97 lief mehr schlecht als recht.
Ich hab das alles rausgeworfen und den freiwerdenden Platz mit  A6 Servos (Ethercat) von Stepperonline gefüllt. 
Mit Hilfe aus den Forum forum.linuxcnc.org/ethercat/54965-stepperonline-a6-servo hab ich alles erfolgreich zum laufen gebracht.
Meine Konfiguration:
Gantry: XYYZ (1800mm x 600mm x 300mm)
Servos: X A6 750W Ethercat STO, YYZ A6 400W Ethercat STO
Die Servos laufen über Netztwerkkarte 1 und die I/O über Netzwerkkarte2
Oberfläche: Gmoccapy
Homing über Homeschalter 
Die Servos werden leider ohne I/O Kabel geliefert. Das wird benötigt, um die Homeschalter an die Servos anzuschließen.
Ich habe mir hier DB15 VGA Stecker bestellt und die Kabel selbst gebaut.
Die Achsen verfahren, Homing funktioniert, jetzt muss ich nur noch die Feineinstellungen erledigen.

Grüße

Andre