Blog

Doran has been in contact with USX and will be presenting a demonstration to them in May 2015. The following notes were created by Fetah for the express purpose of making sure our software still works with the Doran hardware. This information was passed on to Doran and Mike will be available for a support resource when this demonstration takes place. 

• Please set up the new hardware provided by Doran and verify that the system is still functional.
  • System still works with couple considerations:
    1. DT TPMS System was designed (image & tire locations) to work with Doran's 360SL model (more traditional tractor-trailer(s)). Doran sent us their 360HD model, which still works but the tire locations are different. We can tell which system is connected, so it would be possible to detect when the 360HD is connected and adjust the tire positions to match it (some Development work). But, Mike has reached out to Doran regarding this and to ask which system USX might employ, the response was the 360SL.
    2. Although the original DT TPMS software built on .NET 2.0 still works on the newest device software, we will re-compile/build for .NET 3.5
    3. We will also update the copyright and version just to identify the tiny change.
    4. Currently TPMS is not part of the "core" image, so it will require a creation of a new TMPS patch that would be deployed to the desired units.
    5. TPMS would need to be added to the DT Menu as an item for the desired units (via it's own isolated Vehicle Settings group), and potentially TPMS would be setup to auto launch on start up. This would start it out launched in the background with the TPMS tire icon showing on the menu bar for easy access and visual cue for any TPMS related events (Trailer Hook/Drop, Low Pressure, etc.)
• Test with a REV 6 unit and verify where the data goes and how it is stored and accessed.
  • System was tested and it works on a REV 6, after making sure the correct COM port is specified in the TPMS config file.
  • TPMS Data, what/where/when/how:
    1. There are 2 kinds of TPMS related/generated data that is sent and stored:
       1. Real time events - Trailer Hook/Drop, Pressure Low 1/2, Fast Leak, etc.
       2. Historic rollup data - average pressures, average temps, count of events, etc.
    2. Real time events prompt the driver or give the driver a visual cue, and these events are sent up immediatelyHistoric rollup data is collected and rolled up through out the 24hr day and sent at the end of the 24hr day, going into to its own designated backend DB table, with such data as average tire pressures, avg tire temperatures, # of events, etc.
       1. Tire events such as Low Pressures and Leaks go into their own backend DB table, specifying: (tire location, pressure, temperature, lat/lon location, datetime, user, tractor, trailer, etc.). These events can also cause an alert email to be generated and sent out to selected recipients (Modified and managed in FW)
       2. Trailer Hook/Drop events go into their own backend DB table separate from the tire events, specifying their own known info.
    3. Currently all TPMS related collected and stored data, is NOT accessible via FW or DT WS API. Data is only accessible via the backend customer account DB (accessible to DT team)
• Make note of anything we should know before Doran goes to USX for a demonstration. 
  • See items above
• Document customer setup requirements to activate TPMS system
  • See items above