So, in a not so tiny nutshell…I haven’t played with virtual circuitry in 5ever and wanted to know if there were some MultiSim like program where I could virtually recreate the Anduril capable boards to test my Anduril mods BEFORE flashing my driver…I have a tendency to be heavy handed in everything I do, and would prefer to brick an imaginary d3aa rather than my real one…
At one point, I tried to get it running in a simulator, but I didn’t have any luck with it. So… all of my testing has been done on real hardware.
The risk of bricking is extremely low as long as you don’t mess with very specific MCU settings or fuse values. If you leave the fuses alone and stick to UI level features or hardware drivers, you should be fine. The tricky parts are mostly related to adding support for new MCUs.
That’s encouraging to hear. However, I am a defensive programmer’s worst nightmare
You can program all the failsafes you want into a piece of hardware, but my dumbass would step on the cord lol
Also, wanted to pick your brain as to a different method of dissociating the backlit button from the AUX…I still need to learn the syntax and functions, but do you have any insight as to how difficult it would be to accomplish the following:
To set the Buttonlight to be programmed with 6H. I want to keep the 6c functionality of the 6c tactical and toggling stepped to ramp functions.
I.e.
Delete all buttonlight function from aux modes to unbind the buttonlight from aux, then program in a distinct buttonlight function using 6H:
From respective ON/OFF/LOCKOUT, 6H, 3 second shimmer timer for input, ignore first release
0c=off
1c=high
2c=low
3c=blinky
OR
From respective ON/OFF/LOCKOUT, 6H, release at #blink, 2second shimmer timer per blink
1blink = off
2blink = high
3blink = low
4blink = blinky
Will probably need the 6h config to bond with its respective on/off state programming for it to work…
Though I could probably copypaste alot of the existing blinky functions and release-on-blink functions then cannibalize them to apply only to the button light…sloppy and inelegant, but would that be feasible? This seems like the “release on blink” method might be easier, as it would essentially be a copy paste, then referenced in without having to dupe the entire code…
(It’ll be extra steps if you want the button to match the aux again, or just reflash to default.)