When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
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.
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.
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
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.
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.
0
