Your wiring is correct. Yes, you can leave the analog output connected. The ground doesn't matter any more, you can use any ground for the aem and the module, in fact it's best to use DB37 pin 3 for the module and any other ground for the aem.

One last dumb question (likely not the last actually).

Regarding power sources... VVT, WB02 and CAN module, do any of these need hot while cranking sources?

I can't decide how I am going to power the WB02 and the CAN Module. Which one would be best to power through the megasquirt 5amp power out? I assume that line on the db37 stays hot while cranking. I have another hot while cranking source I've got ready to use (airbag module).

You can use the white/red from the DB37 for both. The wideband doesn't pull more than 2 amps, while the module only pulls 20mA or so. The CAN module does need power during cranking or TunerStudio may throw error messages.

See, I lied about the stupid questions... Thanks a ton for the hand holding help.

Are there any other pins that the CAN Module's serial connectors that could get used in the future? I ask because I'm going to make the serial dongle tonight for the WB02 and I'll add a few extra wires/pins if there could be future things.

Nope, the serial port only carries the serial signal, nothing else.

noob question....
I just installed my ms3 basic and can module yesterday. my wideband is an LC2.
should I get a/f readings in tuner studio before I start the car? I haven't tried to start it yet. It is connected and the tps is working correctly.

I found on the other thread on this subject there are instructions for the can module. I will try again later to get this working with the instruction sheet.

I got it all working today with the instructions. Runs good already

Can the can module and the WB02 share the DB37 ground? If not, should I give the AEM it's own clean home run ground or will any old ground do?

See answer below. You can share them but I wouldn't as doing so would likely require you to use a longer than necessary ground wire for the WB02 controller. Instead, use any chassis ground for the WB02 controller and DB37 pin 3 for the CAN module.

If you have V2.2+ Basic MS3 or a V5.0+ Enhanced MS2, use pin 2 for the wideband, and pin 3 for the module.

In any other case, it's best if the module and wideband do NOT share the same ground.

The "Instructions for the MS Labs Basic MS3 ECU, V2.0+" I received did not contain a DB37 pinout. Is the Basic MS3 V2.2 DB37 pinout the same as that listed in your V3.0+ instructions with Pin 2 Device ground (Convenient ground supply for accessories) and Pin 3 Analog ground (Ground for analog sensors)?

Mostly yes. The V3.0+ units have more programmable outputs and analog inputs, but everything else is the same.

Roger that. Thanks man.

Ditto, thanks for the help on my hand holding baby questions. Sorry to ask such stupid ones but I'm really trying to go overboard on my wiring and make it modular/clean and futureproof.

I've got everything moved over to the passenger side airbag and I have a double redundant system with the idea that I have the ability to recover from a failure and soldier on with the track day no matter what happens:
1) MS3basic and Can WB02 Module
2) Stock ECU with vvtuner
3) Added circuit fuse box on switched relays with clean power
4) home run clean ground distribution box

It was a process to do the initial setup getting everything moved and now I'm going back in for the first time to redo things now that I know what I know and convert the car to can wbo2.

You're support was what made all this possible. Before I got your ms3 and accessories I had never touched a wire on any car I ever owned.

In photo, MS3, VVtuner, Can wb02, 6 circuit accessory fuse box.
https://www.miataturbo.net/attachmen...ine=1452786064

Hey Reverant, any chance of getting this to work with the PLX series gauges? I know they also use a digital serial interface to communicate with their gauges, I'd imagine it's just an issue of reading the serial output and adjusting the code to parse it. Has there been any work done on this? If not, would rigging up some kind of arduino to log a sample of the serial commands running up/down the line help you be able to code for it for this box? Thanks!

The newer V2.1 boxes theoretically support it. I haven't tested them with an actual PLX SM-AFR Gen4, only with a simulator. If you want to give them a try, go ahead.

Question about wiring. What do you recommend for the power and ground? Is it okay to use the wideband power/ground?

Edit: disregard, see an earlier post with wiring. Sounds like the module and wideband should have separate power and ground connections.

So having some trouble with the CAN module. Can anyone tell me what the LEDs indicate?

So has anyone tried updating their CAN module firmware yet? I've got one of the early boxes from 2014 and thinking about updating to firmware version V1.0.4 that I found out about thanks to Track Speed Engineering (hey Rev - your website sucks!)

His website can't suck too much if it helped you discover a new version of a firmware for a part you have :loser:

Can you share the link? I'll give it a try.

I have an older unit too. How can you tell what firmware it's loaded with? Are there instructions for updating the firmware? Also, what changed in the 1.0.4 release? ie: is it worth the effort to upgrade

The firmware is not upgradeable. The different firmware versions are due to different hardware revisions of the board (V1.0, V2.0, V2.1).

Well that settles it then.

I'm having problems getting it working.

https://cimg3.ibsrv.net/gimg/www.mia...6c8de59526.png

https://cimg4.ibsrv.net/gimg/www.mia...107b7b959e.png

https://cimg5.ibsrv.net/gimg/www.mia...e8ba084263.png

Make sure the CAN Module's ID is set to 9 in your project properties.

It is.

is the CANegt internally terminated? I'm also running a microsquirt I/O.

There's a jumper inside the unit for termination. If you are running a microsquirt for I/O, then you need to remove the jumper.

Also make sure the unit is receiving power. The red and green LEDs should be on.

Where are the LEDs?
Are there holes or are they internal only?

They are internal. There are also LEDs for CAN comms between the MS3 and the module, for serial and OBD. If the module is correctly connected to the CAN bus and you've set the CAN option to fetch the data through the CAN EGO system (ID 9, table 0, offset 0), the CAN led should be blinking as well.

How about using the #21, Blk ground for the CAN Module? (MS3-Basic). Would that be better or worse than using the Pin3 blk/grn Sensor ground?

https://cimg6.ibsrv.net/gimg/www.mia...cd546b3ed3.jpg

https://cimg7.ibsrv.net/gimg/www.mia...f4a44950da.jpg

https://cimg9.ibsrv.net/gimg/www.mia...fb54418fe7.jpg

I don't see a jumper?

plus, red and green lights are lit as well as flashing blues.

Are both blue LEDs flashing?

Yes, well... they are both lit. I'll have to double check.

Check if they are flashing. Make sure you have the CAN EGO option switched on,

Ok. Will do when I get off of work. if there were a jumper installed, where would it be?

Next minor question- I see a v102 file on trackspeeds website and a v104 file somewhere else. Are they BOTH for running both AEM and Innovate or is the v102 the only version compatible with AEM? Which should I use?

EDIT: I pulled my laptop out during lunch and checked. Looks like v104 is what I want. One thing I noticed was that under the CAN setup tab when I first installed the .ini file, I was unable to select which CAN ID I wanted that .ini to control. If I close the dialog after creating the CAN device and reopen the properties window and select the CAN devices tab I can then select device ID #9.

How does the device know it is #9? Is it that way from the factory? Theoretically if I wanted to use a second CANegt box, I would need to install one, change the CANegt boxes device number to something other than 9, and then install the next one (which will then be #9?).

I am trying to understand this whole thing.

https://cimg2.ibsrv.net/gimg/www.mia...2aa72b70ac.png

Your board version requires the ini v1.0.2, not 1.0.4.

The module's ID is set to 9 by default. So that's what you should use.

When I set "connected devices" to 9 it worked fine. I don't know if it's the current tunerstudio version but as I mentioned I couldn't select that when I set it up.

thanks for the help.

Back to FW. The instructions that I have suggests that I load FW 1.04 in order to be able to see the CAN in T/S. Do I understand that correctly?

At this point, I have the MS working properly with the CAN module on 1.02. (I have not started the car yet, but TS properly shows 14.7 during warmup and then full lean, as expected.

2nd question: Is there a way to have a TS gauge that shows the CAN WB reading (as it does now) and a separate one that displays the results of the LC-2 Yellow wire which is still connected? This is just for an temporary reference of how much my tune might have been off before.

3rd question: 1.4.1 FW on MS3 allows a setting on the CAN screen to ignore the smoothing. If that is set, does it matter if I change the smoothing to "100"? Just being inquisitive here.

If your original instructions said to use 1.0.2, use 1.0.2 and not 1.0.4 or you'll break things.

You can connect the yellow wire to any of the spare analog input instead and use a generic sensor input calibration to watch the offset.

No idea on the 3rd.

I think I meant to say update from 1.01 as shipped to 1.02. Unfortunately, I'm not with the unit or instructions. I will do whatever the instructions say to do.

No, do not update. The ini version is firmware/board specific.

Even better. Leave well enough alone and all that.

Looking for troubling shooting tips.

I have a fresh MS3 basic build. Can't seem to get the wideband CAN unit to communicate to the MS3 unit. I keep getting this

Should I try another "remote CAN id"?

I dumped my LC-1 and upgraded to the LC-2. This solved all my problems.

I am having the issues you had but the stuff you tried is not working. Put it back on analog for now and will re-attack when it is not 1 million degrees outside.

Has anyone had any success with this module fetching the wideband oxygen sensor AFR via the obd2 port using a Bluetooth adapter and a smartphone app like DashCommand? I can see rpm and a few other basic items but having trouble accessing AFR via the app. I don't want a scanguage-II.

Bueller? It takes me 10 seconds to connect OBD Fusion to my Volvo to read AFR. But when I connect to my Miata I get nothing, despite the software recognizing the PIDs for oxygen sensor and AFR as valid. When I try achieving the same goal by entering a custom PID manually (Mode 22, PID 0134) I still get no data. I'm sure this is probably just a config/user error on my part. Anybody have any luck?

Here is what I see when I connect to my Volvo. This is what I want to see when I connect to my Wideband/ CAN/ OBD2 module.
https://flic.kr/p/WpAytb

This is what I actually see when I connect to my Wideband/ CAN/ OBD2 module.
https://flic.kr/p/W5gN4Y

I can confirm that Mode 0x01, PID 0x34 are the correct ones to use.

Thanks. I'll give it a try.

is the MSLabs wideband CAN interface compatible with mspnp pro?

yes. I am doing so now (and over the last year or two) myself.

cheers. appreciate that info.

How do you calibrate the o2 sensor even using this? I'm using Innovate wideband, and when I follow the calibration instructions (unplug the sensor and power on the car to get an error code) the error code doesn't show up.

Thanks!

It does. Follow the instructions and install the ini file for the can module, you will then have an additional gauge cluster which has status/error gauges.

I bought one of these earlier this year to use in conjunction with a PNPPRO running pre-1.5 FW (1.4?), and I'm strongly considering replacing my innovate LC-2 with an AEM at the same time just because the innovate seems to destroy sensors really frequently.

I'm wishing to buy a AEM 30-0300 X-Series, but I don't see it in the compatability list. Can you confirm that I should go with a AEM UEGO instead?

It is compatible. It also supports the AEM's CAN mode, in which mode it also fetches whether the sensor is ready or warming or has failed, to disable the EGO correction, something that the stock MS3 firmware doesn't support without the module.

I've got a DB9 and a DB15 on my module. The instructions say to connect the serial out from the WB controller to pin 2 of the serial port. Is the serial port the DB9, or the DB15? I can't seem to find the answer anywhere.