User Guide, emMesh V1.31(e), FW: 2.
Contents Contents 2 Revision History 5 Trademarks & Copyrights 5 Disclaimers 5 Introduction 6 Document related firmware and hardware 6 Technical Specifications 7 Form factor 7 General Specifications 8 Interfaces 8 Specifications 9 Regulatory conformity summary 9 Technical Drawing 10 GPIOs 11 16 pins connector 11 8 pins connector 12 Design Notes 13 Power supply design 13 Board layout 13 Antenna performance 13 Serial Communication Protocol 14 Introduction 14 Gene
Message Type advanced 19 Encryption Types 20 Payload 21 Payload [0] PayloadType <4: 0> 21 payload [0] PayloadType <7: 5> 21 TypeID 22 Refresh 22 DataWithoutAck 22 DataWithAck 22 FileTransfer 23 Event 23 Return 23 Get 23 Set 23 Payload [1]: sub-type <7: 0> 24 AckData 0x03 24 RoutingTableInfo 0x20 24 TableLvl1 0x21 25 DebugInfos 0x22 25 Settings 0x23 25 Rssi 0x24 25 MasterID 0x25 25 NackInfos 0x2B 25 DecryptionError 0x2C 25 WrongParameter 0x2D 26 Payload [1]
MasterID 0x25 29 ForceRelay 0x26 29 Password 0x26 29 ResetMcu 0x28 29 CloseDevice 0x29 29 Regulatory Informations 31 United States (FCC) 31 OEM labeling requirements 31 FCC notices 32 FCC-approved antennas 33 RF exposure 34 CANADA - ISED (Innovation, Science and Economic Development Canada) 35 Labeling requirements 35 Detachable antenna 35 EUROPE (CE) 36 Maximum power and frequency specifications 36 OEM labeling requirements 36 Declarations of conformity 36 Antennas 36
Revision History Revision Date Description A April 2019 Creation of document Trademarks & Copyrights Penteract and emMesh logos are protected properties of Les Consultants Penteract Inc. or Penteract Consulting Inc. Usage of those logo is strictly prohibited without the written consent of Penteract. © 2018 Penteract Consulting Inc. . All rights reserved.
Introduction The "em" series are the long range 868/915 radios (up to 16 km) using the mesh topology to create network availability in areas where traditional networks are not available. Completely certified, the mesh module allows, thanks to its very low consumption, to be powered only by solar panels and therefore to be used even without supply of electrical network.
Technical Specifications Form factor
General Specifications Frequencies Americas: ISM 902-926 Mhz (emMesh v.1.31) Europe: 863 to 870 Mhz (emMesh v.1.31e) Nombre d'unités Up to 64006 in a single network Bandwidth P2P: 19200 bps FHSS 15.6 ms, 50 channels Lithium battery charger Up to 10 volts of input. Ready for 6 volt solar panels Internal memory 2 Mbits Flash Antenna connector UFL (50 Ohm) Interfaces UART 3.
Specifications Dimensions 34 mm x 21 mm x 10 mm Operating temperature -20°C to 70°C Storage temperature -40°C to 85°C Operating voltages From 3.3 V to 5.5 V Consumption Typical: 4 mAh Antenna connector Integrated Antenna Transmitting power 26 dBm Sensitivity -103 dBm Regulatory conformity summary United States FCC ID : 2ASI4EMMESH (FCC Part 15.247) emMesh 1.31 FW: 2.160 Canada IC : 24776-EMMESH Innovation, Science and Economic emMesh 1.31 Development Canada (ISED) FW: 2.
Technical Drawing
GPIOs 16 pins connector Pins Name Type Description 1 Ground P Ground reference for logic and I/O pins 2 PPR O Power present state 0V when power present at CHG_IN [open drain] 3 Ground P Ground reference for logic and I/O pins 4 TX2 I/O O I/O pin (0-3.3V) UART TX (0-3.3V) 5 BAT+ P Positive supply (3.4 to 5.5Vdc) 6 RX2 I/O I I/O pin (0-3.3V) UART RX (0-3.3V) 7 TX I/O O I/O I/O pin (0-3.3V) UART TX (0-3.3V) I2C SDA pin 8 AN1 I/O I I/O pin (0-3.3V) Analog input (0-3.
8 pins connector Pins Name Type Description 1 nMCLR I Master reset not (reset emMeah with 0V) 2 3.3V P 3.3V output (max 200mA) 3 GND P Ground reference for logic and I/O pins 4 PGD I/O Programmation interface I/O pin (0-3.3V) 5 PGC I/O Programmation interface I/O pin (0-3.
Design Notes The following guidelines help to ensure a robust design and allowes regulation conformity. Power supply design The emMesh has an integrated voltage regulator. Only a single external supply source is needed. For best performances, make sure the supply voltage is within tolerance. Limit the power supply ripple to 100mV maximum. Also make sure the supply source can withstand peak current of 250mA. Adding a 100uF capacitor at the input will help sustain the peak current demand of the emMesh.
Serial Communication Protocol Introduction The following document refers to Penteract emToo Protocol for Generic implementation. emToo Protocol works as a global multi-layer, multi-protocol mesh type networking. Allowing multiples protocol such as WiFi, ISM, IP or Bluetooth to interact with each other transparently and be use as a unique transport layer. The protocol is defined by two mode: Simplified protocol and Advanced Protocol. Description of both mode could be found later in that document.
Generic message structure Both mode, simplified or advanced are using the same base structure. Both are meant to be efficient on any type of transport protocol and secured in both possible encryption and integrity of datas. Every message sent thru emToo protocol must be packet for the Transport layer structure. Said transport layer is what is creating the capacity to travel on every type of protocols.
Communication protocol A message sent must begin with 0x24 0x24 and end with 0x0D 0x0A. In addition, it must contain a size, 8 bits checksum, the message type used and the type of encryption used.
Encryption (6 bits) Encryption Type <6: 0> Value Description No 0x00 Raw message, no encryption Polymorphism 0x01 Simple light cypher algorithm based on polymorphism of paraphrase. Rijndael [CBC] 0x02 Rijndael implentation cypher.
Simplified Mode In simplified mode, the associated device using is acting a a slave accessories. Using that protocol ease the integration by simply allowing Message types The difference between the simplified and advanced type of message is the addition of two headers and types of payload possible In the message forward must provide the header of "peer to peer" and "Mesh".
Message Type advanced BYTE Value Description 0 0x24 Bytetiming 1 0x24 synchronization Byte 2 0-n message size 3 0x01 Message Type <7> 0x00-0x7F encryption Type <6: 0> 4-7 destination P2P 8 11 P2P origin 12 0x00-0xFF Message Type Mesh 13 0x00-0xFF Message ID Mesh 14 0x00-0xFF message reception confirmation ID Mesh 15-18 Mesh origin 19-22 Mesh Destination 23 0x00-0xFF level compared to sending the message 24 to n - 4 Payload [] n-3 ChkSum n-2 0x0D Ender byte 1 n-1
Encryption Types Encryption Type <6: 0> Value No 0x00 Polymorphism 0x01 RijndaelManaged[CBC] 0x02 RSA 2048 bits 0x03 Description
Payload Payload has a variable maximum size of 38 bytes. The first byte must be the type of payload of 5 bit and an encryption index of 3 bit. The byte 0 is therefore never encrypted because it contains the information necessary for decryption.
TypeID Returns module identification information within a "CSV" Structure of the typeID varies according to the device name. See the documentation on the module concerned for details. Example of "CSV" structure: "device name, firmware version, hardware version Version EEPROM memory" Refresh Return the module information. The type refresh must provide at least 3 information which are: the level relative to the origin of the request, the relay used to communicate with the origin and the ID of the group.
FileTransfer Sends data with a file transfer protocol. Event Type of event, see subtypes events for details. Return Return type, see subtypes back for details. Get Type of application, see the application subtypes for details. Set Type of modification, see subtypes changes for details.
Payload [1]: sub-type <7: 0> Return Type Value Description AckData 0x03 Receipt Confirmation RoutingTableInfo 0x20 ID and level of known modules TableLvl1 0x21 ID of this module in the level table 1 DebugInfos 0x22 Settings 0x23 Module Settings RSSI 0x24 signal strength between two modules MasterID 0x25 master ID NackInfos 0x2B Confirmation not received DecryptionError 0x2C Error decryption WrongParameter 0x2D Invalid Parameter AckData 0x03 Message receipt Confirmation.
TableLvl1 0x21 List ID modules that are present in the level of table 1. For asked each index 8 ID will be send. The possible index values are from 0 to size max / 8, rounding up if size max / 8 does not give a whole. 0x1D 0x21 Index Max 8 x ID [4] DebugInfos 0x22 Information on the module. See the documentation on the module concerned for details. Settings 0x23 Returns module parameters. See the documentation on the module concerned for details. Rssi 0x24 Returns signal strength.
WrongParameter 0x2D Parameter error detected. The message ID of the header "Mesh" is returned in the payload to indicate on what message the error occurred.
Payload [1]: subType <7: 0> Application Type value Description TypeID 0x00 Request of identifications information Refresh 0x01 Request information from aModule RoutingTableInfo 0x20 Request ID and the modules known TableLvl1 0x21 Request the IDs of the modules present in the level 1 table DebugInfos 0x22 settings 0x23 module parameters Application RSSI 0x24 Request signal strength between two modules MasterID 0x25 request of the master ID TypeID 0x00 Request of identifications
RoutingTableInfo 0x20 Application part of the list of known modules. For each index 3 requested destination of their associated relay and level will be sent. The possible index values are from 0 to size max / 3, round up if max size / 3 does not give a whole. TableLvl1 0x21 Application part of the list of modules that are present in the table level 1. See the documentation on the module concerned for details. DebugInfos 0x22 Information on the module.
0x23Settings Changing the module parameters. See the documentation on the module concerned for details MasterID 0x25 Changing the master ID. Put into the desired payload ID. ForceRelay 0x26 Changing the ID of forced relay. Put into the desired payload ID. Password 0x26 Changing the password. Put in the payload the desired password. ResetMcu 0x28 Reset the microcontroller. CloseDevice 0x29 Close the module.
Regulatory Informations United States (FCC) emMesh 1.31 RF Modules comply with Part 15.247 of the FCC rules and regulations. Compliance with the labeling requirements, FCC notices and antenna usage guidelines is required. To fulfill FCC Certification, the OEM must comply with the following regulations: The system integrator must ensure that the text on the external label provided with this device is placed on the outside of the final product.
FCC notices IMPORTANT: emMesh 1.31 RF Modules have been certified by the FCC for use with other products without any further certification (as per FCC section 2.1091). Modifications not expressly approved by Penteract could void the user's authority to operate the equipment. IMPORTANT: The RF module has been certified for remote and base radio applications. If the module will be used for portable applications, the device must undergo SAR testing. The emMesh is only FCC authorized for FCC 15.247 rules.
FCC-approved antennas The modules are FCC approved for fixed base station for the channels indicated in the tables below. If the antenna is mounted at least 20 cm (10 in) from nearby persons, the application is considered a mobile application. This device has been approved to be used with antennas of maximum gain of 3dBi, model W1063 from PulseLarsen with RPSMA connector or integrated wire antenna. The antennas in the tables below have been approved for use with this module.
RF exposure If you are integrating the emMesh into another product, you must include the following Caution statement in OEM product manuals to alert users of FCC RF exposure compliance: CAUTION! To comply with FCC RF Exposure requirements, the host must ensure to install the approved antenna in the previous. The module is FCC-approved for fixed base station and mobile applications. At least 20 cm of separation distance between the emMesh and the user's body must be maintained at all times.
CANADA - ISED (Innovation, Science and Economic Development Canada) Labeling requirements Labeling requirements for Industry Canada are similar to those of the FCC. A clearly visible label on the outside of the final product enclosure must display the following text: Contains Model emMesh 1.31 Radio, IC: 24776-EMMESH The integrator is responsible for its product to comply with IC ICES-003 & FCC Part 15, Sub. B Unintentional Radiators. ICES-003 is the same as FCC Part 15 Sub.
EUROPE (CE) The emMesh 1.31e Modules have been tested for use in several European countries. If emMesh 1.31e Modules are incorporated into a product, the manufacturer must ensure compliance of the final product with articles 3.1a and 3.1b of the Radio Equipment Directive. A Declaration of Conformity must be issued for each of these standards and kept on file as described in the Radio Equipment Directive. Furthermore, the manufacturer must maintain a copy of the emMesh 1.
Warranty The only recourse for the customer under this limited warranty is the repair or replacement of the product as described above. Claims based on warranties, including warranties of merchantability or adaptation to a particular use, are limited to the shortest period permitted by law, which can not be less than 3 months. Penteract Consulting Inc. will not be held liable for incidental or consequential damages or material damage.
