How To Install: Updating via USB
You’ll do an update via USB using the following steps:
Copy the blue .bz2 file above onto a usb stick (it must be formatted as fat 32 or ntsf). Click the flyout menu (three bars on top left), general, under firmware click ‘UPLOAD’. Select the 1.3 file.
If you are on firmware 1.0.8 or lower, it may ask for a password. the password to update will either be buildbotics or onefinity
No Gcode uploaded or stored
Prob X Y Z
Prob lower-left corner of material ( 1 inch X and Y axis from home location )
After prob complete. Move z axis up to install dust collection brushes.
Moxe X Y axis back 2 inches.
Click the home button,
Receive the following error message.
I get a different error message every time but always says less than the soft limit.
The only way I found to resolve it is to reboot the system.
I reflashed and Installed firmware. 1.2.1, repeated the same steps, unable to reproduce the error messages.
Machine was Homed and Zeroed as I already did many times with the standard firmwares. It never happened before, only with the alpha firmware.
I have been able to solve the issue rebooting the machine even if it randomly appear again. I do confirm buttons sometimes turn green off and on randomly.
Anyway even if it’s not in error, the depth of the cut is not correct: it’s more or less double the expected measure.
Interesting to see this Alpha version up for almost 1.5 months and see very little activity here other than the classic “Under & Over” issue. The good news is that I don’t see a ton of bugs being reported but I also don’t see many of the most active users/contributors (the ‘usual suspects’ that we rely on so much; thanks again) saying that they’ve upgraded to v1.3 and are so very happy with the results. I’m in the process of installing my PwnCNC spindle and would love to see the VFD in the dropdown.
So, how about a roll call of thrilled v1.3 users??
I upgraded to 1.3.0 Alpha 2 today and ran a few quick tests today. Things seems to be working nicely so far. I like the new sort ordered by upload date descending in the ui dropdown. That probably helps reduce the chances the wrong file gets selected when the 1st file mistakenly gets selected after upload. (i had previously uploaded a BLANK.gcode file in that spot (with the old case sensitive alpha sorting) that prompted me to attach the probe just in case).
Thanks for the continued work on the firmware!
edit. i uploaded files from a remote web browser, xyz probed, used gamepad, ran some gcode files selected in both the local and remote browsers.