Rookie0 wrote:

connecting only one driver is actually insufficient

Sufficient for whose purpose? Yours or mine?

I'm not trying to get a specific machine working...I'm trying to get the driver's IO controllable via HAL.

I don't understand exactly how the xml file's in/out configuration works and I can't find an example I can use as a template.

It can be done this way, but my approach is to use the IO module separately.
The advantage is that there is no need to connect wires from CN1 of the servo driver, as connecting only one driver is actually insufficient. There are more endpoints on the IO module.

The ethercat A6 use a HDB15 connector on the front for the built-in IO.  Not quite as large as an HDB44, but still need to consider cost of cable and stickout/packaging.  If you plan to use a brake on one (or more) servo, you'll need at least one drive to have the IO cable connected.

OTOH, HDB right-angle cables, extensions, and adapters are much more available less expensive than HDB44's.

Actually, in Norway the most used distribution system is called an IT net (IT is short for something like Insulated Terra). This system uses 3 phase conductors and no neutral, with a conductor to conductor voltage of 230v, and with no neutral there are no other voltages available. I think this is different from most of Europe where they use a TN net, at least that is what Wikipedia is claiming...

Keep a wireless mouse and keyboard connected to use for configuration purposes but put them on a cupboard until needed.
Use a GUI like QTdragon that is designed to be a fully touch enabled GUI.

The cables are kinda expensive(relative to others), the bulky part will be an issue too. Also played around with the thought of db44 breakout boards, most expensive because I need a cable and a board for 4 servos but it would reduce the wiring headache (~34 bouncing cables per servo)

Im trying to keep everything on a tight budget as the cnc kept growing and now Im at twice the planned budget. Im trying to future proof what I can and keep the system as adjustable as possible. 

 

A6 Ethercat servos are not step-dir compatible; pick one or the other.
Step-dir with Mesa will be easier to configure than Ethercat, but more wiring

What is complicated or expensive about connecting the step-dir drives to Mesa?  Buy a DB44 cable from Stepperonline and connect to Mesa - maybe I'm missing something?

Only headache I know is that the DB44 cable connector is HUGE, and sticks way out when plugged in to the drive.  If you have a tight enclosure you may not be able to shut the door on a standard 8" deep enclosure.

You can buy DB44 right-angle cables (no adapters I can find) to shorten the package a bit, or you can cut a hole in the enclosure door for the cables to stick out.  And 3D print a raised cover for the new hole...

EDIT - see last post for resolution and xml/HAL examples

Just dipping my toe in the ethercat waters and trying to set up a single drive on the bench.

I've got LCNC talking to the drive, and can start LCNC with a basic 1-axis config.  Very exciting to see the position change when I twist the motor shaft.  Much thanks to the forum!

Next move is to enable/configure the drive's IO, but none of the various xml file examples I could find in the forum appear to have mapped DI1-DI5 & DO1-DO3 to HAL pins.

I'd like to use all the DI/DO as general purpose IO (other than DO3 for a brake).  Does anyone have an xml file with all the IO defined and mapped?

And whatever else I need, maybe a HAL file with IO pin names?

Thanks for any examples or suggestions.

Hallo all,
im planning and building my own cnc from ground up with zero experience. Im in the final stages of planing but like many times before Im rethinking some basic descisions. 
Issue right now is I was planning on using linuxcnc with a mesa 7i96s and send commands to the drivers via step/dir. I plan on using stepper-online a6-series servos for my cnc and am aware that this is a kind of suboptimal setup as its not a fully closed loop system. I have ran into an issue connectiong the servo drives to the mesa, all options are eighter expensive or create a mess in my electrical box. I am considering switching to ethercat as the pricedifference is negligible. Rather it would actually save me money since the wiring is much cheaper and I don't need the mesa anymore. Problem is I already have the mesa (unused) and don't know what the best option would be.
1. Go full ethercat and sell mesa. 
2. Deal with the wiring issue by throwing money at it.
I hope someone with experience with eighter system or both can give me some help deciding or maybe give me pointers that I may not have considered before.
Many thanks in advance.

See comment 

Hey everyone

Next year, I will be building a CNC myself as a school project.
The idea is to use an old ABB IRB140 and mount a spindle on it.
I dont know anything about CNCs nor have I worked with one.

My question is, where to begin???

I welcome all information or help.

Thx in advance!!

Hello
I am trying to set up a cheap touch screen monitor so I can run Lcnc without a mouse and keyboard. The touch screen seems to work well. I have installed 'onboard' as a virtual keyboard, which allows me to log in via the touch screen, but once the os is fully loaded it won't let me type into any text box at all.  I am running Debian Bookworm, with a default xfc session and Lcnc is version2.9.8. 
Any help gratefully received.
Thanx

Hi axemas, Thank you for all your efforts.

I’m testing the  [/code][/code][/code][/code][/code]

(ncam:27369): Gtk-CRITICAL **: 09:12:35.253: gtk_accel_label_set_accel_closure: assertion 'gtk_accel_group_from_accel_closure (accel_closure) != NULL' failed
/usr/bin/ncam:2538: DeprecationWarning: Gtk.UIManager.get_widget is deprecated
  self.main_toolbar = self.uimanager.get_widget("/ToolBar")
/usr/bin/ncam:3530: DeprecationWarning: Gtk.Action.set_visible is deprecated
  self.actionCurrent.set_visible(not self.pref.autosave)
/usr/bin/ncam:4453: DeprecationWarning: Gtk.Action.set_sensitive is deprecated
  self.actionUndo.set_sensitive(self.undo_pointer > 0)
Previous work not saved as current work
/usr/bin/ncam:3993: DeprecationWarning: Gtk.ToggleAction.get_active is deprecated
  if self.actionDualView.get_active() :

I’m trying to determine if additional steps are required to make it compatible.Any clarification or guidance would be appreciated.Thanks.
Doug [/code][/code][/code][/code][/code]

my best guess, shaublin just wrote a very difficult to control pid algorithm with slow speed seeking, and they had a team of engineers, and you'll notice , they got rid of the variator, sometimes the best part is no part. for my suggestion with the closed loop stepper, KEEP the existing worm gear angle driver, make a coupler and adapter slap a stepper in place of the existing AC motor. keep the acme screw and angle drive, looks doable without disassembling the machine from photos. Also my path is, 4 wires from you 2 from the psu and 2 step dir  card. it doesn't need to be decimal perfect.