Convoy S2+ new firmware (biscotti) memory mode jammed

52 posts / 0 new
Last post

Pages

eggmang
Offline
Last seen: 3 months 1 week ago
Joined: 10/23/2016 - 05:22
Posts: 28
Location: Australia
Convoy S2+ new firmware (biscotti) memory mode jammed

I’ve been happily using one of my S2+ without memory mode. It contains the new firmware which I believe is called Biscotti.

The other night I decided to activate the memory (hit switch fast ten times, wait for the second ‘buzz’ then hit switch again) – Memory mode turned on but the problem now is that I cannot turn memory mode off – the driver simply fails to acknowledge the change and now the light seems to be permanently stuck with memory mode on.

All other light modes work perfectly.

I assume the driver memory has failed, (which is a bit disappointing as I had another biscotti driver completely die on me while in the middle of changing modes). I know Convoy says not to leave the torch in the mode configuration for long periods as it could “wear” out the memory, but I never do this, it was the first time I went to activate the memory.

Has anyone seen this or have any idea on how to fix it? If not I may have to get in touch with Simon as the light is not very old. I have seven S2+ with biscotti drivers, and two of them have failed in some way already. I know it is a budget light but this failure rate is pretty bad Crying

MascaratumB
MascaratumB's picture
Offline
Last seen: 3 hours 35 min ago
Joined: 10/29/2016 - 12:12
Posts: 2855
Location: Portugal

Hum, now that you have the memory mode ON, what happens exactly when you try to enter the configuration?
Also, how many 7135 chips does your light have?

eggmang
Offline
Last seen: 3 months 1 week ago
Joined: 10/23/2016 - 05:22
Posts: 28
Location: Australia

I have 7135 ×8 driver

The configuration behaves normal. Hit switch fast 10 times and then it has the two buzz. First buzz to set mode and second buzz to set memory. I suspect mine is a later model biscotti as the flash rate of the buzz and mode is much slower frequency than early biscotti.

It functions just like the flow chart on Convoy aliexpress website – the problem I am having is that no matter how many times I hit the second buzz, it will not turn memory mode back off.

I don’t know much about microchips but I assume there is some sort of flash memory inside the driver and perhaps the location responsible for storing this memory on/off value (0/1) has died.

I guess in future I will just leave alone the memory feature as I don’t want another driver to get ‘locked’

toddcshoe
toddcshoe's picture
Offline
Last seen: 16 min 15 sec ago
Joined: 01/24/2018 - 23:49
Posts: 1195
Location: Foley, MO

Now I don’t know if this will help but, back in the stone age and the beginning of surface mount components, if we ever had a problem with a circuit we would remove all power from said circuit and short our dc + and our dc – together for a few minutes, again, without power applied. Then we would power the circuit back up and start from the beginning. So maybe take a wire and short between the + spring and the tube for a few and power everything back up. Just a suggestion. Don’t hold me responsible for anything please. Smile

zelee
zelee's picture
Offline
Last seen: 1 month 2 days ago
Joined: 06/04/2013 - 06:53
Posts: 1981
Location: S.E.A

i never know that using the configuration will wear out the memory of the driver, only happened when using biscotti driver or apply to another driver too?

Don’t mistake my kindness for weakness.
I am kind to everyone, but when someone is unkind to me, weak is not what you are going to remember about me.

eggmang
Offline
Last seen: 3 months 1 week ago
Joined: 10/23/2016 - 05:22
Posts: 28
Location: Australia
toddcshoe wrote:
Now I don’t know if this will help but, back in the stone age and the beginning of surface mount components, if we ever had a problem with a circuit we would remove all power from said circuit and short our dc + and our dc – together for a few minutes, again, without power applied. Then we would power the circuit back up and start from the beginning. So maybe take a wire and short between the + spring and the tube for a few and power everything back up. Just a suggestion. Don’t hold me responsible for anything please. Smile

I understand, tried shorting the DC input last night but this didn’t work. Thanks for the tip though

zelee wrote:
i never know that using the configuration will wear out the memory of the driver, only happened when using biscotti driver or apply to another driver too?

I have changed mode options on it many times without issue, it was only when I changed the memory that the memory got stuck. I even changed the modes to other ones to see if it would help with the memory but no matter what it stuck on.

varbos
varbos's picture
Offline
Last seen: 14 hours 51 min ago
Joined: 02/16/2017 - 07:36
Posts: 245
Location: Europe

I have same problem with my Convoy C8 Clear w/ Biscotti.

Today I required to change the mode, but accidentally pushed on the second ‘buzz’ and therefore toggled memory to on. I don’t want this, so subsequently tried to toggle it off but it is impossible. Mode memory is stuck on no matter what I do.

It is about 15-16 months old, I didn’t use it much, in fact it spent most time in storage. I have used the mode change just a few times (under 10 surely); I cannot recall if I ever attempted to toggle memory.

lexvegas
Offline
Last seen: 14 hours 32 min ago
Joined: 07/24/2018 - 14:20
Posts: 90
Location: USA

Anyone find a solution for this?

Yokiamy
Yokiamy's picture
Offline
Last seen: 10 hours 28 min ago
Joined: 10/18/2016 - 15:47
Posts: 1143
Location: Netherlands

Did you follow the UI?

Thijsco19 wrote:

a regular symptom of flasholism Big Smile

“Flasholism is the most severe form of flashlight use and involves the inability to manage your flashlight use habits. It is also commonly referred to as flashlight use disorder. Flashlight use disorder is organized into three categories: mild, moderate and severe. Each category has various symptoms and can cause harmful side effects. If left untreated, any type of flashlight use can spiral out of control.”

lexvegas
Offline
Last seen: 14 hours 32 min ago
Joined: 07/24/2018 - 14:20
Posts: 90
Location: USA

Yes. I can change modes fine, but I can’t change mode memory no matter if I do short, long, etc during the 2nd buzz

varbos
varbos's picture
Offline
Last seen: 14 hours 51 min ago
Joined: 02/16/2017 - 07:36
Posts: 245
Location: Europe

lexvegas wrote:
Anyone find a solution for this?

Unfortunately not. I might try to reflash the firmware but currently I don’t have the equipment.

In Banggood reviews I see this:

So that is you, me, eggmang and at least one other guy. The problem may not be widespread but it is not unique, maybe some bad batch of drivers or a component which is failing prematurely.

Yokiamy wrote:
Did you follow the UI?

It is definitely not a problem with what I am doing. I have several Convoy with Biscotti and I can successfully toggle mode memory on all but one. One simply doesn’t change. It changed from OFF to ON at least once, now it refuses to change back.
lexvegas
Offline
Last seen: 14 hours 32 min ago
Joined: 07/24/2018 - 14:20
Posts: 90
Location: USA

That’s the craziest thing. I have re-flashed! It behaves with memory mode straight out of the programmer!

MRsDNF
MRsDNF's picture
Online
Last seen: 11 min 9 sec ago
Joined: 12/22/2011 - 21:18
Posts: 12600
Location: A light beam away from the missus in the land of Aus.

If there is a part on the driver, capacitor or something else, for memory, maybe it is no good.

My current and or voltage measurements are only relevent to anything that I measure.

Budget light hobby proudly sponsored by my Mastercard and unknowingly paid for by a hard working wife. 

djozz said "it came with chinese lettering that is chinese to me".

old4570 said "I'm not an expert , so don't suffer from any such technical restrictions".

Old-Lumens. Highly admired and cherished member of Budget Light Forum. 11.5.2011 - 20.12.16. RIP.

 

lexvegas
Offline
Last seen: 14 hours 32 min ago
Joined: 07/24/2018 - 14:20
Posts: 90
Location: USA

That’s what I thought, but mode changing works fine. I’ve ordered a few replacement drivers that come pre-flashed, so I’m going to dump the ROM and compare to see if the code is different. I’m also thinking about manually compiling biscotti without mode memory support. Lol.

Phlogiston
Offline
Last seen: 5 hours 48 min ago
Joined: 10/27/2016 - 16:57
Posts: 661
Location: Scotland
lexvegas wrote:
That’s the craziest thing. I have re-flashed! It behaves with memory mode straight out of the programmer!

That sounds like a dead memory cell to me. The EEPROM cell storing the setting has failed, so the MCU always sees a one or a zero despite all efforts to set it to the other value. In this type of failure, other EEPROM cells – like the one storing the mode setting – can still be perfectly fine.

If you know what you’re doing with the firmware code (I don’t), you might be able to move the storage location to a different EEPROM cell. Alternatively, you could just hard-code the setting you want and render the EEPROM irrelevant.

neo71665
neo71665's picture
Offline
Last seen: 1 week 1 day ago
Joined: 02/21/2016 - 10:53
Posts: 146
Location: Arkansas

My next to last s2+ failed but when it happened it went to only single mode. It would not enter into the mode selection at all. Had to make a video for Simon and he sent me out a new driver. That light was only 3 or so months old and I only keep it in mode 2. Pulled it out of my pocket one day and it only had 100%.

lexvegas
Offline
Last seen: 14 hours 32 min ago
Joined: 07/24/2018 - 14:20
Posts: 90
Location: USA

I also have a C8 that is stuck in “always on” mode, but I fried that one myself while swapping parts. I need to probe it with my scope, but I’m going on vacation next week and have to pack more than just my flashlights Smile

I am wondering if it might be a fried diode or something, as I didn’t do too much to it, and I inspected it under a magnifying glass.

Barkuti
Barkuti's picture
Offline
Last seen: 5 hours 38 min ago
Joined: 02/19/2014 - 14:46
Posts: 3135
Location: Alhama de Murcia, Spain

PWMing 7135s Facepalm in a practically unregulated driver (when high frequency switching 7135s, they lose most regulation voltage margin and efficiency). Screw it!

Believe as you wish and undergo its consecuences, period.

 

Cheers Party 

sbslider
sbslider's picture
Offline
Last seen: 3 hours 48 sec ago
Joined: 01/22/2017 - 13:41
Posts: 786
Location: United States

So exactly how does one disable next move memory? I recently received a light with biscotti and the mode memory was off, but now it is one and I can’t figure out how to disable it.

I have tried no click and a short click during the second buzz, has not seemed to change the behavior. My first light with biscotti in it, have only had it a couple days.

Edit: I guess what I am finding is if I leave the light off long enough (have not figured how long) it will go back to the first mode. Guessing that is just a characteristic of biscotti. If I turn the light off, then back on even 10 seconds later, it starts at the next higher mode. Maybe 2 minutes off and it’s reset. Guessing the timeout is somewhere in between. Actually, what I am finding is the mode set also reset to number 2 mode set also. Hmmm . . . . I had moved it to mode 10 when I found I could not reset the mode memory.

PocketSammich wrote: I don’t need this, but I want it. Please sign me up.

Quad-XXX
Quad-XXX's picture
Offline
Last seen: 3 days 9 hours ago
Joined: 06/30/2018 - 01:46
Posts: 34
Location: Nowhere Land

- memset(0) manually if needed
- port(:)=0 manually if needed
- change the backdoored compiler

For me: the looped counter ?D? because above

Alienon2wheels
Offline
Last seen: 1 day 4 hours ago
Joined: 12/04/2017 - 11:31
Posts: 17
Location: India

Actually, there is a bug in those drivers. I’m the one who posted the BG reviews and so far I’m 4 for 4 when it comes to them getting stuck in memory mode on.

A reflash fixes the problem, so it’s not a broken memory cell, since it doesn’t move any of the storage locations for config or mode.

All in all, just a software bug.

varbos
varbos's picture
Offline
Last seen: 14 hours 51 min ago
Joined: 02/16/2017 - 07:36
Posts: 245
Location: Europe

Alienon2wheels wrote:
Actually, there is a bug in those drivers. I’m the one who posted the BG reviews and so far I’m 4 for 4 when it comes to them getting stuck in memory mode on.

A reflash fixes the problem, so it’s not a broken memory cell, since it doesn’t move any of the storage locations for config or mode.

All in all, just a software bug.


Interesting, thanks for the new information
ToyKeeper
ToyKeeper's picture
Offline
Last seen: 40 min 51 sec ago
Joined: 01/12/2013 - 14:40
Posts: 8243
Location: (469219) 2016 HO3
Alienon2wheels wrote:
All in all, just a software bug.

Yeah, it’s a known issue. And an annoying one.

Simon wanted new firmware, so he sent me some drivers to use for development. Nanjg 105d drivers, specifically. I got things working, even though the drivers had particularly bad 7135 chips, and I sent Simon a proof of concept to test. I wanted to find out if he liked it, if he noticed any issues, etc. It wasn’t really finished, but it was far enough to ask for feedback.

I guess there was a misunderstanding, because he then sent that version to production. Facepalm

Not long afterward, I found a bug which occurred on an infrequent random basis, causing the issue described in this thread. It didn’t sample enough bits of SRAM, so some drivers would fail. On some hardware it never happens, on other hardware it happens almost every time, based on random luck. And I fixed it. But that was too late, because Simon had already made a lot of drivers.

Making all this worse, production used different driver hardware. And different fuse values so it ran at the wrong clock speed. And the production hardware seems to have a lot of variation between individual circuit boards, which messes with the button timing. And MCU pin 5 is connected to ground, which makes reflashing difficult.

So… a lot of things went wrong. And now, a year and a half later, it’s still biting people. Sad

Some of it can be fixed by reflashing, but that’s not something people can really be expected to do. Some of it may be fixable by changing or removing components from the driver. But, again, not something people shold have to deal with.

If you do reflash it though, gchart’s Babka has more features. It’s worth a look.

Alienon2wheels
Offline
Last seen: 1 day 4 hours ago
Joined: 12/04/2017 - 11:31
Posts: 17
Location: India

Thanks for providing some background.
Next time I get around to flashing stuff, I’ll definitely consider Babka. Smile

d_t_a
Offline
Last seen: 5 hours 10 min ago
Joined: 08/04/2017 - 23:58
Posts: 940
Location: Manila, Philippines

That’s some background information that explains what’s happening. Thanks again ToyKeeper!

Hmm.. does that mean even the newer recent batch of Biscotti (Convoy S2+ and Convoy C8/C8+) would still have this bug? Simon did not try to fix the problem that’s affecting some Biscotti drivers?

ToyKeeper
ToyKeeper's picture
Offline
Last seen: 40 min 51 sec ago
Joined: 01/12/2013 - 14:40
Posts: 8243
Location: (469219) 2016 HO3
d_t_a wrote:
Hmm.. does that mean even the newer recent batch of Biscotti (Convoy S2+ and Convoy C8/C8+) would still have this bug? Simon did not try to fix the problem that’s affecting some Biscotti drivers?

I think he fixed it a long time ago, but I’m not totally sure. He might just still have some of the old drivers around, and they could get mixed in randomly.

Generally the easiest way to tell whether a driver is from the first batch is by measuring the speed of the bike flasher. If it pulses once per second, it should be good. If it pulses twice per second or more, it’s probably a first-batch driver. The first batch ran at about 2.3X the intended speed, due to the factory accidentally overclocking the MCU.

Aleister
Aleister's picture
Offline
Last seen: 7 hours 18 min ago
Joined: 10/23/2010 - 15:27
Posts: 656
Location: Greece

- Check this pre-alpha version that almost works when Hermes in on Scorpio, background temperature is 24c and you are wearing black belt and give me feedback…


a few days later


- So, did you checked it?
- Sure, it works fine, I pushed it to production
- …

Been there, lived that Big Smile

Let a flooder be my wife and a thrower be my mistress

Phlogiston
Offline
Last seen: 5 hours 48 min ago
Joined: 10/27/2016 - 16:57
Posts: 661
Location: Scotland

Not quite that bad, but I did have someone send one of my betas to production once. Fortunately, it stood up to “unscheduled production testing”, so all we had to do was send the “new minor version upgrade release” a couple of months later Smile

lexvegas
Offline
Last seen: 14 hours 32 min ago
Joined: 07/24/2018 - 14:20
Posts: 90
Location: USA

So what’s the “real” final hex/source for biscotti? It could be that I flashed an older version or something.

Alienon2wheels
Offline
Last seen: 1 day 4 hours ago
Joined: 12/04/2017 - 11:31
Posts: 17
Location: India

TK has the flashlight firmware repo in her signature. Simply dig there, it contains a precompiled hex file that works well.

lexvegas
Offline
Last seen: 14 hours 32 min ago
Joined: 07/24/2018 - 14:20
Posts: 90
Location: USA

Yeah, I’m more wondering which branch is “final”. I’m not familiar with bzr at all, so I’ve been using the stuff at flashlight-firmware with no extra on the end.

Pages