Ok! Finally got the mazdaspeed started today after installing the mspnp pro and aem wideband... it's been a journey of stupid issues to this point, but it seems as if I at least have the car and gauge up and running and communicating with each other and my laptop.

The issue that im having is that the gauge reading and the tunerstudio readings don't match (off by at least 1 point) . I have the gauge grounded to pin A, and signal (white wire) to pin C, power coming from the power window 12v source. When I go to the drop down menus for uego selection, it doesn't list the 30-4110 sensor/gauge. So I assume I have to use the custom linear wideband option and configure it manually. (I have tried both aem selections available and neither seem to sync things up)

my aem gauge reads 10-10.1 far at idle, and the tunerstudio gauge reads 11 or so in its current configuration. Both gauges do respond to changes in afr i so both are getting signal from the sensor itself.

any guidance/flaming is appreciated, I'd like to get things working correctly so I can really get a chance to play with this thing

 

You need to calibrate the sensor on tunerstudio. Do a search, there are tons of threads on this.

Let me try to find the recent one where Aidan and Brain helped me out.

Edit: Here's the thread: https://www.miataturbo.net/megasquir...ettings-92849/

 

Thanks! I'll try the values listed in the thread, I've been reading and it seems aem's published values are wrong
don't know how I missed that thread in my searching

 

This is why I spent the extra $20 on the 03-0300 and plan to feed the wideband signal over CAN... Don't have to mess with this calibration nonsense.

 

No problem. I asked the question there and it helped me out so I feel obligated to post a link every time it comes up again!

 

Using the can module? Good luck with that.

I don't really see why people are so overwhelmed by this: you adjust 2 values until the numbers match up. linear curve. takes 10 minutes

 

Yup. Not a huge deal at all.

So easy, I could do it!

 

I just had this issue with my AEM X-Series. I fixed mine by selecting the correct WB in the EGO Sensor drop down in the Calibrate AFR Table menu.

 

it's just a huge pain in the *** when the manufacturer gives you the wrong numbers to input

 

I don't think that's the actual issue.

I think the actual issue is that every Miata has huge variances between voltage, grounds, noisy signals, and then you also have different installs tapping into different power and ground sources, etc.

I've had to install various widebands into Miata's and this isn't just limited to aem, and different cars/installs required different voltage offset corrections.

 

New issue, tunerstudio isn't following changes in the wideband readings at all now, I think I have a problem with the output itself. At this point, if I unplug the sensor from the gauge and force it to read/output a 14.7 afr, tunerstudio doesn't even see that. Looks like I'll be taking things apart again tomorrow and measuring to see if the gauge is even sending a signal to the ms at all. Not sure why this issue could have developed overnight with no other changes unless I have a faulty gauge/controller

 

Ok so the gauge is outputting 2.37v @ 14.7 afr with the sensor disconnected, and it is outputting voltage with it connected as well. The plot thickens

 

No, the x-digital has CAN output built in. Connects directly to the canh and canl lines on the megasquirt, requires no calibration. I went through the same exercise on my lc2 (analog calibration) and was never confident the calibration didn't change with conditions - rpm, battery voltage, etc

 

That's pretty cool. I'll have to check that out

 

That does sound pretty nice to deal with

 

hey I just picked up one of those wideband's and having some difficulty connecting it the ms2. I was wondering how you made it work?