CANBus Wideband on MSPNP Pro?
#1
Senior Member
Thread Starter
iTrader: (2)
Join Date: Jun 2006
Location: Wisconsin
Posts: 1,269
Total Cats: 7
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?
Does anyone know about this, or am I making it up?
#2
Senior Member
iTrader: (1)
Join Date: Dec 2010
Location: Farmington Hills, MI
Posts: 1,218
Total Cats: 175
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
#4
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.
MSLabs CAN Wideband Module
I have one and it works great. I will be selling mine soon as well if you are interested.
#5
Senior Member
Thread Starter
iTrader: (2)
Join Date: Jun 2006
Location: Wisconsin
Posts: 1,269
Total Cats: 7
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?
#8
Senior Member
iTrader: (1)
Join Date: Dec 2010
Location: Farmington Hills, MI
Posts: 1,218
Total Cats: 175
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.
#9
So far I've got the following set:
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 )
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 )
Last edited by adlb; 03-10-2018 at 08:00 AM. Reason: get picture working
#10
Senior Member
Thread Starter
iTrader: (2)
Join Date: Jun 2006
Location: Wisconsin
Posts: 1,269
Total Cats: 7
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.
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.
#11
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
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
#13
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?
#15
Senior Member
Thread Starter
iTrader: (2)
Join Date: Jun 2006
Location: Wisconsin
Posts: 1,269
Total Cats: 7
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
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
#17
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
#18
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?
#19
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?
#20
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.