So I've had a couple weeks here without much of a progress update. A lot of work has gone on. So here's a quick update before the holiday. First some photos. The first one is of the original prototype 3D printed out with some Pi in it.

This is my blog about software development, mountain unicycling, Photography, and stuff I find interesting.
So I've had a couple weeks here without much of a progress update. A lot of work has gone on. So here's a quick update before the holiday. First some photos. The first one is of the original prototype 3D printed out with some Pi in it.
Posted by
Chris Bensen
at
7:00 AM
0
comments
Labels: Raspberry Pi
I spent most of today fighting with Fusion 360 so I don't have much progress to report besides a serious complaint about Fusion 360. A new updated was released. If I didn't upgrade I couldn't save. If I upgraded I lost my changes. I had no choice but to upgrade, loose my changes and redo them. Then when I loaded up my models there were errors with unresolved imported components. The error states that if I save my model in this state I will loose my model. Personally I find this unacceptable and while I like Fusion 360, I like the disruption to the CAD world, many of the features, the price is reasonable and the fact that it runs on Mac and Windows, I also find it extremely buggy and a toy. I may be switching back to SolidWorks. Hopefully I get all of this resolved in the next few days and can report on the progress.
Update: After restarting Fusion 360 five times, and reloading the model after closing it with the error saying it will be destroyed, I finally got all the linked models and everything to load. So it was just a lot of ignoring errors and closing and reopening things and much ado about nothing, but extremely worrisome that just an update being pushed could cause such concern.
Posted by
Chris Bensen
at
7:00 AM
0
comments
Labels: Raspberry Pi
Last week I posted about the very very large Raspberry Pi cluster that I'm building for Code One. Read that post here.
I realized after that post went live that I didn't give any backstory as to what we are actually building. When building something like this it's easy to document the entire process, it just takes 2-3 times as long to build. I figured I'd document the process in a fast and loose to blogs, YouTube and Twitter. So, before we go any further with the status of current progress let's backup.
Last year Stephen Chin and Gerald Venzl came to me with an idea. The conversation went something like this:
Stephen: "Gerald has an idea"
Gerald: "Let's build a HUGE biggest Raspberry Pi cluster for 2019 CodeOne. Like 1000 Raspberry Pis. The developers will love it. We will call it OSCAR!"
Me: "1000 is a lot, but 1024 is a better number"
Gerald, Stephen: "😃"
Back in the lab a few months later Jasper Potts and I did some math about how to pull off a cluster like this and we produced this rendering.
Posted by
Chris Bensen
at
7:00 AM
0
comments
Labels: Raspberry Pi
I am building a very large Raspberry Pi Cluster and I'm going to document the process here. My goal is to post once a week until it's complete and shows up at Oracle Code One in San Francisco September 2019. Thus far an unimaginable amount of work has been put into this project to determine if it's even viable. We think it's viable so I'm going to start talking about it. There may be some mistakes. No, there will be some mistakes. Hopefully I won't make too many of them.
For the first taste, here is a rendering of a 2U rack that will hold 20 Raspberry Pi Model 3B+. I've printed out about 50 versions of this and this packs the most in while still allowing heat dissipation and still being serviceable in a standard server rack.
Posted by
Chris Bensen
at
7:00 AM
0
comments
Labels: Raspberry Pi
Why this isn't the default I have absolutely no idea, but the first thing you should do when learning Fusion 360 is to turn on this option:
How to Turn on Automatic Save in Fusion 360
Posted by
Chris Bensen
at
7:00 AM
0
comments
It has been nearly a year since I last posted to this blog. It isn't that I haven't wanted to or that I've been sitting around watching TV. I've been busy. Real busy. I now work for the Oracle Developer Marketing team as a Groundbreaker building experiences for developers. It's an amazing opportunity that I had to jump into 1000%. Here's one experience that I built last year and blogged about but not on this blog. Go check it out https://blogs.oracle.com/developers/building-the-oracle-code-one-2018-escape-rooms. Not only do I get to draw on my 20+ years of Software Engineering/Architecture experience, I get to use everything I've ever learned about being an inventor, tinkerer professional photographer, maker, prop builder, and videographer. I use 3D printers, CNC, camera's, Arduino, Raspberry Pis and a whole lot more on a daily basis. So follow me on Twitter https://twitter.com/chrisbensen and YouTube https://www.youtube.com/channel/UCLf9yhC2uo7TxNIwiJqIDcw as a lot more content should be coming! Like the world's largest Raspberry Pi cluster.
Posted by
Chris Bensen
at
7:00 AM
1 comments
Posted by
Chris Bensen
at
7:00 AM
1 comments
AWS Lambda is I think one of the best additions to AWS, however it does have some issues becuase the architecture has changed over the years and one such problem the default VPC that it runs in. Default configuration runs great, but if you want better security, then not so much. But I digress. One of the most compelling features of Lambda is that you don't have to manager the VM or Docker Container. However because of that you might want to break up the responsibility between multiple Lambda functions, and in this case one Lambda will most certainly want to call another Lambda. So here's how you do that:
const aws = require('aws-sdk');
const lambda = new aws.Lambda({region: 'us-west-1'});
lambda.invoke({
FunctionName: 'LambdaFunctionName',
Payload: JSON.stringify(event, null, 2)
},
function(error, data) {
if (error) {
context.done('error', error);
}
if (data.Payload){
context.succeed(data.Payload)
}
});
Note: I really appreciate Lambda. But to be honest they are difficult to use. There is a time and a place to use them and it should be in every AWS developer's bag of tricks. The real trick I alluded to above is the VPC, but that's for a proper DevOps person to discuss the nuances of that. Also know that while in small uses Lambda is cost effective there is a cross over point where Lambda becomes more expensive than EC2 or Elastic Container Services (Docker).
Posted by
Chris Bensen
at
7:00 AM
1 comments
There are two types of variables in a Dockerfile, ENVs and ARGs. YOu define them in the Dockerfile like this:
ARG some_argument
This requires that you run:
$docker build --build-arg some_argument=something
Then there's ones with a default value.
ARG some_argument="default value"
You don't have to specify it during the docker build, but you can if you want.
ENV some_value=something
ENV some_other_value=${some_argument}
You can override these when you do docker run:
$docker run -e "some_value=others_stuff" ...
Posted by
Chris Bensen
at
7:00 AM
0
comments
Posted by
Chris Bensen
at
7:00 AM
2
comments
Here is a Death Star Christmas ornament build with STl files provided on thingiverse here. A little bit of 3D printing, remixing an existing item on thingiverse and some electronics. Enjoy!
vlog 02
Posted by
Chris Bensen
at
7:00 AM
1 comments