(SDK) CarChip SDK

The CarChip SDK is a development toolkit used by developers to interface with the CarChip device. All the SDK functions are encapsulated in the CarChipSDK.dll and can be accessed through the use of the header files "Structures.h" and "SDK.h" for C developers. The SDK kit acts as a high level tool and makes it much easier for developers to interface with a CarChip device.

Version History

What's new in version 3.2.5

  1. Added GPS support
  2. Fixed maximum speed calculation when bridging trips
  3. Enhanced GUI example application
  4. Built with VisualStudio 2005, unmanaged
  5. Linked with new CC_DavisHid.lib version 1.0.1.4 that fixes an occasional memory leak

What's new in version 1.0.6

  1. CarChip.DLL version 1.7
  2. DavisHid.DLL version 1.0.0.4 - USB Driver (Support for communicating with USB/CAN CarChips)
  3. Handles the ReadinessCode introduced with firmware version 2.20
  4. Added GetLastErrorCodeStringLength() function that helps to allocate the correct buffer size needed by the calling routine for further processing
  5. Added GetSDKVersionComment(...) to obtain detailed information about the current version

What's new in version 1.0.4

  1. CarChip.DLL version 1.6.0.3
  2. DavisHid.DLL version 1.0.0.4 - USB Driver (Support for communicating with USB CarChip's)
  3. Changed function names from "EnableAlarm" and "IsAlarmEnabled" to "EnableBeep" and "IsBeepEnabled"
  4. Fixed crash that can occur if a bad/or corrupt time is retrieved on the CarChip
  5. Enhanced Accident log sorting routine. Fixed duplicate accident record problem
  6. Fixed memory crash after download
  7. Enhanced the robustness of the SDK. Properly handles memory corruption problems that can happen in the CarChip
  8. Avoid possible data corruption during download transfers. The DLL will re-download a page in memory if it finds any corruptions within that page
  9. Fixed ClearAccidentLogs() bug

Platform: Windows 95, 98, ME, NT, 2000, XP

Version: 3.2.5

 File Size: 1.0MB

Released: February 19, 2008


How well did this answer your question?


Powered by HelpDocs