Funkyflynz
-
Posts
15 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Gallery
Blogs
Posts posted by Funkyflynz
-
-
Hi,
I recently installed a Link CAN Lambda (Link module) and can see that its working, the ECU (G4+) was set to use CLL but didnt have anything connected, anyway i can now see target AFR vs actual and it was off with the engine at normal operating temp, around 12 when idling.
The fuel trim settings for CLL were stock wide band setting, i.e 15% for fuel trim and its maxing out. I changed the fuel trim limit to 25% and after about 2-3mins saw the AFR's at idle matching the target of 14.7. 25% seems excessive so went back to 15%. BTW this car have seen a number of track days prior to installing the Lambda sensor and ran like a champ.
Anyways thats a bit of background in hope that it helps diagnose this rev hang issue im now having since installing the Lambda sensor...
Once up to operating temp (CLL ECT lock is 80deg) the car will idle at 950-1050 nicely, but if i give it a few revs it will come back to 1450ish and hang there for 20-30secs before dropping back to 950-1050.
Any ideas what might be causing this?
Thanks
-
Hi,
Ive recently setup the LINK CAN Lambda, the G4+ is now seeing the Lambda module and PC Link is displaying Lambda data, great :-)
I would now like to get the AFR displaying on the Link AIM Strada 1.2 dash.
However in the Racestudio app under ECU Stream of the 41 enabled channels (max 120) i only have "AfrTarget" and "ECU WBO2 LAM2" in relation to AFR. Im not sure where these 41 channels are set and how i can change them, any help to add my Lambda data would be great.
Lee
-
On 5/11/2020 at 10:29 PM, Adamw said:
It looks like it is still there to me. Were you logged in when you looked?
Valid, i obviously wasnt sorry. The file is available.
-
On 3/15/2019 at 10:01 AM, Adamw said:
You can only send out a max of about 50 parameters. Im working on more configurable templates and a video for both ends at the moment that will make it easier for other users in future, but it is only a spare time thing for me so could be some time off. If you attach your dash and ecu files I will set it up for you. Once you have seen my changes you will probably have enough info to make changes yourself.
Hi Adam, any chance you managed to get this video done?
-
On 8/4/2019 at 8:52 PM, Adamw said:
I never got around to doing that video sorry. There are a couple of good Motec webinars that will be worth watching just to learn the basic fundamentals of CAN. I will give a bit of info here to try to help make sense of it. Post any questions you have after having a go.
First, the old Link "generic dash stream" and the new Link AIM MXS strada dash stream are basically identical, the only change made was the scaling of the Lambda channel - this was changed to allow the dash to work out of the box with both G4+ and older G4/G3 ecus without a config change. So if you want to see how the message is formatted, look up the Generic dash stream in the help file.
Most commonly in OEM applications CAN messages are simple single frame messages, what that means is every frame is sent with a unique ID. A frame is usually 8 bytes of data. In motorsports it is more common however to use what is called sequential or compound messages so you can send multiple frames with just 1 ID. The Generic dash/MXS stream uses the compound message technique. In this stream, there are 13 frames of data sent using just 1 ID. To allow the receiving device to know which frame is which once it gets to the other end, you use one of the data bytes in each frame as an index or identifier.
To confuse matters many manufacturers also use different terminolgy to name all these parts - the formats, ID's and even how bits and bytes are numbed, etc so it often can be a bit of a challenge to understand for a noob at first glance but it is actually quite an easy communication technology once you know the basics. Most good software nowadays has some kind of visual representation of the message which makes things easier.
Some examples of the differences I will show below. AIM call a compound message "enable row counter", some manufacturers call it a multiplexed message. AIM call the identifier/index byte a row counter. You will also see in the pic below their bit numbering is done differently to Link's too.
I have attached a configurable version of the AIM stream for the ECU and the dash. To see this in the dash you import it into the "CAN Builder" which is the seventh button from the top left in RS3.
Edit, added later: I forgot to mention byte ordering. A byte can represent a decimal number from 0-255. Stuff like ECT for instance that only goes from 0-120C can use just 1 byte. If you need to transmit a number bigger than that then you need to spread it over more than one byte. 2 Bytes allows 0-65535 so is enough for most automotive stuff. When you have more than 1 byte then there are two ways you can place those bytes into the frame, you can have the big byte first (called Most Significant first, Big endian, or Motorola format) or you can have it last, which is refered to as Least Significant first, Little endian or Intel format. The Link MXS stream uses LSB, you can see on the left side of my screenshot above, AIM call this "Low to High".
LINK_Generic Custom_@20170524_021339_007952.xc1 188.41 kB · 33 downloads Configurable Generic Stream MXS.lcs 5.77 kB · 24 downloads
Hi,
Im looking to add more than the current 40 CAN channels my Link MXS Strada 1.2 dash can see from the ECU (Link G4+ Extreme)
Im assuming this configurable file would allow that but its unavaialble?
Am i able to get a copy please?
-
22 hours ago, Adamw said:
Beep it out with a multimeter, check CAN H is the same pin on all plugs and CAN L is the same pin on all. There was someone on this forum a little while ago that got one of those that nzefi cables with one plug mis-pinned.
Nice one Adam, that's exactly what the issue was, the CAN Hi and Lo were terminated incorrectly on the short tail. Called NZEFI and they said either send it back or switch the pins, I decided to switch the pins. Now I have both the Lambda and Dash working, brilliant. Now on to the next question..... LOL Thanks Again for the reply on a Sunday night mate.
-
Hi Adam, its the old Red Xtreme model.
In the interests of keeping things neat and tidy i brought the NZEFI duel device cable. Problem is whatever i plug into the short tail (Link AIM Dash or CAN Lambda) doesn't seem to want to talk to the ECU. When either device is plugged into the long tail it seems to work. Strange.
-
On 1/20/2020 at 12:23 AM, VR4G63 said:
Hi Guru's,
I have recently connected my Link Aim mxs dash to Link g4+ Vr4 ecu and both Link dash and Link can Lambda don't get along, on can 1 both on same can but different ID on each of their own channel, but only one will work but not together, have tried different bit rate and still the same issue, dash comes on and off but reads the same as ECU?
Any Solutions for this issue our there ?
I'm running the same as per the picture.
This is the same issue i am having, I'm using the NZEFI multi device cable, and whatever device in plugged into the short tail doesn't seem to talk to the ECU.
Did you find a resolution?
-
15 hours ago, Adamw said:
The CAN bus itself can actually be very long, but the length restriction comes from the "stub length" or "spur length", which is quoted in many standards to be 300mm max.
In your case you now have the ECU at one end of the bus and the dash at the other end so effectively if you connect the Lambda in between it will be considered a stub. Something like below
However as a general comment the Link stuff seems to be fairly error tolerant and I think most of those standards are very conservative, I have never had any drama with longer stubs so Im pretty sure you would get away with the "double adapter" and a 1.0 or 1.5m stub as you planned. I just cant guarantee it as I usually try to follow the rules so dont have enough experience at breaking the rules... Having said that, many competing ECU brands now sell the "CAN hubs" which break most of the CAN rules but still seem to work.
What ECU do you have, does it have a 2nd CAN port? Do you have any ability to do some basic custom wiring (like crimp tools to crimp a plug onto some wires) or have any contacts that can? Where abouts are you in NZ? I will make a suggestion on some other options based on the answers to these questions.
Thanks mate.
What ECU do you have, does it have a 2nd CAN port? G4+ Extreme, only has a single external CAN port.
Do you have any ability to do some basic custom wiring (like crimp tools to crimp a plug onto some wires) or have any contacts that can? Yes no problem on this front.
Where abouts are you in NZ? Im based in New Plymouth.
Thanks
-
Hey guys, have a g4+ with the plug in can connection, im currently running a Link AIM Dash (mxs) from this connection using a 1.5m cable from NZEFI.
Im now wanting to install the link Lambda kit which runs over the can bus. NZEFI have a duel device cable with one short tail amd one long tail, but im told you cant plug an extension into the short tail as this will mess up comms.
This is a problem as my dash is a good 1m+ from the link ecu and the lambda sensor will also be 1.5m+ from the ecu.
anyone had experience with can cable lengths to multiple devices?
another option could be to buy or make an extension cable for the lambda sensor to the lambda can module, the sensor link uses is a bosh LSU 4.9 unit with An approx 300mm tail I believe.
thoughts?
thanks
-
1 minute ago, josey said:
oem, i mean factory dash, car original dash?
Oem dash doesnt display the info i want. Also the car is an LS swap and the oem guages dont work very well
-
Thanks for the reply guys,
the reason is a 2nd hand tablet is $100-200. It saves me $500+ that i can use for other important things
-
2 hours ago, paulr33 said:
Plex usdm 102 and be done with it, no need for any displays or tricks. Just raw CAN and fully customisable. I did a thread on it the Vipec section
Thanks, but im not looking to spend that kind of money, maybe one day further down the track but right now im cash strapped. So a cheap $150 tablet is what im looking at
-
anyone have an update on what tablets are currently are good option, finding something is doing my head in lol.
It would be great if someone with a tablet using the tuning cable could make a video showing what they have to do each time they start the car, i.e. do you have to turn the tablet on, then start the application, then wait 30sec for the application to sync? Just looking to get an idea of whats involved and the time it takes.
Rev hang?
in G4+
Posted
E36LS1-log to link.llgHi there,
Ive attached the tune and log from today. Once the CLL is activated (above 70deg) you can see it is maxing out to 20% trim to try and reach Lambda 1. In the log you will see that the rev hang gets worse as the car hests up, below 80deg its not really an issue, above 90 is when you see it hang. At the end of the run i unpluged the Can Lambda to see if that made any difference, this made a huge difference, the car just hung at 1400rpm, it never came back down.
The only other thing i changed was the time to live, it was zero and i changed this to 10sec. I wouldnt expect this to affect this idles issue though?
Thanks for your help
E36LS1-26-5-20.pclr
Log file attached...
E36LS1-log to link.llg