Release Notes for version 0.1.3 (Release Date: 10/6/2010)

• The API was updated to use the open source shared library libFTDI. Previous versions relied on the libftd2xx library available from FTDI, but that version has not been updated to reflect changes in the USB subsystem in the latest versions of the Linux kernel. You will need to have the libftdi.so in your /usr/lib directory. You can either download and install the the libftdi shared library using your Linux desktop software center, or download and build it from here:

        http://www.intra2net.com/en/developer/libftdi/download.php

• The API was developed and tested using Ubuntu 10.4.1, with Linux kernel version 2.6.32.24 - generic.
  
• neoVI Yellow firmware update is now working
  

• This release supports the following Intrepid devices:

  neoVI Fire (all hardware revisions)
  ValueCAN 3
  neoVI Yellow (hardware version 1.2 only)

Release Notes for version 0.1.2 (Release Date: 01/20/2010)

• This release supports the following Intrepid devices:

  neoVI Fire (all hardware revisions)
  ValueCAN 3
  neoVI Yellow (hardware version 1.2 only)
  

• neoVI Yellow firmware update will fail in this version. I still need to track down this bug. If you have a neoVI Yellow and can't connect to it, it's likely that it's firmware does not match the version required by this release. I have included a Windows application called neoVI3GExplorer.exe. Try running it on a Windows PC and connecting to the neoVI Yellow. neoVI3GExplorer will update the Yellow to the proper firmware version. In fact, I recommend  doing this with any supported neoVI device that you are having trouble connecting to. 
  
  ** Note - In order for neoVI3GExplorer to connect to a neoVI device on the Windows PC, you must have Intrepid's signed USB drivers installed. You can download the latest version from www.intrepidsupport.com. On that page look for the link "Drivers (auto install)" under the Product Drivers bullet.

Release Notes for version 0.1.1 (Release Date: 08/21/2009)

• This release adds support for updating the firmware on a neoVI Fire (board rev 1.1). neoVI Fire 1.2 support will be in the next release.
  

• CoreMini scripting functions have been added
  

• Documentation updated. Release and installation notes added to PDF documentation
  

• The CoreMiniScriptExample demonstrates how to load a script into the neoVI or ValueCAN3 and run it
  

• Firmed up the timing issues for connecting to devices and updating their firmware. I am still occasionally seeing firmware updates time-out half-way through the update. If this happens, try removing/replacing the USB cable from the device and power-cycling. 
  

Release Notes for version 0.1.0 (Release Date: 07/20/2009)

• The first release of this Linux shared library is for evaluation purposes only

• This initial release supports the ValueCAN3 and neoVI Fire (board rev 1.1) 

•  CoreMini scripting is not supported for the first release. This functionality will be included in a later release

• A neoVI device can only be opened by one application at a time.  A future version of the library will provide the ability to allow multiple applications to share a device

• The LinuxAPIHelp.pdf file outlines the supported API functions and their usage

• The icsnAPI.pdf file covers the Windows version of the icsneoAPI but is included because it contains more information regarding neoVI devices

• The ReadMe.txt file describes how to build an application to utilize the icsneoAPI

• This release of the icsneoAPI for Linux requires specific firmware to be present on the neoVI Fire. The ability to flash update the neoVI Fire from the shared library for Linux will not be supported until the next release of the API. The firmware versions :  MPIC = 1.84  UPIC = 1.2,  LPIC = 1.24  JPIC = 1.5

• If you are using a neoVI Fire and cannot open it, or you are not able to read/transmit message, contact me at the email address below. We may need to have you reflash your neoVI to a different version of firmware using a Windows PC. Please contact me at the email address below if this occurs

• Firmware updating for the ValueCAN3 is supported in this version and will happen on connect if the firmware in your device does not match that expected by the icsneoAPI. The GeneralTestProject demonstrates how to set callback functions to trap and display the output of a flash update to the user