Advanced Search

it was on a belt drive with an omega style configuration.

Hakan wrote:

Can it also do g-code for plasma cutting?
 

Don't have plasma and can't say what is needed, but if you tell me what is missing I can expand it

Can it also do g-code for plasma cutting?

Okay, I will also make a video about what's happening and post it 

I have see value 1 on much example the xml file and not have problem with this value on debian 10 , lcnc 2.9.0-pre0 and ethercat 1.5.2.

I have test on debian 12, lcnc 2.10.0 and etehrcat 1.6.3 with value 1 and 5 and 1000 , but have error synch 5000 ms foe every drive.

only with -1 the error disappears.

What I don't understand is why on Debian 12, when LCNC starts, the PDO information is written to HAL after a few seconds and in sequence, one Ethercat node at a time from 0 to 5, while with the Debian 10 configuration, the PDOs are immediately read and updated in HAL, as soon as LCNC is running.

another difference between debian 10 and debian 12.
I use PCs with two ethernet ports.
With devian 10, with ip a I have 2 network cards enp1s0 and enp2s0,
while with debian 12 I have three, the two physical network cards and one with written: eoe0s0, which is created when ethercat is running.

Could it be that ethercat 1.6.3 unlike 1.5.2 uses a virtual card that in turn closes on a real one?

Why do you use refclocksynccycles=1? That's low.

for 2.5D you can try github.com/multigcs/viaconstructor/

As for as I know Heidenhain LS403 is a 11uA signal . Not 1Vpp.
Please check the datasheet

Back to the 'knowledge well'... sigh.

What I CAN do:
I have my motion control working (I can job X, Y and Z in the correct directions - or at least in the directions I want them to move when pushing the +/- buttons).
     - I had to 'reverse' the homing direction of my X and Y axes in the INI file, changing the lines:
       HOME_SEARCH_VEL = -0.050000  ; changed 0.050000 to -0.050000
I have my spindle control working - I can turn the spindle on and off from the Axis UI
I have my home/limit switches working - I can 'home' my X & Y (I don't have Z-axis home/limit switches)
     - the 'home' symbol shows in the DRO section of the Axis UI

What I CANNOT do:
1) I cannot 'touch-off' any of my axes. I homed all axes, jog my router off of the Home position, click the 'Touch Off' button and leave the defaults as presented, click the 'OK' button and immediately get an error stating "Can't issue MDI command when not homed. This of course also translates to my MDI (F5) screen when I attempt to move the router around using the G0 command
     - I am somehow way out of 'scale' with motion - I was planning on using the MDI interface to specify G-Code moves and measure results. Of course I immediately got the "Can't issue MDI..." error so I returned to the 'Manual' tab to ensure I was homed... which I was.
     - At this point, 'eyeballing' alignment with marks on the wasteboard, a 5" move shows as ~1.25" on the DRO in the X dimension. I'm guessing Y will be the same - but Z will be different because it uses a different Acme threaded rod.

I did try to find a solution in the 1347 pages of the manual... but that document is just absolutely overwhelming. In fact - I tried going through it again, one more time before I pushed 'submit' on this post (I DID realize that at least part of my motion scaling issue is my INI configuration). I even read the 'history' this time and realized that LinuxCNC emerged from a NIST project that was based on Windows NT... if ONLY the guys that were first involved would have stayed there (insert joking face emoji here).

If you want me to repost this as a new thread with a new title - I am happy to do it.

Well that's frustrating -- found this thread, got excited, read it to the end, and... crickets. :-/

What happened?

I assume you can't just change the Z0 location as you need the Z/Y to be zero'ed with the 4th axis center of rotation.  Otherwise you could probe the top of the part stock and use "G10 L2 P1 Z0" to set a new Z0 offset.

If that's the case you can try putting a stock stop in your collet block.  The collet and nut will change Z-position when you tighten, but the part should remain (mostly) stationary... much like a lathe stock stop attached to the spindle (and not the collet).

Kind of a poor-man's dead-length collet system.

What kind of shaft couplers are you using, and how is (was) the motor connected/aligned to the ballscrew?

For a control box, the simplest way is to use a switched, EMI filtered and fused IEC connector
www.amazon.com.au/uxcell%C2%AE-IEC320-Sw...Filter/dp/B01FT0VRTS
You can see one of these used at the bottom right of my photo shared earlier.

But in your case, this won't work if you want to switch the router on and off because the current of the router will be too high for the typically 6 amp AC rating. Plus you would not want the electrically noisy router to be on the same side of the EMI filter as your electronics.

So in your case, I would use a fixed power lead and a cable gland to bring mains into the control box to two household breakers around 10 amp. One of these will protect your router circuit and the other your electronics, On the electronics circuit, immediately after the breaker, fit an EMI filter
www.jaycar.com.au/240v-ac-emi-filter/p/MS4001
Then connect all of your power supplies to the filtered mains power.

Filtering the power is really important to avoid spurious triggering from electrical noise. I learnt the hard way.

The next thing to work out is your estop. That's a bit tricky because you need to disable the router and the stepper motor power supply without using any relays that could fail. The estop needs to drop power to your router power and  stepper mains motion. You could use 2 phases of a 3 phase breaker but technically you would then need  to use a safety relay to be compliant.
Its probably acceptable to disable your stepper drivers using the enable pins on them that are usually left disconnected.

 

At the minimum you should:

Expand the ferror limits as explained above.

Learn to use halscope.

It will not really be possible to tune without using halscope
regardless of the hal setup.



 

Thanks; you'd think I'd have learned that by now...:-\