TM4000 Series

TinymeshTM Transceiver Plug-In Boards

Product Description
The TM4000 Series Transceiver plug-in boards are compact, high
performance plug-in boards for wireless networking applications.
The plug-in boards are ready to go, with on board antenna,
embedded Tinymesh™ application and selectable Point to Point or
multi-hop protocol stack with automatic network forming and self-
healing features. The embedded Tinymesh™ application layer
supports a full duplex UART, Analogue, Pulse and Digital inputs, as
well as PWM and Digital outputs.

Typical Applications
• Wireless Sensor Networks
• Automatic Meter Reading
• Alarm and Security Systems
• Building Management
• Telemetry Stations
• Fleet Management
• Asset Tracking
• Street Light Control and Monitoring

Key Features
• Embedded application layer for I/O control and data collection
• Self-forming, self-healing and self-optimizing bi-directional Tinymesh network stack or cost
optimized point to point stack versions.
• AES 128 encryption
• Selectable Gateway, Router and low power End Device configuration
• Configurable digital I/O, PWM (Dimmer) output and analogue inputs
• Full Duplex Serial Port with handshake, streaming support and 256 byte buffer for easy
RS232/422/485 wire replacement and MODBUS RTU compatibility
• Pulse counter with configurable de-bounce time and detection feedback output
• 'Walk-by' mode for low power data logging and metering applications
• RSSI and Network connect LED output control for simplified field installation
• Group, Broadcast or Individual addressing modes
• Clustered Node Detection and Network Congestion Avoidance (CND/NCA™)
• RF Jamming Detection and Alarm, with alarm output and network alarm messaging
• Analogue and Digital level triggered event messages.
• Time generated and event triggered status messages
• Locator Function for asset tracking applications
• Network Busy Detection for ad hoc networks with multiple, roaming Gateway Devices
• Multiple Gateway support for redundancy and automatic network load sharing
• No external components
• Wide supply voltage range
• TM4080 conforms with EU R&TTE directive (EN 300 220, EN 301 489, EN 60950)
• TM4090 conforms to regulations for operation under FCC CFR 47 part 15
• TM4070 complies with G.S.R.564(E) (G.S.R.168(E)).
• TM4070 complies to IEEE 802.15.4.g PHY mode 0 encoding when configured for RF Data Rate 8.

Ó2018 Tiny Mesh AS TM4000 Series Data Sheet V1.8 Page 1 of 59

 TM4000 Series
Quick Reference Data
Plug-in board version TM4070 TM4080 TM4090
Parameter Unit
Frequency 865 – 867 868 – 870 902 – 927 MHz
Channels 15 18 50
Data rate 1.2 – 100 1.2 – 100 1.2 – 250 kbit/s
Max TX power 11 11 11 dBm
Sensitivity @ 1.2/ 100 kbit/s -110 / -97 -110 / -97 -110 / -97 dBm
Supply voltage 2.0 – 3.6 2.0 – 3.6 2.0 – 3.6 Volt
RX/ TX Current 24 / 37 24 / 37 24 / 37 mA
SLEEP Current 0.3 0.3 0.3 uA
Temp. range -40 to +85 -40 to +85 -40 to +85 C

Tinymesh Product Family and Ordering Codes

A four-digit product ID preceded by TM is used as a short form for product presentations and
marketing materials.
For orders and logistics purposes, the product ID will be superseded with three additional digits and
an optional letter, describing the Board form factor, configuration, pin out sequence and packaging
type

Digit/letter Designation
1 Product Family 4: Tinymesh plug in board
2 Protocol 0: Tinymesh
1: Point to Point
3 Frequency 7: 865 MHz
8: 868 MHz
9: 920 MHz
4 Front End 0: LP
5 Board format 0: Full size (all I/O ports)
2: Compact (UART, limited I/O)
6 Board 0: Fully populated, including LEDs and Configuration
Configuration switch
1: Optimized, no LEDs, No Config switch
9: Custom
7 Pin-out 0: Default, as per Data Sheet
8 Packaging None: Anti-static wrapping, 250 pcs per pack
S: Anti-static wrapping, 10 pcs per pack
Example: TM4070-000S (Tinymesh Board, Tinymesh protocol, 865MHz, LP front end, Full Size Board,
Fully Populated, Default Pin Out, 10 pcs per pack)

Typical Application Circuit

VCC, GND, UART, 8 GPIO, PWM, VCC, GND, UART,

Analogue, Pulse 2 GPIO I/O

Ó2018 Tiny Mesh AS TM4000 Series Data Sheet V1.8 Page 2 of 59

 TM4000 Series
Table of Contents
Product Description 1
Typical Applications 1
Key Features 1
Quick Reference Data 2
Tinymesh Product Family and Ordering Codes 2
Typical Application Circuit 2
Table of Contents 2
Tinymesh™ Application and Protocol Stack 5
Tinymesh™ Devices 5
Gateway Device 5
Router Device 5
End Device 6
Data Integrity 6
Network Formation 6
Self-healing 6
Self-optimizing 6
Network Addressing 7
Multiple Gateway Support 7
Ad Hoc Networks and Hand Held Gateway Devices 7
Alerts and Device Triggered Events 8
Over the Air Configuration 8
Getting Started 9
Transmitting Serial Data 9
Forming a Network 9
What about the Antenna? 10
How do I change the RF Channel or any other Parameter? 10
Pin Assignment 11
Pin Description 11
Mechanical Dimensions 12
Mounting Recommendations 13
TM4xxx-2x0 13
TM4xxx-0x0 13
Circuit Description 14
Transparent Mode Operation 15
Transparent versus Packet Mode Operation 15
Transparent and Packet Mode Functions 16
Serial Data Streaming 16
Serial Port Handshake 16
AES Encryption 17
Coexistence with AES Encrypted and Unencrypted Devices 17
Sleep Mode 18
RF Jamming Detection and Alarm 18
RF Jamming Detection in Packet Mode Systems 19
Clustered Node Detection and Network Congestion Avoidance (CND/NCA™) 19
Optimizing Polled Systems 19
LED Indicators 20
LED Indicator Timeout 20
Pulse Counter Feedback Indicator 20
RSSI Indicator LED 20
Connection Indicator LED 21
Radio RX /TX Indicator LED 21
Configuration mode indicator 21
Packet Mode Operation 22
Gateway in Packet Mode 22
Router in Packet Mode 22
Transmitting Command and Configuration Packets from Gateway 22
Group and Broadcast Addressing 22
Command Acknowledge 23
Command Packet Format 23
Command String Examples 24
Transmit Serial Data Packet from Gateway 24
Received Packet Formats 24

Ó2018 Tiny Mesh AS TM4000 Series Data Sheet V1.8 Page 3 of 59

 TM4000 Series
Practical Use of Packet Header Data 27
Device and Network Status Interrogation 27
Serial Data Block Counter 28
Locator Function 28
Network Busy Detection 28
Network ID 29
IMA On Connect Function 29
Automatic Status Reporting 29
Receive Neighbour Function 30
Input / Output Functions 31
Digital Input 31
Digital Input De-bouncing 31
Digital Input ‘Trig Hold’ 31
Pulse Counter 31
Pulse Counter De-bounce 32
Pulse Count Verification 32
Digital Output Control 33
Digital Output Drive 34
PWM (Dimmer) Output 34
Analogue Input 34
Analogue Input Event Triggering 35
Setting the Analogue Input Trigger Level 35
Setting the Analogue Input Sampling Interval. 35
End Device 36
Wake Up from Pulse Counter 36
Wake Up from Digital Input 37
Wake Up from Serial Port UART 37
Wake Up from IMA Timer 37
Battery Lifetime Considerations 37
Analogue Port Sampling by End Devices 38
Device Awake Output Function 38
Fixed Destination and “Walk By” Mode 38
RF Frequencies, Output Power and Data Rates 39
Device Configuration 41
Configuration Commands 41
Configuration Mode Entry 41
Configuration Mode commands 42
RSSI Reading (S- Command) 43
Temperature Reading (U- Command) 43
Power Supply Voltage Reading (V- Command) 43
Set Configuration Memory (M- Command) 44
Set Sleep Mode (Z-Command) 44
Alternate Set Sleep Mode (z-Command) 44
Setting and Changing the AES key (K7- Command) 44
Change Calibration Memory Command (HW- Command) 45
Calibrating the Temperature Sensor 45
Setting and Changing the Network ID (NID) 46
Setting and Changing the Fixed Destination ID (FDID) 46
RSSI Sniffer (Test Mode 5) 47
Simple Packet Sniffer (Test Mode 6) 47
Configuration Memory 49
Calibration Memory 54
Absolute Maximum Ratings 55
Electrical Specifications 55
Regulatory Compliance Information 57
R&TTE directive (EU) 57
WPC Compliance (India) 57
Regulatory Compliance Disclaimer 57
Document Revision History 58
Product Status and Definitions 58
Disclaimer 58
Trademarks 58
Life Support Policy 59
Contact Information 59

Ó2018 Tiny Mesh AS TM4000 Series Data Sheet V1.8 Page 4 of 59

 TM4000 Series
Tinymesh™ Application and Protocol Stack
The Tinymesh™ Multi-hop Wireless Mesh Network Protocol Stack is a unique set of multi-hop wireless
mesh network protocols that enable devices to send messages or transfer data to and from each
other. The embedded Application Layer contains an advanced set of configurable I/O handling
mechanisms that enable Tinymesh™ devices to be implemented in most application circuits without
need for an external MCU.
The Tinymesh™ Stack requires no external processor for establishing and maintaining the optimum
network routing path.
Internet applications may connect to Tinymesh™ Wireless Mesh Network through the equally
uncomplicated Tinymesh™ Cloud Services.

Tinymesh™ Multi hop Wireless Mesh Networks may consist of large numbers of Tinymesh™ enabled
devices or nodes where a node is one out of three types as described below. The wireless traffic
between the Tinymesh™ enabled devices follows a tree type topology, where data transfer is up or
down in the tree structure.

A Tinymesh™ Multi hop Wireless Mesh Network in its simplest form consists of a single Gateway and a
Router. End Devices will not perform packet routing and must connect to a Router or directly to a
Gateway. A network may be comprised of thousands of Tinymesh™ enabled devices. There may be
several Gateway devices within a network, for redundancy and automatic workload sharing.
The network addressing structure uses four-byte addressing, for a total of 4.3 billion possible unique
devices per network. The network tree structure may have a total depth 255 hops.

Tinymesh™ Devices
Any Tinymesh™ enabled device may be configured to function as Gateway, a Router or as an End
Device. Single byte configuration commands will set all relevant configuration parameters when
changing operating mode.

Gateway Device
A Tinymesh™ network must have at least one Gateway Device. The Gateway Device initiates the
network formation, and is required to keep the network alive. Gateway Devices provide the
connection between the Tinymesh™ Routers and End Devices, and an external host processor, or to a
local- or wide area network, such as the Internet.
The Tinymesh™ stack supports implementations with multiple Gateways, where additional Gateway
devices provide redundancy and data traffic load sharing.
Gateway devices support full Input / Output control capabilities, similar to Routers and End Devices.

Router Device
Router Devices are full functioning devices with serial data UART and Input / Output capabilities.
Router Devices provide the communication path between individual Router or End Devices, and the
network Gateway.
Router devices must always be powered, to support routing of packets received from other devices.

Ó2018 Tiny Mesh AS TM4000 Series Data Sheet V1.8 Page 5 of 59

 TM4000 Series

End Device
A Tinymesh™END DEVICE will normally be in low power sleep mode for battery operation. End Devices
have full input and output control capabilities, but will not accept messages for redistribution from
other devices.
An End Device will wake up to full power mode by external stimuli, such as a digital input level shift,
serial data input, pulse counter activity or by internal clock. Wakeup conditions are selectable
through configuration settings. After waking up, the End Device will generate an Event Message or a
Serial in Message, depending on the wake up condition. After delivering the message, the End Device
will either return directly to sleep condition, or stay awake for a settable time, to wait for response
commands from a server or application outside the Tinymesh™ network.

Data Integrity
The Tinymesh™ stack uses several mechanisms to ensure safe and reliable data delivery with minimal
latency.
• Listen Before Talk in accordance with the harmonized EN 300 220-2 standard, to reduce
likelihood of RF traffic collision.
• Link level acknowledge on all packet deliveries for positive confirmation of data reception.
• Packet retransmission on missing acknowledge
• Format, data validity and CRC control check on packet reception
• AES 128 encryption
• Packet duplicate check
• Housekeeping mechanisms to eliminate stray packets that are either too old or have hopped
to many times
• Unique numbering of packets to allow duplicate and sequence control by external
applications
• Application level command acknowledge to verify and validate command reception.
• Unique timing mechanisms to handle network congestion

Network Formation
A Tinymesh™ Multi hop Wireless Mesh Network is self-forming, created by Gateway units starting to
invite Routers and End Devices within RF range to join in the network. A Router joins the network
after verifying the invitation, and immediately starts inviting new nodes to join. Within seconds of
powering up the Gateway, a large network may be created automatically.
Gateway and connected Router devices send periodic beacon packets to indicate presence and
availability for connection. Tinymesh™ beacon packets, referenced as HIAM packets, contain
information of device address (UID), System Identity (SID), Radio Frequency Channel and device
Network Level (Hop Level).
Routers and End Devices receive and evaluate connection alternatives by comparing hop level- and
received signal strength of HIAM packets on selectable time intervals (Connect Check Time)

Self-healing
Devices in Tinymesh™ networks continuously evaluate alternate connections by comparing the hop
level and signal strength of received HIAM packets. In cases where the primary communication link
becomes unresponsive, the device will automatically change to the alternate routing if such routing is
available.
If the alternate routing is also unresponsive, the device will enter a state where it searches for new
routing possibilities.
Data received by the device, and event data generated by the device will be stored in the internal
device buffers until a valid connection has been established.

Self-optimizing
The communication path offering the least number of hops and the highest link quality is always
selected as the primary connection for data delivery. A network optimization process runs
continuously as a background task in all Tinymesh™ devices.

Ó2018 Tiny Mesh AS TM4000 Series Data Sheet V1.8 Page 6 of 59

 TM4000 Series
In changing environments with changing link quality, Tinymesh™ networks dynamically adapt to find
optimum routing.

Network Addressing
Tinymesh™ networks utilize a flexible addressing scheme with 4 bytes System address (SID) and 4
bytes for unique device addressing (UID).

The four byte System ID identifies a local network in the same way as a PAN address. All devices in a
local mesh must share the same four-byte SID.

Every Gateway, Router, and End Device belonging to a local mesh network must have unique UIDs.
Duplicate UIDs will cause network instability, lost packets and connection issues.

A separate 4 byte Network Address is applied to uniquely distinguish local mesh networks sharing a
common platform in a cloud, or server controlled environment where local mesh networks may be
deployed with similar SID.

The Tinymesh™ Stack supports unique, group and broadcast addressing of individual devices. Routers
and End Devices may be assigned to addressing groups, by entering up to eight different single-byte
group identifier addresses.

Multiple Gateway Support

Tinymesh™ networks support multiple Gateway devices operating within the same local mesh. In mesh
networks with a single Gateway, the Gateway becomes a critical point for system reliability. In a
Tinymesh™ network, additional Gateways may be added at any point in time to provide redundancy
on the Gateway level.
Adding Gateway devices to a local mesh also improves data throughput and network capacity, as the
additional Gateway devices will automatically load share the upstream data traffic from for instance
a large data collection or sensor network.

Systems with multiple gateways must be controlled by a common server or cloud platform, such as
Tinymesh™ Cloud Services. Data originating from Router or End Devices will automatically be routed
through the mesh to the Gateway device that provides the least number of hops and the best signal
strength. If two or more Gateway devices offer the same number of hops and equally good signal
strength, for instance if the two Gateway devices are located near to each other, the packet will be
delivered to the Gateway device that is currently available. The server platform will use the device
UID to identify the packet origin, and the packet number contained in the packet header to verify
uniqueness.

Commands (downstream data traffic) in multiple Gateway systems should as a rule be entered to all
Gateway devices, to ensure reliable delivery.
Systems where the Gateway devices are located close by each other, offer an exception to this rule.
This will be systems where two or more Gateway devices provide redundancy and added throughput,
and where the distance between the individual Gateway devices is less than the distance to the
closest Router device. A single Gateway may be selected to dispatch commands in such
configurations.

Ad Hoc Networks and Hand Held Gateway Devices

Local mesh systems that are created ‘ad hoc’ by turning on a portable Gateway device such as a
portable CMRI used for data collection in automated metering systems will be formed as a web with
the portable Gateway in the centre of the mesh network.
Because there is no fixed rule to where a Gateway device is located, or when the mesh is created,
there needs to be mechanisms in place to ensure there is only one Gateway device downloading from
the mesh at a given time.
A configurable parameter in a Tinymesh™ Gateway device provides a mechanism for the Gateway to
detect if a network is already present when the portable Gateway is powered up. Depending on the
device configuration, the Gateway device will either refuse connection, provide an alert, or ignore
the presence of the other Gateway that is controlling the mesh.

Ó2018 Tiny Mesh AS TM4000 Series Data Sheet V1.8 Page 7 of 59

 TM4000 Series
If a portable Gateway device is configured to ignore the presence of an existing mesh, a portable
device may be used to temporarily connect to a device that is already connected to a stationary
Gateway device. This function could be used in automatic metering systems with permanently
installed data collection units (DCU), for individual interrogation or downloading of data directly to a
portable device.
The portable device must share the same System ID as the permanent Gateway, and must have unique
UID. When turning on the portable device, the portable Gateway will connect to the closest Router
devices and act as a secondary gateway in the system.
The portable device may interrogate the connected mesh to detect which Router devices have made
connection.
After switching off the portable device, the mesh will automatically reconfigure with the permanent
DCU as the preferred Gateway.

Alerts and Device Triggered Events

The application layer in the Tinymesh™ stack supports automatic alerts and triggered events from
multiple, configurable sources, eliminating the need for traditional status polling as known from
wired multidrop systems.

• Timer triggered status reporting, with time intervals from seconds to days
• Digital input status change, with configurable de-bounce and edge detection
• Analogue level change, with configurable hysteresis, trigger conditions and sample interval
• Power On detection
• Serial data input
• Radio Frequency Jamming detection

Over the Air Configuration

Gateway, Router, and End devices may be reconfigured at any time, even after system deployment.
The flexible format configuration command allows setting of any addressable location in the device
configuration memory.
Remote reconfiguration capability is a valuable feature for system maintenance and service. Any
configurable function, from changing the de-bounce time for digital input detection, to altering the
radio frequency channel may be changed over the air.
A special two step mechanism protects the most sensitive configuration parameters that may cause a
device to lose network connection.

Ó2018 Tiny Mesh AS TM4000 Series Data Sheet V1.8 Page 8 of 59

 TM4000 Series
Getting Started
A simple Tinymesh™ network may be formed by configuring at least one plug-in board as a Gateway
(SET GATEWAY MODE command).

Make sure the Gateway and all Routers have different Unique ID, but same System ID. This is
mandatory for successful self-forming of the network.
Plug-in boards are delivered with default setting 'Router', and with non identical Unique IDs.

Transmitting Serial Data

By default, Gateway Devices are configured to transmit serial data in Transparent Mode, for
transmission of unformatted, binary data.
Send your data to the RXD pin on the plug-in board. Use the UART format with default settings
(19200, 8, 1, N, no flow control). Up to 256 payload bytes are buffered. The data will be transmitted
when
• the serial buffer is full (256 bytes)
• the SERIAL PORT TIME OUT is reached (default 20 ms)
Plug-in boards will by default use the UART CTS signal to indicate when data may be entered. A low
CTS indicates the serial buffer is ready to receive data. A high CTS signal indicates the serial buffer is
unavailable, and data entered to the UART will be ignored.
After successful connection to a network and delivery of the current contents of the UART buffer, CTS
will go low, indicating the node is ready to receive data. CTS will remain low until the data buffer is
full, or a byte-to-byte time out has occurred. CTS will then go high, indicating no more data may be
entered. As soon as the data packet has been successfully transmitted and the data buffer is emptied,
CTS will return low, to indicate new data may be entered.
Data may be entered in binary format, any byte value with proper start- and stop bit is accepted. The
timeout limit is configurable in-circuit by changing the SERIAL PORT TIME OUT parameter in
Configuration memory. Default setting is 20 ms.

Any data entered at the Gateway (while CTS is low), will be delivered to all Routers that are
connected to the network. Received RF data with correct check sum will be presented on the TXD pin
of all Router(s).
Data entered at any Router Device (while CTS is low), will be delivered to the Gateway and presented
on the Gateway TXD pin.

Forming a Network
Nodes In a network may be powered up in random sequence. The Gateway Device starts inviting
neighbouring nodes to become members of the network. The Gateway Device will flash the red LED
every time a network invite beacon (HIAM) is transmitted.
The yellow LED on nodes configured as Router devices n) will start flashing in a slow pattern,
indicating the node is alive and listening, but not connected to the network.

Router devices within acceptable radio range of the Gateway, will detect the invite beacons from the
Gateway. If the received signal strength (RSSI) is within predetermined limits of acceptable signal
strength, the Router Device will attempt connecting to the Gateway by sending an invite response. If
the Gateway properly accepts the invite response, the Router has successfully joined the network,
and will signal its new status by changing the LED flash pattern. The red RSSI Indicator LED now
reflects the RSSI level of the established connection, and the yellow LED indicator starts flashing to
indicate successful connection.
All Routers that successfully connect to the network will immediately start inviting new Routers to
join the network, forming the next level of connected nodes. New Routers will again start inviting the
next level of Routers, automatically propagating the network to encompass all Routers with identical
System ID that are within radio range of at least one other Router or Gateway in the same network.
No external processing effort in the terms of a network organizer, controller PC or micro controller is
required, as each node actively and autonomously participates in the forming of the RF network.

Ó2018 Tiny Mesh AS TM4000 Series Data Sheet V1.8 Page 9 of 59

 TM4000 Series
What about the Antenna?
TM4000 Series plug-in boards come preconfigured with a matched, on board PCB antenna and will in
most cases not need external antenna connection.

How do I change the RF Channel or any other Parameter?

Configurable parameters such as RF Channel, RF Power or RF Data Rate, are stored in non-volatile
memory. There are principally two different ways for changing these parameters. The plug-in board
must either be entered into CONFIGURATION MODE, for direct input of new parameters on the serial
port, or new parameter values may be dispatched to a plug-in board in a live mesh network by issuing
the SET CONFIGURATION command.
Please see DEVICE CONFIGURATION for details.

Ó2018 Tiny Mesh AS TM4000 Series Data Sheet V1.8 Page 10 of 59

 TM4000 Series
Pin Assignment

TM 4xxx-0x0 TM 4xxx-2x0

Pin Description
Pin name Pin no Pin type Description Equivalent circuit
4xxx- 4xxx-
0x0 2x0
VCC 1,11 3 Supply voltage input. Internally
regulated

GND 2,17 4 System ground

RESET 3 9 Input Main reset (active low). Should

normally be left open

Pulse 4 N/A Digital Pulse counter input with With Pull Up Without Pull Up
Input selectable pull-up. Counting on
Hi-Low transition

GPIO 6 5 N/A
Individually configurable as
GPIO 7 6 N/A Digital Input or Output
GPIO 5 7 N/A
Digital In / GPIO7 Configurable as PWM
GPIO 4 8 NA Out output

RSSI/ TX LED 9 1 Output Direct LED drive output.

Flash pattern given for current
sourcing:
Flash frequency indicates
network connection RSSI level
for Routers and End Devices.
Flash indicates RF TX activity
for Gateway Devices.
Connection/ RX 10 2 Output Direct LED drive output.
LED Flash pattern given for current
sourcing:
Flash frequency indicates
network connection
redundancy for Routers and
End Devices.
Flash indicates RF RX (received
packets) for Gateway Devices
CTS / RXTX 12 6 Output UART CTS or RTX Active Low See Pin 4-8
RTS / SLEEP 13 5 Input UART RTS or Sleep See Pin 4-8

Ó2018 Tiny Mesh AS TM4000 Series Data Sheet V1.8 Page 11 of 59

 TM4000 Series
CONFIG 14 10 Input Configuration Enable. Active See Pin 4-8
low. Should normally be set
high
TXD 15 8 Output UART TX Data See Pin 4-8
RXD 16 7 Input UART RX Data. See Pin 4-8
GPIO 3/ DD* 18 11* Digital In / Configurable as Digital input or See Pin 4-8
out Output
GPIO 2/ DC* 19 12*
GPIO 1 20 N/A Digital In / Individually configurable as When Configured as Digital In /Out,
out Digital Input or Output or as see Pin 4-8
GPIO 0 21 N/A or Analogue input
Analogue When Configured as Analogue In:
In

* Pins 11 and 12 used for 4xxx-2x0 device programming

Mechanical Dimensions

55

5.7

33

27.5 +/- 0.5

16.5

2.09
2.54

35.6
5.7

22

3.6 +/- 0.5

16.5
2.09

2.54

Ó2018 Tiny Mesh AS TM4000 Series Data Sheet V1.8 Page 12 of 59

 TM4000 Series
Mounting Recommendations
Tinymesh plug in boards may be assembled in horizontal or vertical mode.

For optimum performance, consideration must be given to the layout of the mother board ground
plane, which will as a counter poise to the on-board antenna, and sufficient distance must be allowed
around the antenna, to allow the antenna to radiate freely.

TM4xxx-2x0
Horizontal mount Vertical mount

Keep off area

for ground plane Antenna counter poise
and trace Antenna counter poise
ground plane in mother
routing. ground plane in mother
Keep off area for board top layer.
board top layer
ground plane and
trace routing.

Minimum 15 mm
each side and Minimum 20mm each
10mm in extension side and 10mm in
of the antenna extension of the plug-in
Minimum 10mm each
Minimum 15 mm board
side of the plug-in board
each side of the
antenna

PCB Motherboard

TM4xxx-0x0

Horizontal mount

Keep off area for ground plane and trace routing.

Minimum 15 mm each side of the antenna trace.

Antenna counter poise ground plane in the mother board

top layer. Minimum 10mm each side of the plug-in board.

Vertical mount

Antenna counter poise ground plan in the mother board

top layer. Minimum 10mm each side of the plug-in board.

PCB Motherboard

Ó2018 Tiny Mesh AS TM4000 Series Data Sheet V1.8 Page 13 of 59

 TM4000 Series
Circuit Description
The Tinymesh™ plug-in board contains a communications controller with embedded Tinymesh™
protocol stack firmware, a high performance RF transceiver with antenna, AES Encryption Engine,
ADC, I/O Controller and internal voltage regulator.
The communications controller handles the radio packet protocol, the UART interface and controls
the RF transceiver. Data to be sent by the host is received at the RXD pin and buffered in the
communications controller. The data packet is then assembled with preamble, start-of-frame
delimiter (SOF), network routing information and CRC check sum before it is transmitted on RF.
The RF transceiver modulates the data to be transmitted on RF frequency, and demodulates data that
are received. Received data are checked for correct address and CRC by the communication
controller. If the address matches the plug-in board's own address, and no CRC errors were detected,
the data packet is acknowledged before retransmitted.
The asynchronous UART interface consists of RXD, TXD, RTS and CTS. The CTS output will be TRUE
LOW when the plug-in board is ready to receive data. CTS must be monitored on a byte-by-byte basis
to avoid losing data when the default CTS handshake configuration is enabled.
When the CONFIG pin is pulled low, the communications controller interprets data received on the
RXD pin as configuration commands. There are commands to change the radio channel, the output
power, the RF Data Rate etc. Configuration parameters are stored in non-volatile memory. For a full
overview of configuration commands, please see DEVICE CONFIGURATION

Ó2018 Tiny Mesh AS TM4000 Series Data Sheet V1.8 Page 14 of 59

 TM4000 Series
Transparent Mode Operation
The default, factory setting for Tinymesh™ Gateway devices, is transparent mode, well suited for
applications requiring serial data transmission only. In transparent mode, UART data entered at the
Gateway, will be received by all Routers in the network, and will be output by the Router UARTs
without any changes. The addressing must be handled by the host MCU application.
Data input to a Router or End Device UART will be transported 'transparently' to the network Gateway
Device and delivered unchanged by the Gateway Device UART.
Regardless of device type (Gateway or Router), the serial port UART is ready to receive data when the
CTS output is low, or when the Xon character has been received from the UART. RF transmission will
automatically be triggered on serial buffer full or character timeout on the serial port. The connected
host MCU should always observe the selected handshake status (CTS or Xon/Xoff) before sending any
data, to avoid losing data.

Transparent versus Packet Mode Operation

When configured for PACKET MODE OPERATION, the Gateway Device may be used for controlling
Inputs and Outputs in individual Routers and End Devices.
Analogue and digital input monitoring, digital and PWM output control, and timed or event triggered
messages are available through Packet Mode operation.
Gateway Commands may be addressed to individual devices, to groups of devices, or may be
broadcast to all devices within a network.
Serial data entered and received at the Gateway will contain extra bytes for addressing, command
and control.

Ó2018 Tiny Mesh AS TM4000 Series Data Sheet V1.8 Page 15 of 59

 TM4000 Series
Transparent and Packet Mode Functions

Serial Data Streaming

When streaming serial data from a Router Device or from a Gateway Device in Transparent Mode, the
data stream will automatically be divided into correctly sized TinymeshTM RF packets before data is
transmitted in the mesh network. The Serial Data Input Buffer has a capacity of 256 bytes, allowing
for e.g. a complete MODBUS RTU packet to be received.
The Tinymesh™ plug-in board will signal a full buffer condition by setting the CTS output high, or by
issuing an Xoff character, as configured by the UART FLOW CONTROL parameter. The SERIAL BUFFER
FULL MARGIN parameter provides for an adjustable margin from the buffer full condition is signalled,
until the Serial Data Input Buffer overflows. The default setting of the SERIAL BUFFER FULL MARGIN
parameter is 18 bytes, allowing the host MCU a margin of some additional bytes that may be delivered
before the Serial Data Input Buffer of the Tinymesh device runs full. The default value of 18 bytes has
been chosen to optimize packet sizes when streaming data. Most host systems and terminal emulators
will be able to respond to the 'CTS off' status within the time needed to transmit two bytes. At this
point, there will be 240 bytes received in the Serial Data Input Buffer, which is the maximum size of
two full Tinymesh™ RF packets.
The host MCU should stop transmitting data as soon as possible after detecting CTS off, or after
receiving the Xoff character. After a time period of a few milliseconds, as determined by the SERIAL
PORT TIME OUT parameter, the Tinymesh™ device will start forming new RF packets from the received
data, and initiate RF transmission.
If the serial data stream does not stop after the device has signalled the 'buffer full' condition, The
TinymeshTM protocol stack will prepare the data for RF transmission immediately after a data buffer
completely full condition is present (256 bytes).

Note: Subsequent data delivered to the UART will then be lost if the data stream continues before
the Serial Data Input Buffer is again available.

After successful transmission of the received data, the Tinymesh device will signal to the external
MCU that the Serial Data Input Buffer is again available, by setting the hardware handshake CTS signal
low, or by transmitting an Xon character.

Serial Port Handshake

The Gateway and Router serial ports (UARTs) offer several optional handshake settings to support
reliable connections to an external host controller. The different settings are available by changing
the UART FLOW CONTROL parameter in CONFIGURATION MEMORY.
The UART FLOW CONTROL parameter is a bitmap of control mechanisms that may be individually
enabled by setting the corresponding bit. To combine settings, add the values in the 'Bit Value' column
and enter the sum value into the UART FLOW CONTROL parameter in CONFIGURATION MEMORY.

Bit Bit De- Name Applies Function

No Val- fault to
ue

0 1 1 CTS Router The CTS control signal will be low when the Tinymesh device is ready to
and receive data. The external host should monitor the CTS line before
Gateway transmitting any data, as received data will be discarded while CTS is
high.
The SERIAL BUFFER FULL MARGIN parameter in Configuration Memory
may be used to set CTS off a number of bytes before the buffer is
completely full, thereby allowing the host system time to respond to the
CTS off situation. This function is important when for instance using
hardware handshake on a system with USB serial ports.
1 2 0 RTS Gateway The RTS control signal may be used by an external host to signal that the
host is ready to receive data. When enabled, the Tinymesh device will
observe the RTS line before transmitting any byte. No data will be
transmitted while RTS is high.
Note: If RTS is enabled, and the host does not set RTS TRUE (Low), a
connected Gateway Device will not be able to deliver data, and
consequently the Gateway will not receive data from the mesh network.
The mesh network will disconnect.

Ó2018 Tiny Mesh AS TM4000 Series Data Sheet V1.8 Page 16 of 59

 TM4000 Series
Bit Bit De- Name Applies Function
No Val- fault to
ue

2 4 0 RXTX Router The RXTX mode is provided for direction control of RS485 drivers. When
and RXTX is enabled, the UART will set CTS HIGH during data transmission.
Gateway CTS will be driven high immediately before the first start bit is
transmitted, and will return low immediately following the last stop bit
from the UART.
3 8 0 Xon/Xoff Router When the Xon/ Xoff function is enabled, the UART will transmit an Xoff
and character (Value 0x13, ASCII DC3) a settable number of bytes (SERIAL
Gateway BUFFER FULL MARGIN) before the buffer runs full. The external host
MCU should then halt further data transfer until an Xon (0x11, ASCII DC1)
character has been received. An Xon character will be transmitted
repeatedly at 1 second intervals while the UART is ready to receive data.
The Gateway Device will only support Xon/ Xoff when in transparent
mode. Please also note that binary data transfer will not work with Xon/
Xoff, as the binary data may contain the Xon / Xoff characters.
4 16 0 ACK/ NAK Gateway When enabled, the Gateway Device will answer any received data on the
serial port with a COMMAND RECEIVED AND EXECUTED or a
COMMAND REJECTED, NOT EXECUTED message. In this mode, the
Gateway will do a format and validity control of received commands
before transmitting in the RF mesh network.
The MESSAGE DATA MSB will contain the user selected Command
Number.
If the packet is not accepted by the Gateway Device, the MESSAGE
DATA LSB in the returned COMMAND REJECTED, NOT EXECUTED
message will indicate why the packet was not accepted.
5 32 0 Wait For Gateway When enabled, the Gateway Device will expect an ACK character (0x06,
ACK ASCII ACK) response to any packet delivered to the host. If the ACK is not
received within a 1second time frame, the packet will be repeated until
a valid response has been received.
The Gateway device will dispatch a NAK character (0x07, ASCII NAK) on
receiving incomplete or illegal commands when Wait For Ack is active
6 64 0 Append Gateway When enabled, the Gateway Device will append a two byte CRC16
CRC checksum to the packet. The packet start byte will be incremented by 2
to indicate the longer packet length.
Note that the CRC append feature only applies to packets FROM the
Gateway device.
CRC is calculated per CRC-16/BUYPASS (CRC16/VERIFONE, CRC-16/UMTS)
Using 0x800 polynom and 0x0000 seed.
7 128 Reserved

AES Encryption
Changing the SECURITY LEVEL parameter in CONFIGURATION MEMORY will enable automatic AES data
encryption. When AES encryption is enabled, the payload portion of all RF data packets are encrypted
using the 128 bit AES encryption algorithm.
The Gateway and Router Device must share a common AES key, settable by the SETTING AND
CHANGING THE AES KEY (K7- COMMAND).
The encryption key is stored in a hidden and secure memory location.
The AES key is retained even after an @TM factory reset command.
Encrypted and unencrypted Router Devices may coexist and will connect to a common network. A
Gateway Device will be able to receive data from encrypted, as well as unencrypted, Router Devices,
but an unencrypted Router Device will not be able to receive and interpret encrypted commands.

Coexistence with AES Encrypted and Unencrypted Devices

Nodes with encryption enabled, may coexist with unencrypted nodes in a common system. Encrypted
data packets are slightly larger than unencrypted packets. SECURITY LEVEL 2 (Compatible mode) is
provided for backwards compatibility to field deployed systems where encryption has not been
enabled.
In systems with a mixture of encrypted and unencrypted nodes, the following rules will apply:

Ó2018 Tiny Mesh AS TM4000 Series Data Sheet V1.8 Page 17 of 59

 TM4000 Series
• Encrypted packets will be transported by unencrypted nodes to their final destination.
• Unencrypted packets will be transported by encrypted nodes to their final destination.
• Encrypted nodes will not accept receipt of unencrypted packets (commands or serial out
packets)
• Unencrypted nodes will not accept receipt of encrypted packets (commands or serial out
packets)
• An encrypted Gateway will accept and decrypt messages from encrypted nodes, as well as
accept data packets from unencrypted nodes.
• An unencrypted Gateway will only accept messages from unencrypted nodes.

Sleep Mode
A Tinymesh™ Device may be set to sleep mode to reduce power consumption.

Note: When asleep, a Router Device will not provide network routing for other devices, and a
Sleeping Gateway device will not issue HIAM beacons.
Tinymesh™ networks will disconnect if no Gateway Device is active.
These conditions must be considered when designing a network with sleeping devices.

Sleep mode may be entered either by issuing the SET SLEEP MODE command while the device is in
CONFIGURATION MODE, or by pulling the RTS / SLEEP pin low, after activating the SLEEP function
through proper configuration setting (SLEEP OR RTS).

The sleeping device will wake up, go through a full Power On Reset cycle and resume operation when:
• The CONFIG pin is driven high, if SET SLEEP MODE command was used for entering sleep
mode.
• When driving the RTS / SLEEP pin high, if the RTS / SLEEP pin was used to enter sleep mode.

To enter/ exit sleep mode using the RTS / SLEEP pin input:
1. Activate the RTS / SLEEP pin by setting SLEEP OR RTS configuration= 1.
2. Pull the RTS/SLEEP input low to enter sleep mode
3. Drive the RTS / SLEEP input high to exit sleep mode.

Note: The internal RTS/ SLEEP and CONFIG input pull-up resistors are disabled during sleep mode to
reduce excessive power leakage. The CONFIG and SLEEP inputs must therefore be actively driven to
the logic high state to exit sleep mode.

On exiting sleep mode, the Router Device will assume normal operation and connection to the mesh:
• CTS will be high while the device is going through the Reset cycle, and then go low when the
device has made a valid network connection.
• If XON/XOFF protocol is enabled, (UART FLOW CONTROL), a single Xoff character will be
issued after completed reset cycle. The first Xon character will be issued after successful
connection to the mesh.
• The CONNECTION INDICATOR LED will start flashing.
• A DEVICE RESET message will be issued.
• A STATUS MESSAGE (IMA) will be issued if IMA ON CONNECT is enabled.

RF Jamming Detection and Alarm

The RF Jamming Detection feature is a unique Tinymesh™ function, providing timed logging and
alarming of RF conditions that may inhibit radio communication. Radio Frequency interference that
may influence RF connectivity may be present in form of intended (jamming) disturbance, or
unintended noise from electrical equipment or RF transmitters.

The following Configurable parameters control the RF Jamming alarm feature:

• The RF JAMMING DETECT parameter sets the number of minutes of RF jamming that
constitutes an alarm condition. The default value is 0 = off.
• The RF JAMMING ALARM PORT parameter selects the GPIO number (0-7) for local alarm
output.
• The GPIO parameter sets the selected GPIO function as active low or active high output.

Ó2018 Tiny Mesh AS TM4000 Series Data Sheet V1.8 Page 18 of 59

 TM4000 Series

RF Jamming Detection in Packet Mode Systems

When RF Jamming Detection has been enabled by setting the RF JAMMING DETECT parameter, the
Tinymesh™ Device will create an RF JAMMING DETECTED message that will be transmitted through the
mesh as soon as RF communication is re-established. The RF JAMMING DETECTED message MESSAGE
DATA MSB will indicate the duration of the jamming situation in minutes, and the MESSAGE DATA LSB
will indicate the time since the jamming condition ended in hours.

Clustered Node Detection and Network Congestion Avoidance

(CND/NCA™)
The Clustered Node Detection feature is a unique Tinymesh™ function, provided to prevent RF
network congestion in situations where multiple Tinymesh™ devices are located densely together. In,
for instance, energy metering installations, large groups of meters may often be located side-by side,
forming clusters of devices ranging from a handful of units, to tens or hundreds of meters in the same
location.
In such clustered situations, there is a risk of excessive amounts of radio traffic, causing network
congestion and bad connectivity, as the RF bandwidth will be filled with radio packets intended for
network maintenance, and there will be very little bandwidth available for data packets containing
payload data.
The Clustered Node Detection feature is controllable through the following, configurable parameters:

CLUSTERED NODE RSSI. The default RSSI setting is 60 (-30 dBm). Lower settings will effectively disable
this function, as the value will be lower than the RX saturation level for the radio. By increasing the
value, the cluster detection function may be adapted to situations with devices using lower TX output
power.

CLUSTERED NODE DEVICE LIMIT. The default setting is 10, forcing the clustered node detection
function to start reducing unnecessary RF traffic when more than ten devices are located closely
together.

Optimizing Polled Systems

Wireless Tinymesh™ networks are well suited for replacement of wired multidrop systems, offering
significantly lower installation and infrastructure cost. Transparent as well as Packet mode
configurations of Tinymesh™ may satisfy the requirement for an RS485 or similar multi-drop
replacement.
Multidrop systems often use a polled communication protocol, with a master device sending
individually addressed, or broadcast 'poll' commands, asking for response from slave devices.
A wireless mesh will generally provide less communication bandwidth as compared to a wired system,
and unnecessary communication overhead should be avoided when possible, to increase payload
throughput. The Tinymesh™ protocol stack provides a number of mechanisms that serve to improve
data throughput in master-slave systems.

In systems configured for TRANSPARENT MODE OPERATION, it is advisable that the master (Gateway)
performs broadcast polling rather than sending individual device poll commands.

Note: Successful implementation of broadcast polling requires that the networked devices will
respond with data packets containing the device address as part of the data payload.

When receiving a command broadcast, the networked devices will attempt communicating the
command response more or less simultaneously after executing the received command. The
Tinymesh™ Router Device that first detects a clear RF channel when performing the Listen Before Talk
procedure, will immediately start transmission. Other devices will detect that the radio channel is
busy, and will retry communication after a random time period. This automatic retry mechanism will
ensure that responses from all devices are communicated to the master (Gateway) Device error free
and within an optimum time period.

Tinymesh™ Packet mode configuration provides additional means for creating efficient replacements
for wired, polled systems. In Tinymesh™ wireless networks configured for PACKET MODE OPERATION,
the ORIGIN ID of the response packet may be used to identify the individual device, eliminating the

Ó2018 Tiny Mesh AS TM4000 Series Data Sheet V1.8 Page 19 of 59

 TM4000 Series
requirement for having device address as part of the data payload. Individual Tinymesh™ devices may
also be set to generate automatic, time generated status reports, and devices may be configured to
automatically generate messages on digital or analogue input status changes, eliminating the need for
the master controller poll function. For further information, please reference the later chapter on
AUTOMATIC STATUS REPORTING.

LED Indicators
Plug-in board pins RSSI/ TX LED and Connection/ RX LED are designed to directly drive LEDs. On Tinymesh
full size demo boards, the Red LED is driven by the RSSI/ TX LED output and the Yellow LED is driven by
the Connection/ RX LED output.
We recommend that these LED outputs are also implemented in target hardware. The LED signals will
be useful for system deployment and configuration.

Flash patterns as documented in the data sheet assume the outputs to be sourcing power to the LEDs.
This is the recommended configuration, that will also work for low power, battery operated devices
while in sleep mode.
If using the outputs as power sinks, the LED flash patterns will be inverted, and connected LEDs will
leak power while the device is in sleep mode.

LED Indicator Timeout

In many applications, the LED indicators will be useful during installation or for field service purposes.
After installation, the indicators may in some applications no longer be desirable. For battery
operated End Devices the indicators will represent an undesired power consumption.
The configurable INDICATORS ON parameter determines the time the indicator outputs are active
after a power-up reset. By default, this parameter is set to 255 = permanently ON for Gateway and
Router Devices. For End Devices, the parameter will automatically be set to default value 1 for a one
minute timeout, when using the 'N' - SET END DEVICE MODE configuration command to change
between operational modes.
Setting the INDICATORS ON to 0 will permanently disable the indicator function.

Pulse Counter Feedback Indicator

Any GPIO may be configured as a feedback output for the pulse counter mode. Please see Pulse Count
Verification for details on the Pulse Counter Feedback function.
The duration of the pulse counter feedback is also controlled by the INDICATORS ON parameter, which
will optionally disable this output after a pre-set timeout.

RSSI Indicator LED

When configured as a Router or End Device, an LED connected to the RSSI/ TX LED output, will function
as an RSSI indicator for Tinymesh™ Router or End Devices. The LED will flash with one of the following
frequencies/ intervals, based on RSSI level for the established connection:

1. Very fast flash (Five flashes per second):

RSSI is better than configured EXCELLENT RSSI LEVEL
2. Fast flash, (Two flashes per second):
RSSI is good, at least CONNECTION CHANGE MARGIN better than RSSI ACCEPTANCE LEVEL
3. Moderate flash, on for 1 second, off for 1 second:
RSSI is acceptable for reliable communication
4. Very slow (2 seconds ON, 2 seconds off):
RSSI is below the RSSI ACCEPTANCE LEVEL that will allow new connection. No new
connections will be established at this low RSSI, but existing connection may still exist if the
Connection LED is still flashing

Ó2018 Tiny Mesh AS TM4000 Series Data Sheet V1.8 Page 20 of 59

 TM4000 Series
Connection Indicator LED
When configured as a Router or End Device an LED connected to the Connection/ RX LED output, will
function as a connection indicator. The LED will flash with one of the following patterns:
1. Steady ON:
The device has established direct connection to a Gateway Device, and at least one more
Gateway Device is available for alternate routing.
2. Rapid flash, 5 times per second:
The device has established direct connection to a single Gateway Device.
3. Fast flash, 2 times per second:
The device has established connection to a Router Device, and at least one more Router
Device is available on the same jump level, as an alternate route (redundant connection)
4. Moderate flash, ON for one second and OFF for one second:
The device has established connection to a single Router Device, and no alternatives exist on
the same jump level.
5. No light: The device is disconnected
6. The Connection LED is flashing in sync with the RSSI Indicator LED immediately from Reset /
Power up: The device is configured with a FIXED DESTINATION ID

Both LED outputs may also be monitored by an external MCU for other visualization of RSSI level and
network connection quality.

The device connection status may be included in the data field of STATUS MESSAGE (IMA) messages.

Radio RX /TX Indicator LED

When configured as a Gateway Device, an LED connected to RSSI/ TX LED, will flash every time an RF
packet is transmitted. An LED connected to Connection/ RX LED, will flash every time an RF packet with
valid formatting and valid CRC is received.

Configuration mode indicator

When Tinymesh™ Devices enter into Configuration mode, the two LEDs will both be turned ON. On
exit from Configuration Mode, the LEDs will resume original function as either RX/TX indicator for
Gateway Devices, or Connection Quality indicators for Router Devices.

Ó2018 Tiny Mesh AS TM4000 Series Data Sheet V1.8 Page 21 of 59

 TM4000 Series
Packet Mode Operation
When configured for packet mode operation, serial data and command packets may be broadcast to
all devices, addressed to a group of devices, or addressed to a specific Router or End Device. Packet
mode allows for setting and reading of the GPIO pins on the plug-in board, as well as reading the two
analogue inputs, and activating the PWM output control for dimmer or speed control applications.
Digital and analogue inputs may be set to trigger messages on input condition changes.
Routers will acknowledge receipt and acceptance of commands and data. The Acknowledge packet
will be available on the Gateway UART.
The Gateway Device will provide additional, bi directional ACK / NAK handshake for error free
connection to an external host

Gateway in Packet Mode

All data entered on the Gateway UART in Packet mode must follow strict formatting rules. The
following tables describe packet formatting for transmitted and received packets. Please note data
must be entered in one, contiguous string of bytes.

Note: Any time gap of more than the configured SERIAL PORT TIME OUT value will cause the Gateway
to treat the entered data as a complete packet. If a timeout should occur before the intended end of
the packet, the Gateway will not recognize the packet format, and the packet will be discarded
(lost).

Router in Packet Mode

Router Devices behave similarly in Transparent and Packet mode. All packets will always be routed to
the Gateway Device. Packet formatting and addressing is handled automatically by the Router
firmware, and binary serial data may be entered to the Router UART without packet formatting and
address information. Serial data packets will be transmitted immediately when the UART buffer is full
(256 bytes), or after a configurable SERIAL PORT TIME OUT time gap between characters.

Note: To switch between Transparent and Packet Mode operation, only the Gateway configuration
needs to be changed.

Transmitting Command and Configuration Packets from Gateway

Gateway commands may be used to transmit serial data, to set or read GPIO pins, to enquire device
operating status, or to alter settings in the Configuration Memory of Router Devices.
All GPIO pins are initially configured as digital inputs with no triggering enabled. The desired GPIO
function must be configured by altering the CONFIGURATION MEMORY settings, to enable functions
such as Analogue input, PWM control, Digital Output or Input Trigger functions.
Tinymesh™ Devices may be configured through the UART in Configuration Mode (CONFIGURATION
COMMANDS), or while operating in a live mesh network by issuing SET CONFIGURATION commands
from the Gateway Device.

Note: To avoid losing connection with devices in a live mesh network, the RF CHANNEL, RF DATA
RATE, UNIQUE_ID and SYSTEM_ID may only be changed through Gateway Commands before the
SYSTEM_ID has been changed from the factory default setting.

The Command Packet formats for device control, inquiry and configuration, are shown in the
COMMAND PACKET FORMAT table.

Group and Broadcast Addressing

Commands may be broadcast to all devices in a network by selecting '255 255 255 255' as the NODE
ADDRESS .
Router and End Devices may also be assigned to addressing groups, by entering up to eight different
single byte group identifier addresses in the configurable GROUP TABLE. The most significant byte of
the UNIQUE_ID in the command NODE ADDRESS is interpreted as a group identifier by the receiving
device.

Ó2018 Tiny Mesh AS TM4000 Series Data Sheet V1.8 Page 22 of 59

 TM4000 Series
The addressing structure for group commands is '255 255 255 nnn', where the 'nnn' byte represents the
group identifier.

Example: Commands addressed for '255 255 255 003' will be accepted by any router belonging to
group #3, identified by one of the group bytes in the GROUP TABLE set to '3'

Command Acknowledge
On receiving a command packet, the Router or End Device will perform a validity check of the
received data before executing the command. If the COMMAND ACKNOWLEDGE function is enabled,
the device will return an event packet indicating if the packet was accepted.

Note: Broadcast and Group commands will only generate response packets if the COMMAND NUMBER
is set larger than 127

• The selectable COMMAND NUMBER will be returned in the MESSAGE DATA MSB field of the
response packet.
• A COMMAND RECEIVED AND EXECUTED Event Message will be returned if the received
command passes the test criteria.
• If command data or arguments are out of range, a COMMAND REJECTED, NOT EXECUTED
Event packet will be returned. The MESSAGE DATA LSB field of the returned packet will
indicate the reason for rejecting the command.

Gateway Devices in Packet Mode will generate ACK or NAK response to Commands if the ACK/ NAK
serial port handshake has been enabled. The response packet format is a short form of the regular
COMMAND RECEIVED AND EXECUTED or COMMAND REJECTED, NOT EXECUTED event packets, truncated
immediately following the MESSAGE DATA LSB FIELD.

Command Packet Format

Byte # Field Size Description

Control and Status request Change Configuration

1 Start character 1 10 (0x0A) Equals length of string 40 (0x28) Equals string length
2 Node Address 4 Configured value of destination node, or use broadcast ID
(255 255 255 255) if command for all units.
Gateway devices will respond to commands where Node Address = Unique ID (UID),
or where Unique ID = 0 0 0 0
6 Command 1 User selectable. This number will be returned as part of the Acknowledge packet
Number from the Router on completed command execution
7 Packet Type 1 3 (0x03) Fixed value
8 Command 1 1 (0x01) Set Outputs 3 (0x03) Set Configuration
Argument 2 (0x02) Set PWM
5 (0x05) Set Gateway in Config Mode
16 (0x10) Get NID
17 (0x11) Get Status
18 (0x12) Get DID Status
19 (0x13 Get Configuration Memory
20 (0x14) Get Calibration Memory
21 (0x15) Force Router Reset
22 (0x16) Get Packet Path
9 Data 1 1 Set Outputs: Bitmap for setting GPIO 0..7 Data 1..33 (32 bytes)
Set PWM: 0-100 % duty cycle. 1st. Byte = address
For other Command arguments, this byte is 2nd. Byte= value
don't care. …..
32rd. Byte=last address
10 Data 2 1 Set Outputs: Bitmap for clearing GPIO 0..7 33rd. Byte=last value
For other command arguments, this byte is
don't care. Address=00 indicates last valid
address.(see example)
Note: The sequence of the UIDs below are UID0-UID4

Ó2018 Tiny Mesh AS TM4000 Series Data Sheet V1.8 Page 23 of 59

 TM4000 Series
Command String Examples
Command Example: Set Router Configuration, Router UID 1 2 3 4,
Configure GPIO 0 as Output, default High, (Config Address 16 = 0)
Configure GPIO 7 as pulse width modulated output, (Config Address 23= 3)
Configure GPIO 4 as Input, negative edge trigger (Config Address 28 = 2)

Decimal notation
40 1 2 3 4 6 3 3 16 0 23 3 28 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

Hex Notation
28 1 2 3 4 6 3 3 10 0 17 3 1C 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

Copy & Paste string for CCTool

'40 1 2 3 4 6 3 3 16 0 23 3 28 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0'

Transmit Serial Data Packet from Gateway

Enter Serial Data Packets to be transmitted to individual Router Devices, using the following packet
format. Maximum packet size is 120 bytes. Payload data bytes may be any format (binary data).
Please note the start byte is a calculated value
Byte # Field Size Description
1 Start Byte 1 Calculated value, total number of bytes, including Start Byte
2 Node Address 4 Configured value of destination router, or use broadcast ID (255 255 255
255) if Serial Data Packet for all units.
6 Command 1 User selectable number, returned as part of the Acknowledge packet from
Number the Router on completed command execution
7 Packet Type 1 17 (0x11) Fixed value
8 Serial Data 1..120 Binary data

Example 1, Send text string 'Hello' from Gateway to Router with UID 0 0 1 2, packet no 6
Decimal notation Hex Notation
12 0 0 1 2 6 17 72 101 108 108 111 C 0 0 1 2 6 11 48 65 6c 6c 6F

Received Packet Formats

Packets received by the Gateway in Packet Mode, will be delivered on the UART TXD pin in the
following formats. The packet Header is identical for all packet types, while the data payload
formatting (starting at data byte # 18) will be formatted differently when receiving serial data and
command responses requiring larger amounts of data.

Byte # Field name Size Description

1 Start Character 1 Total number of bytes in the message, including start character
2 System ID 4 System wide ID, must be identical for all devices in a system
6 Origin ID 4 Address of Router that created the message
10 Origin RSSI 1 RSSI from first receiver to originating node
11 Origin Network Level 1 'Hop' level, number of vertical hops to reach Gateway
12 Hop Counter 1 Number of actual hops from Router to Gateway
13 Message Counter 2 Unique number maintained by originating node
15 Latency Counter 2 Time in 10 ms resolution from message creation to delivery
17 Packet Type 1 Event 2 (0x02) or Serial data in 16 (0x10)

Ó2018 Tiny Mesh AS TM4000 Series Data Sheet V1.8 Page 24 of 59

 TM4000 Series
General Event Packet Format (Packet Type 0x02)
Byte # Field name Size Description
18 Message Detail 1 1 (0x01) Digital Input Change Detected
2 (0x02) Analogue 0 Input Trig
3 (0x03) Analogue 1 Input Trig
6 (0x06) RF Jamming Detected
8 (0x08) Device Reset
9 (0x09) Status Message (IMA)
10 (0x0A) Channel is Busy with Similar System ID
11 (0x0B) Channel is Free
12 (0x0C) Channel is Jammed
13 (0x0D) Unknown Tinymesh™ System(s) Active on this Channel
14 (0x0E) My System and Unknown System(s) Active on this channel
16 (0x10) Command Received and Executed by Router Node (ACK)1
17 (0x11) Command Rejected, Not Executed by Router Node (NAK)1
18 (0x12) Status Message from Gateway (NID)
19 (0x13) Status Message Next Receiver
19 Message Data MSB 1 Message Detail Message Data
1 0
9 Configurable content, ref:
IMA MESSAGE DATA FIELD CONTENTS
0: 0 (Default)
1: GPIO Trig Hold register
2: High Byte of 2-byte Pulse Counter
5: Device Connection status:
1. No alternatives on same hop level
2. Alternatives available, same hop level
3. Single Gateway
4. Gateway, alternative available
6: My Locator RSSI
2,3,8,10,11, 0
12,13,16,18,19
6 Jamming condition duration in minutes
17 0 NAK response from Router or End Device
1 (0x01): Bad Command packet length
3 (0x03): Bad Packet format
4 (0x04): Bad Gateway Command Type
17 (0x11): Bad Config command
18 (0x12): Bad Secured Command Length
20 Message Data LSB 1 Message Detail Message Data
1 GPIO Trigger source, bit 7-0
9 Configurable content, ref:
IMA MESSAGE DATA FIELD CONTENTS
0: 0
1: 0
2: Low Byte of 2-byte Pulse Counter
5: 0
6: 0
2,3,10,11, 0
12,13,18,19
6 (0x06) Hours since jamming condition ended
8 (0x08) 1 (0x01): Power On Reset
2 (0x02): External Reset (RESET input low)
3 (0x03): Reset from Sleep or Config Command
4 (0x04): Forced Reset by command
5 (0x05): Watchdog Reset
16,17 User selected command number

1
ACK and NAK messages from Gateway Device truncated after the Message Data Fields

Ó2018 Tiny Mesh AS TM4000 Series Data Sheet V1.8 Page 25 of 59

 TM4000 Series

Byte # Field name Size Description

21 Address(ID) Data 4 Message Detail Message Data
9 (0x09) Configurable content, ref IMA MESSAGE ADDRESS
FIELD CONTENTS
0: No Data
1: Pulse Counter (4 bytes)
2: Locator ID (4 bytes)
3: Destination ID (4 bytes)
4: Alternate Destination ID (4 bytes)
1-8 and Address of Locator Router with best received signal
10-17 strength (RSSI)
(0x0A)- (0x11)
18 (0x12) Gateway Network ID
19 (0x13) Address of first receiver in hop path
25 Device Temperature 1 Device Temperature, Ref TEMPERATURE READING (U- COMMAND)for
value interpretation
26 Device Voltage 1 Voltage/ Battery Monitor, ref. POWER SUPPLY VOLTAGE READING (V-
COMMAND) for value interpretation
27 Digital Inputs 1 GPIO 0-7
28 Analogue 0 2 Analogue 0 converter, GPIO 0 (12 bits)
30 Analogue 1 2 Analogue 1 converter, GPIO 1 (12 bits)
32 HW version 2
34 FW version 2

Event Packet Format (Packet Type 0x02), Response to Get Path Command
Byte # Field name Size Description
18 Message Detail 1 32 (0x20) Get Path Response
19..23 Message Data 5 Byte number Content
1 RSSI first jump
2..5 First receiver ID
New entries of 5 bytes added per additional jump until packet is full (138 bytes) or last destination reached
134..138 Message Data 5 Byte number Content
1 RSSI Last jump
2..5 Last receiver ID

Event Packet Format (Packet Type 0x02), Response to Get Configuration Memory Command
Byte # Field name Size Description
18 Message Detail 1 33 (0x21) Configuration Memory Dump
19-n Message Data Variable Byte number Content
1..n All bytes of accessible Calibration Memory

Event Packet Format (Packet Type 0x02), Response to Get Calibration Memory Command
Byte # Field name Size Description
18 Message Detail 1 34 (0x22) Calibration Memory Dump
19-138 Message Data 120 Byte number Content
1..120 First 120 bytes of configuration memory

Serial Data Packet Format (Packet Type 0x10)

Byte # Field name Size Description
18 Serial data block counter 1 0: Single data block, terminated by UART timeout.
1-255: Block (partition) number in large data streams controlled
by CTS or Xon/Xoff handshake
19 Serial data 1..120 Serial data

Ó2018 Tiny Mesh AS TM4000 Series Data Sheet V1.8 Page 26 of 59

 TM4000 Series
Practical Use of Packet Header Data
The header section is identically formatted for all TinymeshTM data packets. The header section
contains valuable information for network quality analysis and data validation in a host system.

The four byte SYSTEM ID uniquely identifies the network that originated the message, and may be
used as an identifier in host systems that handle multiple Tinymesh™ networks.

The UNIQUE_ID is unique address identifier of the device that originated the message, and an
important identifier in a host system database.

The ORIGIN RSSI is the RF signal strength of the first link in the hop path for the message, and is an
indication of the quality of the first link. A high value, approaching the minimum level for reliable
connection indicates poor connection, and may be an indication of poor connectivity with possibility
for unreliable connection. An RSSI value above 190 is regarded as potentially too low for stable and
reliable connection. The RSSI ACCEPTANCE LEVEL parameter in Configuration Memory determines the
highest allowable link RSSI for establishing a new connection.

ORIGIN NETWORK LEVEL indicates the network hop level of the originating device at the time when
the message was dispatched. As an example, if ORIGIN NETWORK LEVEL is 3, it indicates the packet
will hop three times from the originating node, before reaching the Gateway. As a TinymeshTM
network inherently is a dynamical network that continuously adapts to changing RF conditions, it is
possible that the packet may require more or less than the anticipated number of hops before
reaching the Gateway. The actual number of hops travelled by the packet is indicated by the HOP
COUNTER value that will increase by one each time the message is passed from one node to another.

The MESSAGE COUNTER is a unique, 16-bit number maintained by the originating node. Every message
received by a host system may be uniquely identified by a combination of the SYSTEM ID, ORIGIN ID
and MESSAGE COUNTER.
Note that the MESSAGE COUNTER is reset to zero after 64k packets, or after a device Reset. In
practical implementations, it may be assumed that a new numbering sequence starts every time a
DEVICE RESET message is received from the device. Reset messages will be generated after Power
On, after a FORCE ROUTER RESET Command or after execution of a Device SET CONFIGURATION
Command.

The LATENCY COUNTER is a 16-bit timer that is reset to zero when the packet is created, and
maintained throughout the transportation chain until the message is delivered from the Gateway
Device to the external host. The timer is updated at 10ms or 2560ms intervals, selectable by the MAX
PACKET LATENCY TIME BASE parameter.
The timer will stop counting after reaching the maximum value. The message transportation delay is
a good indicator of network reliability, and may be used in time critical implementations, to recreate
an accurate time stamp for an event. Typical transportation delays in systems using default
configuration settings may be expected to be less than 100ms per network hop.

Device and Network Status Interrogation

The TinymeshTM protocol stack supports several optional commands for system and device status
interrogation.

Automatic, time generated status messages may be generated by setting the IMA TIME parameter in
Configuration Memory. For details, see AUTOMATIC STATUS REPORTING.

The GET STATUS, GET DID STATUS, and GET NID commands all return similarly formatted status
messages with a payload portion containing the status of all input parameters: Analogue, Digital,
Temperature and Supply Voltage.

The GET STATUS command returns a STATUS MESSAGE (IMA) event message, and may also be activated
on an automatic time base by setting the IMA TIME parameter in Configuration Memory. The contents
of the MESSAGE DATA MSB, MESSAGE DATA LSB and ADDRESS(ID) DATA packet fields is configurable
through the IMA MESSAGE DATA FIELD CONTENTS and the IMA MESSAGE ADDRESS FIELD CONTENTS
parameters.

Ó2018 Tiny Mesh AS TM4000 Series Data Sheet V1.8 Page 27 of 59

 TM4000 Series
The GET DID STATUS command returns a STATUS MESSAGE NEXT RECEIVER event message, containing
the next receiver ID in the packet ADDRESS(ID) DATA field. Next Receiver is the preferred receiver of
all communication from this node.

The GET NID command is only recognized by Gateway Devices, and returns a STATUS MESSAGE FROM
GATEWAY (NID) event message, containing the Gateway NETWORK ID in the packet ADDRESS(ID) DATA
field.

The GET CONFIGURATION MEMORY command returns a CONFIGURATION MEMORY DUMP event message,
a complete listing of the first 120 bytes of Configuration Memory of the addressed device. This
command is useful for verification of individual configuration settings in the network.

The GET CALIBRATION MEMORY command returns a CALIBRATION MEMORY DUMP event message, a
complete listing of the CALIBRATION MEMORY of the addressed device. This command is useful for
verification of individual configuration settings in the network.

The GET PACKET PATH command returns a variable length payload, GET PATH RESPONSE event
message. The payload contains the address and RSSI of all network hops from the original node to the
Gateway. Note that in extremely large systems, the number of hops may exceed the maximum
payload size of the packet. The maximum payload size is 120 bytes, allowing room for 120/ 5 = 24
hops. In such events, the received message will contain all hops from original node until full packet,
and a new Get Packet Path may be issued, addressing the last node in the previously received path.

Note: GET PACKET PATH commands will only return a valid path response when executed in
unencrypted systems.

Serial Data Block Counter

The Tinymesh™ protocol stack supports long data frames and streamed data. The SERIAL DATA BLOCK
COUNTER found in serial data packets in packet mode, indicates if the received data belongs to a
larger stream of serial data, or if the delivered data is a single delivery.
If the SERIAL DATA BLOCK COUNTER is zero (0), the delivered data is a single packet, generated by the
Router or End Device after detecting a timeout on the serial port, but before a 'buffer almost full
condition' was signalled through CTS Off or Xoff (See SERIAL PORT HANDSHAKE).
If the SERIAL DATA BLOCK COUNTER is 1 or higher, the delivered data is part of a larger stream of
data, and the block counter value is an indication of the sequence of the received data. The block
counter will roll over to 1 after reaching the maximum value of 255 and will automatically be reset to
0 after receiving the last packet of a data stream.

Locator Function
Any Router or Gateway may be configured as a 'Locator' by setting the LOCATOR_ENABLE parameter.
By default, the Locator function is disabled (0).
Router devices will continually be listening and waiting for incoming data. In this process, the Router
device will pick up packets originating from any Locator Device within RF reach. Router devices will
always remember the UNIQUE_ID of the Locator Device with the lowest (best) RSSI.
Every time a Router Device dispatches a packet with GENERAL EVENT PACKET FORMAT, the
ADDRESS(ID) DATA field will contain the UNIQUE_ID of the Locator Device within closest radio range
(best RSSI) of the Router.
A GENERAL EVENT PACKET FORMAT Event message may be triggered on a timely basis by setting the
IMA TIME parameter, through a request command from the Gateway, or be triggered by a digital or
analogue input level shift.

The Locator feature may be utilized in systems designed for asset tracking or other locating functions.
Router Devices placed in fixed, known locations should then be set as Locator devices. Portable
devices or devices with unknown location should have the Locator bit disabled.

Network Busy Detection

Gateway Devices may be set to monitor and report network activity before starting to build the mesh
network. In some applications using ad hoc networks with, for instance, portable Gateway Devices, it

Ó2018 Tiny Mesh AS TM4000 Series Data Sheet V1.8 Page 28 of 59

 TM4000 Series
may be important for the operation of the systems that only one Gateway Device is active at any
time.
By enabling the DETECT NETWORK BUSY parameter, the Gateway Device will either monitor and
report status before building the network, or may optionally refrain from building the network if
competing activity is discovered.

Network ID
The NETWORK ID Calibration Memory Parameter is intended for host systems operating multiple mesh
networks, such as the Tinymesh Cloud platform. For standalone systems, the SYSTEM_ID is sufficient
for identifying devices belonging to a system.
When deploying Internet based host platforms, there may already exist deployed networks with
identical SYSTEM_ID settings. To be able to uniquely distinguish between co-existing systems with
identical SYSTEM_ID, the Gateway Device may be configured with a unique, four byte NETWORK ID,
allocated by the hosting system.
A host system may request the Gateway NETWORK ID by sending a GET NID command to NODE
ADDRESS 0 0 0 0. The Gateway Device will respond with a STATUS MESSAGE FROM GATEWAY (NID)
event packet, containing the NETWORK ID in the ADDRESS(ID) Data field.
The NETWORK ID is stored in the device CALIBRATION MEMORY, and will be retained after a RESET
MEMORY factory reset command.
The WRITE CONFIGURATION MEMORY command must be used to change the value of the NETWORK ID.
The device must be set to CONFIGURATION MODE, and the SETTING AND CHANGING THE NETWORK ID
(NID) procedure should be used to change the NID.

IMA On Connect Function

A Router Device may be set to send a STATUS MESSAGE (IMA) report every time it connects to the
mesh network. This function may be useful in networks that are normally inactive, and that are
temporarily formed by introducing a Gateway Device, e.g. for data collection when using a hand held
Gateway.
The host system will receive a STATUS MESSAGE (IMA) messages every time a new device connects to
the network, and may successively build a complete list of connected devices by storing the ORIGIN ID
found in the header of each received packet.
Enable the IMA On Connect feature by changing the IMA ON CONNECT configuration setting.

Automatic Status Reporting

Tinymesh™ networks provide efficient mechanisms for automatic, time generated status reporting,
automatic messaging on analogue or digital input status change and automatic data transmission on
serial data (UART) input. Automatic status and event reports should be considered as an alternate and
more efficient system design than traditional status polling. Poll commands from a master will occupy
valuable RF bandwidth, limiting the data throughput and responsiveness in a mesh system. In contrast
to protocols normally employed in wired multidrop systems, a Tinymesh™ network allows any device
to initiate communication as long as the communication media (the RF channel) is free. The local
intelligence embedded in Tinymesh™ devices automatically handles the access to the shared RF
channel by CSMA (Carrier Sense Multiple Access), eliminating the need for a polling master controller.

Automatic, time generated status messages may be generated by setting the IMA TIME parameter in
Configuration Memory. The IMA timer is a single byte timer, with selectable time base. The time base
may be set from 10 to 2550 seconds by changing the value of the IMA TIME BASE parameter. The
default setting of 6 provides a one minute resolution for the IMA timer. Time generated messages may
be used for data logging purposes, and as a means to keep track of the online status of devices. If the
Routers or End Devices are set to report status once in a given time interval, a host system may
routinely check that all devices have reported back within the time window, and generate an alert if
status messages are missing.

Analogue and digital inputs may be set to trigger event messages on predetermined status changes.
Event messages triggered by input status changes will be transmitted immediately, providing a more
responsive approach than what may be achieved in a traditional, polled system.
Please reference the chapters ANALOGUE Input Event Triggering and DIGITAL INPUT for in-depth
information on configuring the inputs for automatic event triggering.

Ó2018 Tiny Mesh AS TM4000 Series Data Sheet V1.8 Page 29 of 59

 TM4000 Series
All event message packets contain by default the current value of Digital and Analogue inputs, device
temperature, device voltage and the address of the closest Locator Device.

Serial data entered on the device UART will automatically trigger a serial data transmission when the
serial data buffer is full, or after a configurable timeout between bytes.

Receive Neighbour Function

Tinymesh™ Router Devices in live networks with an active Gateway Device, may be configured to
accept messages dispatched by neighbour devices, for direct output of the received data to the UART,
formatted as RECEIVED PACKET FORMATS.
The RECEIVE NEIGHBOUR MESSAGES parameter must be set to 1 to enable this function.
A neighbour device is defined as any device that is within direct link of the Router Device.
By enabling this function, a Router Device will copy all received data packets originating from any
neighbouring device to its serial port. Data will be delivered in the standard packet format, similar to
data received by a Gateway Device.

Note: Data is verified for integrity before accepted, but there is no retransmission nor acknowledge
handshake for this mode.

The Receive Neighbour function may be useful in home control or simple applications where direct
control from one device to another, nearby device is desirable. An external MCU may be programmed
to interpret the received data packet and perform actions determined by the received data.

Example: The received data is a GPIO trig message indicating that the transmitting Router has
detected an input signal transition on a GPIO. The receiving application may interpret this signal as a
command to turn on/ off a function, such as a light source.

Ó2018 Tiny Mesh AS TM4000 Series Data Sheet V1.8 Page 30 of 59

 TM4000 Series
Input / Output Functions
Tinymesh™ Devices have eight connection pins for application Input / Output control, in addition to
the dedicated PULSE COUNTER input and the UART serial port.

The Gateway Device must be configured for PACKET MODE OPERATION to support the Input / Output
functions. Sampled analogue and digital GPIO values may be found in all GENERAL EVENT PACKET
FORMAT received from Router or End Devices.
Outputs may be controlled by the SET OUTPUTS and SET PWM commands from the Gateway.
Routers and End Devices will trigger event packet delivery from several sources:
• By an analogue input signal changing value(ANALOGUE INPUT)
• A digital input changing value (DIGITAL INPUT)
• A timed event (AUTOMATIC STATUS REPORTING)
• By a request command from Gateway (GET STATUS)
By default, all eight GPIO pins are inputs. Any of the GPIOs may however be changed to function as
outputs with default high or default low level.
Additionally, GPIO 0 and 1 may be configured to function as analogue inputs, and GPIO 7 may be used
for 0-100% duty cycle PWM output.
Each GPIO pin is supported by individual configuration settings for function selection (GPIO) and (GPIO
TRIG) condition.

Digital Input
When a GPIO has been configured to act as an input through the GPIO configuration setting, a
separate GPIO TRIG configuration setting is used to determine if the input signal should be used to
trigger an event message. The trigger function may for instance be used to trigger an alarm condition.
The configuration settings allow for triggering on digital signals when changing from high to low level,
from low to high, or both. The default setting is no trig. Digital inputs are preconfigured with a 20k
pull-up resistor. With no external signal connected, a digital input will always read as digital ‘1’ in
Event Messages.

Digital Input De-bouncing

Digital inputs are protected by a de-bounce mechanism, to eliminate problems with unstable signals
or settling times for micro switches or detectors. The de-bounce setting is common for all digital
inputs, and settable in intervals of 1ms by changing the INPUT DE-BOUNCE Configuration Parameter.
The default setting is 10ms, meaning that any digital input must deliver a stable input (no change) for
at least 10ms, to trigger an event.

Digital Input ‘Trig Hold’

The TRIG HOLD function creates an 8-bit bitmap of inputs that have been triggered (meeting
configured digital input GPIO trig conditions) during the last IMA TIME sampling period.
The 'Trig Hold' data may be included in the STATUS MESSAGE (IMA) packets by changing the default
configuration of the IMA Message Data Field Contents .
The trig hold function is useful in data logging applications where several similar trigger events may
occur over a time period, but the transmission of all event messages would introduce unnecessarily
high levels of data traffic.

Pulse Counter
The pulse counter function uses a separate GPIO 3input, not shared by the eight configurable GPIO
inputs. The pulse counter is enabled by changing the PULSE COUNTER MODE configuration.
The pulse counter is a four byte rolling counter, set to zero at Reset. The current counter value is
reported by the STATUS MESSAGE (IMA) event, that may be triggered either on a timed basis by setting
the IMA TIME parameter, or by issuing a GET STATUS command from the Gateway.
The counter status may be viewed either in a two byte format, by selecting the IMA MESSAGE DATA
FIELD CONTENTS parameter = 2, or in a four byte format, by setting IMA MESSAGE ADDRESS FIELD
CONTENTS = 1

Ó2018 Tiny Mesh AS TM4000 Series Data Sheet V1.8 Page 31 of 59

 TM4000 Series

Pulse Counter De-bounce

The pulse counter de-bounce feature is enabled by setting the PULSE COUNTER DEBOUNCE parameter
to the desired de-bounce time in milliseconds. Transitions on the pulse counter input during the
settable de-bounce period will be ignored, and a valid pulse must be at logical low level at the end of
the de-bounce period.

Pulse Count Verification

The PULSE COUNTER FEEDBACK INDICATOR option is a support function to verify proper pulse
counting. The feedback signal may be used to drive for instance a high efficiency LED for instant
verification of pulse detection.

Note: The output drive capability of the output is limited, as indicated in the DIGITAL OUTPUT DRIVE
paragraph.

The feedback signal is controlled by the pulse count firmware, and is therefore a true representation
of pulse detection, and may be used for field test calibration by for instance applying an oscilloscope
to the pulse source and the feedback output.
The feedback output signal has a total duration of minimum 4 ms, maximum 5 ms, and is triggered at
the same time as the device performs the sampling of the input signal level.

Note: When the pulse counter function is used in an End Device, the duration of the feedback
indicator signal will be truncated at the time the device returns to sleep mode, and will therefore
only be active for a few microseconds (us), or for the duration of the PULSE COUNTER DE-BOUNCE
period.

The following Configurable parameters are used to control the Pulse Counter Feedback feature:
• Enable Pulse Counter Feedback by setting the FEEDBACK ENABLE parameter = 2.
• Enter the GPIO number (0-7) selected for the FEEDBACK PORT.
• Configure the selected GPIO as Output by changing the appropriate GPIO function.

Note: Duration of the Pulse Counter Feedback Indicator function is controlled by the INDICATORS ON
parameter. Pulse Counter Feedback will terminate when Indicators are off.

Ó2018 Tiny Mesh AS TM4000 Series Data Sheet V1.8 Page 32 of 59

 TM4000 Series
Digital Output Control
Digital outputs are controlled by Gateway commands, using the SET OUTPUTS Command.

The designated GPIOs must first be enabled as outputs, by configuring the desired GPIO function. The
Default configuration is Input. A command to set or reset a GPIO that has not been configured for
Output control will have no effect. The default output value at Reset is selectable in the GPIO
configuration.
The DATA 1 and DATA 2 bytes in the COMMAND PACKET FORMAT are used to control the output status.
The contents of these bytes are 'bit mapped', such that the first bit of the byte controls the output
status of GPIO 0, and the 7th bit of the byte is used to set GPIO 7. DATA 1 is used for setting outputs,
while DATA 2 is used for clearing outputs.
Note that setting a bit in DATA 2 (Clear output) will override a bit that has been set in DATA 1 (Set
Output). By using two separate bits for setting/ clearing an output, the external application firmware
may be relieved of the task of knowing the previous state of a digital output, because only the single
bits selected by the command will be affected.

Example 1: Set GPIO Outputs 5 and 7

Command Data byte 1 Command Data byte 2
Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
1 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0

GPIO Output
GPIO7 GPIO6 GPIO5 GPIO4 GPIO3 GPIO2 GPIO1 GPIO0
No No No No No No
Set Change
Set Change Change Change Change Change

Example 2: Clear GPIO Output 3

Command Data byte 1 Command Data byte 2
Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0

GPIO Output
GPIO7 GPIO6 GPIO5 GPIO4 GPIO3 GPIO2 GPIO1 GPIO0
No No No No Clea- No No No
Change Change Change Change Change Change Change
red

Example 3: Command Data Byte 2 settings will override Command Data Byte 1 settings
Setting and clearing the same output, results in clearing the output:
Command Data byte 1 Command Data byte 2
Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0 Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0
0 0 0 0 0 1 0 0 0 0 0 0 0 1 0 0

GPIO Output
GPIO7 GPIO6 GPIO5 GPIO4 GPIO3 GPIO2 GPIO1 GPIO0
No No No No No Clea- No No
Change Change Change Change Change Change Change
red

GPIO mapping,
GPIO7 GPIO6 GPIO5 GPIO4 GPIO3 GPIO2 GPIO1 GPIO0
Device Device Device Device Device Device Device Device
pin pin pin pin pin pin pin pin
6 5 7 8 18 19 20 21

Ó2018 Tiny Mesh AS TM4000 Series Data Sheet V1.8 Page 33 of 59

 TM4000 Series
Digital Output Drive
GPIO 0 - 7, when configured as outputs, are capable of sinking or sourcing 2mA, which is sufficient for
driving a transistor or some high efficiency LEDs. When used to drive higher loads, the outputs must
be buffered by a transistor or similar, to provide sufficient drive current.
The two dedicated RSSI/ TX LED and Connection/ RX LED outputs have higher drive capacity, and should
be limited by an external resistor for a maximum sink or source load of 10mA.

PWM (Dimmer) Output

GPIO 7 may be configured for PWM output (Pulse Width Modulation), and used for light dimming or
motor speed control, by setting GPIO 7 CONFIGURATION = 3.
SET PWM commands will control the duty cycle of the output from 0 to 100%, providing full range
dimming control from fully off to fully on.

The default PWM value at Reset is configurable to any value between 0 to 100% by setting the PWM
DEFAULT parameter in Configuration Memory. The factory setting is 0.
The PWM switching frequency is fixed at 1 kHz

Analogue Input
Tinymesh™ Devices support two independent analogue inputs. The analogue function of GPIO 0 and
GPIO 1 may be individually enabled by changing the default configuration setting of GPIO 0
CONFIGURATION and GPIO 1 CONFIGURATION. The analogue inputs will be sampled at a sampling rate
as defined by the GPIO 0 ANALOGUE SAMPLING INTERVAL and GPIO 1 ANALOGUE SAMPLING INTERVAL
configuration settings. The Sample Rate may be set in increments of 10ms. The default setting is 100,
or one sample per second. The analogue value is calculated as a sliding average of the last eight
samplings. The analogue converters are preconfigured to use an internal 1.25V voltage reference. A
positive input voltage between 0 and 1.25V applied to an analogue input pin will be converted to a
positive number between 0 and 2047 (0x07FF). Out of range values will be reported as either 0 or
2047.

The analogue voltage value of the input signal may be calculated as:

Analogue voltage = Measured Value * 1.25 / 2047 [V]

Example:
Measured Value: 0x4CC
Convert to decimal: 0x4CC = 1228
Analogue voltage conversion: 1228*1.25 / 2047= 0.75 [V]
Please note that negative voltages or voltages above the device supply voltage may result in
permanent damage to the device, please reference the electrical specifications for details.

Ó2018 Tiny Mesh AS TM4000 Series Data Sheet V1.8 Page 34 of 59

 TM4000 Series
Analogue Input Event Triggering
The two analogue inputs GPIO0 and GPIO1 may be set to trigger ANALOGUE 0 INPUT TRIG or
ANALOGUE 1 INPUT TRIG event messages when the measured analogue values exceed or go below
defined threshold values. Configurable analogue High and Low settings may be used to create a
hysteresis, to avoid multiple messages to be generated if the analogue signal changes very slowly over
time, or is following a nonlinear curve. This will typically be the situation when analogue inputs are
used to sense temperature variations or battery voltage. By setting the GPIO ANALOGUE HIGH, and
ANALOGUE LOW Trig thresholds to different values, an event message will be triggered when the
sampled analogue signal passes through the hysteresis, from below the low trig value to above the
high trig value, or vice versa. Please see below examples for clarification.

Low to high trigger High to low trigger

Setting the Analogue Input Trigger Level

The analogue high and the low trigger level threshold values must be entered as two-byte values in
the GPIO analogue trigger parameters in Configuration Memory. The maximum trigger level values are
2047, or Hex 0x7FF, entered as High byte = 0x07, and Low byte = 0xFF.

Calculate the Trigger Value as: Trigger Value = Analogue trigger voltage * 2047/1.25

Example: Analogue trigger voltage = 0.75[V]

First find the Trigger Value = 0.75* 2047/ 1.25 = 1228

Divide the Trigger Value by 256 to find the Trigger High Byte value:

1228 / 256 = 4.796 => High Byte = 4

Then calculate the Low Byte value by subtracting the value of the High Byte from the Trigger Value:

1228 – (4 * 256) => Low Byte = 204 (Hex 0xCC).

Note: GPIO 0 and GPIO 1 are both pulled high by an internal 20k resistor when used for digital input
or output. The internal pull-up is disabled when used as analogue inputs, causing the impedance of
the analogue inputs to be in the +100kohm range.

Setting the Analogue Input Sampling Interval.

The analogue sampling interval may be set in steps of 10ms, by changing the GPIO 0 ANALOGUE
SAMPLING INTERVAL or GPIO 1 ANALOGUE SAMPLING INTERVAL for values between 0.01s and 2.55s. The
analogue measurement value is calculated as the sliding average value of the last eight samples. The
sliding average and the sampling interval may be used as a filter function to eliminate spurious
glitches in the measured voltage. The default sampling interval is set for 1 second.

Ó2018 Tiny Mesh AS TM4000 Series Data Sheet V1.8 Page 35 of 59

 TM4000 Series
End Device
A Tinymesh™ Device may be configured to function as an End Device by issuing the SET END DEVICE
MODE command from Configuration Mode.
On initial wakeup, the End Device will make a connection to the mesh by going through a normal
network connection procedure, similar to a Router Device.
When a connection has been established, the End Device will return to sleep mode, and only wake up
when one or more of the configured wakeup conditions have been met.
On subsequent wake-ups, the device will assume the previous binding still exists, transmit data if
required, wait for receipt acknowledgement and resume sleep.
If no acknowledgement is received after RF TRANSMIT RETRY LIMIT retries, the End Device will
attempt to create a new binding on next wake-up, unless the End Device has been configured for
connection to a FIXED DESTINATION ID. If no valid connection has been established during a period of
2 X CONNECT CHECK TIME, the End Device will return to sleep, and repeat the reconnect attempt on
next wake up.
On wakeup, the End Device will dispatch a message identifying the wakeup source, except for wake-
ups caused by the Pulse Counter input.
Before returning to sleep mode, the End Device will stay awake for a configurable END DEVICE WAIT
FOR COMMAND time, allowing an external application to act on the received data and dispatch a
serial data or command packet to the End Device.

End Devices will normally be in low power sleep mode, and may be configured to wake from sleep
from a number of different input sources:
• Pulse Counter Input
• Digital Input trigger
• Serial port (UART) input
• Timed Wakeup
Enable the desired wakeup source by setting the appropriate bits of the END DEVICE WAKEUP ENABLE
parameter. The END DEVICE WAKEUP ENABLE parameter is a bitmap of the different input conditions
allowed to wake the End Device. The default setting after configuring the End Device with the SET
END DEVICE MODE Command, is Timed Wakeup with IMA TIME = 10.
On Timed Wakeup, the End Device will send a STATUS MESSAGE (IMA) MESSAGE before returning to
sleep.

Additional to selecting the End Device wakeup sources, the END DEVICE WAKEUP ENABLE parameter
may be used to enable a timer function that forces the End Device to stay awake and receive
incoming Locator Beacons for a full HIAM time period, before dispatching data. See LOCATOR
FUNCTION for detailed information.

The different wakeup conditions each have different bitmap values. When setting up for multiple
simultaneous options, enter the sum of the bitmap values:
Wakeup Source Bit value Example Settings
Pulse Counter + Serial Port Digital Detect and
Timer Input dispatch locator
address
Pulse Counter 1 1
Digital Input 2 2

Serial Port 4 4

Timer 8 8 8

Wait for Locator Beacon 128 128

Wakeup Enable Parameter Value 9 4 2 136

Wake Up from Pulse Counter

Pulses detected by the pulse counter will wake the device when the pulse counter function has been
enabled. As a basis for power consumption calculations, the awake time without De-bounce Timing is
on average 3ms per pulse.
With De-bounce Timing active, the awake time increases to PULSE COUNTER DEBOUNCE Time + 3ms.
The average power consumption in while Active Mode is 5mA.
Enable Pulse Counter wakeup by setting bit #0 (adding the value 1) to END DEVICE WAKEUP ENABLE
configuration parameter

Ó2018 Tiny Mesh AS TM4000 Series Data Sheet V1.8 Page 36 of 59

 TM4000 Series
On wakeup from the pulse counter, the device will not dispatch data, but return directly to sleep
mode after detecting the pulse.

Wake Up from Digital Input

Enable the Digital Input wake up by setting bit #1 (adding the value 2) to the END DEVICE WAKEUP
ENABLE configuration parameter.
On wakeup, the device will dispatch a DIGITAL INPUT CHANGE DETECTED event message.
Set the GPIO TRIGGER CONDITION for the GPIOs that shall be used for device wakeup for High- Low
triggering.

Note: Only High – Low triggers will wake the device from sleep.

Wake Up from Serial Port UART

Enable wake up by setting bit #2 (adding the value 4) to the END DEVICE WAKEUP ENABLE
configuration parameter.
On wakeup, the device will dispatch a Serial Data packet, containing the received serial data.

Note: The device will require time to wake up from detecting the start bit of the incoming serial
data. Any data entered on the serial port while device is in sleep mode, must be preceded by a single
'0xFF' byte.

Wake Up from IMA Timer

End Devices may be set to wake up and transmit a STATUS MESSAGE (IMA) at timed intervals.
Enable Timed Wakeup by setting bit #3 (adding the value 8) to the END DEVICE WAKEUP ENABLE
configuration parameter.
On wake up, the device will dispatch a STATUS MESSAGE (IMA) event message.
The time base for the IMA timer is controlled by the 10-seconds IMA TIME BASE parameter. The
default setting for the IMA TIME BASE parameter is 6, providing a time base of 6*10 = 60 seconds for
the IMA TIME.
Single second time resolution is obtained by setting IMA TIME BASE =0. By selecting '0' for the IMA Time
Base, the End Device will always spend shortest possible time returning to sleep mode, regardless of
wake up source, thereby reducing power consumption to a minimum, while maintaining longest
possible life expectancy for the battery. Please refer BATTERY LIFETIME CONSIDERATIONS for
detailed information.

Examples:
To set 30 seconds time interval, set IMA TIME BASE = 0 and IMA TIME = 30
To set 20 minutes time interval, set IMA TIME BASE = 6 and IMA TIME = 20
To set 24 hour time interval, set IMA TIME BASE = 180 and IMA TIME = 48

Note: When Timed Wakeup is not in use, set IMA TIME BASE = 0 to minimize power consumption

Battery Lifetime Considerations

While in sleep mode, the power consumption of the End Device will be 0.5uA if the Sleep Timer
function is active and 0.3uA if the Sleep Timer is disabled. This consumption level is less than the
typical leakage current of most batteries.

Note: The sleep current estimates are based on an assumption that all GPIO pins are either
configured as outputs, or left floating or pulled high if configured as inputs. The internal pull-up is
enabled for all GPIOs that are configured as inputs, to enable wake-up from high to low transitions.
The same applies for the RTS/SLEEP input, the RXD input and the CONFIG input.

Ó2018 Tiny Mesh AS TM4000 Series Data Sheet V1.8 Page 37 of 59

 TM4000 Series
The determining factors for battery lifetime calculation will be how often the device is awake, for
how long time, and what is the power consumption of the device plus interfacing circuits while the
device is awake.

Number of instances Device type

Low Power High Power
Pulse Counts with De-bounce Timer off
Wake Time Res = 0 10 000 000 10 000 000
Wake Time Res = 6 600 000 600 000
Pulse counts with De-bounce Timer = 10ms 140 000 140 000
Message Transmissions in Walk by Mode 30 000 2 100
Message Transmission with Acknowledge in live mesh network 5 500 1 600
Key figures, instances per consumed mAh. Assumptions: RF Data Rate 5, RF POWER 5.

Analogue Port Sampling by End Devices

The Sliding Average function, employed when analogue ports are sampled by Router and Gateway
Devices (ANALOGUE INPUT), will not be activated by End Devices, as the time required for the sliding
average calculation would require the device to be kept awake, and power consumption would be too
high for normal battery operation.
When analogue port sampling is activated, by GPIO 0 or 1 set for Analogue Input, the device will stay
awake for at least one GPIO 0 ANALOGUE SAMPLING INTERVAL, or GPIO 1 ANALOGUE SAMPLING
INTERVAL to allow a timed STATUS MESSAGE (IMA) message to represent the current status of the
active analogue port(s).

Device Awake Output Function

In End Device applications, there will often be a need to power up external sensor devices only while
the device is awake. While in sleep mode, such sensors may represent an undesirable power
consumption, and should be switched off.
The Tinymesh™ Device supports external device power control by the Device Awake Output Function.
A dedicated GPIO output will go low on device wake-up, and return high as the device returns to low
power sleep mode. This output may be used to switch off power to external devices, e.g. using a
MOSFET transistor as the power switch.
Enable the Device Awake Output Function by selecting the desired GPIO port in the END DEVICE
AWAKE PORT parameter. Also, remember to activate the same GPIO for output function by setting the
port GPIO configuration for the port to act as a normally high output

Fixed Destination and “Walk By” Mode

End Devices and Routers may be configured to assume a permanent connection to a predefined device
UID.
When the FIXED DESTINATION ID parameter in CALIBRATION MEMORY has been changed to a value
different from the default 0 0 0 0 setting, the Router or End Device will always attempt delivery of
data packets to this UID, regardless of whether the previous delivery was acknowledged or not.
If no Acknowledge is received, the Router or End Device will attempt delivery RF TRANSMIT RETRY
LIMIT number of times before giving up. The End Device will then return to sleep, while a Router will
discard the packet as undeliverable.

The 'Walk By' mode is a variety of the Fixed Destination setting. 'Walk By' is enabled by selecting the
broadcast address '255 255 255 255' as the FIXED DESTINATION ID.
By enabling 'Walk By', the device will skip waiting for receipt acknowledge of dispatched data, and
End Devices immediately return to sleep mode after transmitting a data packet.
The Walk By function works for all types of message dispatches from a device, either the message is
from serial data received on the UART, a status-triggered message or generated by the internal IMA
timer.

Ó2018 Tiny Mesh AS TM4000 Series Data Sheet V1.8 Page 38 of 59

 TM4000 Series
Walk By is typically applied for metering and pulse counter applications, where updated STATUS
MESSAGE (IMA) messages should be transmitted at regular time intervals.
The STATUS MESSAGE (IMA) event message contains current status of all digital and analogue inputs,
device temperature and device voltage level, as well as the current status of the pulse counter, either
in 2- or 4-byte format

RF Frequencies, Output Power and Data Rates

Article Number RF Channel2 Output Power2 Data Rate2

TM4070 1: 865.100 MHz TM4070 1: 1.2 kbit/s
2: 865.300 MHz 1: -20 dBm 2: 4.8 kbit/s
3: 865.500 MHz 2: -10 dBm 3: 19.0 kbit/s (TM4170.X)
4: 865.700 MHz 3: 0 dBm 4: 32.768 kbit/s
5: 865.900 MHz 4: 5 dBm 5: 76.8 kbit/s
6: 866.100 MHz 5: 11 dBm 6: 100 kbit/s
7: 866.300 MHz 7: For future use
8: 866.500 MHz 8: 50kbit/s
9: 866.700 MHz
10: 866.900 MHz
11: 867.100 MHz
12: 867.300 MHz
13: 867.500 MHz
14: 867.700 MHz
15: 867.900 MHz
TM40803 1: 868.050 MHz TM4080 1: 1.2 kbit/s
2: 868.150 MHz 1: -20 dBm 2: 4.8 kbit/s
3: 868.250 MHz 2: -10 dBm 3: 19.0 kbit/s
4: 868.350 MHz 3: 0 dBm 4: 32.768 kbit/s
5: 868.450 MHz 4: 5 dBm 5: 76.8 kbit/s
6: 868.550 MHz 5: 11 dBm 6: 100 kbit/s
7: 868.650 MHz 7: For future use
8: 868.750 MHz 8: 50kbit/s
9: 868.850 MHz
10: 868.950 MHz
11: 869.050 MHz
12: 869.150 MHz
13: 869.525 MHz
14: 869.750 MHz
15: 869.850 MHz
16: 869.950 MHz
17: 869.475 MHz
18: 869.575 MHz
TM4090 50 channels: 1: -20 dBm 1: 1.2 kbit/s
2: -10 dBm 2: 4.8 kbit/s
902+n*0.5 MHz 3: 0 dBm 3: 19.0 kbit/s
for 4: 5 dBm 4: 32.768 kbit/s
n = channel [1, 50] 5: 11 dBm 5: 76.8 kbit/s
6: 100 kbit/s
default: 7: 250 kbit/s
4: 904.0 MHz 8: 50kbit/s
RF channel, output power level and data rate may be changed in configuration memory by using the
WRITE CONFIGURATION MEMORY in CONFIGURATION MODE, or by using the SET CONFIGURATION
COMMAND for system deployment, while the SYSTEM_ID is set at the factory default 0 0 0 1 value. The
default factory settings are shown in bold in the table above. For more details on changing the RF
channel, output power or data rate, refer to the description of the CONFIGURATION COMMANDS.

The use of RF frequencies, maximum allowed RF power and duty-cycles are limited by national
regulations.
TM4080 complies to the applicable directives within the European Union when used within these
limitations.
TM4080 channels 5-9 are license free channels within Russia.

2
RF Channel, Output Power and Data Rate must be set identical for all devices within a network, ref. note on page
16.
3 For channels 1, 6, 7, 12, 14 and 16, the maximum allowable RF-data rate is 19.2 kbit/s, due to limitations in

modulation bandwidth at the given sub band-edge.

Ó2018 Tiny Mesh AS TM4000 Series Data Sheet V1.8 Page 39 of 59

 TM4000 Series
TM4090 conforms to FCC regulations for use in the US and Canada. For more information see section
REGULATORY COMPLIANCE INFORMATION.

Ó2018 Tiny Mesh AS TM4000 Series Data Sheet V1.8 Page 40 of 59

 TM4000 Series
Device Configuration
Device configuration settings may be changed in-circuit from a host MCU during operation, at the
time of installation of the equipment, at the manufacturing test, or as wireless configuration
commands issued by the Gateway device in a live mesh network.

Configuration Commands
Tinymesh™ Devices may be configured during normal operation in an operating mesh network, by
using the SET CONFIGURATION COMMAND. Routers as well as Gateway Devices may be configured
using this method.

RF CHANNEL, RF DATA RATE, UNIQUE_ID and SYSTEM_ID may be changed by the SET CONFIGURATION
COMMAND while the SYSTEM_ID is set to the factory default value (0 0 0 1).

After the SYSTEM_ID has been changed to a value different from the default setting, the above
parameters will be locked for configuration, to avoid losing contact with an operating device in a
live network.

It is possible to override the configuration locking by setting the CONFIGURATION LOCK OVERRIDE
= 1.
After setting the desired parameters, it is advisable to reset the CONFIGURATION LOCK OVERRIDE
parameter to its default setting = 0.

Gateway Devices in PACKET MODE OPERATION may be forced to enter CONFIGURATION MODE by
issuing a SET GATEWAY IN CONFIG MODE command over the UART, as an alternate means to asserting
the CONFIG input low.

Configuration Mode Entry

Tinymesh™ devices will enter Configuration Mode by pulling the CONFIG pin low, for direct UART
configuration of the device. Configuration Mode operation allows a local MCU full control for
reconfiguration on the fly, useful for system development and test.

Configuration mode entry may be restricted or protected by a time-out by changing the value of the
CONFIGURATION MODE ENTRY CONTROL parameter.

Activate the automatic Configuration Mode Time Out control by setting CONFIGURATION MODE ENTRY
CONTROL parameter = 1. When Time Out is activated, the device will automatically exit Configuration
Mode if there has been no activity after a pre-set number of minutes, selected by the
CONFIGURATION MODE TIME OUT parameter.

Activate Two Step Configuration Mode Entry by setting the CONFIGURATION MODE ENTRY CONTROL
parameter = 2. When Two Step Entry is active, the device will issue a ‘?’ character prompt on the TXD
pin when the CONFIG pin is pulled low. The device will expect a single byte entry key to be entered as
response to the ‘?’ prompt.
The ‘?’ prompt will be repeated if an illegal key is entered. The default key value ‘K’ may be changed
by altering the CONFIGURATION MODE ENTRY KEY parameter.

Activate Two Step Configuration Mode Entry and Configuration Time Out by setting CONFIGURATION
MODE ENTRY CONTROL parameter = 3.

On entering Configuration Mode, the device will signal response to commands by sending a ‘>’ prompt
on the TXD pin. The prompt indicates that the device is ready to receive new commands.
The CONFIG pin may then be de-asserted.

Note that the CONFIG pin must be de-asserted before the Exit command (‘X’) is sent to the device, in
order to return to normal operation.

Ó2018 Tiny Mesh AS TM4000 Series Data Sheet V1.8 Page 41 of 59

 TM4000 Series
Configuration Mode commands
A ‘>’ prompt character from the Tinymesh Device indicates the Device is ready to receive a new
command. After a command has been executed, the device responds with the ‘>’ prompt character,
indicating it is ready for a new command.

New commands must not be entered before the ‘>’ prompt has been received. The time required to
execute a command may vary depending on the command. When writing to the Flash memory (M, HW
and @TM Commands), there will be a 300ms delay before the command is executed and the prompt is
transmitted. There is no ‘>’ prompt after the ‘X’ exit command.

Function Code Argument Response Note

ASCII (Hex)
Get Analogue ‘A’ No Argument. Four bytes GPIO 0 and GPIO (0,1) must be set as analogue
Port Values GPIO 1 Analogue Port Inputs
Input value
Get Digital Port ‘D’ No Argument. Single byte digital port GPIO(0_7) must be set as inputs
Values input value
Get RSSI ‘S’ (0x53) No Argument. Single byte RF signal See
strength
RSSI READING (S- Command)
Get ‘U’ (0x55) No Argument. Single byte device See TEMPERATURE READING (U-
Temperature temperature. COMMAND)
Get Voltage ‘V’ (0x56) No Argument. Single byte device See POWER SUPPLY VOLTAGE
supply voltage. READING (V- COMMAND)
Read ‘Y’ (0x59) Address Single byte Return single byte value from the
Configuration 0x00 – 0x7F configuration memory configuration memory.
Memory value.
Write ‘M’ (0x4D) Pairs of No Response See SET CONFIGURATION MEMORY
Configuration address and (M- COMMAND)
Memory data bytes.
Reset Memory ‘@TM' No argument No Response Restores configuration memory to
(0x40 0x54 factory default values.
0x4D)
Exit ‘X’ (0x58) No argument No Response Exit to normal operation mode. All
Configuration parameter changes take effect.
Mode
Set Router Mode ‘R’ (0x52) No argument No Response Set DEVICE TYPE =2,
Set HIAM TIME, CONNECT CHECK
TIME, and INDICATORS ON =
configured values.
Set Gateway ‘G’ (0x47) No argument No Response Set DEVICE TYPE =1,
Mode Set HIAM TIME and INDICATORS ON
= configured values.
Set End Device ‘N’ (0x4E) No argument No Response Set DEVICE TYPE = 3,
Mode Set CONNECT CHECK TIME, IMA
TIME and INDICATORS ON=
configured values.
Set Sleep Mode 'Z' (0x5A) No argument No Response See SET SLEEP MODE (Z-
COMMAND)
Alternate Set 'z' (0x7A) No argument No Response See ALTERNATE SET SLEEP MODE (z-
Sleep Mode Command)
Set AES Key 'K' (0x4B) Key index '7' No Response See SETTING AND CHANGING THE
(0x37), 16 AES KEY (K7- COMMAND)
bytes key
data.
Write 'HW' (0x48 Pairs of No Response See
Calibration 0x57) address and CHANGE CALIBRATION MEMORY
Memory data bytes. COMMAND (HW- COMMAND)
List Calibration 'r' (0x72) No argument Calibration Memory
Memory Contents
List ‘0’ (0x30) No argument Configuration memory
Configuration contents
Memory
Test Mode 1 ‘1’ (0x31) No argument No Response TX carrier ON
Test Mode 2 ‘2’ (0x32) No argument No argument TX modulated signal
Test Mode 3 ‘3’ (0x33) No argument No Response RX mode

Ó2018 Tiny Mesh AS TM4000 Series Data Sheet V1.8 Page 42 of 59

 TM4000 Series
Function Code Argument Response Note
ASCII (Hex)
RSSI Sniffer ‘5’ (0x35) Any input will Single byte RSSI for any See RSSI SNIFFER (TEST MODE 5)
exit and valid Tinymesh™ packet
return to RX received.
mode
Simple Packet '6' (0x36) Any input will RSSI and key packet See SIMPLE PACKET SNIFFER (TEST
Sniffer exit and details for any valid MODE 6)
return to RX Tinymesh™ packet
mode received.

Note: ASCII characters are written as ‘X’, hexadecimal numbers are written like 0x00, and decimal
numbers are written like 10 throughout the text.

Commands must be sent as ASCII characters or their corresponding binary value. All arguments must
be sent as binary values to the device (not as ASCII representation for hex or decimal). Any invalid
command will be ignored and the ‘>’ prompt will be resent. The CONFIG input must be de-asserted
after the first ‘>’ prompt was received, but before the ‘X’ command.

RSSI Reading (S- Command)

The device provides a digital Received Signal Strength Indicator (RSSI) through the ‘S’ command when
in Configuration Mode, and included in received messages when the Gateway Device is operating in
Packet Mode. The device returns an 8 bit character (one byte) indicating the current input signal
strength (followed immediately by a second character which is the prompt (‘>’) when in command
mode). The signal strength is used by the Tinymesh™ protocol to indicate fading margin, and as a
carrier sense signal to avoid collisions.

The signal strength measured by the S command is the instantaneous value. The ORIGIN RSSI value
included in the header portion of all received packets, is the signal strength at the originating device,
when receiving data from the device that has been selected as the first receiver of packets from the
originating device i.e. the first jump in the mesh network.

The RSSI value increases with increased input signal strength in 0.5 dB steps. Input signal strength is
given by (typ):

P = - RSSI / 2 [dBm]

The dynamic range of the RSSI (P) goes from the Sensitivity level up to typical -30 dBm (RSSI
saturation level).

Temperature Reading (U- Command)

The device provides readings of a digital temperature monitoring sensor (TEMP) through the ‘U’
command. The device returns an 8 bit character (one byte) indicating the current temperature in
degrees Celsius (°C) followed immediately by a second character which is the prompt (‘>’).
The TEMP value is also returned in all GENERAL EVENT PACKET FORMAT packets while the device is
operating in Packet mode
The TEMP value increases with increased temperature in 1 °C steps and accuracy of +/- 2 °C.
Temperature is given by:

T = TEMP(dec) - 128 [°C] (Example: TEMP=0x98 equals +24 °C)

Power Supply Voltage Reading (V- Command)

The device provides readings of an internal power supply voltage monitoring sensor (VCC) through the
‘V’ command. The device returns an 8 bit character (single byte) indicating the current power supply
voltage level, followed immediately by a second character which is the prompt (‘>’). The command
can be useful for battery voltage level monitoring.
The VCC value is also returned in all GENERAL EVENT PACKET FORMAT packets while the device is
operating in Packet mode

Ó2018 Tiny Mesh AS TM4000 Series Data Sheet V1.8 Page 43 of 59

 TM4000 Series
The VCC value increases with increased power supply voltage in 30 mV steps. The power supply
voltage is given by:

V = VCC(dec)*0.030 [V] (Example: VCC=0x68 equals 3.12 [V])

Set Configuration Memory (M- Command)

Configuration parameters in non-volatile CONFIGURATION MEMORY may be changed using the 'M'
command

Example: To select Channel 3, change contents of memory address 0x00 to new value 0x03.

Command Hex Response Comment

Enter Configuration '>' By Asserting and releasing the CONFIG input, or
Mode By issuing the SET GATEWAY IN CONFIG MODE command to a
Gateway Device
'M' 0x4D '>' Wait for '>' prompt
0 0x00 No response Address byte received, waiting for Data byte
3 0x03 No response Data byte received, device waiting for next address or 255 (0xFF)
to terminate Memory Configuration
255 0xFF '>' Wait tMEMORY-CONFIG for ‘>’ prompt
New command The device remains in Configuration Mode until 'X' command
received
'X' 0x58 No response The TinymeshTM protocol runs through a full Power On Reset Cycle,
to ensure all configuration changes are applied.

Set Sleep Mode (Z-Command)

The ‘Z’ command will set a device in temporary low power sleep mode. The device will only accept
the ‘Z’- command if the CONFIG input pin is low.
The device will enter sleep mode immediately on receiving the ‘Z’ byte, and will remain in SLEEP
mode until the CONFIG Input is driven high, or the device receives an external RESET.

Note: The internal RTS/ SLEEP and CONFIG input pull-up resistors are disabled during sleep mode to
reduce excessive power leakage. The CONFIG and SLEEP inputs must therefore be actively driven to
the logic high state to exit sleep mode.

Alternate Set Sleep Mode (z-Command)

The ‘z’ command will set a device in temporary low power sleep mode. The device will enter sleep
mode immediately on receiving the ‘z’ byte, and will remain in sleep mode until a new start bit (high
to low transition) is received on the UART RXD pin.
The device will accept the ‘z’- command regardless of status of the CONFIG input pin.

Setting and Changing the AES key (K7- Command)

The default AES key 'TinyMeshAESKey#7' has been pre-loaded to all devices shipped from factory.
Initial testing of encrypted communication may be performed using the default key, but systems
should not be deployed until a new, secret 16-byte key has replaced the default key.
AES keys are stored in a dedicated part of flash memory that is not readable by the '0' and 'r'
Configuration Mode commands. After entering a new AES key, there is no way for reading the key
back. If there is uncertainty as to what key has been entered in a device, the only way to make sure
is to reprogram the key. The key storage part of flash is also retained during an '@TM' factory reset of
flash memory, and may not be changed using the 'M' or 'HW' commands.

Ó2018 Tiny Mesh AS TM4000 Series Data Sheet V1.8 Page 44 of 59

 TM4000 Series
The AES Key may only be changed using the 'K' command while the device is in Configuration Mode.
The following steps should be used to program a new 16-byte key with value 'A B C D E F G H I J K L M
N O P':

Command Hex Response Comment

Enter Configuration '>' By Asserting and releasing the CONFIG input, or
Mode By issuing the SET GATEWAY IN CONFIG MODE command to a
Gateway Device
'K7' 0x4B '>' Wait for '>' prompt
0x37
'A B C D E F G H I J K L '>' Note there is a 10 second maximum time-out between characters
M N O P'
'X' 0x58 No response The TinymeshTM protocol runs through a full Power On Reset Cycle,
to ensure all configuration changes are applied.

Change Calibration Memory Command (HW- Command)

Configuration parameters in non-volatile CALIBRATION MEMORY may be changed using the WRITE
CALIBRATION MEMORY command. See examples below: CALIBRATING THE TEMPERATURE SENSOR,
SETTING AND CHANGING THE NETWORK ID (NID) and SETTING AND CHANGING THE FIXED DESTINATION
ID (FDID).

Calibrating the Temperature Sensor

The internal temperature sensor may require calibration to show correct value. The TEMP OFFSET
parameter in CALIBRATION MEMORY is used for temperature calibration in steps of 0.25 degree
Celsius.
To calibrate the temperature sensor, place the TinymeshTM device in a temperature controlled
environment, enter CONFIGURATION MODE and make sure the device is given sufficient time to adapt
to the environmental temperature.
Read back the current value of the temperature sensor using the GET TEMPERATURE command.
Calculate the actual temperature using the formula in TEMPERATURE READING (U- COMMAND), and
find the offset as the difference between actual room temperature and the sensor reading.
Multiply the found difference by 4 and subtract from the TEMP OFFSET, if the sensor is showing too
high value, or add to the TEMP OFFSET if the sensor is showing too low temperature.
Verify the sensor calibration by repeat readings using the 'U' command

Example:
To calculate a new temperature offset
Room temperature: 24 [°C]
Device reading (U- command): 0x9A = decimal 154
1) Convert device reading to temperature in °C: 154-128 = 26 [°C]
2) Calculate the temperature error reading: 24 – 26= -2 [°C]
3) Calculate the compensation offset: -2 * 4 = -8
4) Calculate the new Temp Offset value: Temp Offset= TempOffset -8

If TEMP OFFSET is currently set at the factory default 128, the new TEMP OFFSET will be 120

Command Hex Response Comment

Enter Configuration '>' By Asserting and releasing the CONFIG input, or
Mode By issuing the SET GATEWAY IN CONFIG MODE command to a
Gateway Device
'HW' 0x48 '>' Wait for '>' prompt
0x57
0 0x00 No response Address byte received, waiting for Data byte
120 0x03 No response Data byte received, device waiting for next address, or 255 (0xFF)
to terminate Memory Configuration
255 0xFF '>' Wait tMEMORY-CONFIG for ‘>’ prompt

Ó2018 Tiny Mesh AS TM4000 Series Data Sheet V1.8 Page 45 of 59

 TM4000 Series
New command The device remains in Configuration Mode until 'X' command
received
'X' 0x58 No response The TinymeshTM protocol runs through a full Power On Reset Cycle,
to ensure all configuration changes are applied.

Setting and Changing the Network ID (NID)

The Tinymesh™ NETWORK ID is an additional level of network addressing that may be deployed to
distinguish between multiple Tinymesh™ networks sharing a common platform or server, such as the
Tinymesh™ Cloud service.

The NETWORK ID needs only be entered in the Gateway Device(s), and has no effect on the internal
addressing in the individual Tinymesh™ networks. By entering unique NETWORK IDs in the Gateway
Devices, different local networks having identical SYSTEM_ID, may still be differentiated on a larger
platform, as the NETWORK ID will serve as an additional level of systems identification that provides
differentiation between messages originating from different systems with identical SYSTEM_ID.

The NETWORK ID is stored in the Calibration part of Flash memory. This part of flash is retained even
after a RESET MEMORY command, and may only be changed using WRITE CALIBRATION MEMORY
command from Configuration Mode. The LIST CALIBRATION MEMORY command may be used to read
back and verify the contents the CALIBRATION MEMORY. The following steps should be used to program
a new NETWORK ID with value 4 3 2 1.

Command Hex Response Comment

Enter Configuration '>' By Asserting and releasing the CONFIG input, or
Mode By issuing the SET GATEWAY IN CONFIG MODE command to a
Gateway Device
'HW' 0x48 '>' Wait for '>' prompt
0x57
23 1 24 2 25 3 26 4 No response Four pairs of address and data received, device waiting for next
or Hex: address or 255 (0xFF) to terminate the command
0x17 0x01 0x18 0x02
0x19 0x03 0x1A 0x04
255 0xFF '>' Wait tMEMORY-CONFIG for ‘>’ prompt
'r' 0x72 Calibration Read back the Calibration Memory contents to verify correct
Memory settings
'X' 0x58 No response The TinymeshTM protocol runs through a full Power On Reset Cycle,
to ensure all configuration changes are applied.

Setting and Changing the Fixed Destination ID (FDID)

A Tinymesh™ device may be forced to assume a permanent network connection by setting the FIXED
DESTINATION ID to a value different from the default 0:0:0:0 setting. A FIXED DESTINATION ID may be
useful in systems using sleeping devices, where the device should spend as little time as possible
making a network connection after wakeup.

Note: A device that has been configured with FIXED DESTINATION ID will skip the normal procedure of
searching for the best available network connection, and will not support Self-forming, Self-healing
and Self-optimizing.

The FIXED DESTINATION ID is stored in the Calibration part of Flash memory. This part of flash is
retained even after a RESET MEMORY command, and may only be changed using WRITE CALIBRATION
MEMORY command from Configuration Mode. The LIST CALIBRATION MEMORY command may be used to
read back and verify the contents the CALIBRATION MEMORY. The following steps should be used to
program a new FIXED DESTINATION ID with value 4 3 2 1.

Command Hex Response Comment

Ó2018 Tiny Mesh AS TM4000 Series Data Sheet V1.8 Page 46 of 59

 TM4000 Series
Enter Configuration '>' By Asserting and releasing the CONFIG input, or
Mode By issuing the SET GATEWAY IN CONFIG MODE command to a
Gateway Device
'HW' 0x48 '>' Wait for '>' prompt
0x57
27 1 28 2 29 3 30 4 No response Four pairs of address and data received, device waiting for next
or Hex: address or 255 (0xFF) to terminate the command
0x1B 0x01 0x1C 0x02
0x1D 0x03 0x1E 0x04
255 0xFF '>' Wait tMEMORY-CONFIG for ‘>’ prompt
'r' 0x72 Calibration Read back the Calibration Memory contents to verify correct
Memory settings
'X' 0x58 No response The TinymeshTM protocol runs through a full Power On Reset Cycle,
to ensure all configuration changes are applied.

RSSI Sniffer (Test Mode 5)

When set to Test Mode 5, the device will output a single byte, received RSSI level for any received
and correctly formatted Tinymesh™ packet. Only packets with matching SYSTEM_ID will be accepted
by the RSSI Sniffer function.

Simple Packet Sniffer (Test Mode 6)

When set to Test Mode 6, the device will output the received RSSI level for any received and correctly
formatted Tinymesh™ packet, followed by a limited set of descriptive data derived from the received
packet. Only packets with matching SYSTEM_ID will be accepted by the Sniffer function.

Simple Packet Sniffer Output Format:

|RSSI|Packet Size|Destination ID|Source ID|Origin Jump Level|Packet Type|Message Counter*

*The Sniffer output is 12 or 14 bytes per packet. There is no Message Counter if the received packet is
an ACK or a Beacon packet.

Simple Packet Sniffer Format Details:

Byte Name Description

1 RSSI Signal Strength of packet as received by Sniffer Device

2 Packet Total length of packet, including header and payload data. Length will vary
Length with Packet Type (see below)
3-6 Destination Next receiver of this packet. (Final destination is always Gateway Device)
ID
7-10 Source ID Last transmitter of this packet. (Not device that created the packet)
11 Origin Jump Jump level of device that created this packet
Level
12 Packet Type Packet Type Packet Length Description

0x02 0x2D Event Message, ref. Received Packet Formats

0x95 Response to GET CONFIGURATION MEMORY
command

Variable Response to GET PACKET PATH and Encrypted

packets
0x03 0x1F Control and Status Request Command, ref.
TRANSMITTING COMMAND AND
CONFIGURATION PACKETS FROM GATEWAY

Ó2018 Tiny Mesh AS TM4000 Series Data Sheet V1.8 Page 47 of 59

 TM4000 Series
0x3D Change Configuration Command, ref.
TRANSMITTING COMMAND AND
CONFIGURATION PACKETS FROM GATEWAY

0x04 Variable Encrypted Command

0x0A 0x11 Acknowledge (Link level)
0x0B 0x11 Beacon (Network Invite)
0x0C 0x11 Beacon from Locator Device, ref. LOCATOR
FUNCTION

0x0E 0x11 Connection Request

0x10 0x1E to 0x95 Serial data to Gateway, ref. RECEIVED PACKET
FORMATS

0x11 0x1E to 0x95 Serial data from Gateway, ref. TRANSMIT

SERIAL DATA PACKET FROM GATEWAY

0xFF Unknown Packet Type

13 Message Sequential counter maintained by originating device.
Counter Not applicable for 0x0A,0x0B,0x0C and 0x0E packets

Note: While processing serial port output data, the device may not be able to receive new RF data
packets.
To avoid losing data, the transfer speed should be set to the highest acceptable data rate. The
Tinymesh™ Device will support data rates up to 230 400 by setting the UART BAUD RATE parameter in
Configuration Memory.

Ó2018 Tiny Mesh AS TM4000 Series Data Sheet V1.8 Page 48 of 59

 TM4000 Series
Configuration Memory
The table below shows the complete list of configurable parameters stored in non-volatile
Configuration memory. These values may be changed using the ‘M’ command while the device is in
Configuration Mode (page 41), or through Gateway Commands (page 22). All addresses and arguments
must be sent as binary values to the device (not as ASCII representation for hex or decimal).
The FW column indicates first Tinymesh™ firmware release supporting the referenced parameter.
Parameter Description Addr Argument Factory Comment FW
setting
Radio and protocol configuration
RF CHANNEL RF channel 0 TM4070: 1-15 4 See table RF FREQUENCIES,
TM4080: 1-18 OUTPUT POWER AND DATA
TM4090: 1-50
RATES for details.
RF POWER RF output power 1 1-5 TM4X70.X: 5 See table RF FREQUENCIES,
TM4X80.X: 5 OUTPUT POWER AND DATA
TM4X90.X: 3
RATES for details
Power setting must be identical
for all devices in a network
RF DATA RATE RF data rate 2 TM4070: 1-6, 8 TM 40XX.X: 5 See table RF FREQUENCIES,
TM4080: 1-6, 8 TM 41XX.X: 3 OUTPUT POWER AND DATA
TM4090: 1-8
RATES for details
Protocol Mode Packet format selection 3 Transparent:14 1 See TRANSPARENT VERSUS
Packet: 0 PACKET MODE OPERATION
RSSI Acceptance Minimum RSSI to accept 4 160- 210, 255 2555 Auto Selected RSSI Acceptance
level network connection TM 41XX.X: N/A levels at given RF DATA RATEs:

1 2 3 4 5 6 7 8
208 200 196 190 186 182 178 188
RSSI Clear Channel Max RSSI for Clear 5 100- 210 140 Do not change
Assessment level Channel during Listen
Before Talk
HIAM Time Time in seconds 6 1-8, 255 2555 Auto Selected values at given RF
between network TM 41XX.X Router: N/A DATA RATEs:
invites TM 41XX.X Gatew: 1
1 2 3 4 5 6 7 8
6 5 4 3 1 1 1 1

IMA Time Time in minutes 7 1-255 Router and G- Note5

between automatic 255= never way: 255
End Dev.: 10
status messages
Connect Check Time Time in seconds 8 1-255 2555 Auto Selected values at given RF
between network DATA RATEs:
evaluation
1 2 3 4 5 6 7 8
24 20 16 12 4 4 4 4
Max Jump Level Highest allowable 9 1-2556 20
network jump level
(hop level)
Max Jump Count Maximum number of 10 1-2556 30
transportation jumps
(hops) before a packet
is eliminated, assumed
undeliverable.
Max Packet Latency Maximum transport 11 1-2556 5 10ms to 652.8 s.
time before a packet (5* Calculated from a time base of
is eliminated, assumed 256*10ms=12 either 10 ms or 256*10ms, as
undeliverable. .8 sec) selected by MAX PACKET
LATENCY TIME BASE
RF Transmit Retry Number of unsuccessful 12 1-2556 100
Limit RF retries before a
Router Device
disconnects and
attempts re-connection
to the network.
Serial Port Time Out Time out in periods of 13 1-2557 20 An additional 2ms is automatically
1ms between character added.
inputs on serial port, Actual timing for setting 20 is 22
before a ms
packet is transmitted in
Transparent mode.

4
Values greater than '1' treated as '1'
5 Set by ‘G’, ‘R’, 'N'-command in Configuration Mode
6 Zero value treated as 1
7
After adding 2, values 254 and 255 will be interpreted as 255

Ó2018 Tiny Mesh AS TM4000 Series Data Sheet V1.8 Page 49 of 59

 TM4000 Series
Parameter Description Addr Argument Factory Comment FW
setting
Device Type Selection sets the 14 1-38 2 1 = Gateway Device
device operating mode, 2 = Router Device
as Gateway, Router or 3 = End Device
End Device. Set by 'G', 'R', 'N' commands in
Configuration Mode
Excellent RSSI Level 15 0-255 150 Do not Change
GPIO 0 Configuration Configure GPIO 0/ 16 0,1,2,49 1 0 = Output, default High
Device Pin 21 1 = Input
2 = Analogue in
4 = Output, default Low
GPIO 1 Configuration Configure GPIO 1/ 17 0,1,2,49 1 0 = Output, default High
Device Pin 20 1 = Input
2 = Analogue in
4 = Output, default Low
GPIO 2 Configuration Configure GPIO 2/ 18 0,1,49 1 0 =Output, default High
Device Pin 19 1 = Input
4 = Output, default Low
GPIO 3 Configuration Configure GPIO 3/ 19 0,1,49 1 0 = Output, default High
Device Pin 18 1 = Input
4 = Output, default Low
GPIO 4 Configuration Configure GPIO 4/ 20 0,1,49 1 0 = Output, default High
Device Pin 8 1 = Input
4 = Output, default Low
GPIO 5 Configuration Configure GPIO 5/ 21 0,1,49 1 0 = Output, default High
Device Pin 7 1 = Input
4 = Output, default Low
GPIO 6 Configuration Configure GPIO 6/ 22 0,1,49 1 0 = Output, default High
Device Pin 5 1 = Input
4 = Output, default Low
GPIO 7 Configuration Configure GPIO 7/ 23 0,1,3,49 1 0 = Output, default High
Device Pin 6 1 = Input
3 = PWM output
4 = Output, default Low
GPIO 0 trig Trigger an event on 24 0-310 0 0 = No trig
input level change if 1 = Rising edge
port set as input 2 = Falling edge
3 = Both edges
GPIO 1 trig Trigger an event on 25 0-310 0 0 = No trig
input level change if 1 = Rising edge
port set as input 2 = Falling edge
3 = Both edges
GPIO 2 trig Trigger an event on 26 0-310 0 0 = No trig
input level change if 1 = Rising edge
port set as input 2 = Falling edge
3 = Both edges
GPIO 3 trig Trigger an event on 27 0-310 0 0 = No trig
input level change if 1 = Rising edge
port set as input 2 = Falling edge
3 = Both edges
GPIO 4 trig Trigger an event on 28 0-310 0 0 = No trig
input level change if 1 = Rising edge
port set as input 2 = Falling edge
3 = Both edges
GPIO 5 trig Trigger an event on 29 0-310 0 0 = No trig
input level change if 1 = Rising edge
port set as input 2 = Falling edge
3 = Both edges
GPIO 6 trig Trigger an event on 30 0-310 0 0 = No trig
input level change if 1 = Rising edge
port set as input 2 = Falling edge
3 = Both edges
GPIO 7 trig Trigger an event on 31 0-310 0 0 = No trig
input level change if 1 = Rising edge
port set as input 2 = Falling edge
3 = Both edges
Input De-bounce De-bounce time in ms 32 0-255 10
for all inputs
GPIO 0 Analogue High byte of two byte 33 0-7 7
High trig High byte High Trig level value
GPIO 0 Analogue Low byte of two byte 34 0-255 255
High Trig Low byte High Trig level value
GPIO 0 Analogue High byte of two byte 35 0-7 0
Low Trig High byte Low Trig level value

8
Values different from 1 or 3 will be treated as 2 (Router)
9
Values out of range will be treated as 1 (Input)
10
Values out of range will be treated as 0 (No Trig)

Ó2018 Tiny Mesh AS TM4000 Series Data Sheet V1.8 Page 50 of 59

 TM4000 Series
Parameter Description Addr Argument Factory Comment FW
setting
GPIO 0 Analogue Low Low byte of two byte 36 0-255 0
Trig Low byte Low Trig level value
GPIO 0 Analogue Time between 37 0-255 100
Sampling Interval samplings in 10ms
increments
GPIO 1 Analogue High byte of two byte 38 0-7 7
High trig High byte High Trig level value
GPIO 1 Analogue Low byte of two byte 39 0-255 255
High trig Low byte High Trig level value
GPIO 1 Analogue High byte of two byte 40 0-7 0
Low trig High byte Low Trig level value
GPIO 1 Analogue Low byte of two byte 41 0-255 0
Low trig Low byte Low Trig level value
GPIO 1 Analogue Time between 42 0-255 100
Sampling Interval samplings in 10ms
increments
CTS hold time CTS hold time in 10ms 43 1-2556 6 (60 ms) Active on Gateway only.
increments
Locator_Enable Enable locator function 44 0 or 1 0
UNIQUE_ID0 (UID0) 45 0-255 1
UNIQUE_ID1 (UID1) 46 0-255 0 UID=
UID3:UID2:UID1:UID0
UNIQUE_ID2 (UID2) 47 0-255 0 UID 0 0 0 0 is not allowed
UNIQUE_ID3 (UID3) 48 0-255 0
SYSTEM_ID0 (SID0) 49 0-255 1
SYSTEM_ID1 (SID1) 50 0-255 0 SID=
SYSTEM_ID2 (SID2) 51 0-255 0 SID3:SID2:SID1:SID0
SYSTEM_ID3 (SID3) 52 0-255 0 SID 0 0 0 0 is not allowed
Data and configuration interface, UART Serial Port
UART Baud Rate Baud rate 53 1: 2 400 5 BE CAREFUL WHEN CHANGING, AS
2: 4 800 HOST MAY LOOSE CONTACT WITH
3: 9 600 THE DEVICE!
4. 14 400
5: 19 200
6: 28 800
7: 38 400
8: 56 700
9: 76 800
10: 115 200
11: 230 400
UART Bits 54 8 or 911 8 Enable Parity by 9-bit word
UART Parity 55 0 or 112 0 0= Even / 1= Odd Parity
UART Stop Bits 56 1 or 213 1 Number of stop bits
Reserved 57 Do not change
UART Flow Control Select handshake: 58 01-127 1 (0x01)= Reference SERIAL PORT
CTS (1) CTS enabled HANDSHAKE
RTS (2) Add setting values to combine
RXTX (4) modes:
Xon/Xoff (8) RTS+CTS = 1+2=3
ACK/ NAK (16) CTS should always be active,
Wait For ACK (32) except in mode 4 (RXTX)
CRC Append (64)
Serial Buffer Full 59 0-100 18 Number of bytes left in Serial
Margin Buffer when CTS goes false and /or
Xoff transmitted
Device description
PART Number 60-68 RF TMxxxx Not Configurable
or
RF TMxxxx.x
60-70
Fill Byte 69 44 (,) Delimiter byte between Part
or Number and Hardware Revision
71 Not Configurable
HW Revision 70-73 x.yz x, y and z; Any number
or 0-9 ASCII
72-75 Not Configurable
Fill Byte 74 44 (,) Delimiter byte between Hardware-
or and Software Revision
76 Not Configurable
FW Revision 75-78 x.yz x, y and z; Any number
or 0-9 ASCII
77-80 Not Configurable

11
Value different from 9 will be treated as 8
12
Value different from 1 will be treated as zero (no parity)
13
Value different from 2 will be treated as 1 (Single stop bit)

Ó2018 Tiny Mesh AS TM4000 Series Data Sheet V1.8 Page 51 of 59

 TM4000 Series
Parameter Description Addr Argument Factory Comment FW
setting
Miscellaneous settings
Security Level Selected encryption 81 0-214 0 Selected Security Level.
mode 0: Off Mode 2 will reduce packet size to
1: On be compatible with unencrypted
2: Compatible systems
Reserved 82,
83
Max Packet Latency Time Base forMAX 84 0/1 1 0=10 ms time resolution
Time Base PACKET LATENCY 1= 2560ms time resolution
calculation.
IMA time base Time Base for IMA Timer 85 1-255 6 Default setting of 6 sets IMA timer
and End Device wake- to 1 minute resolution
up, in periods of 10
seconds
End Device Wait for End Device, periods of 86 0-255 0
Command 0.1 seconds to wait for
command before
returning to sleep
End Device Wakeup Bitmap of signals that 87 0-143 8 Bit-map of signals that may wake
Enable are allowed to wake End Device
End Device (Bit 0 : 0 Bit 0 (bit value 1):Pulse Counter
Bit 1 : 0 Bit 1 (bit value 2): GPIO
Bit 2 : 0 Bit 2 (bit value 4): Serial Port
Bit 3 : 1) Bit 3 (bit value 8): IMA Timer
Bit 7 (bit value 128): Enable wait for
Locator Beacon

Add bit values to set desired

combination.

Example:
Select 8+2 = 10 for IMA timer+ GPIO
Configuration Mode Additional security for 88 0: No Security 0 Provides additional security against
Entry Control entering Configuration 1: Time Out undesired entry in Configuration
Mode 2: Two Step Entry Mode
3: Time Out + Two
Step Entry
Indicators On Time-out in minutes for 89 0-255 Router and Should be set to 1 or low value for
Connect, RSSI and 0: Always Off G-way: 255 End Devices, to minimize power
Feedback indicators 255: Always On End Device: consumption5
1
Receive Neighbour Accept messages from 90 0/1 0
Messages direct neighbour nodes 0: Off
for serial port output 1: On
Command Enable command 91 0/1 1 Applicable in packet mode only.
Acknowledge acknowledge from 0: Off Not applicable for Gateway Device
destination device 1: On
Reserved 92
Sleep or RTS Set function for RTS / 93 0/1 0
SLEEP pin 0: RTS
1: Sleep
IMA On Connect Enable automatic IMA 94 0/115 0 See IMA ON CONNECT FUNCTION
message on Network 0: Off for details
connection 1: On
PWM Default Default PWM duty-cycle 95 0-10016 0 See PWM (DIMMER) OUTPUT for
at Reset details
Pulse Counter Mode Enables the pulse 96 0: Off 0 Bit map of selections
counter function 1: On,W/ Pull Up Bit 0 (bit val. 1): PC On / Off
3: On,W/O Pull Up Bit 1 (bit val. 2): Pull Up Disable

Pulse Counter De-bounce time in ms 97 0-255 0 = no de-

Debounce for Pulse counter bounce
Connection Change Minimum difference in 98 0-255 12 Do not Change
Margin RSSI to justify
automatic change of
network connection
Clustered Node Minimum number of 99 5-100 10 Closely located nodes are forced to
Device Limit densely located nodes act as a single node by reducing
required to be defined network Beacon (HIAM) activity
as a cluster
Clustered Node RSSI RSSI level to form a 100 40-100 60
node cluster

14
Unrecognised values will be treated as 1 (Encrypted)
15
Value different from 0 will be treated as 1 (On)
16
Out of range values will be treated as 0

Ó2018 Tiny Mesh AS TM4000 Series Data Sheet V1.8 Page 52 of 59

 TM4000 Series
Parameter Description Addr Argument Factory Comment FW
setting
Detect Network Busy Gateway action when 101 0-317 0 Applicable in Packet mode only
network activity 0: Ignore
detected after Reset. 1: Halt+Warn
2: Warn
RF Jamming Detect RF Jamming Detection 102 0-100 0 = Off Minimum time in minutes of
Time continuous radio jamming
on all radio channels before an RF
Jamming alarm is generated
RF Jamming Alarm GPIO port used for RF 103 0-7, 255 255 The selected GPIO will go LOW on
Port Jamming alarm output alarm status, and
0-7:Selected port will remain LOW for as long as
255: Disabled18 alarm status is present.
Note: Selected GPIO must be
configured for High Output
Feedback Port GPIO selection for Pulse 104 0-7, 255 255 Port configuration must be set for
Counter Feedback Output
0-7: Selected port
255: Disabled18
Feedback Enable Select event types that 105 0,2 0
will generate feedback 0: No Feedback
flash 2: Pulse Count
IMA Message Data Selects contents of 106 0-6 0
Field Contents Message Data field in 0 : No data
IMA Message 1: GPIO Trig-hold
2: Pulse Counter
5: My Connects
6: MyLocatorRSSI
IMA Message Address Selects contents of 107 0-4 2
Field Contents Address Data field in 0: No Data
IMA Message 1: Pulse Counter
2: Locator ID
3: Destination ID
4: Alternate
Destination ID
Trig Hold Bitmap of triggered 108 0-255 0 1: GPIO 0 16: GPIO 4
GPIO inputs that will be 2: GPIO 1 32: GPIO 5
reported next IMA 4: GPIO 2 64: GPIO 6
period 8: GPIO 3 128:GPIO7
Add values for multiple ports
Example: 7= GPIO 0+1+2
Port must be enabled for trig
End Device Awake Selects GPIO to signal 109 0-7, 255 255
Port Awake condition for 0-7: Selected Port
End Device 255: Disabled
Configuration Lock Enables configuration 110 0: Locked 0
Override of locked parameters 1: Lock Override
when SID not 0 0 0 1
Reserved 111-
112
Group Table Group IDs that this 113- 0-255 0,0,0,0, See Page 22 for Group addressing
node belongs to 120 0,0,0,0
Accept New Minimum time before 121 0-255 10 Do Not Change
Command Time Out new command
accepted (10 ms)
Command Retry Retries if no response 122 0-127 4 (40XX.X) Do not Change
to command transmit 2 (41XX.X) Gateway Device uses double
setting value.
MAC RndTime2Mask Radio State 1 max. 123 0x7F, 0x3F, 0x1F, 0x3F Do not Change
delay mask. Repeat TX 0x0F, 0x07,0x03, 0x1F
255
MAC RndTime1Mask Radio State 1 max. 124 0x7F, 0x3F, 0x1F, 0x0F Do not Change
delay mask. First TX 0x0F, 0x07,0x03
Reserved 125
Reserved 126,
127

17
Value larger than 2 will be treated as 2
18
Out of range values will be treated as Disabled

Ó2018 Tiny Mesh AS TM4000 Series Data Sheet V1.8 Page 53 of 59

 TM4000 Series
Calibration Memory
The table below shows the complete list of parameters stored in non-volatile Calibration memory.
These values may be changed using the ‘HW’ command while the device is in Configuration Mode
(page 41). All addresses and arguments must be sent as binary values to the device (not as ASCII
representation for hex or decimal).

Parameter Description Addres Argument Factory Comment FW

s
setting
Radio and protocol configuration
Temp Offset Offset added to 0 0-255 128 Temperature offset in 0.25
TEMP degree (C) increments.
Increase for positive
adjustment, decrease for
negative adjustment of TEMP
value
RFPower5 1 0-255 Factory set, do not change
FREQOFF 2 0-255 Factory set, do not change
Configuration Automatic Time Out 3 0-255 2 Minutes timer. Activated by
Mode Time Out setting for Configuration Entry Control
Configuration Mode setting
Configuration Key Entry for Two 4 0-255 ‘K’ (0x4B) Activated by Configuration
Mode Entry Key Step Configuration Entry Control setting
Mode Entry
Pulse Counter Pointer to Pulse 5, 6 0-255 2 Do not change
Index Counter Save
Pulse Counter Pulse Counter Save 7..22 0-255 16 Do not change
Save Memory
Network ID NID 0 23 0-255 0 Unique identifier for host
NID 1 24 0-255 0 network and Tinymesh CloudTM
NID 2 25 0-255 0 NID=
NID 3 26 0-255 0 NID3:NID2:NID1:NID0
Fixed Destination FDID 0 27 0-255 0 Permanent Router or End
ID FDID 1 28 0-255 0 Device connection address.
FDID 2 29 0-255 0 FDID=
FDID 3 30 0-255 0 FDID3:FDID2:FDID1:
FDID0
Default = 0:0:0:0 Function
disabled
S4 TimeOut Additional delay in 31 0-255 0 Do not Change
RF State 4
Dispatch Delay Additional delay for 32 0-255 0 Do not Change
Dispatch Timer
S4 Command Wait Additional command 33 0-255 0 Do not Change
response wait time
in RF State 4
Device Identifier Reserved space for 34-41 0-255 0,0,0,0,0,0 Do not Change
device type ,0,0
identifier

Ó2018 Tiny Mesh AS TM4000 Series Data Sheet V1.8 Page 54 of 59

 TM4000 Series
Absolute Maximum Ratings
Parameter Min Max Unit
Supply Voltage, VCC -0.3 3.9 V Caution! ESD sensitive devises.
Voltage on any pin -0.3 VCC+0.3V, Precaution should be used when handling
never the device in order to prevent permanent
V damage.
exceeding
Max value
Input RF level 10 dBm
Storage temperature -50 150 °C
Operating temperature -40 85 °C

Under no circumstance, the absolute maximum ratings given above should be violated. Stress
exceeding one or more of the limiting values may cause permanent damage to the device.

Electrical Specifications
T=25°C, VCC = 3.0V if nothing else stated.
Parameter Min Typ. Max Unit Condition / Note
Operating frequency
TM4070 865.0 865.700 867.0
TM4080 868.0 868.350 870.0
MHz
TM4090 902.0 904.000 928.0

Number of channels
TM4070 15
TM4080 18
TM4090 50

Input/output impedance
50 Ohm

Data rate 1.2

4.8
19.0
32.768
kbit/s
50
76.8
100
250
Frequency stability +/- 40 ppm Including 10 years of ageing.
Frequency stability ageing 1 ppm/year Starting after 10 years
5 ppm/10 Years
Transmit power -20 11 dBm
Spurious emission, TX
< 1 GHz -36
> 1 GHz -30

47 – 74 MHz -54
dBm
87.5 – 118 MHz -54
174 – 230 MHz -54
470 – 862 MHz -54
Sensitivity
1.2 kbit/s -110
4.8 kbit/s -106
19.0 kbit/s -104
32.768 kbit/s -101 1% packet error rate,
dBm
76.8 kbit/s -99 20 bytes packet length
100 kbit/s -97

Adjacent channel rejection 29 dB

Alternate channel selectivity 53 dB
Image channel rejection 28 dB

Ó2018 Tiny Mesh AS TM4000 Series Data Sheet V1.8 Page 55 of 59

 TM4000 Series
Parameter Min Typ. Max Unit Condition / Note
Blocking / Interferer rejection / Wanted signal 3 dB above
desensitization sensitivity level, CW interferer.
Db
+/- 1 MHz 30 43 Minimum numbers corresponds
+/- 2 MHz 35 49 to class 2 receiver requirements
+/- 5 MHz 50 68 in EN300220.
+/- 10 MHz 60 72
Wanted signal 3 dB above
sensitivity level, modulated
interferer. BER=0.1%
Compliant to class 2 receiver
requirements in EN 300 440
class 2

Wanted signal 3 dB above

sensitivity level, CW interferer.
Minimum numbers corresponds
to class 2 receiver requirements
in EN300220.
Saturation -14 dBm
Input IP3 -14 dB
Spurious emission, RX Complies with EN 300 328, EN
30 – 1000 MHz -57 300 440, FCC CFR47 Part 15,
dBm
1 – 12.75 GHz -47 and ARIB STD#T66
Supply Voltage 2.0 3.6 V
Current consumption, RX/IDLE Apply over entire supply voltage
mA
24 range
Current consumption, TX Apply over entire supply voltage
-20 dBm 18 range
-10 dBm 20
0 dBm 22 .
5 dBm 25 mA
9 dBm 35

Current consumption, SLEEP 0.3 1.0 uA

Digital I/O
Input logic level, low 30 % Of VCC
Input logic level, high 70 % Of VCC
Output logic level, low (1µA) 0
V
Output logic level,high(-1µA) VCC
SET pin Minimum 250 ns pulse width
Input logic level, low 30 %
V
Input logic level, high 70 %
UART Baud Rate tolerance +/- 2 UART receiver and transmitter
%
Configuration memory write 1000 The guaranteed number of
cycles write cycles using the ‘M’
command is limited
PWM switching frequency 1 Applies to GPIO 7 when
kHz
configured for PWM

Ó2018 Tiny Mesh AS TM4000 Series Data Sheet V1.8 Page 56 of 59

 TM4000 Series
Regulatory Compliance Information
The use of RF frequencies and maximum allowed RF power is limited by national regulations. The
TM4080 has been designed to comply with the R&TTE directive 1999/5/EC. According to R&TTE
directives, it is the responsibility of the end user to check that the host product (i.e. final product) is
compliant with R&TTE essential requirements. The use of a CE marked radio device can avoid re-
certification of the final product, provided that the end user respects the recommendations given. A
Declaration of Conformity is available on request.
• The TM4090 is designed to meet FCC regulations for license free operation under part 15.
However, a final approval is required by FCC for the end product.
• The TM4070 is designed according to G.S.R.564(E) and G.S.R.168(E) for license free use in
India. The Gazettes are available on request.
• The TM4070 comply to IEEE 802.15.4.g PHY Mode ID 0 encoding when configured for RF Data
Rate 8.

R&TTE directive (EU)

According to R&TTE directives, it is the responsibility of customers to check that the host product
(i.e. final product) is compliant with R&TTE essential requirements. The use of a CE marked device
may avoid recertification of the final product, provided the end user respects the recommendations.
A Declaration of Conformity is available on request.

In order to comply with the spectrum access requirements given in EN 300 220-2, an external
application using the device for serial data transmission, should limit amount of serial data by
introducing minimum time delays between each time data is dispatched. The below table indicates
the minimum time delay between serial data dispatch at given data rates with default configuration
settings.

For applications that dispatch Event Data based on internal timer (IMA Timer) or when meeting digital
or analogue trigger conditions, the application should be designed to ensure minimum time between
each Event Data dispatch, per below table.
RF
0.3 0.6 1.2 2.4 4.8 9.6 19 19.2 38.4 50 76.8 100 250
Data rate kbps
HIAM Time
26 18 12 8 5 4 3 3 2 1 1 1 1
Seconds
10%
Serial Duty 96.8 s 48.3 s 24.1 s 12.0 s 5.89 s 2.86 s 1.36 s 1.34 s 586 ms 410 ms 207 ms 119 ms 0
Buffer Cycle
Fill 1%
Delay Duty 968.9 s 483.1 s 240.7 S 119.5 s 58.89 s 28.59 s 13.59 s 13.44 s 5.86 s 4.10 s 2.07 s 1.19 s 0
Cycle
Min. 10%
time Duty 41.9 s 18.8 s 8.8 s 4.2 s 2.06 s 0.99 s 491 ms 486 ms 240 ms 188 ms 120 ms 92 ms 36 ms
between Cycle
Event 1%
data Duty - s - s - s - s 280 s 22.4 s 7.78 s 7.64 s 3.29 s 3.25 s 1.65 s 1.16 s 394 ms
dispatch Cycle

WPC Compliance (India)

License based operation in India is bases on case by case grant and the basis is normally a compliance
to R&TTE directive(CE) or FCC.

Regulatory Compliance Disclaimer

Users must assess and verify that their final product meets the appropriate specifications and to
perform the required procedures for regulatory compliance.
The relevant regulations are subject to change. Tiny Mesh AS does not take responsibility for the
validity and accuracy of the understanding of the regulations referred above. Tiny Mesh only warrants
that this product meets the specifications in this document. Tiny Mesh is exempt from any
responsibilities related to regulatory compliance.

Ó2018 Tiny Mesh AS TM4000 Series Data Sheet V1.8 Page 57 of 59

 TM4000 Series
Document Revision History
Document FW Changes
Revision Release
1.0 Initial Version
1.1 Pin-out corrected, Pulse Counter and GPIO 3 swapped location
1.2 Editing and textual changes
1.3 Swapped GPIO3 and Pulse counter input pins
1.4 Editing and textual changes
1.5 Added 4xxx-2x0 (Compact) version, ordering codes, mechanical drawings,
updated pin-out including 4xxx-2x0 version, corrected pin-out for GPIO3 and
Pulse connections
1.6 Added packaging info, Image of 4xxx-2x0 board, programming pins 4xxx-2x0,
corrected error in ordering codes table, misc. editing details
1.7 Added mounting instructions
1.8 1.48 Added new configuration features, updated lacking details and minor flaws

Product Status and Definitions

Current Data Sheet Identification Product Status Definition
Status
Advance Information Planned or under This data sheet contains the design
development specifications for product development.
Specifications may change in any
manner without notice.
Preliminary Engineering Samples This data sheet contains preliminary
and First Production data, and supplementary data will be
published at a later date. Tiny Mesh
reserves the right to make changes at
any time without notice in order to
improve design and supply the best
possible product.
X No Identification Noted Full Production This data sheet contains final
specifications. Tiny Mesh reserves the
right to make changes at any time
without notice in order to improve
design and supply the best possible
product.
Obsolete Not in Production This data sheet contains specifications
on a product that has been discontinued
by Tiny Mesh. The data sheet is printed
for reference information only.

Disclaimer
Tiny Mesh AS believes the information contained herein is correct and accurate at the time of this
printing. However, Tiny Mesh AS reserves the right to make changes to this product without notice.
Tiny Mesh AS does not assume any responsibility for the use of the described product; neither does it
convey any license under its patent rights, or the rights of others. The latest updates are available at
the Tiny Mesh website or by contacting Tiny Mesh directly.

As far as possible, major changes of product specifications and functionality, will be stated in product
specific Errata Notes published at the Tiny Mesh website. Customers are encouraged to check
regularly for the most recent updates on products and support tools.

Trademarks
Tinymesh™ is a trademark of Tiny Mesh AS. The protocol handles host communication, data buffering,
error check, addressing and broadcasting. It supports transparent an packet-addressed mesh
topologies.

Ó2018 Tiny Mesh AS TM4000 Series Data Sheet V1.8 Page 58 of 59

 TM4000 Series
All other trademarks, registered trademarks and product names are the sole property of their
respective owners.

Life Support Policy

This Tiny Mesh product is not designed for use in life support appliances, devices, or other systems
where malfunction can reasonably be expected to result in significant personal injury to the user, or
as a critical component in any life support device or system whose failure to perform can be
reasonably expected to cause the failure of the life support device or system, or to affect its safety
or effectiveness. Tiny Mesh AS customers using or selling these products for use in such applications
do so at their own risk and agree to fully indemnify Tiny Mesh AS for any damages resulting from any
improper use or sale.

© 2018, Tiny Mesh AS. All rights reserved.

Contact Information

Web:
www.tinymesh.com
www.tmrcinidia.com

Address:
Tiny Mesh as TinymeshRadiocraftsIndia LLP
Løkkegata 15 The Atrium- Quark City
1532 Moss A-45, Industrial Area Phase 8B
Norway Mohali- 160059
India

Tel: +47 92268419 +91 172-5096234

+91 971-1053588
E-mail: [email protected]
[email protected]

Ó2018 Tiny Mesh AS TM4000 Series Data Sheet V1.8 Page 59 of 59