17mm & 20/26/27mm single-sided DD/FET driver release: A17DD-SO8 / A20DD-SO8 / etc

No idea about the intended target MCU.

What is your compiled size? Make sure the -Os compiler option is set.

Thanks for your help DEL.

I get this :

Error Program Memory Usage : 1088 bytes 106,3 % Full (Memory Overflow)

Data Memory Usage : 39 bytes 60,9 % Full GccApplication5 GccApplication5 0

That is close to fitting. You have to get the 1088 below 1024.
I do not use AVR Studio, but you should have a selection somewhere to ‘optimize compilation for size or -Os’. That should bring you in under the limit.

In AVR Studio right click on the name of the project (in the project tree on the righthand side) and click properties then head to ” toolchain / compiler / optimization / optimization level” via HarleyQuin here.

Hmm i didn’t find something…

Edit : Thanks wight , i’m going to try it
Edit2: Thanks wight!!! It’s ok now :slight_smile: Still have to study a lot about writing/modifying firmwares….

If they’re running the same code and behave differently, it pretty much has to be a hardware problem. You’ve probably got a short or broken connection or burnt component or something.

There are some tools to measure some of this, but if you reflash your MCU you won’t be able to put guppydrv back on. So, that makes things a bit harder.

Anyway, I’d suggest looking for physical problems on those drivers.

No, I don’t think it’s even compatible with tiny25. It sounds like you already got it working though.

If anyone knows a portable way to make the Windows atmel tools get the right build settings, it’d be nice to include that in the repository. This sort of thing comes up a lot. I’ve got the settings in build scripts for CLI-based OSes, but that doesn’t help in Windows. And if I understand correctly, WinAVR’s project files work on a per-directory basis and aren’t portable, so including those is generally not a very good solution. If it might be possible to include just one set though, and apply them everywhere… is there an option for that?

Thanks for the reply TK. It turns out that my d1 was a zener instead of shottky. I swapped in the correct diode and all is fine. I'm just a noob learning new tricks.

I'd like to apologize to everyone for hijacking this thread. After reading it thru it dawned on me that I should've asked my question in another thread or started my own.

Oops, only just noticed this. I should investigate this, but @work now. I’ve been through this of course, tweaking build settings. Guess we could at least document the Atmel Studio settings by screen grabs, etc. - would make it a lot easier for setting up.

I had some issues getting a 10uf capacitor(ordered now) and the 19.1k resistor…
So , i used a 4.7uf capacitor and a 19.6k resistor (one 22k ohm and one 180k ohm resistors , parallel).

I flashed starry offtime , but my modes are weird.
I get (with half clicks): low, medium1, medium2, high1, high2, blank(flashlight does nothing) , strobe , and turbo(?) .

If i unnderstand right , where i get the “blank” mode , i should getting battcheck.

Why did this happen? thanks

Bonus question : If i want memory enabled , i should connect “star 3” to ground ?

Uhhh - parts list in the OP calls for a 22K ohm resistor for R1, so why didn’t you use the one you had? Also the parts list calls for a 4.7 uF cap - should be fine I’m think’n (didn’t try myself though).

Not sure bout the blank mode, but sounds like the battcheck isn’t working - check those R1 and R2’s. Not sure bout the stars in starry offtime.

I might be wrong about the resistors i combined to get R1. I remember for sure i got like 19.5-19.6k ohms.

In the last pages , people suggested 19.1k ohms for R1 and 10uf capacitor , that’s why i had my doubts Tom E.
Thanks for your answer… :wink:

You might want to try battcheck.hex as a sanity check, to make sure your voltage calibration is good.

Also, I think the starry-offtime code uses only the 7135 channel for its blinks, meaning it won’t light up at all on a FET-only driver. It’s a simple one-line change though, if you want to fix that.

Starry-offtime was basically an early prototype of blf-a6, and you might find blf-a6/tk-otc.c a little more robust. It’s blf-a6 minus the soft config mode; configure it at build time instead.

In any case, a FET-only driver will likely require some adjustments to make everything work on just one channel.

question-if i use this driver in triple xpl for one 18650,it has still the same characterics? mode groups,memory on/off?
thanks:)

Yes, obviously the xpl’s need to be connected in parallel. :slight_smile:

Hello everyone .
Can anyone help me get this driver zener modded ?

I mean , what R2 , Rd (resistor in current diode space) and zener should i order , and also , is an already modified firmware available (with the right lvp) ?
I want a simple firmware , 3-5 modes , nothing more .

The driver this thread is based on went through many revs - not even sure what the latest looks like.

This is a similar driver with a zener mod. Notice the 200 ohm resistor in place of the D1, and the zener in it's proper pad, to the right of the MCU. I used this in a XHP70 mod to a Roche LS01.

Some members here told me to use R1 19.1k , R2 2.2k , 200ohm resistor on the place of D1 , and a zener .

What firmware could i use ?

edit : i use v044 boards

That's about the proper ratio, as long as the ratio of R1:R2 is bout the same as 36K:4.7K, all depends what resistor values you have or can get. If you stay with these ratios, you should be able to use standard 13A firmware with LVP protection, because that ratio specifically match's well for 2 cells in series.

Oopsie! Forgot, a "2000" labeled resistor is actually 200 ohms,