1. Has been coded and need to verify on Truck - Currently Updating TPC's in the field to 5.20
2. Have tried on a truck with local OEM but was not able to get unit in REGEN mode
3. Developed JBUS recording tool to assist with troubleshooting
4. Need Had conference call with Mike Auvil  ( See Goal #1)

Last Update: 6/15/2014

1. Identified approx. 1400 vehicles with potential issues relative to EODR
2. Need to troubleshoot, categorizing into buckets for review
3. Certain trucks will need software update, wiring inspection or wires connected (JBUS, Ignition)
4. Several initiatives focused on EODR data, need to get to the bottom of the issues
   1. Need to get 5.20 to these units (6/15 Updated 7471 to 5.20.02 or higher.)
5. Correlation reports to make sure inventory feed is working correctly
   1. Fetah has done majority of the work
   2. Does GetAll… call include inventory information, software version information
      1. XPe truck
      2. DTCore
   3. Currently software version not included, trying to get it in FW3.34
6. Suggested to Ken we wait running report until we have at least 2 weeks of history compiled
   1. Start date 4/28/2014, that’s when half of fleet was deployed.
   2. 6/15/2014 – ran a new report and now down to approx. 1000 trucks
7. Report to Ken who will check to see if we can correlate to oem/make/model

Last Update: 7/22/2014

1. Preparing 8 units for field trial with USX
2. End of April 2014
3. Field Trial: Schedule truck for mid may (After the week of May 12th)
4. Send fuel sensor specs to Ken on 04/30/2014 for review by Mike Auvil
5. Coordinating with USX to get a USX truck for install on 9, 10, 11 July 2014
6. System installed and unit is running as of 7/18/14
   1. The system appears to be functioning as desired

1. Changes have been implemented in FleetWatcher version 3.34
   
   1. Have not heard back from David Tomshack on changes made.
2. Closed this issue as of 11/17/2014 - We have not heard any complaints since we made the changes to FW 3.34

Last Update: 6/15/2014

1. Researched capability of Intel WiFi card used on REV6
2. Developed scripts/configuration to put WiFi card in AP mode (normally a client only)
3. Puts WiFi in AP mode for connection to 7” Android tablet
4. Conducted engineering calls with USX development team
5. Purchased Galaxy TAB3 tablet for testing
6. Tested several RDP clients (VNC like) to connect to REV6 via WiFi interface (AP)
7. Provided development platform and handed off to USX
8. Provided support to setup system at USX
9. Held review call with USX development team and discussed configurations and options for implementation
   1. USX prefers an implementation whereby the apps run on tablet and rely on services API (that runs on REV6) when needed
   2. Discussed connected vs disconnected state
10. Need discussion with Max for direction, perhaps connected for now
    1. Schedule meeting with Max on Friday (4/25/2014)
11. Currently project is stalled, waiting for direction

1. Have had discussion with USX Safety team
2. Reviewing new rules (just released by FMCSA)
3. Development targeted for 2H 2014 (after rule-making finished)

Latest Update: 4/15/2014

Received an email from Joey stating that Ken will probably want to discuss the linked article. 

Food Safety Rules...

Re: Proposed Rule §1.900

Last Update: 6/25/2014

1. Documented Ken Crane's interest in exposing the terminal information to web services
2. Will take 2-4 weeks to develop and implement new web service calls that USX is asking for.
   1. Update/set the driver terminal

   2. Update/set the driver settings group (i.e., HOS)

3. Needs to be scheduled per Ken Crane request made on 6/25.