DSORDA

That's fine Adam, I can appreciate that. Just wanted to rule out it wasn't something as simple as a setting that I had mucked up. Everything reads as it should so I'll leave it at that and report back if something fishy does pop it's head up later on down the track. Thanks for the help as always Adam! Legend

Tried receiving messages 601 and 602, but still had the same errors. I checked the bus resistance at the plug going into the TCE4 (with everything shutdown) and it was only reading 100.5ohm. Potential issue there?

Thanks for the suggestions Adam. I went ahead and unplugged just the EGT box, powered everything up and no errors would reappear. So that's a start. Will measure resistance and report back

Hey guys, Having a wee hiccup with my CAN settings. I swear I just need to sit a CAN course and get my head around this stuff! Previous setup with Link Fury, Motec PDM and Motec Keypad, all working faultlessly on CAN2. Was running an older style AIM Strada dash on CAN1. Now, I have upgraded to a Motec C127 dash, and added a HV Electronics CAN EGT box to CAN2. Nothing on CAN1 anymore. I have uploaded the generic dash stream so I can change around a few of the things I want to display on the C127, and at the moment, everything displays as it should, and the EGT readings are all coming through to the Fury and reading correctly. The odd issue I am having, is when I watch the runtime values, about 2-5minutes after powerup, I will get a "Form Error" alert and after about the same time again, some subsequent errors. Have I simply messed up a CAN ID for the dash or HV EGT? I have tried running the generic dash setting on Channel 1, no difference. Also tried matching the transmit rates of channels 1&3 to 50hz for the different streams and no difference. And finally, tried setting the generic dash frames to be MS first byte order first, and although it put all my dash display readings up the wack, still didn't remove the form error. What am I missing here? I feel like it is right in front of me and something simple. CAN settings attached. Any help would be greatly appreciated as always! CAN Form error.pclr

Many thanks for this Adam, will get this loaded up and have a play. Appreciate your help!

Ok, launch RPM shouldn't be too critical. Might just end up getting a knotched 5v switch in that case. Can you give me any hints to set up sending the CL Fuel trim percentage over CAN?

Here you go Adam Quentin Dash.zconfig

Hey guys, just trying to add a few parameters to view on a Link/AIM MXS Strada dash. I have already had a play with the CAN setup and changed the Inj Duty Cycle (Sec) at the Link end to send ethanol content instead, and this works well and shows up on the dash. I'm now trying to display the "CL Lambada Fuel Correction" percentage, as well as the "Launch RPM" but can't quite get it right. I have the Launch RPM adjustable via a 0-5v pot without any knotches/clicks, so it would be good to view the Launch RPM on the dash as the dial is turned. I've tried changing some of the other unwanted parameters used over CAN, but with no success. Any change you could take a look Adam? Ideally, I would like to display them on Page 4 of the AIM pages, as it's a diagnostic page for trouble shooting. Speed and IAT to be replaced with Launch and Fuel Trim. Cheers Ian Quentin E85 Otago.pclr quentin dash.aimcfg

Hey Guys, Just brainstorming at the moment to help my friend best setup his G4+ Storm in his Evo5 rally car. He will be runnning BP98 as well as E85, but also with and without a turbo restrictor for various events. Obviously will be running an ethanol content sensor, and DI inputs are plentiful. There will be 4 scenarios as I can see it: BP98 + Turbo restrictor BP98 + Unrestricted turbo E85 + Turbo restrictor E85 + Unrestricted turbo I had originally invisioned setting up a DI for dual boost tables (restrictor fitted/not) and another DI for dual fuel tables (BP98/E85) I can already see flaws in that proposal though, such as blending the fuel maps together on E85, and the possibility of wanting to alter ignition timing when the restrictor is fitted/unfitted. Any thoughts and input as to how it should be best setup would be great. Cheers Ian

Thanks Adam, I was met by a prompt stating I required the latest version to connect as you said

If I use the PClink 5.6.5 software and try to connect to an ecu with the 5.6.6 firmware, will I be locked out with the possibility of loosing my current .pcl file? I had my car tuned around the time the 5.6.6 software was released and pretty sure my tuner updated the firmware before tuning. Car runs great, but I wanted to fiddle with some of the launch control settings before an event, but just want to make sure I dont get locked out by trying to do so.

Funny you say that. There would be times where you would power on, and it would display no values from the ecu at all. Then power off, power on and it would show the "snipit" value. I've conceded defeat, and ran a seperate cable for the dash to the CAN1 port of the ecu. Powered up and displays everything perfectly as the last time it was wired. PDM and keypad run off CAN2 and work perfectly as prior, all keypresses configured in the Link fine. We had wondered if it were something to do with the Link and Motec being 1m/500k. Everything in the PDM software and PClink showed no errors on the Canbus though at any time though. Really weird

Dash config attached. Dash will work and read correctly if I plug the dash into CAN1 (using a seperate loom) and obviously swap the Generic Dash channel settings over to CAN1 on the CAN setup. So something must be clashing on CAN2 ?? DSORDA AIM Dash.cfz

Unfortunatly I can't unplug the PDM or Keypad, as dash/ecu is all powered by PDM and ignition on is controlled through the keypad (No ignition key). The best I was able to do is disable channel 2 & 3, but keep Channel 1 Generic Dash alive, but still no live data displayed on dash (Ecu store, power cycle etc)

Sorry Adam, I thought the latest firware would have been visable through my current version of PC Link. Downloaded the latest from the website and updated the firmware to the current. The firmware update didn't affect the CAN issue. Went ahead and changed the Message 0 "3E8" to zero as suggested, no change. Also tried disabling the channel, also no change. Both of these changes were loaded to the PDM, power cycled etc