Yow. 26.4 mA on high. That certainly sounds like the resistor got bridged or something, because that’s close to the maximum amount the attiny can supply. It’s 26 times higher than it should be.
You could just leave it on low though. Sounds like that’s a nice tritium-like level.
Thanks TK..can I call you TK? I feel like we’ve been through a lot lol
I think that’s what I’ll do. Also, in some sick, demented, flashaholic way I don’t hate the wildly overdriven AUXLEDs. I just have to be aware not to leave them on. The torch doesn’t get hot but it’s still concerning for battery drain.
Please help. I can not adjust the temperature (thermal configuration). What should be done to adjust to 45-50 degrees?
This is how to calibrate the sensor and configure a limit of 45-50 degrees C:
Look at a thermometer to check the current room temperature. I’ll assume it says 22 C.
Turn the light off and wait for its temperature to settle to room temperature.
Click 10 times.
The light should blink once, then flicker or “buzz”.
During the “buzz”, click 22 times to tell it the room is 22 C.
The light should blink twice, then flicker or “buzz”.
During the “buzz”, click 15-20 times to tell it you want a temperature limit of 45-50 C.
Wait for the light to return to off.
Afterward, it should attempt to keep itself below 45-50 degrees C.
Thank you very much. And what is the scheme for setting the desired temperature? (if you need to change the temperature) One click is how many degrees?
The temp default setting is 30, so if you want to change it you add to the 30 (hence, click 15 times to get 45, or 20 times to get 50)
Thank. Please specify.
These items (5.6) are required to perform or make “Click 10 times” (3) and perform “During the“ buzz ”, click 15-20 times.
“hence, click now to 30 (hence, click 15 times to get 45, or 20 times to get 50)”?
The temp default setting is 30, so if you want to change it you add to the 30 (hence, click 15 times to get 45, or 20 times to get 50)
Thank. Please specify.
These items (5.6) are required to perform or make “Click 10 times” (3) and perform “During the“ buzz ”, click 15-20 times.
“hence, click now to 30 (hence, click 15 times to get 45, or 20 times to get 50)”?
Yes. The lowest value you can set the Temp limit to is 30C by not clicking at all. Each click is 1 degree higher than the minimum of 30.
Just dont forget to calibrate the temperature sensor during the first set of flickering.
The temp default setting is 30, so if you want to change it you add to the 30 (hence, click 15 times to get 45, or 20 times to get 50)
Thank. Please specify.
These items (5.6) are required to perform or make “Click 10 times” (3) and perform “During the“ buzz ”, click 15-20 times.
“hence, click now to 30 (hence, click 15 times to get 45, or 20 times to get 50)”?
Yes. The lowest value you can set the Temp limit to is 30C by not clicking at all. Each click is 1 degree higher than the minimum of 30.
Just dont forget to calibrate the temperature sensor during the first set of flickering.
Thanks for the answer.
So you need to do it. Calibration
_2.Turn the light off.
3. Click 10 times.
4. The light should blink once, then flicker or “buzz”.
5.During the “buzz”, click 22 times to tell it the room is 22 C.__
_
P.S. Please tell me where you can read about Runtime: in different modes – Turbo and other
[quote=ToyKeeper
Afterward, it should attempt to keep itself below 45-50 degrees C.[/quote]
ToyKeeper, DB Custom, nick779 !!!. Friends, thank you very much for your help. Now completed all the recommendations. How to check the temperature set by me?
P.S. Please tell me where you can read about Runtime: in different modes – Turbo and other
This will greatly vary based on a number of parameters such as your ambient temps, specific battery being used, and emitters that you have, but some rough figures were provided by TK in the original post.
valera, we sometimes get caught up in the numbers as if it were an exact science. It’s really not. These parameters get us close and that’s about as good as it gets. You can measure the amperage your light is making at different levels and then use this information to estimate run time based on the capacity of the cells you are using, but again this an approximation and not an exact science as the diminishing cells will yield lower and lower current and the run time will gradually extend accordingly.
Just dont forget to calibrate the temperature sensor during the first set of flickering.
Friends ! How to check the temperature of the installed temperature control.
I did everything according to the recommendations, and how to check it ????
To my knowledge you can’t read out the temperatur limit what you have set.
But you can read out the temperature of the lamp:
Lamp is OFF: 3 clicks = battery voltage, 2 clicks again = temperature.
Hint: The temperature is from inside the microcontroller. There is probably a little difference between outside when the lamp was on before.
At D1 can be determined. After 10 quick clicks the flashlight flashes the current temperature limit. Is there no such possibility on the D4S?
“**But you can read out the temperature of the lamp:
Lamp is OFF: 3 clicks = battery voltage, 2 clicks again = temperature.**”
I have 2 clicks include TURBO
The D1 uses RampingIOS v2 which is a custom firmware.
On the other hand, the D4S uses RampingIOS v3 which is just Andúril with some minor changes requested by Hank.
If you compare the code or the manuals, you will see, that currently there is no way to get the current set max. temperature.
You can of course, update RampingIOS v3 or Anduril to do that. But you lose your current setting when flashing.
Location: (469219) 2016 HO3 // I get way more privmsgs than I can respond to, so please ask in a public thread if possible, for a faster answer.
valera wrote:
At D1 can be determined. After 10 quick clicks the flashlight flashes the current temperature limit. Is there no such possibility on the D4S?
No.
In RampingIOS V2, the limit was set by letting the light get hot. It could also display the value, to help the user see if they got the specific value they wanted. In practice, this would often take a few tries, and people had to guess until they got close enough.
In RampingIOS V3, the user can set the value directly, instead of using the sloppy “release when hot” method. So there is less need to display the value.
Well, just finished an infuriating flash session with my D4S.
It absolutely REFUSED to flash with the 219c attached. Desoldered them as I was switching to XPL-HIs and it immediately flashed with 0 errors. Not sure if I got lucky the first time, but I repeatedly got transmit errors around the 1% and 60% mark. Im thinking its more hardware related as in with my laptop, and the low vF emitters or something. Really weird.
Well, just finished an infuriating flash session with my D4S.
It absolutely REFUSED to flash with the 219c attached. Desoldered them as I was switching to XPL-HIs and it immediately flashed with 0 errors. Not sure if I got lucky the first time, but I repeatedly got transmit errors around the 1% and 60% mark. Im thinking its more hardware related as in with my laptop, and the low vF emitters or something. Really weird.
No, corrected from Toykeeper. Lexcel wrote you must desolder the AuX-LEDS on the ROT66 to flash it. Maybe that is the same reason on the D4S?
Could the 219C have been reflowed in an incorrect orientation? A short there would have prevented the flash. Low Vf wouldn’t have done it, at least I’ve never had that be an issue in all the multitudes of one’s I’ve flashed…
Well, just finished an infuriating flash session with my D4S.
It absolutely REFUSED to flash with the 219c attached. Desoldered them as I was switching to XPL-HIs and it immediately flashed with 0 errors. Not sure if I got lucky the first time, but I repeatedly got transmit errors around the 1% and 60% mark. Im thinking its more hardware related as in with my laptop, and the low vF emitters or something. Really weird.
The problem could be the power supply.
If you take a close look, the main LED flashes for a bit when data is transferred as both of the channels use the same pins as the data lines.
Since the layout connects the programmers power supply directly to battery plus, your programmer has to also power the LEDs.
If you have a programmer that cannot supply enough current, then there will be some kind of error.
Sadly, I cannot offer you a clear solution, but maybe try a USB 3.0 port as they may be able to provide enough current.
Location: (469219) 2016 HO3 // I get way more privmsgs than I can respond to, so please ask in a public thread if possible, for a faster answer.
joechina wrote:
Lexcel wrote you must desolder the AuX-LEDS on the ROT66 to flash it. Maybe that is the same reason on the D4S?
No, that’s not it. The D4S flashes just fine with aux LEDs installed. The ROT66/PL47 flash issue happens due to the way Lexel’s aux LED board regulates power, and that’s not relevant for Emisar’s designs. Incidentally, this is also why the D4S aux LEDs have a low mode, but the ROT66/PL47 do not.
Could the 219C have been reflowed in an incorrect orientation? A short there would have prevented the flash. Low Vf wouldn’t have done it, at least I’ve never had that be an issue in all the multitudes of one’s I’ve flashed…
The factory noctigon was 219cs, I was going to try to flash it before swapping to the xpl-hi noctigon from my bricked d4s. I’m assuming it was the port but it gave me quite a fight until I desoldered the main and aux emitter boards.
I’ll retest when I have time with the xpl-his with the new flashing adapters I made. The male dupont adapters are a really nice fit in the flashing vias after being crimped and filed down a hair.
I need to double check my USB ports, but I think they’re standard 3.0 but the other ports are the high speed charge 3.0 which I’ll try next. Hopefully its not the laptop. It’s a brand new dell precision workstation.
Thanks TK..can I call you TK? I feel like we’ve been through a lot lol
I think that’s what I’ll do. Also, in some sick, demented, flashaholic way I don’t hate the wildly overdriven AUX LEDs. I just have to be aware not to leave them on. The torch doesn’t get hot but it’s still concerning for battery drain.
Nokoff..still Made in China 山寨主義
Please help. I can not adjust the temperature (thermal configuration). What should be done to adjust to 45-50 degrees?
This is how to calibrate the sensor and configure a limit of 45-50 degrees C:
Afterward, it should attempt to keep itself below 45-50 degrees C.
Thank you very much. And what is the scheme for setting the desired temperature? (if you need to change the temperature) One click is how many degrees?
The temp default setting is 30, so if you want to change it you add to the 30 (hence, click 15 times to get 45, or 20 times to get 50)
Thank. Please specify.
These items (5.6) are required to perform or make “Click 10 times” (3) and perform “During the“ buzz ”, click 15-20 times.
“hence, click now to 30 (hence, click 15 times to get 45, or 20 times to get 50)”?
Yes. The lowest value you can set the Temp limit to is 30C by not clicking at all. Each click is 1 degree higher than the minimum of 30.
Just dont forget to calibrate the temperature sensor during the first set of flickering.
Thanks for the answer.
So you need to do it.
Calibration
_2.Turn the light off.
3. Click 10 times.
4. The light should blink once, then flicker or “buzz”.
5.During the “buzz”, click 22 times to tell it the room is 22 C.__
_
P.S. Please tell me where you can read about Runtime: in different modes – Turbo and other
[quote=ToyKeeper
Afterward, it should attempt to keep itself below 45-50 degrees C.[/quote]
ToyKeeper, DB Custom, nick779 !!!. Friends, thank you very much for your help. Now completed all the recommendations. How to check the temperature set by me?
Not quite. If you don’t click at all, it will leave the value unchanged. The lowest value the user can set is 31 C, by clicking once.
All config menus “fall through” with no changes if you don’t press the button.
valera, we sometimes get caught up in the numbers as if it were an exact science. It’s really not. These parameters get us close and that’s about as good as it gets. You can measure the amperage your light is making at different levels and then use this information to estimate run time based on the capacity of the cells you are using, but again this an approximation and not an exact science as the diminishing cells will yield lower and lower current and the run time will gradually extend accordingly.
Friends ! How to check the temperature of the installed temperature control.
I did everything according to the recommendations, and how to check it ????
To my knowledge you can’t read out the temperatur limit what you have set.
But you can read out the temperature of the lamp:
Lamp is OFF: 3 clicks = battery voltage, 2 clicks again = temperature.
Hint: The temperature is from inside the microcontroller. There is probably a little difference between outside when the lamp was on before.
Or you could leave it for a while and let it stabilize, then check and it should be quite close to the ambient…
At D1 can be determined. After 10 quick clicks the flashlight flashes the current temperature limit. Is there no such possibility on the D4S?
“**But you can read out the temperature of the lamp:
Lamp is OFF: 3 clicks = battery voltage, 2 clicks again = temperature.**”
joechina Thank you very much
Made 3 clicks (from off) blinked 3 + 6 times. Carried out a test device-3,6v. The voltage is correct. But after 2 clicks 2 + 29. What is it?
The D1 uses RampingIOS v2 which is a custom firmware.
On the other hand, the D4S uses RampingIOS v3 which is just Andúril with some minor changes requested by Hank.
If you compare the code or the manuals, you will see, that currently there is no way to get the current set max. temperature.
You can of course, update RampingIOS v3 or Anduril to do that. But you lose your current setting when flashing.
No.
In RampingIOS V2, the limit was set by letting the light get hot. It could also display the value, to help the user see if they got the specific value they wanted. In practice, this would often take a few tries, and people had to guess until they got close enough.
In RampingIOS V3, the user can set the value directly, instead of using the sloppy “release when hot” method. So there is less need to display the value.
To blink out the temperature:
(Edit: I will leave it like this now, but the next time I’ll refresh the browser first… Promised!
)
Well, just finished an infuriating flash session with my D4S.
It absolutely REFUSED to flash with the 219c attached. Desoldered them as I was switching to XPL-HIs and it immediately flashed with 0 errors. Not sure if I got lucky the first time, but I repeatedly got transmit errors around the 1% and 60% mark. Im thinking its more hardware related as in with my laptop, and the low vF emitters or something. Really weird.
No, corrected from Toykeeper.
Lexcel wrote you must desolder the AuX-LEDS on the ROT66 to flash it. Maybe that is the same reason on the D4S?Could the 219C have been reflowed in an incorrect orientation? A short there would have prevented the flash. Low Vf wouldn’t have done it, at least I’ve never had that be an issue in all the multitudes of one’s I’ve flashed…
The problem could be the power supply.
If you take a close look, the main LED flashes for a bit when data is transferred as both of the channels use the same pins as the data lines.
Since the layout connects the programmers power supply directly to battery plus, your programmer has to also power the LEDs.
If you have a programmer that cannot supply enough current, then there will be some kind of error.
Sadly, I cannot offer you a clear solution, but maybe try a USB 3.0 port as they may be able to provide enough current.
Have anyone found a pocket clip that fits on the D4S?
No, that’s not it. The D4S flashes just fine with aux LEDs installed. The ROT66/PL47 flash issue happens due to the way Lexel’s aux LED board regulates power, and that’s not relevant for Emisar’s designs. Incidentally, this is also why the D4S aux LEDs have a low mode, but the ROT66/PL47 do not.
Don’t see how they could fit
Guess I’ll use it for something else, deleted the post to not create confusion…
For the love of god, my dad clicked the button a bunch of times and made a complete mess of the programming.
I’ve got it mostly sorted out except I can’t figure out how to get smooth ramping back.
Can someone please spell out the sequence to change it from stepped ramping to smooth ramping?
Thanks!
Edit: Nevermind, found this great “manual”, worked perfect: http://aperiodic.net/phil/archives/Geekery/rampingios-v3.html
-Jamie M.
The factory noctigon was 219cs, I was going to try to flash it before swapping to the xpl-hi noctigon from my bricked d4s. I’m assuming it was the port but it gave me quite a fight until I desoldered the main and aux emitter boards.
I’ll retest when I have time with the xpl-his with the new flashing adapters I made. The male dupont adapters are a really nice fit in the flashing vias after being crimped and filed down a hair.
I need to double check my USB ports, but I think they’re standard 3.0 but the other ports are the high speed charge 3.0 which I’ll try next. Hopefully its not the laptop. It’s a brand new dell precision workstation.
While on, click 3 times.
Pages