Raptor Telematics FAQ: Difference between revisions
Jump to navigation
Jump to search
(Created page with "==How do I adjust the report period for an existing vehicle?== Note: You must have 'Fleet Manager' or 'Admin' privileges for your company's account on the portal at telematics...") |
|||
| (7 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
==How do I adjust the report period for an existing vehicle?== | ==How do I adjust the report period for an existing vehicle?== | ||
Note: You must have 'Fleet Manager' or 'Admin' privileges for your company's account on the portal at telematics.neweagle.net in order to modify configurations. | '''Note:''' You must have 'Fleet Manager' or 'Admin' privileges for your company's account on the portal at telematics.neweagle.net in order to modify configurations. | ||
# Log in to [https://telematics.neweagle.net telematics.neweagle.net] | |||
# Locate the 'Vehicles' pane on the left-hand side of the dashboard, then click on the vehicle you'd like to modify. This will take you to the page for this vehicle or system. | |||
# Click the 'Configure <VehicleName>' link at the bottom. If this link doesn't exist, then this vehicle's configuration is set by a shared template. To edit the template, click the 'Edit <VehicleName>' link, this will take you to a page for editing details about this vehicle. Near the bottom of the page, it will tell you the template active for this vehicle. Click that link to edit the shared template. Editing the shared template will affect all vehicles linked to that template. | |||
# Enter the new 'reportPeriod' parameter value. | |||
# Click 'Save'. | |||
The configuration for this vehicle will be updated automatically over the air in the next few minutes. If you modified a shared template, all vehicles linked to that template will be updated. | |||
==My vehicle is showing an updating 'Last Update Check' time, but there are no data reports== | |||
The telematics control unit (TCU) must be configured with a DBC file in order for it to send data reports, which include GPS location, to the portal. Once configured with a DBC for data logging, the TCU will start sending reports once it sees some CAN messages that it is looking for. To troubleshoot: | |||
# Check that the TCU is powered up. | |||
# Make sure the TCU is connected on the proper CAN bus with the messages in the DBC file. | |||
# Confirm that there is a 120Ω CAN termination resistor in place on the CAN bus. | |||
# Verify that the CAN baud rate is the same. (250K, 500K, etc.) | |||
Latest revision as of 21:21, 21 February 2023
How do I adjust the report period for an existing vehicle?
Note: You must have 'Fleet Manager' or 'Admin' privileges for your company's account on the portal at telematics.neweagle.net in order to modify configurations.
- Log in to telematics.neweagle.net
- Locate the 'Vehicles' pane on the left-hand side of the dashboard, then click on the vehicle you'd like to modify. This will take you to the page for this vehicle or system.
- Click the 'Configure <VehicleName>' link at the bottom. If this link doesn't exist, then this vehicle's configuration is set by a shared template. To edit the template, click the 'Edit <VehicleName>' link, this will take you to a page for editing details about this vehicle. Near the bottom of the page, it will tell you the template active for this vehicle. Click that link to edit the shared template. Editing the shared template will affect all vehicles linked to that template.
- Enter the new 'reportPeriod' parameter value.
- Click 'Save'.
The configuration for this vehicle will be updated automatically over the air in the next few minutes. If you modified a shared template, all vehicles linked to that template will be updated.
My vehicle is showing an updating 'Last Update Check' time, but there are no data reports
The telematics control unit (TCU) must be configured with a DBC file in order for it to send data reports, which include GPS location, to the portal. Once configured with a DBC for data logging, the TCU will start sending reports once it sees some CAN messages that it is looking for. To troubleshoot:
- Check that the TCU is powered up.
- Make sure the TCU is connected on the proper CAN bus with the messages in the DBC file.
- Confirm that there is a 120Ω CAN termination resistor in place on the CAN bus.
- Verify that the CAN baud rate is the same. (250K, 500K, etc.)