Rawnei Posted Monday at 08:30 AM Share Posted Monday at 08:30 AM 5 minutes ago, Bombardier50 said: No,.. it's not. Then you had an abnormal problem that was somehow fixed, it's not related to different behaviour between the firmwares as they behave exactly the same. 1 Quote Link to comment Share on other sites More sharing options...
Popular Post Mike Sacristan Posted Monday at 08:42 PM Popular Post Share Posted Monday at 08:42 PM 20 hours ago, WheelGoodTime said: Awesome, thanks for the insight. Do you mind telling me where you got that information? I believe you, because that makes sense why I'm not getting any wheel beeps... But since my wife literally depends on that audible alarm, I'd like to know where you got that number for my own peace of mind. 🙂 I used to do a lot of firmware testing a couple of years back and that involved quite a lot of chatting with Bill aka Freestyler. In the beginning of 2023 he made the following post showing the PWM value to be 83.3% for the Sherman S. So this is the value I used as a guideline / goal / confirmation bias number and tried to make it true. It is true on the Patton which broadcasts PWM packets correctly (high speed mode on or not). Whether it is true down to the decimal is another story... but during my testing I found it to be closer to 83 than 84. 20 hours ago, WheelGoodTime said: The numbers that Mike suggested make sense why I don't get wheel beeps but I get them on EUC world. At some point, BG employee told me that LK wheels start to beep at 25%, but it makes sense now to suggest that 16% or so is the correct number. I just found myself getting constant alarms and beeps on EUC world when I'm going suspiciously slow with a full battery. For example, going about 40-43 mph and getting 20-25% PWM alarms. It definitely needs a little bit more trial and reporting back (both in high speed mode and regular mode), but I appreciate the candid discussion so we can get to the bottom of it! The PWM values on the Lynx (and probably the Sherman L) behave as if they get compressed when reaching higher values compared to the lower values. I did a lot of testing in the beginning and it took quite a lot of testing and data and comparing and trying settings. Now the firmware has been improved and bla bla bla real packets but no... it is just words since the Lynx does not behave correctly as the Sherman S and Patton do. PWM will be quick to reach 40, 50, 60, 70, and then somewhere just before 80% it will start to crawl. At this point increasing speed by 10kmh will only add 3-4% PWM. And PWM will pass 100% by quite a bit but be truncated and there is no correction that can be used since values above 100 are thrown away. Internal PWM for the is correct though so the beeper will be always beep on time. But in early firmware, internal PWM formula for the OS based / PWM based tiltback was compressed as well. So 80% PWM would basically trigger tiltback at 70kmh. And since it did not compress at/after 84% I used that. Otherwise I would be stuck riding slow. So the values and settings I have chosen are the best combination I could find to keep me safe but also to keep me free to enjoy the Lynx at it's potential with good safety. The Patton is a different story. I use 78% PWM tiltback on the Patton and the highest I have hit is 88%. I did not try to defeat or surf tiltback and I don't think I even noticed it. I just ran out of bike path at 72.5kmh GPS. So I can hit tiltback and pass it and then beeps and then beeps/alarms will be my cue. Patton -> vibration alarm 78%-> tiltback 78% -> beeps 83.x% -> Darknessbot audio alarm 84% Lynx -> vibration alarm 78% -> beeps 83.x% -> Darknessbot audio alarm 84% -> tiltback 86% I always back off at the beeps / audio alarms. 4 2 1 Quote Link to comment Share on other sites More sharing options...
Mike Sacristan Posted Monday at 09:26 PM Share Posted Monday at 09:26 PM 20 hours ago, WheelGoodTime said: you likely won't notice a difference - It merely adds an additional 10% headroom for max current. It *might* add an additional amount of freespin and top speed, that is worth checking out! The only time you'd likely notice whether the update "worked" or not is if you fall flat on your face when current reaches 301a 🤣 But if you surpass that without a cutout (but keep it below 330...) and survive, then you'll notice a difference because you aren't a meat crayon. 😉 Increasing the phase amp limit from 300A to 330A won't add speed or at least never has in any of the firmware testing I have done. It will increase how much force you can apply to the wheel before you skip through the motor. 3 Quote Link to comment Share on other sites More sharing options...
Skampster Posted Monday at 09:29 PM Share Posted Monday at 09:29 PM Correct, imo. 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.