Anduril ... 2?

[wolfgirl42]

Yeah, I haven’t merged it yet, been a bit busy, I’ll get round to it.

[andrx]

maybe I’m out to ask here, but has anyone ever tried putting anduril on lumintop B01?

[SammysHP]

That would require a new driver with a supported microcontroller.

[andrx]

I don’t even know how the driver is made, as usual I buy flashlights that are impossible to open like ts10 brass, copper and even titanium

[wolfgirl42]

In general, most lights use less capable MCUs than AVR ones. Lights that do use AVR, if they don’t use anduril, generally use narsil or similar.

[andrx]

zero

There are 4 pins

[Quadrupel]

Pins… No Attiny MCU - no custom UI.

[wolfgirl42]

@ToyKeeper

Upgraded the sp36, q8, and BLF LT1 t1616 variants to the new API. No new ramp because I still need to learn the ramp calculator properly.

Diff: upgrade sp36, q8, and BLF LT1 t1616 variants to new API · SiteRelEnby/anduril2@907b27f · GitHub

Edit: Forgot a file. blf-lt1-t1616: forgot to include a file. · SiteRelEnby/anduril2@c115c1d · GitHub

Builds:

Q8

LT1

SP36

All builds: 2.55 MB folder on MEGA

Also found a bug. Thermal regulation support is required for SET_LEVEL_GRADUALLY to be usable.
Fix: bugfix: USE_SMOOTH_STEPS had a dependency on USE_THERMAL_REGULATION · SiteRelEnby/anduril2@2eeb2d8 · GitHub

[Light_Veteran]

@wolfgirl42

Upgraded the sp36

For the pro is the same?

[wolfgirl42]

Yeah, if it’s the t1616 version. The build target is called sofirn-sp36-t1616.

[Light_Veteran]

I think yes because under driver there are 3 pads for updates

[wolfgirl42]

@Light_Veteran

I think yes because under driver there are 3 pads for updates

That’s the correct version then, yeah.

[Tulpenzeit]

@wolfgirl42

All builds: 2.55 MB folder on MEGA

My D4SV2 Dual Channel mod0136 did not confirm the update twice, via avrdude on my MacBookPro, so I returned to Rev767. On the other hand, my KR4 Dual Channel mod 0135 did confirm it. Just FYI. Have not tried any of the other lights yet.

[dmenezes]

What do you mean by “confirm”?

[Tulpenzeit]

@dmenezes

What do you mean by “confirm”?

@wolfgirl42 The avrdude software writes the file to the lamps memory, then reads what it has written, and compares this to the original file - and reports that the comparison was not OK. Twice this result, then I loaded Toykeepers rev 767 again, and that loaded and compared as OK. I was thinking that maybe the rev 784 file is too big for the memory of the lamp, but that is a pure guess. I am not an expert for such things.

[wolfgirl42]

@Tulpenzeit

@wolfgirl42 The avrdude software writes the file to the lamps memory, then reads what it has written, and compares this to the original file - and reports that the comparison was not OK. Twice this result, then I loaded Toykeepers rev 767 again, and that loaded and compared as OK. I was thinking that maybe the rev 784 file is too big for the memory of the lamp, but that is a pure guess. I am not an expert for such things.

Nope, the build toolchain checks the size, and avrdude IIRC won’t flash an oversized hex anyway as it needs to work out the layout in the MCU’s memory. Just a coincidence of bad luck, try again.

[Tulpenzeit]

@wolfgirl42

Just a coincidence of bad luck, try again.

OK, I will do that, as soon as I have time, many thanks.

[Garik_F]

Hello! Can anyone tell me what config file I should use for d4v2 with Hank’s new boost driver? kr4-v12?

[wolfgirl42]

@Garik_F

Hello! Can anyone tell me what config file I should use for d4v2 with Hank’s new boost driver? kr4-v12?

kr4-12v. It hasn’t been updated to the new API yet, but when it is it will be renamed to kr4-boost (as not all boost drivers are 12V). I’ll put it on my list.

[dmenezes]

@Tulpenzeit

@wolfgirl42 The avrdude software writes the file to the lamps memory, then reads what it has written, and compares this to the original file - and reports that the comparison was not OK. Twice this result, then I loaded Toykeepers rev 767 again, and that loaded and compared as OK. I was thinking that maybe the rev 784 file is too big for the memory of the lamp, but that is a pure guess. I am not an expert for such things.

Thanks for the clarification. I got confused because AVRDUDE doesn’t call it “confirmation” but “Verify” IIRC.

I have flashed at least a hundred times and never seen a failed verify here (both on my TS10 and FC13, using both the GChart and TheFreeman adapters). You must have some kind of hardware issue.