Jump to content

TomTomZoe

Members
  • Posts

    180
  • Joined

  • Last visited

  • Days Won

    11

TomTomZoe last won the day on September 20

TomTomZoe had the most liked content!

Reputation

23 Excellent

Recent Profile Visitors

770 profile views
  1. @eyeballs Have you already tried to reset the complete route by button, close and restart the app/website? Maybe this can help.
  2. @Chris Yoder It seems to be the same issue like reported here
  3. Description: If you charge beyond the intended SOC charge level, the forecast charge remains at "1 min to xx%". In the graphic, some time information is then given as "Invalid Date". Type: ABRP APP V4.0.50 Replication Steps: Create a route with a charging point Start routing and drive to this charging point Charge beyond the departure SOC @Katya-ABRP Perhaps the time until the departure SOC should no longer be specified once the departure SOC has been reached. I cannot currently think of any other meaningful output of a time specification for this case. However, the current SOC and the current charging power should be displayed while charging continues. In my example the intended departure SOC was 84%.
  4. @spiceagent11@Axeman Meanwhile there’s an option to choose routing alogorithm called “Charging stops”: You can choose between Fewer stops - quickest arrival - shorter legs
  5. @Katya-ABRP Only the straight ahead route instruction is light gray, all other route instructions ae still blue. Is this intended or a bug?
  6. @Wolfgang All options always relate to all locations of a network, not to a single location 🙂 Few months ago I made the translation into German more understandable, if you have a suggestion for a better term, please tell me.
  7. The new Chevrolet Bolt MY2022 and the Chevrolet Bolt EUV MY2022 have a slightly smaller battery: Instead of 66kWh since MY2020 they have only 65kWh capacity beginning in MY2022. @Katya-ABRP Can ABRP create a new Bolt EV car model for Bolt 2022 version? Second request: Due to the safety recall for all ever built Bolts EV/EUV (and also Opel Ampera-e) all built Ampera-e (and also older Bolt EVs) will get the new version of the Bolt EV/EUV MY2022 battery with 65KWh capacity. The replacement will start in a few weeks/months. Can ABRP already create an additional car model with foresight for the Ampera-e with the new 65kWh batterie? (At the moment all Ampera-e have 60kWh capacity.) This would be very nice. 🙂
  8. This seems to be the reason: MG Battery State of Charge,"SoC","","LOOKUP(1.1*(VAL{MG Battery State of Charge RAW}+VAL{XX_BMS_Version_SoC _Factor})::10~0=0:100~110=100)",0,100,"%","","","",1 I think Torque Pro transfers SOC instead of SOC RAW to the ABRP Webserver: SOC is approximatly 10% higher than SOC RAW. I would be happy if that is the solution 🙂
  9. @Bluecruiser Depending of the car Torque Pro knows different SOCs: Cockpit SOC, gross SOC, net SOC, ... Which car do you own? Is it the MG ZS EV? Do you use these OBD PIDs? There are two different SOCs available for MG ZS EV: MG Battery State of Charge RAW,"SoC Raw" MG Battery State of Charge,"SoC" There is no communication directly on the same device between Torque Pro and ABRP. Communication is only possible via the ABRP web server. You have to make sure that the correct SOC is transmitted from Torque Pro to the ABRP web server, so that ABRP App can receive the correct SOC for range calculation. I hope this can help you 🙂
  10. @Katya-ABRP It seems this is the same issue like mentioned here.
  11. TomTomZoe

    iWatch

    Have you already tried to remove both ABRP app on iPhone and also on Apple Watch and reinstall both? Maybe this could help.
  12. @Katya-ABRP I also have this strange behaviour on every route I drive. Using iPhone 11 Pro with ABRP App 4.0.49 and CarPlay. I try to record this phenomenon with a second smartphone. 😉
  13. Meanwhile it is fixed, tested with version 4.0.49. Thank you very much!
  14. Unfortunatly not yet fixed half a year later with version 4.0.49 😐 @Katya-ABRP Is this issue on the todo list?
  15. @Katya-ABRP Here is an example with version 4.0.49 where the issue seems to be solved, it is showing 13km distance.
×
×
  • Create New...