In many parts of the world, living in a trailer has gained a social stigma. We’re talking about a rectangular building placed on three wheels and towed to your preferred plot of land. It’s going to take a lot to break that social stigma, but this is a pretty sweet attempt.
PassivDom is an off-grid home. It sidesteps the electrical grid as well as water and sewer service. It’s marketed as utilizing revolutionary breakthrough in wall insulation which they claim makes it very easy to heat and cool. In addition to this self-sustaining angle, it taps into the tiny home movement with a footprint of just 36 m2 (4 m by 9 m; about 118 390 ft2 or 13′ by 30′).
For this to make sense you really need to get the “Autonomous” model, the only one that is designed for “off-grid” living and comes with solar panels and battery storage plus water storage and purification. That’ll set you back 59,900 € (about $63,461 USD) but hey, it does come with “high quality minimalistic furniture” which the best way we can think of to serve Ikea nesting instinct without saying the brand name. Yep, this ticks all the “marketing to millennials” boxes. We’re kind of surprised it’s not doing crowdfunding.
So where’s the hack? Obviously this is a hard sell at 1,664 €/m2 ($538 $163/ft2). A project of this size and scope is well within the purview of a single, motivated hacker, and arguably a weekend project for a well-skilled team from a hackerspace. Tiny Houses started as a build-it yourself so that’s already solved. We’ve seen what it takes for hackers to add solar to their RVs, and experiments in home-built power walls. Water storage and purification is already solved and quite affordable at the home store.
Python is the Arduino of software projects. It has a critical mass of libraries for anything from facial recognition and neural networks to robotics and remote sensing. And just like Arduino, I have yet to find the killer IDE for Python. Perhaps I just haven’t tried the right one yet, but it could be that I’m just doing Python wrong.
For Years I’ve Been IDLE
I’m a Linux-only type of a guy so using IDLE for Python is a natural fit. It’s in the repositories for super quick and easy install and there’s basically zero configuration to be done. Generally speaking my preferred development environment is text editor and command line compiler. IDLE is just one step above that. You get a separate window for the shell and each Python file you’re working on. Have IDLE run your code and it saves the file, then launches it in the shell window.
For me, there are two important features of IDLE’s shell. The first is that it keeps an interactive session open after you run your Python code. This means that any globals that your script uses are still available, and that you can experiment with your code by calling functions (and classes, etc) in real time. The second desirable feature is that while using this interactive shell, IDLE supports code completion and docstring support (it gives you hints for what parameters a function accepts/requires).
But simplicity has a tough time scaling. I’m working on larger and larger projects spread over many files and the individual nature of IDLE editor windows and lack of robust navigation has me looking to move forward.
I’ve tried perhaps a half-dozen different Python IDEs now, spending the most time on two of them: Geany and Atom. Both are easy to install on Linux and provide the more advanced features I want for larger projects: better navigation, cross-file code completion (and warnings), variable type and scope indication.
The look of Geany brings to mind an “IDE 1.0” layout style and theme. It’s the familiar three-pane layout that places symbols to the left, code to the right, and status along the bottom. When you run your program it launches in an interactive terminal, which I like, but you lose all IDE features at this point, which I despise. There is no code completion, and no syntax highlighting.
I have been using Atom much more than Geany and have grown to like it enough to stick with it for now. I’d call Atom the “IDE 2.0” layout. It launches with a dark theme and everything is a tab.
Atom depends heavily on packages (plugins that anyone may write). The package management is good, and the packages I’ve tried have been superb. I’m using autocomplete-python and tabs-to-spaces, but again I come up short when it comes to running Python files. I’ve tried platformio-ide-terminal, script, and runner plugins. The first brings up a terminal as a bottom pane but doesn’t automatically run the file in that terminal. Script also uses a bottom pane but I can’t get it to run interactively. I’m currently using runner which has an okay display but is not interactive. I’ve resorted to using a “fake” python file in my projects as a workaround for commands and tests I would normally run in the interactive shell.
Tell Us How You Python
It’s entirely possible I’ve just been using Python wrong all these years and that tinkering with your code in an interactive shell is a poor choose of development processes.
What do you prefer for your Python development? Does an interactive shell matter to you? Did you start with IDLE and move to a more mature IDE. Which IDE did you end up with and what kind of compromises did you make during that change. Let us know in the comments below.
Venture away from your workbench and see what others have been building this year. It’s time for Hackaday World Create Day when hackers all over the world get together to work on projects.
On April 22nd, join the creative minds in your area for a few hours of build time. It’s an opportunity to inspire and be inspired by others. There’s no better way to make those leaps forward on a project than to share your work with others. This pollination of ideas is what sparks creativity, and it’s a great excuse to meet new people.
When the Hackaday community gets together it’s always a fun time. Each meetup on April 22nd will be unique. These are organized locally and given life by those who show up. Bring an open mind and something you’re excited about and you’ll be right at home.
For instance, if I were Brian Benchoff I might bring along my 3D printed WiFi antenna and a few different WiFi devices to see if anyone wanted to do some distance measurements and signal strength characterization. I myself have been working on an art project that uses computer vision and replacement display for my exercise machine so I’ll bring one of those. After a few hours of hacking, it’s customary to go around the room and have people give a very brief explanation of their work.
World Create Day is the perfect place to put together you Hackaday Prize Team. As the ideas fly, keep in mind the power of one idea to change the world. Consider picking a challenge, brainstorming an idea, and entering it in the Hackaday Prize.
Pics or It Didn’t Happen
Don’t let the great ideas live for only one day. Make sure you tell the story of your World Create Day. Post your pictures and descriptions on social media with hashtag #WorldCreateDay during the event. Pictures, project links, and a brief summary should be added on your meetup’s Hackaday.io event page. We want to cover as many of these as possible on Hackaday, so don’t be bashful about telling everyone what people at your meetup were working on — finished project or pencil drawing, we want to hear it!
It’s official, World Create Day is on April 22nd. Get together with hackers in your area and create something! This is best way to meet all the Hackaday readers in your area, and a great excuse to carve out a few hours of your busy life to have fun working on a project.
The Hackaday community around the world will meetup and spend time building together on Saturday, April 22nd. If you’re like us you have a long list of projects you want to do ‘some day’, this is the day. Pack up your current build (or grab gear to start a new one), get together with some old and new friends, and hack on your projects with each other.
It’s traditional to block out a bit of time at the end for lightning talks to show off the builds each of you has been working on. Don’t forget to take pictures and post the story of your World Create Day meetup. We enjoyed getting a great look at many of last year’s meetups this way and want to expand the builds we feature on the front page this year.
This is the second year of World Create Day. Last year we saw meetups in 64 cities. Many of those will happen again this year, but we also need you to organize an event in your area. We’ll help you get things set up and put your event up on the big map so others in your area will plan to join in. Do it now, if we get your shipping info early we’ll send you stickers and other swag to hand out at your gathering.
Build Something that Matters
The core of World Create Day is to stop making excuses and just build something. Since you’re already getting together with other people consider forming a team to enter the 2017 Hackaday Prize. Currently we’re in the idea phase: Design Your Concept means tackling a problem and planning a build to solve it. When you get a bunch of creative people together in one place, great ideas begin to flow. Seize the moment by turning that creativity into an entry for the Hackaday Prize and see where it takes you!
Ask any security professional and they’ll tell you, when an attacker has hardware access it’s game over. You would think this easily applies to arcade games too — the very nature of placing the hardware in the wild means you’ve let all your secrets out. Capcom is the exception to this scenario. They developed their arcade boards to die with their secrets through a “suicide” system. All these decades later we’re beginning to get a clear look at the custom silicon that went into Capcom’s coin-op security.
Alas, this is a “part 1” article and like petulant children, we want all of our presents right now! But have patience, [Eduardo Cruz] over at ArcadeHacker is the storyteller you want to listen to on this topic. He is part of the team that figured out how to “de-suicide” the CP2 protections on old arcade games. We learned of that process last September when the guide was put out. [Eduardo] is now going through all the amazing things they learned while figuring out that process.
These machines — which had numerous titles like Super Street Fighter II and Marvel vs. Capcom — used battery-backed ram to store an encryption key. If someone tampered with the system the key would be lost and the code stored within undecipherable thanks to “two four-round Feistel ciphers with a 64-bit key”. The other scenario is that battery’s shelf life simply expires and the code is also lost. This was the real motivation behind the desuicide project.
An overview of the hardware shows that Capcom employed at least 11 types of custom silicon. As the board revisions became more eloquent, the number of chips dropped, but they continued to employ the trick of supplying each with battery power, hiding the actual location of the encryption key, and even the 68000 processor core itself. There is a 6-pin header that also suicides the boards; this has been a head-scratcher for those doing the reverse engineering. We assume it’s for an optional case-switch, a digital way to ensure you void the warranty for looking under the hood.
Thanks for walking us through this hardware [Eduardo], we can’t wait for the next installment in the series!
Every week, we find a few interesting people making the things that make the things that make all the things, sit them down in front of a computer, and get them to spill the beans on how modern manufacturing and technology actually happens. This is the Hack Chat, and it’s happening this Friday, March 31, at noon PDT (20:00 UTC).
Jørgen’s company has developed a line of multi level Class D amplifiers that focus on power reduction to save battery life in mobile application without losing audio quality.
There are a lot of tricks to bring down power consumption, some on core technologies on transistor switching, others based on input level where modulation type and frequency is dynamically changed to fit everything from background audio level to party mode.
Here’s How To Take Part:
Our Hack Chats are live community events on the Hackaday.io Hack Chat group messaging.
Log into Hackaday.io, visit that page, and look for the ‘Join this Project’ Button. Once you’re part of the project, the button will change to ‘Team Messaging’, which takes you directly to the Hack Chat.
You don’t have to wait until Friday; join whenever you want and you can see what the community is talking about.
Upcoming Hack Chats
We’ve got a lot on the table when it comes to our Hack Chats. On April 7th, our host will be [Samy Kamkar], hacker extraordinaire, to talk reverse engineering.
We love taking on new and awesome builds, but finding that second part (the “awesome”) of each project is usually the challenge. Looks like [Nathan Seidle] is making awesome the focus of the R&D push he’s driving at Sparkfun. They just put up this safe cracking project which includes a little gamification.
The origin story of the safe itself is excellent. [Nate’s] wife picked it up on Craig’s List cheap since the previous owner had forgotten the combination. We’ve seen enough reddit/imgur threads to not care at all what’s inside of it, but we’re all about cracking the code.
The SparkX (the new rapid prototyping endeavor at Sparkfun) approach was to design an Arduino safe cracking shield. It has a motor driver for spinning the dial and can drive a servo that pulls the lever to open the door. There is a piezo buzzer to indicate success, and the board as a display header labeled but not in use, presumably to show the combination currently under test. We say “presumably” because they’re not publishing all the details until after it’s cracked, a process that will be live streamed starting Wednesday. This will keep us guessing on the use of that INA169 current sensor that plugs into the safecracking shield. There is what appears to be a reflectance sensor above the dial to keep precise track of the spinning dial.
Electrically this is what we’d expect, but mechanically we’re in love with the build. The dial and lever both have 3D printed adapters to interface with the rest of the system. The overall framework is built out of aluminum channel which is affixed to the safe with rare earth magnets — a very slick application of this gear.
The gamification of the project has to do with a pair of $100 giveaways they’re doing for the closest guess on how long it’ll take to crack (we hope it’s a fairly fast cracker) and what the actual combination may be. For now, we want to hear from you on two things. First, what is the role of that current sensor in the circuit? Second, is there a good trick for optimizing a brute force approach like this? We’ve seen mechanical peculiarities of Master locks exploited for fast cracking. But for this, we’re more interested in hearing any mathematical tricks to test likely combinations first. Sound off in the comments below