Control-demon configuration

From Apez

1 Apez.control-demon device configuration

Apez.control-demon device configuration

Bellow you will find the detailed setup information for all current devices of the control-demon system. This information's is also included in the *boxed* version of the control-demon when you purchase it. See the change log for the version history.

To fit your building with this system, rez one of the controllers and set the controllers script to next owner – no transfer. The server will reset and confirm it's valid usage to you in chat. If you try to transfer the system without the permission change, the system will fail to work for your customer.

In the controllers ~ControllerConfig notecard you can set your own channel you want the system to communicate on. Default channel upon purchase is 911. You can change it to anything you like. But if you change it make sure you change the channel in the ~Config notecard of all other devices.

Since v1.4 authorised users are also stored in the ~ControllerConfig notecard.

This also allows you to create individual controllers such as a control that only open/close windows on one floor or a certain channel. Or a private door with keypad on it's own channel that only gives you access. There is many things you can do with this scripts and the included objects are only samples. The demon-controller stores a list of valid users. This list is communicated to all devices on the defined channel whenever it is required. All devices refer to the list of authorised users before accepting any commands. (eg. open door, light on, tint window etc).

In addition you can add User=All to you ~ControllerConfig. This wiöö allow any avatar to use the devices (public usage).
However, the demon-controller can only be used by those specifically named in the ~ControllerConfig.

Quick Setup (plug&play)

Rez the demon server or demon keypad in-world.
Right-click the device and select edit, in the build menu change to the "content tab".
Change the permission of the demon-controller script to next owner - no resell / give away.
The controller will reset and run a permission check and confirm his valid usage.
Open the ~ControllerConfig notecard and set the desired channel for the system. Default Channel of all devices =911 upon purchase.
Add at least 1 user to the ~ControllerConfig (User=Your Name). Only Avatars that have a "User=" entry will be able to operate the demon-controller.
Rez any device (or create one from the scripts) like a window, door, tp etc. Make sure you set the ~Config notecard of each device to the same channel as your controller (eq. =911).
Name your devices. The system reads "device names" from the device "description field". Right-click and select any device, give it a name in the descriptions field (for example Door 1)
When you placed some devices and named them, touch your controller and select "config" from the menu.
The controller will now register all devices, create their menus and they are operational.
That's it.. plug&play...

Inter-device communication

Controller communication channel:

This is specified by the builder and is stored on the notecard in each device. This allows any number of systems to be installed, in close proximity, without interfering with each other, simply by using different communications channels. Default Channel of all devices upon purchase =911.

Device communication channel:

All devices of this system communicate using COMMS_CHANNEL. If you're creating a building which will have multiple control-demon systems you should always use Odd channels for each system. For example: 910,912,914 The reason for this is, the internal system communication uses COMMS_CHANNEL +1. This means, if your system is using channel 911, it will be using 912 internally as well. There needs to be a gap of at least 2 between COMMS_CHANNELs.

The object description:

This allows the central control to communicate with groups of devices. (e.g. a set of double doors both named Door 1, or all the windows on a single floor, all called Window 1). Since control-demon v1.4 "any name" in the description field is supported for the devices. However, the name should be less than 10-12 characters, since the menu can't display longer names (SL limitation).

Device Configuration

Bellow you get a brief instruction on how to use the demon system.

While the control-demon system has been designed to be used in a plug&play style, there is many features for the advanced user and customisation of the control-demon and it's devices. You can discuss the demon usage, device configuration and feature suggestions on the apez.biz forum. If you have any questions regarding the system usage and features, please don't hesitate to contact ApezProducts Engineer or open a support ticket here.

Demon-Controller

The demon controller is the heart of your control system. The controller communicates with all devices on a low lag level using the mono script language. Via the controller you configure and control all the builds devices.

Removed in v1.3 --> Top Menu=Users*Windows*Doors*Lights*Blinds*TP Config.
Removed in v1.4 --> Users are now stored in ~ControllerConfig NC, ~Users NC has been removed.

To configure devices, simply touch the controller and select "config" from the menu. The controller will register all devices and create the relevant menu entries.

Demon-Doors

Since the release of v1.3 there is only 1 "demon-generic-door_x.x" script included in the package. This script is used for all door types now and the type is set in the ~DoorConfig notecard. Current door types are "Swinging,Moving,Squeeze". Moving and squeeze are 2 different types of sliding doors. The doors now also support texture change, changing tint level, open,close,lock,unlock sound.

By default, doors are closed, so once they are positioned, the first click will open them from this closed position and a further click will restore them to this original position. Once closed, if they are then moved again, they will continue working from this *new* position. Most swinging doors can be a problem when they keep resetting themselves. Demon doors are by default 'closed', so wherever you put them and whichever angle, they will continue to work from that point.

Since demon v1.4 the sliding door (moving) auto-detect's it's rotation.

Sample ~DoorConfig notecard:

// Device Channel (must be same as related controller)
Channel=911

// Door Type Swinging, Squeezy, Moving (See docu for details)
Door type=Swinging

// Allow tinting (or texture changing)
// No - door does not tint at all
// Restricted - only people specifically named on the user list.
// Yes - people on the user list, including 'All'
// If Restricted or Yes then touch the door for more than 3 seconds to tint/texture it
// simply click door to open/close it
Tinting=Restricted

//Textured door or tintable door? This is the initial state of the door.
Texture or tint=Texture

// This controls the level of tint in tinting windows
// You may have any number of values and each value should be from 0.0-1.0 (max tint)
Tint levels=0.2,0.4,0.6,0.8

// Texture levels, controls the textures to be used for the stages of a window opening
// You may have any number of values, but the texture must exist in the object's inventory
// They have been suffixed 1 and 2 to denote 2 sides of the door. Please note this may be on the inside
// or the outside depending on the door orientation and direction of door opening.
// Texture Remainder means the texture to be applied to the remaining sides
Texture levels1=door3
Texture levels2=door3
Texture Remainder=door3

// Time door remains open
Open time=15.0

// Door sounds, the sounds must be located in the doors content.
// "none" if you dont want to use any sounds.
Open sound=sound_door_sliding
Close sound=sound_door_sliding
Lock sound=none
Unlock sound=none

// Only need to set the section of options relavent to specific door type.

// MOVING DOOR
// Movement size for sliding door
movement=2.0

// SQUEEZY DOOR
// Movement size for sliding door
// This door acts as sliding door by changing the prims size
Open size=0.5
Closed size=4.2

// SWING DOOR
// Movement of door Clockwise/Anticlockwise
Open turn direction=Clockwise

Supported Door Types:

Sliding Door (Moving)
- This door should not be linked into the build, as it will be prevented from physically moving. This door is a normal prim, not cut or tampered with. See demo door included in the release version for details.

Sliding Door (Squeezy)
- This door can be linked into the build, provided it is not the root prim.

Swinging Door
- This door is a 50% path cut prim (0.375 and 0.875) which operates by rotating about its its central vertical axis. This door can be linked into the build, provided it is not the root prim.

Demon-Collision Detector Mat

The collision mat is non phantom and can be linked to your building.

Setting:

Linked door=Door 1

If it detects an authorised avatar stepping on it, it will send a message to open the linked door. (set in the note card options). This mat is designed to be flat and transparent, or possibly a step into a building. Something that an avatar would step on before reaching the door. Because it is not phantom, this mat can be linked into the build.

Demon-Collision Block

The collision block is a phantom device and hence, not linkable to your building!

Setting:

Linked door=Door 1

If it detects an authorised avatar passing through it, it will send a message to open the linked door. (set in the note card options). This block is designed to be large and transparent,of a size sufficient to surround the door and the region leading up to the door. Because it is phantom, this block can NOT be linked into the build.

Demon-Window

3 textures representing open, half open and closed states. The Textures can be added to each window individually,just drag the texture into the windows content,and it's done. You may also add 3 different textures to three different windows in the same group.

Since control-demon version 1.3 the windows support different texture change levels for inside/outside when operated. To assigj different textures all of them need to be present in the objects content and have to be configuted in the window notecard.

// Texture levels, controls the textures to be used for the stages of a window opening
// You may have any number of values, but the texture must exist in the objects inventory
Texture levels1=wooden window clear,Wooden window 50 dark,wooden window 100 dark
Texture levels2=wooden window clear,Wooden window 50 dark,wooden window 100 dark

Demon-Blinds

Like the sliding doors, the venetian blinds operate by a 50% path cut prim (0.375 and 0.875), contracting about a horizontal axis (x or y ).
Open and closed size represent the sizes for those 2 states.

Closed size is 5m maximum

By default, blinds are closed, so once they are positioned, the first click will open them from this closed position and a further click will restore them to this original position. Once closed, if they are then moved again, they will continue working from this *new* position.This blind can be linked into the build, provided it is not the root prim.

Demon-Teleporter

Rez the teleporters to their required positions,
Edit the object description to the location name
On the central controller select 'TP config'
That's it, ready to use...

TP config causes each of the teleporters on the same communication channel to broadcast their name and position to the controller on the same channel, and therefore each teleporter to receive that information from all other in the system. A maximum of 13 in each system is allowed. Mainly because there are only 12 buttons on a blue menu.

The demon-teleporter uses llRegionSay() since version 1.4. This allows sim wide teleporting and usage.

Demon-Security System

Easy config and installation
Protects your land without the need of red "ban lines".
Protect your entire land or just a single room
Works on avatar and group owned land
Get authorised users/visitors from demon-controller
Protect "cubic area" (most systems protect radial areas)
Ejects intruders from the land or teleport them home
Modify scan rate, x-y-z coordinates and more

Demon-Security System Instructions

Demon-Radio Player

Users managed by related demon-controller.
Allows access & control for friends or DJ's
Easy stream management through NC config
Show / Hide station name and more

The radio must be deeded on group owned land.
For this reason you should set the radio perms to next owner modify, no copy,transfer!

Demon-Light

Settings:

Glow red=0.0
Glow green=0.0
Glow blue=1.0
Glow intensity=1.0
Glow radius=10.0
Glow falloff=0.75

The above settings allow for the various glow parameters to be changed, for when the light is turned on. The light will turn on and off by clicking it or when you access it from the controller. The light can be linked into the build, provided it is not the root prim.

Demon-Mailbox

You can add this mailbox to you builds. Just set it next owner - no transfer to work. It will accept notecards from anyone and inform the owner if a NC is dropped on the mailbox.

Demon Fireplace

The fireplace is a animated and scripted fire. A demo fire and chimney are included in the system package. The fire can be hooked into the demon system and be controlled from authorised useds or the controller.

Retrieved from "http://wiki.apez.biz/Control-demon_configuration"