I’ll get straight to the point here: There’s no silver lining to this post. There’s a lot of bad, and a lot of scrambling to make the best of a very bad situation.
To start it all off: The screens on the V3 badges did not work. More accurately, they do work but they have a different driver chip in them. It is a problem that is fixable via code, but I am not a programmer in anything more than the most basic things. I can take existing libraries and combine them, but interfacing with hardware on the level of a display chip is well beyond me. For completeness’ sake, the driver is an HX8347D – In SPI mode/pinout. I have had a hard time finding any libraries for the HX8347D in such a configuration, and then there’s another hurdle – None of the libraries I’ve found work on the ESP8266. Fixing this issue in, at this point, less than three days is just not going to happen.
In addition to that, the V3s have a handful of other problems. There’s something screwy between the ATTiny and the ESP8266, which is causing the ESP8266 to not boot properly. This IS a code issue, as putting the ATTiny into a bare code state with only specific pins set does allow the ESP to boot up. The CP2102 also doesn’t connect to the ESP module – I’m not sure what the issue is as I haven’t poked into it at all, but the module connects to USB, but it doesn’t connect to the ESP. And the final issue is that the adhesive used for the battery packs is just not good enough. The pressure from the wires is enough to eventually separate the battery pack from the board.
On the plus side: The voltage regulators work – Both of them. I had also included a method for bypassing the CP2102 when prototyping, so that works to upload code. It’s annoying because an external adapter is needed, but it works. The ATTiny also works largely as intended from what I can tell (Although I haven’t tested it much).
So where do I go from here, with a pile of largely unusable DigiBadges?
I’ll likely simply do nothing with the pile. Replacing the screens is costly and time-consuming, resources better spent making sure this issue is resolved for future versions. I may put them up on the shop with a notification about the issues. Doing this will take some time, however, so I’ll need something in the meantime.
That something is going to be a modified V2 badge. It won’t decode JPEGs, but it’s a known device. It works. I’ll have to do some modifications for components that the PCB house can source and place, but that should be fairly simple. It should also be a bit cheaper than the V3 design, since it has much fewer components. Depending on cost, I may keep it around as a “Light” version of the badge.
Additionally, because of the no-longer-linear progression of badges, I’m not going to call them the V2+, V3 New, or whatever. I’m not entirely sure what I WILL call them at this point, but trying to keep generation numbers would just become a headache.
As far as BronyCon goes, I’ll still be there, at booth #33 in the Artist’s Alley. I’ll be showing off the V3 badge I’ve made work by swapping the screen on, and will be more than happy to answer any questions you may have.