Jump to content

palachzzz

Full Members
  • Content Count

    269
  • Joined

  • Last visited

Community Reputation

535 Excellent

7 Followers

About palachzzz

  • Rank
    Advanced Member

Profile Information

  • Location
    Moscow
  • EUC
    Ninebot Z10, Inmo V8, Inmo V5f, GW Tesla

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thank you for your work)) Without your contribution I will not start this work at all, because with you fork Inmotion was almost work, but speed was incorrect, that made me download the sources and fix this problem xD
  2. That's doesn't means that I can't ride without overlean. I realy like Ninebot Z10, I rode different wheels during this summer (18XL, V10F, GW Tesla) about week on each (~350 km) on each, and rode about 1000 km on GW Tesla when my Z10 was burnt. Also I tried 16X, MSX.. I feel advantages and disadvantages of each wheel.. But as result, I bought the second Z10 for the mean time until I repair my first Z10 But, I can't say that Z10 the best, or the safest wheel, because it isn't true.
  3. Pretty conservative GW use phase currents, it gives almost nothing. 210A-220A is the absolute maximum for measuring of MSX/Monster mainboards, and about 160A for Tesla board. This currents in logs doesn't means burning. I have seen a lot of logs with numbers 210A + and all of them still alive. Most probably the real currents may be more... (not measured). But I have log with burnt monster at current 170A That's right. MSX84 rotate speed - 78km/h Z10 - 81.5 km/h Z6 - 61.5 km/h
  4. Forget about 58.8v.. Limitation of NB speed is pretty reasonable for battery which installed in Z10 (pretty poor). Nominal battery current - 60A, but the limit is about 110A, it is almost twice overcurrent for battery, that's why it's pretty reasonable from different points of view. Lately I got burnt bottom Z10 board, and realized that Motor phase "C" FETs are burned at all (4 pcs), it makes short circut for the battery input, but.. nothing else were burnt. So it seems Z10 BMS has overcurrent protection, so, I think software limitation of current implemented in BMS. Such capable motor installed in Z10 to mitigate possibility of speed overlean (it is not possible in any charge on stock firmware). That's good point. Like if you choose MSX 100v and set tiltback at 48 kmh
  5. @Planemo, well... EUCs have two general type of overlean: 1. by speed (that's something described in first post) 2. by torque First is pretty clear, no matter how powerful the motor, controller and battery are, the motor cannot spin faster than it can. In some point it will provide not enough torque, that will lead to overlean. This is what the numbers in the first post are about. Thats absolute maximum that cannot be exceed with such motor and such battery voltage. The second one - it's much more complicated to describe for each wheel. It depends on slope, weight, wind, acceleration, etc.. a lot of things which leads to increase battery current. And in general the maximum possible current depends on speed (at higher speed - less possible current may flows throw the motor), that's about @Chriull 's graphs. Also current may be restricted by software, like Ninebot Z, Inmotion and KingSong. That's all makes everything difficult to explain, but.. Generaly gotway wheels are more powerfull, that's why it is much more hard to overlean gotway wheels on speeds [max speed] - [10km/h]. So, it is almost impossible to overlean MSX84 at speeds less than 50km/h (fully charged). But due software limitation of current in Ninebot Z10, I can overlean it at any speed, even at almost zero speed. So, if you choose MSX100 and will not exceed 60 km/h (full charge, and.. about 45km/h at zero charge) - you will be much more in safe, than using Ninebot Z10 at any speed at any charge.
  6. Most probably it was 84v instead of 67v, because the user set incorrect voltage option. I have following numbers (from Russian Telegram community, confirmed by logs or screenshots, sorry I can't provide it right now, need to seek in history): MSX84 - 62.6 km/h (screenshot) - the fastest speed without overlean. 63km/h - overlean (I think I already have sent this log to @Chriull) MSX100 - 72km/h -without overlean (video) Nikola100v - 66km/h - almost overlean (video ), 62km/h overlean at almost empty battery (video) Monster100v - 72km/h - without overlean (video) Tesla84 - 56km/h without overlean (screenshot), I did 53 km/h by myself. Ninebot Z10 - overlean between 62-64 km/h (video, iphone - no logs, only fixed max speed - 64km/h, 62km/h was successful previous day). Ninebot Z6 - overlean around 46 km/h at half battery So.. Using this data, I derived a very simple overlean formula: Overlean speed ≈ rotation speed * 0.8, MSX84: 78*0.8 = 62.4 MSX100: 93*0.8 = 74.4 Nikola100v: 83*0.8 = 66.4 Monster100v: 91 * 0.8 = 72.8 Tesla84v: 69 * 0.8 = 55.2 Ninebot Z10: 81*0.8 = 64.8 Ninebot Z6: 61*0.8 = 48.8 Surely it does not take into account the load, slope, and is valid only for an almost fully charged wheel. Therefore, it is a very rough estimate, but it allows you to roughly understand the capabilities of each wheel, and when I see numbers more than this - it makes me pretty sceptic that the data is relevant (rotation, app bug, etc)
  7. @Planemo, In my expirience, 110 Amps = overlean, in any speed in any voltage. Pedals starting to tilt forward and becomes soft at current ~80 Amps, in any voltage in any speed. So I usually set alarm at 75 amps, it's really helpful for Z, but please note, as @Chriull told, in some circumstances data is not updated for a some period of time (0.5-3 sec) I think this video may be helpfull. @Chriull here log of this ride for your visualizer if needed (time ~8:48:50): https://electro.club/data/users/7470/geodata/4681.csv and here my another overlean (with fall) on test of acceleration (time ~11:02:00), without video: https://electro.club/data/users/7470/geodata/8340.csv
  8. I don't know why, but I can confirm this threashold. Moreover, I didn't see more then 58.4v on batteries when charge is finished, most probably the reason - diode in BMS (basicaly, FET in reverse-diode mode).
  9. 9A limit in BMS. But be carefull with 9A charging. Because the battery get hot with 9A, when the temperature of one of batteries will exceed 40 degrees - BMS will block charging. In this case, if one battery will block, but another one will continue the charging with 9A (not 4.5A per battery but 9a into one) it may cause burnout of the BMS like it was in my case I use to charge 6a (350W) every day (and would say that it is safe, because it works during 6.5k+ km, and about 9 month). During this time I charged about 10 times with 9A and it was OK. But now I would say - that 9A not so safe)
  10. By the way, the WheelLog with Garmin support already in Play Market.
  11. @AllSySt3msG0, great job! thank you for your effort. Guys, just to let you know - I have a little free time for now, so I don't check this forum often. But I still able to update Google Play version if needed. I'll add @AllSySt3msG0's commits soon (It is under test right now). So feel free to send pull requests, or contact me via email if needed.
  12. Not possible. Indicator update once per 10sec, like voltage in app.
  13. Never seen such behaviour on V8. This example with wheel which is not transmits negative currents. Decreasing speed with voltage sag doesn't means braking, it also may mean hill, viscous surface or something like that.
×
×
  • Create New...