Jump to content

Vaughan

Moderators
  • Content Count

    336
  • Joined

  • Last visited

  • Days Won

    15

Vaughan last won the day on December 30 2020

Vaughan had the most liked content!

2 Followers

About Vaughan

  • Rank
    Software Engineer (Staff)

Profile Information

  • Gender
    Male
  • Location
    Christchurch NZ

Recent Profile Visitors

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

  1. I had a play and a latch based on a voltage range is complicated to implement and even more complicated is having it not detect when you pass through that voltage on the way to a higher one. If you don't want to to wire the buttons to the ECU individually (at least for the things that latch) I would personally go with an arduino and CAN adapter or equivalent as that means you could write as complicated a setup as you want and then just communicate with the ECU through CAN DIs and CAN Analogs. There is a lot of software behind the Cruise Controls analog input option which does differentiat
  2. You could also use a gp pwm function instead of tacho function which will give you the ability to add an offset
  3. The calibrate feature forces the cam to its resting spot so the ECu knows what the 0deg advanced/retard cam angle is, you might be confusing the calibrate function with the tuning of the PID control loop which does the moving of the cam.
  4. if you change each fan output to test on do all fans turn on?
  5. On the 1.6 motors the signal comes straight from the igniter, on the 1.8 NA motors it looks like it comes from the coils and that bridged pin just adds a pullup. Also regarding CE lights they don't all have them, my mx5 is admittedly a very basic one (1989 NZ new) but it is short quite a few things, this can be checked by pulling the dash cluster but that does involve removing the very fragile cowl. https://www.miataforumz.com/1990-200-Miata-Wiring/95sys.pdf
  6. You could use a GP PWM instead of the IC spray function if you were fine with a slightly simpler activation setup, you would have a minimum frequency of 0.6Hz (spray period of 1.67s) and you could probably get some on/off hysteresis with the activation conditions. You could also do a Math Block setup with a statement like (Oil Temp > X) | (ECT > Y) | (IAT > Z) which can be used to activate the IC spray (use the math block as the activation input). This wouldn't be increasing DC with temp but would be spraying or not spraying with temp. Alternatively if you have separate spra
  7. have fixed that math block thing, will be in the next release Could maybe make an afr conversion that takes into account the ethanol % runtime and both stoich values, would this would be useful for anything.
  8. looks like that would work just fine, there isn't any special hardware that I can see on those pins
  9. have you set the jumper to bridge the two pins by the header?
  10. I can replicate this, will see if I can get it fixed. If you power cycle after loading and storing the map it works.
  11. Vaughan

    Missfire?

    Please attach a copy of your basemap and if possible a short PC Log.
  12. All looks to line up to me.
  13. looks like you can just use the factory wiring.
  14. That 3rd image has the wrong polarity but I don't think that will affect active/inactive, to confirm you have connected the VANOS cam sensor to pin 65? If you set DI2 to a gp input with pullup on and tap that cam sensor wire against an earth does it go active and inactive?
×
×
  • Create New...