I have a circuit I have been playing around with with a similar situation where the switch is coming from the positive supply (about 4V). With a pull-down resistor, removing the call out to enable the pull-up on the pin, and ToyKeepers mod above, I have the levels changing without an issue.
works also for me also.thanks.
Just got my USBASP in yesterday. I had been building some hex files while I waited for it to arrive.
I just finished up my Convoy C8 with off-time, no memory, MN-L-M-T. No stars on the 105D complicated it a bit, but once I got the levels I wanted (using on-time STAR) I flashed my off-time and then soldered the 1uF directly onto the attiny pins between 2 and 4. PWM level 4 is the lowest the LED would turn on (2800mA 105D w/ XM-L2).
My SRK clone is next on the list.
Thanks!
Ooh, I hadn’t thought about soldering one there… that’s a clever solution. 
For the SRK, be sure to take a look at ToyKeeper/Ferrero_Rocher/* in my code repo. Everything in there should run on a SRK (with attiny13a) and it’s all enhanced compared to STAR_momentary.
Thanks - will take a look. Need to get it disassembled first.
I thought about adhering the cap on top of the attiny and just run some small wire down to the pins - thought this would make it easier to reflash (out of the way of the clip), but figured I’d do that next time I need to flash it. Looking forward to trying it out tonight.
If you use anything with a battery check mode or low-voltage protection, you might want to check the calibration first. You can get raw voltage ADC values with the battcheck firmware; just connect a battery or power source at the voltage where you want to set a threshold, and it’ll blink out the number to plug into other firmwares.
Hi everyone,
after several try to resolve a strange problem with output i have to come back to get a good answer! I installed the firmware STAR mom , with e switch on pin number 2. I reprogram almost 30 drivers , may be 20 working good but some work strangly. If i put on turbo mode , even if a reprogram the timer to 120 sec or more or less… it will turn to lower mode after 5 sec. I changed a bunch of values, remove turbo mode, reprogram and get the same result.
I resolded every 7135 to check if it was a bad ground but i got the same result.
Is there a line of code that i could remove that could influence this situation???
Any idea what could go wrong with those driver? a bad 7135???
tks for your help
Stepping down in 5s sounds like a low voltage protection. Have you checked what voltage that driver thinks it's getting? See TK's calibration tip above.
^ Yeah, get a DMM voltage reading at the MCU pin connected to your voltage divider used for LVP. If low, check out the 2 resisters in your voltage divider.
Ill Check tonight with the TK battcheck program … I think your Right on that one.
Easy think to do is to remove battery voltage monitoring and see how it work.
That will point out what is the exact problem.
Tks for your answer!
Tks for all your answer. I check the voltage with the program of TK and i got 181 for result. Resistor have been check and value look ok. i Play with the code and i changed value and removed some
#ifdef VOLTAGE_MON
if (adc_ticks > 0) {
—adc_ticks;
}
if (adc_ticks 0) {
// See if conversion is done
if (ADCSRA & (1 << ADIF)) {
// See if voltage is lower than what we were looking for
if (ADCH < ((mode_idx 1) ? ADC_CRIT : ADC_LOW)) {
++lowbatt_cnt;
} else {
lowbatt_cnt = 0;
}
}
// See if it’s been low for a while
if (lowbatt_cnt >= 4) {*CHANGE VALUE TO 10 , SHOULD I PUT IT TO 3750 (1MIN)???*
prev_mode(); REMOVED THAT LINE AND EVERYTHING WORK FINE!!!
lowbatt_cnt = 0;
// If we reach 0 here, main loop will go into sleep mode
// Restart the counter to when we step down again
adc_ticks = ADC_DELAY;
}
// Make sure conversion is running for next time through
ADCSRA |= (1 << ADSC);
}
#endif
}
press_duration = 0;
Any idea how to change the value of battery monitoring (ADCH) in the code??? Dont want to compromise the battery monitoring and automatic previous mode…
TKs for your help!
To make LVP work correctly, you kinda need to measure the voltage with both a full battery and a nearly-empty battery, to find out how much it drops. Just one value won’t help much.
Which of these will be a best replacement for off time cap, 0.1uf, 0.22uf, or 2.2uf? I am planning to buy the otc and c1 10uf x7r from one ebay seller but he doesnt have 1uf x7r in stock, only those caps i mentioned are in stock.
Also what would be the effect if i use y5v capacitor on c1?
Hi to all,
tks for all your answer, youre the best! i finally found whats was the problem. My power supply couln’t deliver the proper current… well it work for 20 drivers but the other batch that i received was consumming more current??? I installed a freshly charge 18650 battery pack and and… IT WORK!
I spend some time figured it out what it was in the code to change setting in voltage monitor. It pin point the problem , but i felt a little disapointed to change some safety feature.Everything was fine from the begining! Thumb up for JohnyC for its code… its really well design! Almost bulletproof!
Tks for all your reply
Well, I bought the hardware (USBasp, Pomona clip, color ribbon, USB extender) and installed AVR Tools, the driver and RMM’s batch file. The only hard part so far was finding the right driver (Libsub0 v1.2.4.0 ) and installing an unsigned driver in Win 8.1. Is that the right driver?
Hooked the Pomona to a MCU and downloaded the BLF-VLD.hex, and got this:
C:\Hex and Flash Files>flash BLF-VLD
C:\Hex and Flash Files>avrdude -p t13 -c usbasp -u Uflash:w:BLF-VLD.hex:a
se:w:0x75:m -Uhfuse:w:0xFF:m
avrdude: warning: cannot set sck period. please check for usbasp firmware up
.
avrdude: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.01s
avrdude: Device signature = 0x1e9007
avrdude: NOTE: “flash” memory has been specified, an erase cycle will be per
ed
To disable this feature, specify the -D option.
avrdude: erasing chip
avrdude: warning: cannot set sck period. please check for usbasp firmware up
.
avrdude: reading input file “BLF-VLD.hex”
avrdude: input file BLF-VLD.hex auto detected as Intel Hex
avrdude: writing flash (882 bytes):
Writing | ################################################## | 100% 1.02s
avrdude: 882 bytes of flash written
avrdude: verifying flash memory against BLF-VLD.hex:
avrdude: load data flash data from input file BLF-VLD.hex:
avrdude: input file BLF-VLD.hex auto detected as Intel Hex
avrdude: input file BLF-VLD.hex contains 882 bytes
avrdude: reading on-chip flash data:
Reading | ################################################## | 100% 0.69s
avrdude: verifying …
avrdude: 882 bytes of flash verified
avrdude: reading input file “0x75”
avrdude: writing lfuse (1 bytes):
Writing | ################################################## | 100% 0.01s
avrdude: 1 bytes of lfuse written
avrdude: verifying lfuse memory against 0x75:
avrdude: load data lfuse data from input file 0x75:
avrdude: input file 0x75 contains 1 bytes
avrdude: reading on-chip lfuse data:
Reading | ################################################## | 100% 0.01s
avrdude: verifying …
avrdude: 1 bytes of lfuse verified
avrdude: reading input file “0xFF”
avrdude: writing hfuse (1 bytes):
Writing | ################################################## | 100% 0.01s
avrdude: 1 bytes of hfuse written
avrdude: verifying hfuse memory against 0xFF:
avrdude: load data hfuse data from input file 0xFF:
avrdude: input file 0xFF contains 1 bytes
avrdude: reading on-chip hfuse data:
Reading | ################################################## | 100% 0.01s
avrdude: verifying …
avrdude: 1 bytes of hfuse verified
avrdude done. Thank you.
C:\Hex and Flash Files>
So, did it work? I don’t have a light to test it with, and my test bench isn’t up yet—but a 5-pound, finned, heat sink came in today, so I’m a little closer.
This is the only warning I get:
avrdude: warning: cannot set sck period. please check for usbasp firmware up
I get this warning using the avrdude test string also. Can I just ignore this warning? Is there a way to get rid of it?
Thanks in advance.
looks like it worked to me
Looks good. Don't worry about that warning.
Well that was painless. Do you know what the “cannot set sck period” warning is? I’ve seen it before in these threads.
Also, is the source code C? I want to study the correct version of C. Some computer guy I met snow camping this weekend recommended Lynda.com to learn C.
Thanks again.
Oops RMM, looks like I typed over you.
It's a modified C, so the basics are there but there are some differences. There are some good guides to programming Atmel MCUs online. If you're not already proficient, and your goal is specifically to program Atmel, then I would focus on Atmel programming tutorials and not generic C or C++ tutorials.
It uses a limited version of C with some assembly-like conveniences thrown in for direct access to hardware features. An atmel-specific guide would be far more helpful than a generic C guide, and either one would be light years ahead of a C guide. Even a simple C program probably wouldn’t fit on an attiny.
The main ways that its version of C is limited are that the MCU lacks some basic operations — so if you use those it must emulate the process, and that takes up a lot of extra room. Specifically, floating point math is probably a bad idea (use integers instead), and it uses a lot of room for each multiply or divide instruction… so try to use addition, subtraction, and bitwise shifting instead. Also try to use 8-bit integers when possible, since that uses significantly less room than 16-bit or 32-bit.
Oh, and most standard C library functions will also use a lot of extra room… so you may want to write your own minimal versions instead, if you need anything from the standard libraries. The atmel-specific libraries are pretty decent and compact though.
Other space-saving tricks are to use data tables instead of logic (when possible), and try to avoid accessing ‘volatile’ variables or variables which were defined outside the local scope. Don’t use interrupts unless absolutely necessary. And always compile with -Os to optimize for size.