Jump to content

CamB

Members
  • Content Count

    95
  • Joined

  • Last visited

  • Days Won

    5

CamB last won the day on January 4 2018

CamB had the most liked content!

1 Follower

About CamB

  • Rank
    Advanced Member

Profile Information

  • Location
    Auckland

Recent Profile Visitors

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

  1. I've been advised that the CAN lambda will manage the heater by using the ECUs running information, so should be connected as per the wiring diagram. Would be worth waiting until someone from Link confirms or you should try the tech support help line.
  2. Thanks Adam. Mine is twin plug and ITB and I was interested as that one you posted is only slightly higher than I would have expected for twin plug (max 28* under load) but slightly more conservative than I would have expected for single plug. I've just been collecting data points. Either way I will get mine tuned properly - I've been told that MBT is pretty clear on a twin plug 911 and occurs at quite low advance.
  3. @Adamw - do you know if that is a table from a twin plug or single plug 911?
  4. There are quite specific instructions in the manual - worth reading all of it as it covers: motor +/- a relay to provide the ECU with power for the above an Aux so the ECU controls the relay plus the accelerator sensor and TPS wiring https://www.vi-pec.com/techdata/ecu-manuals-v-series/vi-pec-manual.pdf
  5. Did you re-check base timing after swapping polarity?
  6. > I understand that pin Q5 is the ÷10 output that gets fed into the ECU's DI input. Correct > +5VDC from ECU sensor power supply goes to which pin on the IC? VDD - pin 16 > Turbo speed sensor original output goes to what pin on the IC? D = Data - pin 1 > Does the IC need power earth or sensor earth fed into it and on what pin? I'd ground to chassis, all the ones shown (Jam 1-5 and R for reset) and VSS
  7. CamB

    ID1000's I'm confused

    The most interesting thing for me is that short pulse adder changes depending on your fuel pressure. I'd already worked this out playing with the Motec data, but useful to see it from a vendor. Couldn't tell you why the short pulse is different between the two ID sets though. If you press Alt-F11 in Excel you can unhide the worksheet with the data and have a look but its just a hardcoded table of short pulse by pressure.
  8. That will depend on whether there is an output from the ECU which is useful to you, and it may rapidly use up outputs too. A better idea would be to try and get CANBUS working (adding a CAN shield to Arduino, or I think there are other Arduino-like options with CANBUS built in). I suspect this will give you a better outcome.
  9. I believe it is "Second comms port CAN1 / RS232" (RS232 not for PC Link, for a serial stream).
  10. Would also be nice if you had a way to measure load (MAP or TPS, although I am not sure how feasible either is with Webers as I've never looked into it - must be options) for ignition mapping.
  11. Was just reading this the other day - the manual says it is required (page 12): http://www.linkecu.com/wp-content/uploads/2016/10/CAN-Lambda.pdf
  12. CamB

    Can protocol sample

    @Davidv - thanks, I should have looked more closely at that! It was easy enough to change the code (I ended up using a custom stream rather than the generic one as I had trouble capturing all the incoming CAN messages if there were too many).
  13. CamB

    Can protocol sample

    From my messing around with it, all the raw data in the Generic stream is the second parameter + 256 * the first parameter (in the pair). Interestingly when you set a custom stream the order is reversed... Is there a reason not to just use the standard convention? (I guess efficient coding?)
  14. If stalling I would try: - using "idle ignition", so you've got an increase in timing when idle falls below target (there is an HPA webinar on this) - turning off transient ignition retard unless you are convinced you need it, and at least zero-ing it anywhere near idle There's a bunch of other stuff in the map (assuming the first one you posted is close enough to what you are using) that I am unfamiliar with but wouldn't necessarily expect (like quite significant ECT ignition trims, etc). These may not actually be affecting anything - its not possible to tell as your log doesnt have enough parameters. I can, however, see that your first map's ignition table doesn't match the logs (although, without the data, can't say why).
  15. CamB

    Motec PDM to Fury CAN

    There should be more than that - a relatively recent PCLink upgrade pushed it out to 8x. Try loading the Monsoon example if you don’t have an ECU to update.
×
×
  • Create New...