Advanced Search

Ok, I got some help and realized the mesa 7i76e was in mode 0, now it is in mode 2 and I can see the counts on hm2_7i76e.0.7i76.0.0.enc0.count

I am still lost about how the following works (as for the logic)

I would love to have one button that enables the jog for x axis for example, and then the mpg makes it move (while the button is pressed)

 

Don't know why file didn't come through, but I'm pasting it here:

o<auto-xy-zero> sub
<#factor> = 1 (Adjust for metric)
o100 if [#<_metric> EQ 1]
#<factor> = 25.4
o100 endif

#<X-move> = [#<_ini[LASER]laser-offset-x> * #<factor>]
#<Y-move> = [#<_ini[LASER]laser-offset-y> * #<factor>]
#<feedrate> = [20 * #<factor>]

; (Move table to program start)
G91 G0 X#<X-move> Y#<Y-move> F#<feedrate>
G10 L20 P0 X0 Y0 A0 ( Set X/Y DROs to zero )

o<auto-xy-zero> endsub

m2

Looks to me that all of the references are correctly formatted.

Regards,

Hi,
Is there any way to easily add spindle reversal each hole during drilling? I drill a lot and the my steel is too stringy regardless of speed and feed. i came across HASS video of it. this is the link .
is there any way I can modify G83 like that? or even better spindle reversal between pecks

That was not helpful. Now it's off the no reply list without solution.
As mentioned, any input but zero greys out the ok button. The real machine and sim in Virtualbox have the same issue.
In the dialogbox it says:  file not open
A gcode file is loaded, so this could point to an internal fault
 

Aciera wrote:

I've replaced the standard kinematic file with your modified version, added extra joints and changed the config to inches to test in the simulation but I cannot reproduce your jogging issue in TWP mode.
I'm afraid I'm a bit at a loss as to how to troubleshoot this further.
 

Hi,
I was able to test this out a bit today and I've figured out it wasn't working because after setting the TWP, the G59 offset made the axis positions outside my soft limits,  I made my soft limits massive and it worked as expected.  If I have G54 zeroed out, then I don't get any values in G59, but my axis position are still outside the soft limits. 

I've been digging through the remap.py trying to figure out where the G59 offsets are coming from and I can see where it sets them around line 863, but I'm not sure how it's getting it's value.  It looks like it's passing the G54 offset value to to the twp-helper-comp.twp-ox-in correctly, but after that I'm not sure what to check.  Any idea what I should be looking for?

Some Testest with the Mesa 7c81 and 400W Servos:

www.youtube.com/shorts/KLijHrYiQXw

Board: eusurplus.com/index.php?route=product/product&product_id=131 + 5Axis-BOB
Servos: www.amazon.de/dp/B0DM5V6BZ2
Spindle: Huanyang VFD via Modbus

I am currently developing a parametric program (sub) to measure the exact dimensions of my tools. I need to read the theoretical diameter contained in the tool table that I use for my approaches. Thank you.

I can't configure the spindle, the configuration screen doesn't appear.
 also can't choose the PWM signal or CW - CCW.
I am on 2.9.5 and I don't understand what I'm doing wrong.

There is something that changed, in version 2.7.15 of LinuxCNC it could be done without problems, now it is impossible for me, I don't understand what is happening, I can't find information to guide me. Thank you.!!!

Since 2.9.5 update, touch off, the OK button greyed out, after input a value. Also after some restart of PC. A (senseless) touchoff with zero works:


 
 

Well, then I would say my suspicion is confirmed. The explanation says it.

The thing is that DC is very precise, and the ethercat master can follow the DC time of the slaves very precisely.
The first ethercat slave determines the DC clock speed.

But Linuxcnc's clock, used for the servo period and base period, is not synchronized with ethercat's DC.
One clock always runs slightly faster/slower.

The consequence of this is that when one clock is overtaking the other, there will be either double PDO or no PDO sent during an ethercat cycle. If there is no data sent one cycle the drive sees that as "stay on the current position" which means a hard brake if it is moving. Or move double delta this time, which means huge acceleration.
Latency and a not so suitable NIC makes it worse, the duration for one clock to overtaking the other becomes longer and more of these hits and misses takes place.

What can you do? Work on latency. Use an Intel NIC. See if your drive have some limitations you can set like max-acceleration. In short, see if your drive can handle hits and misses in a better way.

One would like to see Linuxcnc's clock synchronized with ethercat's DC, but it isn't.
 

“Synchronization overflow times” = the number of times the drive saw Sync0 + PDOs outside the valid window.
there is a tab in the tunner called diagnose that monitor the sync parameter for the communication, please check the attached screenshot from the tunner.
this screenshot is token while jogging the machine, jitter random sounds appears from the motor in random time there is no pattern.

the leadshine tunner app " motion studio" runs on seperate PC connected to the driver via USB.
 

github.com/linuxcnc-ethercat/linuxcnc-et...uration-reference.md
refClockSyncCycles tells how often the slaves' clocks are synchronized. "1000" should be fine, and "1" and "5" also.
I don't think you can have a floating point number there but I could be wrong.

I have a suspicion on what is going on, it has happened before with other drives, for me included.

I am not familiar with the Leadshine software. It runs on a Windows computer, right? And how does that computer
connect to the drive? I read Modbus somewhere. Just to see the difference with linuxcnc and ethercat.
What is the explanation of the Synchronization overflow times message, what does it mean?

What latency number do you have for the linuxcnc computer? And what network adapter does it have?

youtube.com/shorts/GbX_E2VRqPE?si=Lk3vPLiqrdEQZu4t

Success

SOLVED!

I am running LinuxCNC with EtherCAT  and Leadshine EL8-EC400F servo drives in Cyclic Synchronous Position (CSP) mode. I’m struggling with jitter / noise that seems to be related to Distributed Clock (DC) synchronization between LinuxCNC and the drives.
My Machine Setup:

• Controller: LinuxCNC (2.9.4) + EtherCAT (lcec)
  • Drives: 5 × Leadshine EL8-EC400F
    • Mode: CiA-402 CSP (0x6060 = 8) ( Control mode CSP)
      • Interpolation time (0x60C2): Read-only, fixed at 2 ms (

        value=2, [code]index=-3)

        [/code]

        • [code][b]Servo thread: 2 ms (2000000 ns) in LinuxCNC INI
          
          Please the attached XML for EtherCAT communication settings.
          My problem is as follows : [/b]

          [/code]

          • [code][b]When I jog axes in LinuxCNC, the motors make a [b]raspy / friction-like noise.[/b][/b]

            [/code]

            • [code][b][b]In HALScope, I see [b]large torque and acceleration spikes at the same time.[/b][/b][/b]

              [/code]

              • [code][b][b][b]In Leadshine MotionStudio → Diagnostics, I see the counter [b]“Synchronization overflow times” increasing steadily during motion.[/b][/b][/b][/b]

                [/code]

                • [code][b][b][b][b]However, when I test motion with the Leadshine tuning software (without LinuxCNC), the motors run perfectly smooth.
                  
                  what i tried so far : 
                   [/b][/b][/b][/b]

                  [/code]

                  • [code][b][b][b][b]Matched [b]SERVO_PERIOD, [code]appTimePeriod, and [code]sync0Cycle to 2 ms.

                    [/code][/code][/code][/b][/b][/b][/b][/b]

                    • [code][b][b][b][b][b][code][code]Tested different [code]refClockSyncCycles values:

                      [/code][/code][/code][/code][/b][/b][/b][/b][/b]

                      • [code][b][b][b][b][b][code][code][code][code]5 (every 10 ms) → overflow counter increased faster.

                        [/code][/code][/code][/code][/code][/b][/b][/b][/b][/b]

                        • [code][b][b][b][b][b][code][code][code][code][code]1 (every 2 ms) → better, but still some overflows.

                          [/code][/code][/code][/code][/code][/code][/b][/b][/b][/b][/b]

                          • [code][b][b][b][b][b][code][code][code][code][code][code]0.5 (every 1 ms half-cycle) + [code]sync0Shift=10000 → gave the [b]best result so far, but the overflow counter still increments slowly.[/b]

                            [/code][/code][/code][/code][/code][/code][/code][/code][/b][/b][/b][/b][/b]

                            • [code][b][b][b][b][b][code][code][code][code][code][code][code][b]Increased [code]sync0Shift from 1 µs up to 20 µs → small improvements, but not fully stable.

                              [/code][/code][/code][/code][/code][/code][/code][/b][/code][/code][/b][/b][/b][/b][/b]

                              • [code][b][b][b][b][b][code][code][code][code][code][code][code][b][code]Checked 0x60C2 (interpolation time) → confirmed it is [b]read-only fixed at 2 ms, so I cannot change the drives to 1 ms.
                                
                                Also i noticed in the tunner motion studio that all the drivers has EtherCAT slave ID = 2 , while it should be configured by the master which is wired.
                                 
                                my Questions : [/b]

                                [/code][/code][/code][/code][/code][/code][/code][/b][/code][/code][/b][/b][/b][/b][/b]

                                • [code][b][b][b][b][b][code][code][code][code][code][code][code][b][code][b]Is it valid/expected that [code]refClockSyncCycles="0.5" works better than [code]1 or [code]5? Or does this mean I have a deeper DC setup issue?

                                  [/code][/code][/code][/code][/code][/code][/code][/code][/code][/code][/b][/b][/code][/code][/b][/b][/b][/b][/b]

                                  • [code][b][b][b][b][b][code][code][code][code][code][code][code][b][code][b][code][code][code]For LinuxCNC + EL8 drives fixed at 2 ms interpolation, what is the recommended [b]refClockSyncCycles and [b]sync0Shift strategy?[/b][/b]

                                    [/code][/code][/code][/code][/code][/code][/code][/code][/code][/code][/b][/b][/code][/code][/b][/b][/b][/b][/b]

                                    • [code][b][b][b][b][b][code][code][code][code][code][code][code][b][code][b][code][code][code][b][b]Has anyone successfully run EL8-EC400F in CSP under LinuxCNC without sync overflows?[/b][/b]

                                      [/code][/code][/code][/code][/code][/code][/code][/code][/code][/code][/b][/b][/code][/code][/b][/b][/b][/b][/b]

                                      • [code][b][b][b][b][b][code][code][code][code][code][code][code][b][code][b][code][code][code][b][b]Any advice on NIC/IRQ tuning (isolated cores, rt-preempt) that could help with reducing these overflows?[/b][/b]

                                        [/code][/code][/code][/code][/code][/code][/code][/code][/code][/code][/b][/b][/code][/code][/b][/b][/b][/b][/b]

Apologies @Jmp97 your profile got deleted by accident. Feel free to reregister with the previous username/ password.