3 ms·

We're in a similar position and the PC runs DOS, with all of it's memory limitations. Any of our bigger pieces need to be run in multiple jobs as one job won't

We're in a similar position and the PC runs DOS, with all of it's memory limitations. Any of our bigger pieces need to be run in multiple jobs as one job won't hold enough data to complete it.

Gracana 5y ago
You may be able to use a "drip feed" / DNC (direct numeric control) system, where NC code is fed to your machine from an external controller. At a previous company we had a modern PC on the network, with connections to ethernet COM port modules installed on the CNC machines. You'd choose a program for a machine, set up the machine controller to run a program from tape (or somesuch.. it depends on the controller), cycle start.. boom, you're running a large program over the network. It's a very handy solution.
- bluedino 5y ago
  We have Moxas on almost all of our machines now. This one is a special case.
- Brian_K_White 5y ago
  Sounds like Klipper but for cnc. The scheme is a huge win on 3d printers even though it adds a component to the system (generally a bad thing all else being equal, but all else is not equal). Even when you aren't talking about being stuck with some old proprietary and limited controller & firmware but can buy powerful new wide open controllers and load your own up to date open source firmware on them, it still ends up being even better to have the minimal klipper firmware on the controller and do all the real work on a host.
jonhohle 5y ago
While I don’t recall ever having a problem with DOS, have you ever tried OS/2? We never attempted it due to the relative fragility of the system and lack of support, but thought it would have provided some more modern capabilities (this was back between 2000-2003).
- bluedino 5y ago
  Unfortunately it wouldn't help since you'd still need to re-write the program (or at least port to a 32-bit compiler and use a DOS Extender), it's the 64k memory segmentation that's the issue

We're in a similar position and the PC runs DOS, with all of it's memory limitations. Any of our bigger pieces need to be run in multiple jobs as one job won't hold enough data to complete it.

Gracana 5y ago

You may be able to use a "drip feed" / DNC (direct numeric control) system, where NC code is fed to your machine from an external controller. At a previous company we had a modern PC on the network, with connections to ethernet COM port modules installed on the CNC machines. You'd choose a program for a machine, set up the machine controller to run a program from tape (or somesuch.. it depends on the controller), cycle start.. boom, you're running a large program over the network. It's a very handy solution.

bluedino 5y ago
We have Moxas on almost all of our machines now. This one is a special case.
Brian_K_White 5y ago
Sounds like Klipper but for cnc. The scheme is a huge win on 3d printers even though it adds a component to the system (generally a bad thing all else being equal, but all else is not equal). Even when you aren't talking about being stuck with some old proprietary and limited controller & firmware but can buy powerful new wide open controllers and load your own up to date open source firmware on them, it still ends up being even better to have the minimal klipper firmware on the controller and do all the real work on a host.

jonhohle 5y ago

While I don’t recall ever having a problem with DOS, have you ever tried OS/2? We never attempted it due to the relative fragility of the system and lack of support, but thought it would have provided some more modern capabilities (this was back between 2000-2003).

bluedino 5y ago
Unfortunately it wouldn't help since you'd still need to re-write the program (or at least port to a 32-bit compiler and use a DOS Extender), it's the 64k memory segmentation that's the issue