CNC Brain is ready! 6-axis Double Closed Loop Controller

[Switcher]

turmite,

Thanks for the answer above.


---------------------------------------------


Have you bought one of the CncBrain's yet, If so how's it working for you?


.

[brccrb]

**Turmite,
You are never out of line and always have the most excellent suggestions!

Great idea!

**Peu,
Fantastic question! Actually the Control Panel was intended for a lot of different types of machines. For example, the Tools Tab uses X,Y,Z,A,B, and C offsets. This was specifically with lathes in mind.

On the short list is support for threading, including rigid taping (both very close to the BitSave functionality already there).

Sleep? What's sleep? Seriously, just trying to cover all the bases. Now, I'm sure I'm going to goof something, but it won't be from a lack of sincere intent .

**Regnar,
Purse!! Wow! CNC Brain is really inexpensive. The Brain was designed to return the cost of the device very quickly.

**Switcher,
Yes. About 200KBytes. It uses the memory primarily for caching instructions, look ahead, and ... the key point ... dealing with the USB interface.

The CNC Brain, through the MPP, is a little different from standard processing. In a PC, the processor uses memory like a filing cabinet. In the Brain (which is why it is named such), it resembles the functionality of an animal brain ... everything parallel. So, while the PC is doing the "bit shuffle tango" with the memory, the Brain just does it.

Excellent question!

[Switcher]

brccrb,

Thanks!

Can't wait for the next version (SDK), to see what else you come up with.

I've been looking thru the SDK, man you really have a lot of work in this.


.

[brccrb]

**Switcher,
To have such a brilliant person as yourself say that means alot. Thank you.

Going through v1.0.5 right now.

Near Future: Version 1.0.6 (should be next week) will have the direct Rhino-to-G-Code import option . This should save some people a bundle (and a quick tool for some that may already have CAM). If you have a router based mill for cutting plywood or letters, then all you would need is Rhino and a CNC Brain as the Control Panel is free.

In Rhino, just draw the lines (or for text, the text as lines) to create the toolpath. To compensate for tools diameters, just "draw" the tool and place it on your model. Then draw lines between the tip centers to create the lines. Tada, your very own manual CAM program (beats G-Coding it ).

Will be adding DXF support later (just have the Rhino SDK already, so its first).

Looking for time to use the Brain to create an 80/20 based loading robot. Itching on that one.

Again, thank you.

s/Bruce

[turmite]

Originally Posted by Switcher turmite, Thanks for the answer above. --------------------------------------------- Have you bought one of the CncBrain's yet, If so how's it working for you? .

Switcher let's say I have one scheduled, but due to my wife being diagnosed with a most severe invasive carcinoma breast cancer, things are kinda in a whirlwind right now. She starts chemo next week and we have no idea what the future holds, so things are kinda on idle!

Mike

[Khalid]

Turmite.. Lets Cross the fingers...I will pray for her to have a long long healthy life...

[PEU]

Originally Posted by turmite Peu wouldn't canned cycles be functions of the gcode and made available in the post processor? I still think some are confused about what the Brain is. If I attempt to clarify this, I by no means am trying to be condesending.

I know my question aimed at the response that Bruce provided, It should been asked this way: if I buy cncbrains today can I use it in a lathe or I need to wait for certain features to be finished?

Now for a new question:

I know no one should compensate with software hardware defects or limitations, but given the abilities of the cncbrain to predict and compensate errors, in a retrofit scenario, what would be the point of replacing regular screws with ballscrews? just toss some large steppers or servos, add the required encoders and lineal scales and call it a day. Am I missing something here?


Pablo

[turmite]

Originally Posted by peu I know Now for a new question: I know no one should compensate with software hardware defects or limitations, but given the abilities of the cncbrain to predict and compensate errors, in a retrofit scenario, what would be the point of replacing regular screws with ballscrews? just toss some large steppers or servos, add the required encoders and lineal scales and call it a day. Am I missing something here? Pablo

Pablo I suppose the correct answer would be how long do you want your machine to last? The better the compontents the longer the life. I personally will not be using ball screws whether I retrofit my current machine, or build new ones, and I say ones because I need to build three. My current machine uses rack and pinion and my builds will either have r/p or timing belts!

Mike

[PEU]

Originally Posted by turmite Pablo I suppose the correct answer would be how long do you want your machine to last? The better the compontents the longer the life. I personally will not be using ball screws whether I retrofit my current machine, or build new ones, and I say ones because I need to build three. My current machine uses rack and pinion and my builds will either have r/p or timing belts! Mike

what if the machine to retrofit is new?

[turmite]

Originally Posted by peu what if the machine to retrofit is new?

The answer would still be the same. How long do you want the machine to last? Better parts, longer life. I don't know that I would want to build a less quality machine just because the Brain will make it better. If we start down that slope/hill, somewhere down the road, someone will build a machine that won't work even with the Brain, and then they will blame it on the Brain. Who's fault would it be......builder of the machine, or the Brain?

Mike

[brccrb]

**Peu,
First, the only things not yet added you mentioned are the rigid tapping and threading. Those are coming up.

For the other functionality, it should be there.

-- As for the "new question", that is the idea behind the CNC Brain. Thank you for bringing it up.

Seems like, sometimes there is a gap between the two camps: home and pro. The pro (with the capital already invested is focused on getting the job done now!) may not understand/remember the challenges of the home CNCer (who is just beginning to invest and focuses on a prototype or limited production).

Though at times it seems like a conflict, places like the CNC Zone help everyone with experience flowing from the pro to home, and new ideas flowing the other way.

So for both cases, the CNC Brain was designed. For the pro (mid range), he gets closed loop to improve his processes (less waste = more profit, quick ROI). For the inventor, he gets to keep his investment low and have the functionality needed for prototyping (get the idea off the ground).

From the comments Turmite made, you can tell he is concerned with production (and in his case, often unique item production which is prototyping and production in one nutshell). He needs accuracy to prevent waste.

From your comments, you want to take that most excellent human quality (invention) and see where you can take it ... with the least money possible. You need accuracy for prototyping.

We spent a lot of time making sure the Brain could grow with the home CNCer. That is why it runs mixed mode (Open/Closed/Double Closed for any axis). You start off with "something", and if it goes the way you want, you grow your equipment and ideas until it becomes a business unto itself.

Hopefully, in time you start worrying about MTBF and production rates and ROI ... all the fun stuff when your dream is your business.

Great point!

s/Bruce

[brccrb]

**Turmite,
Excellent point! There are physical boundaries to any machine. The accuracy increase from the CNC Brain is function of the machine to start.

The idea is to close G-Code/prototyping gap and make the machine run reliably.

After that, it is a function of where to improve (speed, power, rigidity, etc.) ... then human greed kicks in ... more power, more speed ... grunt, grunt


s/Bruce