Jump to content

Ou Boet

Members
  • Content Count

    27
  • Joined

  • Last visited

  • Days Won

    1

Ou Boet last won the day on March 16

Ou Boet had the most liked content!

Community Reputation

1 Neutral

Recent Profile Visitors

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

  1. Might be better to just leave out a standard driver weight because that will vary widely, and let users enter a value. That, or clearly state that 75kg is assumed.
  2. I have noticed that when entering a tunnel ABRP will loose it's GPS fix and note that "you're not on the route" and the pointer does not advance (obviously). Is there a way for ABRP to obtain secondary speed information through the the OBD port to avoid this. That way it doesn't have to recalculate once it reestablishes a GPS fix when you exit. Once other thing, because I get to use HOV lanes which have me deviate off the indicated route a short distance before rejoining, ABRP thinks that I've detoured and recalculates and then recalculates again when I rejoin. I'd like an option to delay the recalculation longer, or perhaps dismiss it if possible.
  3. To confirm, that is only true for premium members right?
  4. Not sure I fully understand the question/comment above, but just to clarify. The 28 kWh IONIQ can charge at up to 69 kW. The 38 kWh IONIQ can charge at up to 44 kW. Additionally, the 38 kWh IONIQ tapers earlier in the charge cycle. This means that in some instances, the 28 kWh IONIQ can complete a long trip a little faster than the 38 kWh IONIQ, as indicated above. The 28 kWh IONIQ is 16 min faster but with one extra stop.
  5. Green = less energy used than planned. Red = More energy used than planned.
  6. I would like it too.
  7. BACKGROUND_MODE did the trick. Thanks a million.
  8. Fwiw, I disabled "Location synchronisation" in EVNotify and told ABRP to "Overide car position". That worked for the GPS tracker on ABRP. But after about 10 mins, it still stopped updating SoC data from EVNotify. Again the old switch back and forth fixed it - for a while. Just accessed the dark side and enabled background mode as suggested above. Will test on the way home. Thanks for the help. Btw, what is SEXY_DASHBOARD
  9. I did a bit more testing last night on the way home from work. It appears that that when EVNotify is not dispayed, it stops uploading after a short while. This I concluded when I noticed that when I do display it, it displays outdated information for a split second before refreshing. Not sure if that's conclusive though. There are no holes in the data though after a switch back and forth, in EVNotify or ABRP, even if I leave ABRP displayed for a long period and it gets "lost", as soon as I do an EVNotify switch, it seems to have all the past data correct once it updates. Very weird. I will look for the "run in background" setting in EVNotify, I don't think I recall seeing that, so it's unlikely I've activated it. Thanks for the tip.
  10. Description: During a trip, ABRP repeatedly lost connection with EVnotify Type: ABRP v 4.0.6 Android (I updated to this latest version immediately before the trip) Link to Plan: N/A Replication Steps: Start EVnotify and confirm that it's reading info from OBD II dongle and uploading to the web Start ABRP and plan a route. Start route and track progress. After a minute or two, the GPS location stops updating the the SoC % stops updating. Switch to EVnotify and switch back to ABRP. ABRP now shows vehicle location correctly and SoC% is updated and correct. Continue to track route. Loop back to step 4. I hope that this issue can be resolved quickly. I really am enjoying the new app and layout. But switching back and forth is a pain in the a*** and a distraction. OB
  11. Ok, did a test charge this weekend in the cold - ambient a ball hair above freezing with high winds. Managed a consistent 45kW (from a 50 kW machine). Battery temp started at about 14 Deg C and peaked at 30 Deg C at the end. Took the vehicle from about 20% to 83 % SoC in a smidge less than 25 mins. Think I'll do another test at a higher powered unit next weekend (if I can find one that isn't Electrify Canada). Looks like my previous experience may have been down to the DCFC unit and not a cold battery.
  12. The 25 deg C was a number that was reported on a forum. On the day I did my charge, ambient temps were around freezing and the battery was cold soaked before driving. I don't have exact temp data because I didn't have my OBD scanner with me, but based on similar drives at ambient similar temps, I estimate my battery would have been about 10 deg C when I charged it. Once things warm up, I'll see if I can do some testing and find the break point.
  13. I've noticed that my 28 kWh IONIQ will throttle DCFC charging speeds unless the battery is warm (>25 Deg C). Did a charge the other day and only managed 37 kW right up to 80%. If the App is working out charging duration based on a warm battery when it's cold outside, it will under estimate by about half. Apart from spending more time stationary, it's also a problem when estimating cost for those networks (Electrify America/Canada) that charge by time and not the amount of energy delivered. The 38 kWh IONIQ is less severely affected by the cold since it never charges at more than 45 kW anyway.
  14. I think that you can easily achieve something similar by reducing your % arrival and % leave limits.

Contact Us

Bo - Lead Developer and Tesla owner: bo@abetterrouteplanner.com

Jason - New Car Models, Developer and Bolt owner : jason@abetterrouteplanner.com

Idreams - Forums Administrator, Forums Developer and Tesla owner : idreams@abetterrouteplanner.com

×
×
  • Create New...