HEC Posted June 26, 2016 Share Posted June 26, 2016 53 minutes ago, Jason McNeil said: First time I've heard of this. You won't believe the number of times I've pleaded with KS before whimsically implementing FW changes that they at least inform/consult their distributors with the proposed changes. From the factory visit a couple days ago, I was informed that the conservative ride mode kicks in at 55v & limp-home 50v. Can someone please confirm what the voltage level is when it goes into this speed restriction mode? The 50% battey level speed limit info might be indeed incorrect however that's what happens if the detials of the new FW features are not communicated by manufacturers clearly and openly ... 3 Quote Link to comment Share on other sites More sharing options...
US69 Posted June 26, 2016 Share Posted June 26, 2016 sorry, what means " limphome" 50v? @Jason McNeil Quote Link to comment Share on other sites More sharing options...
Jason McNeil Posted June 26, 2016 Share Posted June 26, 2016 3 minutes ago, KingSong69 said: sorry, what means " limphome" 50v Where the Wheel is at a >7° pedal angle & generally unresponsive to lean inputs. Quote Link to comment Share on other sites More sharing options...
US69 Posted June 26, 2016 Share Posted June 26, 2016 (edited) 55volt and this "limphome" sounds totally different to "half batterie" so:. @tinawong whats the matter? give us some more info.... on "half batterie" i would NEVER upgrade to 1.20...... please! some more info! or...like i write before...let customer/upgrader decide.... Edited June 26, 2016 by KingSong69 1 Quote Link to comment Share on other sites More sharing options...
Chriull Posted June 26, 2016 Share Posted June 26, 2016 2 hours ago, Jason McNeil said: ...From the factory visit a couple days ago, I was informed that the conservative ride mode kicks in at 55v & limp-home 50v. Can someone please confirm what the voltage level is when it goes into this speed restriction mode? According to the manual 55v are 3 leds on (4 leds >56v, 3 leds >54v). 50v are 1 led blinking (2leds on >52v, 1 led blinking is everything below) As far as i remember my KS16 went in the speed restriction mode with 3 leds of the batt indicator. 1 Quote Link to comment Share on other sites More sharing options...
Jimi00 Posted June 30, 2016 Author Share Posted June 30, 2016 On 25/6/2016 at 4:51 AM, edwin_rm said: I would suppose so. But if the regular app can't do it thou, then maybe @fearedbliss or @esaj could modify the app to allow it to do so. Possible or not @fearedbliss @esaj ? Can't stay in 1.20 anymore Quote Link to comment Share on other sites More sharing options...
US69 Posted June 30, 2016 Share Posted June 30, 2016 i am sure this can only work as near as the ninebot Freaks done it: As i see it the app seams to contact a Server to look after new Firmware..... So we have to take the 1.18 File, rename it to lets say 1.21.... Then we have to set up a Server which feign/auditons he is the Kingsong Server to load up the old Firmware as the new one...... Or somebody has to reprogram the KS app in this section..... So more or less Work for Professionals...so we can also ask Kingsong to undo this stupid Setting in the next Version.... @tinawong Pleeaaaaase?! 1 Quote Link to comment Share on other sites More sharing options...
John Eucist Posted June 30, 2016 Share Posted June 30, 2016 (edited) 29 minutes ago, KingSong69 said: ..so we can also ask Kingsong to undo this stupid Setting in the next Version.... I don't mind this new "safety feature" all that much as long as it doesn't cause what @Cloud said below. On 6/26/2016 at 3:31 PM, Cloud said: I also have a concern about how this is implemented. Lets say im riding at 30kph and at that time the battery goes below 50%. Will i be hit with an aggressive tiltback because suddenly i am 5 kph over speed limit? this kind if tiltback happening unexpectedly is enough to throw one off the wheel. Does anyone know? @Jason McNeil can you find out? Edited June 30, 2016 by John Eucist Quote Link to comment Share on other sites More sharing options...
HEC Posted June 30, 2016 Share Posted June 30, 2016 27 minutes ago, KingSong69 said: i am sure this can only work as near as the ninebot Freaks done it: As i see it the app seams to contact a Server to look after new Firmware..... So we have to take the 1.18 File, rename it to lets say 1.21....@tinawong Pleeaaaaase?! Hardly - see my earlier reply in this thread: Quote Link to comment Share on other sites More sharing options...
John Eucist Posted June 30, 2016 Share Posted June 30, 2016 (edited) 15 minutes ago, HEC said: Hardly - see my earlier reply in this thread: I think he's referring to this: Edited June 30, 2016 by John Eucist removed a redundant sentence Quote Link to comment Share on other sites More sharing options...
HEC Posted June 30, 2016 Share Posted June 30, 2016 (edited) @John Eucist Yes I know and I've looked at that thread before when originally mentioned however this is using the fact that Ninebot is not doing any deep check of provided FW files. That's not guaranteed to be the case with KS and just brief look at update files via HEX editor might be hinting that it would not be that simple as we could wish for / expect (I might be indeed wrong but even then I'd not risk to perform unofficial downgrade like this unless it would be something major totally braking or making unusable the whole wheel.) Edited June 30, 2016 by HEC 1 Quote Link to comment Share on other sites More sharing options...
US69 Posted June 30, 2016 Share Posted June 30, 2016 (edited) 34 minutes ago, HEC said: @John Eucist Yes I know and I've looked at that thread before when originally mentioned however this is using the fact that Ninebot is not doing any deep check of provided FW files. That's not guaranteed to be the case with KS and just brief look at update files via HEX editor might be hinting that it would not be that simple as we could wish for / expect You are not really thinking that KS is in any way better/more professional in implementing there Software than ninebot, or? ;-) I have an ninebot Mini pro before and the Ninebot app and upgrading process itself and everything else there is A LOT more professional than anything that KS has done until today in Software and/or in their app...... As an (former) Software engenieer i also now, that i only mentioned fragments of/on the way howto do it at all.....and/or that it could be completly different But i am absolutly sure it could be done in a way....at least from an actual android/Server specialist.... I see it from this side: A lot better i would find it, that KS would implement a way to let us choose ourself....Let's say to at least set the 25km/h from just 20 to 50 % or even not set it..... It is just that i find 50% WAY to conservative.....and to do this now on an much later Firmware update would have been at least an buy/not buy Argument for me!!! Why upgrade/buy a new KS device(i have a KS14 also!) that on half of its Batterie life is just not even as fast/save as my old KS14(for example, Exchange KS14 with MCM2s or so).... Even my KS14 did not brake me in on 50% Batterie.....(under 25% i would not drive 30kmh on it at all for safety, i love my health), but even this 1 Year old device is faster now on half of its Batterie life! Edited June 30, 2016 by KingSong69 Quote Link to comment Share on other sites More sharing options...
Jason McNeil Posted June 30, 2016 Share Posted June 30, 2016 Has anyone established what the actual voltage is for this 50%? Percentages are relativistic & therefore unscientific, let's recall that it wasn't all that long ago that KS arbitrarily choose 54v as the got-off-now point. I have dozens of datalogs from a variety of Wheels & can say with some confidence that there are situations where 55v is touch and go, & that setting a limit of 25kph for this level is not unreasonable. 2 Quote Link to comment Share on other sites More sharing options...
John Eucist Posted June 30, 2016 Share Posted June 30, 2016 (edited) 12 minutes ago, Jason McNeil said: that setting a limit of 25kph for this level is not unreasonable. I think it's reasonable. Just worried about what Cloud said regarding a SUDDEN aggressive tilt-back (causing a fall) when the battery falls to "50%" and it switches modes abruptly mid-ride while already over 25 km/h. Edited June 30, 2016 by John Eucist 1 Quote Link to comment Share on other sites More sharing options...
Jason McNeil Posted June 30, 2016 Share Posted June 30, 2016 4 minutes ago, John Eucist said: Just worried about what Cloud said regarding a SUDDEN aggressive tilt-back (causing a fall) when the battery falls to "50%" and it switches modes abruptly mid-ride while already over 25 km/h. I don't think there's been any reports of this though & lots of people are using v1.2 2 Quote Link to comment Share on other sites More sharing options...
Popular Post Jimi00 Posted June 30, 2016 Author Popular Post Share Posted June 30, 2016 (edited) 3 hours ago, KingSong69 said: i am sure this can only work as near as the ninebot Freaks done it: As i see it the app seams to contact a Server to look after new Firmware..... So we have to take the 1.18 File, rename it to lets say 1.21.... Then we have to set up a Server which feign/auditons he is the Kingsong Server to load up the old Firmware as the new one...... Good news : this trick works ! I can see/download/update my faked 1.21 version by editing the json file. But now.... big dilema.... should i try the downgrade or not ? What is you opinion ? Is it risky ? Should I do it ? ... and if i decide to proceed, as an inconvenient, i won't be able to flash a new "true" 1.21 upgrade (or will have to rename it 1.22 and so on...) Edited June 30, 2016 by Jimi00 5 Quote Link to comment Share on other sites More sharing options...
Chriull Posted June 30, 2016 Share Posted June 30, 2016 17 minutes ago, Jimi00 said: Good news : this trick works ! I can see/download/update my faked 1.21 version by editing the json file. But now.... big dilema.... should i try the downgrade or not ? 17 minutes ago, Jimi00 said: What is you opinion ? Is it risky ? Should I do it ? ... and if i decide to proceed, as an inconvenient, i won't be able to flash a new "true" 1.21 upgrade (or will have to rename it 1.22 and so on...) The worst case should be that the motherboard has to be replaced? So maybe someone with easy access to new motherboards wants to try it first? Or one at least first checks the availability/delivery time and cost of a new one... Quote Link to comment Share on other sites More sharing options...
Jimi00 Posted June 30, 2016 Author Share Posted June 30, 2016 Waiting for your advice... DISCLAIMER/IMPORTANT NOTE : FOR THOSE WHO DIDN'T READ THE WHOLE THREAD : THIS IS NOT A NEW OFFICIAL FIRMWARE (but the old 1.18) 2 Quote Link to comment Share on other sites More sharing options...
John Eucist Posted June 30, 2016 Share Posted June 30, 2016 2 minutes ago, Jimi00 said: Waiting for your advice... I would hold off until more reassurances. Especially since right now your KS16, at least, still works. Quote Link to comment Share on other sites More sharing options...
edwin_rm Posted June 30, 2016 Share Posted June 30, 2016 (edited) 4 hours ago, Jimi00 said: Good news : this trick works ! I can see/download/update my faked 1.21 version by editing the json file. But now.... big dilema.... should i try the downgrade or not ? What is you opinion ? Is it risky ? Should I do it ? Just do it bro. YOLO!! It is highly unlikely a firmware reflash/downgrade will brick the machime. I have done it with smarthphones and other more advanced devices. As long as yours is a 16B you'll be fine. Also, put phone in Airplane mode, so that it doesn't download a new firmware during the downgrade. Edited June 30, 2016 by edwin_rm Quote Link to comment Share on other sites More sharing options...
Addwyn Posted June 30, 2016 Share Posted June 30, 2016 7 hours ago, Jimi00 said: ... and if i decide to proceed, as an inconvenient, i won't be able to flash a new "true" 1.21 upgrade (or will have to rename it 1.22 and so on...) I don't think that the "current" firmware version exposed by the wheel after downgrade will be "V1.21". It think that the version number that is memorized inside the KS16.BIN file can be different fom the version number showed by the JSON file. Remember, with older firmwares, we always had a firmware version number different after update than the one offered to be downloaded. Exemple: When the V1.19 was offered to download then, after update, the wheel said it was V1.18 ! So, with your trick, despite the offered download version is V1.21, I think that, after update with the V1.18's bin file, the wheel will say to the app that it's "current" firmware is V1.18. 1 Quote Link to comment Share on other sites More sharing options...
Jimi00 Posted July 1, 2016 Author Share Posted July 1, 2016 5 hours ago, Addwyn said: I don't think that the "current" firmware version exposed by the wheel after downgrade will be "V1.21". It think that the version number that is memorized inside the KS16.BIN file can be different fom the version number showed by the JSON file. in fact i think so too... I'm just afraid to brick my lovely wheel ! Quote Link to comment Share on other sites More sharing options...
Guest Chief Posted July 1, 2016 Share Posted July 1, 2016 Someone can do the same for ks14 firmware? You give me hope, I hate my wheel since I upgraded it in 1.20. Dangerous vibrations and always biping. Quote Link to comment Share on other sites More sharing options...
Popular Post Jimi00 Posted July 1, 2016 Author Popular Post Share Posted July 1, 2016 OK... I did it... I'm now back in v1.18 8 Quote Link to comment Share on other sites More sharing options...
Ecko Posted July 1, 2016 Share Posted July 1, 2016 And everything is fine?!? Could you do a step-by-step how to? That would be awesome!!!! 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.