| Electronic Logging Device | GeoSpace Labs Trux ELD |
| Model Number | TRUX100 |
| ELD ID Number | FF55EE |
| Software Version | v 5.5.0.0 and Higher |
Model Information
| Data Transfer Methods | TRUX ELDr supports wireless Web services and email (Option 1) for its compliant data transfer mechanism. For a driver to transmit this information to an authorized safety official they will: 1. Tap the tools button in the upper right corner of the mobile ELD device. 2. Tap the send logs button in the lower right of the popup. 3. NOTE: Driver may check the 'copy me on this email' option to also receive a copy of the log transfer |
| Malfunction Notes | 1. Check that Bluetooth is enabled on the phone and that the modem device is available for pairing 2. Inspect the physical model for its error state. There are 2 primary states 3. A rapidly blinking light indicates that the modem was unable to pair with the mobile device 4. A steady dull light means the modem was entered an error state and is not attempting to pair with any device 5. In either scenario hold the small button on the bottom left of the modem device front panel for 5 seconds to reset the device and to clear its error state ERROR CODES The primary default code is the inability of the mobile device to connect to the engine modem. This is indicated by the red bar along the top of the device. For troubleshooting instructions see above section “Setting Up The Plug In” FMCSA Error Codes Malfunction/Diagnostic Code Description P “Power compliance” malfunction E “Engine synchronization compliance” malfunction T “Timing compliance” malfunction L “Positioning compliance” malfunction R “Data recording compliance” malfunction S “Data transfer compliance” malfunction O “Other” ELD detected malfunction AKAL Equivalent Codes Code Description Shown on Mobile Device P “The plug in device is not powered on.” E “The plug in device is not able to synchronize” T “The plug in timing is not working correctly” L “System is not able to determine positioning” R “System is not able to record data” S “System is not able to transfer data” O “An unidentified error has occurred” Malfunction/Diagnostic Code Data Diagnostic Event 1 “Power data diagnostic” event 2 “Engine synchronization data diagnostic” event 3 “Missing required data elements data diagnostic” event 4 “Data transfer data diagnostic” event 5 “Unidentified driving records data diagnostic” event 6 “Other” ELD identified diagnostic event AKAL Equivalent Codes Code Process Run, Description 1 “AKAL will attempt to reset the plug in” 2 “AKAL will attempt to reset the plug in” 3 “You are missing data xxx from the ELD logs” 4 “Attempting to reconnect..” 5 “Unidentified driving records found” 6 “A general system diagnostic is in process..” |
| Certifying Statement | The FMCSA ELD Requirements document and usage case scenario document were followed step by step to validate each function in the requirements with our ELD device. Several updates to the software were made and the testing procedure was repeated until all scenarios passed. Software version 2.0 contains the code base tested against the FMCA requirements. |
Company Information
| Manufacturer | GeoSpace Labs |
| Website | https://www.geospacelabs.com |
| Contact Email | [email protected] |
| Contact Phone Number | 877.4.GEOWIZ |
| Address | 4460 Florida National Driv,, Lakeland, FL 33813 |
Devices From GeoSpace Labs
| Device | ID |
|---|---|
| GeoSpace Labs Trux ELD | FF55EE |
| GeoSpace Labs Geowiz ELD | FF44EE |
| GeoSpace Labs AKAL ELD | FF66EE |
Related ELDs
| ELD | ELD ID |
|---|---|
| Navistar, Inc. OnCommand(R) Connection Electronic Driver Log | OCC001 |
| HCSS HCSSELD | GEO84A |
| GPS Trackit ELD Fleet | ELDFLT |
| AAMP Global (Formerly M2M In Motion) M2MIM ELD | M2M018 |
| GPS Trackit ELD Fleet | ELDFLT |
| InTouch InTouch ELD - Android | ITELD1 |
| Satinder Singh Keep Truckin | KTIELD |