Connecting a MS3 Basic to an AEM Uego 30-0300 X - Wiring Clarification
 

I just ordered an MS3 Basic, I have the AEM in my hands, and a GM IAT is on its way from DIYAUTOTUNE

I have been going over the wiring as I am fairly terrible conceptualizing it.


1. Could someone confirm this is the correct way to wire everything?


AEM Red Wire > White/Red wire on DB37 Harness

(This gives the AEM it's power, inline harness already in the MS3)

AEM Brown Wire > Black/Green wire

(The AEM's Analog Sensor ground connected to the MS3's Analog Sensor ground)

AEM White Wire > Yellow wire

(The AEM's Analog Signal wire connected to the DB37's Analog Input wire)

2. It also looks like there is a black ground wire on the AEM, can I also connect that somewhere on the ECU, or would I be better off grounding it to the engine block?

3. Other than these 3 (or 4) wires, is that all I need to wire up for the wideband to work properly?

4. Do I need to use the OEM O2 Sensor Harness at all? I have an old O2 sensor I could use the connector from if I need to.

5. Regarding the GM IAT Sensor, it looks like it should hook directly up to the OEM Temp Sensor harness without any additional fiddling(except for splicing some wires), unless I need to ground it to the ECU?

Thanks!

The best wire up with the AEM 30-0300 to the MS3 Basic is via CAN - it will give you spot on reading on the MS.

Connect the red and black from the AEM to the MS3 basic like it show on the MS3 instructions PDF, connect the white/black and green/black to the CAN on the MS3, black and white - pin 8 and 9.
Upgrade your MS3 firmware to 1.5.1 for CAN wide band.

About the GM temp sensor be more specific about how you think to connect it.

I don't believe the basic version of the MS3 has CAN integration built in, the module typically used to convert the signal doesn't appear to be listed on their site anymore, could be out of stock. I had to pull it up via archive.org to see what it looked like.

Regarding the firmware 1.5.1, I can try that however the base-map is made for 1.4.0, and I am unsure if the basemap will work with the engine states feature in that firmware revision. I don't mind hooking up the wideband via a slower connection if it means I can stay on 1.4.0, it is more established and most tutorials here are geared toward it. I will probably end up asking much less inane questions if I can get the car running on 1.4.0 rather than 1.5.1.

Regarding the GM IAT Sensor, I did a bit more research and I confused the wiring between the OE Temp Sensor & The MAF sensor I will be replacing. It looks like it should be plug & play once I wire the connector the kit comes with.

My MS3 Basic is on 1.5.1 and connected via CAN directly to the AEM 30-0300.... (that is why I gave you this info....) - I have the CAN wideband module but I do not use it - I connected the AEM directly to the MS3.

It is not about slower/faster connection, it is about 100% sync with no calibration between the MS and the AEM.
Firmware upgrade using TS was the smoothest upgrade I have ever done to any MS I have/used - everything was restored and I had nothing to re configure.

The GM temp sensor needs to be connected to the IAT sensor pins on the MAF connector.

https://cimg9.ibsrv.net/gimg/www.mia...50661cd3f5.png
From Braineck instructions.

OP has a NB2. That diagram is for a NA8.

I did not see the MK of the OP, any way:

"99-05
Your AIT sensor is located behind the MAF on the intake pipe, unplug it and use that connector in the same fashion as the above."

OK, my mistake. I will try connecting the wideband via CAN directly to the MS3 Basic, will also update the firmware to 1.5.1 and see how it works once I have some free time

I have found a very useful thread clarifying CAN output for AEM Uego Gauges I will be referencing for setup

Tune the ECU as-is first, using the analog input. Once you are more comfortable, you can update to 1.5.1.

For nb iat sensor, chop off old sensor and splice in the 2 wires from the new sensor. No polarity. Done.

I made this for myself as I am really bad with this stuff, hope it helps somebody

https://cimg3.ibsrv.net/gimg/www.mia...a9b9f5f6bc.jpg

I fail to understand why would you prefer to connect it via analog and suffer mismatch reading between the ecu and AEM when you can connect it via CAN and have it 100% accurate...

Maybe its because I am not sure how engine states work, my basemap is made for 1.4.0, and I would prefer to start from a known configuration that is stable enough that my ECU creator decides to still make their basemaps for? It should be pretty easy to re-wire it for CAN when I am comfortable, there are plenty of people on here who simply run the car on firmware that is pre-engine states due to their distaste of it, and there is little documentation on how they work and interact, even on this forum.

There is a thread for that

Read it to (EDIT) post #23 where issues were solved.

Thank you for that link, I suppose I could upgrade to 1.5.2/whatever the most recent MS3 firmware is and give it a try, however I would like to try starting the car with it wired in analog and see how bad the disconnect is between tunerstudio & my AFR gauge after I get everything calibrated. If I have issues with it I will look into upgrading to 1.5.2 after I learn a bit more about engine states

So I wired it up using analog with the 1.4.0 basemap, the car started right up, I fixed the timing, calibrated the sensors, and started using VEAL to tune fueling. Great basemap, once I tune my idle a bit more it should be perfect for daily use.

I didn't notice much mismatch between the analog gauge and tunerstudio, I think the two ground locations helped. I grounded the sensor on the back of the engine block on the cam angle sensor cap location, everything else was attached to the DB37 options pigtail as I outlined in the diagram. The only other thing I needed to buy was 10 ft worth of 4/32" Vacuum line for the MAP sensor.