What would it take for developers to interface with the motion control back-end from other architectures? For example, bCNC or a USB Motion Plugin for Mach3 controlling the BuildBotics controller instead of the standard web-based GUI?
These systems have unique features that would help users transition to BuildBotics more seamlessly. I am interested on working on this feature, but I'm not familiar with the codebase so some guidance would be welcome.
What would it take for developers to interface with the motion control back-end from other architectures? For example, bCNC or a USB Motion Plugin for Mach3 controlling the BuildBotics controller instead of the standard web-based GUI?
These systems have unique features that would help users transition to BuildBotics more seamlessly. I am interested on working on this feature, but I'm not familiar with the codebase so some guidance would be welcome.