quote from other thread:

Quote Originally Posted by JAZZCNC View Post

However there are many potential pot holes it could fall down on like Canned cycles etc, long cycle times etc.
Lack of memory is also another issue. Even the higher spec controller is memory limited. 32Mb or even 64mb isn't enough for Large 3D programs and will require DNC to drip feed the code. For some 32Mb may seem plenty but I can tell you some the people I help have 3d files in the Gb's. Pauses or temp locks while dripping code, even if position is not lost, is problem on 3D surface because it leaves mark which wreck the job or at best cause extra work hand finishing.
Dripping from USB isn't always reliable and RS232 just defeats the point of stand alone Controller. All these things have to be tested and influence the final outcome.!! . . . . Unfortunately again we are back to Cracking open the Good or Bad Egg.?

After talking with a couple of manufacturers unfortunately that seems to be the case. The typical answer i received was:

Our CNC controllers are using standard G code, the system can be directly copied from the U disk file to the system processing, but can not directly use the U disk online processing.The file size depends on the disk space of our system.The largest disk space of our system is 128M.

Its incredible but the mini controller DDCSV1 beatas them on that front. I will continue its review in the relative thread. Just would like to say here that it reads and executes 10 million line file without a glitch. From start to end. There were some glitches at first and at the end i found that was because i was not using the original pen drive. Once i started doing that, 2 weeks of perfection till today, working 8h per day at least non stop.

If you wonder how i managed to make 10 million line file. Very simple. Milling 1300x1000, trochoidal using 6mm bit. it was not big on size though. So at the end that memory limit could not be such big problem as it seems.