Building the code from Github

Look here to see if your question has already been answered.
Post Reply
haiqu
Posts: 5
Joined: Sat May 07, 2022 11:13 pm

Building the code from Github

Post by haiqu » Sun May 08, 2022 3:01 pm

Firstly, thanks for adding me to the forum. Secondly, thanks to Doug (and Joe) for an innovative product. If it didn't exist I would have had to invent it, and it's certainly a step or two beyond the Houdaille HECC 80 I cut my teeth on in 1983.

I'm planning to use the controller on a machine I'm currently designing, which is a laser cutter and router combined. I would have preferred an extra axis (I have X, Y, rotation and two heads down, which makes five already, leaving no room for expansion) but with some innovative switching that can be fixed.

I intend to build the controller from the plans. Yes, I could just buy one from the website, but where's the fun in that? Besides, since it is Open Source and since I live a long way from that original source, it makes sense to know as much as possible about the internals of the controller I intend to use, and what better way than to build it from raw materials.

My issue is the Github files, which don't seem to be current and/or complete. Yesterday I installed Debian 9.6 under Virtualbox and attempted to build it, but found that neither the firmware nor the hardware would build satisfactorily. The box files are easy enough, I managed to display those with Inkscape in Windows 7.

It appears that this is in need of a review for completeness and that dependencies need to be documented better. An example was that at one stage I was notified of the need for some files related to KDE. Since I installed the default, which is Gnome, they were missing. But worse, the builds failed with errors that require an intimate knowledge of the code to correctly rectify.

I know how such projects can evolve over the years, leaving unfinished parts that go uninspected, since I contributed Open Source software for years. But in the spirit of co-operation I plead that they be looked over; companies and people come and go, and this product deserves to remain regardless of that. I hope to be the guinea pig (or perhaps Crash Test Dummy :-) ) that proves this thing can be independently built.
The old guy in the shed.

User avatar
Joe
Site Admin
Posts: 8
Joined: Fri Feb 02, 2018 2:00 pm
Location: Petaluma, CA
Contact:

Re: Building the code from Github

Post by Joe » Mon May 09, 2022 4:30 am

Hello. Thanks for your interest in the Buildbotics controller. All the needed files are on GitHub. Nothing is left out intentionally. However, it would take a lot more time and effort to document and simplify the build process. That has not been a high priority for us. If you want to document the process and contribute the documentation, that would be most welcome. I can help but I have limited time available for this.

Also, please note that the CERN license we use allows others to build and sell our controller but only if the final product is also Open-Source under the same license. That means if you build and sell a CNC the entire CNC must be Open-Source under the same license unless you negotiate a different licensing agreement with Buildbotics. You can build anything for your own personal use but if you publish plans or sell a product based on our work then the license comes in to effect. So basically you either pay by sharing your work or pay by buying an alternative license from us.

haiqu
Posts: 5
Joined: Sat May 07, 2022 11:13 pm

Re: Building the code from Github

Post by haiqu » Mon May 09, 2022 7:08 am

I guessed you missed the part where I stated that I'm an experienced contributor to open source projects.

I am not asking you to document it, I'm asking you to fix the broken builds. I'd post the error messages here but apparently you'd just misinterpret that as criticism.

In any case there's no real hurry, since parts are hard to come by right now. Maybe you'll find the time when they run out. :-)
The old guy in the shed.

haiqu
Posts: 5
Joined: Sat May 07, 2022 11:13 pm

Re: Building the code from Github

Post by haiqu » Sun May 22, 2022 9:53 pm

My PCBs and solder stencil arrived today. Still waiting for a heap of parts though so won't be picking and placing just yet. The component shortage is proving to be a bit of a bear, and some substitutions had to be made.

I had originally intended to use this board on a laser cutting machine of my own design, but a used Chinese 1325 laser bed of 2010 vintage has shown up and if I can find someone willing to move it from Sydney 500km (310 miles) away to my place this board will make an ideal replacement for its old controller.

BBCTRL.png
Last edited by haiqu on Sun May 22, 2022 10:39 pm, edited 3 times in total.
The old guy in the shed.

haiqu
Posts: 5
Joined: Sat May 07, 2022 11:13 pm

Re: Building the code from Github

Post by haiqu » Sun May 22, 2022 10:29 pm

And here's a happy snap of the BBCTRL software running remotely on my PC, complete with webcam output. I used the same camera as BuildBotics sell on their website, 1080p resolution. Nice camera!

CAMERA.png
The old guy in the shed.

haiqu
Posts: 5
Joined: Sat May 07, 2022 11:13 pm

Re: Building the code from Github

Post by haiqu » Sun May 22, 2022 10:35 pm

In compliance with Open Source rules, I have forked the BuildBotics repositories and any changes that occur will be posted at https://github.com/haiqu?tab=repositories

So far there have been none of any consequence.
The old guy in the shed.

Post Reply