CDR v3.1 and v3.1.1 software versions do not support collecting data thru the DLC on the 2009 Dodge Journey.
The coverage notes for these vehicles were confusing because note 6 was intended to be generic and applicable to all supported Chrysler vehicles except for the vehicles that included note 7.
The Help file notes were changed in CDR v3.2 which now supports DLC data collection thru the DCL on the 2009 Dodge Journey. CDR v3.2 help file has also been changed so that it is less confusing.
When you attempt a download of an unsupported module, it will return a message in the File Information block tht there was "data not retrievable." Attempting to retrieve data but that attempt being unsuccesful does nothing to what, if anything, is in the module.
Sorry, no. Since a CDR file should be reviewed in the latest version of the CDR program and that formatting may change from version-to-version, there would be no real way to provide a "sample data" report. Having said that, check Volume 5, Issue 1 of Collision Magazine for a list of the general data elements available by vehicle make and model for vehicles supported by the CDR program.
Actually, that question is NOT so simple. Depending on the type of vehicle you're asking about there may be more than one "brake switch" referenced in a CDR report. Generally speaking; however, an indication of "brake switch = 'off'" - assuming it is actually a monitored parameter - means the switch isn't closed, not whether ornot there was braking or the brakes were "applied."
No, it is not. What you're proposing is called "VIN Spoofing" and it is specifically NOT a supported process and is strongly discouraged. Assuming that you DO actually get the CDR program to communicate with the otherwise UNsupported module, you CANNOT be sure any recovered data is translated correctly. Part of the proper translation process often includes a reliance on the VIN and "spoofing"a VIN may result in data being incorrectly translated.