Adturb

I've had a reply on another forum and someone is successfully using the Adafruit AD 8495 board, after a minor mod to rescale it for 0-1000 Deg C. As the output is a linear 0-5V I can't see why it wouldn't work? Ads

OK, so as per the title. I have a Defi EGT sensor and gauge, but as I've got a CAN display in the car I want to remove the gauge and put it through the ECU for display and logging purposes. Now I thought that it would be as simple as hooking it up to an AN Temp input, but after a bit more reading a thermocouple generates a voltage (55uV per degree C, as far as I can see for a k-type), rather than a resistance, like an IAT does. Traditionally a thermocouple would be wired into an adaptor/ amplifier (I saw a PLX Devices adaptor mentioned in a post referring to ViPec 44) to give a linear 0-5V, with temperature compensation of sorts, output which can then be scaled on any AN V input, just like an external wideband. There is Raspberry Pi K-Type adaptor/ amplifier which is VERY cheap, I'm wondering if this would do the job? However, the PC Link help file indicates to me that it can potentially take a thermocouple input directly? I know the Thunder can, as well as wideband, but I'm running a PNP EvoLink G4+. I'm a little bit frustrated as I though this would be as easy as pie, but the more I've read, the less straight forward it appears to be. On the upside it's quite interesting!

Thanks Guys, noted for future! Has this changed- or have I always needed to deliberately save the log files when using the laptop?

Bit of a basic question- previously when I've logged using the PC the log has been automatically saved in the 'Logs' folder within the 'Link G4' folder. I've just done some logs and I can't see them on the computer, so do they need to be manually saved with the current version (5.6.4.3229) of PCLink?

You can run multiple devices- BUT you need to have 'ends' on the bus. The Link is one 'end' as it has a 120 Ohm resistor on board which is fixed. A lot of the aftermarket gear will either have a fixed resistor, or may have a switch for the resistor to blow it to be removed, but you can't have more than 2 in total, and they need to be at the ends of the chain. The help file has some good diagrams & info, and if you google CANBUS it should pull a wiki page that details a multi drop network. Next step is then identify if the devices have resistors and if they can be switch off/ removed. Obviously each device needs to have a different address. Hope that helps?!

Did you try to change the trigger offset to 180?

Couple of plans of attack here- I scale mine inversely (0v = lean/ 22AFR, 5V = rich/ 8AFR) so if the MXTL dies then it'll overfuel rather than run lean. The ECU can be set to work on a narrow range, as most sensors do- 0.5 to 4.5V, either side of that (0 or 5V) will register as a sensor fault- I tried this but kept getting false ECU alarms, I don't think there is a time delay on the alarm so it activated each time the car started. Thirdly when you set up closed loop it is only active under certain conditions, typically cruising/ steady throttle. Furthermore there is trim limit, so it can't or subtract more fuel than that setting- I think I set mine to 8%.

Last edit- changed the ID from '1792' (which is specified for the 300 and 500 series) to '1000' and it's working! Only thing not displaying correctly is the Lambda, I suspect it's a math problem as the value is changing- but I'm sure my car isn't running 6-7AFR

Hi Scott, I have made up my own lead and plug for the uSDM, but I am really struggling to find THE pin out for my EvoLinkIX CAN Plugs- there is no info in the help file. Looking at the following link http://www.vi-pec.com/techdata/accessories-manuals/can-catalogue I believe that I have used the yellow for CAN H (White on the lead, goes to pin 3 on the ALTW plug) and Blue for CAN L (Green on the lead, goes to pin 4 on the ALTW plug), hence I've ended up with the attached image. I have tried to swap the H and L wires on the off chance this was wrong, but still no comms. I have followed the PLEX instructions for setting up comms, but it's not talking!? edit: I have subsequently found this thread http://forums.linkecu.com/index.php?/topic/1869-where-is-serial-connection/#comment-24947 so it looks like I DO have it correctly wired. Really would be a good addition to the excellent help file!

Magic, just what I was after Thank you!

I recently realised that since doing an update (not sure which one exactly) I no longer have my fuel or ignition table AND a graphical 3D view of it in another window to the side. The current base link layout does have this, but I can't see how to add it as separate window (or essentially a second table) to have up next to the main table. Can you advise how to add it as I can't see a way, all I can do is toggle the table between numbers and graphical view? I guess worst case will be adjusting the current default layout to match my custom one?

I have a suggestion regarding the GP output selection- It would be great if you could select a specific GP output, rather than just a condition, > or <. Likewise if you could select a state, such as anti theft (this isn't a drop down option), being active, as you can when it's not set to GP. I was hoping to program an existing dash light output to flash when the Anti theft was active (if the car won't start it'd be nice to know it's not the ECU deliberately holding it off, likewise if a GP RPM Limit was active). I would do it by changing the output that's already set (e.g. CE Light) to a GP output, then ideally set condition 1 to CE Light and then condition 2 to a virtual aux, which was set to a timer and anti theft (assuming I can make the virtual aux timer oscillate?). The other request is for the shift light to be on a 3d table (gear Vs ECT) so the light will come on in correlation with the RPM limit table. Or as per my above request, it could programmed to shift light or RPM limit. Hope that makes sense!?

The Delphi coils are direct equivalents for the Denso 02240 coils- so same plugs, shape and wiring buuuuuttt they're easier to get hold of (for me) and as a further bonus, are cheaper. Edit: I received a response from Delphi regarding dwell times for their GN10312 coils (Denso 02229 equivalents) and they are: Battery Voltage (V) Dwell Time (msec) 8 5.60 10 3.40 12 2.48 14 2.00 16 1.65 18 1.42

The attached table is what I'm using. No issues to report. I have also moved away from the Denso coils to Delphi GN10312's. I'm able to source these far cheaper and again, no issues to report!

Dont suppose you know the make/ part number for the round CAN/ programming connector too?

Ok..... So which variables do I need?? As put in my initial post it has pointed me to the fuel table and target table. I believe I have found the fuel table (fuel table 1) but can't find any variable that sounds like target table.

Thanks for the reply. I do know it works with laptop logging, but was curious if it can be done by ECU logging alone

I was curious- is it possible to ECU log the necessary parameters to allow the mixture map to populate? After uploading the log from the ECU I then right click the mixture map and hit 'update'. All I get is a message saying 'Log file error: Fuel table parameter missing. Target table parameter missing.' I am logging 'Fuel Table 1', but when I search for 'target' there aren't any obvious parameters to add?

The BTI gauge looks cool, certainly not something I've seen elsewhere. I'm itching to get my hands on the new Plex uSDM http://newplexmicrodisplay.instapage.com I think I'm right in saying- coolant temp, RPM and boost should all be monitored by the Link already. Oil temp and pressure will need extra sensors if you want to log via the ECU. I'm sure your Link dealer will be able to get a pair of suitable pressure and temperature sensors for you? Then program the calibration table and add it to the logged parameter list.

Am I right to assume that I'll need a CANPCB lead to go from the ECU and a CANF plug to connect that to the display?

I don't know about the Fury and Thunder, but in the Extreme's Closed Loop settings there is 'FTrim Limit +/-' so the ECU won't compensate past that level.

I have the MXT-L and I'm very happy with it. An advantage over the LC-2 is that when calibrating you can see what's going on, not to mention the option of seeing that all is well when using the car. I've mounted mine in the glovebox so it's not on display at all times

Could be worth posting up the map file. Im I'm fairly sure that Evo 4-9 use a 6kHz narrowband sensor.

I've seen the new uSDM online and it looks like a great display to replace my gauge setup without dominating the dashboard. Is the G4+ going to have CAN protocol in place to work with it?

First off check the inputs are set correctly, the use the test output to confirm the ECU has control (also proves wiring and the pump itself). You may also find that Mivec isn't working. Use the runtime values window to verify. Digital input 8 is the auto input but needs the pull up resistor to be on and set to falling edge. if Mivec isn't working check the pull up resistor is on for digital input 1.