Printable Version | Subscribe | Add to Favourites
New Topic New Poll New Reply
Author: Subject: Megasquirt setup problem
iti_uk
Builder






Posts 163
Registered 13/10/08
Member Is Offline

Photo Archive Go!
Building: The KLMX-5 ('97 MX5 w/Mazda KL 2.5L V6)

posted on 16/4/10 at 11:47 AM Reply With Quote
Megasquirt setup problem

Hi, I have a small problem with my Megasquirt;

I have a Megasquirt 2 V3 setup which I want to run an EDIS6 module for spark as well as the normal injection stuff.

The symptoms are that there appears to be no tach signal reaching the CPU.

The history of my board is that I initially built it to use the hall sensor circuit (everything worked perfectly), then decided I was going to use the VR circuit, so installed the necessary components and changed the jumpers accordingly (everything worked perfectly). Now that I have settled on using the EDIS module, I need to go back to using the hall sensor circuit (PIP/SAW(?) input from EDIS).

I have done the EDIS circuit mods as described in the megamanual and changed the jumpers back in the required manner, but the jumper nearest the top of the CPU (tsel-optout? can't remember off hand) pulled the tsel pad through the board as I changed the jumper. I have tried to repair the connection with the soldering iron, but I don't think the problem ends there - I have tried jumpering directly from the tsel-optout(?) jumper to the tach signal input pin on the CPU IIRC, pin 14?), but it doesn't seem to help. However, touching that pin with a finger will cause the MS to jump into life and run at a permanent ~750RPM, uneffected by the "RPM" pot on the stim.

This is not helped by the fact that I only get ~2 minutes of Megatune time before Vista blue-screens.

Is there someone I can send my MS to to get it working? I'm fed up with trying to figure this out myself. I hate electronics now, I have decided

Before anyone suggests, I have posted this up on the msefi.com forum, but the only answers I get are "read the manual first". I can't find any reference to this problem in any of the literiture..

TIA

Chris

View User's Profile View All Posts By User U2U Member
flak monkey

posted on 16/4/10 at 11:58 AM Reply With Quote
To solve your blue screen problem download this:

http://www.efianalytics.com/TunerStudio/support/download/GUC232_WINXP.zip

And replace the ser2pl.sys file in your windows\system32\drivers\ directory with the one in the zip.

Should stop it crashing - worked for me.

Follow these instructions to the letter

http://msextra.com/doc/ms2extra/MS2-Extra_EDIS.htm

And it should all work





Sera

http://www.motosera.com

View User's Profile Visit User's Homepage View All Posts By User U2U Member
iti_uk
Builder






Posts 163
Registered 13/10/08
Member Is Offline

Photo Archive Go!
Building: The KLMX-5 ('97 MX5 w/Mazda KL 2.5L V6)

posted on 16/4/10 at 01:09 PM Reply With Quote
quote:
Originally posted by flak monkey
To solve your blue screen problem download this:

http://www.efianalytics.com/TunerStudio/support/download/GUC232_WINXP.zip

And replace the ser2pl.sys file in your windowssystem32drivers directory with the one in the zip.

Should stop it crashing - worked for me.

Follow these instructions to the letter

http://msextra.com/doc/ms2extra/MS2-Extra_EDIS.htm

And it should all work


Thanks, I'll try that file tonight.

Chris

View User's Profile View All Posts By User U2U Member
iti_uk
Builder






Posts 163
Registered 13/10/08
Member Is Offline

Photo Archive Go!
Building: The KLMX-5 ('97 MX5 w/Mazda KL 2.5L V6)

posted on 18/4/10 at 07:04 PM Reply With Quote
Excellent stuff, thanks flak monkey!

That Vista replacement .sys file works like a treat.

Having got a reliable Megatune, I have now fault-found - it was indeed the pulled-through pad which has pooped the party, so I have jumpered from optout to pin 14 on the CPU base (I think it's 14, I know the pin by sight, can't remember the numbering...), and hey presto, it works!

I do have one problem still - the EDIS wiring setup.

I have found many differing EDIS MS modification diagrams, and I have mine set up as a standard Hall input circuit (XG1-XG2, etc.)**. However, the diagram you linked to (does the megamanual change that often?) shows a removed C30 and a jumper from the top of C30 to S12C, and tachselect to XG1. Which way is correct, or is it the case that there is more than one way to skin a cat?

Output circuitry seems common for all of the EDIS how-to's - JS10 -> IGN. No worries there.

Chris

** Link to source at megamanual.com;

To install EDIS with MegaSquirt-II, you connect:

V2.2 main board:

* the 5th hole of JP1 to the SAW pin (#3) on the EDIS module (which you can jumper to an unused DB37 pin, if you want),
* the PIP pin (#1 on the EDIS module) to DB37 pin #24,
* Make sure D8 (the 'John' Zener diode) is jumpered.

V3.0 main board:

* DB37 pin #36 to the SAW pin (#3) on the ignition module
* DB37 pin #24 to the PIP pin (#1) on the ignition module
* On the V3.0 main board:
o use the 'Hall sensor circuit' (step #50.a in the assembly guide) - jumper D1 and D2,
o jumper OPTOIN to TACHSELECT on the bottom side of the PCB, near the DB37 connector, opposite the heat sink,
o jumper TSEL to OPTOOUT on the bottom side of the PCB, near the center.
* jumper JS10 to IGN (this uses the processor port for the SAW signal directly),
* jumper XG1 to XG2 on the bottom side of the PCB, near the 40 pin socket,

If you are using the relay board with a v3 main board:

* the SAW signal connects to the S5 terminal (#11 on the 20 position terminal strip) on the relay board, it comes from DB37 pin 36 (make sure you have a wire connecting pin 36 to pin 36 in the MegaSquirt/relay board connecting cable),
* the PIP signal connects to the Tach terminal (#15 on the 20 position terminal strip) on the relay board, it goes to DB37 pin 24.


[Edited on 18/4/2010 by iti_uk]

View User's Profile View All Posts By User U2U Member
iti_uk
Builder






Posts 163
Registered 13/10/08
Member Is Offline

Photo Archive Go!
Building: The KLMX-5 ('97 MX5 w/Mazda KL 2.5L V6)

posted on 20/4/10 at 08:27 AM Reply With Quote
Anyone have any idea?
View User's Profile View All Posts By User U2U Member

New Topic New Poll New Reply


go to top






Website design and SEO by Studio Montage

All content © 2001-16 LocostBuilders. Reproduction prohibited
Opinions expressed in public posts are those of the author and do not necessarily represent
the views of other users or any member of the LocostBuilders team.
Running XMB 1.8 Partagium [© 2002 XMB Group] on Apache under CentOS Linux
Founded, built and operated by ChrisW.