Alternative to ROS2/Lua/etc: Beeptoolkit for FarmBot?

Proposal: Beeptoolkit as an Alternative Software Platform for FarmBot

Dear FarmBot Team,

I’ve been following the discussions in the FarmBot software forum, and I’m impressed by how open the platform is to various software solutions — from Arduino and Farmduino to ROS2, Raspberry Pi, Lua, and others.

I’d like to introduce Beeptoolkit — a low-code IDE Software Logic Controller designed for Windows 10x (LTSC)-based PCs. It was built specifically for designing control logic and enables not only engineers but also a broader developer community to create automation logic without writing traditional code, while still being fully extensible for advanced users.

Given FarmBot’s modular and programmable architecture, Beeptoolkit could serve as an attractive alternative platform — both for optimizing existing workflows and for developing new ones. It may be especially useful in contexts where rapid prototyping, hardware adaptation, or educational applications are important.

I would be glad to discuss the potential for integration or develop a prototype demonstrating how Beeptoolkit can interface with FarmBot hardware. Would you be open to such a conversation?

More information about the platform can be found here: [insert your link]

Looking forward to your feedback.

Best regards,
Alex K.
Beeptec Engineering

@Trigg

Alex,

Thank you for reaching out. We are always looking to expand the FarmBot OpenSource Community and you are welcome to interface the Beeptoolkit for the FarmBot hardware and software.

Having said that, the Farmduino controller stands out as a purpose-engineered open source solution that guarantees FarmBot’s cost effectiveness and long-term reliability. The fully open source Arduino based Farmduino controller are CE and RoHS certified and they have gone through 10+ years of development and more than 5 design iterations. Also, the Farmduino controllers have gone through thousands of hours of real world testing.

It would likely require a significant engineering effort to fully integrate the Beeptoolkit with the FarmBot hardware and software. Also, the Beeptoolkit IDE Software Logic Controller would likely not conform to the governing constitution of the FarmBot Open Source technology. While the Beeptoolkit provides accessibility and flexibility for developers, its core platform is proprietary which would disqualify it from becoming FarmBot technology.

I would encourage you to browse through FarmBot governing documents and core Open Source philosophy.

Marc

Hi Marc,

Thank you for your thoughtful and detailed response - I truly appreciate the openness of the FarmBot community and your encouragement to explore integration opportunities within the framework of your open source principles.

I fully recognize the strength and maturity of the Farmduino controller and understand the importance of long-term reliability, certification, and open development, especially when it comes to ensuring accessibility and trust across your user base.

That said, I’d like to briefly clarify how Beeptoolkit (SLC Beeptoolkit) aligns with some of the principles mentioned.

Although the IDE itself is currently proprietary, it provides an open project-sharing model - users can export their behavioral logic as binary configuration files. These files are portable, editable, and shareable between users, supporting collaboration, import/export, and deployment for both development and end-user applications. The logic files include configuration for interaction with external hardware and USB GPIO communication, allowing the platform to adapt to various hardware use cases - including potentially FarmBot systems.

Moreover, we’re open to building a custom HMI layer aligned with FarmBot’s interface expectations if that’s ever of interest to your team.

SLC Beeptoolkit is designed to run on SBCs or compact PCs, with pre-installed OS and a set of USB GPIO modules. These modules are non-proprietary and based on widely available components from vendors like Amazon, eBay, and AliExpress. We also offer a variant with machine vision capabilities for users interested in integrating computer vision.

If the idea is of interest, I’d be happy to review your hardware documentation and BOM in order to provide a comparative proposal of the system configured with SLC Beeptoolkit components. My goal is not to replace your existing stack, but rather to demonstrate compatibility and explore whether Beeptoolkit could serve specific experimental or educational purposes within your broader ecosystem.

Looking forward to hearing your thoughts.