Advanced Search

Hallo!
Mich würde interessieren ob linuxcnc mit PAL, Sinumeric / und oder Haidenhain kompatibel ist oder ob es etwas eigenes macht.

Vielen Dank im voraus.

MfG R.Lehmeier

A diagram of the hal logic for disabling with NC inputs might look something like:

Not sure if it is absolutely necessary, but let Ethercat have its own port.
Daisy.chain is mandatory.
First slave in the daisy chain is slave 0, and so on. The network ports are marked In and Out, follow that.

EtherCAT uses a special technique to strip and fill in data in a packet on the fly.
One packet to send data to all clients. The same packet on the way back picks up data from all clients and give that to the EtherCAT master.
 

Thanks again. Initially I plan to do this using a Raspberry Pi using software stepping through GPIO, so I am a bit concerned about the Pi being able to keep up with encoder pulses. If it doesn't work on just the Pi, I will get a 7C81 Mesa board for it, but want to try using just the Pi first.

I don't ever see needing to use the spindle as a dividing head. I have a 4th axis on my mill if I need that, so I think two encoders, one for index and one for pulses would work okay for what I need. We will see.

Looking at your picture, that is almost exactly what I was picturing for the slot sensor mounting. I may try a 3d printed slot wheel. We'll see if it flys apart, but I generally don't run too high speeds and think it will be fine. I'll print it at 100% infill and make an aluminum hub to sanwich behind the pulley.

What brought this about is that the threading nut setup on the lathe broke last time I needed to thread a part and I figured it was time to convert to CNC. I plan to include 2 MPG handwheels mounted on the carriage so that I can mimick a manual machine for times when I just want to do simple turning. I have that worked out on the Pi already. I use a handheld wireless MPG on my mill but am thinking about adding 3 handweels and eliminating the wireless MPG. I've had a few loss of connection issues with it in the past.

This is a long term project so things won't happen too fast. I have access to a friends 13" Clausing lathe if I need one and he is only about 3minutes away. I have another big project I'm working on and this one is a fill in for times when I need a break from that one. Thinking about the basic X-Z conversion, the Z axis looks like a piece of cake, and if that 12mm ballscrew I got fits, the X axis cross slide won't be too bad either.

Thanks again.

If your probe contacts are normally open you could simply pass them through a Hal or2 component.

If your probe contacts are normally closed then you would pass them through an and2 component. With this arrangement you would need to have something to disable one of the inputs if one was to be used while the other is disconnected. For that you could either use a dummy shorted plug or use more Hal logic. Such as passing the signals through another set of and2s or something simular.

Also you many hardware drivers have a -not option for their inputs. You can use those or a "not" component to change the polarity of an input signal if you need to.

The mux component is more for choosing between 2 different "float" values (aka numbers), and isn't really what is needed in this application.

Okay so with an MPG that has rotary switches or buttons, you don't have to use the interface you can do everything right at the mpg so I think that fixes your issue there's nothing special just pick the one you like.

Ok. I started again from 0.

I downloaded the linuxcnc-uspace_2.9.3_amd64.deb file.
I extract the files in a newlinuxcncn directory.
I replace the qtaxis.ui with my qtaxis.ui

What's next ?
I ask in order not to commit mistakes.

Thanks a lot.