AEM X SERIES Can-bus troubleshooting and Internal settings

There is no post anywhere, either here or on their crap explanation video. There is no technical data explaining how to use the x-series or why the settings are what they are.

#1 - If it doesn't connect or it stops connecting, disconnect, reconnect, etc. Do not mess with the settings internally. No Can-Bus vehicle will have issues other than the random connection issue.

Make sure the first ecu setting in the gauge controller is set to #7, set the other ecu setting (What the controller identifies as) to #4, this will never interact or overlap other ecu's
The can-bus system works as 7x* - * being the sub-computer in the network, 1 will be the ecm, 2 is transmission (unless its included into the ecm) 3 will be the fuel control module if the vehicle is equipped with one. So setting the controller to 4 will be perfect for any vehicle.

If you have also messed with the bit-rate, the maximum data rate is 1Mbit/s, but this is the raw rate, there are 46 "management" bits for up to 64 data bits. This reduces your net data rate to about 580kBit/s.

The bit-rate is something you will have to mess with because I can't really remember right now.

#3 Connect to the vehicle, but do not start a datalog.
Attachment 102071

#4 Click "Repoll for parameters" as shown in the photos
Attachment 102072

#5 add the wideband from the parameter list to your logged PID's, it will show up as a fourth, third, or second controller. But will always identify as 7x4
Attachment 102073

So, now that you know more than the company selling these apparently does, enjoy your new wideband.

The best practice is to use the VCMScanner VCM Suite Info to determine which ECU IDs are, already, in use. #4 #6 and #7 are USUALLY available. But, some applications use an odd combination of IDs. Also, some people get confused by the pairings of the ECU IDs. As, each ECU uses 2 ID's ( request and reply ), 8 digits apart. They go like this:

#0 7E0/7E8 PCM
#1 7E1/7E9 TCM ( usually )
#2 7E2/7EA
#3 7E3/7EB
#4 7E4/7EC
#5 7E5/7ED
#6 7E6/7EE
#7 7E7/7EF

The VCM Suite Info shows the reply ( 2nd ID in each set ), so for ID #2, it will show 7EA, etc.


Setting the PID# to a number larger than 4 makes the AEM WB easier to find, in the add channels list. If using 2 WBs, set one of them to 5 and the other to 6. At least, that's what I do.

Ignore the EF1 and EF2 settings for the PID#. They are specifically for EFILive V8. And, I'm pretty sure, they will cause issues with HPTuners.


The bitrate is what it is, regardless of protocol overhead.

Both the Bitrate and ( indirectly ) the ID bit address size are in the VCM Suite Info log.

if you see ECU IDs that look like 7E?, that is 11-bit. If you see ID's that look like 18DA1?F4, that is 29-bit.

99%, leave the bit rate at 500 for and the bit size at 11-bits. Unless, the VCM Suite Info log specifically shows otherwise.

Knowing that much can prevent a lot of chasing your tail, using multiple combinations of incompatible settings.



Here is an example of the VCM Suite Info log. The important parts are in RED
In this case ( tester on my desktop )

The interface is CAN @ 500kbps

There is only one ECU ,#0 ( The PCM) @ 7E0/7E8, because, that's all I have connected, on my desk. In a real application, there will be multiple blocks, with more ECU IDs.

Since the ECU address is 7E? The bit size is 11-bit


Since only ID #0 (7E0/7E8) is in use, all other ECU IDs ( #1 .. #7 ) are free, in this case.


( you need to scroll down, a bit, to get to the good stuff. )
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>

8/5/2020 5:41:45 PM
VCM Suite Product: VCM Scanner 4.6.3

Operating System: Windows 7 Service Pack 1
Microsoft .NET: 4.0.30319.42000, 4.7.1 or later
CPU: Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz
Available Memory: 22,811 MB


Device ID: xxxxxxxxxxxxxxxxxx
Application xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx xxxxxxxxxxxxxxx


Device ID: xxxxxxxxxxxxxxxxxxxx
Credits Purchased: 0
Credits Used: 0
Credits Available: 0
Licensed Features: Pro Feature Set,


ConnectionMethod: USB
ID: 2051900463
HardwareVersion: 1.4.0
ManufactureDate: 12/6/2018 8:32:57 PM
PartNumber: 6230
FirmwareVersion: 3.0.30
PoweredOnTime: 00:17:31
VehicleConnectedTime: 00:17:30
VehicleDiagnosticConnector: 1


Protocol Info: ISO 15765-2, J1962: CAN, 500 kb/s

8/5/2020 5:41:45 PM
VCM Suite Product: VCM Scanner 4.6.3

Operating System: Windows 7 Service Pack 1
Microsoft .NET: 4.0.30319.42000, 4.7.1 or later
CPU: Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz
Available Memory: 22,811 MB


Device ID: 1311592705
Application Key:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx


Device ID: 2051900463
Credits Purchased: 0
Credits Used: 0
Credits Available: 0
Licensed Features: Pro Feature Set,


ConnectionMethod: USB
ID: 2051900463
HardwareVersion: 1.4.0
ManufactureDate: 12/6/2018 8:32:57 PM
PartNumber: 6230
FirmwareVersion: 3.0.30
PoweredOnTime: 00:17:31
VehicleConnectedTime: 00:17:30
VehicleDiagnosticConnector: 1


Protocol Info: ISO 15765-2, J1962: CAN, 500 kb/s

ECM: 7E8, CAN, ECM - MED17.1 B, VAG
VIN: LFV3B28R8A3025310 - 1980
OS: 8R0907115M__0002
Calibration IDs: 8R0907115A-Q0006
Calibration VNs: 12637084
Basic PIDs: 82
Trouble Codes:
Controller Type ID By OS: 50019
Diagnostic Requirements: Init CAN 0x10 0x03
Scanning Methods: ISO 15031-5 Mode 0x01 Functional, ISO 15031-5 Mode 0x01 Physical, ISO 14229-1 Mode 0x22, CAN Listener, CAN, ECM - MED17.1 B, VAG
VIN: LFV3B28R8A3025310 - 1980
OS: 8R0907115M__0002
Calibration IDs: 8R0907115A-Q0006
Calibration VNs: 12637084
Basic PIDs: 82
Trouble Codes:
Controller Type ID By OS: 50019
Diagnostic Requirements: Init CAN 0x10 0x03
Scanning Methods: ISO 15031-5 Mode 0x01 Functional, ISO 15031-5 Mode 0x01 Physical, ISO 14229-1 Mode 0x22, CAN Listener

also check in the menu that u have "obd2" listed, if u dont have that an u only have "can" listed then u have the wrong firmware and wont pick it up in the data, been hearing about that a bit lately but AEM know about it so contact them for replacement

If you love games and want to discover something new, I can help you. You can check hot seven and try it out. Maybe you will like it

Quote:

---

Originally Posted by 07GTS

also check in the menu that u have "obd2" listed, if u dont have that an u only have "can" listed then u have the wrong firmware and wont pick it up in the data, been hearing about that a bit lately but AEM know about it so contact them for replacement

---

Is this a common problem with the AEM X series? I've had an analog input Ballenger on the left bank of my late Gen4 truck for years, had an AEM 30-0310 inline that I used with serial input when I needed to tune my other cars, and wanted to add it to the right bank as a permanent install. I do not get any controllers listed other than ECM, TCM, and FPCM....no OBD controllers listed even after multiple attempts of repolling, adding channels, even trying to use the switch inside the inline AEM to change the PID. The only PIDs that show up are the external sensors when searching for "WB". Trying to remember when I bought the 30-0310, it may have been 3+ years ago.

Quote:

---

Originally Posted by NotSure

Is this a common problem with the AEM X series? I've had an analog input Ballenger on the left bank of my late Gen4 truck for years, had an AEM 30-0310 inline that I used with serial input when I needed to tune my other cars, and wanted to add it to the right bank as a permanent install. I do not get any controllers listed other than ECM, TCM, and FPCM....no OBD controllers listed even after multiple attempts of repolling, adding channels, even trying to use the switch inside the inline AEM to change the PID. The only PIDs that show up are the external sensors when searching for "WB". Trying to remember when I bought the 30-0310, it may have been 3+ years ago.

---

Did you figure this out?