I just received a clear C8 from Simon’s store, and it is acting weird:
When I click the button the first time (to switch it on), it blinks a few times with variable rates, then settles at the minimum level (0,1%). After this I can go through all the modes and back to moonlight by tapping the button, but when I switch it off, then back on, the same weird blinking happens again.
I had one of the separately sold drivers from Simon’s Aliexpress Store do exactly the same thing.
Unfortunately no sensible reply off Simon, just Huh?, don’t understand, etc.
Very unlike him, as usually one of the Good Guys to trade with. Won’t be making a case out of it, not here to persecute the Better dealers and have placed orders with him since.
Just very disappointing as I know he has been contacted from here about the Fuse Settings in the software being programmed wrongly.
Only appears to be us 2 so far with this starting glitch, as well as being too fast on the programming select / bike mode etc.
Cheers,
S-L
P.S. Mine is the 8 x 7135 2.8A or 3A one. What rating is yours?
Mine came from Simon’s Aliexpress store as well, and it is a 8 x 7135 2.8A (red driver with “convoy” text on it.)
In the meantime I found a better description of the problem, here
The new driver and the moonlight mode was one of the reason I bought this light, but in this form, it is useless to me.
So I came here to try to find a solution, if there is any.
It sounds like some units may have lost the SRAM decay lottery. Typically each bit decays to 1 when power is removed, but it has a random chance of decaying to 0 instead. This is the natural state of that bit.
For detecting fast presses, the normal method sets a byte to all zeroes, 00000000. Then at boot, it checks to see if the value is still zero. If so, it assumes that was a fast press.
If any of the bits have decayed to 1, it assumes the button was pressed for a longer time. This could give you a value of 1 to 255, but not 0.
With a probability of 75% for each bit to decay to 1, or 25% to decay to 0, that gives us 0.25 8, or a 1-in-65536 chance that a particular byte will decay to all zeroes.
Or, using an offtime capacitor like in most BLF drivers, it eliminates the lottery effect completely.
However, there is no OTC so the byte which tracks fast presses is used to detect button timing. IIRC it uses 4 or 5 bits to count the number of button presses and 3 bits to detect how long the button was held: 0000 0000 or 000 00000 … That increases the chance of an all-zero decay to 1-in-256 or 1-in-64.
I’m going to see if I can make enough room somehow to use a second byte for tracking the decay. That should get us back to the 1-in-65536 chance of error.
Not to give you bad news, but most likely be you won’t be getting a reply until after Chinese New Year Celebration ends on February 15.
Sorry for your trouble and good luck. :+1:
Just received my unit. From Simon. The packaging is squashed, but the lights are ok. It worries me as I also ordered a spare lens and a S2+ reflector. The light’s reflector is way dusty.