hello im ben from australia i have a 1976 mini clubman with an 1152cc a-series engine that is turbocharged and running megajolt.
first questions is about shelded wire , i didnt use any when engine was on engine dyno and i didnt have any problems or missfires so gathered it was ok. Since engine has been installed in the car i have a few mis fires? is sheilded wire crucial? should i use
next question is the map sensor , at the moment i have BOV , boost guage , boost controller and megajolt all running of the same vacum line i was told that the blow off valve should be separate as spikes could harm the map sensor?
last question is the RPm , im using the factroy rover cooper 3 guage cluster and the rpm works fine up to 2500rpm the flickers on and off dependent on engine loads. The tacho is hooked up to the megajold tacho line is the anything i can try to fix this easliy ? using the same takoff from megajolt
thanks
ben
few megajolt questions
Moderators: JeffC, rdoherty, stieg, brentp
Hi Ben
Welcome!
Shielded wire - highly recommended, but not mandatory. First option, rather than re-wiring, would be to make sure you have V3.2.1 firmware in the MJLJ. This is more immune to noise pickup. If that doesn't solve it, then shielded is the way to go
MAP sensor - it's got a physical min/max rating of circa 0 to 10 bar (only measures between 0 and 2.5 however). Presumably the BOV just dumps excess pressure. I can't see any problem.
RPM - a common problem! Try hooking the tacho to the EDIS PIP line (MJLJ pin 2) instead. That often solves it.
Report back, especially on the RPM problem please!
Welcome!
Shielded wire - highly recommended, but not mandatory. First option, rather than re-wiring, would be to make sure you have V3.2.1 firmware in the MJLJ. This is more immune to noise pickup. If that doesn't solve it, then shielded is the way to go
MAP sensor - it's got a physical min/max rating of circa 0 to 10 bar (only measures between 0 and 2.5 however). Presumably the BOV just dumps excess pressure. I can't see any problem.
RPM - a common problem! Try hooking the tacho to the EDIS PIP line (MJLJ pin 2) instead. That often solves it.
Report back, especially on the RPM problem please!
-
- Posts: 122
- Joined: Tue Jan 10, 2006 8:17 pm
- Location: North Yorkshire, UK
I recently upgraded my firmware... I had real trouble... tried it on 2 separate computers with the same error of something about "forgot to set single wire mode?". What I eventually found with mine was that I had to have the MJLJ powered up before running hc08sprg, and when it was looking for the reset, I powered the unit down and then back up again and it worked fine.
This was on an old laptop (win95) with proper serial port.
This was on an old laptop (win95) with proper serial port.
ok tried a few more times on two computers with no luck??? just keeps counting higher and higher im using a usb to serial. ?MartinM wrote:Looks like that's what's being done....the reset ack (0xFC) is associated with the power up of the MJLJ
It's a bit of a cop-out, but all I can suggest is trying it a few more times - sometimes it is a bit temperamental.....
ok finally got it to work
went a bought a more expensive usb-serial cable and it worked straight away no troubles. The cruising miss seems to have gone and doesnt hesitate coming into boost anymore, so much happier. Still hesitates wehn taking off but could be something else , will investigate.
Re the tacho, spliced into the pip line megajolt nuber two for the tacho and it seems to work fine now although havent taken for a drive it works reving in nuetral.
will add some pics in the gallery soon.
thanks
ben

went a bought a more expensive usb-serial cable and it worked straight away no troubles. The cruising miss seems to have gone and doesnt hesitate coming into boost anymore, so much happier. Still hesitates wehn taking off but could be something else , will investigate.
Re the tacho, spliced into the pip line megajolt nuber two for the tacho and it seems to work fine now although havent taken for a drive it works reving in nuetral.
will add some pics in the gallery soon.
thanks
ben
Thanks for the update, and great you're seeing improvements!
As you probably know, noise on the PIP line can cause the MJLJ to see them as extra PIP pulses, which translates into RPM spikes.
The software based noise filtering in the 3.2.1 firmware attempts to disqualify those noise spikes, which helps in many cases.
However, for optimal results, think of an installed system designed with 'robustness in depth'. Meaning:
Robust (rigid and accurate) VR sensor bracket mounting and alignment to feed a clean signal to the EDIS module
Robust (shielded , properly grounded and preferably solder-connected ) wiring for both MJLJ and EDIS - to reduce noise and provide a clean signal path between EDIS and MJLJ
Last in line is robust signal processing in the MJLJ - with 3.2.1 we attempt to filter out these extraneous PIP signals.
If you can, try to perform a datalogging session and see if you can correlate any RPM spikes with the remaining hesitation you're seeing.
Will love to see your pics in the gallery!
Regards,
As you probably know, noise on the PIP line can cause the MJLJ to see them as extra PIP pulses, which translates into RPM spikes.
The software based noise filtering in the 3.2.1 firmware attempts to disqualify those noise spikes, which helps in many cases.
However, for optimal results, think of an installed system designed with 'robustness in depth'. Meaning:
Robust (rigid and accurate) VR sensor bracket mounting and alignment to feed a clean signal to the EDIS module
Robust (shielded , properly grounded and preferably solder-connected ) wiring for both MJLJ and EDIS - to reduce noise and provide a clean signal path between EDIS and MJLJ
Last in line is robust signal processing in the MJLJ - with 3.2.1 we attempt to filter out these extraneous PIP signals.
If you can, try to perform a datalogging session and see if you can correlate any RPM spikes with the remaining hesitation you're seeing.
Will love to see your pics in the gallery!
Regards,