Thank you so much for your interest and assistance. It’s just that elusive signal which preps the laser just before it fires. We’ve got all the x and y axis signals sorted and the grbl-lpc firmware flashed onto the Cohesion3d mini board and are communicating with it via Mac and Lightburn. The machine can technically handle 400mms (as per its brand new state with the original controller). I have been using it with grbl lpc but the speed is limited to about 100mm/s. The laser cutter control unit was missing its USB key for the original controller (currently unknown) so it was bypassed with an Arduino 2560 r3 when I bought it.
Quick Navigation Open Source Controller Boards Top
I hope the machine that I build (which uses a controller card which in turn use smoothieware) is not considered derivative work? This is referred to as the anti-Tivoization clause and is one of the main reasons for v3 of the GPL.This sounds better than I expected, I also contacted a hardware vendor who produce controller cards that run smoothiware and their opinion was similar. GPLv3 software does not require the hardware which runs it to be open source, but it does require the user be able to update the GPLv3 software running on the hardware. This is referred to as the anti-Tivoization clause and is one of the main reasons for v3 of the GPL. If you are selling boards with unmodified smoothieware pre-flashed, then you need to provide users a link back to the smoothieware repo and provide users instructions on how to flash custom firmware if they ask. The software that runs on the PC that communicates with smoothieware would not be considered a derivative work of smoothieware unless you took some code from smoothieware to use in the PC software. In this context, derivative work would be modifying the smoothieware code or putting a non-trivial part of the smoothieware code into some other software. I am not a lawyer, so take this with a grain of salt but I don't see a legal issue with what you have described.
0 kommentar(er)
