ORA Funky Cat

[guhlandreas]

Hi all,

The ORA Funky Cat is now in front of our cottage. I would like to integrate it into Home Assistant and charge via EVCC.
All attempts somehow via the ORA app / API to get the data such as SOC have failed for me.
Therefore, I have opted for the following way via OBDII, which I also have not gotten to run.
But here in detail, where I currently stand:

I bought the WiCan from Meatpi

The device is easy to install. I got myself another short extension cord and now it disappears into the Cat fuse box.
There is a nice tutorial for WiCan to integrate with Home Assistant using Nodered:
https://github.com/meatpiHQ/wican-fw/tree/main#home-assistant

The WiCan communicates with the MQTT server and also NodeRed. However, no data arrives in the HA.

I suspect that I have to address other PIDs. Unfortunately, however, I can't find any information on this.

What I have managed to do, on the other hand, is to read the Cat with the app "Car Scanner" on my iPhone. And that without any problems.

CONCLUSIONS:
My conclusion is therefore that the adapter (WiCan) works. Also, the Cat's data bus provides readable data.
I just can't manage to read them out with the instructions via Nodered.

Does anyone have any ideas what I am doing wrong?
Suggestions are very welcome ...

Many greetings

Andreas

[meatpiHQ]

Hey @guhlandreas , which PIDs do you need ? Here is a list of all the standard PIDs. I'm guessing you want to read the battery SoC?

https://en.wikipedia.org/wiki/OBD-II_PIDs

[meatpiHQ]

Ok that's a good start. I'll try to help you getting it going.

I think the easiest way to do this is the enable MQTT on WiCAN and also use carscanner app at the same time. Once carscanner app connects to the WiCAN click on All sensors then click on the specific sensor you want, let's say battery SoC. Now carscanner will continuously request the SoC so you'll see live data.

Use any MQTT software or APP such as MQTT explore and subscribe to WiCAN receive topic, try to log the messages and post it here I'll help you analyze it to get the PID.

[guhlandreas]

@meatpiHQ thanks a lot for your willingness to help!! I was away some days but will try to work on it tonight.
First findings:
As suggested by you I connected Car Scanner and enabled MQTT.
Car scanner needs elm327, whereas Home Assistant needs slcan as protocol. Right?
I also installed MQTT Explorer where I can see the MQTT traffic. but it is hard to log it.
Anyway, while querying on car scanner the battery SOC I can see the following data:
tx = {"bus":"0","type":"tx","frame":[{"id":2016,"dlc":8,"rtr":false,"extd":false,"data":[2,1,47,170,170,170,170,170]}]}
rx = {"bus":"0","type":"rx","ts":152,"frame":[{"id":1995,"dlc":8,"rtr":false,"extd":false,"data":[5,98,3,8,3,192,204,204]}]}
And on car scanner Battery SOC is "96". Must be %.

When I turn on the slcan protocol to test in Home Assistant communication on MQTT stops immediately and no data is received by Home Assistant.

Any idea?
Best
Andreas

[meatpiHQ]

@guhlandreas Please update to firmware v2.80 below. I've added a new feature that will help us log the OBD2 request from an to carscanner app.

Note that this update will reset your device configuration.

Here's what you need to do:

1. Enable Ap+Station mode, fill in your ssid and pass
2. Set protocol to elm327
3. Enable MQTT
4. Enable MQTT elm327 log

On your MQTT explorer or whatever mqtt software you're using subscribe to topic : wican/+/elm327

Now run you carscanner app, click on all sensors and battery SoC so it will start send OBD2 requests.

You should find something like this, which is the request and response.

Note: make sure to disable MQTT elm327 log mode when you're done, otherwise the normal mqtt function will not work. And you can leave the protocol as elm327 not need to change to slcan

wican-fw_v280_hv300.zip

wican-fw-usb_v280_hv150.zip

[guhlandreas]

@meatpiHQ thank you so much for your help.
But now I got stuck at a very bad point ...
I updated the firmware to your version wican-fw_v280_hv300.
The firmware update seemed to be completed ok.
It also seems that all config data hs been erased. OK. not unusual ...
But when I try to connect via AP my password is always rejected.
I tried my old password, as well as "@meatpi#", without success.
Have you set a different standard password in the new fw?
Thanks

Andreas

[meatpiHQ]

@guhlandreas no, nothing changed it should default to @meatpi#

It's ok you can always recover using the USB port. And also you can plug USB, it will print out the password on the terminal.

If you can want do the USB reflash make sure to erase the flash before downloading the new firmware.

https://github.com/meatpiHQ/wican-fw#2-usb-flash

[guhlandreas]

Thank you so much for your help!
The WiCAN got your 280 firmware and is running!

I was able to retrieve a huge amount of data and I am confident, that I extracted the correct data for the following purposes:

1. Battery SOC

tx: {"bus":"0","type":"tx","ts":21767,"frame":[{"id":1931,"dlc":8,"rtr":false,"extd":false,"data":[3,34,3,8,170,170,170,170]}]}

rx: {"bus":"0","type":"rx","ts":21782,"frame":[{"id":1995,"dlc":8,"rtr":false,"extd":false,"data":[5,98,3,8,2,69,204,204]}]}

The Value should be 58,1%

or

rx: {"bus":"0","type":"rx","ts":5301,"frame":[{"id":1995,"dlc":8,"rtr":false,"extd":false,"data":[5,98,3,8,1,236,204,204]}]}

The Value should be 49,2%

2. Charging Power:

tx: {"bus":"0","type":"tx","ts":22535,"frame":[{"id":1930,"dlc":8,"rtr":false,"extd":false,"data":[3,34,208,97,170,170,170,170]}]}

rx: {"bus":"0","type":"rx","ts":22542,"frame":[{"id":1994,"dlc":8,"rtr":false,"extd":false,"data":[7,98,208,97,30,31,13,84]}]}

The Value should be - 9,88 kW

3. Milage

tx: {"bus":"0","type":"tx","ts":39812,"frame":[{"id":1931,"dlc":8,"rtr":false,"extd":false,"data":[3,34,208,4,170,170,170,170]}]}

rx: {"bus":"0","type":"rx","ts":39833,"frame":[{"id":1995,"dlc":8,"rtr":false,"extd":false,"data":[6,98,208,4,0,5,66,204]}]}

The Value should be 1346 km

I was also able to adjust in Code Red so, I get the data from WiCAN --> Node Red --> Home Assistant.

Now I have still two issues!

1.
How can I properly get the data from the the above rx to decimal numbers.
E.g. when receiving the following data:
rx: {"bus":"0","type":"rx","ts":21782,"frame":[{"id":1995,"dlc":8,"rtr":false,"extd":false,"data":[5,98,3,8,2,69,204,204]}]}
The decimal value should be 58,1.
In my case it is another figure.
I used the calculation of your NodeRed snippet:

`var obj = Object();

for(let i = 0; i < msg.payload.frame.length; i++){
//check frame id
if (msg.payload.frame[0].id == 1995 && msg.payload.frame[0].data[2] == 3){
obj.fuel_level = msg.payload.frame[0].data[5] * (1 / 2.55);
obj.fuel_level = Math.round(obj.fuel_level * 100) / 100;
msg.payload = obj;
return msg;
}
}`

But I also don't know what exactly has to be calculated. Can you pls help me ....

2.
The other issue is, that at a certain point of time the data flow stops.
When I open CarScanner again, then the Car continues to deliver data.

3.
Lastly, I removed in Node Red your box "check Init Resp". What was the purpose of that step?

Sorry for all my basic questions.
But I love your device :-)

Best regards,

Andreas

[meatpiHQ]

@guhlandreas the data you collected is awesome!

Don't worry about calculating the parameters in NodeRed, we will use the new CAN to JSON interpreter to do the calculations. Actually we might be able to do it without using NodeRed all together. I will update you soon on how to do this.

Btw check Init Resp, it handles the responses of 01 00 PID request which is initialize the Bus.

[guhlandreas]

That's great. Looking forward to hear from you ;-)
BTW: Just updated my post above and updated one PID.

[meatpiHQ]

@guhlandreas Here what I think you should do. Please try it and let me know if it works.

1- On WiCAN disable MQTT elm327 log

2- Add a filter like in the screenshot below, then click Add ID then Store button. This is based on the Battery SOC CAN frame,. The battery SoC is calculated using Byte 4 and Byte 5, ((2*256)+69)/10

{"bus":"0","type":"rx","ts":21782,"frame":[{"id":1995,"dlc":8,"rtr":false,"extd":false,"data":[5,98,3,8,2,69,204,204]}]}

ID: 1995
Name: BatterySoC
PID: 3
Start bit: 0 (Not used)
Bit Length: 1 (Not used)
Expression: ((B4*256)+B5)/10
Cycle: 1000

3- Now in HA create a new automation to send OBD request every 5 second or what ever interval you want, make sure in the topic to replace xxxxxxxxxxxx with your device id.

The result should be something like:

[guhlandreas]

@meatpiHQ: awesome, awesome, awesome!
That is so great!
Thank you so much! It works and delivers proper values.
I added some more devices, like Milage and Charging Power.
... and here comes my new issue ;-)
I am too stupid to understand how to interpret the data. The calculation using Byte 4 and Byte 5 is clear.
How do I calculate with more Bytes?

e.g. Milage: Data: {"id":1995,"dlc":8,"rtr":false,"extd":false,"data":[6,98,208,4,0,5,66,204]} in decimal this should be approx.: 1346
or e.g. Charging Power: {"id":1994,"dlc":8,"rtr":false,"extd":false,"data":[7,98,208,97,30,31,13,84]} in decimal this should be approx.: -9,88

Thanks again for your swift help!!

Best regards,

Andreas

[lucakes]

Hi, thanks to your effort. I got batterysoc information on my openhab instance. I'm able to read the data when the vehicle is charging, when its locked and shutdown, after like 5 minutes no more new messages get send.

Currently im trying to get the Mileage info, im stuck at the configuration of the wican. Im not sure about some points:

ID: 1995
Name: Milage
PID: 3 ??
Start bit: 0 (Not used) ??
Bit Length: 1 (Not used) ??
Expression: (B5*256)+B6
Cycle: 1000

[meatpiHQ]

@lucakes sorry I missed your comment, if you still have a problem please open an issue.

[acehalk]

Hello, based on this study, did you get the ELM commands to retrive the SOC information ?
If yes, could you please share ? I'm trying to retrieve this info but without luck

[lucakes]

Hi, no sorry, have not tried any further.

[spicydog]

For Charging Power I have approximate expression which is

-(((b[4]*256+b[5])*0.03425743)-274.108-0.05)

I think it is reflect from HV Bus Current which is

-((b[4]*256) + b[5] - 8000)/10;

[spicydog]

In case anyone coming up to work with Ora Good Cat.
This is the list I work so far.
Feel free to use and contribute.

Name	Unit	Init	PID	Expression
hv_battery_soc	%	ATSH78A;ATFCSM1;ATCRA7CA;	22D0621	[B4:B5]/10
hv_battery_soe	kWh	ATSH78A;ATFCSM1;ATCRA7CA;	22D0621	((B6*256)+B7)/10
hv_bus_current	A	ATSH78A;ATFCSM1;ATCRA7CA;	22D061	-((B4*256)+B5-8000)/10
hv_bus_power	kW	ATSH78A;ATFCSM1;ATCRA7CA;	22D061	-((([B4:B5])*0.034257)-274.16)
coolant_temperature	°C	ATSH78A;ATFCSH78A;ATFCSM1;ATCRA7CA;	22D0311	((B6*256+B7)-400)/10
tire_pressure_front_left	psi	ATSH76C;ATFCSH76C;ATCRA7AC;	2202102	B5*0.2-0.22
tire_pressure_front_right	psi	ATSH76C;ATFCSH76C;ATCRA7AC;	2202102	B7*0.2-0.22
tire_pressure_rear_left	psi	ATSH76C;ATFCSH76C;ATCRA7AC;	2202102	B10*0.2-0.22
tire_pressure_rear_right	psi	ATSH76C;ATFCSH76C;ATCRA7AC;	2202102	B12*0.2-0.22
tire_temperature_front_left	°C	ATSH76C;ATFCSH76C;ATCRA7AC;	2202102	B6-50
tire_temperature_front_right	°C	ATSH76C;ATFCSH76C;ATCRA7AC;	2202102	B9-50
tire_temperature_rear_left	°C	ATSH76C;ATFCSH76C;ATCRA7AC;	2202102	B11-50
tire_temperature_rear_right	°C	ATSH76C;ATFCSH76C;ATCRA7AC;	2202102	B13-50
odometer	km	ATSH78B;ATFCSH78B;ATCRA7CB;	22D0041	[B5:B6]

[TPoi2]

So pressure in bar would be "B#0.0138-0.01518".
I currently retrieve the TotalCharge via MQTT tx with {"bus":"0","type":"tx","ts":28695,"frame":[{"id":1931,"dlc":8,"rtr":false,"extd":false,"data":[3,34,33,113,170,170,170,170]}]} and read it from PID 1995 2B7+B8/128. How does this translate into the values above?

[TPoi2]

I discovered the documentation about to use of the CarScanner log file and found the entries for TotalCharge and TotalDischarge. Below the json entry I am using now. However, I am confused about the use of the pid_init as both PID have the same pid_init. Is there a way to combine the below code into one entry?

{"pid":"2221711","pid_init":"ATSH78B;ATFCSM1;ATCRA7CB;","parameters":[
  {"name":"TotalCharge","class":"energy","expression":"10000*([B5:B6]+B7/256)","unit":"Wh","min":"","max":""}
  ]},
{"pid":"2221721","pid_init":"ATSH78B;ATFCSM1;ATCRA7CB;","parameters":[
  {"name":"TotalDischarge","class":"energy","expression":"10000*([B5:B6]+B7/256)","unit":"Wh","min":"","max":""}
  ]},

NB: Regarding tyre pressure in bar, I changed to "B5/73" which seems to be sufficiantly exact.

[spicydog]

Maybe you need to do like vehicle_profile but I'm didn't dig down to it yet.
Since I have talked with MeatPi, he said you may build your own vehicle_profiles and upload to the device.
This is the sample form the current code for GWM I was working on with MeatPi (it is not up-to-date with the table I list above, that one I did myself.)
https://github.com/meatpiHQ/wican-fw/blob/main/vehicle_profiles/gwm/gwm.json

Let me know if you need help, we can work together and may submit pull request to MeatPi. :)

[TPoi2]

Based on your and my investigations with CarScanner I created below json-file. However, I still do not understand the need of equal pid_inits. If I look in the log, the commands are only sent ones and then the PIDs where collected. I would expect that several PIDs are subordinated to one pid_init but may be I do not understand correctly.

{"cars":[{"car_model":"GWM: Ora Funky Cat","init":"ATSP6;ATAT1;","pids":[
{"pid":"22D0621","pid_init":"ATSH78A;ATFCSH78A;ATFCSD300000;ATFCSM1;ATCRA7CA;","parameters":[
  {"name":"SoC","class":"battery","expression":"[B4:B5]/10","unit":"%","min":"-5","max":"105"},
  {"name":"SoE","class":"battery","expression":"[B6:B7]/10","unit":"kWh","min":"","max":""}
  ]},
{"pid":"22D061","pid_init":"ATSH78A;ATFCSM1;ATCRA7CA;","parameters":[
  {"name":"HVBusCurrent","class":"current","expression":"(8000-[B4:B5])/10","unit":"A","min":"","max":""}
  ]},
{"pid":"2220511","pid_init":"ATSH78B;ATFCSM1;ATCRA7CB;","parameters":[
  {"name":"SoH","class":"battery","expression":"[B4:B5]/10","unit":"%","min":"","max":""}
  ]},
{"pid":"2221711","pid_init":"ATSH78B;ATFCSM1;ATCRA7CB;","parameters":[
  {"name":"TotalCharge","class":"energy","expression":"10000*([B5:B6]+B7/256)","unit":"Wh","min":"","max":""}
  ]},
{"pid":"2221721","pid_init":"ATSH78B;ATFCSM1;ATCRA7CB;","parameters":[
  {"name":"TotalDischarge","class":"energy","expression":"10000*([B5:B6]+B7/256)","unit":"Wh","min":"","max":""}
  ]},
{"pid":"22D0311","pid_init":"ATSH78A;ATFCSH78A;ATFCSM1;ATCRA7CA;","parameters":[
  {"name":"CoolantTemperature","class":"temperature","expression":"([B6:B7]-400)/10","unit":"°C","min":"","max":""}
  ]},
{"pid":"2203081","pid_init":"ATSH78B;ATFCSH78B;ATCRA7CB;","parameters":[
  {"name":"TrueSoC","class":"battery","expression":"[B4:B5]/10","unit":"%","min":"","max":""}
  ]},
{"pid":"22D0041","pid_init":"ATSH78B;ATFCSH78B;ATCRA7CB;","parameters":[
  {"name":"Mileage","class":"distance","expression":"[B4:B5]*256+B6","unit":"km","min":"","max":""}
  ]},
{"pid":"22D0031","pid_init":"ATSH78B;ATFCSH78B;ATCRA7CB;","parameters":[
  {"name":"OperatingVoltage","class":"voltage","expression":"B4/10","unit":"V","min":"","max":""}
  ]},
{"pid":"2220032","pid_init":"ATSH78B;ATFCSH78B;ATCRA7CB;","parameters":[
  {"name":"HVBatteryVoltage","class":"voltage","expression":"[B5:B6]/10","unit":"V","min":"","max":""}
  ]},
{"pid":"2202102","pid_init":"ATSH76C;ATFCSH76C;ATCRA7AC;","parameters":[
  {"name":"TirePressureFL","class":"pressure","expression":"B5/73","unit":"bar","min":"","max":""},
  {"name":"TireTemperatureFL","class":"temperature","expression":"B6-50","unit":"°C","min":"","max":""},
  {"name":"TirePressureFR","class":"pressure","expression":"B7/73","unit":"bar","min":"","max":""},
  {"name":"TireTemperatureFR","class":"temperature","expression":"B9-50","unit":"°C","min":"","max":""},
  {"name":"TirePressureRL","class":"pressure","expression":"B10/73","unit":"bar","min":"","max":""},
  {"name":"TireTemperatureRL","class":"temperature","expression":"B11-50","unit":"°C","min":"","max":""},
  {"name":"TirePressureRR","class":"pressure","expression":"B12/73","unit":"bar","min":"","max":""},
  {"name":"TireTemperatureRR","class":"temperature","expression":"B13-50","unit":"°C","min":"","max":""}
  ]}
]}]}

[spicydog]

@TPoi2 I may not understand 100% correct as well but this is what I discovered so far.

1. There will be the main initialization above of all
2. To get the value of a sensor at least another custom_pids has to be send
3. After custom_pids is sent, WiCAN will connect to OBD 2 and response the data
4. 1 custom_pids will response 1 output data
5. 1 output data may have several sensor inside that what we have to figure it out

The clear example if TireSensors, when we send pid_init":"ATSH76C;ATFCSH76C;ATCRA7AC;, the response will be in 2 lines, (2 times of usual), and all bytes are represent 8 sensors, pressure and temperature of all 4 tyres.

It would be easier if you debug in elm327 mode, send the expected tx and get the expected response.
From this, you can write the formula correctly then make the automation in WiCAN with pid_init later. :)

[TPoi2]

This is understood but still my irritation remains. :-)