Jump to content

Link CAN gauge reading issue


AGalecki

Recommended Posts

Hello,

 

I cannot get my CAN gauge to read.

 

I followed the instructions in the manual. It is wired to CAN1/RS232

 

It has power and ground and powers up. CAN low/high is matched.

 

Followed the instructions to program and selected link in the app. 

 

Then selected the CAN Stream configurations in the manual and applied to the ECU.

 

It is still reading 0.0. Not sure what to troubleshoot?

Link to comment
Share on other sites

I think I know what I did wrong. I have two separate Deutsche connectors and I need to Y them instead. 

 

Both the gauge and the CAN/Lambda controller go to one CAN low/high?

17099306475483830081000169265164.jpg

Link to comment
Share on other sites

I believe I found the issue. Looks like I need a can Splitter

Part: LINK-101-0212

This will allow me to see the AFR on the gauge and the ECU?

 

Why was I not able to see the AFR when logging through the ECU? Do you always need the splitter, even to see it when logging on the ECU?

Link to comment
Share on other sites

14 minutes ago, Adamw said:

You would only need a splitter if you want to connect both devices to one bus.  It is fine to have them connected to separate buses as you have.

Interesting. Do you happen to know why it is not communicating? Each have a plug and play deutsch connector and have power. Gauge lights up, but nothing is communicating to the ECU.

Link to comment
Share on other sites

1 hour ago, Adamw said:

Attach a copy of your tune. 

Here it is. The ECU is not logging and the gauge is not putting out a reading, but it is showing in the ECU. Hopefully just needs to be input a little different because it is in two CAN connections.

Link successful cycle.png

Edited tune - Base map Mitsubishi EVO 7-8 7Bar PCB V1.5+ G4X Xtreme Plugin.pclx

Link to comment
Share on other sites

In your first post you said the gauge is connected to CAN1/RS232, but in your map "transmit generic dash" is set up on CAN 2.  Your most recent screenshot shows the lambda detected on CAN 1, and it is working in your map, so I assume that first statement is wrong?

Can you confirm that the gauge is connected to CAN 2.  

And it is only the gauge that is not working right?  The lambda appears to be working in your map.  

Link to comment
Share on other sites

6 hours ago, Adamw said:

In your first post you said the gauge is connected to CAN1/RS232, but in your map "transmit generic dash" is set up on CAN 2.  Your most recent screenshot shows the lambda detected on CAN 1, and it is working in your map, so I assume that first statement is wrong?

Can you confirm that the gauge is connected to CAN 2.  

And it is only the gauge that is not working right?  The lambda appears to be working in your map.  

Yes, when you said that the gauge and the CAN/lambda controller can be run as connected, I adjusted some stuff to try and get it functional without the deaustch splitter. Neither Lambda or the gauge are giving readings still. 

 

As previously set, the gauge was never going to work because it was in can 2 and not selected properly. The lambda should have shown in logging but wasn't and still isn't. Not sure what the issue is...

 

I was unable to see the Lambda reading anywhere.

I can play with it, but are you able to walk me through selecting the CAN 2 for the gauge? Or is it correct in the map currently? It is not reading as currently set. 

 

How do I get the lambda (more specifically maybe, the AFR) to show in the logging? It was not showing any data, even though the ECU is seeing it. AFR reads 0.0. Is the wrong thing selected to log?

 

Also, would like to confirm that the lambda reading will equate to AFR in logging? Not just a lambda value of 0.x or 1.x?

Link to comment
Share on other sites

The lambda was working when you last saved your map.  It will only give a reading when the engine is running.  You can look at the runtime "Lambda 1 status" to see what it is doing.  

10 hours ago, AGalecki said:

Also, would like to confirm that the lambda reading will equate to AFR in logging? Not just a lambda value of 0.x or 1.x?

You can display in AFR or lambda.  U key is the shortcut to change units.  

 

10 hours ago, AGalecki said:

I can play with it, but are you able to walk me through selecting the CAN 2 for the gauge? Or is it correct in the map currently? It is not reading as currently set. 

It is already set up correctly in the map you attached earlier.  If it is not working then there is either a wiring issue or the gauge is not configured correctly. 

Link to comment
Share on other sites

10 hours ago, Adamw said:

The lambda was working when you last saved your map.  It will only give a reading when the engine is running.  You can look at the runtime "Lambda 1 status" to see what it is doing.  

You can display in AFR or lambda.  U key is the shortcut to change units.  

Unfortunately the tuner I am using doesn't seem super familiar with the Link platform. He's tuned a lot of Link, but the interface to the devices doesn't seem super great. Can you screenshot where it is showing and how to select the lambda in the logging and toggle the type of unit displayed? He wasn't seeing it when we were trying to get the AFR to show.

The AFR average was just showing 0.0.

10 hours ago, Adamw said:

It is already set up correctly in the map you attached earlier.  If it is not working then there is either a wiring issue or the gauge is not configured correctly. 

I followed the steps in the provided instruction manual for wiring.

I have the gauge plugged into CAN 2 and used the plug play deaustch connectors just like I did in CAN 1. Didnt want to mess  with the wiring and even purchased the CAN plugs from Link. SKU: Link101-0197

 

They are plugged into: 

CAN 1 to the CAN lambda controller / Link wideband sensor

CAN 2 to the gaugd's deaustch connector

Only thing I did wiring wise was wire ground/power and they're on the same ground/ power source. The gauge comes on, but no CAN devices show in the CAN 2 devices page. The big difference noticed is the paper directions say set the ID to 56 and the ECU directions say 950.

Gauge is set to AFR and accepted the programming with Link selected as the ECU.

 

In logging, hitting U just changes the PSI to KPA. The Lambda Avg  on the right never changes. Just reads 0.0 AFR.

 

Lambda picture.png

Link to comment
Share on other sites

3 hours ago, AGalecki said:

The AFR average was just showing 0.0.

The CAN Lambda doesn't warm up and start sending out a proper Lambda value until after the engine is running.

For the gauge it might be best to set it up to show TPS or MAP initially as if Lambda is 0 in the ECU and it is 0 on the gauge you can't be sure that the gauge is working but if you have TPS or MAP showing on the gauge then you can immediately see if it is working.

Link to comment
Share on other sites

I was just replying at the same time as Vaughan, will leave it here as a bit of extra info.

 

2 hours ago, AGalecki said:

Unfortunately the tuner I am using doesn't seem super familiar with the Link platform. He's tuned a lot of Link, but the interface to the devices doesn't seem super great. Can you screenshot where it is showing and how to select the lambda in the logging and toggle the type of unit displayed? He wasn't seeing it when we were trying to get the AFR to show.

First lets confirm it is working.  If it was showing zero that suggests it is in error or the engine was off.  With the engine running, hit F12 or R to open the runtimes screen, use left or right arrow to move to the ecu status tab and here you can see lambda 1 status, errors, temp and measured lambda similar to below. 

To change units you just hit the "U" key on your keyboard.  If you are not using an english keyboard then there will be an equivalent key, but the other way to get there is to go via the menu bar >options>units>options

N33WKCx.png 

 

 

 

 

Link to comment
Share on other sites

3 hours ago, Vaughan said:

The CAN Lambda doesn't warm up and start sending out a proper Lambda value until after the engine is running.

For the gauge it might be best to set it up to show TPS or MAP initially as if Lambda is 0 in the ECU and it is 0 on the gauge you can't be sure that the gauge is working but if you have TPS or MAP showing on the gauge then you can immediately see if it is working.

Okay, I think I understand it a little more now. There is no device to register in CAN2. I am just pulling ECU data from it. 

I set battery voltage, coolant temperatures,  and air temp into the gauge and they are reading appropriately.

I also added Lambda 1 to the tuning and will see if it pulls it up.

Still not sure why AFR is not working on the gauge. It seems like I have it selected incorrectly and somehow need to set it... the battery and temp data popped up no problem and instantly after programming.

I set one of the gauge screens to Lambda 1 and will attempt to see if that works, since the AFR is not.

I now see what you're talking about with the U key (I was selecting the Lambda and hitting U, I believe that was the issue) I now see the units in the options and imperial was selected, but it is still reading Lambda.

Should I change the metric units to the imperial AFR to get AFR, if that is what I want it to read?

Link to comment
Share on other sites

1 hour ago, AGalecki said:

Should I change the metric units to the imperial AFR to get AFR, if that is what I want it to read?

You can set whatever combo you like.  Some users like temps in deg C but pressures in Psi and lambda in AFR for example, so they would likely choose the imperial set then just change temp units to C in the imperial set.    

Link to comment
Share on other sites

1 hour ago, Adamw said:

You can set whatever combo you like.  Some users like temps in deg C but pressures in Psi and lambda in AFR for example, so they would likely choose the imperial set then just change temp units to C in the imperial set.    

Thank you for all the assistance.

I selected Lambda 1 in the tuning parameters and set that on the gauge on the second page. Doesn't explain the gauge now working in my head, but the gauge and the tuning log are showing AFRs.

 

Lambda and AFR both are working on the gauge on separate gauge screens.

 

 

Working lambda and AFR.png

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...