It would be great if you can built a firmware with AP IP Adresse: 192.168.0.10:35000
THX

Here you go. You can change the port in the configuration webpage.

wican-fw_v298_hv300_ipc.zip

thx, it works - well I connect to the adapter. still no communication with the ecu

Please try this firmware version.

wican-fw_v299a_hv300.zip

// this is the actual code for SoC
commandToSend = "03 222002";

@meatpiHQ
Well I gave a new try with AutoId I tried to send 220002 and get a response:

{"autoSOC":345.3,"raw":"056220020D7D"}

Any hints for the PID request, any init I have to apply?

What was the actual SoC at time of reading?

Looking at one of your older posts, you divided by 50, not 10. I think your expression might be: [B4:B5]/50

It's working now! What a nice update!

So topic closed 🥳

Have you tried this ?#112 (reply in thread)

No success with HA, but just a quick test. No logs so fare. But AP IP Adress is back to standard?

Oh sorry about that, I'll send you a new one with the correct IP.

Here you go, fixed the IP. wican-fw_v299b_hv300.zip

I working on adding a configuration to initialize the bus, like setting up the header and other parameters

I'll need a few days for futher testing...

How about in topic soc2, that you've set in destination?

How about in topic soc2, that you've set in destination?

No Data, i only get the "Status" online and the rx frames

How about if you disable car specific? And just keep the custom.

Btw the check box next to the tx topic is to enable the topic.

Sry gave ro stop testing, my wife needs the car,😔 will continue tomorrow

No worries, I'm really curious about this unusual problem. Maybe tomorrow we can send raw elm327 commands over tcp or do the USB logging.

Is the reported SOC always 0?

@TheSmartGerman What is the formula for the odometer? It is cropped in the screenshot. Thanks!

@TheSmartGerman What is the formula for the odometer? It is cropped in the screenshot. Thanks!

Only at the mobile phone right now. The formula is:

(((B465536)+(B5256))+B6)

@TheSmartGerman Since you have some experience with the PIDs, maybe you can help me.
In the Zoe definitions of OVMS there are other "endpoints" for the state of charge: line 40, line 55 and line 171. Do you know what the matter is with them? They don't seem to have PIDs?
Another point is that i would like to get the state if the charging cable is connected. Line 54 seems to be right. How does it translate for usage with the Wican?
I am quite a noob in this regard.

ok, well I guess this are other ECUs (7ec) is the main ECU. 7bb as far as I know it the Battery Safty ECU. I tried to log the CanZE app. But most of the ECUs calls didn't work. Maybe you can have a try. This app reports different SOCs (as far as I know).
https://canze.fisch.lu/

Well, I use Auto PID + MQTT "productiv". I started with FW 2.98, since Auto PID I'm using MQTT and it's working.

I created the vhicle profile but never switched to the profile permanent.

If I switch from MQTT to the profile + HA Integration, I'll use my historic data.

My plan is to switch some day, but right at the moment, other projects are more in focus.

So far I'm reading this data:

All data is from ECU Adress 0x7ec, I'm still try to figure out how to get data from 0x7bb

0x7bb is the BMS, with this data ever single cell can be monitored and the min/max cell, dif etc. will be possible

PIDs / ECUs are well documented here: https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/blob/ab50584ae9a1533d0b4c6e74b1a1121dacc41e7f/vehicle/OVMS.V3/components/vehicle_renaultzoe/docs/PIDs_Renault_Zoe.txt

Hi,
Noob alarm here :-)
Could you please show the meat-pi config-line for the temperature of the HV-Battery?
Thanks!

you can check the vehicle profile above or my screenshot from 08/2024

The PID is 223203, expression: [B4:B5] * 0.2

            "pid": "223203",
            "parameters": [
                {
                    "name": "HV Battery",
                    "expression": "[B4:B5] * 0.2",
                    "unit": "V",
                    "class": "battery"
                }
            ]

Hi,

Thats only volt but not temperature, is it?

Right, this is only the Voltage. From the OVMS I found this: + "7ec,24,31,1,40,0,°C,222001,622001,ff,Battery Rack temperature\n" //

The Encoding is like this:
// ID (hex), startBit, endBit, resolution, offset (aplied BEFORE resolution multiplication), decimals, unit, requestID (hex string), responseID (hex string), options (hex, see MainActivity for definitions), optional name, optional list

So PID is 222001, Resolution 1, Offset 40, 0 decimals, °C

I guess offset is negative, to get a full temp range.

Therefore the Temp of the battery should look like this (not tested):

The PID is "222001": expression: "B4-40"

oh, interessting ;) missed it, I do have the data, but don't show it somewhere :P

Really cool - works fine!
Could you help with two more entries?
"654,2,2,1,0,0,,,,ff\n" // Charging Plug Connected
and
"654,32,41,1,0,0,min,,,ff\n" // Time to Full

sorry, this is another ecu response 0x654, so far all data is from 0x7ec. I guess for this PIDs you need another PID Init to switch to the other ecu.

There is a ELM LOG above. I was not able so far to get data from another ecu. In theory it should be possible to switch, by using it Init.

A "full" PID_init can look like this: ATSH7E4;ATFCSH7E4;ATFCSD300000;ATFCSM1;ATSTFF;ATATA0;ATSP6;ATAT1;ATCRA7EC;ATFCSH7E4;

It should look like this profile, the pid_init changes the header from 78A for one pid to 76c to the other...

{
  "car_model": "GWM: Ora Good Cat/Funky Cat/ES11/Haomao/Ora 03",
  "init": "ATSP6;ATAT1;",
  "pids": [
    {
      "pid": "22D0621",
      "pid_init": "ATSH78A;ATFCSH78A;ATFCSD300000;ATFCSM1;ATCRA7CA;",
      "parameters": {
        "SOC": "[B4:B5]/10"
      }
    },
    {
      "pid": "2202102",
      "pid_init": "ATSH76C;ATFCSH76C;ATCRA7AC;",
      "parameters": {
        "TYRE_P_FL": "B5*0.2-0.22",
        "TYRE_P_FR": "B7*0.2-0.22",
        "TYRE_P_RL": "B10*0.2-0.22",
        "TYRE_P_RR": "B12*0.2-0.22"
      }
    }
  ]
}

My Kangoo is build 2021
How old is yours? Perhaps I ask my dealer for an update.

mine is from 2013. I guess your's PH2 and 33kWh? the behavior may differ.

Most informations I got from the OVMS: All my PIDs are based on this. https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/blob/ab50584ae9a1533d0b4c6e74b1a1121dacc41e7f/vehicle/OVMS.V3/components/vehicle_renaultzoe/docs/index.rst

There this info:

Vehicle Type: RZ
This vehicle type supports the Renault Zoe(PH1) and Kangoo(2011 - ~2019). The newer Zoe ph2 and Kangoo are not supported yet.

Yes, its the 33 kWh

I will try on to solve my problem :-)

I've got 2012 but upgraded with 33 kWh akku. :-)
I can reproduce my above picture. 4 minutes after the car was locked I get SOC 0 / HV Voltage 0 / HV temp -40 and SoH 0
When i unlock the car and turn the ignition the right values are here.
So maybe some parts of the Battery go on sleep although meatpi is running (dongle online)

This I knock out with sleeptimer 1 minute. WiCan is faster in bed as the Kangoo.
But after charging Kangoo switched faster than WiCan.
evcc then have 0%, starts, real SOC, stops, and so on ... :-&

...and really. After the stop of charging SOC will become zero...
So evcc restarts charging - just to detect 90% and stop charging again. And so on ...
Oh dear. That renders wican unusable with Kangoo.

But the Idea to keep the last entries when 0 occurs would solve this!

Yes, stupid car ;-)

I'm actual testing with the period WiCan is writing the mqtt. Standard is 5 Seconds, I set to 2 Minutes, now I had only one time 0% soc - perhaps I go longer and than the probability for zero SOC goes down.

The Problem is the arriving of the car. WiCan must connect WiFi and leave the actual SOC before the timer.

I set 100% in evcc again and will unplug the car at 90% like I did before.
Maybe the developer can add the idea to not show 0 to the kangoo profile in the next firmware.

The Kangoo with WiCan is implemented as a generic mqtt car, not a specific profile.
I think evcc (or other) are not the right place to filter this because the do not know the latest correct SOC because there is only 0 now in mqtt.

I would like to have a filter in WiCan that I can specify for example only 1-100 as possible values to announce.

Perhaps @meatpiHQ have got the option to implement a filter.

I didn't mean evcc but wican - there you may choose the Kangoo Z.E. profile
Your idea about the filter is fine!

@Derdirkf
I do have a updated version, with even more informations...

@meatpiHQ
How to provide the profile? Sync the Fork and create a PR?

Edit: I synced the fork and discarded my changes :( have to fix it later...

@TheSmartGerman what more information could this be :-)

Where I find this profile??

@TheSmartGerman what more information could this be :-)

Where I find this profile??

I have up update it ;) or I'll have to upload here. I do have: SOC, ODO, Range, SOH, LV Bat Voltage, HV Bat Voltage, HV Bat Temp, HV Bat Current, Battery Available Energy: #112 (reply in thread)

Hey @TheSmartGerman

I use the profile with soc, odo, LV and HV bat, SoH and Range

While charging today everything looks fine, after charging SoH goes from 97,00 to 126,00 - quite good :-)
And range goes from 143 to 1023 - quite better :-))

Any ideas why this happens??

It's the Same für me. While Charching values are fine. After this, the values are not valid any more.

@TheSmartGerman Can you please create a PR? fork and edit the profile . And please change the parameters names to match the schema