I’ll start. So far, there is only one known issue with the FW3A: When using the stepped ramp, there is a 1-second delay between turning on at moon and being able to ramp up.
This was fixed only 20 minutes after it was reported, but it wasn’t reported until after the drivers had been produced. So it’s expected to be an issue in the first batch of production lights.
To reproduce this issue:
Configure the light to use the stepped ramp.
Turn the light off.
Hold the button to turn on at the floor level.
Release the button after the floor hint blink, to stay at the floor.
Hold the button again within 1 second to ramp up.
Expected results: Brightness steps up.
Actual results: Brightness stays the same.
After one second has passed, everything works as expected.
This is considered a minor bug, and it has already been fixed upstream, but it’s here to let everyone know about it… and to provide an example of how to write a bug report. It helps to provide a description, detailed steps to reproduce the issue, and a description of both actual and expected results.
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.