Nano Out

Overview

Purpose of the device

Nano Relay Output is specifically designed to control a single electrical circuit via a relay output. Its compact design allows easy installation in various environments, providing reliable and precise control of the electrical circuit. Users can manage the relay output state via a LAN network, enabling flexible and efficient remote control.

Nano Relay Output supports various communication protocols, such as HTTP GET, Modbus TCP, SNMP, MQTT, and TCP/UDP, allowing integration with a wide range of monitoring systems and applications. Additionally, the built-in web interface allows for intuitive device management, giving users access to advanced configuration and monitoring options. These features make Nano Relay Output a perfect solution for remote control of electrical devices in smart buildings, industrial automation systems, and other applications where precision and reliability are crucial.

Changelog

1.0 13th of March 2025

• Firmware revision v1.42

Device construction

Nano Relay Output PoE

Technical characteristics

Dimensions

General characteristics

The device is equipped with a 7-segment LED display, on which the current output state can be shown (ON or OFF). The following communication options are available:

• Built-in WWW server, available from a standard web browser (Mozilla Firefox, Opera, Google Chroma are preferred),
• Windows/Linux command line programs,
• HTTP GET,
• Modbus TCP,
• SNMP,
• Own application via TCP (shared protocol),
• Inveo MQTT protocol.

Module connectors description:

• LAN – LAN and PoE IEEE 802.3af,
• RESET – Button used to enable DHCP, check the current IP address and restore the module to factory settings.

• OUTPUT – NO relay output,
• POWER – Additional power connector when PoE is unavailable. Power supply voltage: 12-24V DC.

Nano Out

Technical data

Dimensions

General characteristics

The module is equipped with LED indicators that indicate power supply and output state.

The following communication options are available:

• Built-in WWW server, available from a standard web browser (MOZILLA FIREFOX, OPERA, CHROME are the preferred browsers),
• Windows/Linux command line programs,
• HTTP GET,
• Modbus TCP,
• SNMP,
• Own application via TCP (shared protocol),
• Inveo MQTT protocol.

Module connectors description:

• LAN – LAN and Passive PoE,
• RESET – Button used to enable DHCP and restore the module to factory settings,
• OUTPUT – NO relay output.

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 disabled (enabled by default), the device needs to be configured by changing the computer's subnet:

To enable remote configuration:

1. Go to the Administration tab,
2. Select Enable Remote 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:

Network settings configuration

The Network tab allows the user to change LAN settings.

• 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,
• Gateway – Network gateway,
• Subnet Mask – IP subnet mask,
• DNS1, DNS2 – DNS addresses,
• Destination IP – IP address of the module, the input state should be routed to when using M2M communication,
• Destination Port – Port, on which the remote device is listening.

Security and services configuration

In Administration, active device services and access password can be selected and/or changed.

Changing the password:

To change the password, input the Current Password. Next, type in the new password into the New Password and Re-type Password fields. Apply the changes with Save Config. If you want to remove the password altogether, leave New Password empty.

Services settings:

The device allows selection of services that should be available. To activate the service, select the field next to its name.

• Enable Program Access – Enable access by external programs (Windows, Linux) and TCP/IP on port 9761,
• Enable Modbus TCP Protocol
• Enable SNMP
• Enable Destination Client – Forwarding of the input/output states to other modules,
• Enable MQTT Inveo – Activate MQTT protocol,
• Enable Remote Network Config – (Discoverer programme),
• Enable TFTP Bootloader.

Communication with a module from an external network

If the module is located in a different LAN, port forwarding is required. Depending on the communication method utilized, contact with the network administrator and forwarding of certain ports is needed.

WWW webpage and HTTP protocol:

• TCP port 80

Computer programme or own application:

• TCP port 9761

Modbus TCP:

• TCP port 502

SNMP protocol:

• UDP port 161

Checking the IP address

To check the current device IP address (Nano PoE only):

1. Press and hold the RESET button. The screen will display the four groups of an IP address in sequence: eg. 192 168 111 15..
2. After the full address is displayed, release the RESET button.

DHCP

To enable or disable DHCP support:

1. Press and hold the RESET button for a time between 5 and 10 seconds.
2. The LED will blink about 2 times per second (Nano), the display will show dhcp (Nano PoE).
3. Release the RESET button.
4. The current DHCP status will be displayed: On (enabled) or Off (disabled).

DHCP can also be enabled or disabled in the network settings. Access the Network tab or use the Discoverer programme.

Device functions

Input state preview

The primary function of Nano Relay Output is controlling a relay output. The current output channel and relay state can be viewed in the Home tab.

Output channel configuration

The output channel of Nano Relay Output can be configured in the Channel tab.

• Power on state – Defines the output state after the power is connected:
  • OFF – Channel inactive,
  • ON – Channel active,
  • LAST – The output channel assumes the state it had before power was disconnected,
• Invert – Enable output channel inversion.

Operating modes configuration

The built-in relay can operate in 3 modes:

• Bistable – The relay has a stable position (activated or deactivated).

• Astable – After the channel is activated, the relay closes and opens the contacts periodically. The activation and deactivation times are defined by the Time on and Time off parameters.

  

• TimeBased – Single trigger mode.

  • If ton>0 and toff>0, the relay will activate after toff time passes and will remain active for ton.

  

• If ton>0 and toff=0, the relay will activate for ton and will remain active.

• If ton=0 and toff>0, the relay will activate after toff passes.

Destination Client (M2M)

Inveo devices shuch as LanTick, Nano Temperature Sensor, Nano Digital Input, Nano Relay Output etc. can send the data to a server or other module equipped with outputs using TCP or UDP. Thanks to this, the remote module will react to channel activation and activate/deactivate relay outputs in real-time. The messages are sent after each change of state and every 5 seconds.

Configuration for receiving modules (target devices):

Step 1: Enable the service In Administration, select Enable Program access and Save config.

Configuration for messaging modules (output status):

Step 1: Enable Destination Client

In Administration, select Enable Destination Client and Save config to activate the service.

Step 2: Network settings

In the Network tab, fill in the fields:

• Destination IP – Target device or server IP address,
• Destination Port – Port, on which the remote device is listening. 9761 by default.

Step 3:

Go to the Channel tab and select the type of message to be sent. If using TCP and UDP, select the channel that will be controlled on the taget device.

The following options are available: - Off
- TCP Ch:x
- UDP Ch:x
- Status
- MAC+Status
- HTTP GET

TCP Ch:x and UDP CH:x

TCP Ch:x – This function uses the connection oriented protocol (TCP). Ch:x is the target output channel in the remote device (eg. LanTick) that will be controlled after the local device channel state changes. TCP frame format #1.

UDP Ch:x – Function uses the connectionless protocol (UDP). Ch:x is the target output channel in the remote device (eg. LanTick) that will be controlled after the local device channel state changes. UDP frame format #1.

The format #1 frame is sent in HEX form. Example TCP frame sent while Ch:1 is active:

Example TCP frame sent while Ch:1 is inactive.

CH determines the output channel in the target device that will be controlled when the channel state changes.

OUT_STATE – 01 - channel active, 00 - channel inactive.

Calculating CRC:

CRC = (SOF+CMD+CH+F_ID+OUT_STATE+!OUT_STATE+CNT0+CNT1+CNT2+CNT3) MOD 256

Format 1:

Status

Selection of this message type will cause the device to send its channel state. TCP frame format #2.

The format #2 frame is sent in the form of a character string.

<OUT_STATE>

• OUT_STATE – 01 - channel active, 00 - channel inactive.

Format 2:

MAC + Status

Selection of this message type will cause the module to send its MAC address and current channel state. TCP frame format #3.

The format #3 frame is sent in the form of a character string.

<MAC>[SPACE]<OUT_STATE>

• MAC – Module MAC address,
• OUT_STATE – 01 - channel active, 00 - channel inactive.

Format 3:

HTTP GET

The module sends its MAC address and channel state. Frame format #4.

Setting Client Mode to HTTP GET makes the device send data to the server in the following form:

nano.php?mac=<MAC>&io=<OUT_STATE>

• MAC – Module MAC address,
• OUT_STATE – 01 - channel active, 00 - channel inactive.

The TCP frame can be handled by own software.

To test the data transfer, go to Administration, select Enable Destination Client, and click Save Config.

In the Network tab, fill in the following fields:

• Destination IP – Computer's IP address,
• Destination Port – Port, on which the remote device is listening on (default 9761).

To test the TCP message type, select TCP Ch:x in the Channel tab. The next step is to run Inveo Discoverer and click TCP. Input the values from Network into the IP address and Port fields. Select HEX in Receive Data, then click Listen.

To test the UDP message type, select UDP Ch:x in the Channel tab. The next step is to run Inveo Discoverer and click UDP. Input the values from Network into the IP address and Port fields. Select HEX in Receive Data, then click Listen.

To test the Status and Mac+status message types, select Status or Mac+status in the Channel tab accordingly. The next step is to run Inveo Discoverer and click TCP. Input the values from Network into the IP address and Port fields. Select STRING in Receive Data, then click Listen.

To test the HTTP message type, select HTTP in the Channel tab. The next step is to run Inveo Discoverer and click HTTP. Input the values from Network into the IP address and Port fields, then click Listen.

SNMP configuration

Nano Digital Output is equipped with an SNMP v2c server, making remote readout of input state possible. To Enable SNMP, go to the Administration tab.

Configuration options are located in the SNMP tab:

SNMP allows readout of current module output state. To use this function, download the MIB file (describing the data structure) first. To do that, right-click Download MIB file and select Save link as. Import the downloaded MIB file into the MIB Browser programme.

The basic parameters that can be read from the module are displayed in the following table:

The module also has the ability to send TRAP notifications if the output channel state changes. To configure the destination addresses for those notifications, input them into Trap IP Address 1 and Trap IP Address 2.

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>Nano Out</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.0</temp1>
</response>

Linux control programme

cURL can be used in Linux:

curl "http://192.168.111.15/temp1.txt" -w "\n"

The device will respond identically as it would to a Windows command – see above.

Modbus TCP

To activate the function of sending data using Modbus TCP protocol, select Enable Modbus TCP protocol in the Administration tab.

Modbus is available via the LAN connector.

Modbus TCP listens on 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

Coils addressing

Holding Registers addressing

MQTT

The device supports MQTT protocol. Data from the device is sent to the server every minute and after each value change. The data is not encrypted. The user subscribes the device data after connecting with the broker. The amount of users that can receive the data from a single device is unlimited.

In addition to the default Inveo MQTT broker, the user can specify their own MQTT server for relay output state monitoring purposes.

Configuration:

Firstly, Enable MQTT Inveo in Administration. In the Network tab, MQTT broker address and port can be configured:

In the Administration tab, after clicking Show info for Enable MQTT Inveo, MQTT client settings that will be needed for launching the application will be displayed:

It's possible to control the output using the MQTT protocol. To do that, select Enable MQTT output control. To control the output, use the device's topic modified with /nosec (inserted before the topic), and /s (inserted after /nanoO).

The output can be controlled using commands sent to an appropriate topic:

• 1 (activate output),
• 0 (deactivate output).

HTTP GET

The modules can be controlled using the HTTP GET protocol. To read the current module state, recall the resource using a web browser eg. http://192.168.111.15/status.xml

The module will display all important information in the form of an XML file:

<response>
<prod_name>Nano-1-0</prod_name>
<sv>1.21</sv>
<mac>00:00:00:00:00:00</mac>
<out>00000001</out>
<on>00000001</on>
<in>00000000</in>
<counter1>0</counter1>
<temp1>0.0</temp1>
</response>

HTTP GET module control examples:

1. Activate relay output:
   http://192.168.111.15/stat.php?on=1

2. Invert relay output state:
   http://192.168.111.15/stat.php?inv=1

3. Deactivate relay output:
   http://192.168.111.15/stat.php?off=1

cURL data readout example:

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

Read module name:
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}'

Activate/deactivate the output channel:
curl -u admin:admin00 "http://192.168.111.15/stat.php?on=1"
curl -u admin:admin00 "http://192.168.111.15/stat.php?off=1"

TCP/UDP/IP

Data frame for TCP/UDP port 9761:

** Chx returns 2 bytes: - 1 – Output state, - 2 – Coil state.

Set output to astable mode with Ton=Toff=1.7 seconds.

Save settings to EEPROM.

Factory settings

Restoring factory settings

To restore the factory settings:

• Power up the device,
• Press the RESET button for a time period between 10 and 15 seconds,
• The TAG LED will start flashing about 4 times a second (Nano, Nano RFID PoE), rSt will appear on the display (Nano In/Out/Temp PoE),
• Release the RESET button.

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

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.