Sending Text, TTS and Remote Settings to Fleet Vehicles from CMSV6
Fleet Platform Guide
A fleet platform can reach vehicles without a phone call: it can send a text message that the device reads out or shows, and it can change device settings from the office. In AlwayCare CMSV6 these functions are in the monitoring tree menu and in the rule section. This guide covers manual and timed messages, information publishing, the history report and remote parameter and upgrade tasks.
What you can send and change
| Function | What it does | Where |
|---|---|---|
| Manual text message | Sends a message to one or more online vehicles, read out by TTS or shown on a screen | Right-click a vehicle in the monitoring tree |
| Timed TTS rule | Sends a message on a schedule, once or on a cycle | Rules, timer tasks |
| Information publishing rule | Sends road conditions, weather, notices and credit results on a schedule | Rules, timer tasks |
| Delivery history | Shows what was sent, by whom and whether it succeeded | Reports, data query |
| Remote parameters | Changes common device settings, for one vehicle or a batch | Real-time monitoring |
| Remote upgrade | Sends an upgrade file to devices | Real-time monitoring |
Send a message by hand
- Select one or more vehicles in the monitoring tree and right-click.
- Choose Send Messages, write the text and tick the message type, such as TTS reading or terminal display.
- Click Send.
- Several vehicles can be selected at once.
- Fixed messages can be added by hand, and the text you send can be saved automatically as a fixed message for reuse.
- Only online devices receive messages.
- Devices on different protocol versions, such as 808-2011 and 808-2019, cannot be handled in one batch. Send to them in separate batches.
There are two entries. Send Messages supports saved common messages and suits private-protocol devices. Text Message Delivery, under the 808 function menu, suits standard-protocol devices and does not keep common messages. The flag and text type options differ between 2011 and 2019 devices. See How to send text information to TTS and the difference between the two text entries.
Send on a schedule
| Setting | Options |
|---|---|
| Rule name | Your own name |
| Enable date range | Optional. Tick to set the dates the rule is active |
| Time range | The period each day when the rule is active |
| Send mode | Cycle: send every set interval during the time range. Single: send once |
| Message flag | Urgent, terminal display, terminal TTS reading or advertising screen. Pick one or all |
| Content | The text to send |
| Interval | Time between two sends. Shown for cycle mode only |
| Match all vehicles | No: only vehicles assigned to the rule. Yes: all vehicles of the company |
| Global share | No: only your company sees it. Yes: all companies on the platform see it |
Typical uses are a shift-start reminder, a fixed safety message on a long route or a notice to a group of vehicles. Keep wording short and consistent. See Timed TTS Rules.
Information publishing rules
Publishing rules send a type of information to vehicle terminals on a schedule or a trigger. Choose an information type: custom text, road conditions, weather forecast, emergency or public welfare notice, where you enter the content, or enterprise credit information and driver credit information, which the platform fills from the latest evaluation result. If no result exists, nothing is sent. The function also resends or reminds when a message fails to publish. See Customized Information Publishing.
Keep a record of what was sent
The Distributed Information Details report lists what the platform sent. You can query by vehicle, by user account, by time range, by type and by status.
| Type | What it records |
|---|---|
| Automatic | Voice messages the system sent by rule, such as speeding, fatigue, fence or alarm linkage messages |
| Manual | Text messages written and sent by platform users, including manual alarm handling messages |
| From the superior platform | Text instructions sent down by a superior platform through the JT/T 809 protocol |
Filter by successful or failed to find messages that did not arrive. See TTS Issued Information Details Query.
Change device settings from the office
- Common parameters. Right-click a vehicle and open the common parameter setting for a short list of frequent settings. See Set common parameters of the device remotely.
- Batch parameters. Open the parameter configuration, change the values, choose Save to other vehicles and tick the online vehicles. See Remote batch set device parameters.
- Remote upgrade. Right-click a vehicle and choose remote upgrade. Upload the upgrade file, set the version number and name, and save. Use Save to other terminals to send to several devices. An online device upgrades at once, and an offline device upgrades when it next comes online. A saved task that has not been sent yet can be deleted. See Remote device upgrade.
Test a parameter change or an upgrade on one vehicle first. A wrong value or file sent to the whole fleet is hard to undo quickly.
Good practice
- Agree a short list of standard messages with safety and operations staff, and save them as fixed messages.
- Prefer a voice message while the vehicle is moving. A driver should not read text on a screen while driving.
- Use timed rules for routine reminders and keep manual messages for real events.
- Check the delivery history after a campaign for failed sends.
- For upgrades and parameter changes, pilot on one vehicle, then a small group, then the fleet.
For the alarms that trigger voice messages, read our guide to alarm rules and alarm handling in CMSV6. For connecting devices to a platform, read Integrating AI Dashcams with Your Existing Telematics Platform.
Limits to plan for
- Only online devices receive messages, and what a device does with a message depends on its model and protocol.
- Devices on different protocol versions need separate batches.
- A message is delivered to the device. The platform report shows success or failure of the send, not that the driver acted on it.
- Sound and text in a vehicle are subject to local rules. Agree a policy and tell drivers.
Questions fleets ask about sending messages to vehicles
How do I send a text message to a vehicle in CMSV6?
Right-click the vehicle in the monitoring tree, choose Send Messages, write the text, tick the message type and send.
Can I send to several vehicles at once?
Yes, select several vehicles. Devices on different protocol versions, such as 808-2011 and 808-2019, must be sent in separate batches.
Can the platform send a message every morning?
Yes. Use a timed TTS rule with a time range and cycle mode, or single mode for one send.
How do I check whether a message was delivered?
Open the Distributed Information Details report and filter by vehicle, user, time and status. It shows success or failure for each send.
Can I upgrade devices remotely?
Yes. Upload the upgrade file and send the task to one or several devices. Online devices upgrade at once, and offline devices when they come online.
Do I need a special device for TTS messages?
The device must support the message type you send. Confirm TTS or display support with the device supplier.
Summary
- Send manual messages from the monitoring tree, and scheduled ones with timer rules.
- Publishing rules cover road, weather and notice messages.
- The delivery report shows what was sent and whether it succeeded.
- Pilot remote parameter and upgrade tasks before a fleet-wide send.
Read the source documentation at docs.alwaycare.com, or send an inquiry for a platform demonstration.
For fleet management, tracking and video platform options in one place, see the fleet management solution.
