Mode eDIN+ RTI Driver.

Driver Setup

This driver is to control a Mode eDIN+ lighting system. A Mode eDIN+ NPU is required and any combination of eDIN+ modules to allow for the control of your lighting system. The driver can handle 99 room or areas with up to 30 lighting scenes in each room. 1000 lighting channels in any combination of rooms. 99 wall plates and 99 auxiliary device inputs.

All the functions and variables in this driver a tagged for ID11. Each area, channel, wall plate and Aux Input is added to the RTI file as a separate device. Try to put the devices in the correct rooms in your design. Once you have built a nice user interface for one device. You can easily copy this to other devices and the tags will auto program if the page is set to the correct source.

Initial configuration of the driver:

Licence Key: This is a licence specific to the XP processor you are using. The driver will function for two hours from reboot without a licence to allow for testing and evaluation of the driver. Licences can be purchased from johnmarshav.com

IP Address: This is the IP address of the eDIN+ NPU on the local network. Ideally this IP address should be fixed in the NPU web interface. [Settings & Upgrades/TCP/IP properties].

Set the login credentials for the account that you have setup on the eDIN+ NPU. These can either be user or configurator credentials.

For the driver to be able to communicate with the NPU you need to do the following:

Enable gateway control under [Settings & Upgrades/Network Services].

Tick the box for ‘Enable gateway control’.

Set the port to the same as the port in the RTI driver configuration. Default 26. Only change this if you have problems.

Tick the box for ‘TCP Keepalive’ and set the idle time to 120.

Wall Plates:

To add a wall plate to your RTI file, go to ‘Add Workspace Item’ add a wall plate to the room or to the global area. In the Source Properties for the plate add the name. the driver does not use any addresses, ID numbers or device numbers, it finds the devices in the eDIN+ system by its name. The name you enter here must match exactly the name of the plate in the NPU. The match is exact so ‘Lounge Plate’ is not the same as ‘Lounge plate’ and will not be discovered by the driver.

To ensure that all the devices in the driver have been discovered correctly a diagnostics web server is provided. This webpage is accessible at http://<IP Address of XP>:1880

Mode manufactures a range of wall plates. All these plates have the same configuration regardless of the number of buttons on a plate. All plates have ten buttons. Some of the buttons may not be used on all plates but the location of the buttons is the same. See the separate document on button numbers.

All wall plate buttons have associated driver events. This allows you to add any commands or macros in RTI to any wall plate button, so a button on a wall plate could be used to turn off the AV in a room or close a garage door. Separate events are provided for ‘Button Pressed’ and ‘Button Hold’ events.

Mode wall plates have colour changing LEDs behind each button, these can be configured in the NPU to show scene states etc. a simple graphic has been included in the driver bundle to mimic these LED colours depending on the state of the real wall plate. Add the graphics file to your Sample Colour Bitmap Library.

If all you want to do in your RTI system is to simulate panels for your client to use, then you only need to add wall plates. If you want to give the user more control, then you will need to add areas or rooms and individual channels.

You can add wall plates to your RTI design even if they do not physically exist. This means you can use RTI wall panels as eDIN+ wall plates and simply program non-existent wall plates in the NPU.

Lighting Areas/Rooms:

The mode eDIN+ configuration uses areas and RTI uses room. This works well together. As far as we are concerned rooms and areas are the same thing.

You add areas to your RTI design using the ‘Add Workspace Item’. Up to 99 areas can be added. A Lighting Area can create a page on your controllers. Areas are only for creating pages and controlling scenes. If you want control of individual lighting channels, then these can be added later as separate devices.

It is important that you have setup all the rooms with the correct names in the NPU.

Area Name: This is the name of the room or area as shown in the NPU. It must be an exact match for case, spacing etc. Any name is allowable but obviously the more descriptive the the better. So, a room called ‘Lounge’ in RTI would ideally match with an area in the NPU called ‘Lounge’ rather than ‘Area 3’. You cannot have two rooms with the same name.

In the NUP you can now add scenes. Each scene should be given a name that describes it’s function like ‘100%’, ‘50%’, ‘Off’, ‘Movie’, ‘Relaxing’ etc. You now need to add these scenes to RTI. Enter the number of scenes you want to control in the area. Enter the scene names exactly as written in the NPU. Use the diagnostics server to check that everything matches.

Channels:

If you want to give your client full control of the lighting, you can add each individual lighting channel in the NPU as a new device in RTI. Add channels using the ‘Add Workspace Item’. Add the channels to the area in which they appear in the NPU. Adding the channel devices to the correct rooms will make life much easier going forward.

Because of the way the RTI driver API works, you need to add two names in the driver configuration for each channel device. First is the Area Name. This is the same as the name you gave to the Lighting Area that matches the area name in the NPU. The second name is the Channel Name. This must match exactly the name of the channel in the NPU. Finally, you need to select the type of channel. The driver is not concerned with the lighting protocol that is used to control the actual lights. It can be Dali, DMX, Dimming, 0-10 or relay. The driver just needs to know the name and type. There are three types to select from the dropdown menu. The Area Name, Channel Name and Channel Type must match the names and type in the NPU. Use the diagnostics server to test this. You cannot have two channels with the same name in the same area.

Auxiliary Inputs:

Many eDIN+ modules have auxiliary inputs that can be connected to buttons, switches, contacts, PIRs etc. Auxiliary Inputs are added to RTI using the ‘Add Workspace Item’. Enter the name of the auxiliary input exactly as written in the NPU. There are events for input pressed and held although some devices do not allow for held events.

Driver functions and variables:

All the functions in this driver are Tagged for RTI. You shouldn’t need to enter any driver commands directly in the Tag Editor if you follow the tag naming conventions described below and ensure that the page or layer you are working on is set to the correct device. Tags are shown as <Tag Name>. Some tags have numbers include to trigger different buttons. These are represented as <Tag Name n> where n is the number required. Example <Button n> where n is the button number on a wall plate. To trigger button one use the tag <Button 1> for button five use <Button 5>. Tags are case sensitive.

Wall Plate Functions:

<Button n> Button Pressed command for button n.

<Button n Hold> Button Held command for button n.

<Button n Release> Button Released for button n. This is used for dimming buttons

Wall Plate Variables:

<Button n> String variable of the button n name from NPU. The text will mirror the name in the NPU.

<Button Led n> Integer variable 0-16 to indicate the current colour state of a button Led. A simple graphic is included with this driver bundle to indicate the correct colours. The table below shows the enumeration if you want to build you own.

0 Black
1 White

2 Red

3 Green

4 Blue

5 Orange

6 Cyan

7 Magenta

8 Yellow

9 Dim White

10 Dim Red

11 Dim Green

12 Dim Blue

13 Dim Orange

14 Dim Cyan

15 Dim Magenta

16 Dim Yellow

Lighting Area Functions:

Scene Functions:

<Scene n> Recalls scene n in a room.

<Scene Off n> Turn off scene n.

<Scene Toggle n> Toggle a scene on or off.

<Scene Save n> Save the levels of the lights as they are set in a room into Scene n.

<Scene Level> Sets the level of the currently active scene in a room.

Scene Variables:

<Scene n> Boolean value to indicate if Scene n is running.

<Scene Level> Integer of the level of the currently active scene.

<Scene Name n> String of the scene name from the NPU

<Scene Name> String of the name of the currently active scene in the room.

Channel Functions:

<Light Level> Sets the level of lighting channel.

Channel Variables:

<Channel Level> Integer of the lighting channel level. Percentage.

<Channel Name> String of the channel name from NPU.

RGB and RGBW functions:

<Red Level> Sets the level of the red on channel on RGB and RGBW fittings.

<Green Level> Sets the level of the green on channel on RGB and RGBW fittings.

<Blue Level> Sets the level of the blue on channel on RGB and RGBW fittings.

There are 12 preset colours for RGB and RGBW channels. Use the tags bellow.

<Red> <Orange> <Yellow> <Lawn Green> <Green> <Mint> <Cyan> <Deep Sky Blue> <Blue> <Purple> <Magenta> <Deep Pink>

There are three user defined preset colours recalled using the following tags:

<User 1> <User 2> <User 3>

There are 10 sequences that can be recalled using:

<Sequence 1> Long Rainbow solid

<Sequence 2> Short Rainbow Solid

<Sequence 3> Hot Colours Solid

<Sequence 4> Cold Colours Solid

<Sequence 5> User Colours Solid

<Sequence 6> Long Rainbow Ripple

<Sequence 7> Short Rainbow Ripple

<Sequence 8> Hot Colours Ripple

<Sequence 9> Cold Colours Ripple

<Sequence 10> User Colours Ripple

RGB and RGBW Variables:

<Red Level> Integer of Red level of a channel.

<Green Level> Integer of Green level of a channel.

<Blue Level> Integer of Blue level of a channel.

Tuneable White Functions:

<Kelvin> Sets the colour temperature of tuneable white fitting in the range 1800K to 7000K. If this tag is linked to a slider, then you need to set the maximum and minimum values in the slider maximum and minimum values properties to 1800 and 7000.

There are 8 tuneable white preset temperatures.

<Candlelight> <Soft Warm> <Warm White> <Whitelight> <Cool White> <Bright White> <Daylight> <Blue Sky>

Tuneable White Variables:

<Kelvin> Integer 1800 -7000 of the kelvin temperature of channel n.

If using this Kelvin variable on a slider, then you need to set the minimum and maximum values to 1800 and 7000 respectively for the feedback on the slider to work properly.

eDIN+ NPU global variables:

<Project Name> Name of the project.

<Config Name> Name of the configuration.

<Project Version> Project Version

<Project Owner> Project Owner

<Connected State> Boolean, state of the connection to the NPU

Diagnostics Web Server:

The driver has a built-in web server. The address of the server is the IP address of the XP processor on port 1880.

http://<IP Address>:1880

The port setting of 1880 can be changed in the driver configuration if it clashes with other drivers in your system.

The server shows if you have any mismatches between the RTI driver configuration and the Mode eDIN+ NPU configuration. If there is a mismatch, a red message will appear on the top of the page. You will need to resolve any mismatches for the driver to function correctly.

The webpage displays all the elements of your RTI design and will highlight in red anything that it thinks doesn’t match. The driver checks area names, wall plate names, channel names and if the channel in in the correct area and checks the channel types and auxiliary input names.

A button at the top of the page allows you to rescan the eDIN+ system and test the matches again. Remember to upload your RTI project to the XP, if you have made any changes to the RTI side.

Change Log:

v1.01 10/11/25

Added login credentials for users and configurators. Various bug fixes.

V1.02 27/11/25

Added error correction so that the diagnostics webpage works, even if there is no communications to the NPU. Diagnostics webpage now displays an error message explaining what the problems might be.