Advanced Search

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)

Moin Muecke,

sei mir nicht böse aber in der Zeit in der Du deinen Post verfasst hast, hättest Du locker mal googeln können
wie man die Uhrzeit einstellen kann.

Debian 12 Uhrzeit einstellen

Dann muss man halt etwas probieren, welche Lösung passen könnte...

Gruß

Lampje wrote:

You are saying that in LinuxCNC you have to tell it how many microsteps are in 1 regular step?

No, not LinuxCNC as it uses steps per unit only, but you can tell it on wizards in several ways.

Lampje wrote:

But how do i know how many full steps there are in 1 revolution?

Motor steps per revolution are 200 usually, there are other types with 400 steps per turn but are rarely used in hobby machines. And there are also 3 and 5 phase stepper motors that have 300/600 or 500/1000 steps per revolution.

Lampje wrote:

So to what number would I have to change the 1000 then? And what about the step times?

That you will have to figure out depending on your setup:
-belt drive = pulley / teeth / pitch / reduction if any
-ball screw or lead screw = pitch per turn
etc

We use these:

It's a fuse and a switch in the same box, the picture shows 2 of them.

Hi PCW.
The dip's on the drivers have it as needing 1600 (or 25600) pulses for 1 revolution.
In the stepper settings in Lightburn you set the pulses per revolution, so 25600. And I was expecting the same behaviour in LinuxCNC.
You are saying that in LinuxCNC you have to tell it how many microsteps are in 1 regular step? But how do i know how many full steps there are in 1 revolution?
So to what number would I have to change the 1000 then? And what about the step times?

unknown wrote:

One thing you need to remember is that the PSU have an initial inrush current that is greater than the max current the PSU draws when running.
I went with fuses rather than circuit breakers.
 

Thank you Rob. I have found the following specs on the MDR-100-24 PSU:



The full PDF document address is: 100W Single Output Industrial DIN Rail Power Supply MDR-100 series
Best regards,

...behai.

I don't think the 1600 and 25600 numbers are microsteps, but rather
steps per turn, so 1600 = 8 microsteps and 25600 = 128 microsteps