Wideband was working and displaying in TS but MS glitched and now won't read at all.
12-14-2019, 05:35 PM
#1
Newb
Thread Starter
Join Date: Jan 2017
Location: Round Rock, Texas
Posts: 25
Total Cats: 1
Wideband was working and displaying in TS but MS glitched and now won't read at all.
Hi, I have a 1999 NB with MTX-L plus WB and MSPNP2 for the ECU.
I've been working my way through trying to tune on tunerstudio MS this last week. This morning when I went to try and tune, it read my AFR like normal. After about an hour though, tunerstudio kinda glitched out when I was cycling power to the ECU and gave that message where it tells you that settings on the ECU and in TS didn't match. It showed me what the differences were and I can't recall what all the differences were, but some things were obviously wrong on the MS side (Ignition options/Wheel decoder had spark mode on the ECU set to something other than Miata 99-00. There were multiple options that had been changed that I've never touched before in Ignition and I believe also in General settings.
Because the settings that had somehow corrupted on the ECU were obviously wrong, I decided to load the settings from TS. After doing this though, my AFR stopped displaying in TS. The wideband guage itself has been displaying, but in TS the AFR is stuck on 7.4 no matter what I do. I have the guage analog output going to the stock sensor plug and made sure it was giving out a signal (roughly 3.4 volts on my multimeter and reading around 18 AFR, AKA working). I tried running the car both with the guage plugged in and with it removed and there was no difference in the engine behavior during cranking/idle/light throttle. In EGO control I went through all of the sensor port options and none of them registered any signal from my wideband at all. After that, I decided to undo all the changes I had made and go back to the most recent tune from yesterday where I KNEW the Wideband was working correctly with MS and TS. Still no luck.
As far as I can tell, the guage is 100% functional and none of my wiring is the issue. The tune and settings aren't the issue either because I reset those to a known good point. I've closed and reopened Tuner Studio and made sure to retest the serial connection (communications>settings). The ECU works and will run the car, but for some reason it's not giving reading the WB output anymore.
The only thing I can think to try next is maybe updating the MS firmware from 3.3.1 to the newest firmware and see if that works, but I don't know how to do that on the MSPNP2 and I can't find a guide on it anywhere.
Do any of you have any thoughts or tips?
I've been working my way through trying to tune on tunerstudio MS this last week. This morning when I went to try and tune, it read my AFR like normal. After about an hour though, tunerstudio kinda glitched out when I was cycling power to the ECU and gave that message where it tells you that settings on the ECU and in TS didn't match. It showed me what the differences were and I can't recall what all the differences were, but some things were obviously wrong on the MS side (Ignition options/Wheel decoder had spark mode on the ECU set to something other than Miata 99-00. There were multiple options that had been changed that I've never touched before in Ignition and I believe also in General settings.
Because the settings that had somehow corrupted on the ECU were obviously wrong, I decided to load the settings from TS. After doing this though, my AFR stopped displaying in TS. The wideband guage itself has been displaying, but in TS the AFR is stuck on 7.4 no matter what I do. I have the guage analog output going to the stock sensor plug and made sure it was giving out a signal (roughly 3.4 volts on my multimeter and reading around 18 AFR, AKA working). I tried running the car both with the guage plugged in and with it removed and there was no difference in the engine behavior during cranking/idle/light throttle. In EGO control I went through all of the sensor port options and none of them registered any signal from my wideband at all. After that, I decided to undo all the changes I had made and go back to the most recent tune from yesterday where I KNEW the Wideband was working correctly with MS and TS. Still no luck.
As far as I can tell, the guage is 100% functional and none of my wiring is the issue. The tune and settings aren't the issue either because I reset those to a known good point. I've closed and reopened Tuner Studio and made sure to retest the serial connection (communications>settings). The ECU works and will run the car, but for some reason it's not giving reading the WB output anymore.
The only thing I can think to try next is maybe updating the MS firmware from 3.3.1 to the newest firmware and see if that works, but I don't know how to do that on the MSPNP2 and I can't find a guide on it anywhere.
Do any of you have any thoughts or tips?
Reply
0
0
12-27-2019, 03:00 AM
#3
Newb
Join Date: Dec 2019
Location: phoenix, az
Posts: 18
Total Cats: 1
Man, I'm gonna try that Right now!!! I even made a video
because I just got my DIYPNP two weeks ago... It actually worked with my AEM 41--- series WB controller and on Xmas eve I decided to upgrade to the registered version of tuner studio and decided to try VE live I was fine until I got to a light TS glitched and the car died... did a power cycle.. connected but as soon as it read it threw my whole tune out the window and error messages plagued my screen... anyways I let you know if I can get it to work
Reply
0
0
12-27-2019, 10:36 AM
#4
Newb
Thread Starter
Join Date: Jan 2017
Location: Round Rock, Texas
Posts: 25
Total Cats: 1
Lol look at us noobs, figuring things out without anyone else's help.
In case you're wondering, yes I went in and installed the "boot" jumper onto the board like the website's directions said. Idk if that's 100% necessary though since I saw a video where someone didn't use that jumper and the firmware seemed to work fine (aka no need to remove the ecu from the car or open it up). Worth mentioning and maybe trying.
Also the coil packs on my NB were a pain to get at to unplug so I just unplugged all 3 of the connectors at the front of the engine just inboard of the throttle body. Not sure which one goes to the coil packs, but one of them does for sure since my method worked and my car ran after that no problem.
In case you're wondering, yes I went in and installed the "boot" jumper onto the board like the website's directions said. Idk if that's 100% necessary though since I saw a video where someone didn't use that jumper and the firmware seemed to work fine (aka no need to remove the ecu from the car or open it up). Worth mentioning and maybe trying.
Also the coil packs on my NB were a pain to get at to unplug so I just unplugged all 3 of the connectors at the front of the engine just inboard of the throttle body. Not sure which one goes to the coil packs, but one of them does for sure since my method worked and my car ran after that no problem.
Reply
0
0
Thread
Thread Starter
Forum
Replies
Last Post
