Jump to content

Monsterbishi

Members
  • Content Count

    47
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by Monsterbishi

  1. The first order of business is to test the components you have, there's no point in getting out the Visa card until you know whether something actually needs replacing. What is the Wideband/Lambda value doing immediately prior to when the issue presents itself?
  2. As far as tuning goes, what functional differences are there between using the mixture map and the quick trim feature?
  3. There's not much point in even looking at what your boost controller is showing until you sort out where the misfire is coming from, test all the ignition components and then work from there, have you determined whether it is one specific cylinder that is misfiring?
  4. I'd look at the plug gap first, what did you gap them to when you installed them? There are a lot of parts manuals out there that wrongly specify a plug that has a 1.1mm/0.043" gap - it should be between 0.7mm/0.028" to 0.8mm/0.032" We used to run 29psi through our 4g63 powered Mirage with a 0.8mm gap.
  5. Looks like it's blowing out the candles, as it were - what happens when you dial the boost down?
  6. Now that's an idea! I wonder what other goodies I could get them to connect at the same time - the daughterboard is essentially a Extreme isn't it?
  7. It's running my 302w at the moment so I'm bouncing around ideas to see what I can get it to do in the off season
  8. I have a Mazda MX5 Plugin G4+ and have a question about the pinout on it - for the Ign outputs, IGN 1,2,3 and 4 are listed on the main pinout, IGN 7 & 8 are listed as being on Expansion Connector 2, but there is no mention of Ign 5 & 6 at all, are these available for use anywhere or is it one of the physical limitations of the MX5 plugin ECU?
  9. The most common one I come across is that once you've got the ecu re-configured you need to power cycle the ecu, ie pull it's fuse - a normal key off power cycle won't do the job. Failing that, find a Android device that it works with then use those settings on the Windows version of realdash.
  10. Can Lambda manual which includes the pinout: https://linkecu.com/documentation/canlambda.pdf
  11. Your post is somewhat lacking in information, ie what car, cluster, ecu, etc.
  12. I'd say the biggest problem is the tuner, after five months you'd expect all and any issues identified and/or solved.
  13. Picked up a G4+ CAN Lambda unit this week, I see in the instructions that it says to install the sensor at least one metre downstream to avoid overheating the sensor. I was planning on using the factory O2 sensor location but it is situated circa 500mm downstream of the engine (NA 302 windsor) - should I weld the supplied boss further downstream or just use the factory location?
  14. I use a windows tablet, I have my power saving options set to keep the display on when on USB power and turn off the display and then shutdown the tablet asap when it's running on battery, so when I turn the car off the tablet shuts down shortly thereafter.
  15. Or a separate power supply.
  16. There's two things that usually cause issues, once you've enabled the datastream in the ECU you absolutely need to power cycle the ECU, ie disconnect/reconnect your battery then retry. If that doesn't work, it's probably a issue with the tablet itself not supporting serial comms - assuming you have a windows laptop, go into the windows store and download realdash onto it and test the connection using that - then you can switch to the tablet and that will tell you if the tablet is compatible or not.
  17. Put me down for one vote towards bad idle stepper controller and base idle set screw incorrectly set.
  18. It doesn't take long for that to happen if it's in a humid environment, moreso if it's located somewhere that gets hold/cold on a regular basis.
  19. I'm running a Ford V8 off my MX5 Plugin ECU so a V6 should be just fine, as has already been mentioned the main thing is to pair the injectors.
  20. Check the wheel speed sensor ground. Then check that your wheel speed sensor is outputting correctly? Once that's done test the DI connection. Then make sure you have the DI correctly configured for the type of speed sensor, ie reluctor, etc. Then it shall be sorted. Just remember that if it is a reluctor type sensor it may not read at very low speed, and they don't like too many teeth on the trigger wheels either.
  21. If you plug a usb mouse/keyboard into the OTG adapter you're using to connect the S9 to the ECU you can use the mouse/keyboard to configure the gauges, etc easily without even touching the screen :-)
  22. Hi Dave, It takes a bit of time for a update to be approved through the Microsoft store system, if you email the team at Realdash they may be able to give you an idea of when the next version is going to be publicly available which will include the fix for the lag. Cheers, Mark
  23. Problem solved, well, there was never actually a problem to start with - I had the meter on Aux6 instead of Aux5...
  24. ECU is a G4+ Plugin for a Mazda MX5 running a Ford 302w V8 in my Mustang. (Don't ask) At any rate, we have a DI configured as a Stop Switch, when active it kills the Ignition but the Aux5 Fuel Pump output remains hot, is there a setting somewhere that I'm missing?
×
×
  • Create New...