Difference between revisions of "AVR Drivers"

139 bytes added ,  11:31, 1 July 2013
m
Correcting errors
(Adding Nanjg 150C. descriptions)
m (Correcting errors)
Line 243: Line 243:
'''Mode Memory''' Some flashlights will remember the last mode they were in. Often the mode will be remembered after the light is off for a couple of seconds (if it was too short an interval you couldn't change modes by half-pressing the tail clicky to off briefly). But NANJG drivers usually have memory that sets after the light is on for a couple of seconds. When you turn the light off, it will come back on in the last mode, but if the light was on for less than 2 seconds, it will come back on in the next mode. This works pretty well except that if the light is on for a couple of seconds and you want to change modes, you will have to half-press the clicky once and end up in the same memorized mode, and then again to change the mode. The reason for memory to be this way is that when power is cut to the driver, it can't write to its memory. But it is easy for the memory to be written while the light is on and a timer can be used to write to the memory after the light is on for a couple of seconds. In order to get conventional memory, a capacitor would have to be added to hold on to power long enough after the power is turned off for the driver to write to its memory. BLF user sixty545 has done just this, described [http://budgetlightforum.com/node/799?page=3#comment-15453 here].
'''Mode Memory''' Some flashlights will remember the last mode they were in. Often the mode will be remembered after the light is off for a couple of seconds (if it was too short an interval you couldn't change modes by half-pressing the tail clicky to off briefly). But NANJG drivers usually have memory that sets after the light is on for a couple of seconds. When you turn the light off, it will come back on in the last mode, but if the light was on for less than 2 seconds, it will come back on in the next mode. This works pretty well except that if the light is on for a couple of seconds and you want to change modes, you will have to half-press the clicky once and end up in the same memorized mode, and then again to change the mode. The reason for memory to be this way is that when power is cut to the driver, it can't write to its memory. But it is easy for the memory to be written while the light is on and a timer can be used to write to the memory after the light is on for a couple of seconds. In order to get conventional memory, a capacitor would have to be added to hold on to power long enough after the power is turned off for the driver to write to its memory. BLF user sixty545 has done just this, described [http://budgetlightforum.com/node/799?page=3#comment-15453 here].


'''Low Battery''' The Atmel chip can monitor voltage through its VCC pin, however, the voltage can't be more than 1V. Therefore the battery voltage being directed to the VCC pin must go through a couple of resistors to come down to a readable level. Then the software can have some calibrated values so that the user is warned of a low battery by the brightness dropping or the light flashing periodically.
'''Low Battery''' The ATtiny chip can not monitor voltage through its VCC pin, however, it can monitor voltage via an ADC input channel pin as long as the voltage is within measurable range of 1.1V internal reference voltage. Therefore the battery voltage must go through a couple of resistors to be divided to a readable level. Then the software can have calibrated values so that the user is warned of a low battery by the brightness dropping or the light flashing periodically. Or do anything else the user wants when low voltage is detected.


== Drivers ==
== Drivers ==
confirmed
36

edits