This document contains "SmartDocs" capabilities. This will allow you to easily see only the content that is relevant to the Zebra device you are working with.
MX Features will be available on a device based on a combination of factors:
After identifying the version information for your device, simply select them in the SmartDocs bar. Any section that does not apply to your device will be greyed out. You can clear all settings by hitting the SmartDocs button. Clicking the back and next buttons on the SmartDocs bar will navigate to the sections that are relevant to your device.
The Clock Manager allows the setting of Date, Time, and Time Zone or to configure the device to automatically acquire it via NTP.
Zebra Android devices contain Clock functionality that tracks the current Date and Time on the device, in Coordinated Universal Time (UTC), and that can calculate the current Date and Time, in Local Time Coordinates (LTC), for a device's configured location. UTC is effectively the same as the LTC at the Prime Meridian in Greenwich, England. LTC is computed from UTC by using an offset determined based on a configured Time Zone that us suitable for the location where the device is being used and any Daylight Saving Time offset that is required for that Time Zone.
To avoid complications related to LTC, all Date and Time values used by the Clock must be represented as UTC. Using UTC reduces complexity and ensures a deterministic result when setting the Date and Time, regardless of the configured Time Zone or any Daylight Saving Time offset that might apply. For example, if the Date and Time were set in LTC, then the order of setting Date, Time, and Time Zone could affect the actual results. Also, if LTC were used, then certain combinations would become invalid such as the times "skipped" during adjustment for Daylight Saving Time.
This parm allows you to control whether the Date and Time on the device should be set automatically or manually.
When AutoTime is turned On, the time will be acquired automatically, if possible. For devices operating on a Cellular network, AutoTime will typically cause the Date and Time to be from the carrier network and set on the device. For other devices, AutoTime will cause a specified NTP server to be automatically contacted on a specified interval and the Date and Time of the device to be set based on the UTC received from that server.
When AutoTime is turned Off, the Date, Time, and Time Zone can be set explicitly and will count forward unless/until explicitly changed again.
Parm Name: AutoTime
| Option | Name | Description | Requires |
|---|---|---|---|
| false | false | This value (or the absence of this parm from the XML) will turn AutoTime Off, thus preventing the automatic contacting of an NTP Server and automatic setting of the Date and Time of the device. |
OSX: 1.3+ MX: 4.2+ |
| true | true | This value will turn AutoTime On, thus enabling the automatic contacting of an NTP Server and automatic setting of the Date and Time of the device. |
OSX: 1.3+ MX: 4.2+ |
This parm allows you to specify the URL of the NTP server that will be contacted periodically to acquire the Date and Time and set them on the device. Specifying an empty (length of zero) value (or the absence of this parm from the XML) will cause a default NTP server to be used.
Note: For devices operating on Cellular networks, the Date and Time may be obtained directly from the carrier network and may not require contacting an NTP server. On such devices, the Time Zone may also be automatically acquired from the carrier network and set onto the device.
Shown if: AutoTime is "true"
Parm Name: NTPServer
Requires:
- MX: 4.2+
- Android API Level: 19+
This parm allows you to specify the interval at which an NTP server will automatically be contacted to acquire the Date and Time to set on the device.
Shown if: AutoTime is "true"
Parm Name: SyncInterval
| Option | Name | Description | Requires |
|---|---|---|---|
| 00:30:00 | 30 minutes | This value will cause the device to attempt to contact the NTP server every 30 minutes. |
MX: 4.2+ Android API Level: 16+ |
| 00:60:00 | 60 minutes | This value will cause the device to attempt to contact the NTP server every 60 minutes. |
MX: 4.2+ Android API Level: 16+ |
| 06:00:00 | 6 hours | This value will cause the device to attempt to contact the NTP server every 6 hours. |
MX: 4.2+ Android API Level: 16+ |
| 86400 | 24 hours | This value will cause the device to attempt to contact the NTP server every 24 hours. |
MX: 4.2+ Android API Level: 16+ |
This parm allows you to set the TimeZone that will be used to calculate LTC on the device. Specifying an empty (length of zero) value (or the absence of this parm from the XML) will cause a the TimeZone currently in use on the device to be unchanged.
Parm value input rules:
Shown if: AutoTime is "false"
Parm Name: TimeZone
Requires:
- MX: 4.1+
- Android API Level: 1+
This parm allows you to set the Date on the device. The Date must be specified in UTC and not in LTC. This means that the Date specified in UTC might be the same as the Date in LTC or might be one day earlier or later, depending on any offsets applied due to Time Zone and/or Daylight Saving Time. Specifying an empty (length of zero) value (or the absence of this parm from the XML) will cause the current Date on the device to be left unchanged.
Parm value input rules:
Shown if: AutoTime is "false"
Parm Name: Date
Requires:
- MX: 4.1+
- Android API Level: 8+
This parm allows you to set the Time on the device. The Time must be specified in UTC and not in LTC. Specifying an empty (length of zero) value (or the absence of this parm from the XML) will cause the current Time on the device to be left unchanged.
Parm value input rules:
Shown if: AutoTime is "false"
Parm Name: Time
Requires:
- MX: 4.1+
- Android API Level: 8+
We want to set local time of the device as follows:
We can then make the following observations:
The values specified to the Clock would therefore be:
The above UTC values would be converted to the desired LTC by:
We want to set the local time of the device as follows:
We can then make the following observations:
The values specified to the Clock would therefore be:
The above UTC values would be converted to the desired LTC by:
<wap-provisioningdoc>
<characteristic type="Clock" version="4.2" >
<parm name="AutoTime" value="false"/>
<parm name="TimeZone" value="GMT-5"/>
<parm name="Date" value="2015-07-09"/>
<parm name="Time" value="10:25:33"/>
</characteristic>
</wap-provisioningdoc>
<wap-provisioningdoc>
<characteristic type="Clock" version="4.2" >
<parm name="AutoTime" value="true"/>
<characteristic type="AutoTimeDetails">
<parm name="SyncInterval" value="00:30:00"/>
</characteristic>
</characteristic>
</wap-provisioningdoc>
<wap-provisioningdoc>
<characteristic type="Clock" version="4.2" >
<parm name="AutoTime" value="true"/>
<characteristic type="AutoTimeDetails">
<parm name="NTPServer" value="1.2.3.4"/>
<parm name="SyncInterval" value="00:30:00"/>
</characteristic>
</characteristic>
</wap-provisioningdoc>