Jump to content

Search the Community

Showing results for tags 'odb'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • General Discussion
    • Introductions
    • Trip Reports
    • Planning Lounge
    • Discussion
    • Site Feedback
  • ABRP Feedback
    • Report bug in the ABRP Bug tracker
    • Request a feature in the ABRP bugtracker
    • (Old) Bugs - Use ABRP bugtracker instead
    • (Old) Features - use ABRP bug tracker instead
    • Community Support
    • Vehicle Model Discussions
    • ABRP app
  • Electric Vehicles
    • Tesla
    • BMW
    • Chevrolet
    • Hyundai
    • Jaguar
    • Kia
    • Lucid
    • Nissan
    • Porsche
    • Renault
    • Rivian
    • ŠKODA
    • Volkswagen
    • Polestar


  • ABRP Blog

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



About Me

Found 2 results

  1. Any recommendations on WIFI/Bluetooth OBD dangles? Also do these OBD dangles work directly with the new IOS and Android apps of ABRD, or do they need to have and intermediate apps such a Torque Pro? Thank you for any advice.
  2. Description: Integration of ABRP with autopi device to provide OBD data directly to the application. Use Case: Autopi is a powerful hardware platform with many possibilities to benefit the EV driver and is available with or without cellular (4G) connection. Purchasing without the cellular dongle is appealing due to the lower outlay for the hardware and contract for the SIM. Having ABRP query the OBD data directly (over port 35000 for example) would remove the need to have the data upload to ABRP's servers via a cellular connection. This is beneficial as cellular connections are typically patchy in the locations where you most need them (such as planning an unexpected recharge-stop). The existing use-case is as follows: - Torque Pro or EV Notify ("the app") queries the OBD device either over BT or WiFi. The app then sends the data through the API to ABRP's servers. ABRP then downloads that data to create a dynamic overview of the battery SoC, temp, SoH... In the proposed sutuation the autopi device would become the AP (or hotspot if cellular is needed/enabled) with the phone/tablet running ABRP and querying the autopi device for OBD data. If needed, the phone/tablet could instead be specified as the network gateway to provide a route to the internet, etc. Additionally, upload of the OBD data to ABRP's servers could also be enabled, probably directly from the autopi too, if needed. Additionally, autopi may also be able to provide logging facilities (for OBD data or trip data from ABRP) as a local point of reference for users. Hopefully this makes sense.
  • Create New...