Michal Posted May 11 Report Share Posted May 11 Hi, so I've read many pages about this topic and by now I feel quite dumb to ask again, but I can't seem to get it to work in my case. I have an X series inline wideband 30-0310 connected to a G4X CAN 2. I use a Link CAN cable with 4 pin DTM connector and wire it like drawn in this diagram: https://drive.google.com/file/d/1EvTB879acwCV6LzePVelw-yqbXJ_ChLU/view?usp=drive_link Because of the voltmeter readnigs, I guess that it is wired properly, as the values seem reasonable enough. In the CAN 2 and in the channel settings on my ECU I set it up according to the users manual: 500kbps, extended format, decimal ID 384. https://drive.google.com/file/d/13ES6ycWyHEFIUEjZFiIHPS_sSEuCDWLb/view?usp=drive_link From what I read in the PCLink help, I set up my Lambda 1 source to be CAN An 1 and I set the calibration to X series. In the stream settings, I used the "Load frame" option and loaded the X series template. I changed the parameter to CAN An 1 and based on another thread about this topic here in the forum, I took the advice that the Link lambda resolution is 0,001 and the X series has 0,0001. I set up the divider to 10 with hope, that it will work, but it doesn't. Pictures of the settings: https://drive.google.com/file/d/13EeNwjdblph919EaOGzckukcd2pJJuqO/view?usp=drive_link https://drive.google.com/file/d/13K2Pa8CLU7z07Q131zfVMcAOFb97edM6/view?usp=drive_link This is basically a cold start tuning. I allready got the engine to idle for a while, but I get no lambda readings, only the error value, so I now only test it with the "Run when stalled" option. Any suggestions where I might have gone wrong would be appreciated. Mike Quote Link to comment Share on other sites More sharing options...
keizsr Posted May 11 Report Share Posted May 11 Hello, please take a look at this setting. https://drive.google.com/file/d/10igocwuzd_PlHAt4rQVvvFLEJ_bNEATa/view?usp=sharing jdniss 1 Quote Link to comment Share on other sites More sharing options...
jdniss Posted May 12 Report Share Posted May 12 @keizsr's config matches my working X-Series config @Michal. Change your 'Frame 1' CAN parameter to Lambda 1 and add the divider of 10000 like he has: And your Lambda1 input needs to be 'Link CAN' same as his: Not sure that secondary 120 Ohm resistor needs to exist - the ECU should have one inbuilt - I only added a resistor at the X-Series end of my CAN wiring. Quote Link to comment Share on other sites More sharing options...
Adamw Posted May 12 Report Share Posted May 12 On 5/11/2024 at 10:06 PM, Michal said: From what I read in the PCLink help, I set up my Lambda 1 source to be CAN An 1 and I set the calibration to X series. In the stream settings, I used the "Load frame" option and loaded the X series template. I changed the parameter to CAN An 1 and based on another thread about this topic here in the forum, I took the advice that the Link lambda resolution is 0,001 and the X series has 0,0001. I set up the divider to 10 with hope, that it will work, but it doesn't. This is wrong. Go back to your stream 1, delete the frame, load the x-series template as is, you dont need to change anything. Then go to Analog inputs>lambda 1 and set sensor control to Link CAN. Quote Link to comment Share on other sites More sharing options...
keizsr Posted May 13 Report Share Posted May 13 Hello, there are multiple AEM canids. Have you tried them? link help can-lamda Set the CAN ID to suit the ID selected in the gauge. If the gauge is set to ID 1, enter CAN ID 384, for gauge ID 2 enter 385, ID3 = 386, etc Please check the manual for AEM 30-0310 Quote Link to comment Share on other sites More sharing options...
Michal Posted May 13 Author Report Share Posted May 13 Hey everyone and thanks for your replies. @keizsr I am currently using only one device and it's not a gauge just a controler - but the CAN setup should be the same. The setting you suggested and everyone else as well, I tried that the first time, as it seemed the most logical, but as it didn't work, I tried what I posted here. I somehow overlooked, that G4X has a terminating resistor, so today I rewired the CAN, so that the ECU is at the end of the bus (instead of the second 120Ohm resistor) and then changed the settings in the ECU as you all suggested. Loaded the X series template without any changes and set up the Lambda 1 to CAN Link. But even now, when I turn on the "Run when stalled" option, it still shows the error value 3.00 I had set previously. Any guess why? Or what value does the sensor show, when the engine is not running? Do I need to recalibrate it or something? Thanks for any help. Quote Link to comment Share on other sites More sharing options...
Adamw Posted May 13 Report Share Posted May 13 2 hours ago, Michal said: But even now, when I turn on the "Run when stalled" option, This option is only for Link controllers, the AEM runs anytime it has power, it has no ability to turn off the heater. Please attach a copy of your tune and a PC log. Quote Link to comment Share on other sites More sharing options...
Michal Posted May 13 Author Report Share Posted May 13 See them here. I checked again with the voltmeter after the rewire and it showed the same values that I meassured before. The wideband module diod is solid green. PC Datalog - 2024-05-13 7;47;12 pm.llgx Startup tune 240513.pclx Quote Link to comment Share on other sites More sharing options...
Adamw Posted May 13 Report Share Posted May 13 Your map is reporting bus errors on CAN 2. What ecu do you have? Quote Link to comment Share on other sites More sharing options...
Michal Posted May 14 Author Report Share Posted May 14 G4X Supralink non vvti Quote Link to comment Share on other sites More sharing options...
Michal Posted May 17 Author Report Share Posted May 17 Do you have any suggestions, where do I start my troubleshooting to get rid of this error? Any advice would be much appreciated, thanks On 5/13/2024 at 11:57 PM, Adamw said: Your map is reporting bus errors on CAN 2. What ecu do you have? Quote Link to comment Share on other sites More sharing options...
Adamw Posted May 17 Report Share Posted May 17 Looking at your map again I noticed the CAN errors being reported were transmit errors, not receive errors as you would expect. I loaded your map into a live ecu on the bench and got the same transmit errors. The only logic that I could fit to that would be "Lambda 1" has seperate receive and transmit runtimes so perhaps you manually selected the lambda 1 transmit runtime rather than just loading the AEM .lcs template which has the correct receive runtime? Anyway, by deleting that frame and loading the AEM template again your map is not reporting CAN errors for me now. So try loading the attached updated map in. Startup tune 240513 CAN reset up.pclx Quote Link to comment Share on other sites More sharing options...
Michal Posted May 17 Author Report Share Posted May 17 11 hours ago, Adamw said: Looking at your map again I noticed the CAN errors being reported were transmit errors, not receive errors as you would expect. I loaded your map into a live ecu on the bench and got the same transmit errors. The only logic that I could fit to that would be "Lambda 1" has seperate receive and transmit runtimes so perhaps you manually selected the lambda 1 transmit runtime rather than just loading the AEM .lcs template which has the correct receive runtime? Anyway, by deleting that frame and loading the AEM template again your map is not reporting CAN errors for me now. So try loading the attached updated map in. Startup tune 240513 CAN reset up.pclx 476.07 kB · 1 download When I open your file it doesn't show the transmit errors you mention, but when I connect the ECU, I see that it shows Bus Warning, Error Passive and Transmit Error Counter is 128... Even after I download your file into the ECU and store it, it shows again, the same errors as before. I also tried to delete the stream and just open the AEM.lcs template as you say you did amd it shows the same thing. So did I wire it wrong? Quote Link to comment Share on other sites More sharing options...
Michal Posted June 5 Author Report Share Posted June 5 Hey guys, I let it rest for a bit, vent on a vacation and when I got back, I redid the wiring from the top, no error reports now and when I turn the engine on the sensor works just fine. Thanks all of you for your feedback and input 🙏🏻 the final problem was in a faulty wire... keizsr 1 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.