rusefi.com

Posted: **Fri Jun 14, 2019 9:56 am**

I'm tested one board without FET,
and have same result .. as you can see on videos ..

This LED wiring for heater activity is wrong ..

look here also .. https://rusefi.com/forum/viewtopic.php?f=4&t=1052&start=180#p33371

Posted: **Fri Jun 14, 2019 10:00 am**

kb1gtt wrote: ↑
Fri Jun 14, 2019 9:50 am
... MOSFET will leak some current, which might be enough to make the LED bright, even though there is not enough current to cause any significant heat in the heater.

Is not problem to "make some heat on heater" ...
Is the problem for CJ125 chip, to measure heater resistance correctly...
(and started to work, in my case)

Posted: **Fri Jun 14, 2019 5:55 pm**

OK .. small victory ..

It started to work, after cranking ...
but it cut-off, when heater dc reach 90%...

..and console log is full of unknown numbers .. for me..

Any advice ..??

Can anybody post me, "any range" of working UA and UR values..??

Is (any) switching between LSU4.2 or LSU4.9 needed ..??
..or it is automatic ..??

Posted: **Fri Jun 14, 2019 6:16 pm**

JRD McLAREN wrote: ↑
Fri Jun 14, 2019 5:55 pm
Is (any) switching between LSU4.2 or LSU4.9 needed ..??
..or it is automatic ..??

OMG, we've forgot to make the checkbox visible in Tuner Studio. Here you are - https://github.com/rusefi/rusefi/commit/43acf4c3fc740fb204a3f89d848cdd3470ff115c

also there are resistors on the PCB. So, by default it's 4.2, now with the switch you can change to 4.9

Posted: **Fri Jun 14, 2019 6:16 pm**

I have some of Matt's logs at https://github.com/rusefi/rusefi_documentation/tree/master/overview/wbo - that's 4.9 I believe

Posted: **Fri Jun 14, 2019 6:42 pm**

JRD McLAREN wrote: ↑
Fri Jun 14, 2019 5:55 pm
Can anybody post me, "any range" of working UA and UR values..??

4.2:

Code: Select all

EngineState: cj125: state=5 diag=0xFF (vUa=2.119 vUr=0.916) (vUaCal=1.501 vUrCal=0.909)
EngineState: cj settings: offset=0 P=0.02441 I=0.00762 D=0.00000 dT=1
EngineState: cj status: value=0.53 input=0.90/target=0.91 iTerm=0.53561 dTerm=0.00000

Posted: **Fri Jun 14, 2019 6:46 pm**

russian wrote: ↑
Fri Jun 14, 2019 6:16 pm

JRD McLAREN wrote: ↑
Fri Jun 14, 2019 5:55 pm
Is (any) switching between LSU4.2 or LSU4.9 needed ..??
..or it is automatic ..??
OMG, we've forgot to make the checkbox visible in Tuner Studio. Here you are - https://github.com/rusefi/rusefi/commit/43acf4c3fc740fb204a3f89d848cdd3470ff115c

also there are resistors on the PCB. So, by default it's 4.2, now with the switch you can change to 4.9

I found something in my .msq file ..

Code: Select all

<constant name="cj125isLsu49">"false"</constant>

Posted: **Fri Jun 14, 2019 6:52 pm**

andreika wrote: ↑

Fri Jun 14, 2019 6:42 pm

4.2:

Code: Select all

EngineState: cj125: state=5 diag=0xFF (vUa=2.119 vUr=0.916) (vUaCal=1.501 vUrCal=0.909)
EngineState: cj settings: offset=0 P=0.02441 I=0.00762 D=0.00000 dT=1
EngineState: cj status: value=0.53 input=0.90/target=0.91 iTerm=0.53561 dTerm=0.00000

Thanks for reply.

So when I have ---
cj status: value=1.00 input =0.00/target=1.40 iTerm=2.35xxx dTerm=0.00000
then something is wrong ...

I can try to wire this CJ125 board as prometheus have it.

Posted: **Fri Jun 14, 2019 6:55 pm**

I know about (selection) resistors on cj125 board.
I have 2 LSU4.2 sensors, one LSU4.9 ..

and 5 assembled controllers ...

(.. so don't worry about it .. )

Posted: **Sat Jun 15, 2019 11:19 am**

Hmmm, how does the LED cause heater ohms to be wrong? AKA with LSU connected you have low ohms to Vbatt. How does the parallel high ohms cause a significant variation in measurement? I guessed the heater ohms, and entered aprox values into this calculator. What is the temp vs ohms curve for a LSU? How many degrees of error does about 0.06 ohms cause? http://www.sengpielaudio.com/calculator-paralresist.htm

: ohms.png (6.12 KiB) Viewed 22169 times

Please note that when all parts are not connected, AKA missing MOSFET and missing LSU, does not mean there is a problem with the PCB. I believe you are saying DIAHD is leaking enough mA to keep the LED bright. How many mA do you measure with a multi-meter? If the LSU is connected you will still have this leakage. So I think there is no functional problem with this. I think you are just trying to say the LED doesn't turn off, but it still works OK. Some LED's turn on with 0.01 mA or less. Others turn on with 1.0mA of current. We might need to specify a different LED, or we might need to increase the ohms of the LED resistor to decrease the LED current.

So far the only problem I have been able to identify is that the leakage of DIAHD may prevent the LED from turning off. I need additional information before I can suggest a solution.

I also do not currently have enough data to understand how or why there might be an ohms measurement problem. Can you tell me your heater ohms when hot? Can you tell me temperature vs ohms curve?

Posted: **Sun Jun 16, 2019 12:21 pm**

..it's too hard to me, to explain it in english ..

Posted: **Mon Jun 17, 2019 12:55 am**

I understand your request about the LED. I do not see the problem. I understand you want it removed, which of course is easy to do by simply not populating the components. Can you tell me the leakage mA that is causing the LED to be bright when you expect it to be dim?

Posted: **Mon Jun 17, 2019 8:03 am**

kb1gtt wrote: ↑
Mon Jun 17, 2019 12:55 am
.... I do not see the problem...

The problem is, parallel connection to sensor.
We don't need any kind of parallel connection to any sensor's pin.

I understand you want it removed, which of course is easy to do by simply not populating the components.

LED can stay on this place / board, but we need to redesign / rework they wiring.
Current wiring / connection is fail.

Can you tell me the leakage mA that is causing the LED to be bright when you expect it to be dim?

No, sorry. I have not enough time (and energy) to try to measure them.
(Yes, I have different FET, different LED parameters, maybe ... )

I'm repeat myself.
Current heater LED wiring is fail.
That `s my opinion.

You can ask someone other, for they opinion.

Posted: **Mon Jun 17, 2019 9:49 am**

I just added the below to the knownissues.txt document. It should be updated in the official repo once @russian gets some time to merge.

Code: Select all

19) D2 is reported to not turn off. It is believed the leakage of DIAHD pin is keeping it on even when the MOSFET is off. Unfortunately there is no solid math, or data to back this up. We need to look at what is required to make the LED blink, as well we need to look at the potential this parallel path is causing the heater measurement to measure wrong.

Please note I do not make changes because someone has an opinion about something. I make changes because I see a clear path of math, physics, etc. I do not have hardware or time to replicate the problem ans then analyse the issue. So unfortunately I will not be able to fix it any time soon

Thank you for the report. I'm grateful you were able to identify an issue, and raise a caution flag. raising a flag has made this board better. Please keep making great progress, and please feel free to raise more flags. Also please understand that when I ask for detailed information, I am not questioning you, I'm trying to understand the issue. I do not have your experience with this board, and I do not know what you have seen. Please keep in mind that I'm seeing this with a blind fold on, and I'm looking at it in 10 minute windows of time.

Again, thanks for the report, and keep up the good progress.

Posted: **Mon Jun 17, 2019 1:47 pm**

Ok, I'm understand ...

I will try to connect LED on FET's Gate, (not DRAIN) ..
and make some tests ....

Posted: **Mon Jun 17, 2019 2:47 pm**

JRD McLAREN wrote: ↑
Mon Jun 17, 2019 1:47 pm
Ok, I'm understand ...

I will try to connect LED on FET's Gate, (not DRAIN) ..
and make some tests ....

for more accuracy you removed LED and everything started working ???

what didn't work with LED on board ???
and what started working after removal LED ???

Posted: **Mon Jun 17, 2019 3:44 pm**

Heater can't start working ...
(duty cycle stay on 15%)

what didn't work with LED on board ???
and what started working after removal LED ???

I'm mean, CJ125 can't measure "right resistance value" of heater
(can't measure current heater temperature)
reported "overheat" maybe ...
and entered to "FAIL STATE" .

I don't know ....

but, I'm just remove R2 and LED and it started to work ... (but not successfully at this moment)
(it was my first try, to do something with "not working cj125 board")
(after backward engineering of cj125 board)
(and try to find, why heater led is still ON)

LED is connected parallel to heater .. in current cj125 board ( REV 0.4.1 )

Posted: **Wed Jun 19, 2019 11:38 pm**

CJ125 no longer available from US? https://octopart.com/search?q=cj125

Just placed an order for some from Poland?! https://www.tme.com

Posted: **Fri Jun 21, 2019 1:16 pm**

Hi all. This is my first post in this forum.

My goal is to build atMega and CJ125 based stand-alone controller for WBO probe. I had collected several reference schematics across the net, including the one from rusEfi repository. All of them shows the Rcal wire (the green one) is connected to the IA pin (pin 4) of the CJ125. The sensors I have does not have that wire, since the calibration resistor, which is slider-type, is inside the connector, and it is factory soldered at 62 ohms. The external resistor of the rusEfi board have the same value.
The sensor was tested with the controller of one of the popular high-end brands and it is working fine. I suppose it is also CJ125-based.
My question is what will happen if IA pin is left unconnected? Or something else, like pulled down to the ground or connected to the IP pin (pin 3)? If not, what is the approach to resolve that issue?
I'm browsing this forum for quite some time and I think the guys here are the most competent to answer that question. And I think it will be great addition to the rusEfi CJ125 board knowledge base.

Posted: **Fri Jun 21, 2019 6:29 pm**

Hello all, first time post. I've worked with the CJ125 for a while, casually (not professionally), of course. Recently, I wanted to buy more of the chips but was unable to find a vendor. I ended up contacting Bosch directly, and I actually received an answer!

"The specific part number you are requesting has been terminated and a new lead-free variant has been released to replace it. The part number you are will want to order now is: 0272 240 103"

0272240103 is for the LQFP-32 version.
0272240104 is for the SOIC-24 version.

My personal preference is for the LQFP-32 version but if the SOIC-24 version is the only one available for purchases in multiples less than 2400 (LOL) I may have to switch.

At the time I write this, Future Electronics actually has the SOIC-24 version in stock (Qty: 2399)
https://www.futureelectronics.com/p/semiconductors--signal-interface--specialty-interface/0272240104-7076626

Future Electronics lists the LQFP-32 version, but right now they don't stock it.
https://www.futureelectronics.com/p/semiconductors--signal-interface--specialty-interface/0272240103-2795789

Thanks!
Jeff

Posted: **Sat Jun 22, 2019 1:55 am**

Welcome along for the ride. Pleasure to hear from you. Thanks for the leg work on the CJ125.

Posted: **Sat Jun 22, 2019 1:57 am**

Реконструктор wrote: ↑
Fri Jun 21, 2019 1:16 pm
The sensors I have does not have that wire, since the calibration resistor, which is slider-type, is inside the connector, and it is factory soldered at 62 ohms.

Every one LSU sensor have they own unique calibration resistor ...

Posted: **Sun Jun 23, 2019 8:44 am**

JRD McLAREN wrote: ↑
Sat Jun 22, 2019 1:57 am

Реконструктор wrote: ↑
Fri Jun 21, 2019 1:16 pm
The sensors I have does not have that wire, since the calibration resistor, which is slider-type, is inside the connector, and it is factory soldered at 62 ohms.
Every one LSU sensor have they own unique calibration resistor ...

OK, why is that external resistor, then?

Posted: **Sun Jun 23, 2019 8:57 am**

...it is CALIBRATION RESISTOR ...

Every one LSU sensor is UNIQUE ..

CJ125 do the calibration automatically, and "read" this Rcal value,
for proper operation.

Try to look at any VEMS manual, and try to find something like " Free Air Calibration" ..
cause, VEMS use "they own" Lambda controller onboard, no use Rcal resistor (5 wire only)
and you must calibrate your LSU manually. (before use them)

Posted: **Mon Jun 24, 2019 11:33 am**

I'm asking about this resistor, what is its function?

: rcal.png (24.93 KiB) Viewed 21940 times

Posted: **Wed Jun 26, 2019 7:24 am**

R4 is not the calibration resistor. The calibration resistor is INSIDE the lsu4.9 connector, hence why there are 5 wires from connector to sensor, but 6 pins in the connector.

There are some docs here about the cj125 and LSU4.9 if you want to read more: https://github.com/rusefi/rusefi/tree/master/hardware/CJ125_board

Posted: **Wed Jun 26, 2019 7:36 am**

MHTSOS wrote: ↑
Mon Jun 03, 2019 10:24 am
If you run the engine for a long time without the sensor heated to its working temp it gets coated with a layer of soot/carbon just like the inside of your exhaust. Then when you eventualy power on the sensor heater this carbon deposits start burning off when it reaches over 500 C and this can damage the sensor.
By having the heater off for the first 10 to 30 seconds after engine start you wont get the sensor covered in carbon. If you have so much unburned carbon in your exhaust gasses then you have much bigger problems to worry about like your spark plugs shorting out all the time. I really think that having the sensor pre warmed is a bad idea.

Actually Bocsh has devised a desoot protocol for LSU4.9 by ramping up the temperature of a sensor for a short period to 870C to burn off contaminants. Please see patent US20140047912A1.

Posted: **Wed Jun 26, 2019 11:59 am**

mck1117 wrote: ↑
Wed Jun 26, 2019 7:24 am
R4 is not the calibration resistor. The calibration resistor is INSIDE the lsu4.9 connector, hence why there are 5 wires from connector to sensor, but 6 pins in the connector.

There are some docs here about the cj125 and LSU4.9 if you want to read more: https://github.com/rusefi/rusefi/tree/master/hardware/CJ125_board

So, in conclusion, if I connect the 5 wire sensor to the board it will works fine?

Posted: **Wed Jun 26, 2019 9:46 pm**

да... (edit: yes)

Posted: **Thu Jun 27, 2019 1:34 am**

JRD McLAREN wrote: ↑
Wed Jun 26, 2019 9:46 pm
да... (edit: yes)

Let me clarify a bit. The cj125 only works with the five wire, six pin LSU 4.2 and 4.9. If you have an LSU4.2/4.9 sensor with the six pin connector, that's what it supports. If you have something other than a Bosch LSU 4.2/4.9 sensor, it won't work.

rusefi.com

DEAD DESIGN rusEfi own wide band controller board add-on using CJ125

Re: rusEfi own wide band controller board add-on using CJ125

Re: CJ125 board

Re: rusEfi own wide band controller board add-on using CJ125

Re: rusEfi own wide band controller board add-on using CJ125

Re: rusEfi own wide band controller board add-on using CJ125

Re: rusEfi own wide band controller board add-on using CJ125

Re: rusEfi own wide band controller board add-on using CJ125

Re: rusEfi own wide band controller board add-on using CJ125

Re: rusEfi own wide band controller board add-on using CJ125

Re: rusEfi own wide band controller board add-on using CJ125

Re: rusEfi own wide band controller board add-on using CJ125

Re: rusEfi own wide band controller board add-on using CJ125

Re: rusEfi own wide band controller board add-on using CJ125

Re: rusEfi own wide band controller board add-on using CJ125

Re: rusEfi own wide band controller board add-on using CJ125

Re: rusEfi own wide band controller board add-on using CJ125

Re: rusEfi own wide band controller board add-on using CJ125

Re: rusEfi own wide band controller board add-on using CJ125

Re: rusEfi own wide band controller board add-on using CJ125

CJ125 part numbers

Re: rusEfi own wide band controller board add-on using CJ125

Re: rusEfi own wide band controller board add-on using CJ125

Re: rusEfi own wide band controller board add-on using CJ125

Re: rusEfi own wide band controller board add-on using CJ125

Re: rusEfi own wide band controller board add-on using CJ125

Re: rusEfi own wide band controller board add-on using CJ125

Re: CJ125 board

Re: rusEfi own wide band controller board add-on using CJ125

Re: rusEfi own wide band controller board add-on using CJ125

Re: rusEfi own wide band controller board add-on using CJ125