Remote Row Edit: Remote Schedule tab
- Last UpdatedApr 24, 2025
- 4 minute read
Use the Remote Schedule tab in the remote Row Edit dialog box to schedule various requests for data from remotes.
Caution: In many locations, requests specified to run between 02:00 AM and 03:00 AM on the second Sunday in March do not execute, and requests specified to run between 01:00 AM and 02:00 AM on the first Sunday in November execute twice. These are the dates when many locations change from Standard Time to Daylight Savings Time (DST), and vice versa. This is due to time comparisons being based on local time.
The remote scheduler ensures that (a) the required remotes are connected, (b) all requests are processed efficiently, and (c) the highest priority requests are processed first. This includes:
-
Scheduling non-critical, low-frequency data requests (for example, where a connection to a dedicated line is not cost-effective, and polling using dial-up modems is preferred).
-
Scheduling periodic commands (for example, time sync or AGA upload).
The remote scheduler process maps schedule entries in the remote table to commands that are issued to remotes at certain times. Any Controller-initiated command that does not take a parameter can be sent through the remote scheduler. Such commands include polling, but exclude commands such as setting setpoints and issuing digital commands.
Note: Remote scheduled commands can be set to low, polling, medium, or high priority. Controller commands are set to a priority above high to ensure they will execute before a remote scheduled command, and so they can interrupt currently running scheduled commands. For connections that use Host Poll mode, polling is normally done at a priority below low so that remote scheduled and Controller commands take precedence. However, polls may be interleaved into low and medium priority remote scheduled commands to enable fastscan polling after a Controller command has interrupted a long-running lower-priority scheduled command; for example, a gas history data upload.
The remote scheduler goes through the entire remote table scanning the schedule entries. Requests are processed in descending order of priority. Those destined for remotes on permanent connections are sent to the Omnicomm process for that line. The command is issued for temporarily connected remotes. If the temporary connection used is a dial connection, it attempts to secure a modem or post a reservation against the modem bank. If neither a modem nor a reservation is available, the remote scheduler reschedules the request for the next round. If there is an available modem, the connection with the oldest, highest priority request is connected through this modem.
Refer to the table below for field descriptions and instructions on how to configure the editable fields.
|
Item |
Description |
|---|---|
|
Request |
Select the request type. Up to 15 requests can be setup for each remote. Open Platform Communications (OPC):
|
|
Priority |
Select the scheduled event’s priority. The choices are:
|
|
Command |
Select (...) and enter a protocol-specific command string in the Schedule Command Edit Form. This field is generally not used, except with some protocol drivers that allow you to pass them command-specific parameters. |
|
Schedule |
Select (...) to open the Remote Schedule dialog box and configure scheduling for the remote. Refer to Configure a remote scheduled event for more information. |
|
Enable nth Week |
To run the command on a specific weekday:
|
|
nth Week |
Select the desired week of the month. When the remote_sched process locates a request scheduled with a weekday, it:
|