Jump to content

Seba

Full Members
  • Content Count

    552
  • Joined

  • Last visited

  • Days Won

    1

Seba last won the day on January 31

Seba had the most liked content!

Community Reputation

924 Excellent

7 Followers

About Seba

  • Rank
    Advanced Member

Contact Methods

  • Website URL
    https://najednymkole.pl

Profile Information

  • Location
    near Gdansk, Poland

Recent Profile Visitors

431 profile views
  1. Dear WheelLog users, today I released WheelLog 2.0.30 update that is available at https://euc.world/getwheellog. This version contains many new features, bug fixes and improvements. It also adds new languages - German, Brazil Portugese and Russian. However there is one issue I want you to be aware of, especially if you're using Pebble watch. 2.0.30 may not work with Pebble (again) Sadly, I don't have a Pebble (but I will try to get one) so when working on WheelLog development I can't test Pebble-related features. So if you're using Pebble, please stay with 2.0.28. If you don't use Pebble, feel free to update to 2.0.30 as it brings very useful features. I'll try to resolve Pebble issues as soon as possible.
  2. Photos taken by WheelLog are saved to phone external memory, under WheelLog/Pictures folder.
  3. Voice prompts are already at their maximum possible volume.
  4. I had similar problems some time ago. My wheel started to loose BT connection without any reason. Updating it to 1.12 helped and until now, I don't have any more problems. But now I don't think that the problem was firmware version related, but I'm more and more convinced that the root cause was some firmware execution state. It's important to note, that by turnong off the wheel doesn't turn of wheel microcontroller. It is still active and executes it's code. By upgrading I caused the MCU to reset, so BT module was also reset. I suspect that when "turned off", BT module is ordered to low-power mode, but it will retain it's config. When I had problems with BT connectivity I noticed that BT address changed. But it's just my guess. Yes, I noticed that previous WheelLog versions (including original from which I forked) caused wheel counters to reset. However I fixed it in 2.0.30 that will be published tomorrow. I also suspect temporary server connectivity problem. From 2.0.28 normally there is no risk that WheelLog will close before any network operations will finish. It will go to the background, but won't be killed until all photo uploads and tour closing command will be complete. Well, it may be caused by some delay in photos indexing. This already worked with all versions that supported adding photos to tours. However I'm glad it works for you now. Your photos are great and I LOVE them . Really marvellous landscapes! Keep adding photos to your tours
  5. These settings and features wasn't changed and reflect Github repo I forked from. As I don't have a Gotway wheel, I was not able to develop/test it. If I understan correctly - are you asking to add actual speed reading at the end of "Slow down" message? Well, I know that alerts logic may seem tricky. In general, you should set alerts from low priority to high priority. So for example - lowest priority set to 30 km/h, medium priority to 35 km/h, high priority to 40 km/h. Alert will work only if speed is set to non-zero value. As for battery alert I assumed that there is no direct danger accompanied with low-battery condition. Usually wheel will limit speed and starts to tilt back, so I set battery alarm as a non-critical warning that doesn't need to be repeated like speed, overcurrent and overtemperature alerts (that in my opinion should be addressed/responded immediately by the rider). I'm considering adding two-level alert. One "instant" that you can set to detect abnormal spikes (as is currently) and another for filtered, "sustained" current value. Adding voice/audio alerts and ability to log rides online were main causes I decided to fork WheelLog and continue develop it. Especially voice/audio messages and alerts are far superior to wheel beeps, because they are usually gone in wind noise. Thank you I'll try to find someone with Tesla so I'll be able to test and fix it. But this may take some time. Originally, I made it for myself, just to allow my blog readers to watch me live on map when I was on a longer tour. Soon realized that other EUCers would love to use this functionality, so I made it available to anyone interested. Seems it was a good decision, as euc.world is going to be more and more popular among EUC riders. I'm glad they find my work useful and this makes me motivated to expand it's functionality and add new features PS. Would you like to have a WheelLog in Swedish language? If yes, pconsider making translation. If you're interested, PM me and I will give you details and advices. In short, it shouldn't take more than one hour. You just need to translate two XML files. Not a complicated thing. Voice alerts are much more functional when used in native language.
  6. Hello fellas! Currently "Top riders" section is calculated from total user history. Well, this may (and probably is) creating confusing results. What do you think about narrowing this to - say - last 30 days? I think it would better reflect latest uses activity, make "Top riders" results more fair and actual, and will also focus on actual, not historical user activity. In this case users that were active long time ago but are inactive for some time won't be high ranked. I'll be glad to hear your opinions.
  7. It's normal for Gotway wheel. Unlike other makes, Gotway doesn't send battery current to the connected app, but sends motor phase current. In general it reflects motor load, but is more an arbitrary value and should not be confused with battery current. This is because current flow in three-phase BLDC motor is more complicated. With 84V MSX and Tesla spikes up to 120 A should be considered normal. They are not "real" amps and watts, use it only for reference. It's hard to tell from such short trip. Voltage drop at the first kilometer may be considered normal, as there is a change from "idle" voltage to "under load" voltage. From what I see from your charts you've been riding faster at the end (and probably going uphill), so it may be the cause of additional 15% drop. Just keep track on your future rides and examine charts
  8. Seems that there is an issue with @GMOne's WheelLog version. From what I see, it doesn't report distance to the server or report it incorrectly.
  9. This is intentional. Pause button is mainly intended to show on the map that you took a break. It will still record your mileage, wheel data and track. In addition, when you are "paused", if you turn off the wheel without disconnecting, you won't get connection lost beeps. If you want to stop tour recording, just finish it. Soon I'll implement tour segments, currently it's not working (regardless of setting, new tour is started).
  10. It's common to protect aluminium sheets and heatsinks with plastic foil. So it could be a small strip of such foil that unnoticed left bounded to the heatsink plate. To be honest, I don't know and I don't believe it's the case. And I admit that I may be wrong, but I don't think it's a residue of protective foil from silicone thermal sheet. I've been using this kind of thermal insulation for years and never received from the supplier with any kind of foil or paper. Of course there are thermal sheets that are protected with foil. But this usually applies to gel or rubbery, elastic (usually white, blue or rose) sheets that is somewhat adhesive by itself and need to be protected from dust etc.
  11. In general it's a bad design practice to keep heatsink at any electrical potential. It's also common that low-side MOSFET drains are not connected together and directly to the negative battery terminal, but there are separate shunt resistors to measure phase current. Also I wouldn't blame silicone insulating sheets as they're very goot thermal conductors. Not as good as thermal silicone paste, but difference is not important here.
  12. You can't use paste in this case, because metal tab of each MOSFET is electrically connected with center pin (so called "drain"). You can also notice a plastic insulation sleeves used to insulate thermal tab from the screw (that is electrically connected to the radiator). This type of insulation thermal sheets is not adhesive and there is no additional paper or foil.
  13. You're right. It also seems that there is no temperature probe near the radiator or MOSFETs. This is a major design flaw, as PCB temperature where temp probe is apparently located in Nikola, being additionally cooled by the fan located on wrong side, doesn't reflect MOSFET tab or package temperature. This is why @Marty Backe got misleading, very low temperature readings. For example, in KS-18L/XL there is a temperature probe located close to the heatsink and MOSFET that is farthest from the cooling fan. This is why L/XL may be perceived as a "hot running wheel". Nikola wasn't "cold running wheel", it was just a "very hot running wheel with low temp readings". From what I see, PCB design may cause MOSFET source (S) leg to overheat, as there is highest thermal resistance due to small copper pad directly under the MOSFET leg. I don't see the other side, but i assume it's similar so drain (D) legs are also connected using small pad located on an edge of larger copper plane. Another design flaw is to use two TO-220 MOSFET instead of one TO-247. Doubled small package design is prone to many failures. MOSFET leg fracture during bending or PCB assembly will increase leg resistance. Improper soldering or improper PCB design may cause current imbalance, so it wont be divided 50/50 between both transistors. And if one MOSFET will fail, but won't short, second MOSFET failure is a matter of short time, as it takes over full current instead of part of it. As we can see in the photo, it was the case. Failed both MOSFETs on one side of a motor phase half-bridge circuit. Double MOSFET design may work well only if is properly oversided, so each single MOSFET is able to carry maximum current expected to flow in the motor phase circuit. But as failing MOSFET will likely create a short circuit, secondary MOSFET won't be beneficial.
×
×
  • Create New...