ABRP for charging monitoring

[Jojo]

Some guys created an app for EVs without online access (Kona, e-Niro) called EV-Notify, to monitor charging. Using a secondary phone in the car it builds a bridge between OBD dongle and a server to monitor charging and to get notifications on a primary phone. Due to expected access problems of two apps (EV-Notify and Torque) to the OBD Dongle, we cannot use ABRP and EV-Notify at the same time.

Description: Implementation of charging monitoring and notification within ABRP. 

Use Case: Travelling with a planned route using ABRP with a the primary phone. A secondary phone running Torque keeps uploading current SOC from OBD dongle to ABRP server. Primary phone acquires those date from server for use of dynamic planning adjustment and monitoring of SOC during charging brakes. Notification about SOC can be set manually or will be pushed automatically according to the SOC defined by the routeplanner to leave the charger. 

Thanks

[Jojo]

Add1: Recognized new feature "View Live data". First step is already made.

Notification would be great in addition.

Thanks

 

[Shidar]

ABRP is basically a Routeplanner. But you can take your phone with you and always watch the SoC.

[Bo-ABRP]

On 1/12/2019 at 5:59 PM, Jojo said:

Add1: Recognized new feature "View Live data". First step is already made.

Notification would be great in addition.

Thanks

 

Ah, I see. So basically you'd want a popup or something saying "Charging almost done?"

[Jojo]

Yes, a popup. If you mean something like an android system popup. Otherwise an email for example. Something that notifies me during my charging brake, drinking coffee, waiting on SOC reaches the value that is defined by ABRP planning for that specific stop.

Notification rings, finish coffee, go out to the car and drive on according to plan.

Thanks

 

 

 

[Bo-ABRP]

Yes, we could definitively do this - all technical functionality is there. I'll add it to our TODO feature list!

[Jojo]

Great, thanks.

[Jojo]

Hello

Maybe to finetune my request.

Could we have some check boxes behind the depart charge to request notification for that stop. General selection for all stops at the top and single check boxes for each stop.

Hover over description "SOC notification, if your car provides real time online data"

I think you have to put some effort in the triggering conditions. My first thought would be to use the GPS position of the charger. If ABRP planner detect GPS within 50m around the charger, the car is charging and it provides online data, than it should send notification (Popup, Email...).

Thank

 

[K1000]

On 1/17/2019 at 2:15 PM, Bo (ABRP) said:

Yes, we could definitively do this - all technical functionality is there. I'll add it to our TODO feature list!

With my e-Niro, EVnotify can retrieve data from the OBD even when the car is turned off, while Torque stops receiving information shortly after the car is turned off. So it might not be sufficient to include the charging supervision in ABRP, but a change in Torque is probably necessary as well. I guess that there must be some kind of command to be send via Bluetooth to the dongle in order to keep it alive, even after turning off the car.

Edited March 4, 2019 by K1000

[Jason-ABRP]

Probably the better solution is to work with EVNotify to see if they'll support sending us data. Easier to set up than Torque as well.  I've sent them an email, we'll see if anything comes of that.

Just so I understand the setup, you have EVNotify installed on two phones? One to stay in the car, one to take with you? And they send each other data so you know when you've reached your desired charge?

If we did end up collaborating with EVNotify, what features would you like to see, what data shared between us?

[K1000]

On 3/4/2019 at 5:02 PM, Jason (ABRP) said:

Probably the better solution is to work with EVNotify to see if they'll support sending us data. Easier to set up than Torque as well.  I've sent them an email, we'll see if anything comes of that.

Just so I understand the setup, you have EVNotify installed on two phones? One to stay in the car, one to take with you? And they send each other data so you know when you've reached your desired charge?

If we did end up collaborating with EVNotify, what features would you like to see, what data shared between us?

To my understanding EVnotify is one-way. The App on the mobile in the car reads OBD2 data and regularly updates a server somewhere in the cloud. By the same App on a second mobile you can retrieve the information from that server and receive alerts, i.a. if the server detects an unexpected end of charging, if it does not receive any data for a certain time, or if a predefined level of charging is reached.

I could imagine that the part in the car could be done via Torque as well. This would avoid changing the App and the bluetooth connection between driving and charging. Visualising the charge status in ABRP would be fine, but could as well be done via EVnotify as today.

The essential issue is to avoid switching the App and  reconnecting the BT dongle each time you switch from driving to charging and back.

Having a different App (on the second mobile) to remotly supervise charging is not an issue. 

This said, I could imagine that Torque sends data to ABRP as it does today (perhaps additional data if needed by EVnotify), and ABRP forwards relevant data to the EVnotify server including the identification of the user (ideally the same user name or email for both). Than the EVnotify app could continue, as today, to remotly show the status and receive alarms. For EVnotify this would mean "no change" as long as ABRP could provide data in the same format to the server as EVnotify does it with its own App.

By duing it that way, it would still be possible to use EVotify the same way as today, by having an additional input channel to the server via ABRP.

One essential thing is that Torque needs to continue retreiving data from OBD2 and sending it out when the car is turned off (during charging). I am not sure that Torque keeps the dongle awake, when the car is off.

Of course, the other way around would also be possible. Asking EVnotify to retreive relevant OBD data during driving and transmitting it to ABRP, either directly as Torque does, or by forwarding it from the EVnotify server. In that cas the "in car interface" would be EVnotify and not Torque. But this would mean that EVnotify has to change a lot.