Jump to content

Jason (ABRP)

Administrators
  • Content Count

    836
  • Joined

  • Last visited

  • Days Won

    74

Jason (ABRP) last won the day on May 27

Jason (ABRP) had the most liked content!

Community Reputation

105 Excellent

2 Followers

Recent Profile Visitors

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

  1. Turns out that was a lie, rewrote my_abrp quite substantially to make it easier to handle per-car differences like shifter position or methods to determine if a car is on or not. On which note, is there any PID for the Kona / Niro which gives shifter position? Looking for something I can use to reliably determine if you're driving the car.
  2. At the moment I don't have anything planned, but I plan to do some of my own driving and charging, so if I find any bugs I may update.
  3. I'll let you know when it's just about ready to test!
  4. I just got that version yesterday evening, haven't driven my car in a while so had to actually turn it on for a bit to get the AutoPi to take the update. Annoying that jobs seem to be prevented from running while it's staging the update. I'll be taking it for a drive today, have to get groceries, so will see how everything performs now on the new update.
  5. I have an idea on this, when I thought it was possibly a "zombie" copy of the script running I introduced an auto-quit call in the manage_sleep function. This would cause the ABRP script to potentially miss a lot of data in the period where the charge is ending, as it's dying and restarting multiple times (intentionally). I've since reverted that change since it didn't do anything useful. Does your current version of the script have: else: # Kill script, gives us 60 seconds to wait and check again. safelog("Car not active, retrying in 60 seconds", always=True) os._exit(1) At line 206-209? If so, update to the most recent version from the GitHub. I really need AutoPi to come up with a better way to share user scripts so you get notified when I update. If we have to we'll build something into the ABRP app. If not I'll need to think on it more.
  6. You read our minds! This is coming soon.
  7. We really like this idea too, it's on our to-do list! Really helpful for caravanning road trips with friends.
  8. When you say you saw the power go from 2.2kW to 0kW, where did you see that? In ABRP or in AutoPi's interface, or somewhere else?
  9. Huh, interesting, if the last charge rate was 2.2kW, it should have stayed awake. What did the log on the AutoPi say about why it went to sleep? Perhaps a critical power event, 12V battery voltage got too low? My Autopi > Advanced > Events
  10. Ah, is this with the most recent version of the script where I cut off the is_charging marker at 0.5kW to avoid phantom charge events? Bet there's some very low power battery conditioning still going on, so it should probably stay awake for a little longer to catch the tail end of that. I've pushed a new version of the script which lowers the sleep tolerance to 0.01kW, or you can just change line 202 from: if 'power' in data and round(data['power']) != 0: To: if 'power' in data and abs(data['power']) > 0.01: Which will have the same effect.
  11. Sounds great! I think the first order of business is for us to expand our poller so we can easily incorporate additional manufacturer methods like BlueLinky. As far as parameters which can be retrieved - if we have SoC only that's workable. It'll take a long time to calibrate correctly though. Calibration is much faster if we can get Power data from the battery pack (input/output) and much more accurate we've found. Of course, if it's not possible, that's a limitation we'll have to deal with.
  12. Yes, we've been talking about how to best link, once we get through that I'll post an update.
  13. We don't have an easy way to delete them outright, but if you're concerned about having them stored you could set them to an arbitrary other location.
  14. Interesting that it offers that as an option. As far as we know, the Tesla app can't open ABRP links. To forward a destination to your Tesla you'll need to connect MyTesla and then use the "Send to MyTesla" button in Driving Mode (so we can figure out what the next destination is).
  15. That'd be great! We actually have a system set up to poll APIs, as you mentioned for the Tesla logins. It was designed to be easily expandable once we gain enough knowledge about another API. The main things we'd need from the API to make it useful to you (in order of importance): SoC Speed Lat/Lon Power Any other data about the car's status (health, temperature, voltage, current, etc) If we can get those things relatively frequently, we can make a really good tool! Of course, once we find enough about the API to start building, we'd need someone with an actual Hyundai to help us out so we can test the telemetry calls out.

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...