It honestly doesn’t even sound like a minor issue, it sounds like a virtual non-issue. Still, sadly, it could have been easily fixed had it been reported, with better communication.
Maukka discovered it and told me about it. I had a fix tested and committed to the repository 20 minutes later. So it was fixed quickly and easily… but not until after the first drivers had been produced. It’s not a big deal though, just a minor inconvenience for one specific UI flow.
It can’t connect the 7135’s big thermal pin directly to the outer ground ring like usual because it has a switch contact ring in the way. Driver layout was a little weird with the switch ring there.
As it says in the layout file, that’s the optic nerve. It can see. I did a video about it two years ago, around the time the FW3A project was starting, and it ended up being included in this driver design. But after looking into it more, it turns out to not be very practical so I didn’t make use of it in the FW3A firmware. It’s still there for anyone who wants to try it though. I’d still like to do more development with it sometime, but it hasn’t been a priority.
I completely missed this programming interface, even though it is rudimentary or not enable right now. This is some next-level gadgetry you guys built!
If there was a single LED optic that would fit, and allow more Aux LED’S that would be perfect for this light, IMO. I’d really love to see a focus on adding more Aux LED’s and different channels for different colors. Then we’d be able to have all kinds of funky modes that my daughter and I could have fun with.
Those lights came out at the same time, not a year apart. This means they are unrelated. No one copied anything. It’s just two somewhat similar lights coming out at about the same time.
I know this has been covered, so if you have any threads that you could suggest, that would be appreciated. Two legs are for power, and the 6 free legs are used for? Is the biggest hurdle in using some of the newer MCU’s just designing and building drivers? I understand that we don’t have firmware for them, but from what I gather it’s fairly easy to port the Attiny85 firmware.
2 legs power
1 leg unuseable reset pin
1 pin voltage divider
1 pin switch
1 pin switch LED
2 pins for FET+AMC
usually
new MCUs like the 1634 got like a dozen pins that can be used when you already have power and reset connected
just so far no BLF firmware runs on them so you can add fancy stuff like color fading aux board or stuff
Thank you Lexel, so if we gave up the ability to reflash (easily) we could gain another pin to use by getting rid of the reset fuse. But, not practical for mass production, and not much memory left on the Attiny85 with Anduril to utilize said pin.
There isn’t currently anywhere to attach an aux LED board in the FW3A, unless it was on all the time with no ability for the user to control the aux LEDs. Here’s the MCU pin layout:
However, if you cut pin 7, it could be used for this purpose. Basically remove the capacitor and resistor it’s attached to, put on a different resistor (optional), and attach it to an aux LED board instead. Flash new firmware with support for aux LEDs, and it should work.