Nexmosphere XN-135M3 User manual

Xperience platform
All of Nexmosphere’s controllers are built on the same platform principles. If this is your rst time using a Nexmosphere
controller, we recommend to rst read https://nexmosphere.com/technology/xperience-platform/ to learn the basics about
our platform and its terminology.
XN-135M3
The XN-135M3 is an Xperience controller with 2 X-talk interfaces and
1 presence sensor interface:
1. X-talk interface 001
2. X-talk interface 002
3. Presence sensor interface (X-talk address 003)
USB. 5V Power input and API interface (micro-USB connector)
LED. White status LED
Hardware setup
1. Connect one or more Elements to any of the 2 X-talk interfaces. Connect an IR presence sensor to its dedicated interface.*
2. Connect the micro-USB cable to a 3rd party device (e.g. Digital Signage Player or PC).
3. Wait until the white status LED stops blinking. This lasts about 5 seconds.
*Make sure the IR sensor matches the Controller and sensor cable: XN-135M31 matches with sensor S-CM01 and cable CA3-S..C,
XN-135M34 matches with sensor S-CM04 and cable CA3-S..C, XN-135M37 matches with sensor S-CM07 and cable CA3-54C.
Software setup for testing (Terminal)
Typically, the XN-135M3 controller is connected to a 3rd party device, such as a Digital Signage Player, on which CMS software is installed that has built-in
functionality for sending and receiving Serial Events. However, if you want to do a rst test on a PC or Mac, follow the instructions below:
1. Download a terminal program. For example Termite or Hercules.
2. Open the Terminal program and go to settings. Choose the COM port on which the XN-135 controller enumerated*.
In most cases this is the highest available number in the COM port drop-down setting.
3. Set the COM port settings to the following values
Baudrate 115200 Flow Control None
Parity None EOL CR+LF
Data Bits 8 Protocol ASCII
Stop Bits 1
4. Set the COM port to “Open”. The controller is now ready for use.
5. When sending consecutive API serial commands to the XN-135M3 controller, place a 50mS delay between each command.
*In case the XN-135M3 controller is not recognized as a COM port by the 3rd party device, a driver (Prolic PL2303) can be downloaded here.
Functionality
The XN-135M3 runs our API which provides serial output when a specic sensor Element is triggered (for example a pick-up,
or -motion sensor or touch button) and provides control over output Elements (for example controlling LED strips) via serial
input commands. These API serial commands are typically used to create interactive Xperiences for Digital Signage.
The complete API Manual and additional helpful documents can be found on https://nexmosphere.com/support-
documentation. To get you started, we’ve included some starter examples of our Elements and the corresponding API serial
commands on the following pages.
3rd party devices and software
This Quick Start Guide oers a generic explanation of the setup and operation of the XN-135M3 Xperience controller. It
does not cover information on how to integrate the Controllers, Elements and their API triggers in specic 3rd party devices
or software. We have manuals available with step-by-step instructions on how to integrate Nexmosphere products with the
products of our hardware, -and software partners. You’ll nd these on the support and partner pages of our website.
Nexmosphere
High Tech Campus 10 (Mμ building)
5656 AE Eindhoven • The Netherlands
T [phone]
[e-mail]
QUICK START GUIDE

© 2020 Nexmosphere. All rights reserved. v1.0 / 04-20
All content contained herein is subject to change without prior notice.
1
XN
XN
001 002 003
003
004
008 007 006 005
001 002
1 2
3
USB
LED

© 2020 Nexmosphere. All rights reserved. v1.0 / 04-20
All content contained herein is subject to change without prior notice.
Nexmosphere
High Tech Campus 10 (Mμ building)
5656 AE Eindhoven • The Netherlands
T [phone]
[e-mail]
2


When a presence sensor connected to the presence
sensor interface (X-talk interface 003) detects a person in
distance zone 4, the following API serial command is sent
from the XN-135M3 to the 3rd party device: X003A[4]
When a presence sensor connected to the presence
sensor interface (X-talk interface 003) does not detect a
person, the following API serial command is sent from the
XN-135M3 to the 3rd party device: X003A[1]

When tag 2 is picked up from an antenna connected to
X-talk interface 001 the following API serial commands are
sent from the XN-135M3 to the 3rd party device:
XR[PU002]
X001A[1]
When tag 1 is placed on an antenna connected to X-talk
interface 001, the following API serial commands are sent
from the XN-135M3 to the 3rd party device:
XR[PB001]
X001A[1]

When button 1 of a (touch) button interface connected
to X-talk interface 002 is pressed, the following API serial
commands are sent from the XN-135M3 to the 3rd party
device: X002A[3]
When button 4 of a (touch) button interface connected
to X-talk interface 002 is pressed, the following API serial
commands are sent from the XN-135M3 to the 3rd party
device: X002A[17]
XN-135M3
(Xperience controller)
USB-A to Micro-USB cable
(connect to 3rd party device)
XR
XR-C10
(RFID antenna)
XR-C10
RFID Tags
(number 1-3)
XR-DR1
(RFID antenna driver
XN
XN-135M3
(Xperience controller)
USB-A to Micro-USB cable
(connect to 3rd party device)
XT-B4N
(4x buon interface)
XT-4F
(Touch buons)
Push buons
(with LED, 4x)
XT-B4
1 2 3 4
XN
XN-135M34
(Xperience controller)
USB-A to Micro-USB cable
(connect to 3rd party device)
XN
S-CM04
(presence sensor)

© 2020 Nexmosphere. All rights reserved. v1.0 / 04-20
All content contained herein is subject to change without prior notice.
Nexmosphere
High Tech Campus 10 (Mμ building)
5656 AE Eindhoven • The Netherlands
T [phone]
[e-mail]
3


To set all button LEDs of a (touch) button interface
connected to X-talk interface 002 to “on”, send the
following API commands from the 3rd party device to the
XN-135M3 controller:

To initiate an X-Wave LED pattern on an X-Wave connected
to X-talk interface 002, send one of the following API
example commands from the 3rd party device to the XN-
135M3 controller:

The XN-135M3 Xperience controller has 2 X-talk interfaces and 1 presence sensor interface to which any combination
of Elements can be connected. For example, three of the examples in this Quick Start Guide can be combined on a single
XN-135M3. The API commands and operation will remain the same. When connecting multiple Elements that require
a high amount of current (LEDs or push buttons with LED ring), calculate the total required current of the Elements and
check if this is within the specication of the controller and its power supply source.
To set all button LEDs of a (touch) button interface
connected to X-talk interface 002 to “o”, send the
following API commands from the 3rd party device to the
XN-135M3 controller:
40% brightness, color 0 (white), 0.5 second ramp time
Blue pulsing pattern (99% to 20%), 1.8 second ramp time
White wave pattern moving to the left
X002A[255]
X002B[240005]
X002B[399C1801020C180018]
X002B[499018001200009]
X002A[0]
XN-135M3
(Xperience controller)
USB-A to Micro-USB cable
(connect to 3rd party device)
XT-B4N
(4x buon interface)
XT-4F
(Touch buons)
Push buons
(with LED, 4x)
XT-B4
1 2 3 4
XN
XN-135M3
(Xperience controller)
USB-A to Micro-USB cable
(connect to 3rd party device)
XW-L96
(X-Wave LED)
XW-L9
XN
XN-135M34
(Xperience controller)
USB-A to Micro-USB cable
(connect to 3rd party device)
XW-L96
(X-Wave LED)
XW-L9
XN
S-CM04
(presence sensor)
XR XR-C10
(RFID antenna)
XR-C10
RFID Tags
(number 1-3)
XR-DR1
(RFID antenna driver