Lantick (all versions)

Overview

Purpose of the device

Lantick modules are general-purpose electrical circuit control devices. The Lantick Pro combines the function of output (relays or High-Side Power Switch) control with support of digital inputs (potential-free and voltage). Additionally the inputs may operate in the pulse count mode, which further enhances their capabilities.

Thanks to LAN communication, the Lantick allows for remote control and device condition monitoring. Different Lantick models offer various input and output configurations, with their numbers incorporated into model numbers making selection for specific needs easier.

Changelog

1.0 11th of March 2025

• Firmware revision v4.24

Device construction

Lantick PE-0-1

Technical characteristics

Dimensions

General view

Signaling

Input

Binary input schematics are shown on the image below.

Lantick PE-1-0

Technical characteristics

Dimensions

General view

Signaling

Lantick PE-1-1

Technical characteristics

Dimensions

General view

Signaling

The module is equipped with a display that informs the user about the input and output state:

• When an output is inactive, the display shows the o symbol, when it is active – 0,
• Similarly an inactive input channel is signalled by the i symbol, when it is active – I.

Thanks to this system, easy channel state readout is possible.

Input

Binary input schematics are shown on the image below.

LanTick PE-2-2

Technical characteristics

Dimensions

General view

Signaling

Inputs

Binary input schematics are shown on the image below. The upper schematic applies to the opto-coupled input. The lower schematic applies to the NO input. The input type is determined during device manufacturing. It's possible to assign different configurations to both inputs.

Module connectors

Upper section

Lower section

Lantick PE-0-4

Technical characteristics

Dimensions

General view

Signaling

Inputs

Binary input schematics are shown on the image below. The upper schematic applies to the opto-coupled input. The lower schematic applies to the NO input.

The input type is determined during device manufacturing. It's possible to assign different configurations to both inputs.

Module connectors

Upper section

Lower section

LanTick PE-4-4

Technical characteristics

It is possible to select the power supply method:

• 10-24V DC power supply connected to the screw terminal (Pwr switch up),
• LAN Passive PoE using the blue and brown pairs (Pwr switch down).

Dimensions

General view:

Signaling

Outputs

The relay output sections are shown on the image below. The COM contact is common for all 4 relays.

Inputs

Binary input schematics are shown on the image below.

The input sections are shown on the image below. The COM contact is common for all 4 inputs.

Module connectors

Upper section

Lower section

Lantick PE-0-8

Technical characteristics

It is possible to select the power supply method:

• 10-24V DC power supply connected to the screw terminal (Pwr switch up),
• LAN Passive PoE using the blue and brown pairs (Pwr switch down).

Dimensions

General view:

Signaling

Inputs

Binary input schematics are shown on the image below.

The input sections are shown on the image below. A COM contact is common for each group of 4 inputs.

Module connectors

Upper section

Lower section

Lantick PE-8-0

Technical characteristics

It is possible to select the power supply method:

• 10-24V DC power supply connected to the screw terminal (Pwr switch up),
• LAN Passive PoE using the blue and brown pairs (Pwr switch down).

Dimensions

General view:

Signaling

Outputs

The relay output sections 1-4 and 5-8 are shown on the image below. The COM contact is common for each group of 4 relays.

Module connectors

Upper section

Lower section

Lantick PE-0-16

Dimensions

General view

Signaling

Inputs

Binary input schematics are shown on the image below.

Module connectors

Upper section

Lower section

Lantick PE-16-0

Dimensions

General view

Signaling

Module connectors

Upper section

Output connection examples:

Network configuration

Changing the device's IP address - Discoverer programme

After running the Discoverer programme and searching for the appropriate device:
1. Right-click the device
2. Click the Change button.

After the dialogue window is opened you can:

• Set the IP address, mask, gateway, DNS1/DNS2.
• Change the Host name.

If Remote Config is enabled (enabled by default), the device needs to be configured by changing the computer's subnet:

To enable remote configuration:
1. Go to the Administration → Services tab.
2. Select Enable Remote Network Config.

Changing the computer's subnet address for configuration

During configuration without Discoverer programme, it's needed to change the subnet address of the computer on the same network.

To access the computer's network configuration, do one of the following:

• Press Win + R, type in ncpa.cpl, and then press Enter.
• Alternatively, go to:
  Start → Control Panel → Network and Internet → Network and sharing center → Change adapter settings.

Then:
1. Select the network connection.
2. Right-click it and select Properties.
3. After selecting this option, network connection configuration screen will appear.

Select Internet protocol version 4 (TCP/IPv4) and type in the following parameters:

In the Network tab, LAN parameters can be changed.

The following fields are used for network configuration:

• Host Name – NetBios name.
• DHCP – Enable the DHCP client; selecting this option forces the use of DHCP assigned IP address.
• IP Address – Module IP address.
• IP Mask – Subnet mask.
• Gateway – Network gateway.
• DNS1, DNS2 – DNS addresses.
• Reset to default – Reset to default settings:
  • To restore the module to factory settings, type reset into the empty field and confirm using Save.

Communication with a module from an external network

WWW:

• Port: TCP/UDP/IP 80

KNX/IP protocol:

• Multicast address: UDP 224.0.23.12
• Port: 3671

Computer programme or own application:

• Port: TCP/UDP/IP 9761

Modbus TCP:

• Port: TCP/IP 502

SNMP protocol:

• Port: UDP 161

Device functions

Device status

• Model: device type (eg. LantickPro-4-4)
• Firmware: installed module firmware revision
• IP: module IP address
• MAC: module MAC address
• Name: user-defined module name

Outputs table

• Name: channel name assigned by the user (default: CH1, CH2...),
• On/Off: allows turning the output on or off by clicking the appropriate icon.
  Colour of the icon informs about the output state:
  • red – output deactivated,
  • green – output activated.
• Coil State: relay state active/inactive.
  • This state can be different from the On/Off column eg. in astable mode, where a channel is displayed as activated (On/Off green) but the relay is alternately on/off according to the Time On and Time Off settings.

Inputs table

• Name: channel name assigned by the user (default: CH1, CH2...),
• In State: current input circuit state
  (red colour – input inactive, green colour – input active),
• Counter: counter input state (applies to inputs; output state counting is described below),
• Action: Counter reset. Clicking "Reset" causes the appropriate counter to reset.

<response>
  <prod_name>Lantick-8-0</prod_name>
  <user_name></user_name>
  <out>0000000000000000</out>
  <on>0000000000000000</on>
  <in>0000000000000000</in>
  <counter1>166</counter1>
  <counter2>7</counter2>
  <counter3>0</counter3>
  <counter4>2</counter4>
  <counter5>22</counter5>
  <counter6>0</counter6>
  <counter7>0</counter7>
  <counter8>0</counter8>
  <counter9>0</counter9>
  <counter10>0</counter10>
  <counter11>22</counter11>
  <counter12>0</counter12>
  <counter13>0</counter13>
  <counter14>0</counter14>
  <counter15>0</counter15>
  <counter16>0</counter16>
  <insim></insim>
</response>

The above XML file informs about:

• prod_name – Product name,
• out – All outputs state,
• on – Output activation (in astable mode, periodic output activation and deactivation can be defined: in the out tag, one output state alternates - in the on tag, output activation is indicated as "1"),
• in – Inputs state,
• counter[x] – Counting input state (applies to both inputs and outputs).

Visualization

In the Administration tab, select the Enable Graphic Mode Config and confirm the selection with Save.

• Saving the settings allows change of background graphic and arrangement of input and output icons.
• The Map tab enables transition to graphic mode.

Background

To change the background:

1. Open the settings in the Map tab.
2. Click the Browse button to select an image file from the PC's hard drive.
3. Upload the file to device memory using Upload JPG (during the file loading process, the cursor will assume the form of an hourglass).
4. After uploading is complete, refresh the browser (F5 key).

After selecting the appropriate background, move the cursor to a selected icon, click and hold the left mouse button and move the icon to selected coordinates. Save the changes.

Clicking the output symbol causes its state to change. The background colour underneath the output symbol represents the relay contact position (green-closed, red-open).

Picture Mode

The Picture Mode field at the bottom of the MAP tab enables channel selection:

• 1 Picture – single picture (displayed entirely),
• 2 Pictures – Select by Channel X – selection of two picture mode switched by input or output No. X.

Output channel configuration

• Name – The user can assign a name to the channel (up to 15 characters),
• Output mode – Selected output channel operation mode selection:
  • Disable – Channel disabled, no activity,
  • Bistable – Bi-stable mode, the relay remains in one state (activated or deactivated),
  • Astable – Astable mode, the relay is activated and deactivated with defined time periods (Time On and Time Off),
  • Time based – Single trigger mode, the output is activated after the defined time period (Time Off) and remains active for the (Time On) time,
  • Shutter – Shutter control mode, groups two relays preventing simultaneous activation of both,
  • Comm Monitor – Test mode used for output operation monitoring.
• Power on state – Define output channel state after the device is restarted:
  • Off – Output channel disabled,
  • On – Output channel enabled,
  • Last state – The output channel assumes the state it had before the power was disconnected,
  • Invert out – Output state inversion. Changes the output mode from NO to NC.

Output channel mode explanation:

• Bistable: The relay switches between two stable states - enabled or disabled.
• Astable: The channel operates periodically, the relay alternates between enabled and disabled according to defined Time On and Time Off times.
• Time Based: The output operates according to the rules:
  • If Time On > 0 and Time Off > 0, the output will activate after Time Off and remain active for Time On,
  • If Time On > 0 and Time Off = 0, the output will activate for Time On, and then deactivate,
  • If Time On = 0 and Time Off > 0, the output will activate after Time Off.
• Shutter: This mode groups two relays enabling safe shutter control and preventing simultaneous activation of both. Two output channels are used to control one shutter:
  • Full move time: Time needed to open or close the shutter entirely,
  • Half move time: Time needed to open or close the shutter half-way.

• Comm Monitor: Function enables monitoring of communication between two Lantick devices. It's useful when one device sends frames to the other one and monitors what happens on the device receiving those frames.
  • Function operation:
    • Connecting two Lantick devices:
      Two Lantick devices need to be connected so that one is sending frames to the other one.
    • Enabling the Comm Monitor option:
      This function needs to be active on the device that will monitor communications.
    • Frame monitoring:
      The receiving device monitors the channel it awaits the frames on.
    • No frames received:
      If no frames are received on the monitored channel (eg. channel 4) for a defined time (default 30s), the Comm Monitor function will activate another channel (eg. channel 1).
    • Notification about lack of communication:
      If no frames are received for a determined period of time, channel 1 can be activated. It can be a bell or other device signaling connection problems.

• Disable: The channel is disabled, no activity during protocol control.

Input channel configuration

• Name – The user can assign a name to the channel (up to 15 characters).
• Destination channel – Channel number in the remote device that is to be activated. The output channel state will be reproduced in the input channel.
• C2O HoldOn time – Time after which the "HoldOn" event will be triggered for the Comm2Other service.
• C2O Repetition – The frequency the module will retry sending of the last triggered frame in the Comm2Other service with. For example, the "HoldOn" frame will be transferred periodically until a "HoldOff" frame that will resume the periodic sending appears.
• Counter input filter – Input signal filter. Can be used to eliminate interference.
• Invert in – Inversion of the input channel. Changes the input mode from NO to NC.

Input simulation mode

For control system operation testing, the input simulation mode can be used. To enable this mode, type in the following address into the web browser: http://nr_ip/stat.php?insim=1

In the simulation mode, it's possible to activate inputs with a click on the input icon. The input will remain active as long as left mouse button is held down.

To disable simulation mode, type in the following address into the web browser: http://nr_ip/stat.php?insim=0

<response>
    <ch1>Switch 1</ch1>
    <ch2>Switch 2</ch2>
    <ch3>Lamp</ch3>
    <ch4>Fan</ch4>
    <ch5/>
    <ch6/>
    <ch7/>
    <ch8/>
    <ch9/>
    <ch10/>
    <ch11/>
    <ch12/>
    <ch13/>
    <ch14/>
    <ch15/>
    <ch16/>
    <prod>LantickPro-2-2</prod>
    <user>Demo1</user>
</response>

The above XML file informs about:

• ch – Lantick device channel name defined by the user,
• prod – Product name,
• user – Module name defined by the user.

SNMP server configuration

To use the SNMP protocol, it's required to save the MIB file using the right mouse button, clicking the Download MIB file link and selecting the Save link as option. Next, use the appropriate program, eg. MIB Browser. After starting the program, it is required to upload the downloaded MIB file.

The next step is to input the device's IP address (Lantick's in this case, default IP: 192.168.111.15) and select an appropriate operation. The OID field can be left blank for the program to display all table contents.

Input, output, counter states and general information about the Lantick module are displayed in the table. To preview an element from the MIB tree table, double click it. On the left side of the programme's window an access path will be displayed.

OID structure in the MIB tree

Each element in the MIB (Management Information Base) has an unique OID (Object Identifier) number assigned. OID is the path identifying the given element in the structure made by numbers separated by dots. This is an OID structure example:

Basic OID example: - OID: iso.org.dod.internet → .1.3.6.1

The following digits in the OID define subfolders in the MIB tree structure. This is an OID structure example for particular folders and functions:

OID examples for folders:

• Folder inveo: .1.3.6.1.4.1.42814
• Folder Lantick: .1.3.6.1.4.1.42814.28
• Folder control: .1.3.6.1.4.1.42814.28.3
• Folder channels: .1.3.6.1.4.1.42814.28.3.1

OID examples for channels:

• Channel input: .1.3.6.1.4.1.42814.28.3.1.1

OID functions

• Last OID digits define the functions assigned to a given channel: Function examples:

• Output activation/deactivation:

  • OID: .1.3.6.1.4.1.42814.28.3.1.1.2.x
  • Where x is the output number (number starting with 0).

• Coil status control:

  • OID: .1.3.6.1.4.1.42814.28.3.1.1.3.x
  • Where x is the output number (number starting with 0).

• Checking the input state

  • OID: .1.3.6.1.4.1.42814.28.3.1.1.4.x
  • Where x is the input number (number starting with 0).

• Checking the counter input:

  • OID: .1.3.6.1.4.1.42814.28.3.1.1.5.x
  • Where x is the input number (number starting with 0).

To activate input No. 2, advanced settings configuration is required. To do that, press the Advanced button located next to the device's IP address.

After the above steps are complete, output No. 2 can be set as enabled. The channelOn.1 (1 because the inputs are numbered starting from 0) should be selected and the Set button should be right-clicked.

The next step is to input the value of 1 into the Value field, and accept with OK.

Communication protocols and administration

Module name

Each module can have a unique name assigned for identification.

Changing the password

To change the password, input the current password into the Current Password field. Input your new password into the New Password and Re-type Password fields and save using Save Config.

User Password
User password change (access only to the home page) (Username: user):

• New Password – new password,
• Re-type Password – new password confirmation.

Admin Password
Administrator password change (access to all settings) (Username: admin):

• Current Password
• New Password
• Re-type Password

Services settings

The device allows selection of what services should available. Selecting the field next to the name of the service and pressing of the Save button activates the selected service.

• Enable User Password
• Enable Admin Password
• Enable Program Access – enable access by external programs,
• Enable Modbus TCP Server
• Enable SNMP – enable SNMP agent,
• Enable Destination Client – the service for forwarding the input/output states to other modules (bridge mode),
• Enable Comm2Other Module – enable communication on the multicast address (IP:224.0.23.12 port 3671),
• Enable Inveo Dashboard – cloud control service http://dash.inveo.com.pl,
• Enable TFTP Bootloader
• Enable Remote Network Config – (Discoverer programme),
• Enable Graphic Mode Config – configuration of graphic mode from the Map menu,
• Disable LED – disables LED indicators on the module. If the reset button is pressed, the indicators will glow for 5 minutes and then shut off (Lantick PE-4-4, PE-0-8, PE-8-0, PE-0-16, PE-16-0),
• LED Status 1/2 – allows the user to select a channel, the front-panel Status LED will represent the state of (Lantick PE-2-2, PE-0-4).

Communication protocols

The device supports the following control methods:

• Built-in www page,
• KNX/IP protocol,
• Inveo Dashboard access service http://dash.inveo.com.pl,
• SNMP,
• Modbus TCP,
• HTTP,
• Windows command line programme,
• Linux programme,
• Android smartphone/tablet (e.g. HTTP Shortcuts app – set the HTTP request that uses dash.inveo.com.pl and sends the command to Lantick).

1 to 1 communication – LAN extender

The modules are equipped with inputs that can transfer information to devices with outputs, in order to react for channel activation. This means that when the input module is activated, it will automatically communicate with the appropriate device (Lantick) and activate the output channel. After the input channel is deactivated, the appropriate output channel is deactivated too. This functionality is useful for applications where replication of the input state to a remote output is required.

Configuration

1. Input module settings

In the Lantick module with inputs, go to the Administration tab and Enable Destination Client. After that, fill in the following fields:

• Destination IP: Input the IP address of the output module,
• Destination Port: Enter the port number, on which the Lantick listens. (default: 9761).

2. Channel assignment

Go to the Channel tab and select which output should be activated the moment an input channel is activated.

3. Output module settings

In the output module, access the Administration tab and Enable Program Access.

This configuration allows for direct communication between modules, allowing for instantaneous reaction of outputs to input state changes.

Communication protocols

The devices can be connected to a network, allowing for creation of advanced control systems. "All to all" communication settings can be changed in the Comm2Other tab. The modules are equipped with tools that simplify module-to-module communication. The following protocols can be used:

• TCP,
• UDP,
• KNX,
• HTTP GET.

Comm2Other – KNX

The Lantick supports a protocol compatible with KNX-IP in Routing mode. The protocols is designed to control home ("smart homes") and office automation.

The network is built around the all-to-all principle without a Master device, even though it is possible to specify one for more extensive installations. Failure of one module does not render the entire network unoperational. Communication between modules is carried out via LAN using UDP multicast broadcast packets.

Configuration and operation are based on the principle that the receiving devices (e.g. relays connected to lamp circuits, shutters) and triggers (inputs) are assigned to a common group. Each input channel has an assigned address and command. The output channel can react (on, off, invert state, activate with a delay, shutter) to specified groups. When an input sends the command to the defined group address, all receivers that have the group assigned will react. Each input/output can have several addresses assigned. The inputs can send various events to the address such as: pressing, holding, release of a button. Additionally, they can send a pre-defined TCP, UDP or HTTP frame. Outputs can be connected in sections to control shutters. The system can be expanded with a central unit for building visualisastion and remote control.

All KNX devices preview

The View all modules function is useful for configuring extensive systems. This function scans the LAN, detects all Inveo devices that have KNX protocol activated and fills a table with them.

Frame format converter

Clicking the Configurator button in Comm2Other opens a KNX service configuration window. The following buttons are located in the upper-right corner of the tab.

• Save data – The process takes around 10 seconds to complete,
• Clear data – Clear current settings,
• Close – Close the configuration window,
• Toggle Frame Format – Toggle between ASCII and HEX representation,
• 1, 2, 3, 4, 5, 6, 7, 8 – Navigation buttons, open the view of the selected input/output,
• Calc – Decimal to HEX time format calculator.

Controlling the output channels

In this table, basic (DPT 1.xxxx) or priority (DPT 2.xxxx) functions can be used.

Using the priority function (DPT 2.xxxx) locks the basic functions.

This is useful for example:

• During a fire – All shutters open and can not be closed,
• When a light is switched on and we do not want anyone to turn it off.

KNX commands

• ReadState – Address allowing for readout of module state (e.g. by an external program). Assumes values 0-31/0-7/0-255,

• On (DPT 1.001) – Output activation – can assume 2 values:

  • \x00 – Output deactivation,
  • \x01 – Output activation.

• Off (DPT 1) – Function opposite to On (DPT 1.001). Used when the deactivation of one device should cause the activation of another one.

• Invert (DPT 1.012) – Output state invert:

  • \x00 – This command will NOT cause the outputs state to be inverted,
  • \x01 – Output state inversion.

• Time – Timed output activation/deactivation:

  • \x00 – Relay deactivation,
  • \x01– TonMSB TonLSB ToffMSB ToffLSB – Activation of relay for the defined time period after a delay. This time is in 0,1 second units in HEX format.

• On Control (DPT 2.001) – Output activation with priority – can assume 4 values:

  • \x00 – Output deactivation – functions like On (DPT 1.001),
  • \x01 – Output activation – functions like On (DPT 1.001),
  • \x02 – Sending this command will deactivate the output with priority – the output can be unlocked (lock flag deleted) by sending \x00 or \x01. The output can be deactivated with \x03 or manually (the lock flag will still remain active),
  • \x03 – Output activation with priority – the output can be unlocked (lock flag deleted) by sending \x00 or \x01. The output can be deactivated with \x02 or manually (the lock flag will still remain active),

• Off Control (DPT 2.001) – Function opposite to On Control (DPT 2.001) with priority.

• Invert (DPT 2.012) – Output state inversion with priority, assumes 4 values:

  • \x00 – This command will NOT cause the outputs state to be inverted,
  • \x01 – Output state inversion,
  • \x02 – Sending this command will lock the output in its current state with priority. The output can be unlocked (lock flag deleted) only by sending \x00 or \x01,
  • \x03 – State inversion with priority – The output can be unlocked (lock flag deleted) only by sending \x00 or \x01.

• Scene Control (DPT 18.001) – Store the current scene settings, e.g. outputs 1 and 3 activated, 2 deactivated, 4 – unspecified.

Store outputs 1, 2 and 3 to group 1/1/1 (type 1/1/1 into Scene control).

Scene write/read command: \xab, where:

• a:
  • Value of „0” activates the scene from device memory,
  • „8” writes the current scene to the device's memory.
• b: subsequent scene numbers, max 16. Assume the values 0-F.

Scene Control is used for frequently used settings, e.g. after a work day, power to all workstations is to be cut – all outputs deactivated; in one room at 5:55, the ceiling, wall lights and PC power should be switched on.

Up to 4 different groups can be assigned to each output channel (Group 1-4 table columns). The output channel will respond with a defined command to each of the assigned groups.

KNX commands for channel configuration in shutter/gate mode

• Step (DPT 1.007) – Increase/decrease the shutter opening by a step:

  • \x00 – Up,
  • \x01 – Down.

• Up/Down (DPT 1.008) – Open/close the shutter:

  • \x00 – Open the shutter entirely. Sending this command again will not cause the shutter to stop,
  • \x01 – Close the shutter entirely. Sending this command again will not cause the shutter to stop.

• Stop (DPT 1) – Stop the shutter:

  • \x00 – Shutter stop,
  • \x01 – Shutter stop.

• Up/Down with Stop (DPT 1) – Open/close the shutter with the ability to stop it – if the command is set once, the shutter will start to open/close, sending the command again will cause it to stop:

  • \x00 – Shutter open/stop,
  • \x01 – Shutter close/stop.

• Gate (DPT 1) – Open/close/stop the shutter alternately. Sending the command again will deactivate the output, stopping the shutter:

  • \x00 – Shutter stop,
  • \x01 – Shutter open/stop/close.

• Step Control (DPT 2.007) – Step (DPT 1.007) function with priotity. Increase/decrease the shutter opening by a step:

  • \x00 – Up,
  • \x01 – Down,
  • \x02 – Up with priority (DPT1.X control locked),
  • \x03 – Down with priority (DPT1.X control locked).

Output can be unlocked (lock flag removed) only by sending \x00 or \x01.

• Up/Down Control (DPT 2.008) – Up/Down (DPT 1.008) function with priority. Open/close the shutter:
  • \x00 – Open the shutter entirely. Sending this command again will not cause the shutter to stop,
  • \x01 – Close the shutter entirely. Sending this command again will not cause the shutter to stop,
  • \x02 – Open the shutter entirely with priority. (DPT1.X control locked),
  • \x03 – Close the shutter entirely with priority. (DPT1.X control locked).

Output can be unlocked (lock flag removed) only by sending \x00 or \x01.

• Stop Control (DPT 2) – Stop (DPT 1) with priority – stops the shutter:
  • \x00 – Shutter stop,
  • \x01 – Shutter stop,
  • \x00 – Shutter stop with priority (DPT1.X control locked),
  • \x01 – Shutter stop with priority (DPT1.X control locked).

Output can be unlocked (lock flag removed) only by sending \x00 or \x01.

• Up/Down with Stop Ctrl (DPT 2) – Up/Down with Stop (DPT 1) with priority. Open/close the shutter with the ability to stop it – if the command is set once, the shutter will start to open/close, sending the command again will cause it to stop:
  • \x00 – Shutter open/stop,
  • \x01 – Shutter close/stop,
  • \x02 – Shutter open/stop with priority (DPT1.X control locked),
  • \x03 – Shutter close/stop with priority (DPT1.X control locked).

Output can be unlocked (lock flag removed) only by sending \x00 or \x01.

• Gate Control (DPT 2) – Gate (DPT 1) with priority. Open/close/stop the shutter alternately. Sending the command again will deactivate the output, stopping the shutter:
  • \x00 – Shutter stop,
  • \x01 – Shutter open/stop/close – Sending the command again while the shutter is moving, will deactivate the output, stopping it,
  • \x02 – Shutter stop with priority (DPT1.X control locked),
  • \x03 – Shutter open/stop/close with priority (DPT1.X control locked).

Output can be unlocked (lock flag removed) only by sending \x00 or \x01.

• Blind Control (DPT 3.008) – Open/close/stop the blind:

  • \x00 – Blind stop,
  • \x07 – Blind open,
  • \x0F – Blind close.

• Percentage 0-100% (DPT 5.001) – Percentage opening of the shutter. To open the shutter half-way, write 50 in HEX: 50dec = 32hex.

  • \xCC – Percentage opening of the shutter, where CC is % in HEX.

• Value 0-255 (DPT 5.004) – 0-255 opening of the shutter: 0 - shutter closed, 255 - shutter open entirely. To open the shutter to around 70%, calculate the 70% of 255 = 178,5 and convert it to HEX rounding down: 178dec=B2hex.

  • \xCC – 0-255 opening of the shutter (0-100%), CC in HEX.

• Scene Control (DPT 18.001) – Store the current scene settings.

Store the shutters 1, 2, 3 settings to group 1/1/1 (1/1/1 in Scene control).

Scene write/read command: \xab, where:

• a:
  • Value of „0” activates the scene from device memory,
  • „8” writes the current scene to the device's memory.
• b: subsequent scene numbers, max 16. Assume the values 0-F.

Configuration of triggers – input channels

• ReadState – State read address (e.g. by an external program). Assumes values 0-31/0-7/0-255,

The timing of sending the frame depends on the assigned function:

• On 0 – Detects the rising edge (will be recalled when a high state is present at the input),
• Off 0 – Detects the falling edge only if the high state persisted for less than C2O Hold On Time (recalled after the input voltage disappears, after a button is released),
• Hold On 0 – Reacts to a high state on the input, only if it persisted for C2O Hold On time defined in the Channel tab,
• Hold Off 0 – Reacts to a low state on the input, only if it persisted for at least C2O Hold On Time.

Recall of a specified function is dependent on the input pulse length. The input pulse recalls the event saved as On. If the pulse persists for a time longer than the C2O Hold On time – the Hold On function is recalled. If the pulse stops before C2O Hold On time passes, the Off function is recalled. If the pulse stops after C2O Hold On time passes – action Hold Off will be recalled.

The aforementioned functions can send the frames periodically depending upon the C2O Repetition time. The device can send the last triggered frame periodically, e.g. HoldOn can be sent with the specified frequency until a HoldOff frame appears (that will be sent periodically too).

Protocol column

The following settings can be selected:

• Disable – Control disabled,
• TCP – TCP control,
• UDP – UDP – multicast control,
• KNX – KNX protocol,
• HTTP GET – HTTP GET control.

IP column

Input the IP address of the target device.

Port column

Input 80 if using HTTP GET. For TCP/UDP, input the port the remote device listens on (9761 by default).

KNX Group column

Using the KNX protocol, you define groups, which are the link to control the outputs.

Frame field

Type in the commands that will be sent.

Try! button

The button allows the user to test the data frame operation.

KNX addressing

KNX communication is carried out by broadcasting data to specified groups. The output channels react to groups defined in input channels. The groups can be assigned to different outputs.

The group addressing in KNX has the following format: a/b/c

• a: main group 0-31 (the standard specifies 0-15),
• b: intermediate group 0-7,
• c: subgroup 0-255.

e.g.: 4/0/8

Example group assignment:

Creating groups:

• 1/0/0 – control main lighting in the kitchen,
• 3/0/0 – control main lighting in the boiler room,
• 4/2/3 – control the southern shutter in the garage,
• 2/2/2 – control the northern shutter in the living room.

Example module connections:

Comm2Other – TCP/UDP

In the Comm2Other tab, it us possible to select the TCP or UDP client settings. This means that the "server" device listens on the specified port, and a Lantick module can send a notification to it.

Comm2Other – HTTP GET

By using the HTTP GET protocol, other devices that have HTTP implemented can be controlled. Depending on the current state of the device input, the appropriate HTTP protocol commands are sent, to which the module with a defined IP number will respond.

Cloud control

Inveo Dashboard allows for controlling module outputs and input state preview via the http://dash.inveo.com.pl webpage.

After clicking Enable Inveo Dashboard in the Administration tab, the module sends the current input/output state to the server.

To use Inveo Dashboard, it is required to create and activate an account.

After typing the address into a web browser, click Create an account. Fill all fields in the new window and click the reCAPTCHA.

Click Create after filling in the form. An e-mail message containing a confirmation link will be sent to the e-mail address provided during the sign-up process.

After logging into the account, add the devices that you want to control and preview status of.

After clicking Add device, a window used to provide a key read from a Lantick module will appear. The key is located in the Administration tab.

A window containing required data will appear after clicking on the hyperlink.

To add a new device, paste the key from the first field.

The device can be deleted by providing the key from the second field.

Windows command line control programme

When controlling the module from the command line, the cURL program can be used.

First, Enable Program Access in the Administration tab.

<response>
    <prod_name>Lantick</prod_name>
    <sv>1.42</sv>
    <mac>00:00:00:00:00:00</mac>
    <out>00000000</out>
    <on>00000000</on>
    <in>00000000</in>
    <counter1>15</counter1>
    <temp1>0</temp1>
</response>

Linux control programme

cURL can be used in Linux:

curl -u admin:admin00 "http://192.168.111.15/stat.php" -w "\n" 2>/dev/null | grep 'prod_name' | awk -F "[><]" '/prod_name/{print $3}'

Modbus TCP

To activate the function, go to Administration > Enable Modbus TCP Protocol. Default port: 502.

The device supports the following Modbus functions:

• 0x01 Read Coils
• 0x03 Read Holding Register
• 0x05 Write Single Coil
• 0x06 Write Single Register
• 0x0F Write Multiple Coils
• 0x10 Write Multiple Registers

Holding Registers addressing

Coils addressing

HTTP GET

Lantick modules can be controled via HTTP. Depending on the current status of the device, HTTP commands the module will react to can be sent. To read the current state of the module, recall the subpage (for example http://192.168.111.15/stat.php).

The module state is also available via htttp://IP_address/status.xml. The status.xml resource is read-only and does not require an access password. The device name is not shown in status.xml.

The XML file contains the necessary information:

<response>
    <prod_name>Lantick-PE-2-2</prod_name>
    <user_name>
    <out>0000000000000001</out>
    <on>0000000000000001</on>
    <in>0000000000000000</in>
    <counter1>166</counter1>
    <counter2>7</counter2>
    <counter16>1</counter16>
    <insim/>
</response>

Available HTTP GET commands:

Examples of module control via HTTP:

1. Activate the OUT2 output: http://192.168.111.15/stat.php?on=2
2. Invert the state of OUT1: http://192.168.111.15/stat.php?inv=1
3. Deactivate the OUT2 output: http://192.168.111.15/stat.php?off=2
4. Activate output 1; negate 2: http://192.168.111.15/stat.php?set=000000n1
5. Set the channel 3 counter value to 1234: http://192.168.111.15/stat.php?cnt=3,1234
6. Send the frame defined in Comm2Other for Hold On of channel 5: 192.168.111.15/stat.php?c2o_hon=4

TCP/UDP/IP communication protocol description

Data frame for TCP/UDP port 9761.

* Chx returns 2 bytes:
1 – output state,
2 – coil or input state.

The module listens on TCP/UDP port 9761 by default. Example frames:

Activation of output #1 in static mode

15 1 0 1 1 0 0 0 0 0 18
0x0F 0x01 0x00 0x01 0x01 0x00 0x00 0x00 0x00 0x00 0x12

Deactivation of output #1

15 1 0 1 0 0 0 0 0 0 17
0x0F 0x01 0x00 0x01 0x00 0x00 0x00 0x00 0x00 0x00 0x11

Read input #2 counter value

15 12 1 0 0 0 0 0 0 0 28
0x0F 0x0C 0x01 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x1C

Set input #2 counter to 100

15 10 1 100 0 0 0 0 0 0 126
0x0F 0x0A 0x01 0x64 0x00 0x00 0x00 0x00 0x00 0x00 0x7E

TCP/UDP in program control

The Lantick devices can be controlled via TCP/UDP using text commands. The module listens on port 9761. All HTTP GET commands are supported.

On the device's webpage, go to the Administration tab and Enable Program access. Save the changes.

Send the character string beginning with '?' to port 9761 along with the appropriate command.

Application examples

Example of a bridge connection configuration between two Lantick modules

Objective: Configuring of two Lantick modules for cooperation, where one device operates as a transmitter and the other one as a receiver with TCP/IP port connection.

Implementation instructions:

First (transmitter) module configuration:

• Set the IP address of the device that will operate as a transmitter: 192.168.111.15
• Enter the Administration tab and set the IP address of the controller (second module) in the Destination IP field: 192.168.111.16
• In the Port field, set the value: 9761

• In the Channel tab, go to Channel 1 and set the Dest field to: dest 1

• Next, in the Channel tab, go to Channel 2 and set the Dest field to: dest 2

Second (receiver) module configuration:

• Set the IP address of the device that will operate as a receiver: 192.168.111.16

Testing:

After both modules are configured, you can start testing:

• Trigger Input 1 in the 192.168.111.15 module (eg. with a button or an external signal).
• Verify if Output 1 in the 192.168.111.16 module has been triggered.
• Trigger Input 2 in the 192.168.111.15 module and verify if Output 2 in the 192.168.111.16 module has been triggered.

Operation summary:

• Thanks to this configuration, after the 192.168.111.15 module inputs are triggered, the corresponding outputs in the 192.168.111.16 module will be automatically activated, which enables the connection of two devices in an automation system.

Description:

A bridge connection between two Lantick modules allows for creation of more advanced automation systems where one device controls the outputs based on signals received from the other device. Thanks to this configuration both devices can cooperate using a wired or wireless connection, allowing for automatic output activation in response to external inputs.

Example of a window shutter motor connection to the PE-2-2 module

Objective: Window shutter control using the Lantick PE-2-2 module and opening/shutting relays. The configuration includes the setting of Full Move Time, which is crucial for correct system operation.

Implementation instructions:

1. Connecting the shutter motor to the PE-2-2 module:

   • Make sure the motor is connected to the Lantick PE-2-2 device correctly.
   • The shutter motor must be connected to the appropriate relay outputs of the module - for example Output 1 and Output 2.
   • Output 1 will be responsible for unveiling of the roller shutter and Output 2 for covering it up.

2. Full shutter move time configuration:

   • In the PE-2-2 control panel go to the Channel Configuration tab.
   • Select the appropriate channel (eg. Channel 1) responsible for controlling the shutter.
   • Define Full Move Time – the time needed for the shutter to fully open or close. If the shutter completes its motion in 30 seconds, set Full Move Time to 30 seconds (300).

Testing:

After applying the settings, make sure the shutter operates correctly. It should open after 30 seconds and close after another 30 second period. If the shutter is operating correctly, you can change the movement and delay times to suit them to your needs.

Connection of a signalling device or additional devices:

You can also connect a signalling device to the output to notify you when the shutter fully opens or closes.

Description:

Shutter control in home automation systems using the PE-2-2 module enables precise control of their movement. In this function, correct Full Move Time setting is crucial - enabling synchronization of relays to the time needed to fully open or close the shutters.

The Lantick PE-2-2 enables fully automatic shutter control. The system can be easily adapted to the user's individual needs, taking the delay, opening and closing times into consideration.

Monitoring of communication between two Lantick devices in an alarm system using the Comm Monitor function

Objective: Using the Comm Monitor function to monitor if the Lantick device responsible for alarms is receiving signals from the alarm control unit. If no signal is present, the device activates an alarm device (eg. a bell).

Implementation instructions:

Connecting the Lantick devices:

• Make sure that both Lantick devices are connected to the same local network.
• Device 1 (np. 192.168.111.15) is connected to the alarm system.
• Device 2 (np. 192.168.111.16) serves the function of a receiver monitoring communication with Device 1.

Comm Monitor configuration on Device 2:

• Log in to the Device 2 control panel using a web browser, entering the IP address (eg. http://192.168.111.16).
• Go to the Administration tab.
• Select Enable Program Access.

• Next, in the Channel tab, Output mode row select Comm Monitor.
• Choose a channel (eg. Channel 4) to monitor the communications on.

Setting monitoring parameters:

• Set the timeout to 30 seconds (default value).
• If Device 2 doesn't receive a frame from Device 1 for 30 seconds (eg. the alarm controller doesn't transmit any information), Device 2 will trigger the Channel 1 alarm signal automatically.

Connecting the signalling device:

A signalling device (eg. a bell or a control lamp) can be connected to the Channel 1 output of Device 2 to notify about communication problems.

Description:

The Comm Monitor function is perfect for use in alarm systems where reliable communication between devices is crucial. If the receiving device doesn't receive any signals for a defined time (eg. 30s), it automatically triggers an alarm or a device notifying about connection failure.

Lighting and shutter control in a guest room using the Lantick and KNX

Objective: Designing a lighting and shutter control system for a guest room using two Lantick modules and the KNX system. The mono-stable wall switch allows lightning and shutter control depending on the action type.

Implementation instructions:

1. Configure the Lantick 0-8 inputs:

2. In the Comm2Other tab configure:

   • Channel 3: assign KNX group 1/1/1 to Off 0 function.
   • Channel 3: assign KNX group 1/1//2 to Hold On 0 function.

1. Configure the Lantick 8-0 outputs:

2. In the Channel tab set channel 1 to bistable mode.

• In the Comm2Other tab, configure:
  • Channel 1: assign KNX group 1/1/2 to On Control function.
  • Channel 2: assign KNX group 1/1/1 to Invert function.

System operation

1. Short button press:

2. Triggers the Off 0 function, causing a signal to be sent to the KNX group 1/1/1.

3. Lantick 8-0 changes the Output 2 (lightning) state, turning the guest room lighting on or off.

4. Button hold:

5. Triggers the Hold On 0 function, causing a signal to be sen to the KNX group 1/1/2.

6. Lantick 8-0 controls the Output 1 (shutter), alternating between opening an closing the guest room window shutter.

One-to-many or many-to-one communication with connection loss failsafe

Objective: Controling multiple output modules using a single input module. In an event of communication loss, the output modules will switch of automatically after specified time.

Implementation instructions:

Connecting the Lantick devices:

• Make sure that both Lanticks are connected to the same local network.
• Device 1 – Lantick PE-0-8 – serves the function of a Master device, to which a switch is connected. Toggling the switch should cause activation/deactivation of output channels in both output modules.
• Devices 2 and 3 – Lantick PE-2-2 – Slave devices. In the event of a Master - Slave communication loss, all outputs should automatically be deactivated after 10 seconds.

Module No. 1 configuration:

• Log in to the Device 1 control panel using a web browser, entering the IP address (e.g. http://192.168.111.15),
• Go to the Administration tab,
• Enable C2O Module,

• In the upper section, a notification about a device reset will appear. Click the highlighted button,
• In the Channel tab, for Channel 1 enter the following settings:
  • C2O HoldOn time – 0,
  • C2O Repetition – 4.

• In the Comm2Other > Channel In 1 tab, for On 0, select KNX, assign the group 1/1/1 and enter the following data frame: \x01\x00\x64

• For Off 0, select KNX, assign the group 1/1/2, enter the frame: \x01

Modules No. 2 and 3 configuration

• Log in to the Device 1 control panel using a web browser, entering the IP address (e.g. http://192.168.111.15),
• Go to the Administration tab,
• Enable C2O Module,

• In the upper section, a notification about a device reset will appear. Click the highlighted button,
• In the Comm2Other > Channel Out 1 tab, for Off 0 (DPT 1), assign the group 1/1/2,
• For Time, assign 1/1/1.

Factory settings, backup

To restore the device to factory settings, hold the RESET button for 10 seconds. The button is located on the device's housing:

• In 4-4, 0-8, 8-0, 0-16 and 16-0 models, the RESET button is located on the front panel of the device (wrench symbol).

• In 2-2, 0-4 models, the button is located in the upper section of the device, near the power connector.
• In 0-1, 1-0, 1-1 models, the button is located in the lower section of the device, near the Ethernet port.

Once the above steps have been completed, the device will be set to the following parameters:

• IP address: 192.168.111.15
• IP mask: 255.255.255.0
• User: admin
• Password: admin00

Backup / Restoring user settings

To save all user configuration data, download the file from the Backup tab:

1. Click the Download button in the Backup section.
2. Save the file on your hard drive.

Restoring settings:

1. Select the backup.bin file.
2. Click the Upload button to restore saved settings.

Warranty and manufacturer's liability

The manufacturer undertakes to respect the warranty agreement, if the following conditions are met:

• All repairs, changes, expansions and device calibrations are carried out by the manufacturer or an authorized service center,
• The power supply system meets the applicable standards,
• The device is operated in accordance with the suggestions presented in this manual,
• The device is operated in accordance with its intended purpose.

The manufacturer assumes no responsibility for consequences resulting from improper installation, improper use of the device, failure to comply with the instruction manual, and repairs made by unauthorized personnel.

Storage, operation and transport conditions

The device should be stored in enclosed rooms, where the atmosphere is free from vapours and corrosive substances:

• Environment temperature from -30°C to +60°C (-22°F - 140°F),
• Humidity from 25% to 90% (condensation unacceptable),
• Atmospheric pressure from 700 to 1060 hPa.

The device is intended to operate in the following conditions:

• Environment temperature from -10°C do +55°C (14°F - 131°F),
• Humidity from 30% to 75%,
• Atmospheric pressure from 700 to 1060 hPa.

Recommended transport conditions:

• Environment temperature from -40°C do +85°C (-40°F - 185°F),
• Humidity from 5% to 95%,
• Atmospheric pressure from 700 to 1060 hPa.

Installation and device operation:

• The module should be operated in accordance with recommendations provided later in this manual.

Disposal and decommissioning

In an event the device needs to be decommissioned (eg. after its intended life period is surpassed), it is recommended to contact the manufacturer or his representative, who are responsible to respond appropriately, i.e., to collect the device from the user. The user can alternatively contact companies specializing in electronic device or computer equipment disposal and/or decommissioning. Under no condition should the device be placed with other waste.