Anduril ... 2?

[NewGuy420]

Thank you I will look into it

[NewGuy420]

Do you know anything about wiring up drivers

[wolfgirl42]

A little, but if you have a general question it might be better to start a new thread.

[NewGuy420]

Ok thanks

[NewGuy420]

I was wondering about wiring both negatives from 2 channel driver to single channel mcpcb… what would happen

[wolfgirl42]

Probably wouldn’t make any real difference. Certainly wouldn’t give you more output. Just wire the first channel (with the direct drive FET) to a single channel MCPCB and it will have the same performance as if it was a single channel driver.

[NewGuy420]

Ok thanks for the tip i didn’t think it would work in that way either

[thefreeman]

@ToyKeeper

To be viable for a torch’s always-on aux LEDs, a proposed solution needs to have less than 0.100 mA of overhead beyond what the LEDs use, and the LEDs need to go down as low as 0.050 mA. That means a total standby power of 0.200 mA or less, while the aux LEDs are lit up

Posting here instead of in the D3AA driver topic since it’s generally more Anduril related

lcsc_datasheet_2004151709_WILLSEMI-Will-Semicon-WD3153D-10-TR_C506151.pdf

3 channel LED driver :

• 2.4V-5.5V
• operating current : 80/120uA typ/max
• shutdown current : 1uA max
• regulated current options : 25, 15, 10, 5mA
• 8bit PWM dimming : 20uA steps at 5mA full scale
• I²C
• DFN 2x2mm
• dirt cheap

Depending how it can be programmed that looks like a good candidate for rich RGB

edit : 500Hz PWM frequency, could be better but for AUX LEDs it’s acceptable.

[Balint]

I2C and 2x2mm package sounds really nice. Theres a lot going for this chip.

[wolfgirl42]

Yeah, this seems like a great one. Would be nice to have smooth aux.

[ASlotnick]

So is the D3AA shipping with the 2024-04-01 release? Dark mode jokes aside, it’s the only release up on github which contains the code for this new light.

Just curious and happy to see continued developments here.

[wolfgirl42]

0161-2023-12-03-2. The -2 indicates it has two extra commits to the source code after that release, which so far @ToyKeeper hasn’t pushed to GitHub.

TK: Reminder the D3AA is in people’s hands now - I want to take a look into the D3AA specific changes myself too

[SammysHP]

Most / all of them are in the dark mode branch IIRC.

[Lumaine_Moore]

Is there a way to change the batt check readout to 1 digit after the decimal ? Like in previous versions. Coudnt find any info in the user manual on github.

[ASlotnick]

No, this is not currently user-configurable. Do you have access to flash new firmware? If so, it can be turned off in the code:

@dognodding

To use 1 decimal place accuracy for the 3C battery check instead of the 2 decimal place accuracy used in some modern lights, add the following to your custom anduril.h:

#ifdef USE_EXTRA_BATTCHECK_DIGIT
#undef USE_EXTRA_BATTCHECK_DIGIT
#endif

[wolfgirl42]

Here’s a build without USE_EXTRA_BATTCHECK_DIGIT, no other patches or mods.

820.1 KB file on MEGA

[Tulpenzeit]

Many thanks for this build. Very helpful. Gives me the only chance for a new Anduril version on my lights, without this multiple digit voltage thing - which I personally find confusing, completely useless, and an irritation.

[Chris100575 (Chris)]

I must admit that I don’t like the extra digit either, but I’ve gotten used to just counting the first two and ignoring what happens next. To be honest I’d much prefer a system of one to four blinks representing 25%, 50%, 75% and 100%. If I want to know the exact battery voltage I have a multi-meter, day to day I just need to know if the battery wants charging or not.

[SammysHP]

@Chris100575

To be honest I’d much prefer a system of one to four blinks representing 25%, 50%, 75% and 100%. If I want to know the exact battery voltage I have a multi-meter, day to day I just need to know if the battery wants charging or not.

That’s already implemented in Anduril and can be enabled during compile time.

[Chris100575 (Chris)]

Thank you, will have to look into how to compile it.