Jump to content

Search the Community

Showing results for tags 'firmware'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • General Electric Unicycle Forums
    • Forum Rules (and topics relating to this forum)
    • General Discussion
    • Videos
    • Reviews
    • Which Electric Unicycle to get?
    • Where to buy?
    • Learning to Ride
    • Advanced Skills and Tricks
    • Riding Safety and Protective Gear
    • Apps and App-related Gadgets
    • Mods, Repairs, & DIY
    • Tires
    • Local Group Meet Ups
    • Private Sales (secondhand)
    • Commercial Advertisements
    • Video-Making and Gear
    • Off Topic Discussion
    • Testing Only
  • Brand-Specific Forums (EUC only)
    • Begode (Gotway) and Extreme Bull
    • Inmotion
    • Inmotion Official Announcements and Information
    • King Song
    • King Song Official Announcements and Information (Currently Inactive)
    • Veteran
  • Inactive EUC brands
    • Airwheel
    • Firewheel
    • IPS
    • IRON Korea and Rockwheel
    • Ninebot
    • Solowheel
    • Uniwheel
  • One-Wheeled Skateboards
    • One-Wheeled Skateboards
  • Two-Wheeled Self-Balancing PEVs
    • Ninebot Mini, Segway MiniPRO, Xiaomi Mini, Airwheel S8 or equivalent
    • Segway (or equivalent)
    • Hoverboard
    • Commercial Advertisements (Ninebot Mini & equivalent only)
  • Non-Self-Balancing PEVs
    • e-Scooters
    • Other Non-Self-Balancing PEVs

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







  1. Hi all, 1. app stated device (installed l) firmware ends with *2002 2. app stated current version available *2003. 3. update through eucw or default app says successful, then verification is done (again both apps) and device (installed) version is still *2. any suggestions might one resolve this issue? Attached is 1. image of software update options 2. display of current version
  2. For future reference: "Tiltback voltage" is a misleading term, because many EUC's begin tiltback as a function of voltage and speed. So here, 0% means "when the EUC will not move at all without severe tiltback" I think these numbers are right- any criticisms? Info for other models appreciated, thx.
  3. I’m interested in knowing what firmware revisions are out there at the moment for the Sherman. Mine arrived to me in late October 2020 with FW 1053, and I’ve just received the 1055 update chip. I have seen others here have 1056, which apparently addresses pedal dip on turns. I realise that there’s no release notes or change logs with this so it is mainly what is noticeable to you. I’ll start: 1053 - my only experience with the Sherman so far. It is stable and rides well, except for an unsettling forward dip when I make a turn (especially at slower speeds)
  4. Hello everyone! I want to reflash my KS-14M back Where to get the firmware on it? If you have, please share
  5. As you may have noticed Inmotion released the firmware V1.4.15 for V11, with a statement. This post from @Cecily Inmotion describes it with a lot of restraint as bringing "New Functions", underselling it IMO. As far as I understand, it is all about battery safety, alerting the user in various cases where the packs experience faults in order to reduce risk of fires when charging. At the time of writing (June 7 2022), the fire history thread now lists three V11 fires, the last two of which occurred on May 20 and 25. Here's a preview of the battery safety and charging alerts this firmware added: I don't own a V11 nor understand how the voltage between packs can drift (maybe due to BMS drain while idle?) nor how it can result in a fire, but these alert precautions and instructions look reasonable. Inmotion noticed however that the rate of install of this new firmware is low, so @Cecily Inmotion asked for a signal boost. Given the severity, I understand any help is welcome, therefore: Apps Adding a firmware upgrade prompt, explaining why. @Seba EUC World: Would it be possible for you to include a persistent prompt requesting to update the firmware to V1.4.15 or newer? With a link to the Play Store for the Inmotion app. @Ilya Shkolnik @Alla Shkolnik DarknessBot: Could you also encourage the rider to upgrade its Inmotion V11 firmware to V1.4.15 or newer? A link to the App Store with some minimal instructions would also be welcome. Reviewers, YouTubers In no specific order: @Mike Sacristan @Hsiang @evX_Mick @ThaBlackCobra @GoGeorgeGo You Since you've just read this message, you can help broadcasting this to anybody relevant.
  6. Hi all, Today the Inmotion app pushed the 1.4.13 firmware for my V11 (Main board: 1.4.13, Driver board: 4.2.21, no BLE firmware). This time, the app was very adamant about me installing the firmware: the app actually locked the wheel on connection (flashing battery indicator, motor disabled) until I would accept the new firmware. As I've learnt my lesson on installing V11 firmware with an iPhone - V5F, V8 are fine with iPhone, rock stable, probably older bluetooth hardware, but V11 not so much - I did not accept the new firmware on my iPhone. I used my iPad instead, which worked fine, last last time. After firmware upgrade, my wheel was unlocked again (*phew*). Release notes: Optimized motor drive parameters and higher stability of high-speed riding. Body-sensation separation mode added to allow independent adjustment of sensation while accelerating and braking. Known bugs fixed. Perhaps point 1 and/or 3 prompted Inmotion to disable the wheel until the update was installed...? In any case, this firmware adds the split mode pedal sensitivity adjustment (2), which should help with braking - something I felt was weak in this wheel. After trying it out (50% forward - 30% reverse), I noticed mostly faster acceleration, but not much difference in braking. I will just continue my practice of bleeding off speed when approaching an area where I may have to make a full stop ("pre-braking"). Also, Inmotion added dynamic remaining range estimation - like Darknessbot has supported for a while now. It requires you to ride for 3 km for it to calibrate, and then it gives you a sensible reading. While it's still a bit optimistic, it's much more accurate than the default range estimation. Aside from that, I noticed that the Darknessbot app no longer gets correct readings of the various metrics, such as speed and battery level: the battery level now appears to vary with speed, turning it into a wonky speedometer. Darknessbot is therefore no longer usable with firmware 1.4.13. That's a shame really, as I used my iPhone as an arm-mounted dashboard while riding (I use one of those arm-mounted phone sleeves for running), and Darknessbot would disable screen locking and rotation when enabled. The Inmotion app has no rotation lock, and more importantly, it allows the screen to go dark and become locked: this is a no-no for a dashboard app. Hopefully, Darknessbot will get updated to support this firmware. And hopefully, the Inmotion app will get updated to support screen lock disable and screen rotation lock. Two great apps are better than one :-). And while I'm requesting Inmotion app fixes: I think the Darknessbot offline mode is great for reviewing ride metrics afterwards: no need to connect the wheel, and metrics are remembered after switching off the wheel. It would be great if the Inmotion app could also make recent ride metrics available without having to connect the wheel. What are your experiences with this firmware?
  7. TLDR Processing accelerometer to identify rough terrain allows to gradually adjust beeps, alarms and tilt-back to the riding conditions in order to provide consistent safety guarantees. It will prevent avoidable crashes, currently due to the safety margin being static: calibrated and suitable only for smooth roads. Inspiration An idea I had after watching Chooch V12 HT first ride crash, and first referenced in this reply to @Tasku Quick info and analysis about the crash: Speed reported at 37 mph / 60 mph It is (near) the max for V12 HT Tire pressure: 40 PSI Goal: protect the rim of this demo wheel sent by eWheels A bump follows a whole, which make the wheel bounce up in the air We can observe the wheel trailing behind the rider instead of staying below the rider Cause: The wheel lost forward speed by hitting the bump which converted the energy into the upwards bounce. In the air, the rider moves forward faster than the wheel which lacks traction Eventually, the rider lands ahead of the wheel instead of on top, hence crashing. My conclusion is that in step 3, the wheel doesn't have enough instantaneous torque in order to maintain the same speed as the rider during the brief moment it touches the ground. The causes for this crash are Major: a riding speed too high for the environment given the wheel speed and torque headroom. Minor: high tire pressure which makes the wheel bounce back before the stabilisation algorithm / controller / motor have a chance There was no apparent beeps or tiltback triggered. Problem to solve Alarms/Beeps and tiltback are the typical feedback mechanism the wheel has to indicate that it is near its maximum capabilities. With this information from the wheel knowing its status, the rider can modulate speed and reduce it before getting in a situation where the vehicle would not be able to provide the power needed to keep the wheel stabilized, hence introducing an over-lean and inevitable crash. From Chooch's video we learn that alarm & tiltback thresholds calibrated for safe riding on good roads are inadequate on bumpy off-road trails Despite that fact might seem obvious to everyone, in practice many riders push their wheel near the limits - wether they realize it or not. So these limits must be set according to the real world conditions. Solution description Adaptive safety margin and speed limit leverages information every self-balancing vehicle already has access to: accelerometer data in order to dynamically adjust the beeps/alerts and tilt-back thresholds. Example If the wheel identifies that the wheel is rolling on a bumpy off-road terrain, it should increase the safety margins as well as Two methods proposed to identify terrain A fairly simple algorithm could process the vertical acceleration read by the sensor, using filtering and thresholds to identify how "bumpy" is the ride. The bumpy index would go up quickly and go back down slowly in order to provide a form of smoothing over time. A neural net could run on a local micro-controller in real time and do recognition on which type of road surface is currently ridden, like asphalt, gravel, forest single track, skate park, jumping. The model should infer more parameters like: confidence and intensity of shock/bumps/vibrations in order to set the safety margin. Suspension and tire pressure Elements affecting the amount of shocks and vibrations: Higher tire pressure: increases Suspension: reduces Suspension tuning: increases or reduces Fortunately, tire pressure or suspension behavior, are taken into account automatically by this approach. It's a useful trait since they affect the safety margin requirements as Chooch describes in the crash video. Bonus: extra features Based on machine learning If we have an AI model inferring riding type, we can adjust the wheel pedals, and throttle response accordingly. Sensor fusion between accelerometer and phase current variations The amplitude of oscillations of motor phase current should also tell about how irregular the surface is, since each branch, rock, hole would create a negative or positive current spike in order to maintain flat pedals and self-balancing. Combining accelerometer data with phase current can give a more rich representation of the ground surface in multiple dimensions, in a way that can give a sense of its texture. With barometer sensor By using a barometer sensor (not available in current EUC generations), the wheel could also identify very precisely inclines and adjust its behavior in real-time when climbing, riding downhill. Example uses: Adjust power limits when climbing to avoid overheating Adjust pedals when climbing to avoid dipping too much in soft modes Adjust pedal behavior descending to avoid dipping too much backwards which makes braking using power pads difficult in softer modes Tune self-balancing behavior to maximize grip when climbing or descending on rocky terrains Mobile phone implementations As suggested by @rolis on the EUC-Technical group, phone implementations could also be explored. Mobile app alternative Provided the phone would be securely held in a pocket and not moving around erratically in a backpack, it should be possible to infer a few things about the riding conditions from the movement of the device. In turn, alarms could be emitted by the mobile app to a bluetooth speaker or standalone alerting device both for: adaptive safety margin, as offset on top of inverter load (Inmotion) and safety margin (Kingsong) provided over bluetooth data, and possibly estimated PWM for Begode and Leaperkim wheels. speed alarms, as offset on top of the real wheel speed limit (Kingsong) or offset on top of estimated max speed limit (based on voltage) for other wheels. Mobile apps could run with the idea and might implement this concept quicker than OEM in their firmware, although there is the challenge of the lower quality of the data captured. Prototyping A mobile phone strapped securely to a wheel case would be useful to: build and test a proof of concept gather accelerometer data in order to train machine learning models This would be more like an intermediary step towards a wheel implementation, a convenience, helping to iterate fast initially, and enable crowdsourcing for accelerometer data collection in diverse contexts. Implementation recommendations In order to avoid dangerous bugs, the minimum safety margin (calibrated for smooth asphalt) must always be the minimal safety margin and maximum speed limit the absolute maximum as well. These parameters must not only be calculated or inferred by a neural net, but always enforced some minimum and maximum values. In some cases, some expert riders would prefer disable the adaptive margins and limit at their own risk. Typically for race scenarios, or if the implementation has issues which were not fixed yet in a firmware update. If using neural net inference, riders should be able to record and contribute training data which can be sent to the OEM via a mobile app. I believe that a low complexity implementation, without machine learning or barometric data would already provide value. Limitations The solution proposed does not help with sporadic potholes on otherwise smooth roads Tiltback might not be effective on rough terrains (but alarms still are) Early feedback I described this idea with @Cecily Inmotion who shared it with Inmotion Engineers. They answered: So maybe we'll have an OEM implementing soon, at least in testing? I'm confident that these adaptive limits are required to make this domain of EUC safety more adaptive instead of relying solely on rider experience. I would like any EUC maker to implement these ideas, so there won't be any patents filed or any attempts to keep control. Now, what do you guys think. Does it makes sense to you too? Would you like to have this feature? Can you think of more improvements or drawbacks?
  8. This is not my idea !. This super man MRN76 !! He figured out how to install any firmware on the wheel! Instruction in Russian !! Http://electrotransport.ru/ussr/index.php?msg=1042930
  9. Interesting, the new 1.1.7 BMS FW claims better/lesser vampire drain, but after leaving my Z10 unridden indoors for 1+ day (42 hours), I'm seeing what translates into .14V drop per day, roughly 1% per day.
  10. Hello everyone, got a bit of a story here. So yesterday I discovered that with the newest revision Gotway/Begode wheels (most models) you can now update the firmware through the manufacturer app. I had read that the newest update can get rid of the annoying motor whine. So here's where it gets weird, there are 2 different firmwares for this wheel. One says "T3 84v, speed shows MPH" and the other is just "T3". Living in the states I decided to go with the MPH version since the display came from the factory reading KPH. The first flash went well, no issues BUT the display was still reading in KPH and the whine was still there. I thought that was strange so I decided to try again however this time the wheel entered the bootloader mode (constant quiet beeps) to receive the update but the app froze at 11%! So after about 5 minutes of waiting and sweating thinking I just bricked my wheel I decided to shut it off. Upon turning it on there was no display and no signs of life from the motor. Just the constant beeps from it being in bootloader mode. Que more freaking out. I restarted the app and lo and behold it can see my wheel. Upon retrying the update it worked fine thankfully. However, the same thing persisted (speed in KPH and loud whine). I decided to try the other "T3" firmware, flashing went without issue and the whine is gone! I went for a short ride (~5 miles) and all seems to be well. I will note the motor commutation creates a bit of noise (almost like a vibration) at slow walking speed when using the trolly handle now but I'll attribute that to whatever they did to make it quieter. I didn't notice a change in performance but I've only been riding for a week so I'm not really pushing anything to the limit. So here's a couple things I would suggest Begode improves for this process. 1. They really need to add a change log for these firmwares. Both of them report the same version #GW1601001. Even though they are clearly different. Plus we have no idea what they are changing. 2. They need to translate the firmware section in the app to english. It's dead simple (only 1 button) but it makes an already sketchy process even weirder. 3. Why would they name one firmware "speed shows MPH" when it clearly does not? If it's an unfinished firmware I certainly would NOT release it to the public! So anyways that has been my experience updating my Tesla V3 Firmware. Hopefully I don't get some random glitch that sends me face first into the ground lol. Thanks for reading!
  11. What are your impressions of the impact of the firmware on the driving characteristics of FW1.0.58. I mean subjective evaluation because officially nothing has changed that would affect the pedal dip acceleration or braking. After update to 1.0.58 i can say here is diference in riding "feel" for me wery positive way. Straight after update (i not calibrate level yet) and my first ride on new FW with knobby tire 28PSI diference is big great job Veteran company now is sherman worth XXX dollars more . I have my "test 5km circuit" where i testing PSI, pedal adjustment ,riding modes, "track" include inclines and many types of surface and roundabout for dip testing. Positives: Firmware 1.0.58 is definetly harder in medium mode now is wery close to gotway medium mode or KS16X hard mode this mean you can acelerate more efortless. Simply say aceleration curve is stronger. Sherman is more nimble. Important thing whan need to be say on every mainboard revision FW can be diferent feel this is just FACT confirmed by testing Ks16X on board revisions 1.4 vs 1.5 where FW 1.05 was great on revision 1.4 and very bad on revison board 1.5 Same be propably on sherman and board revisions think about this before comment! Pedal DIP: My original FW was 1.0.56 and comapre to this Pedal dip on 1.0.58 have hudge improvents in long inclines and sharp turning too is strong change on ALL modes soft/medium/hard Pedal hardnes: Pedal is harder definetly medium mode is like/almost medium on MSP 2500W or hard mode on KS16X what is big improvement for me and something i wish many time sherman be like this. PA: PA pedal i ride before was PA +1 this mean now PA+3 but if i use PA adjustment sherman lost efortless aceleration what gain on PA +0 this is subjective but this is what i feel and my testing always end this results. Negatives: Braking is same like on 1.0.56 or little worse i canot decide if is downgrade or upgrade becasue when i break intensively pedals dip under presure very deep to level where i am close to fall behind. Veteran sherman have speed motor we(riders) must acept this becasue is just fact. This is subjective and i am very heavy rider 260lbs +-120kg with gear this is on edge technical spec what sherman have this must be write here for fair play and i compare braking to MSP2500W or KS16X where i never experience braking pedal DIP. (on FW 1.0.56 i have 2 falls to my ass becasue braking dip on sherman both in low speed) Speculative: After my test circuit when i check data in eucworld i realize on inclines where normaly eucworld report 6000W now report 4000W and all AMP numbers is lover compared to numbers on 1.0.56. Motor sound in inclines is little diferent but strugle vibration in same when i am around 3500W+ reported power. Results: Im happy i do this upgrade over my fear and risk brick sherman for me is many positives and this is what i want long time make sherman more efortless to ride. Personlay i think this FW and update tool is LEAK and hope this firmware is safe for public use/to ride now i have big anxiety ride this FW1.0.58 becasue i have strong PTSD after my asphalt faceplant on MSP HT in 30+miles(55km/h) becasue i overlean EUC. My sherman speed limit/tiltback is 43km/h (25miles) im not aceleration/speed demon anymore.
  12. Hi All! As I promised to myself i worked hard to develop this app. This is the latest version. AVAILABLE SPEEDS: -One battery from 16 to 24 Km/h -Two batteries from 22 to 30 Km/h. Items needed: 0) A Ninebot A1 or A1+ or S1 or S2 (with a quite recent firmware); 1) J-Link (clone too) to connect and download original firmware; 2) Few soldering skills to connect J-Link to Ninebot; 3) A backup of your original firmware! I won't do it!; 4) This software to modify your original firmware. You can find full tutorial below. Please send me other Ninebot binary files to increase the compatibility of my app. And remember... I WORKED HARD, and I want to make it better and to make it compatible with your device, so please be GENEROUS... ? By clicking on KO-FI you can donate... Think how you would have paid to have your speed increased... ? Feel free to suggestions, big mistake patches, and anything else! Any feedback appreciated. Goodnight! GM Please remember to like me, or love me if you feel it! ? Speed2Increase120.zip
  13. Hi guys! From the documents released today, I'm considering the Inmotion V12 as my next wheel. (currently: Inmotion V10F + Kingsong 16X) However the the V10, V10F and V11 have a flaw in their alarm design, preventing it to ring more often than every 5s. And so much can go wrong during 5 seconds, it's enough to go from standing still to almost max speed. It's a really bad flaw that can lead to over power or over-lean of the the wheel during the 5 seconds the alarm is muted, due to any combination of: acceleration speed incline It was identified by analysing a V11 crash and I reproduced it for demonstration purposes in this video: Now, the V12 goes up to 70 km/h. An overlean at this speed is much more dangerous than the moderate 35+ km/h of the V10F. Please 🙏, anyone testing the V12: can you check (safely) if this issue is fixed? I'll be happy to help with testing methodology 👍 References: Post about this video EUChristian V11 crash due to this issue
  14. Hi guys ! I'm looking informations for some of my friends. The lastest official Z10 firmware is the 1.0.5 but some of my friends have the firmware 1.0.2 and the application tell them there is no update available but 2 of them have no problem and have update to 1.0.5. Even when using a china vpn to try to get the update, they can. Does any body else get this problem ? Or anyone have an idea about how resolve this ? Thanks in advance for help
  15. This is still a beta version at this point. Just upgraded with no issues, my wheel has fortunately not become an expensive paper-weight Haven't taken it for a ride yet, but reports so far indicate that there are no noticeable changes in behavior compared to FW 2.0. (I can confirm that has been my experience so far on FW 2.02 with my 16X, although I've only put 15 km on it since the upgrade) The only change I can confirm for sure is the ability to change pedal tilt (as well as set wheel auto power-off). And no, the headlight/taillight bug has not been fixed...
  16. The currently on fire 16x thread is hard to dig through to find actual issues with the newly released KingSong 16x between all the comradery between us. I am creating this in hopes that we can have a thread listing and tracking the issues that are currently being reported with the first batch of 16x. I am waiting on the second batch and curious about what they will fix before or during production is the largest driver of this thread. NOTE: I will try to keep this post updated with any issues folks list below. ChangeLog at bottom Latest Firmware = 1.06 (click here for post with release notes) —— Issue: high speed/stress oscillation problem and will be out in a few days.Recommended everyone update to this firmware as soon as possible as a safety precaution. Source Fix: Firmware 1.03 fixes Issue: There is another problem where the pedals will not stay level and regularly show a very slow oscillation in some cases which makes the wheel unridable. This might be a hardware problem. Kingsong may or may not have stopped 16X production temporarily to fix this (board modification I guess). Not entirely clear what is going on, here's the source: click I would expect any good dealer to be informed about this and only ship out wheels with the fix from now on. That is conjecture. Fix: Issue: The 16X has a notable "gyro effect" where it becomes hard to turn the wheel above a certain speed, it will try to keep going straight. Like the Z10. This is due to the standard tire that comes with it (the one with a colored stripe on one side). Replacing the tire with a different one, like the CST tire the Nikola has or the Chao Yang tire the 16X prototype had, removes the gyro effect almost entirely. This is only due to the standard tire that comes with the 16X, nothing is wrong with the 16X itself. Fix: Not sure if this is really an issue vs personal preference, 16x tire thread going on HERE. Issue: Battery level not showing up correctly in KS app android ver. 3.1.3 & iOS version 1.3 (or Darknessbot not sure about WheelLog) Fix: n/a Issue: Bluetooth module might cause interference as reported by others, I don't have the wheel yet so I have not tested it. by @Unventor Fix: Process below in this post. Shared with permission from Jason @ ewheels | @Jon Stern states this is still an issue and Jason @ ewheels has looped in KS rep via email. Issue: Handlebar screws rattle loose while riding. Fix: Process below in this post. Shared with permission from Jason @ ewheels Issue: Firmware 1.06 introduces throttling at 76V (50%ish) with new firmware. Fix: not upgrading to 1.06 Issue: Firmware 1.06 for some has introduced noises that are bothering dogs around where it was not on 1.05. Fix: not upgrading to 1.07 ------------- Process for Updating the Bluetooth Music Module Applies ONLY to the KS16X Download the pdata.bfu“ file (link at end) AND a MP3 music file to a FAT32 Formatted USB stick—place on the the parent folder, without folders King Song 16X Firmware File Switch on the KS16X Go into the App & verify the Music function is enabled from the settings. Insert the USB stick into the left USB socket The Music module makes the announcement: "Enter Music Mode", then the installation process starts After installing the firmware, six long beeps will sound Disconnect the USB stick & switch off the Wheel Delete the .bfu file from the USB stick Applying Threadlocker to the handlebar screws: Some feedback received from some of the first Customers, was that during use, vibration from riding can cause handlebar screw to fall-out. In the package with the charger, you should have received a small bullet tube of threadlocker, this is to apply to the screw that secures the handle to the retractable telescopic rails. Please allow it 20 minutes to dry before using. Change Log Updated 2019-09-07 @ 0930am PDT - Added issue with noise bothering dogs after 1.06 firmware update. Updated 2019-09-05 @ 0800am PDT - Added 1.06 firmware message and issue about 76v throttling Updated 2019-08-27 @ 630pm PDT - Added BLE issue comment by Jon Updated 2019-08-23 @ 4pm PDT - added iOS app and version, darknessbot to speed issues on app, confirmed by myself. Updated 2019-08-22 @ 11am PDT - Info from Jason @ ewheels about ble update and lock-tight for handle screw. Previous Changes were not logged.
  17. 2nd Batch Update We have already started shipping the 2nd batch Inmotion V11 Electric Unicycle. Please contact the local distributor to check if you are in the 2nd batch. Difference App Functions Added and Firmware Updated IOS Latest Version: v.7.5.3 ; Android Version v7.5.2; It has the same function just the different way we named it in our company. 1."Go-home" Mode Started from 2nd batch, we have offered the latest firmware 1.1.62. But you have to upgrade it mannually. 2.55km/h embeded to the official app. Step 1 Get to the "Vehicle Setting" Step 2 Click "Feature" word for five times, then it will automatically turn to the 55km/h option--"Fancier Mode" Step 3 Switch to "Fancier Mode". Then you have succed unlocking V11 to 55km/h. 3. Inmotion Smartwatch Supported It will be soon released it to the market. Please stay tuned. 4. Audio Effect Redefine(You can upgrade it by simply update it to the latest firmware) Effect Package 1st Batch: one package only 2nd Batch: multi pacakge, one click to switch DIY Sound Effect With the new firmware, you can record your one and only voice as the sound effect. Time to redefine the alarm. And it's supported to reset to default setting. Backup Effect When you reset the wheel, the sound effect will be backup and reset to it automatically. Structure and Apperance Design 1. Pedal Protective Parts. 1st Batch: Inmotion Orange 2nd Batch: Gray Rubber 2. Chrome Plate 1st Batch: White Stainless Steel Background, White Logo 2nd Batch: Black Stainless Steel Background, INMOTION Orange Logo delete on Sep 3, 2020. It was mistaken made by one of our employee transferred the wrong message. The final version of the chrome plate and the logo will stay the same as the first batch. Deeply sorry about that. 3. Redesign Valve Cover The final color of the cover will not be painted. 4. Motor Bearing 1st Batch: Z Bearing 2nd Batch: RS Bearing 5.As for the fragile breaking point at the saddle, it will be improved in the later batch by using metal hole. If you have any puzzle towards the above question, feel free to send me an email. Liam@imscv.com
  18. Firmware Issue 1.1.6 WARNING, NOT SAFE! CUT OFF if feet leave fotplates (see Yourube videos at bottom) Here is the list so far, PLEASE if anyone can do the "footplate test" (as on first video) on mainboard 1.1.7 and report if issue is solved. I would like to update mostly for the BMS, but I dont dare if the unsafe behaviour is still there. Lift vehicle while pressing on foot plate, wheels should spin as its lifted. Then release foot plate pressure. Wheels SHOULD free wheel to a stop - NOT STOP INSTANTLY by breaking like in 1.1.6 video. FW marked with * is the one I have now and includes my comments, other FW comments are from FW update screen *mainboard 1.0.8 - GOOD/SAFE, no cutoff if foot removed with wheels spinning (when off ground) - PROBLEM, adjusting steering sensitivity and ride sensitivity during an active ride, sent mine into steering freak mode and after stopping it was locked into left turn (constant turning). Turn back to "auto mode" again at standstill - problem solved, Now it can once again be set manually for sharper control (or softer if one likes that) - PROBLEM, tiltback and alarm at 19km/h in app - PROBLEM, 19-20km/h in app = 16km/h real speed (GPS show 16 when pushing it constantly) mainboard 1.1.6 WARNING, NOT SAFE! CUT OFF if feet leave fotplates (see videos below) mainboard 1.1.7 Optimized uplsope performance Optimized alarm in slope Other small known bugs MY WARNING - UNKNOWN IF SAFETY ISSUE FROM 1.1.6 IS RESOLVED *BLE 1.0.0 Ocasinal problems at "search again" (Huawei P8) BLE 1.0.1 IOS11 bluetooth connection fix *BMS 1.1.8 No known/noted yet BMS 1.2.0 Optimized cell balance function *Co-control 1.0.6 A bit confused when starting "not facing" remote Co-control 1.1.4 New function: - Optimized follow me performance *Follow 1.0.0 None noted, see co-control 1.0.6 Follow 1.0.X NO UPDATE AVAILABLE (have it been included in co-control in latest FW?) *Remote 1.0.3 None noted, remote and phone both work fine to remote control Remote 1.0.4 New function: - Fix that remote sometimes cant be charged - Optimize indication of remote control battery volume (level?) Gimbal N/A (dont have one) Likely this one also suffers from 1.1.6 FAST FORWARD to 00:20 for crash
  19. Issue: BT module might cause interference as reported by others, I don't have the wheel yet so I have not tested it. Fix: talk to your dealer there should be an update done by use stick. Note: My dealer will update my wheel before it is shipped. Video show how: (shown at 6:15ish)
  20. Hi, I'm a new member of this wonderful forum. I would like you to help me find a solution to my problem please . So, my problem is that I purchased Hoverboard for robot projects. Unfortunately, I discovered that it is not original. My project is to control their motors with Arduino. So, I tried to work on it, but I made a mistake and I lost the firmware. There are three CPUs and I only work with one of them. I will mention it in the pictures. If you can help me get him back to work as they were or given me a solution to control it with Arduino, I would be very grateful.
  21. Hi all, I was hoping someone might know of where I can find a list of all the different firmware versions and the changes that each version made for the KS-16s. I've spent like 20 minutes and can't find anything except a few comments on the forum about specific versions. Ideally I would also like to know the date they were released and if it's safe to upgrade straight from v1.07 to 2.01 or do I need to be cautious about how I upgrade? Appreciate it!
  22. I updated to FW 1.07 yesterday and did extensive testing yesterday and today. Speed and throttling: On FW 1.05 I rarely hit 50 kmh. I really have to push the soft tiltback and I am not a big fan of that. Also I have only been able to reach 50 kmh with a pretty fresh battery. As voltage drops I then get stuck at 48, 47 and eventually down to 45 kmh soft tiltback. This would continue down to 72V. I would rarely push on the soft tiltback at FW 1.05 because I was unsure about the power reserves. This is something that nagged me more and more as time has passed because it has stopped me from pushing the wheel (and myself). FW 1.07 is similar but with once difference: When I was at 75v I pushed a bit on the soft tiltback to see what would happen. So instead of riding the soft tiltback gently I went into a more medium-aggressive lean on the pedals. It was still quiet. I then hit some bumps and at that point it did 4 beeps in quick succession. It only did this once and this is the 88% overpower alarm. Once the bumps were gone it was quiet again. This was a huge relief for me because it was the missing link I was looking for. At the skate park I smacked too aggressively into a high climb and the wheel let out a high amp warning. It has done this in 1.05 as well. On my way home today I was doing 30kmh at below 64v. It was letting off battery alarms and medium tiltback. I then went up a 22 degree ramp and it didn't make a sound. During the very last halv V under load I was still doing 20kmh and also throwing my body back and forth on the wheel to see if I could get it to do the 4 beeps at me which it did a couple of times. The numbers above where not achievable going up slight inclines as the 16x loses some speed there. Also I don't have data for below 70v on the 16X with FW 1.05 as I rarely went that low. 34kmh at 67v is good enough for me. Range: I did 73km. Temperature was +3C. Riding weight was 69.5kg. This was spread out over 2 days. 50km yesterday. Lights: There are more light modes for the headlight. And rear indicators for turning. Nice features. Charging: I am currently charging with a 1Radwerkstatt charger which tends to charge between 5.0A and 5.1x A. The wheel is quiet and has been for an hour now. Climbing: Feels the same. Perhaps a tiny bit harder. Pedals: Feels the same. Perhaps a tiny bit stiffer. Acceleration and braking: Feels smoother. So what does this mean as many have said it before... It feels less jerky. Any spikes and irregularities in body movement or pedal movement seems to be smoothened out. This makes acceleration and braking easier for me. It was too twitchy before and cause me to wobble. Also it being a 16X wheel one would expect some crazy acceleration from it. Simon (18 XL), Thomas (MSX) and I did a drag race when I was on FW 1.05. We are all even. I accelerated harder than I usually do. I have way more riding time and experience than Simon and Thomas put together. But the 16X holds me back. Now with smoother 1.07 acceleration AND a 88% warning AND a high amp warning maybe I can finally push the wheel. However it was quite interesting that the 16X did not have a clear advantage when it comes to acceleration and that was against 18" wheels. So because of that little drag race I felt that there was no big loss in upgrading to FW 1.07. The wheel is less twitchy now and I feel more relaxed on it. Some of this could be in my mind as well of course. Final words: 1.07 feels safer and more mature. It feels smoother and more robust. I think at this point the 16X is quite a mature product. I did not use the speakers but I might further on. Let me know if I missed anything or if you would like me to to do some more tests. Day 1 of riding Day 2 of riding Final thoughts / review
  23. Hi! Who can help to solve this mystery? My speed goes to 22kmh, I am 79KG, and I always drive in Red Sports mode. I want my ES2 to go to 34km/h. My configuration: ES2Lite but changed serial to a ES4 Custom firmware 5.5.1 (1.5.1) with speed 34KMH and motor power 48000 BME v 141 BLE v 104 External battery Regards M
  24. Hi everyone, This is my first post as a new owner of Ninebot ES2 purchased during 2018 Black Friday's. Upon switching on the scooter for the first time, I got a prompt to update the firmware, the current firmware is 1.2.9 but no where is mentioned what is the number of the new firmware. Here is a screen shot from the phone. Is it safe to update? What are the benefits of this update?
  • Create New...