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.
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.
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.
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.
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.
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.