• System usage: #define POWER_LOAD 155
• Application usage: #define APP_POWER_LOAD -1155
• Processed by: subsystem manager (_power)

Description:

Creates or alters a load. This is a permanent form of power drain tracked by the subsystem manager. Each load has three attributes: a source device, a name (any string, as long as it contains no spaces), and a value (specified as a floating-point number of Watts, or Joules per second.)

POWER_LOAD was designed with the expectation that most such messages would be sent by the device manager (triggered by the load light bus command) and as such, the frequently-sent DEVICE linked message will automatically purge power loads for devices that are no longer attached. To avoid this, specify the controller's UUID (obtainable from within user memory with llGetLinkKey(1)) as the device name; this is handled specially and will keep the load active until the controller is detached.

Parameter format:

The string parameter consists of three tokens separated by spaces:

• The load-device value may either be the connection address of a valid device (e.g. "battery", "HUD", "handle") currently registered with the device manager, or the current UUID of the controller's root prim. Upon receipt of notification that a device has been removed (or a device probe has been initiated), all matching power loads will be purged. When the controller's UUID changes (e.g. when attached), loads using the old UUID will be invalidated and removed (along with all other loads, as attaching the controller triggers a device probe). If a bogus device name is specified that is neither the name of a real device nor the controller's current UUID, it is susceptible to pre-emption whenever a device probe is initiated.
• The load-name value is a free text field; it may not contain spaces but otherwise has no restrictions. This is visible to users via the power status command. Load names may be re-used by different devices, but must be unique within each device. For example, ATOS/E uses loads named "cooling" and "repair", TESI uses loads named "metabolism" and "arousal", and auxiliary power uses a load named "auxiliary-recharge".
• The load-value is the actual wattage of the load. Power consumption is accounted once per second under SSM on a fixed timer, but SPCM (the ATOS/CX power manager) uses a continuous time quantum model where accounting occurs irregularly. A value of 0 deletes the power load entirely.

The key parameter is not used by this message.