MEGAsquirt A place to collectively sort out this megasquirt gizmo

My 95 NA is running with DIYPNP MS v2.0.8 but not v3.2.5

Thread Tools
 
Search this Thread
 
Old 09-08-2013 | 11:25 PM
  #1  
jonny5's Avatar
Thread Starter
Newb
 
Joined: Jul 2013
Posts: 6
Total Cats: 0
Default My 95 NA is running with DIYPNP MS v2.0.8 but not v3.2.5

I assembled and installed my diypnp 1.5 last week and it wouldn't start or show rpm signal with 3.2.5, so I flashed 2.1.0 and it sees rpm and runs fine. So this week I tried again and flashed 3.2.5 again and went through all settings, calibrations, etc and still no rpm. I'm using the starter maps from the diypnp install site. Why would it run with 2.1.0 but not a later version? I would appreciate any help.

Last edited by jonny5; 09-09-2013 at 11:16 AM.
Old 09-09-2013 | 08:34 AM
  #2  
Braineack's Avatar
Boost Czar
iTrader: (62)
 
Joined: May 2005
Posts: 79,818
Total Cats: 4,152
From: Chantilly, VA
Default

Did you review the errors when you loaded the basemap to see what settings were different between the two firmwares so you could make sure that there's nothing that needed to be fixed in order to start the car?
Old 09-09-2013 | 09:38 AM
  #3  
jonny5's Avatar
Thread Starter
Newb
 
Joined: Jul 2013
Posts: 6
Total Cats: 0
Default

Originally Posted by Braineack
Did you review the errors when you loaded the basemap to see what settings were different between the two firmwares so you could make sure that there's nothing that needed to be fixed in order to start the car?
Sort of... There are 2 startup maps on diypnp for a non-sequential car, one for 2.1.1 and one for 3.0.3. So when I tried again to get the car to start on the newer firmware I flashed it with 3.2.5 and got a few errors that looked non related when I loaded the 3.0.3 map. I did do a comparison of the two maps (2.1.1 & 3.0.3) and couldn't find any differences relating to where it is getting cam signal (assuming that not getting the correct cam signal would be the problem in not seeing rpm). I have run the 3.0.3 map on the 2.1.1 firmware and it starts right up, but I do get 46 errors. I was just assuming that was from loading a new map on old firmware.
Old 09-09-2013 | 10:01 AM
  #4  
Braineack's Avatar
Boost Czar
iTrader: (62)
 
Joined: May 2005
Posts: 79,818
Total Cats: 4,152
From: Chantilly, VA
Default

I would review the errors before comparing maps.
Old 09-09-2013 | 10:28 AM
  #5  
jonny5's Avatar
Thread Starter
Newb
 
Joined: Jul 2013
Posts: 6
Total Cats: 0
Default

Originally Posted by Braineack
I would review the errors before comparing maps.
These are the errors i got when I flashed 3.2.5 this morning and loaded the 3.0.3 basemap



Disregard the larger screenshot, I uploaded the wrong one by mistake.
Attached Thumbnails My 95 NA is running with DIYPNP MS v2.0.8 but not v3.2.5-9710599044_a90d3e2ae8_o.jpg   My 95 NA is running with DIYPNP MS v2.0.8 but not v3.2.5-9710853276_8d2ab32da4_o.jpg  

Last edited by jonny5; 09-09-2013 at 11:07 AM.
Old 09-09-2013 | 11:33 AM
  #6  
jonny5's Avatar
Thread Starter
Newb
 
Joined: Jul 2013
Posts: 6
Total Cats: 0
Default

I also got this when I powered it up in the car. The Tacho Output was set to on, so I turned it off and power cycled it and still nothing. Same thing when I turned it back on with the output on TACHOUT. I was under the impression miatas don't require this to be on though.


Attached Thumbnails My 95 NA is running with DIYPNP MS v2.0.8 but not v3.2.5-9710994556_b57f3d5ca0_o.png  
Old 09-09-2013 | 11:56 AM
  #7  
Braineack's Avatar
Boost Czar
iTrader: (62)
 
Joined: May 2005
Posts: 79,818
Total Cats: 4,152
From: Chantilly, VA
Default

depends on your model year.


but that suggests you have two functions using tacho for the output; this could be anything, not just tach.
Old 09-09-2013 | 05:50 PM
  #8  
jonny5's Avatar
Thread Starter
Newb
 
Joined: Jul 2013
Posts: 6
Total Cats: 0
Default

I have the 4 wire ignition coils so if I'm right, the in dash tach signal is coming directly from the coils to the tach, so the tach output from ms should be off. If that is right, what should my next step be?
Old 09-09-2013 | 07:07 PM
  #9  
Braineack's Avatar
Boost Czar
iTrader: (62)
 
Joined: May 2005
Posts: 79,818
Total Cats: 4,152
From: Chantilly, VA
Default

figure out what two outputs are set to tacho and turn one off.
Old 09-14-2013 | 06:50 PM
  #10  
jonny5's Avatar
Thread Starter
Newb
 
Joined: Jul 2013
Posts: 6
Total Cats: 0
Default

I have been working on this and found no answers. I added the 1k resistor in the diagnostic box from 12v to tach, but still no signal. All I can confirm is that 3.2.5 still wont see rpm with the exact settings that 2.1.0 runs with. I just reverted back to 2.1.0 today to double check things and it fired right up. I also tried 3.2.4, and it saw no rpm either. I attached my tune if you want to take a look. Not sure where to go from here.
Attached Files
File Type: msq
CurrentTune.msq (83.8 KB, 132 views)
Related Topics
Thread
Thread Starter
Forum
Replies
Last Post
Full_Tilt_Boogie
Build Threads
84
04-12-2021 05:21 PM
90 Turbo
MEGAsquirt
19
10-19-2015 04:23 PM
The Gleas
MEGAsquirt
3
10-01-2015 10:30 AM
viriiguy
General Miata Chat
5
09-28-2015 08:39 PM




All times are GMT -4. The time now is 06:21 AM.