Jump to content

Jason (ABRP)

Administrators
  • Content Count

    923
  • Joined

  • Last visited

  • Days Won

    89

Everything posted by Jason (ABRP)

  1. Hmm, strange, we rely on power data from LeafSpy for the calibration, but I thought that was added quite a few versions ago. Did LeafSpy have an update recently?
  2. Glad to hear it's working as intended now! And to avoid sleep management, don't even need to remove the manage_sleep function itself, just where it's called on the second line you quoted. I also just pushed a version that adds a 0.1kW power tolerance on the sleep function, only keeps you awake if you have >= 0.1kW power.
  3. Jason (ABRP)

    Trip chart

    This is a little complicated to do, but we're working on it!
  4. Nice! Saw this and got all ready to fix the LeafSpy API, glad it was an easy fix on his side. We used to return status:0, not sure when we changed that.
  5. Jason (ABRP)

    Time zone bug

    This bug is now on our priority backlog, so expect it fixed soon!
  6. This is probably a problem with the Open Street Map there, if you click on the route you should see an "edit in Open Street Map" button: Where you can make sure it's showing it properly as a split-lane highway, and submit edits to have it done properly.
  7. Wellp, I made a dumb error. Generic is_driving() always returned false for you, so yeah, it'd basically go to sleep and never report in. I upgraded the generic 'is_driving' function so it's a little smarter than that, so hopefully it works as expected now. I also merged it into the service branch, so feel free to grab either version and give it a try.
  8. I'll take it! Or if easier, just pick out the commit on Github with the most recent working version: https://github.com/iternio/autopi-link/commits/master And I'll work it out from there.
  9. The Bolt's MyChevy App can display all the kinds of information we want to for ABRP, so it's not impossible. They do have some more leverage, as they're also the ones installing AA in their cars.
  10. I think we also need to have that toggle on the map like in other mapping applications, instead of hidden on a difficult-to-parse 'Modes' button. I've added both to our to-do list.
  11. That's really weird, I just took my Bolt for a camping trip with the AutoPi and it worked really well. That would imply that the problem is somewhere in the HKMC-specific code. Wish I had one on-hand to test with. Don't suppose anyone is in Houston with one so I can test directly? Either way I'll take some time and see if I can figure out what's going on. Great! Will probably need to tinker with the CAN recording mode to figure out the PIDs. I've also heard that the E-Tron has a system which sets the alarm something tries to access the OBD while it's locked and off, might have to figure out how to turn that off.
  12. That's may be by design, actually. To avoid using more data then we need, I have it only send data in when it's different from the last measurement, or if enough time has elapsed to keep the data marked 'fresh' in the app. That's minimum every 30 seconds while driving, or every 60 seconds while charging. Of course, it should send much more frequently when the data is actually changing (IE while on the road). If you want to get rid of this in your copy of the script to see if that resolves your issue just change these lines to a much smaller timeout value (or 0): https://github.com/iternio/autopi-link/blob/master/my_abrp.py#L102-L106
  13. I added install instructions to the "service" branch, let me know if I missed anything: https://github.com/iternio/autopi-link/tree/service It does start up ~10 seconds faster. If it doesn't work right, try setting debug to true and that'll give you some extra logs when it starts up. You'll probably also have to power cycle the AutoPi once it's sync'd to get the script to start. Edit: For what it's worth, the most recent version of the script starts up just fine on my AutoPi.
  14. This is something we're tracking, and will implement next time we work on the map styling.
  15. That's a very good point, I don't use that toggle much, so it escaped my notice. It doesn't even follow the design scheme we use on other toggles like that, where we put a bright checkmark on the button, we'll get that brought in line!
  16. Ah, it may also be that we don't get much data from the Zoe via EVNotify, since (if I recall) it has limited support. Would you email me (jason@abetterrouteplanner.com) with your account details so I can take a closer look, and at least get the app working better with limited data?
  17. You can dismiss the recalculation by tapping the countdown, and for some vehicles we do have an OBD PID which provides speed, but we don't use that to estimate where you'll be in the future, though we can certainly think about it as a future improvement.
  18. Could you post a link to the chargers (click on the charger, click share) so I can take a look? We're aware of an issue with out-of-date information coming from Plugsurfing, and we're looking into a solution, although if those are from a different source I'd like to investigate there too.
  19. Very good! For future reference, if you run into this again you can go and override all of those settings manually until you can get updated Live Data from the car. You can turn all the Live Data settings off in bulk by untoggling "Automatic Settings", although this will also turn off Live Weather and Traffic if you are subscribed to Premium.
  20. It's something pesky we haven't solved yet, and annoys me too as it does it on my device as well.
  21. Hmm, probably a bug with our notification system, I haven't seen this show up on Android, so must be specific to iOS, we'll check it out and get it fixed.
  22. Mainly because we forgot to implement this. I'll get it in the next release!
  23. We have three levels of car model confidence which we use to label the cars in the planner: Alpha - Modeled manually by us, these are generally closely matched to the EPA and WLTP range provided by the manufacturer, but won't be a perfect representation of the car. Beta - Modeled based on some real-world data. Release (no label) - Modeled based entirely on real-world data. Live Data To move a model out of Alpha, we need real-world data, and that's where you come in! The best way to get that real-world data is to use a Live Data connection. The first step there is to check your car against our list of Live Data Support and see if it's already supported. If so, great! Set up Live Data, and once we have enough data we'll promote the model from Alpha. Of course, setting up Live Data also has a ton of benefits for you as a driver as well: We do live calibration of your personal car and account for things like extra passengers, cargo boxes, bikes, and weather automatically You get a live graph and arrival predictions of state of charge while in Driving Mode You get completion estimates while charging and can see charging status And of course, if we don't currently support your car, but you know how to get data from your car we provide an API to connect Live Data with us. Send us an email at info@abetterrouteplanner.com if you'd like more information about this, and our API Docs are available on our Postman. Testing Procedure If we don't have Live Data support for your car, the other option is using the Trip Odometer. We've prepared a test procedure document you can print out and fill in to provide this data. See the attached "Manual Car Calibration" document. The goal here is to provide a series of data points at a variety of speeds to estimate the efficiency across all speeds. With many tests on different copies of the same car, we can produce a reliable model. Manual Car Calibration.pdf
  24. Soon enough you won't even need to input the weight of the trailer, as we're figuring out how to calibrate that directly (and hopefully get a much more accurate read on the weight!). We did miss a few places to set the configuration when picking the car model in the original release of the vehicle configurations, and that should be fixed in the next version. Let us know if we missed any! I wouldn't worry too much about 'polluting' the vehicle configuration with the wrong data, it adjusts quite quickly to data that doesn't match, so within 5-10 minutes of swapping back to the trailer config you'll have fixed the calibration. One interesting side note, the little three-part bar graph is a view of your calibration confidence: You can see this detailed view by going to the car details and tapping on the bar graph, but it gives a quick visual representation of how confident the calibration is. As far as the notification badge, is that on iOS or Android? I can't say I've seen it do that before, so I'll have to investigate a bit.
  25. Easy enough! Amused I never ran into that with my Bolt.

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