After Upgrading, All Files Have X and Y "Under" on Axis Table.

Post technical questions about the Buildbotic Controller here.
Forum rules
No profanity, no gambling, no illegal activity, so sexual or pornographic material.

Posts not related to the Buildbotic CNC Controller are likely to be moved or deleted.
Post Reply
missionarymike
Posts: 15
Joined: Mon Mar 29, 2021 6:46 pm

After Upgrading, All Files Have X and Y "Under" on Axis Table.

Post by missionarymike » Tue Apr 05, 2022 5:39 pm

Since upgrading, all files, new and old, all show an "under" warning in the axis table after loading. The soft limits have not changed, and my files are all set as a lower left origin, so it is weird that both axis are under.

And to top it all off, i somehow deleted the configuration backup yesterday after doing some server maintenance...

The 3D viewer doesn't show any issues either.

Mike
Last edited by missionarymike on Tue Apr 05, 2022 6:40 pm, edited 1 time in total.

missionarymike
Posts: 15
Joined: Mon Mar 29, 2021 6:46 pm

Re: After Upgrading, all files have X and Y axis "under" on axis table.

Post by missionarymike » Tue Apr 05, 2022 6:30 pm

Just an update.

Doug emailed me back and said this is a known issue and they are working on a fix, hopefully later this week.

In the meantime, just revert back to a backup of the configuration prior to upgrading.

Here is the latest release candidate for you to download and revert too, if you lost a backup like i did. This can get you to a running configuration prior to this upgrade. Doug is on vacation and has limited access to email.

http://buildbotics.com/bbctrl/bbctrl-1.0.1-rc28.tar.bz2

Just download it to the machine and then select "upload" from the "Settings - Admin" page.

After you revert, if you have to, make sure you go ahead and create a new backup so you are ready when the upgrade fix is released.


Mike

User avatar
Doug
Posts: 343
Joined: Fri Feb 02, 2018 4:56 pm

Re: After Upgrading, All Files Have X and Y "Under" on Axis Table.

Post by Doug » Thu Apr 07, 2022 3:30 pm

We released Version 1.0.3 to fix the problem described here. Try upgrading again.

Doug

Post Reply