Hey David,
You are completely wrong. When Onefinity came up with the idea of developing the Onefinity CNC machine, they looked at what kind of controller that is available on the market could be used for their machine, which they could customize to fit their machine, and that they could also sell with the machine. The Buildbotics CNC Controller was, and is, a four-axis CNC controller that was not only available at a reasonable price, it is also a CNC controller where both the firmware and the hardware were released under a free license, it is Free and Open Source Software and also Open Hardware. So with the Buildbotics CNC Controller, Onefinity did not only have a CNC controller firmware platform available that they could fork to fully customize it to fit their machine due to the free license, they were also able to develop their own version of the hardware and produce the motherboard themselves due to the Open Hardware license, which was cheaper than buying the Buildbotics CNC Controller from Buildbotics and reselling it.
The Buildbotics CNC Controller, of which the Onefinity Controller is a software and a hardware fork, is a well-done, stand-alone universal four-axis CNC controller. It was ensured by its inventor that it was only released after it had been developed to a complete CNC Machine Controller according to the NIST RS-274 G-code standard. More than that, the Buildbotics G-code is patterned after the LinuxCNC G-code syntax. The Buildbotics Controller is a new CNC Controller written from scratch. Its inventor wrote the ➪ CAMotics 3D Toolpath Simulation Software before, and as you can imagine, in order to be able to do this, they had to implement in software any G-code commands you would expect to appear in a G-code program, and to implement a visualization of what the specific command will exactly do when running the toolpath.
Therefore, you can give the Buildbotics Controller (and the buildbotics-derived Onefinity Controller) nearly any G-code and it will run it very well and like expected.
(To be exact, you can see a complete list of the G-Code commands that are implemented on your buildbotics-derived Onefinity Controller’s User Interface at http://onefinity.local/#cheat-sheet. And if you click on “Show unsupported codes” on the bottom of the page, you can see which were not.)