Normal bad. FR4 PCB material is fiberglass with a flame retardent mixed into the resin. Typically it is a bromine-based flame retardant, which has a low toxicity.
A bunch more info here (page 8 in particular):
I would imaine if someone dug around enough, considering PCB trimming is a fairly common practice, that there are EPA or OSHA documents on permissible exposure to FR4.
Disclaimer: I have literally no idea what I’m doing. Use at your own risk. These files might make your flashlight explode or something.
I doubt anyone but me will ever use these, but I spent a little more time trying to update these configs for use with the current Anduril 2 codebase: * They now more resemble other, newer configs (in terms of certain functions/variable definitions). * They now compile without warnings (related to the above). * Party Strobe works again (I hadn’t noticed, but it wasn’t working when using the configs in my prior post).
The only issue I’ve noticed is that SMOOTH_STEPS seems kinda weird. Probably related to OPAMP_ON_DELAY/noflash? I don’t care because I don’t use SMOOTH_STEPS.
Edit: Refer to the below post for further updated configuration files.
Probably MCU configured in hwdef.h to run slower. Set it to original CLKCTRL_PDIV_2X_gc.
-Updated OP Anduril.hex file
Can you please share latest > “V.816” hex file ?
Not to detract from this thread, but swapping out the LED is easier than swapping out your driver in your mini 2. You’ll have it done in about 20 minutes. You can also try some minus green filter
Oh, you mean the hex file that was produced by my modified configs? That was in the .zip file which was linked in my post (located at anduril/hex/anduril.quad-skilbuck.hex).
I can just directly attach it, but remember — like I already said — I have no idea what I’m doing. This might make your flashlight explode for all I know: anduril.quad-skilbuck.hex (27.0 KB) Edit: Refer to the below post for an updated hex file.
I had changed that section to mcu_clock_speed(); which was copied from another config that used to contain _PROTECTED_WRITE( CLKCTRL.MCLKCTRLB, CLKCTRL_PDIV_2X_gc | CLKCTRL_PEN_bm );. This is essentially all I have done: look at changes to other configs and copy them over. Probably in some cases it may not be apropriate.
This .hex file was produced by using the above configuration files along with the most current version of Anduril 2 (cbfc1a1), as of the time of this post.
If you want to add this to your OP, please test it and/or look carefully at my changes, since, like I keep saying, I don’t really know what I’m doing.
I posted this stuff here in case it was of any use, but I wasn’t really imagining it would be “officially” added to your first post.
I assume that the reason for this was that in this commitvoltage was changed to “an 8-bit value. ... Volts * 40.”
The config file is defining custom values for VOLTAGE_RED and VOLTAGE_LOW. Either multiplying them by four, or just using the default values will probably fix the LVP.
The default voltages for RED and LOW are 3.3 and 2.9, while the ones defined in the config are 2.7 and 2.6. Was the reason for this to… get a bit more use out of a battery? Or, is there another reason that the driver needs those values?