Advanced Search

Search Results (Searched for: )

  • JT
  • JT's Avatar
Yesterday 08:27
Replied by JT on topic Forum Upgrade #5

Forum Upgrade #5

Category: Forum

Yes, all posts will be in the new forum. None will be lost. I don't give estimates, sorry. I'll make the change as fast as possible but there is no control on DNS propagation at all. I've seen DNS propagation take seconds to hours...

JT
  • mwc
  • mwc
Yesterday 08:17
Replied by mwc on topic Forum Upgrade #5

Forum Upgrade #5

Category: Forum

Just a quick question, which I'm sure the admin are covering with the announcement, but will all posts before the maintenance period be safe?

Also, I know it might be asking how long a bit of string is, but it might be worth giving an estimated time frame.
  • mwc
  • mwc
Yesterday 08:06
Replied by mwc on topic AMSAMOTION IO module

AMSAMOTION IO module

Category: EtherCAT

Thanks for that. I'll have a dig around the github later, as I'm off to do some workshop organising just now.
  • mwc
  • mwc
Yesterday 08:03
Replied by mwc on topic EtherCat homing, limits, and probing

EtherCat homing, limits, and probing

Category: EtherCAT

@tuxcnc for most machines, basic limit/home switch homing is perfectly adequate, especially on stepper driven machines, but on servo driven machines it is pretty common practise to use index homing, however EtherCAT makes that harder to achieve.
There's also the added benefit with closed loop EtherCAT drives (and especially now with the advent of multiturn absolute encoders) that the drives themselves maintain position through power offs, so in drive homing has become a much more beneficial thing to have and use.

Probing to me is the more interesting part. I have a homebuilt CMM, which I currently have no plans to upgrade as it does everything I need it to, so this more a discussion around what could be possible, and when I get around to retrofitting my little mill, I'll want accurate probing on it.
My CMM is stepper driven, with the loop closed using glass scales, and it all driven and controlled with a Dynomotion KFlop and Mach3 using the ProbeIt plugin. The exact trigger point is stored in the KFlop, then transferred to Mach3, eliminating any delays in Mach3 recognising the trigger.

@rodw I know you mention the methods being inherited from Mach3, but Mach3 can handle various probing methods. I know in ProbeIt, you can rely on simply the first touch, slow second touch, or reverse off for storing the touch point.

As a general comment, I'm well aware of chasing pointless accuracies.
The current plasma build, I'd be happy with a 1mm accuracy, as plasma isn't exactly a precision process, however on the two lathes I've previously retrofitted (both of which are now sold, as I have a commercial lathe with standalone controller), accurate X-axis homing made a big difference.
First lathe used a simple optical slot, which had 0.02mm repeatability, but there was noticeable drift with temperature, so if doing anything requiring high accuracy, I had to do a couple test cuts first, whereas the second lathe used servo index homing, and was always spot on.
  • rodw
  • rodw's Avatar
Yesterday 06:01
Replied by rodw on topic AMSAMOTION IO module

AMSAMOTION IO module

Category: EtherCAT

Using the EL6021 is probably the way to go, Once installed, it presents a TTY port that you can use with MB2HAL.
Also the CATIO-A IO module on AliExpress  does Modbus RTU and I have got it going too.
  • rodw
  • rodw's Avatar
Yesterday 05:55
Replied by rodw on topic EtherCat homing, limits, and probing

EtherCat homing, limits, and probing

Category: EtherCAT

I think homing is useful particularly where torque mode homing without any switches as on that said plasma, there is added simplicity engineered in by deleting limit and home switches. Limit switchers are part of some homing methods so if you do homing, you might as well use limits as well.

Probing to me  is  not useful in CNC but maybe for industrial applications. Applications like QTDragon and probe basic do not leverage the full capability of Linuxcnc homing because they don't probe onto a part and then probe away from it. Instead they repeat a probe at a slower angle.

From memory a 3d probe I had said not to exceed 200 mm/min dso something like this is how we should do ut
g38.2 Z -100 F200
g38.5 Z 5 F100 (or F50 even)
F100 = 0.00166 mm per servo period so surely that is as accurate as you need surely
The advantage of this is it removes any spring from the probe and gets a very accurate position much faster than the methods currently In use which seem to have been inherited from Mach3
  • Kittifix
  • Kittifix
Yesterday 04:35

Ethercat installation from repositories - how to step by step

Category: EtherCAT

update to PREEMPT_RT Debian 6.12.117-1 and it works ....
  • tuxcnc
  • tuxcnc
Yesterday 03:41
Replied by tuxcnc on topic EtherCat homing, limits, and probing

EtherCat homing, limits, and probing

Category: EtherCAT

In most machines and their applications, using internal homing within the drive systems makes no sense and offers no benefits.
While it might technically provide greater precision, the question is whether that precision can actually be put to practical use. In amateur-grade machines, certainly not—and even in professional-grade equipment, not necessarily.
For instance, what is the point of homing a plasma cutter to an accuracy of 0.001 mm?
When turning or milling from raw stock, the machining allowance provided is far greater than the precision of the homing process.
Even when performing an additional operation on a nearly finished part—such as reaming a hole—you should still set your zero point using a probe or dial indicator; otherwise, a tiny speck of debris on the vise could ruin the entire job.
  • elizacommunities
  • elizacommunities
Yesterday 02:40
Replied by elizacommunities on topic EtherCat homing, limits, and probing

EtherCat homing, limits, and probing

Category: EtherCAT

Thanks for raising this, it is a useful question. On limits, I would keep LinuxCNC in control of the limit handling where possible, so the behaviour stays consistent across the axes, and treat the drive's internal stop as a safety net rather than the main mechanism. For probing, the drive's internal latch sounds attractive for accuracy, but as you say it adds wiring and configuration for every drive, so for most work probing a little more slowly through LinuxCNC seems the simpler and more maintainable route. I have not used in-drive homing yet, so I would be interested to hear how it behaves in practice once the new release is out.
  • awallin
  • awallin
Yesterday 01:26
Replied by awallin on topic Tuning Steperonline A6 Servos

Tuning Steperonline A6 Servos

Category: EtherCAT

the edited parameters can be permanently saved to the drive EEPROM with this command. The -p parameters sets ethercat device number (adjust for your setup, and run this for all drives tuned).

$ ethercat download -p 5 0x1010 1 0x73617665 --type uint32
 

  • awallin
  • awallin
Yesterday 01:09

Technical questions about CIA402 and homecomp.comp on A6

Category: EtherCAT

FWIW with the latest homecomp updates (github.com/linuxcnc-ethercat/cia402_homecomp/pull/4) I now got cia402 homing working with stepperonline A6 drives.
My config is here github.com/aewallin/FS4MG_config
  • Sviper
  • Sviper
Yesterday 00:41 - Yesterday 00:44

LCNC-Cyclo: Conversational Programming for LinuxCNC

Category: Other User Interfaces

 

LCNC-Cyclo: Conversational Programming for LinuxCNC

I'm currently working on LCNC-Cyclo, a shop-floor-oriented user interface for LinuxCNC. The idea: anyone who works with conversational-programming controls at their job should be able to work the same way on their own LinuxCNC mill at home. You write the program in conversational format, call a cycle, fill in the parameters in a form, and you're done.What already works:
  • All screen areas and operating modes you'd expect from a shop-floor control, light/dark theme
  • 58 cycles: drilling, threading, pockets, SL/contour pockets, engraving … each with an input form and help graphic
  • Conversational code is translated live into real LinuxCNC G-code, with a switchable view
  • PLANE functions using LinuxCNC's tilted work plane (G68.2)
  • Simulation with toolpath lines, material removal, full machine model and target/actual comparison against STL
  • Checks for limit switches, rapid moves in material, holder collisions and head/table collisions
  • Sim machines: 4-axis XYZ+B swivel head (my Slayer_1000) and 5-axis XYZAC

    Important: Unmodified LinuxCNC runs underneath. Only G-code is executed on the machine. No third-party software or data is included. The goal is simply to make operation easier for everyone who is used to conversational programming.Next steps: First use on the real machine (EtherCAT, lean system that boots directly into the GUI) and connecting an original matrix keyboard via Arduino.Feedback and ideas are welcome!
    There's still a lot to do, test and expand before this becomes a full-featured GUI, but the first tests on the machine look good.The screenshots are numbered in the order they appear in the text:
    1. Cycle with input form
    2. G-code view
    3. Material removal simulation
    4. Machine simulation
    5. Programming run → Program run
  • Hakan
  • Hakan
Yesterday 23:46
Replied by Hakan on topic AMSAMOTION IO module

AMSAMOTION IO module

Category: EtherCAT

I can give you a pointer. There was recently a commit in linuxcnc-ethercat for EL6021 a serial-over ethercat device.
That should do the Modbus transport.
  • Hakan
  • Hakan
Yesterday 23:06
Replied by Hakan on topic EtherCat homing, limits, and probing

EtherCat homing, limits, and probing

Category: EtherCAT

I guess it is a case where the drive moves outside of LinuxCNC direct control.
Just like homing. Mostly a question on how to interface to motion. Have you dug into that?
The drive will need settings for the probe action, that's manageable.
 
  • mwc
  • mwc
14 Nov 2026 19:09

EtherCat homing, limits, and probing

Category: EtherCAT

I'm aware there is a release imminent to make proper use of in drive homing routines, but it's also got me wondering about limits and probing.

Limits aren't that big an issue, as they should work just like any other limit switch by just using whatever input is suitable, but most EtherCat drives can act on the limit inputs internally by stopping motion. Is it worth the effort of utilising that functionality?

For reference, my current build has a dual motor gantry, and will home of the limit switches, so there would obviously be some parameter changing needed during the homing process.

Probing is a bit more interesting.
Probing can be handled like any other system with LCNC directly controlling things. but again EtherCat drives often have the ability to have a probe directly connected, with the probe trigger storing the exact position to an internal register.
Has anybody made use of this functionality yet?
I know the easy answer is just to probe slower to minimise how much any time delays affect the read position, so this is more about the theoretical possibility, as you'd then also have the electrical problem of connecting a probe to every drive that might need it.
Displaying 46 - 60 out of 11366 results.
Time to create page: 0.363 seconds
Powered by Kunena Forum