That sounds great. I installed 3.11 and set a rule for my Kia e-Niro 2019 like so (based on OBD-PIDs-for-HKMC-EVs/Hyundai Kona EV & Kia Niro EV/extendedpids/003_Kona&Niro_EV_BMS.csv at master · JejuSoul/OBD-PIDs-for-HKMC-EVs · GitHub):
Name: soc_disp
PID: 220105
Expression: B2/2
Period: 1000
Send_to: wican/my_id/soc_disp
Do I still need to trigger something over wican/my_id/tx from home assistant? That’s the part that I haven’t been able to figure out how to configure…
no trigger needed, should read/start transmitting
But in fact I’m running Version 3.10 beta: Release v3.10Beta · meatpiHQ/wican-fw · GitHub
Ok, good. I guess I will have to try some general PIDs first.
Can’t really see what the differences between 3.10 and 3.11 are. The tags are on the main branch, and on the same commit.
Maybe I will try to build the latest commit from the auto-pid branch and install that.
im on 3.11 now.
any idea why Battery Alert is not working?
i set the threshold high at 12.8v. the battery dipped below 12.4 many times but i never see anything via topic “CAR1/voltage”
Did you find a solution. Did not get my wican working need to put some time into this topic.
I did manage to get the state of charge published on MQTT, but only when I run carscanner at the same time, so clearly that triggers it somehow. I got a bit tired of it all, so I’ve paused my efforts for a bit…
New FW is out: Release v3.21Beta · meatpiHQ/wican-fw · GitHub
Supports Car spezific settings using a json file.
Any idea why I’m not seeing any rx MQTT messages from the wican? Using MQTT Explorer, I see the Online status message, and have tried publishing some of the example tx messages to the wican/my_id/can/tx topic, but don’t get anything in response. I did get a Low Battery mqtt message, after enabling the Sleep and Battery Alert settings. Just not sure why I’m not getting any responses to any requests.
EDIT: Nevermind, it started spamming a thousand messages after starting the engine…
You need to disable the logging for carscanner
I am also interested to know.
for my Ioniq 5, E-vehicle, i see this equation ((B34<8)+B35)/10
any idea what this “<” do? what does B34 do to 8?
Hi Tung256
I think that is a sort of C syntax for a bit shift. In C the << means shift left, the 8 means 8 positions. In reality that means a divide by 256.
To be honest a multiplcation by 256 would make more sense:-) then it is just a two byte 2 number, with one being the high and the other the low part.
FYI, WiCAN developer @MeatPi has now started a new crowdfunding/crowdsourcing campaign for an updated ”WiCAN Pro” next-generation OBD dongle product that includes an added dedicated CAN bus chip that provides full support for all legislated OBD-II protocols as well as featuring a powered-USB port for hardware addons (including an upcoming ESPNetLink LTE/GPS module for it to allow for real-time location tracking and online data analysis), this one will also have a microSD card slot for data logging:
| Feature | WiCAN Pro | WiCAN | OBDLink MX+ |
|---|---|---|---|
| USB Host Interface | Yes | No | No |
| Dual USB to Serial | Yes | No | No |
| ISO 15765-4 CAN J1962 (PIN 6/14) | Yes | Yes | Yes |
| SAE J1939 CAN J1962 (PIN 6/14) | Yes | No | Yes |
| ISO 11898 raw CAN J1962 | Yes | No | Yes |
| Medium Speed CAN MS-CAN J1962 (PIN 3/11) | Yes | No | Yes |
| GM High-Speed J1962 (PIN 12/13) | Yes | No | Yes |
| Single Wire CAN GMLAN J1962 (PIN 1) | Yes | No | Yes |
| SAE J1850-PWM | Yes | No | Yes |
| SAE J1850-VPW | Yes | No | Yes |
| ISO 9141-2 | Yes | No | Yes |
| ISO 14230-4 Slow/Fast | Yes | No | Yes |
| ELM327 instruction v2.3 | Yes | Emulation v1.5 | Yes |
| ELM329 instruction v2.2 | Yes | No | Yes |
| STN instruction | Yes | No | Yes |
| VT instruction | Yes | No | No |
| Interface | WiFi/BLE/USB | WiFi/BLE | Bluetooth |
| Button | Yes | No | Yes |
| SD Card Logging | Yes | No | No |
| WiCAN Firmware | Yes | Yes | No |
| Realdash CAN Protocol (PIN 6/14) | Yes | Yes | No |
| slcan/socketCAN (PIN 6/14) | Yes | Yes | No |
| Price | $80 | $42 | $139.95 |
References:
By the way, WiCAN beta firmware has improved support for Home Assistant according to @MeatPi
First of all, I’d like to thank everyone who has supported the release of WiCAN PRO so far.
Over the past couple of months, I have been working on better integration with Home Assistant, making it easier for you to pull data from your vehicles. My goal is to make the process as seamless as possible. With the new wican firmware, users will be able to simply select their car model and the available parameters will be pushed to Home Assistant over MQTT. I’ve also added a Home Assistant MQTT Discovery option, so all available sensors will be automatically created in Home Assistant. Additionally, users can add their own custom PID requests for even more flexibility. Currently, only a few cars are supported, but I expect the list to grow rapidly.
It’s now easier to support more vehicle models by simply adding a JSON file, allowing users to share their vehicle profiles and contribute to the WiCAN firmware by making a pull request. This improvement is thanks to backer Jay O., who suggested and implemented the idea of having a separate JSON file for each vehicle and using GitHub Actions to merge them into a single file. This merged file will be built into the new firmware version or can be directly uploaded to WiCAN.
The new firmware update is still in beta testing and will be released soon, along with the documentation.
One user, Tung, has already made a YouTube video about adding a new custom PID request:
Hi Tung, I’m not sure about the first “Signed(X)”. The second one, I would guess (again based on C syntax comparison, that it takes the lower 6 bits of the byte, so basically a number between 0 and 32. Does that make sense for the entity you are trying to compute?
Wonderful to see that the WiCAN works even better with Home Assistant now. And that you can add a new car model very simply.
Is there a list of car models that are already supported?
I am driving a 2017 Opel Ampera-E, It is identical to the GM Bolt 2017. Is any of those already working?
Regards, Bert
You can also post such questioms to WiCAN’s own community here:
See example
I received my dongle yesterday. Had my Kona EV integrated with Homeassistant through the car selection within the hour. Big compliment to MeatPi!
Now I would like to get my odo, which seems to be a multiple frame reply. Can that be handled in the Custom PID setup? Or does it need programing? Any pointer appreciated!
BTW car scanner does not supply this value either, so maybe it is not even feasible…
