Danlaw

A Danlaw Device is an OBD-II dongle that reports high precision vehicle data. The Danlaw package gives the ability to capture and report on the information received by one or multiple Danlaw device(s) via TCP connections.

The Danlaw package is intended to be used as a Proxy. Allowing users to connect remote devices that do not support communicating directly with the Portal. The Hosted Proxy can be deployed in a data center or can be co-resident with the IoT Portal Service. 

Danlaw Overview

• Allows for the use of Triggers and Methods to send Danlaw device data. 
• Supports a number of asset types and client engagements.
• Guarantees a 0% loss of data between the Danlaw device and an Asset Gateway.

Danlaw data exchange overview

Once the Danlaw package is installed and the Danlaw Server is configured and started, Danlaw devices can communicate with the Danlaw Server. The data exchange between the two partners is as follows:

• Each time a Danlaw device connects, the Danlaw Server will communicate with the Danlaw device and save the conversation with the device to disk. 
• Once the device has no more data to send, and disconnects, the Danlaw Server will attempt to send its gathered data to a configured Danlaw Event trigger.
• The Danlaw Event trigger will be passed a Danlaw Event Handle that holds the data retrieved from the device until the trigger completes.
  • The Danlaw Event can create a JSON from the data received, and send the Danlaw Event Handle to the Danlaw Routing Action for processing. 
  • Every time the Danlaw Routing Action is called, a record from the Danlaw Event Handle is picked up, and a route is determined for the type of record that was retrieved. 
  • This retrieved record can either be skipped, by calling the Danlaw Routing Action again, or routed off to one of the Danlaw actions to be decoded: Danlaw ASCII, Danlaw Trip Data or Danlaw Trip Event.