Wideband Controller: Fully Custom, no ASIC!

[pkagiantas]

also im facing an issue two brand new sensors on a a proteus reads backwards !

it sits at 10.0 afr at free air and when i hit it with butane it goes to 29

[mck1117]

are Ip and Rtrim pins swapped?

[pkagiantas]

i hope not but i will check

[bitshifted-MX5]

Could anyone explain to me how I can build the code for the wideband controller?

[AndreyB]

Could anyone explain to me how I can build the code for the wideband controller?

what are you trying to accomplish? expectation is that anyone who has needs to change code also has skills to compile?

[bitshifted-MX5]

Could anyone explain to me how I can build the code for the wideband controller?

what are you trying to accomplish? expectation is that anyone who has needs to change code also has skills to compile?

I am used to compile my code using the STM32CUBE IDE. I see that there are build files to run in my Linux shell and Makefiles, but when I run these I get the error `../../../ChibiOS/os/common/startup/ARMCMx/compilers/GCC/mk/rules.mk: No such file or directory`.

Is there maybe a guide or something which explains how to compile the code?

[Dron_Gus]

Is there maybe a guide or something which explains how to compile the code?

Seems you did not checkout git submodules.

[JRD McLAREN]

Which repository of WBO2 controller is most actual ..?
mck1117's or Dron_gus's ... ??

I have compiled fw from this repo - https://github.com/mck1117/wideband/releases/tag/2311-release
modified for "my wbo2 addon board" for F072 mcu with analog outputs ...
.. but I need some help with this ...

I'm found any issue on github, about this ..
EDITED: https://github.com/mck1117/wideband/issues/300

..
and I can send some boards to someone to test if needed

[dynfer]

Hello,

I have two f0 boards which have two different behaviours, both running November firmware from mck1137/wideband.

1. Nerst voltage fluctuates depening on the applied oxygen (sensor over candle or lighter) afr sometimes jumps if nerst crossed over 450mV
2. Nerst voltage stays fixed at around 450mV, pump current changes depending on applied oxygen, AFR stays pretty much fixed at around 15.45

I've attached logs from both boards 2024-01-18_18.02.05.zip

Both boards are hand assembled so there might an issue with soldering??

//EDIT
I've verified all solder joints and now both units behave like in the log below, the spikes are nerst V and pump DC are from me applying propane to the sensor 2024-01-18_21.41.24.zip

//EDIT 2
After more troubleshooting I've found that when applying gas to the sensor the PumpDC rises which is expected but this should cause the nerstV to stay relatively around 450mV, in my case the nerst V shoots up to 0.9/1V

[md_sanci]

Hello all,

I also have a question regarding Wideband. Using hellen 128, my car is running on this as a daily driver for the last 2 years at least. Sensor is still the same, and milage is around ~15K.
I noticed in the last few months strage WBO values, i do not have a display, so only when i connected my phone with real dash i noticed and then the laptop to get some logs. I do not see nothing strange in running parameters but WBO values are all around, i also checked older logs to see what is the wbo reporting, maybe i can get a picture of what is happening or if i can say for sure that sensor is half dead.

https://rusefi.com/online/view.php?log=1361 here is one log, AFR is reported nicely then it start to jump all around, driving on the highway i also noticed values of 6 to 23 jumping or even staying there. Is there a way to see if this is really sensor or not? i know that it would be nice to change it but i do not have time at least not in the next few weeks, and i was thinking maybe this also helps to handle some error cases?

[AndreyB]

I also have a question regarding Wideband. Using hellen 128, my car is running on this as a daily driver for the last 2 years at least.

I would recommend starting with update of the wideband firmware. I believe that November 2023 version was a major improvement see https://github.com/mck1117/wideband/releases/tag/2311-release

Second step would be some logs - Wideband transmits and rusEFI logs a number of internal metrics

[md_sanci]

I also have a question regarding Wideband. Using hellen 128, my car is running on this as a daily driver for the last 2 years at least.

I would recommend starting with update of the wideband firmware. I believe that November 2023 version was a major improvement see https://github.com/mck1117/wideband/releases/tag/2311-release

Second step would be some logs - Wideband transmits and rusEFI logs a number of internal metrics

I did update via TS, i know this was done in the past, but now no message, did it went ok or not.... should i just take the ecu out and stlink the fw? is there a way to test if it is all good, what version am i running, maybe my memory is bad, but i remembered a debug mode for this, but i cannot find it

[AndreyB]

I am not sure if current TS updater works especially in case of two units especially to update older firmware. Maybe it does maybe it does not

I would st-link just to be sure

https://github.com/rusefi/rusefi/issues/5719
https://github.com/mck1117/wideband/issues/311

[AndreyB]

fault code 5

``SensorUnderheat = 5``

is it possible to say anything from this log?

image.png (179.91 KiB) Viewed 11267 times

[md_sanci]

fault code 5

``SensorUnderheat = 5``

is it possible to say anything from this log?

image.png

I had issues way back with cable management, due to limitation of what cables and connector i used for WBO, sporadically had issues with heater, so as a tip, use good cables, good soldering or crimping and good connectors, at least for me that fixed issues with heating.

[md_sanci]

I am not sure if current TS updater works especially in case of two units especially to update older firmware. Maybe it does maybe it does not

I would st-link just to be sure

https://github.com/rusefi/rusefi/issues/5719
https://github.com/mck1117/wideband/issues/311

Only now i had time to pull ecu out, conncet ST-link to WBO + usb for ecu supply, and when trying to flash it looks like by F0 is in reset, i have to figure it out why but i am still stuck, lucking at hellen schematic, main cpu is not controlling this reset, so maybe i have hw issue, oxide is not present on the pcb, but i need a better magnifier to better inspect the pcb

[AndreyB]

fault code 5

``SensorUnderheat = 5``

is it possible to say anything from this log?

[benassi124]

fault code 5

``SensorUnderheat = 5``

is it possible to say anything from this log?

image.png

I had issues way back with cable management, due to limitation of what cables and connector i used for WBO, sporadically had issues with heater, so as a tip, use good cables, good soldering or crimping and good connectors, at least for me that fixed issues with heating.

Continuity + resistance verified from connector 2 board. Wire used is Tefzel wire/ M22759/32

[AndreyB]

Wire used is Tefzel wire/ M22759/32

I see some OEM harness where heater wires are thicker than signal but Dron says it should not matter.

[benassi124]

Wire used is Tefzel wire/ M22759/32

I see some OEM harness where heater wires are thicker than signal but Dron says it should not matter.

18AWG was used for heater wire, tefzel has thinner insulation than TXL because it is a stronger material. TEFZEL is 31% thinner than TXL, 1.52mm nominal OD vs 2.20MM (txl), conductors strands are also tightly twisted in the insulation as well. This is why it looks thinner

signal wires are 22 awg 1.09mm Nominal OD

[AndreyB]

fault code 5

``SensorUnderheat = 5``

is it possible to say anything from this log?

this was a cable mistake - dual-sensor cable had some wires going to wrong sensor

[AndreyB]

New log, here I only have one channel working while second one is not showing any reading.

Latest main firmware logs detailed info for both WBO channels

image.png (161.44 KiB) Viewed 9954 times

[AndreyB]

Same setup sensors are now flipped - problem stayed with second controller

image.png (165.55 KiB) Viewed 9954 times

[Dron_Gus]

Please check Ip and CalR connection for sensor #2. Green and Red wires. Pins #2 and #6 on sensor connector.

[AndreyB]

Please check Ip

It was a hardware design issue, Ip was shorted to GND

[kimman1]

I'm just finishing WBO lambda x2.
But i got a problem when plug in the sensor the wbo still heating the sensor but about 30s, wbo return sensor is overheat
I'm using lsu 4.2 sensor. I attached log.

[kimman1]

I'm just finishing lamba x2
The problem is when I connect the lsu 4.2. Just about 30 second after heating, the temperature notification on tunner studio is sensor overheat.
I attached log below. Please help me
Attached the is latest file

[AndreyB]

I'm using lsu 4.2 sensor.

You could be the first person attempting to use 4.2 sensor.

In reality the most proven calibrations are for the 4.9

[kimman1]

I'm using lsu 4.2 sensor.

You could be the first person attempting to use 4.2 sensor.

In reality the most proven calibrations are for the 4.9

Actually I'm not buy LSU 4.9 sensor yet. For LSU 4.2 I got 3 of them ( from another commercial Wideband controller ).

[JRD McLAREN]

"any release" of wbo2 controller have prepared hardware for LSU4.2 and LSU_ADV sensor ...
see pic.

it's just a plan?? or... WIP