Mega megasquirt fail 65k rpms
#8
MS lite v2.6.19
megasquirt firmware updated to 3.4.0
Car is a bone stock 1.6 besides GM IAT censor and intake (engine wise)
http://www.megasquirtpnp.com/downloa...Miata_331a.msq
megasquirt firmware updated to 3.4.0
Car is a bone stock 1.6 besides GM IAT censor and intake (engine wise)
http://www.megasquirtpnp.com/downloa...Miata_331a.msq
#12
Elite Member
iTrader: (1)
Join Date: Jun 2006
Location: Warrington/Birmingham
Posts: 2,642
Total Cats: 42
The error message tells you there is a conflict with an Output port.
Why would adding an input resolve this?
Brain has already told you how to fix this. Ben has asked for a copy of your MSQ, if you'd actually posted this he would've told you EXACTLY what to change.
But yes adding a VTPS will definitely 100% fix your issue. :faceplam:
Why would adding an input resolve this?
Brain has already told you how to fix this. Ben has asked for a copy of your MSQ, if you'd actually posted this he would've told you EXACTLY what to change.
But yes adding a VTPS will definitely 100% fix your issue. :faceplam:
#13
The error message tells you there is a conflict with an Output port.
Why would adding an input resolve this?
Brain has already told you how to fix this. Ben has asked for a copy of your MSQ, if you'd actually posted this he would've told you EXACTLY what to change.
But yes adding a VTPS will definitely 100% fix your issue. :faceplam:
Why would adding an input resolve this?
Brain has already told you how to fix this. Ben has asked for a copy of your MSQ, if you'd actually posted this he would've told you EXACTLY what to change.
But yes adding a VTPS will definitely 100% fix your issue. :faceplam:
Reason why I didn't upload code is because I got rear ended and insurance has to check it out sorry.
I'm just going to put stock ecu in and sell megasquirt, not worth it for the struggle for me. your welcome
#15
Boost Czar
iTrader: (62)
Join Date: May 2005
Location: Chantilly, VA
Posts: 79,499
Total Cats: 4,080
Honestly, your real problem is that you didnt load the firmware properly for your ECU and you told your MS that it's a normal ms2 and not a microsquirt module.
So when you loaded the basemap setup for a microsquirt module -- that uses ALD and WLD for functions -- on a firmware that uses ALD and WLD, by default, as the two spark outputs (instead of spark A and spark B).
You're going to have that conflict until you reflash the firmware correctly, using option 3 when prompted, and choose microsquirt (including MSPNP2) as the CPU -- not ms2.
So when you loaded the basemap setup for a microsquirt module -- that uses ALD and WLD for functions -- on a firmware that uses ALD and WLD, by default, as the two spark outputs (instead of spark A and spark B).
You're going to have that conflict until you reflash the firmware correctly, using option 3 when prompted, and choose microsquirt (including MSPNP2) as the CPU -- not ms2.
#16
Honestly, your real problem is that you didnt load the firmware properly for your ECU and you told your MS that it's a normal ms2 and not a microsquirt module.
So when you loaded the basemap setup for a microsquirt module -- that uses ALD and WLD for functions -- on a firmware that uses ALD and WLD, by default, as the two spark outputs (instead of spark A and spark B).
You're going to have that conflict until you reflash the firmware correctly, using option 3 when prompted, and choose microsquirt (including MSPNP2) as the CPU -- not ms2.
So when you loaded the basemap setup for a microsquirt module -- that uses ALD and WLD for functions -- on a firmware that uses ALD and WLD, by default, as the two spark outputs (instead of spark A and spark B).
You're going to have that conflict until you reflash the firmware correctly, using option 3 when prompted, and choose microsquirt (including MSPNP2) as the CPU -- not ms2.
Thank you
Thread
Thread Starter
Forum
Replies
Last Post