Here you will find short summaries of changes between the different firmware revisions. Developers should read the detailed changelog found inside the respective update archive. To install an update, download and extract the archive, then run StnFirmwareUpdater.exe.

Important Notes

1. If you have an OBDLink with Bluetooth option, be sure to switch the Bluetooth baud rate to 115.2 kbps before upgrading the firmware from version 2.0.2 or older to version 2.1.0 or newer. Alternatively, you can manually set the baud rate to 38.4 kbps.
2. Some diagnostic software may not work with versions 2.1.0 and above. Check to make sure your software supports 115.2 kbps before upgrading, or manually set the baud rate to 38.4 kbps.
3. Downgrading from version 2.x.x to version 1.x.x will cause all programmable parameters (AT PP) to be reset to factory defaults.

Latest Version 4.2.0

Release Date: February 2, 2017
Level of Importance: Recommended
Download

This major release fixed several serious bugs including:

• CAN message loss or corruption due to CAN bus errors
• ATPB could cause auto-filtering not to be set up correctly
• Undefined behavior if reset during startup
• ATMA command cleared CAN H/W filter on exit
• ATMP commands cleared all current filters on OUT OF MEMORY error
• ATBI/STPO did not activate pending USER1 protocol configuration changes
• Automatic generation of 11-bit flow control ID pairs for segmented message transmission
• UART transmission lock ups
• ISO 9141 keep-alive messages

The major release added many new features including:

• Turn LEDs off/on
• Extra data parameter for the STPX command
• Set CAN addressing modes
• Set and read CAN timing registers
• Support for 7F xx 78 response pending messages
• Report factory calibration status
• Fail-safe clock monitor
• Complete ISO 15765 multi-frame message support
• CAN Rx multi-frame message assembly
• CAN Tx message segmentation
• Arbitrary OBD message transmission
• Set minimum time between the last OBD response and the next request
• Other stability and performance improvements

See obdlink-changelog.txt inside the archive for detailed descriptions of the changes.

Version 3.3.0

Release Date: September 26, 2012
Level of Importance: Recommended
Download

This major release fixes a number of serious bugs and introduces many new features.

See obdlink-changelog.txt inside the archive for more details.

Version 3.1.0

Release Date: May 16, 2012
Level of Importance: Recommended
Download

This major release fixed three serious bugs:

• The device would sometimes lock up while monitoring a busy CAN bus.
• Due to a race condition, heavy UART Tx traffic sometimes would generate FATAL ERROR 0x0101 [5, ..]
• KWP2000 fast init would not work reliably with vehicles that have multiple ECUs responding to StartCommunication message.

The following major new features were implemented:

• New AT and ST commands, including:
  • Set/report protocol
  • Protocol open/close
  • Enable automatic filtering mode
  • Set automatic check byte calculation/checking
  • Set CAN monitoring mode
  • J1939 header formatting, response timeout multiplier
• Ability to turn off J1850 CRC calculation and checking
• Removed length limitation for certain types of messages
• Increased CAN buffer size
• Increased UART buffer size
• Other stability and performance improvements

See obdlink-changelog.txt inside the archive for detailed descriptions of the changes.

Version 2.2.2

Release Date: January 11, 2011
Level of Importance: Recommended
Download

This release fixes a few minor bugs and introduces the following new features:

Mario party 3 wii wad download. Mystics Apprentice rates this game: 3/5 When Mario Party 3 came out I was already well engrossed into the Mario Party series, and was excited to try another one out. This game was very much like the other 2, but again with more improvements, but also a few flaws.

• Voltage-based PowerSave triggers
• Higher precision voltage measurement

See obdlink-changelog.txt inside the archive for more details.

Version 2.1.2

Release Date: August 25, 2010
Level of Importance: Recommended
Download

Bugfix release (see obdlink-changelog.txt inside the archive for details).

Version 2.1.0

Release Date: June 24, 2010
Level of Importance: Recommended
Download

This release changes default baud rate to 115.2 kbps.

Version 2.0.2

Release Date: June 24, 2010
Level of Importance: Recommended
Download

Bugfix release (see obdlink-changelog.txt inside the archive for details).

Version 2.0.1

Release Date: June 8, 2010
Level of Importance: Recommended
Download

This major release introduces the following new features:

• Support for the SAE J1939 (protocol for heavy-duty vehicles)
• Custom CAN protocols
• Support for majority of the new ELM327 v1.4 functionality
• Changes aimed at improving the stability of communication with 'problem' vehicles

Previous Releases

I purchased this 3130c model to help me resolve an ABS -VSA malfunction created by installation of two rear Reybestos (brand) hub/bearing units on my 2008 Honda Accord. I am a retired mechanic shop owner who also savy with computers. After researching my options for such a ScanTool, I purchased this for its' abilities to read ABS fault codes in addition to OBDII emission fault codes, and for some vehicles, OEM fault codes (but did not read OEM codes for my 2008 Honda Accord). With a few quirks, I think it was a good deal at a fair price. This scantool is more than a fault code reader as it can also read live date from inputs connected to your emission system. Internet Quirks: The 3130c and its' PC-Link for printing reports works, but did require me to create an account with password (it was free). There are additional resources on the Innova website including 30day fix assistance (for emission code faults only/ NOT ABS. which I found out by buying/ then getting refunded), title report, or one year support. ABS Quirk: I got 3 codes from the ScanTool for my disable ABS-VSA brake system (basic brakes still worked) which helped me out big time. I like the FixAssist info. that points at the problem area in way a mechanic can make sense of. The 3 codes on the ScanTool made sense to me, plus were codes I could also look up on the internet. ABS Quirk 2: When I went to print a report via the PC-Link connected to Innova Website, the printed report translated the 3 code of ScanTool into nonsense codes. When I sought tech support to understand that, I was first told it was related to old stored codes. Then when I told them that did not make sense to me, because I ran the ScanTool through its' paces and there were no other stored codes.. they offered me an upgrade to the 3130e model (not yet offered here 11-15-2016.) While I think I'd buy the 3130c again & liked how it could erase my ABS codes to see if they reappeared, .. I like the 3130e model better. It read & listed 12 Honda OEM ABS related fault codes (overlapping codes which gave a more detailed picture of problem) on my 2008 Honda Accord: . I like the Innova products. .. I think the Innova 3130c is a good product at fair price. While it did not read the 2008 Honda Accord's OEM codes, it still pointed at the ABS problem, and likely would preform well on emission fault codes. Hard to know how it will do on other model cars. Studying Innova's support info an/ or the owner manuals for a specific Innova ScanTool model can give you info. on what what vehicles it can read (not OEM) on ABS codes. For ABS codes, there is a list in the manuals of which cars can be read for ABS codes.
By the way, (Tech Talk): .. I resolved my ABS malfunction by replacing the Reybestos hub/bearing units (made in China) with Timken (made in USA) hub/bearing units. I identified the problem on Reybestos's ABS encoder rings with an ABS encoder ring reader tool (ATE 760130 ABS Test Card on Amazon) plus comparing magnified digital pictures. This easy to repeat examine showed my problem. There were too many magnetic lines on the Reyabestos encoder ring as compared to old OEM bearing encoder ring, translating into approximately 4 extra ac millivolt pulses going to ABS computer. I was surprised as heck. Never thought I ever see something like that! I pre-checked the Timkens with this same easy to repeat examine and they matched up to the OEM bearings. ..Then installing that pair of Timken bearing/ hub units fully resolved my problem.