-
Posts
5,120 -
Joined
-
Last visited
-
Days Won
114
Reputation Activity
-
Simon got a reaction from Davidv in G4x Base map
For those looking for a base map to have a play with.
Software can be found at http://www.linkecu.com/pclink/PCLink 6.15.15.exe
Monsoon FW 6.15.6.pclx
-
-
Simon got a reaction from koracing in MR2/ST205 and Knock
It would actually be a huge task to implement this due to the way the code is written so will not be happening on the G4+ platform.
-
-
Simon reacted to Adamw in Wire type and sizes
The Link looms use a Japanese standard thin wall automotive wire known as "AVSS". It has a higher temp rating (120°C) than common PVC insulated wire.
Most of the wires are 0.56mm2 from memory except for the two main grounds and the main red 14V wire, these are 0.75 or 0.85mm2 (sorry I cant find my old spec sheet).
If you are in USA, a very similar alternative would be 20AWG TXL for the small ones and 18AWG TXL for the power/gnds.
-
Simon got a reaction from cubeqtio in Evo PnP with Turbosmart E-gate
I would say unknown at the moment. It looks to need a heap of current to operate so we would have to use a solid state relay as none of the ECU drives will do 20A
There is also position feed back which currently we have no strategy directly for.
-
Simon reacted to Adamw in HELP - Setup AEM CD7 Dash with Blinkers through BPM analogue to digital converter and Link G4+
Ok, all the CAN is done, I havent added any of the new channels to displays or whatever but they should now be available. I have kept all the channel names pretty much as per the BPM datasheet.
The only one that is a bit ambiguous is Fuel level. He has used 2 bytes like it is expected to cover a large range of numbers but then says the range is only 0-53L. Just one byte can do up to 255 and 2 Bytes is capable of 65000. So I suspect he might be sending it as "0.1L" rather than whole Litres but that is not clear. If your fuel level says "500 Litres" when you have it all working then set the scalar to 0.1.
Marvin-LinkG4UpdatedV2Port2CAN Adam.aemcd7
-
Simon reacted to Adamw in HELP - Setup AEM CD7 Dash with Blinkers through BPM analogue to digital converter and Link G4+
Yep sounds like you got it. Here's a quick demo: https://1drv.ms/u/s!AiYbYlZQuRHPqylX67m5Oo57-JVv?e=t3SK3f
-
Simon reacted to TechDave in OBD II Android is a Joke! Seriously??
We have a really nice colour display:
http://dealers.linkecu.com/MXS_street
Completely customisable, you can display any parameter inside the ecu over CAN Bus.
-
Simon got a reaction from Bculp7 in Aem wideband throws code 26
You will have to move the fault voltage as it will be reading full scale at start up. Set error Low to 0V
-
Simon got a reaction from Ducie54 in Map Limit didn't engage during Shift Cut
Hi CJ
The Gear cut takes the higher priority over just about all other limits.
A hard cut on the fuel will be higher priority so if you set the map limit to have the hard cut on then when it then hit the hard limit it would then over ride the gear cut.
Regards
Simon
-
-
Simon reacted to Adamw in Link atom to motec SDL dash?
Attach your ecu and dash config and I will set up the comms.
-
Simon reacted to Adamw in Link atom to motec SDL dash?
Try these.
H8SR2071019 with CAN dash.pclr Dashmuckingaround CAN setup.U16
-
Simon reacted to Brad Burnett in link ecu tps not reading when starting the car
@Khaled Abdurhman What vehicle do you have? Some vehicles tps is only an idle switch and wot switch, for example early model MX5 miatas.
-
Simon got a reaction from Supra Scotty in G4 storm, possible faulty map sensor?
First step will be to get the PC link tuning software connected to check what the MAP sensor is reading at key on engine not running.
Fault 10 and 11 both relate to AN volt 1. It is indicating its at either ground or 5V it cant be both at the same time so there might be a setting issue.
-
Simon reacted to Adamw in launch control setup - Subaru STI V7
You didnt have a non driven wheel speed set up so that is why speed deactivation did not work.
As far as I know the V7-9 does not have a clutch switch connected to the ECU so I have set it up to activate the launch limiter whenever speed is <10Kmh, using virtual aux 1.
I have thrown some rough numbers in there as a starting point, it is up to your tuner to keep an eye on things and fine tune it. I have set the launch to 5500RPM, ign at 10ATDC and 10% extra fuel.
Make sure you pray to the Subaru transmission god before every launch.
LaunchControlsetupfile Rev A.pclr
-
Simon got a reaction from ZipTieTECH in G4+ NS15+ Barometric pressure sensor tuning
The ECU has a dedicated baro sensor on board this is displayed as BAP in the runtimes.
-
-
Simon got a reaction from Sven in Matching wire for flying lead harness.
AVSS is what the wire is not ADSS.
http://prd.sws.co.jp/cables/en/avss.html
-
Simon got a reaction from Ausmoo2 in WRX phantom RPM limit problem
It is likely getting noise on the trigger signals so could be a coil breaking down causing noise and then the RPM error.
I'm assuming this is an older install and it has developed over time.
-
Simon got a reaction from Serkan in Problem with random E Throttle fault code 76
@Serkan Thanks for getting back to us with that info. Good to know it was resolved.
-
Simon reacted to Serkan in Problem with random E Throttle fault code 76
Hi sorry for being late to reply. In both my cases I concluded that there were problems with the wiring. In the first car, there was a problem with the solder of the sensor ground, in the second car the throttle plug was not seating fully into the socket. In both cases there was electrical continuity most of the time but from what I understand the e throttle system is VERY sensitive. The solder problem and the problem with the plug were randomly creating just enough resistance to trigger the fault. Fixed the problems, re calibrated and no more faults ever since. Hope it helps !
-
Simon reacted to Adamw in RPM 65535
No, the dwell scatter is a symptom of a trigger error. It means the ECU isnt receiving the regular tooth pattern that it expects from the trigger.
As I said earlier, the quickest way to find your problem is to get an oscilloscope capture of the triggers - preferably when it is playing up. The Oscilloscope will show us what is wrong with the waveform and this will usually give you some strong clues what is causing it. Do not waste time changing random parts - there could be many hundreds of different scenarios. Your logs show the ECU is not happy with the trigger so you need to start by diagnosing what it is about the trigger signal that the ECU it is not happy about.
-
Simon got a reaction from Spyrosgeo in Extreme g4+ red can bus 2
The Red cased Xtremes did not have CAN 2 they only have CAN 1