badobsessionmotorsport
patreon
Project Binky - Episode 41
🕑 Added 2025-07-30 21:55:21 +0000 UTCIn the penultimate build episode of Project Binky, we didn't get as far as we'd hoped. This is not unusual for us as you know, but this one was lined up and ready to go with just a few bits to finish off earlier in the week except for a nasty hand injury sustained by Nik that slowed us down some. Super glue was deployed to keep us going; after all, that's what it was designed to do right?
Anyway, there's no more noodling needed, most things are working as we want and there's just a few things to cross off the list before we can actually get the thing off the stands and out in the wild for the first time.
Subsequent videos will be about the running in period, the get-to-know-you drives, the rolling road tuning session(s) and then the performance drives, along with any snagging and troubleshooting we'll inevitably need to do. Don't worry, there's plenty more to come.
Thanks as always for your incredible patience, it almost feels like we're nearly done now.
Hope you enjoy it!
Cheers,
Nik and Richard.
Comments
Kjartan Bartley Hallingstad
Making your own dash took this build to another level! Watching all of these latest episodes I have to juggle the feeling of how insane and unusual it is, with how freakin amazing it is and the awesome craftsmanship you are putting into it! Keep up the excellent work guys. So fun to watch! :D
Erik Ekedahl
You should also have backups for all your 3d prints as well, there would probably be enough space on those USB drives. Not having that much experience with 3D printing I don't know what additional things to backup beyond the 3D project files themselves.
Erik Ekedahl
From an experienced software developer, you need to back up everything you did. My suggestion: learn to use git (useful anyways for software development) and backup your code to github (either private or public repo depending on your preference). If you don't want to learn GIT and just have your copy offline, get a couple USB drives from different venders and put copies on each. In addition, you need to backup your environment. the IDE you use to compile the code plus any libraries you might have used, all the install files you used of the versions you used. Final step, document everything, how you installed, order installed, how you connected to the devices, compile settings, IDE settings, etc. In your code you also need to document. Don't document what you are doing but why. I can read the code and see you are incrementing x until it reaches the value of y before doing something, but I don't know why. Comments are free, don't cost you anything in your final code, but done right it helps you a ton when it comes to understanding what is going on. Why go through this? In a year or two you will either find something you need to update/change/fix, or a device might fail and you need to replace it. When that happens you will sit down and realize you forgot a ton of details on how and why you did things. Why copy the IDE and libraries? Things change, you might have a new computer, and while you did your work on v1.2.3 in a year or two it might be v3.2.4 and oh, by the way, there were several breaking changes between then and now and your code no longer compiles. For libraries it might be worse, the library might have been 'obsoleted' or abandoned and is no longer available, or updated and the API has changed.
Adam Stadnick
SO CLOSE!!! Y'all are giving me confidence on my own crazy interior ideas. I have a concept for my project (still VERY far in the future) that would require making custom plastic rocker switch covers that look OEM. I think it's doable. Onward and upward, gents!
