reach

I contacted the developer about the S18's battery level reported incorrectly. He quickly replied with a precise instruction how to set manual voltage levels and then set the algorithm to "custom". This worked only on the surface: right after I make those adjustments in the app, the battery is shown with a realistic value. However, when I start the app from scratch, or after some time, the main screen is showing no battery level. The S18 makes its typical stupid series of beeps upon BT-connection. The app shows a voltage, but battery level. Looks like a plain bug to me, but maybe anybody here knows the issue an has a solution? BTW: since I need Darknessbot for proper battery indication, I notices, that the beeping of the S18 is very different when connecting to DNB, rather than EUCworld. DNB are much less beeps than EUCworld. Anybody observed such a thing before?

Just wondering... does "Leaperkim" mean anything? I didn't find a hint in the English dictionary. Maybe in another language?

Please disregard. There is a limiter setting which can only be accessed directly on the wheel, not via app. All good now.

Very late update on the topic: as it turns out, both, the Kingsong app as well as EUCworld read the battery state wrong. The lower the SOC, the bigger the error. Darknessbot shows it exactly. When the others show 32%, Darknessbot shows 4%(!!), which is accurate. I contacted the EUC guy about that, but no response. Sad, but manageable.

Hi, my new Lynx is limited (according to the app and real life) to 20km/h, even after 11km ride. The Leaperkim app doesn't allow any speed limit (only a speed alert, which is set to 25km/h). EUCworld also shows no speed limit setting, while there is one in the the same menu, when the S18 or the V11 is connected. Both apps work in principle. I can switch on the lights with it, they show all metrics, etc... Is this a factory safety limit? If so, shouldn't this go away at least after 10km?

I'm now having the same issue. I turned it on and there was a voice announcement sounding like "please prepare" and a red LED next to the battery indicator. I connected via the app to see if there was more information. I saw that a new firmware is available, so I went for that straight away: same problem. Factory reset via app: same problem. My V11 is some 3 years old, if the battery really has a problem, this can't be normal. How did the story end for you?

I noticed that my S18 is making noises. Something one doesn't hear while riding, only when you turn your ears "into the wind". Hard to describe, something between scratching and whining. Despite it looked fine, I had the suspicion that it might be the small rubber thingies on the knobby tires (Heidenau K66) touching the inner fender. So I spent some 30mins to cut all of them. Voila! Now it's silent again. What a joy to ride. Just wanted to let you know :-)

Fair point. Pretty sure they are allowed there. But the locations I have in mind are either still too far away (=costing 2 days of vacation time) or islands.

Hi. I don't think there is a legal way to do this, but I still wanted to check: has anybody managed to check-in his EUC for a flight? I remember when I was travelling with my diving gear. To transport the flashlight it was only necessary to unmount the bulb. Maybe a disconnected battery pack will do the same trick?

Hi. Can anybody recommend an 18“ spike tire? I find lots of them for motorbikes and a few for bicycles, but those for bicycles (e.g. Schwalbe Winter) are not knobby enough for snow. The Schwalbe Ice Spiker Pro would be ideal, but isn’t available in 18“. Thanks!

off topic, but I need to say that for me it's exactly the opposite: the S18 gives me soooo much confidence that at the very first ride I was consistently exceeding the top speed I've ever reached on the V11. Most likely also, because it's sitting much lower than the V11, but anyway. But that's off topic and also unnecessary: you'll get faster naturally the more you practise, no matter which wheel ;-) Hope you're wearing proper gear. Have fun! :-)

Sorry, forgot to write an update: unfortunately the FW upgrade to 2.16 did not fix the issue. It's visible with the bare eye, when it's slightly dark, at least with my white one: when you disconnect the wheel after charging, a red LED keeps glowing underneath the shell, in the area of the grip. If I'm not mistakes also BT stays on forever. Only power-cycling turns it off properly. The good news is: I have exactly that with my S18. Fully loaded, disconnected and power-cycled and, I just went to the garage to double-check: still 100% after 15 days!

OP here. Not sure if you noticed that I wrote also about that same experience. Wheel going in slow motion forward and backwards. For me a simple powercycle fixed the issue, but for me it only happened around 10% battery or even less and I was able to ride with walking pace for the missing few hundred meters home. And it was desparately beeping all the way home. So the behavior is weird, but at least you're not the only one. I have no idea why this happens already at 23% for you. Maybe some sort of calibration issue? Like some devices need to run a full battery cycle first before they display the SOC correctly. (Just guessing, I have zero insight if this is a thing!) Respect that you're already hitting 25mph as a newby! Take care ;-)

Hi. If the wheel spins freely, your issue most likely a different one. In all similar cases I've heard some of the MosFETs were blown which causes a short and blocks the wheel. But I guess this doesn't matter, broken is broken. Have you tried if the wheel, despite appearing off, can be seen from the app via Bluetooth? If your's is a different issue, maybe the repair is more trivial, like a bad connector or so. Why haven't you changed the spare parts they sent you? Are you so averse against tinkering (no offense!)? I have made myself a step-by-step manual for taking it apart. Absolutely no magic involved. If you want, I can post it here. You could at least open the electronics compartment and have a look. Also a smell might help in case of a burnt MosFET.

Woohoo! I really was on 2.09. Which is strange, because the first thing I do with any new device is to look if there is an update available :-) I updated now to 2.16 and will report back how it goes. Thanks a million anyway! Sounds reasonable. Let's hope the issue is just with the firmware.