Configuration

Please contact your controller supplier for specific instructions on how to configure your controller.  The following general guidelines apply when using Elevate Dispatch:

Controller behaviour requirements

To ensure the correct operation of Elevate Dispatch, the controller must accurately report the current floor, travel status, and door status. It also must respond to the dispatcher's commands as expected. Problems will occur if, for example:

1. The controller reports to the dispatcher that the lift is in service, but then moves independently without receiving a command.

2. The controller reports that the lift is in a state where it can move (e.g. doors closed), but fails to act on a command to move to a specified floor.

Parking functions

Parking functions are typically used in conventional control systems to reduce wait times at busy floors (e.g. the ground floor), by automatically returning idle elevators to designated ‘home’ floors. These are usually configured in the controller, often with timers or similar mechanisms.

When using Elevate Dispatch, these parking functions must be disabled, as they can interfere with the dispatcher’s operation.

If needed, Elevate Dispatch can manage parking logic. However, this offers limited benefit in a destination control environment, since—at least in theory—the system already has full visibility of all passenger demand. When the system is busy, this knowledge allows more efficient allocation without relying on fixed parking behaviour.

Load bypass

In conventional systems, load bypass prevents elevators from responding to landing calls when they are full.

When using Elevate Dispatch, load bypass functions must be disabled. This is because the system has already informed the passenger that a specific elevator will stop for them.

Again, with destination control, the system is aware (in theory) of all passengers and their destinations. As a result, situations where an elevator is instructed to stop despite being full are less common.