Jump to content

Bo-ABRP

Administrators
  • Posts

    215
  • Joined

  • Last visited

  • Days Won

    24

Bo-ABRP last won the day on August 5

Bo-ABRP had the most liked content!

Reputation

32 Excellent

1 Follower

Recent Profile Visitors

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

  1. Since a release or two, iOS before 13.2 does not seem to work with the app - probably a change when we upgraded to the latest Apple developer tools, Xcode. Unfortunately iPhone 6 does does not receive upgrades beyond iOS 12, and in the next release we will mark the ABRP app to require 13.2. As for iOS 15.0 we are not aware of the issue. Does it crash for you on a fresh install even without logging in or selecting any particular settings?
  2. It's not available for a couple of days, it takes some time to get through the review process. Version will be 4.0.56.
  3. Great bug report - the "it does not happen on the phone screen" helped us find it. A new version is on the way to Apple which fixes it.
  4. Bo-ABRP

    App crashing

    Really sorry about this! Our quality control slipped for this (urgent) release - 4.0.55 is in for urgent review with Apple, hope it gets through tonight.
  5. We have seen this issue a couple of times this summer; due to the renovation of Skurubron, the OpenStreetMap data has been wrong/broken so that routing via it has appeared impossible. This has been resolved in the latest version of our maps it seems (we update every Sunday for non-realtime-traffic).
  6. This must have been due to a corrupt realtime traffic map at that time - the issue has been corrected now (it works as it should when I try now). Thanks for letting us know!
  7. We just released a refactored integration with both Tesla and Tronity today as our old solution was way overloaded with all the vehicles connected now. This will lead to much more frequent updates from Tronity too - let us know how it works!
  8. We had no personal data at all in that database, so we would have to assume that that password reset email was a coincidence. If you want we can investigate the logs for you and see what/who triggered it?
  9. Yesterday (April 20th 2021) we became aware that one of our development servers - not used for the public ABRP service - had been attacked by somebody who deleted data from one of the databases and requested a ransom to give it back, or else expose it. The test database was exposed due to a human mistake. The data in the database consisted of randomly selected anonymous vehicle live data recordings. The data was collected from actual drives or charging sessions, and contains location, speed, SoC, power, weather data and car model. The leaked data does NOT contain any personal data - only pure, anonymous vehicle data. It does NOT contain any names, vehicle identity numbers, credit card numbers, passwords, e-mail addresses, live data tokens (from e.g. Tesla) or anything else that could cause damage if published. ABRP takes your privacy and data security very seriously. We have designed our systems and databases in a way to minimize risk and damage in case of, e.g. a hacker attack. Our production servers (used for our public service) are protected in the best way we can with very restricted access. We have taken and will continue to take necessary actions to make sure this does not happen again. Bo and the ABRP team
  10. Sorry for the slow response! This turns out to be a bug/feature due to the charger max SoC limit. This has now been fixed, and your plan runs well. Thanks for reporting!
  11. Now there is an official beta program for Android over at Google Play. If you want to test the new upcoming release for us, just sign up and enjoy it already! (Voice navigation, further improved driving mode, MyTesla MFA and many other small goodies)
  12. Thanks for reporting! We use Bugsnag to catch all crashes, which is extremely useful for us. This also means leaving "breadcrumbs", which in our case means all pages visited in the app so we can see the sequence of events until a crash. We don't track anything else there. Anyhow, it should of course not make things slow! What platform is this - browser or app? Is it reproducible?
  13. Spot on! Chipley only has 50 kW chargers, and that means that the charger limits power instead of your battery up to a certain SoC. Most chargers are built so that they actually do not limit power but instead current, in this case 125A. Your battery will have slightly higher voltage at higher SoC and voltage x current = power so charging with a fixed current at higher SoC will actually give you more power. In these cases the difference is probably on the order of seconds or at most a minute, but the planner does not care - it looks for the fastest trip.
  14. Thank you for this feedback - the issue has been found and fixed! Technically, we the planner is an optimizer which optimizes a cost. The cost is usually total trip time, but we modify the cost to weigh in preferences and risks. This means that the total trip time may not always be minimized since other factors do play a role. In this case, the bug was that we calculated the number of stalls completely wrong, which made Target look like a risky choice. When you add the charger as a waypoint, we ignore that risk. Now corrected!
  15. Really sorry about this - we have an ongoing case with our subscription provider Chargebee on it. They are still developing support for GPay on their side and have enabled it by mistake for us. So basically, it will probably be removed as an option today to later re-appear when they have properly implemented it.
×
×
  • Create New...