BDI Live will need 256M RAM
when run from CD. So one solution is if you can borrow more memory from another machine, install to hard disk, then you can go back to 192M again. When run from CD, it needs RAM to use as a RAMdisk. Then it will not even touch your HD until you choose to install it there.
I find it hard to do a review of a control program. It's like doing a car review, if you followed my recommendations, you would drive the most twisted roads in your county just for fun, but your groceries would have to be brought home in a wheelbarrow.
It all depends upon what you need it for, and what your preferences and background is.
EMC needs to boot it's own kernel, as it is based on the RTAI real time system that is compiled into the kernel. If you know Linux, it should not be difficult to make it a boot option into it's own partition. EMC cannot be installed just as an application program onto an existing kernel. You can do that if you just want to look at the GUI and run the backplot though. But you can't run your machine then.
I don't think showing screenshots is very useful for several reasons:
- There are at least 3 different user interfaces for EMC. You can choose the one you like the best, or even pick the one closest to your liking and customize it. That would be only if you can do a bit of programming though.
- The user interface is one of the least important points IMO. That's just the "operator panel". It does not help a bit if you like it a lot if the works behind it does not do a good job, and/or it cannot be tied to your hardware.
EMC is very flexible when it comes to connecting hardware. If you start out with steppers, then find that too limiting and want to change to servos no problem, just fix the .INI file to reflect what you have connected. (Some configurations, like servos without step/dir interface need special hardware. Even though it should be obvious, I mention it). This versatility is the main reason I chose EMC and not Mach2. I don't want to be forced to change control program for running high speed servos which is my next stage.
If your need for speed is moderate, it can be connected directly from the parallel port to your step/dir drives. There should be a breakout board in between if your drives do not have galvanically separated inputs (optocouplers).
If you need to go fast, you should consider one of the hardware options that makes this possible. I'm upgrading to pico-systems Universal Stepper Controller. A friend of mine already use it, and his old PC can spit out step pulses faster than any motor can swallow them. Other possibilities are ISAbus or PCIbus analog servo control boards. There are several to choose from at reasonable prices.
As I mentioned, the user interface can be first chosen, then changed. I have an industrial PC with integral LCD touchscreen that I want to use. As all the source code comes with it, I can adapt whatever needed to exploit that possibility.
All this adaptablility comes at a price: You should have a bit of stamina to get it running. If not, you should at least choose one of the example setups. The documentation is scattered and not well updated. I found this frustrating at times, but the EMC community is very helpful, and I got a system I feel can do whatever I want to do in future projects. At the moment it is not suited for lathes (no threading), but this is one of the highest on the priority list for EMC2 that is well on it's way. So I stay confident that when I get to retrofitting my largest lathe, EMC2 can do it.
The closest I found to EMC is Mach2. It's not for me, as it is closed and I would have to live with the existing interface to the drives which to me is not an option, I need more speed and versatility. If you like to just answer "yes" when asked if you want to install, then be up and running the same evening, Mach2 could do that if you just read the nearly excellent manual. BTW, read the Mach2 manual even if you don't intend to use Mach2! My hat off to the guy that wrote it.
I also lisenced TurboCNC the other day, so I can probably soon see what's in that program. Reason for that is I need a quick and easy replacement for the ancient controller that my Emco Compact5 lathe came with, and as mentioned EMC can't do threading just now. TurboCNC also comes with source code, so even if the 100-hole spindle encoder of the Emco does not fit in with the program, I can choose to alter the lathe or the program. Whichever I feel give the best result.
Hopefully my ranting have given been of use to you even if it is not a review.