Jump to content

Lance Pickup

Members
  • Posts

    4
  • Joined

  • Last visited

Reputation

2 Neutral
  1. Whoa! I hadn't even considered using an OBD2 link (too used to not needing it in the Tesla). I called up my sister and got my OBD2 dongle out of the LEAF that I sold her (she didn't even know it was there, even though I told her what it was for at the time!), plugged it into the ID.4, and after some relatively simple setup and linking EVNotify and ABRP, it seems to work GREAT! Even though we haven't actually headed out on our trip yet (we leave in a few hours), the live data in ABRP is working great (we were charging the car at the time, and this is clearly shown in ABRP). Mind is blown. Very nice job on this integration. Looking forward to seeing how this all works on the trip, but no doubt this is a game changer compared to the previous trip we took. This trip will be quite an adventure...over 1800 miles and going through a few areas that frankly are quite underserved in terms of charging stations.
  2. It looks like you forced the plan to have you charge for 1h00m at the Supercharger. Normally you wouldn't do this. If you have a desire to stop at that specific Supercharger (versus just accept whatever plan ABRP gives you), then you can click on the Supercharger and then Add Waypoint (you've already done this part). If then you know you want to stay for an hour at that stop, use the Add a stop around this waypoint pulldown to state how long you will be there. I just did this and it appeared to work properly: I suspect that you may have run into a bug of some kind resulting from trying to "force" the charging at a Supercharger. Instead, let ABRP do that calculation for you, and use the other method to state your intention to stop at the Supercharger for an hour. If you aren't trying to stop for a particular amount of time, don't actually specify any charging speed or time and just let ABRP figure out how long you need to stop for.
  3. Hi Larry, not sure this is the proper thread for your question (it seems like a standalone question), but I too have noticed this today. It seems like the site is a bit glitchy today and it is not finding viable routes and is highlighting those charging stops where it thinks you are having to limit your travel speed to make it to the destination. The thing is it appears to be skipping many valid Supercharger stops en route. I don't know if this is the case here (it actually doesn't seem like it with only 106 and 108 mile legs), but that's what I've noticed today. I would advise sanity checking ABRP's recommendations with the car's nav system.
  4. Avid ABRP fan here. I use it religiously with my Tesla Model 3 on road trips and feel confident in its use with my Tesla. However, we took my wife's new ID.4 on a recent trip and it left me wondering about best practices in vehicles that do not support live data feeds (specifically SOC) while en route. I have gotten used to monitoring the original predicted vs. current predicted arrival SOC. The ID.4 does not appear to support live data feeds (via Tronity), at least in the US, at this time. I found that while in the app, the live en route display shows Planned SOC and Current SOC, and has up/down arrows around the Current SOC to adjust the current SOC manually. In my head, this provides the desired functionality I have with my Tesla, albeit manually entered. But there are a few problems. First, adjusting the Current SOC one percent at a time is very cumbersome. For a variety of reasons, the Current SOC is usually way off--either due to a bug or non-ideal functionality of the app with respect to the Planned SOC (sometimes the Planned SOC just makes no sense--i.e. sometimes it uses the live SOC from my Tesla for example, even though I have the car set to ID.4) meaning I have to hit the up/down arrow many, many times to get the correct SOC entered (I wish I could just click on the number and enter the SOC using my keypad). Second though, adjusting the Current SOC doesn't seem to have the expected effect of re-calculating the arrival SOC. I see the current SOC number going up to what I am setting it to in the elevation/trip graph (although it doesn't rescale the display, so the number just disappears off the top of the graph), but the arrival SOC doesn't change--and that's ultimately what I'm looking to see. And as soon as I hit the Replan button, it goes back to the original Planned SOC value. I've found the only reliable way to do this is to go back to the settings, manually enter the Current SOC into the Starting SOC, and replan a new route from the Current Position to the original destination. This works, but is fairly workload heavy, and I have to believe that the intent is that there is an easier way to do this. Ideally, it would work a lot like how it does in my Tesla with a live data feed. That is, during the trip, as my Current SOC drifts from the Planned SOC, the graph shows a second line with the updated estimate and estimated arrival SOC. Am I not using the app as intended in this situation? Is there a better way?
×
×
  • Create New...