what are you referring to as an info log?
what are you referring to as an info log?
There should be a few other you can change for bits and things I can't remember right now
The info log will have some info on CAN bus speed, bits, etc. so I was going to see if those all match up with the settings on the WB. I left mine on the defaults and it was fine
Connect to vehicle, hit ctrl+i in VCM Scanner, then hit the blue "i" on the screen that pops up. Post whatever it says (can take out VIN #'s and stuff if you want)Quote:
Originally Posted by JPC
It's a total guess, just something to try..
6/21/2016 4:07:41 PM
VCM Suite Product: VCM Scanner 3.0.128
Operating System: Windows 7 Service Pack 1
Microsoft .NET: 4.0.30319.42000
CPU: Intel(R) Core(TM) i5 CPU M 460 @ 2.53GHz
Available Memory: 5,015 MB
Available Credits: GM 4/8, Ford 0/0, Dodge 0/0
Available License Slots: 406/409
[Specific Vehicle]
2008 Chevrolet Express (8 cyl) 4.8 5.3 6.0, 86YPJWK2302757CJ, [LS3/4l80], (GM: 2)
2012 Cadillac CTS (8 cyl), 86ABGMK3134858FX, (GM: 2)
Hardware: 0121
Firmware: 0120
PartNumber: 0000006221
BuildDate: 8/11/2014 12:00:00 AM
InterfaceOnTime: 00:00:57.5200000
ROM: 00 3F 00 82 00 01 00 00 FF
Config: CC 00 00 00 00 40
System Info: F7 00 00 00
Comm Errors: 00 00 00 00 00
SPI Info: 00 00 00 00 00 00 00 00
VehicleConnectedTime: 00:00:57.5200000
DetectedProtocols: CAN
SAE J1979 Info: CAN, 500 kb/s, Standard 11 bit, 500 kb/s, None: 7EB, None: 7EA, ECM: 7E8
ECM: 7E8, CAN, ECM -EngineControl - E67, GM Gen4
VIN: - 2012 Cadillac CTS V, 6.2 L, 8 Cyl
Serial: 86ABGMK3134858FX
OS: 12653238
Calibration IDs: 12653238, 12648691, 12648595, 12625997, 12642972, 12642977, 12642983, 12642979
Calibration VNs: 00001D82, 0000BDC1, 00005D49, 00001F46, 0000ACA4, 00008EA9, 0000195A, 00000A03
Basic PIDs: 46
Trouble Codes:
Controller Type ID By OS: 5040
Diagnostic Requirements: None
Scanning Methods: ISO 15031-5 Mode 0x01 Functional, ISO 15031-5 Mode 0x01 Physical, SAE J2190 Mode 0x22, HPT Mode 0x23, GM Mode 0x2C 0x2D 0xAA, CAN Listener
None: 7EA, CAN, TCM -TransmisCtrl - T43, GM A6
Serial: DV1870Q518601312
OS: 24261871
Calibration IDs: 24261871, 24255389, 24262640, 24262643
Calibration VNs: 00005546, 000023D2, 00004D43, 00001856
Basic PIDs: 7
Trouble Codes:
Controller Type ID By OS: 60
Diagnostic Requirements: None
Scanning Methods: ISO 15031-5 Mode 0x01 Functional, ISO 15031-5 Mode 0x01 Physical, SAE J2190 Mode 0x22, HPT Mode 0x23, GM Mode 0x2C 0x2D 0xAA, CAN Listener
None: 7EB, CAN, FPCM-FuelPumpCtrl
Calibration IDs: 20791915, 20818975, 20808548
Calibration VNs: 0000B0E2, 0000A594, 00006417
Basic PIDs: 8
Trouble Codes:
Scanning Methods: ISO 15031-5 Mode 0x01 Functional, ISO 15031-5 Mode 0x01 Physical
This is what I was curious about.. it's the same as mine though, so no help thereQuote:
SAE J1979 Info: CAN, 500 kb/s, Standard 11 bit, 500 kb/s
Was the WB connected when you did it?
I don't think so. I did this several days ago
If you're running 3.0, you should upgrade to 3.2
I just upgraded. nothing changed, same shit.
Is everything connected and powered on, wideband included, when you repoll for supported parameters? Dumb question but figure I'd ask it.
Sounds like it should be assumed that the 30-0333 is for CAN-based ECUs, only, for the time being.
yes everything is connected when repolling. this diagram shows the gauges details. where it shows the modes to scroll through the guage, I don't have "obd2" as one of my modes. mine says "can" instead. when I select it I have an option of id1-id16 to choose from. that's it. futher down this diagram it says the ob2 settings available are "ecu" and "pid" which I have neither.... so could it be read as an o2 sensor with a specifc pid listed in the pid diagram on the attachment?
I'll check mine out tonight and see what menu options I have. They should be the same I'd think
Just to ask another dumb question, are you running the -0333 or the -0300 that has been reflashed by dr.mike?
I'm running the 0333. No it hasn't been reflashed. Fwiw it's approximately 2 weeks old
ok, I'll check mien when I get home and see if I have the same menus as you. I'm honestly wondering if it has the right firmware on it from AEM? I thought mine matched the AEM manual and it sounds like yours is a bit different
I'll confirm this evening if it isn't figured out by then
I think the issue is the Cadillac computer setup. Yours is working fine and the guys listed above is working fine but it looks like his is on a G8. JBZ channel config looks the same as mine missing the engine option under obd2 and he also has a ctsv. That's my guess.
What's the dr Mike flashing needed for? All of these guages, early models, or just certain cars need it?
The original -0300 gauge was meant to work with some kind of AEM CAN based logger box thing.. it would NOT work in HPTuners
Dr.mike re-wrote some of the firmware on that one to make it show up in HPTuners (no longer works with AEM logger box). For a little while you could send your 0300 to him and he would reflash it so it would work in HPT. At that point the 0333's did not exist.
AEM then released -0333 which included the firmware dr.mike wrote (or something similar to it) so people didn't have to keep sending -0300 units to dr.mike to be re-flashed
So, basically:
0300 works with the AEM CAN logger box, but not HPT. Can be re-flashed to work with HPT (dr.mike)
0333 works with HPTuners on CAN based vehicles out of the box (or should, anyways). AFAIK it does not work with the AEM CAN logger box.
ill attest to that. although I don't have the 30-0333 yet I was trying to help out JPC yesterday and I am seeing the same thing. I have had 3.2 loaded since it came out. but I do know that GMtech (im almost positive he has an E67) has his working although If I remember they are 03-0300's. another strange thing is I do have them in my chart parameter selector. but not in the channel selector.Quote:
Originally Posted by JPC
JPC have you tried to contact HPT support and AEM support. working together with both of them may be able to get you some positive results?
Parameter selector will show everything whether you can use it or not (unless you select the gear icon w/green check mark). Channel selector only shows channels you can actually add to the channel list and use, so that part makes senseQuote:
Originally Posted by JBZ
I wish one of you guys were closer so I could come take a look or try your WB on my car or something to see what the heck is going on
Sounds like a sensor/wiring issue.
FYI, we don't support the AEM 30-0333, you'll have to contact AEM's support for that.