Advanced Search

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...:-\

Yes thank you but then I have no idea how to do it .

Regards

I'm just using F360, I draw all my work in there, often using the sheet metal functions when the target is plasma cutting.
Flatten the part and insert some bend relief lines. Generate G-code.
The "new" F360 post processor works great. Spotting, small holes, cutting with and without lead ins/outs.

QtPlasmaC can do many things on its own.
Cutting using an rotated coordinate system no problem with a laser marker.
It can't do nesting but it can make multiple parts in one or two dimensional arrays.
Load the G-code and use the block feature in the conversational section.
QtPlasmaC can also do wiggle piercing or ramp piercing, just that this needs to go
into the post processor and there it isn't. So hand editing.

I was set on using Sheetcam again after I rebuilt the plasma table, which took long enough time that I forgot how to work with Sheetcam.
The "new" F360 post processor made wonders, that problem with "arc ends differ" was a real annoyance but is completely gone.
A drawback is the kerf width which is hard-coded in the G-code file. If I change my mind at the plasma cutter I must regenerate G-code for the new kerf width.

Regarding nesting, check out www.deepnest.net/en/ that does nesting of svg and dxf 2d parts.
A browser version of an early version to quickly try is here svgnest.com/ (skip deepnest.io)

Hi at all.
I have install r8168-dkms, but not have result , the wait time for read pdo is present again and in dmesg have again wait synch message.

I have in refClocksynccycles =1.
If change refClocksynccycle at -1 , not have error synch , the wait time for read pdo is more short, but on debian 10 is more fast .

I thing the problem is in ethercat version, the version installed on debian 10 , the 1.5.2 is more fast at start up .

And i don't undestand why with debian 10 and the same ethercat configuration use
refClocksynccycles =1 and on debian 12 use refClocksynccycles =-1

Hi, Thanks for the input.

I finally did get the motors to turn*. And rechecked the micro steps. They were actualy set to 1000 pulses/rev. One of the driver documents listed the dipswitches wrong....

In the wizard i got it to run at least. But having completed the setup the motors won't turn from the interface.
There is no enable wired to the drivers. And it has functioned (back in 2017) without the enable wiring. Weird.

If you divide the steps/turn by 200 (full steps per turn), you get the microstep ratio
(for 99% of 2 phase step motors)

Microsteps are by definition the number of step pulses needed to get a full step.

I would start with 5 usec (5000 ns) for steptime/stepspace as a starting point and only decrease
them if you can't reach the desired velocities (and the drive can accept shorter pulses)

I would use 20 usec (20000 ns)  for dir setup and hold (as this has no real effect on performance)