|
|
|
|
|
|
by danshapiro
3921 days ago
|
|
|
Cofounder/CEO here, just finished with Makercon and catching up. The Glowforge does require a cloud connection to operate. We use cloud vs. local a host of reasons including the motion planner, alignment, image recognition, and faster feature development. But based on the excellent point made here that nobody wants a paperweight if we fall off the globe, we decided to make a change. We're going to do a GPL release of the firmware so people can do whatever they want, including porting offline functionality. You buy it, it's yours, you should get to do what you want with it. http://glowforge.com/gpl-licensed-open-source-firmware-for-g... Thanks for the great feedback. |
|
|
1. When you mention planner, etc, does this imply the cloud service is involved not just in a prep phase, but actively during the control loop while the device is cutting? The latter would be worrisome to me.
2. Will you be able to elaborate at all on the functionality of the firmware (and/or provide protocol documentation for it) prior to ship? I'm not sure how comfortable I am pre-ordering without understanding just how much work there is between the device as delivered and an actual, functional, standalone cutter.
I see on the blog that modifying the firmware invalidates warranty coverage. This seems like another argument for protocol docs and/or ability to usefully have at least one cut path that does not tie you to an online service or nuke your warranty.