# Onefinity firmware

**URL:** <https://forum.onefinitycnc.com/t/onefinity-firmware/12673>\
**Category:** Controller (Buildbotics) Discussion\
**Created:** [April 24, 2022, 12:29am UTC](https://forum.onefinitycnc.com/t/onefinity-firmware/12673 "2022-04-24T00:29:50Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![WaywardWoodworker](https://avatars.discourse-cdn.com/v4/letter/w/e79b87/32.png) [@WaywardWoodworker](https://forum.onefinitycnc.com/u/WaywardWoodworker)\
**Post date:** [April 24, 2022, 12:29am UTC](https://forum.onefinitycnc.com/t/onefinity-firmware/12673/1 "2022-04-24T00:29:50Z")

</div>

What is the ETA for bug fixes in the Buildbotics firmware to make their way into the Onefinity firmware fork? This one has been driving me nuts and looks to be resolved on the Buildbotics version

> <https://github.com/buildbotics/bbctrl-firmware/issues/297>
>
> G53 tells the controller to move in absolute coordinates. Assume the following:
> …
> 
> \- X position is 0
> \- X absolute is 100
> \- X offset is -100
> 
> Then execute the following command
> \`\`\`
> G53 G0 X50
> \`\`\`
> The system will correctly move to the following:
> 
> \- X position = -50
> \- X absolute = 50
> \- X offset = -100
> 
> However, in the simulation, it seems to add the current X position to the target position in the G53 move which would result in X absolute position being 150. If this is beyond the upper soft limit, then 'OVER' is displayed and the axis line turns yellow.
> 
> The same thing happens when using G92.2 to adjust the code. G92.2 is supposed to disable the offsets. Once again, executing the following code works correctly;
> \`\`\`
> G92.2
> G0 X50
> G92.3
> \`\`\`
> This moves to absolute position 50 and sets the position and offsets correctly. However, it results in a 'OVER' condition in the simulation if the current x position plus 50 is greater than the upper soft limit.
> 
> This problem occurs in the current version (0.4.15) and in the current beta release (1.0.0rc15).

I realize the Onefinity fork is now heavily customized however it seems some of the innovations in the Buildbotics controller over the past year aren’t making their way over (like macros), it would be awesome to know what is on the horizion.

---

<div class="post-metadata">

**Author:** ![Atroz](https://avatars.discourse-cdn.com/v4/letter/a/958977/32.png) [@Atroz](https://forum.onefinitycnc.com/u/Atroz)\
**Post date:** [April 25, 2022, 1:56pm UTC](https://forum.onefinitycnc.com/t/onefinity-firmware/12673/2 "2022-04-25T13:56:57Z")

</div>

I hit a similar bug this weekend. I’m new to this and it threw me for a while. Using Carveco Maker+ I had a 3D carve with 3 tool paths. I did the profile cut first, which cut to the bottom of the piece. Then the 3D rough and finish paths. In the simulator the 3D tool paths start below the Profile tool path, and therefore below my wood. I never attempted to run it because I didn’t know what would happen (if it even allowed me to run).

I’ve checked the G-code and have no G53 or G92.x that I can find. It seems to be adding to the last cutting position (even though there is a Z-safe done between) instead of going to the absolute position. Viewing the same file (downloading it from the onefinity) in CAMotics displays correctly.

In my case the workaround was to output 3 tool path files.