Has anyone used lambda to can for showing second lambda with v3? If yes, does it need some extra steps versus V2 and what Can speed it is working for you?
The CAN speed must be the same for the whole CAN BUS. So make sure that all devices works with the same speed (doesn’t matter what but must be the same).
Both base ID are supported in V3 (the same as V2) 0x664 or 0x644.
And that’s all.
I have set the speed to 500kbps amd with light client i changed lambda to can work for same speed. Can states no errors but lambda 2 reading stays at 0 at all time.
What is base id of tghe lambda cobtroller ? You chceck it with the light client
Ok we will check it. It for sur worked, but maybe something wrong happens
I have now tried with also 0x644 id, and new lsu 4,9 sensor. I also tried to change the speed back to 1mbps and output frequency to 20,50 and 100. and no luck with any of these changes.
We tested it on the car and we have no issue.
Please checkwith the light client the value for lambda that controller see.
Maybe there is an lambda error and lambda is just 0
Where can I check that?, can you show me your settings?
I have here car running with light client on and I can confirm that the lambda to can is working and the lamda is wotrking.
Please publish your base map here.
Maybe there are some CAN conficts or so.
We will test it on the bench
Here, thank you!
audi 2.7 pnp v3 map.emub3 (59.8 KB)
I use LSU 4.2 for the Black ECU + LSU 4.9 with Lambda to CAN. Using default values all poped up in the logs without any changes in the Light Client.
So there is something about it.
First it happened my Lambda to CAN hanged at nearly 1 - rock solid, but I did power cycle the Black ECU and it turned back, it happened once so I ignored it.
Today it happened again, but power cycle did not resurrect it. When I removed the fuse for Lambda 2 CAN the value changed from 1 to 0, so it was alive as a device and communicating with the Black.
I could not get it back to operate, so decided to plug the USB 2 CAN and try the Light client, et voila the Light Client connection “unblocked” the Lambda 2 CAN and the Black V3 software sees it back again.
And here hanging at 0,87 (fixed by light client).
I can upload logs if needed.
Are you powering up your lambda to can from emu 12v switched or directly from battery? Also is it sensor grounded or just to chassis?
If you can send me the map i could try it
So it’s getting interesting here.
To be clear on wiring - I have a dedicated Relay and Two Fuses for on-board Lambda and Lambda 2 CAN.
I tried to start the engine after few hours today and Lambda 2 CAN did not provide any values in the log.
So I tried to connect with USB to CAN and Light Client - it looks fine there, for a glance.
I power cycled the car and started the engine. Again nothing from Lambda 2 CAN (rock solid 1.0).
I was running the 5.0 FW in Lambda to CAN, so I upgraded it to 7.3 (latest available).
Again it looked fine in the Light Client, so I power cycled to start the engine, but an error appeared.
Afer 2-3 retries Light Client opened, but the state changed to something odd, attaching some screens.
Sometimes it was blank.
Sometimes it was with frames greyed out (and not changing). What is important to note, that after my first “reset” with connecting to Light Client, frames were alive and changing all the time (also in the LOG in Black the values appeared then).
I tried to downgrade to FW 5, but no changes (only FW5 shows Lambda 1 in the LOG, while FW7.3 shows 0 in the LOG).
The error with communication with light client appeared once or twice again, in general USB to CAN started showing errors (red LED).
That made me hard reset everything (disconnect Lambda 2 CAN from the wiring, disconnect car battery).
In general no changes, kinda faulty Lambda 2 CAN ???
And now to the MOST INTERESTING part.
I noticed that in the lower RPM I have some misfires. In general my tune is in very early stage, so everything is disabled. I operate TPS by my foot, ignition locked and changed by finger, only the VE map I use is used from the previous project.
You can notice the misfires by the Lambda 1 readings (obviously seen at the Tach and felt / heard).
At first I thought it might be my early tune, but I figured out a correlation that when Lambda 2 CAN worked fine, I did not get those misfires (that was some time ago, before I did all those tests). Those misfires happen when RPM <2000, above 2000 it’s not noticeable at least easily.
I tried different configurations - with USB 2 CAN connected (termination switch on). Without USB 2 CAN (terminator plugs at ends of the bus).
Finally I fully removed the “not working anyway Lambda to CAN” and to support my observations the misfires disappeared. I tried maybe 5-6 short runs idling at 1500-1700 RPM and ZERO MISFIRES.
Attaching one of those short runs without misfires / Lambda 2 CAN removed from the config and physically disconnected.
So what’s happening?
Attaching LOG where misfires are catched by Lambda 1 readings.
Attaching base map used.
20240602_2238_Lambda2CAN_not_working_Misfires_below_2000RPM.emub3 (57.6 KB)
20240602_2238_Lambda2CAN_not_working_Misfires_below_2000RPM.emublog3 (460.0 KB)
EDIT:
Attaching log of another short run WITHOUT misfires (no Lambda 2 CAN attached). Interestingly CEL came up here (sorry I’m not aware what it does and why it was triggered - maybe you can tell from the log).
20240602_2244_No_Lambda2CAN_no_misfires.emublog3 (65.7 KB)
EDIT2: From my head as I might forget it. When the Lambda 2 CAN was “in a working condition” sometimes misfire happened as well and was reported by both sides of the engine (Lambda 1 and Lambda 2). This really leads me to think Lambda 2 CAN is behind those misfires.
I show it to Lambda 2 CAN team on Monday.
1 Like
Hi,
First of all, you shouldn’t have any CAN bus errors in the Light Client. There is no point in looking into anything else unless this is fixed. The status on the bottom of the Light Client must always show OK.
Let’s start simple. Check if you have the correct CAN bus status when you are connected to the LambdaToCAN only. Supply the LambdaToCAN with power and connect only USBtoCAN and Lambda together. You must have 2 resistors, so one can be from USBtoCAN, and the second one has to be added externally.
That is OK. My bus is 2x 120Ohm terminators at the ends, using twisted pair of cables. EMU Black V3 and USB2CAN in the bus, where I plug USB2CAN instead one of the end 120Ohm terminators and switch set to 120Ohm - all green and amber, no red LED. Red LED only with the Lambda2CAN connected and… the first time I connected it with Light Client I did not notice anything strange (like the Red LED), second time all looked fine, bus speed autodetected at 1Mbps. Then those errors and messages started to appear in the light client. What is strange to me is that it used to work out of the box just like that (see my first post in this thread) and it kind of granually degraded. I verified all the connections and did not find anything suspicious.
Power supply is ok, you can confirm that im my screens above.
My educated guess now it’s more likely HW failure of the Lambda2CAN rather than the SW bug of the V3, but I can’t tell that.
Timewise I’m off for 2 weeks now (away from the workshop), but I can get you my Lambda 2 CAN module shipped if you want to bench test it.