Jump to content

DSORDA

Members
  • Content Count

    27
  • Joined

  • Last visited

About DSORDA

  • Rank
    Member

Profile Information

  • Gender
    Male

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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
  2. Thanks Adam, I was met by a prompt stating I required the latest version to connect as you said
  3. 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.
  4. DSORDA

    Fury CAN issue

    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
  5. DSORDA

    Fury CAN issue

    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
  6. DSORDA

    Fury CAN issue

    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)
  7. DSORDA

    Fury CAN issue

    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
  8. DSORDA

    Fury CAN issue

    First thing I did was check for firmware updates, and was met with the message I was already on the latest firmware V5.6.1? PDM Config attached DSORDA PDM.pdm
  9. DSORDA

    Fury CAN issue

    Hey Guys, Just having a wee issue setting up some CAN settings between the Fury, AIM MXL dash, Motec PDM and keypad. I've previously had the Fury and the Dash working faultlessly, and only started acting up when the new settings were put in for the PDM and keypad, so something is conflicting. The keypad works fine, and all the keypresses are working accordingly to activate boost tables, antilag etc etc. The issue is, the Dash will not display live data any more. It will merely display a 'snipit' of the data upon power-up, and stay at that value unchanged. This is for all channels I have displayed through the Dash from the ecu, speed, oil pressure, fuel pressure etc etc. My only guess is its something conflicting in the new CAN settings, but I'm a bit out of my depth with CAN protocol. If someone can spot anything obvious in my settings, that'd be great. AIM MXL settings have all been used as per the help file. Only thing to note is the CAN has been hardwired to CAN2 (B Plug loom) and I tried a 10Hz transmit rate as per another thread, with no success Cheers Ian DSORDA CAN Issue.pclr
  10. DSORDA

    Motec PDM to Fury CAN

    Appologies Adam, I only mentioned it as that was the way we discussed it would be configured in post #2. However, I see not all funtions can be selected over CAN, such as the antilag. Any reason for this? You mentioned over in the other topic on CAN keypads that we may be in trouble with the Motec Keypresses not transmitting a latched signal? How can we get around this, if it is indeed the case?
  11. DSORDA

    Link PDM

    Any updates to this?
  12. DSORDA

    Motec PDM to Fury CAN

    The reason I ask is that, if I am restricted to switching via a Virtual aux, does this mean I will be limited to only being able to switch 3 things (Boost, antilag, launch etc)? Since there are only 3 virtual aux avaliable?
  13. DSORDA

    Motec PDM to Fury CAN

    Are there any firmware updates planned in the near future to have the CAN DI's added as switching conditions?
  14. DSORDA

    Motec PDM to Fury CAN

    Thanks for the input Adam, had guessed after a quick play in PClink that I couldn't directly assign a "CAN DI" and that a Virtual Aux my be required. I can still happily hardwire Aux outputs to the PDM to trigger things like the fuel pumps, fan etc, it was more about activating stuff through the keypad if I were to get one. I'll have a better look into the PDM software to see how the keypresses are configured. Cheers
  15. DSORDA

    Motec PDM to Fury CAN

    Hey guys, Going to be running a Motec PDM15 in my car and toying with the idea of a CAN keypad for the PDM. I would be looking to use the keypad for activation of the usual things, like hi/low boost, antilag etc, and curious how I would configure the system arming in my Fury ecu, since the keypad is over CAN. Antilag for example.. is it simply a case of setting the system arming to say DI4, and the respective key on the keypad to CAN DI4? Or can't these funtions be armed over the CAN network? Cheers Ian
×
×
  • Create New...