sbn1979 Posted June 19, 2020 Report Share Posted June 19, 2020 Getting this error message when setting up can lambda, car was running before. Possible faulty coms port forces ecu upgrade so was working before. Quote Link to comment Share on other sites More sharing options...
Adamw Posted June 19, 2020 Report Share Posted June 19, 2020 We havent added the CAN bridge yet, it will be in the next release. You only need it if you are using more than one CAN lambda and need to reprogram them for different cylinders. Quote Link to comment Share on other sites More sharing options...
sbn1979 Posted June 20, 2020 Author Report Share Posted June 20, 2020 I’m only using one can lambda. And I’ve only selected one channel for Can comms so don’t understand why it’s saying this then ? Quote Link to comment Share on other sites More sharing options...
Adamw Posted June 20, 2020 Report Share Posted June 20, 2020 23 minutes ago, sbn1979 said: why it’s saying this then ? Why its saying what? You shouldnt even use the "Find devices tool", as I say it is only used to re-program the CAN lambdas. Quote Link to comment Share on other sites More sharing options...
sbn1979 Posted June 20, 2020 Author Report Share Posted June 20, 2020 But I’m using the find devices to see if the ecu can see the can lambda not to reprogram it, just as a test and I can’t even press find devices as it’s greyed out and says the above message. The can lambda has 12v to it can line has 60 ohms on it and I’ve tried reconfigure the can lambda to communicate on can2 but it’s find devices is greyed out and all I’m seeing is said message.... Quote Link to comment Share on other sites More sharing options...
Adamw Posted June 21, 2020 Report Share Posted June 21, 2020 18 hours ago, sbn1979 said: But I’m using the find devices to see if the ecu can see the can lambda not to reprogram it, just as a test and I can’t even press find devices as it’s greyed out and says the above message. The can lambda has 12v to it can line has 60 ohms on it and I’ve tried reconfigure the can lambda to communicate on can2 but it’s find devices is greyed out and all I’m seeing is said message.... Yes, the "find devices" tool is the CAN bridge that is used for re-programing, you dont need it. So what is the actual issue - is the Lambda not working? Have you set Lambda 1 in the analog menu to "Link CAN"? What does the Lambda 1 status runtime show? Quote Link to comment Share on other sites More sharing options...
sbn1979 Posted June 21, 2020 Author Report Share Posted June 21, 2020 Yes lambda is not working, yes set to lambda1 in link can. On the can staus everything is green and no errors. Everything seems fine just can’t get anything to display Quote Link to comment Share on other sites More sharing options...
Vaughan Posted June 21, 2020 Report Share Posted June 21, 2020 have you tested it with the engine running? The CAN Lambda doesn't start the sensor up until after the engine is running. It is also possible to send it CAN messages to make it run while the engine is off. Quote Link to comment Share on other sites More sharing options...
Adamw Posted June 21, 2020 Report Share Posted June 21, 2020 Please attach a log, the tune, and some photos of how the lambda is connected to the ecu. Quote Link to comment Share on other sites More sharing options...
sbn1979 Posted June 22, 2020 Author Report Share Posted June 22, 2020 9 hours ago, Vaughan said: have you tested it with the engine running? The CAN Lambda doesn't start the sensor up until after the engine is running. It is also possible to send it CAN messages to make it run while the engine is off. Yes always with engine running mate 9 hours ago, Adamw said: Please attach a log, the tune, and some photos of how the lambda is connected to the ecu. Ok mate will do today Quote Link to comment Share on other sites More sharing options...
sbn1979 Posted June 22, 2020 Author Report Share Posted June 22, 2020 Dave.pclx Quote Link to comment Share on other sites More sharing options...
Adamw Posted June 23, 2020 Report Share Posted June 23, 2020 Those two photos with the multimeter, do you have some higher res versions? I cant zoom in to see the details. The set up in your map looks correct but it is odd there are errors showing on CAN 2. Quote Link to comment Share on other sites More sharing options...
sbn1979 Posted June 23, 2020 Author Report Share Posted June 23, 2020 It’s not plugged into can2 it’s in can1 at moment , had to upload low res as the file limit size basically the multimeter is showing 12v power to the can lambda red/black wires can green/yellow is showing 60ohms so can line is good also Also pinned into the back of the can plug to board reading 60 ohms still everything plugged back in Quote Link to comment Share on other sites More sharing options...
Adamw Posted June 23, 2020 Report Share Posted June 23, 2020 The lambda appears to be working fine in the map you attached above. Its status says "disabled" which means it is waiting for the engine to start. Can you attach that log. Quote Link to comment Share on other sites More sharing options...
sbn1979 Posted June 23, 2020 Author Report Share Posted June 23, 2020 I’ll get that sorted today Quote Link to comment Share on other sites More sharing options...
sbn1979 Posted June 24, 2020 Author Report Share Posted June 24, 2020 log Log 2020-06-22 8;19;27 am_dave.llgx Quote Link to comment Share on other sites More sharing options...
Adamw Posted June 24, 2020 Report Share Posted June 24, 2020 You have Lambda 1 error = 16 heated too long. This error is generated when the controller applies power to the heater but doesnt see the temperature increase at the expected rate. The two most likely possibilities that can cause this error: The power supply circuit isnt adequate, there is too much voltage drop in the supply circuit. There is excessive inductive noise on the power supply which upsets the controller. This could be something like ignition coils, idle valve etc. So try running a couple of temporary wires direct to the battery, that will eliminate both these possibilities then start it up and watch the Lambda 1 error and lambda 1 temperature runtimes. If the problem goes away then you can look at the power supply closer. Quote Link to comment Share on other sites More sharing options...
sbn1979 Posted June 24, 2020 Author Report Share Posted June 24, 2020 So swapped the lambda sensor just on the off chance now fault code 54 any relation? Quote Link to comment Share on other sites More sharing options...
Adamw Posted June 24, 2020 Report Share Posted June 24, 2020 No, I dont think I have ever seen error 54 so dont know what that means. But the 16 suggests you have a power issue so the test I mentioned will confirm. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.