Uc300

[JAZZCNC]

Chaz if your converting lathe you want Centroid Acorn. Nothing else can touch it. Watch this.
http://www.centroidcnc.com/centroid_...ontroller.html

[Chaz]

Thanks, spotted it too, looks good.

Will it allow me to use a rotary turret with some form of macro like Mach?

[JAZZCNC]

Thanks, spotted it too, looks good.

Will it allow me to use a rotary turret with some form of macro like Mach?

Yes I think it's already setup to do that but if not then it can be made to do it thru macros and the built in PLC.

[m_c]

Chaz if your converting lathe you want Centroid Acorn. Nothing else can touch it. Watch this.
http://www.centroidcnc.com/centroid_...ontroller.html

I've been able to do all that for the past 5 years on my lathe (and not have limited IO)... ;-)

The real benefit of Acorn would be the conversational programming, but you have to consider how often you'd use it.
It is something I thought I'd really miss when I dumped Mach3, but in the past 5 years, there's only be once where I've really missed having the ability. However nearly everything I do is repeat production, so I design it once on a computer, generate the G-code, and copy it to the lathe where it remains with just an occasional tweak if needed. If I was doing more one-off/repair parts on the CNC lathe, I'd of probably pulled my hair out by now.

[JAZZCNC]

I've been able to do all that for the past 5 years on my lathe (and not have limited IO)... ;-)

To do that did it work straight out the box.? . . . How much C programming did you have to do to get it working how you wanted.?
How stable is the Software, is it tried tested on Industrial strength machines.?

There's more to a product than just I/O in my book. Look how many all singing dancing stuffed to the gunnels with I/O motion controllers have failed or been less than popular ie: Kflop . . just because there software is hardwork or just plain lacking or bug ridden.

Sometimes somethings are worth paying little more for even if sometimes that means getting less IMO.!

[m_c]

To do that did it work straight out the box.? . . . How much C programming did you have to do to get it working how you wanted.?
How stable is the Software, is it tried tested on Industrial strength machines.?

There's more to a product than just I/O in my book. Look how many all singing dancing stuffed to the gunnels with I/O motion controllers have failed or been less than popular ie: Kflop . . just because there software is hardwork or just plain lacking or bug ridden.

Sometimes somethings are worth paying little more for even if sometimes that means getting less IMO.!

Does Centroid, or any controller work straight out the box with no programming or configuration?
FWIW, for CSS and rigid tapping, examples are provided, and there are instructions on how to configure the software, along with example G-code.
As I've previously admitted, it's never going to be the easiest of controllers to setup, as it's that versatile, but I certainly don't go around telling others it's what they should use while failing to mention it's shortfalls.

Out of curiosity, how are you getting on with Centroid PLC Ladder? And will you be brushing up on Python for the new CS-Labs software?
We could argue about this all day, but the reality is, with any controller on any non-basic machine, you need to learn or at least understand the basics of some form of programming.

[JAZZCNC]

Does Centroid, or any controller work straight out the box with no programming or configuration?
FWIW, for CSS and rigid tapping, examples are provided, and there are instructions on how to configure the software, along with example G-code.

Obviously, that depends on the machine in question. Configuration yes certainly every machine needs to be configured for it to work. But basic's like CSS and Ridgid tapping shouldn't require programming skills. Even providing examples isn't acceptable IMO it should be implemented as standard, esp for Lathe.

As I've previously admitted, it's never going to be the easiest of controllers to setup, as it's that versatile, but I certainly don't go around telling others it's what they should use while failing to mention it's shortfalls.

For Lathe, it doesn't really have any shortfalls, which is what Chaz asked about. So I have no problem recommending this controller/software.

The only other thing possibly is only having 16 x I/O but for Lathe, this is enough. For more industrial Lathe setup yes wouldn't be enough but it's not sold as an industrial controller. They have more expensive (stupidly expensive) ones for those machines.
Same goes for Mill really, Software is rock stable and works out the box for any DIY Mill. For more advanced Mill with advanced ATC etc then yes limited I/O isn't ideal but like said before there's ways around this.

The only area it lacks in is having layout and setup which doesn't suit Routers, which is not where centroid have lots of experience. However, this being worked on as we speak, by them and me. Which takes me to your next point.

Out of curiosity, how are you getting on with Centroid PLC Ladder? And will you be brushing up on Python for the new CS-Labs software?

PLC Ladder isn't the most intuitive language I agree but it's not rocket science either. Like I said above the Router setup isn't great and at the moment the way it handles tool changes doesn't suit routers at all. However, after only a few nights familiarising my self with Centroids PLC/Macros and ways of working I now have Macro which sets it up to work exactly has would like. And trust me I'm no programmer so can't be that hard.

Edit: Also just to big up Centroid guys. After only asking one time on the forum within 3 days they provided two working macros to suit routers tool changing. They didn't suit what i wanted but do many others and I'm sure if I've asked they would have provided one for what I wanted but by then I'd already made my own.

Regards Python then I've used this before so holds no worries for me.

We could argue about this all day, but the reality is, with any controller on any non-basic machine, you need to learn or at least understand the basics of some form of programming.

I agree for more advanced setups but for basic Lathe or Mill or Router then No you shouldn't need to know any programming IMO.

[Ger21]

I think of the KFLOP as being a lot like Mach4. Enormous potential, but far too complex for the average user, and even what a lot of advanced users want to deal with.

[JAZZCNC]

I think of the KFLOP as being a lot like Mach4. Enormous potential, but far too complex for the average user, and even what a lot of advanced users want to deal with.

100% Agree and that's why I won't use them and think I can class my self in the advanced category.

[m_c]

Obviously, that depends on the machine in question. Configuration yes certainly every machine needs to be configured for it to work. But basic's like CSS and Ridgid tapping shouldn't require programming skills. Even providing examples isn't acceptable IMO it should be implemented as standard, esp for Lathe.

You don't really need programming skills though. You just need to copy and paste.

For Lathe, it doesn't really have any shortfalls, which is what Chaz asked about. So I have no problem recommending this controller/software.

The only other thing possibly is only having 16 x I/O but for Lathe, this is enough. For more industrial Lathe setup yes wouldn't be enough but it's not sold as an industrial controller. They have more expensive (stupidly expensive) ones for those machines.
Same goes for Mill really, Software is rock stable and works out the box for any DIY Mill. For more advanced Mill with advanced ATC etc then yes limited I/O isn't ideal but like said before there's ways around this.

16 IO would depend on the type of tool changer used. I know on my turret, it needs 6 inputs alone, along with 3 outputs. Combine with 2 homing switches and that's all the inputs gone. Now where do I connect the E-stop? Or as you've previously advocated, where do the limit switches go if you're not wiring them as part of the E-stop circuit?
And I'd love to know your way around the lack of IO?

PLC Ladder isn't the most intuitive language I agree but it's not rocket science either. Like I said above the Router setup isn't great and at the moment the way it handles tool changes doesn't suit routers at all. However, after only a few nights familiarising my self with Centroids PLC/Macros and ways of working I now have Macro which sets it up to work exactly has would like. And trust me I'm no programmer so can't be that hard.

Regards Python then I've used this before so holds no worries for me.

So what you're essentially saying is, you're happy to learn a language when it suits you, yet criticise others for using a different language when it doesn't suit you?
;)


FWIW I do think the Centroid software looks good, but I think the Acorn is just too restrictive for anything other than a basic machine and I think they could really do with something that sits in between their current offerings. But I'd just hope they don't put relays on it. That really is one of my pet annoyances. If I want a relay, DIN mounted relays come in various sizes, so I can pick the one most suitable for the load, and not be stuck with a one size fits all that will likely die because of switching too much or too little current.