Attiny25/45/85 FW Development Thread

Sorry I was responding to Mitko. But anyway, what are doing to handle the voltage spikes that cause the 25 to reset? Are you scoping the signals? Generic 13A boards and parts usually result in flaky problems with 25/45/85's -- all noted earlier in this thread.

BangGood (or Manker) that developed the 25 driver for the X5/X6's (runs Bistro) used a 12 uF cap, not the standard 10 uF cap -- that seems to fix the problems on that board (well they think it fixed it mostly), But I've done more.

Yes TOm, the controller is overheating and starts acting wierd, happenes too often in smaller lights like S2( mostly) and C8s with longer turbo run time

Nope, Astro drivers are bad - bad caps, bad soldering work too
I use fet +1 v 09 and now for the first time i used V14 boards

I dunno - I either forgot about this heat problem or never heard it before. Has the topic ever come up? I've run lights to the untouchable level, but do't recall seeing anything wierd.

Edit: But.. You got me think'n. Maybe when they are that hot, I just turn them off and don't play with modes, etc. Guess it depends on the nature of the weird problems - flaky while just running in a mode, or flaky when operating (changing modes, etc.).

Try making an offer on this one - you should get it for ~15$ (AU)

I feel like this might just be a big development. :beer: :+1:

I recommend the cheap ones from ebay, there are several vendors, e. g.:

You’ll need more than one if you are going to use them often, this clips - also the expensive ones - don’t last forever. I used the expensive clips of 3M and Pomona before, they have not been better than the cheap ebay ones.
As you probably know you will have to re-wire the connector.

I agree with Mike.

I have flashed over 30 drivers the last 3 months with the cheap soic8 clip from ebay without any issue.

Me as well. I must have flashed the same driver at least 100 times with the 4$ model which comes with the grey cable and small PCB. I find the extra cable length useful. It isn’t showing any sign of wear so far but I am very careful with my stuff.

Finally got the drivers working , but with some problems .
The fet+1 with the attiny13a (a6 firmware), have very short times for the half clicks , nearly impossible to click . Is there any way to have longer times ?

The other driver , the one with the attiny25 (bistro firmware) seems it has one “empty” mode before moon .

The ” empty ” mode( its actualy a true moonlight, you can turn it off in the menu, 3th blink) is caused by the mosfet( high int resistance) and/or poor solder joints

WIll you post a pic of that driver pls( a macro one if possible)

As long as the hardware is not faulty I would first try to adjust the regarding definitions in “tk-calibration.h”.

// The OTC value 0.5s after being disconnected from power
// (anything higher than this is a "short press")
#define CAP_SHORT 190
// The OTC value 1.5s after being disconnected from power
// Between CAP_MED and CAP_SHORT is a "medium press"
#define CAP_MED 94 // Below CAP_MED is a long press

To increase switch times you have to decrease the values.

But it’s the 7135 that controls moonlight , right ? I will try to increase the value in the firmware and try again.

About the 13A drivers , the solution is probably the one Flashy Mike mentioned . Any clue how much lower should the values be ?

They are not cheap caps from ebay , but it’s the X7R from Farnell . Will try Mikes method before changing something :slight_smile:

As a start I would leave CAP_MED unchanged and decrease CAP_SHORT in steps of 10.

Success! fet+1 with 13A are ready!!!

Reduced both CAP_SHORT and CAP_MED by 20 and works perfect! Also changed to lower moonlight (from 3 to 2 on the 1x7135 channel) .

Edit : Still can’t find the problem on the other with the attiny25 . Moon mode is just empty…

This explains how to calibrate the button timings, along with some other things:
http://bazaar.launchpad.net/~toykeeper/flashlight-firmware/trunk/view/head:/ToyKeeper/battcheck/README

Also, the tiny25 fuse settings are in bin/flash-25.sh in the same repository.

Thanks Tk ,
I couldn’t find this file you mentioned . :slight_smile:

Ive finally made some sort of firmware for my drivers available: Mike C drivers and X85 firmware.

Very nice. May I include it in the firmware repository? If so, what kind of license should I list for it?

Each project has a key/value-list metadata file used for description and indexing, but I can probably figure out what to fill in for the rest of that. :slight_smile:

Sure you can add it, but managing version releases on the repository is something I won’t do. If I release a new version I’ll just switch out the zip file in my link.

What kind of license? I don’t know much about those things… as it’s for my own specific drivers I’d hope no one edits it and sends it off… But if someone actually builds any of my drivers they might want to change the code so they should. To be honest, with all the other cool driver projects floating around I don’t expect must interest in mine. I’m mainly releasing this stuff because I promised I would a long time ago :slight_smile:

Key/value-list metadata file?? Sounds good to me :blush:

Already found a bug… I’ve replaced the zip file in my download.

It might be useful if I can replace firmware versions in the firmware repository after all.