CANBus Wideband on MSPNP Pro?
 

I've got my Hydra out and sold, now I'm starting to think about the installation of my MSPNP Pro. I've got the current model AEM UEGO wideband (30-0300), which has CAN outputs. I thought I read about someone else here being able to use those for a digital signal on the MSPNP Pro, but I can't find that post now. It seems like a better/more modern solution than using analog and having to worry about ground connections as much.

Does anyone know about this, or am I making it up?

From what I understand, you can directly hook up CAN connections to MS3 if you have firmware 1.5.1 or later, but have to shut off Megasquirt CAN communication since AEM reads on another protocol (so no go if you have a CAN expansion board or CAN gauge). The older method is to purchase one of these, which converts AEM CAN to MS CAN: MSLabs CAN Wideband Module

I have the same gauge and have it hooked up to my MS3 via CAN with no issues. As ace said you have to shut off CAN broadcasting, and then enable the AEM protocol on the CAN/EGO/GPS page (or whatever the equivalent is on the MSPNP Pro)

Sam, if you are interested in keeping CAN, you can get the MSlabs CAN wideband adapter.
MSLabs CAN Wideband Module

I have one and it works great. I will be selling mine soon as well if you are interested.

Okay, I'm finally setting this up, but something isn't right. I've got CAN Broadcasting turned off, and AEM X UEGO selected under EGO Data, but it's pegged at full rich with the engine off. Is there some other setting I'm missing?

Did you fix this? Got the same issue, setup as above but getting 0.00 as AFR.

can you please share details? or is this already laid out somewhere that we can find?

Have you tried turning off "29bit Megasquirt CAN Enable" in the CAN Parameters tab? Only turning off Dash Broadcasting would keep the main Megasquirt CANbus alive, which is likely interfering with the AEM bus.

So far I've got the following set:

https://cimg3.ibsrv.net/gimg/www.mia...bb22931afa.png

Things I'm unsure of / points worth mentioning:
Do I need to detail the specific can message details in "CAN Recieving" (Presume not given CAN EGO has its own dedicated setting section?)
CAN wiring itself (I'll double check my loom and ms3x)
I also have the AEM's analogue output hooked up (could this interfere? I doubt it)
My CAN id is set to ID1 in the wideband (I've tried other id's also)
I've wired "aemnet+" to CAN-H, aemnet- to CAN-L ( as per wiring in manual page 2: http://www.aemelectronics.com/files/...ns/30-0300.pdf )

I finally had a chance to look at mine again this weekend, and I had just missed one setting as I suspected.
I figured out that I just needed to change the EGO Port setting (under Fuel Settings > AFR/EGO Control) from O2 to CAN and my AEM X Gauge started working perfectly over CAN.

https://cimg3.ibsrv.net/gimg/www.mia...ea8cf13bdd.png

Question on how you wired this guy in. According to AEMs directions, the 30-0300 should be wired for AEM net through the white/blk (+) and green/blk(-). Did you use the factory narrowband O2 input pins on the MS3pro or the CAN-H and CAN-L on either the options plug or the bottom ECU side unused pins?

Also, just to confirm Sam, you are running 1.5 software which is what DIY recommends for AEM net functionality. 1.4 seems to have all the same tables displayed and if I can avoid using engine states which don't seem to be reviewed well here, I would like to stick with 1.4 but have the gucci CAN interface that this "digital" sensor seems equipped for.

Thanks

Pre 1.5 does not support AEMnet.

The connections are made to can-h can-l on the ecu. The narrowband input will be unused.

Excellent, thank you. Do you think that CAN O2 input functionality would be a reason to use 1.5? Or does the conventional logic still apply. Perhaps another question is does the MSLabs CAN bus adapter work with an MS3Pro-PNP and would that bridge the gap between 1.4 and 1.5 firmware without having to use engine states for tuning?

It was enough for me. Engine states haven't created any problems for me.

This might seem like a silly question but if you are wiring in your wideband onto the canl and can wires, does that prevent you from using the same can wires to a standalone gauge? I guess better put, can you run 2 separate can devices to the megasquirt?

The answer is in the second post.

That answer seems more specific to the AEM setup though since their protocol is different than a normal CAN protocol. I guess my question was more in theory for something like the conjunction of a CAN expansion board with a CAN gauge. Can both be used simultaneously or does enabling can for one preclude any other can device from running as an input / output?

I think it's going to depend on what CAN protocol each device is using so the answer is going to vary. Exactly what hardware are you wanting to use?

I was looking into using this gauge
https://perfecttuning.net/en/gauge/5...sal-gauge.html

Possibly coupled with the mslabs canbus wideband controller . Unsure if I want to pursue the canbus wideband controller but for sure I was interested in that gauge. I guess I wanted to know if it would limit me in the future as to what I could use.

AFAIK those can both be used at the same time.

CAN is a multidrop bus

So I've followed what was said here in terms of settings and hooking it up and Im still not getting connectivity from the wideband to the ms3propnp, is there something else that I could be missing?

Sub'd. Getting ready to connect AEM 30-0300 to a can module & MS3 pro w/FW 1.4.1

Post your tune so I can see your settings.

You will need different settings. Andrew has links.

MSLabs CAN Wideband Module

Ok, good stuff. I bought it though TSE, so I'm aware of what's posted there. I'm still just casting a wide net and trying to learn from what other folks are doing to get this set up right.

I love the research, just know that x series straight to megasquirt is completely different than what's happening with your setup.

I'll have to do it when I get home, are there any specific settings you need to see?
I'm still new to the MS setup and have not done anything with the car other than first start.

Well we actually got it sorted, the gauge wasn't sending any kind of signal out

Did you guys use termination resistor on the AEM end?

Nope just wired can H and can L to each other and set it up in tuner studio.

Does the newer MTX-L Plus work with the MSLab CAN Module?

Thanks to all that posted their settings! I am also doing an 30-0300 on an MS3PRO PnP and there's still one setting I'm a bit confused about. Under "calibrate AFR table", what are you putting into "EGO sensor"? Since the AFR gauge will be using CanBus now, and not an 0-5v signal, is this even relevant? Should I select the blank option in the pull down and write that to the controller?

No need calibrate AFR if you're using the CAN bus since that's only for the analog signal.

It's been a few months into 2021, are there any new info updates on OP's particular wideband? I moved away from the MTX I bought a few years back and was thinking about this one for my MSM project too. From what I'm gathering it's a lot more straight forward of a process than using the older analog widebands?

My apologies if my questions have super obvious answers, or are too general for a useful answer. I've been out of the game for a LONG time on my build and I'm trying get back into the hang of things 😂

(Not OP) I can confirm using AEM X-Series via CAN w/ MS3ProPnP works great. 9/10 would recommend, only caveat being using AEM Net precludes you from using other CAN devices with MS3 IIRC

One day these semiconductor shortages will end and this will go back in stock (woo native wideband). I've been trying to buy one for about a year now...

https://www.14point7.com/products/spartan-3-adv

Would having a MSLabs CAN wideband module allow you to avoid the AEM Net problem of shutting down the ability to connect anything else via CAN?

Hello, I hope you can help me:
I have this configuration with the FW 1.5.2RC16 and the wideband does not read me
I have tried changing the CAN ID of the wideband and it doesn't work either.
what am I doing wrong?

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

Instructions for using AEM widebands with MSLabs CAN Wideband Module

1. Install your CAN Wideband Module according to the instructions from our website. Complete steps 1 through 4, then stop and complete these instructions.
2. Download the CAN Wideband Module INI file from our website: http://www.trackspeedengineering.com...nd-Module.html
3. Open your TunerStudio project. Click File>Project>Project Properties. Click the "CAN Devices" tab.
4. Next to CAN Devices, click the plus sign to add a device. Next to "Device Configuration File", click the "..." button. Navigate to the CAN Wideband Module INI file, click "open", then click "OK."
5. Your project will close and re-open automatically. In the upper left-hand corner, you will see a new Device drop- down menu. Select "CAN1" (or the custom name you used for your CAN module), then click "CAN Wideband Module Setup" at the top of the screen. Click "CAN Wideband Settings" from the dropdown menu.
6. Next to "Wideband Model" select "AEM" , then click "Burn", then "Close".
7. Click Tools>Calibrate AFR Table. Next to "EGO Sensor", select "Innovate LC-1/LC-2 Default" (not a typo - you must select Innovate even when using an AEM wideband). Click "Write to Controller", then "Close".
8. Complete steps 5 through 18 of the normal instructions.


Did you follow the instructions in step 7?

I use the AEM X UEGO and I want to connect it to the ms3pro via can as in the attached photo, I have the same WB.
I connect it directly to the CAN of the MS3PRO but in the software configuration it seems that something is wrong.
Question, is it very necessary to use the "MSLabs CAN Wideband Module"?
or the AEM X UEGO can't be connected directly?
https://cimg9.ibsrv.net/gimg/www.mia...2f251d940a.png

No, if you do some searching you can find some posts on how to set up your MS CAN to work on AEM Net but you will loose the ability to connect any other CAN devices to your network.