Closed bjj closed 13 years ago
Thanks for the updates-
Any leads on the firmware update not working? I think the only thing that's changed there is accepting file URLs (file:///), but I think it's been tested on windows, mac and linux.
The firmware bad state issue doesn't sound great, either. We're not seeing much of that with gen4/makerbot, any theories?
After this release, I'm not planning on changing much with RepG for a while.
On Sun, May 22, 2011 at 12:08:46AM -0700, cibomahto wrote:
Any leads on the firmware update not working? I think the only thing that's changed there is accepting file URLs (file:///), but I think it's been tested on windows, mac and linux.
When I select "upload firmware" nothing happens. Probably it's throwing an exception I can't see. I did add new icons in my previous work and I fixed bugs with nonexistent icons causing crashes. Perhaps you didn't take either the icon or the fix and my personal firmware.xml is why I'm seeing the problem.
The firmware bad state issue doesn't sound great, either. We're not seeing much of that with gen4/makerbot, any theories?
No. I had done extensive testing to ensure you could recover from all kinds of failures (inability to connect, firmware resets, aborted builds) before my first big pull request.
After this release, I'm not planning on changing much with RepG for a while.
I am probably going to revert to the "24+" I had working. It does not feel like I can make forward progress with makerbot:master by submitting patches.
Ben Jackson AD7GD ben@ben.com http://www.ben.com/
This only modifies RepRap5d so hopefully there can be no objections!
I have not been able to test with firmware other than Klimentkip because "update firmware" does not work (?) at the moment. No dialog pops up.
I also fixed a glitch in the changelog that prevented the dist script from setting the version.
I only had time for very brief testing but this version does not work nearly as well as the modified RepG 24 my original mega pull request was generated for. Stopping leaves RepG in a bad state. Resetting the firmware while connected leaves RepG in a bad state. No time tonight to fix it all again :(