Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Hans2183]

Just pushed an update to the app store with the first version with OBDII connection integrated. The screenshot is from development but with actual data from my bike. Also tested with a real connection.



It's all very rough at this point. The Android version has evolved quite a bit including background services running and pushing data to https://ev-monitor.com. Those features will slowly make their way into this app also. For now you can connect and retrieve the current values by pressing the center blue button.

So if you just want to know current battery temp this will work. I'll add the charge speed and charge state flag later on in one of the updates. The app is still pending approval but if you become a pilot you can already download it.

Android version https://play.google.com/store/apps/details?id=be.hcpl.android.emapp
iOS version https://apps.apple.com/app/id1559468042?fbclid=IwAR262m6qf-x368mweND2HjopkhEq3U1-6v_dn53QNmpnOawGAk8c7X-KXjE

I'll probably skip the Energica BLE connection all together for this app. It was fun working my way around the "security" but there is no extra data, in fact there is less. The only benefit of the Energica BLE connection (besides the fun of making it work better than the original app) is that you don't need to plug in an OBD dongle. It's on when the key is on (and while charge).

I just have an OBDII bluetooth dongle plugged in and it only comes out when I'm at my dealer when he needs to attach my bike to the shops computer. This way the connection is also always available. I'm an iOS user myself but I've been using an Android test phone just for pushing the data.

I'm using the dongle from Power Cruise Control that you can get (here in Europe) as a kit from amazon (see link below). It's not overly expensive and it works great and is small. I've tried their app also but found the estimates not too accurate (those on the bike are better) and for me it's too expensive for what it does.



from https://www.amazon.de/gp/product/B08PL2F11P/ref=ppx_yo_dt_b_asin_title_o03_s00?ie=UTF8&psc=1

An alternative is this dongle, it's important to look for one with Bluetooth 4.0 or higher so that BLE is supported. Otherwise they won't work with iOS. Also not all copies (read cheaper dongles) support the full stack. Most of the typical clear blue ones and the black and yellow ones simply don't work for non standard OBD data like Energica requires.

In my opinion it's also best to stay away from the wifi enabled ones. First of all my app won't connect to those. I could technically make that work but honestly wifi is just not the way to go for these applications. BLE is way better suited.



from https://www.amazon.de/gp/product/B07PLDC2SC/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1

Update : this black dongle is available in many variants (check Ali) and although the one I received worked not all of these do. Also on energica the 12V power supply is completely cut off when the bike isn't running or charging so you have to press the on/off button on these on startup. Since its behind a panel that might not be convenient at all. If I find another one working I'll report back.

[Hans2183]

This is the OBDII port location on the bike



And these are some screenshots from the data visualised on http://ev-monitor.com. Note that I still need to integrate that into the iOS app.





(I've shared these before on facebook and on my blog)

[Hans2183]

I was making this keynote to explain how the BLE connection works (as I never really did that in detail) https://www.dropbox.com/s/90sbuynwvboklvs/Energica-BLE-details.pdf?dl=0



And was thinking it might be worth it to trigger a few of the missing requests from below image



The missing ones are

Code: [Select]

{4, 17, 1, -1, 0, 0, 0, 0, 0, 0}
{4, 17, 3, -1, 0, 0, 0, 0, 0, 0}
{4, 17, 5, -1, 0, 0, 0, 0, 0, 0}
...
{4, 17, 19, -1, 0, 0, 0, 0, 0, 0}
{4, 17, 26, -1, 0, 0, 0, 0, 0, 0}
{4, 17, 28, -1, 0, 0, 0, 0, 0, 0}

Anyone tried that before? The risk is limited as long as you don't put any data after the -1 position. Having a 1 there is enough to trigger something (like the horn or worse). But even then it's safe to play around. I've done some tests with the speed limit for example and it respects the system limit at all time.

If anything is received the question then is how to parse it obviously. I've been focusing on OBDII data myself lately.

[Hans2183]

I've tried the other ble requests recently and got no new responses at all. So safe to say we have the supported responses covered. That route is closed.

On the ones we do receive we had around 5 bytes left that weren't parsed yet. Someone jumped in and discovered that one byte is battery temperature. Unlike obd2 it's a single max value instead of min/max but that is still very nice as an indication without the need for obd dongles. App updates are coming.





The other 4 are 1,0 and 0,0 and logged for now. We'll see if that changes to anything useful.

Focus now will be on the OBDII data since BLE seems to be complete. On OBDII there is plenty of stuff to discover.