1.5 Beta 2 for BB Controllers (8/31/24) (Set Time and Date) (Outdated)

8/15/24

1.5 Beta 2

This is the third release version of firmware 1.5

This is test firmware. As with all test/alpha/beta software, DO NOT INSTALL unless you like to be on the bleeding edge and can live with potential bugs.


Beta 2 adds:

  • NEW. Ability To add date and time when offline. (Please note, due to the lack of battery in the controller on the raspberry pi, it is impossible to remember the time settings after a reboot or power off. You will need to manually reset the time upon every boot if your controller is not connected to the internet. If your controller is connected to the internet, the time will always be set automatially as long as itā€™s connected.)

  • NEW: Added text to the play, stop, load, ect buttons for clarification as many didnā€™t understand the difference between the upload FOLDER button (which only sees folders with gcode in them and will not show gcode) and upload FILE button (which only sees gcode, not folders).

Use the FOLDER button to upload a folder that has a bunch of gcode files in it.
Use the FILE button to upload a single gcode file at a time.

  • NEW: Remember last XYZ zero position upon reboot or estop (Must home machine first).

Download here

(click the blue link below to download. Do not unzip the file.):
bbctrl-1.5.0-beta-2.tar.bz2 (2.7 MB)


How To Install:

Updating via USB
Youā€™ll do an update via USB using the following steps:
After downloading, DO NOT UNZIP THE FILE!!!
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

Manual on how to update.

1 Like

Yesterday, I installed and tested the new firmware, primarily to ensure the XYZ position memory feature was working. Typically, my process involves setting the XYZ coordinates using the probe block, followed by a separate Z probe, as I base my parts on the spoilboardā€™s reference.

After completing this process yesterday, I attempted to reboot and reset the machineā€™s XYZ coordinates but was unsuccessful (absolutes and offsets were both 0.00 after homing). I then tried again using the probe block and restarted, then it seemed to have remembered some values, but they all seemed random.

I then manually adjusted the XYZ positions and saved them using the location pin button on the screen. Following another reboot and machine homing, I noticed that while the X coordinates were accurate, the Y coordinate had been lost, and the Z coordinate was randomly set around 20mm above the intended Z position.

Could you provide any specific instructions or steps I should follow to resolve this issue?

1 Like

Maybe the issue is that I dirty flashed this via the web ui file over the previous beta 1?

Iā€™m also seeing unexpected behavior when I test XYZ recall by these steps

  1. home all axis
  2. move xyz to some other position using jog buttons, make note of it x30 y20 z-10
  3. zero all offsets
  4. estop / estop again
  5. home all axis
  6. after homing, zero offsets are x30 y0 z0 instead of expected x30 y20 z-10.

attaching a before/after screenshot below in case that helps.

itā€™s weird since XYZ recall worked for me in the previous Beta 1.

edit: in case it matters, iā€™m using a remote Chrome browser, not the touchscreen.

Hope this helps!

reflash 1.4.1, the update to 1.5 beta 2 and try to reproduce it.

2 Likes

upload a video of this so the devs can take a look.

I have not made a video; but a few photoā€™s instead; I homed the machine, set XYZ using probe (Image 1 and 2)

Absolutes:
X:10.668mm
Y:10.617mm
Z:-56.574mm

Then I restarted the controller, and homed the machine (image 3 and 4);

Absolutes:
X:56.402mm
Y:10.894mm
Z:-84.261mm




I however did run the machine a whole day yesterday. I rebooted it just to see if it made any difference, and this time it did save the correct values for XYZ.

Could it be, that after setting XYZ you need to run at least 1 carve for it to save and store the values?

1 Like

Iā€™d love more guidance on how/when the XYZ home is actually stored. Is it when they are initially set? I canā€™t get it to work, and have seen more weirdness where sometimes it restores a previous X value, but the correct YZ values. and sometimes only X value, but not YZ values.

Anybody else tried this? Is it working consistently now for anyone?

It seems Iā€™m encountering the same issues as well. The machine has retained XYZ values that I initially set (about a week ago), but not the most recent ones. The XY coordinates were set manually using the location pin, and the Z was set using the probe.

Despite conducting several carves since then, restarting the machine multiple times, and resetting the XYZ values both manually and with the probe in between, it strangely does not store the latest set values but rather some values set some time ago.

This situation leads me to propose a feature that could potentially alleviate these problems and should be relatively straightforward to implement, given the current functionality:

The idea is to introduce a ā€œSave XYZā€ button that allows users to save the current XYZ coordinates under specific labels such as ā€œXYZ.1ā€, ā€œXYZ.2ā€, or ā€œXYZ.3ā€. Additionally, incorporating three buttons on the main interface labeled ā€œUSE XYZ.1ā€, ā€œUSE XYZ.2ā€, ā€œUSE XYZ.3ā€.

By saving the XYZ values under one of these three buttons, you can easily retrieve and apply them as needed. This feature would be particularly useful after restarting or estopping the machine and homing it, allowing for the selection of one of the 3 (or more?) predefined XYZ settings to establish the desired coordinates.

This approach would not only address the current issue of the machine storing random XYZ values but also facilitate the process of carving multiple items with different starting points. Moreover, it could significantly benefit users employing a tool changer, enabling them to assign distinct Z values for that tool.

1 Like

Iā€™ve tried it. It flat doesnā€™t work for me.
It got tested on a real project where it E-Stopped. I had to restart the project and nothing was saved.

Iā€™ll be honest hereā€¦and this is ONLY my opinion, I donā€™t speak for others.
I really donā€™t see the value in saving XYZ zero pointsā€¦not for me. Thatā€™s not even on the radar as far as feature enhancements for me.

Hereā€™s the issue:
If Iā€™m set out to make 10 widgets with some very expensive exotic wood, and I complete three of those today with the intent of completing the remaining seven tomorrow; when tomorrow arrives and I start the machine up, Iā€™m not going to just press run and hope for the best. Iā€™m going to verify the correct g-code file is loaded and selected , check that work is in place and secured, home the machine and probe X,Y,Z to verify everything is going to start out correctly. It doesnā€™t take that much time. Iā€™ve been burned too many times by assuming everything is just fine when it really isnā€™t. Everybodyā€™s had that same experience at one time or another. I just donā€™t see where saving X,Y,Z really provides any time saving benefit. Maybe Iā€™m missing something here.

2 Likes

I have a bug that could potentially be dangerous or scrap a project. When I home an axis individually, sometimes (not always) it indicates the actual position as being what it was before home while the spindle is actually at home. I noticed it on X axis, did not do it with Y axis for now, but again, the problem does not always happenā€¦

Beta updated!

Let us know if this fixes your issues!

1 Like