So, I’ve had some ideas for how to improve the DigiBadge Mini, but without a complete re-design. So, where the DigiBadge Mini was a re-named revision of the DigiBadge V2 (Hence the R1), the DigiBadge Mini R2 is a revision of the R1. There’s a bunch of changes, which I’ll go over below. Warning! This will get quite nerdy and in-depth! If you’re looking for the new shop information, you can just skip to the end.
It’s a new month today, and while my ears and sinuses may still be infected after my trip to Texas, I can still type (As an aside: Nose sprays suck. Leave an AWFUL taste in the back of your throat. Will be happy to be full and alive again). So, you get this “Beginning of the month and what I plan to do” thing.
It’s something I just came up with, but whatever.
The general overview for the month is pretty simple:
Get the Web Store 100% up and running
Send DigiBadge Minis back for fixing.
Post bounties (See below for details)
That’s it. Three goals. Let’s go over them so you know what I’m talking about.
For the Web Store, I basically need to take and update pictures of things. There are a few things I need to acquire beforehand, so the goal is to have everything working between mid-month andend-of-month. To be clear, I am making zero guarantees about stock – This is just getting everything functional so that when I have stock, it can be sold.
Once the Web Store is up and running, expect New Product posts to start popping up. I have a number of things in the works, but I will be rationing them out so I can spend time and make sure they’re working properly. My goal is to have 1-2 New Products Monthly so it will be a mid-month post of new things.
Fixing the DigiBadge Minis
So, for those of you that haven’t seen: The DigiBadge Minis are borked. In short, they had an ATMega328 put on them, when they should have had an ATMega328P. Not MUCH of a difference, except it makes them not work. The Non-P 328 has issues with not having a crystal – Many things I read said it simply wouldn’t work. Guess what? The DigiBadge Mini doesn’t have a crystal!
But wait! There’s more!
The biggest issue with them is the methodology which people used to set the fuses on them in the first place. They used “High-Voltage” Programmers which ran 12V through the chips. This is high enough that it forces the fuses to set how they want them to set, although there were still the mentioned issues with the crystals. This is great! Except it would fry the SPI flash that’s on the DigiBadge Minis.
So how am I fixing them? In short: I’m not! I’m going to send them back to the PCB house in China. There, they’ll pull the 328s off, put the 328Ps on, and also add on the LCD Screens. I had sourced those screens separately, as they couldn’t find them. Also, as I am sourcing the 328Ps, I’ll be able to put the bootloader on before sending them out. Programming 250 of them will be super tedious, but I’ll be able to weed out any bad ones while I’m at it.
So, you know what a bounty is, right? Someone asks you to do the thing, you do the thing, and they pay you for doing the thing. In this reference, the “Thing” is generally going to be coding. Because I, in general, don’t like it. I do have some stipulations on things I will bounty, and I will not take requests for bounties. I’m currently debating on allowing others to put up bounties on the bounty board, and how I would handle that, but at the moment it’s just Phoenixborn bounties.
How will bounties work? Well, here’s a handy dandy list:
Bounties will be posted on the Bounties Board (This page!), and mentioned in relevant blog posts.
Bounties will be for open-source only. They will be usable by everyone, for free, and while they may be inspired by specific hardware or software, they shouldn’t be limited to only that hardware.
Bounties will not be re-sold. IE, I won’t take the Bounty Hunter’s work, repackage it, and sell it as a Phoenixborn product. It may be used or modified to be used in a Phoenixborn product.
Bounties will not be limited to Phoenixborn code. I might put a bounty on an issue that’s open on an Adafruit code base, or even someone’s personal code base.
Bounties must be claimed. While I don’t expect a giant number of bounties (That’d be a lot of money!), I still won’t be keeping a super-active eye on them.
Bounties can only be claimed upon completion and verifying that all goals are met.
Bounties have specific requirements to be claimed. These will, of course, vary between bounties, and some may be optional (Perhaps for a higher payout). These requirements will be checked when a bounty is claimed
Bounty requirements can be changed at any time, including after a claim has been submitted.
Bounty claims can be rejected even if they technically fit all requirements. If the requirement is to display a BMP in 1 second on a 320×240 screen, and someone makes code that will work within the time frame on one image but on many others it takes 2 or 3 second or whatever, then it will be rejected. The spirit of the bounty matters.
No, we’re harder to kill than that. I’ve just been busy and haven’t updated the website in far too long. I’ll give you the short version, and then the long version. So, here we go with the short version.
I’ve largely been waiting on the Minis to assemble and ship, and they’re mostly there. I have slacked a little on the code end of things, so I need to get by butt in gear and write working code for the Minis. I did sort of break my prototype by frying the SPI flash, but I’ll be able to do everything else before the other Minis get here. Outside of that, I’ve begun fiddling with Adafruit’s Circuit Python and M0 boards. It’s definitely made me want to design the larger DigiBadge around an M0 microcontroller. While CircuitPython doesn’t do graphics well yet, the M0 runs Arduino just fine. And CP will get there eventually, and putting it on boards will only make it faster. I’m also working on some prototype Feather Wings – A Hall Effect Sensor Array and a 10440 LiPo Battery. Beyond that, I’m going to Nightmare Nights next week, and I’ll have STUFF.
Now, for the long versions.
The DigiBadge Minis are in production and should be done soon! Unless Bad Things happen, I’ll have them before the convention, although I’ll have to spend a decent amount of time soldering the screens on, programming them, and packaging them. As mentioned above, I still have to finish the programming for them. That’ll take some time, but I can start kicking on that before they arrive. I also have some pictures of them!
Now, for CircuitPython and Adafruit. CircuitPython is Adafruit’s adaptation of MicroPython, itself a rebuilding of Python that works on microcontrollers powerful enough. MicroPython runs on a few MCs, but Adafruit has largely focused on the SAMD21 and ESP8266, as their boards use those two chips. CircuitPython is great, as it allows the microcontroller – plus the SPI Flash if it’s an Express board – appear as a thumb drive on the computer. You simply put the code files on the board and it executes them. It’s super great, especially because it allows you to pull your code off on any device, edit it, and run it immediately. As Python was my first programming language, I’m quite biased to it, and this mixes my love of Python with my love of microcontrollers. I’m likely to rebuild the larger DigiBadge as a M0 device and make it work with CircuitPython, even though CircuitPython doesn’t have a large amount of functionality as far as screens go. But one of the best ways to get things like that going is to put them out there, so that will definitely help.
Now, for my own projects! There’s a Hall Effect Array that I made, and then realized it was almost exactly the size of a Feather, so I turned it into a wing. I’m still waiting on some parts, but I already had the previous non-Wing version working. I took a short terrible phone video of the array in action, which you can see on the twitter:
Terrible video. One hand on phone, one with magnet… I'll need a better setup. It's a Hall Effect array PCB, piped to a TFT. pic.twitter.com/ALGWVl4aMy
I’ve already re-designed it as a feather, which you can see here:
I haven’t yet assembled it though. That comes later. But what’s the other green Feather Wing? Well, it’s a super simple one that I still managed to mess up: It’s a wing designed to fit a 10440 LiPo Battery. It’s enough to power a Feather-sized project and fit compactly inside it. It’ll even stack mostly nicely, but I’d recommend long male headers for the board above it. How did I screw it up, though? Simple: I forgot a power switch. Oops. Anyway, have a video and some pictures:
What else was there? Oh, right! Nightmare Nights! And I’ll have things! What things? Well, first and foremost, unless Bad Things happen, I’ll have the DigiBadge Minis. Many minis! I won’t be bringing my whole stock – I only have packaging for 100 of them. It was originally for the V3, so the boxes may be a little large, but it should work fine.
Additionally, I’ll have a bunch of Arduineigh boards, a handful of component kits for the Arduineigh boards, and a bunch of prints by Sophie Scruggs! I will also have art cards with art by Sophie and by LeekFish.
If you’re wondering where I’ll be, it’s super easy to find me. Walk in the door, take a few steps and turn right. I’ll be there, right next to the My Dreamy Star booth. Give them some love, because they’re going to be dealing with my terrible puns the whole convention.
After the convention, I’ll be polishing up the store with more pictures, an actual front page, and the ability to, well, buy things. Important for a store.
And speaking of buying things, I’m going to end with a shoutout to Sophie’s Coloring Book and Art Showcase. You can buy it on her website: US Shipping International Shipping