1 User Guide, emMesh V1.31(e), FW: 2.147 Document version : A [04/01/19]
Contents Contents Revision History Trademarks & Copyrights Disclaimers Introduction Document related rmware and hardware Technical Specications Form factor General Specications Interfaces Specications Regulatory conformity summary Technical Drawing GPIOs 16 pins connector 8 pins connector Design Notes Power supply design Board layout Antenna performance Serial Communication Protocol Introduction Generic message structure Communication protocol Encryption (6 bits) Message Type (1 bit) Simplied Mode Message types Payload: Simplied Message type 2 2 5 5 5 6 6 7 7 8 8 9 9 10 11 11 12 13 13 13 13 14 14 15 16 17 17 18 18 18 Message Type advanced Encryption Types Payload Payload [0] PayloadType <4: 0>
payload [0] PayloadType <7: 5>
TypeID Refresh DataWithoutAck DataWithAck FileTransfer Event Return Get Set Payload [1]: sub-type <7: 0>
AckData 0x03 RoutingTableInfo 0x20 TableLvl1 0x21 DebugInfos 0x22 Settings 0x23 Rssi 0x24 MasterID 0x25 NackInfos 0x2B DecryptionError 0x2C WrongParameter 0x2D Payload [1]: subType <7: 0>
TypeID 0x00 Refresh 0x01 RoutingTableInfo 0x20 TableLvl1 0x21 DebugInfos 0x22 Settings 0x23 Rssi 0x24 MasterID 0x25 0x23Settings 3 19 20 21 21 21 22 22 22 22 23 23 23 23 23 24 24 24 25 25 25 25 25 25 25 26 27 27 27 28 28 28 28 28 28 29 MasterID 0x25 ForceRelay 0x26 Password 0x26 ResetMcu 0x28 CloseDevice 0x29 Regulatory Informations United States (FCC) OEM labeling requirements FCC notices FCC-approved antennas RF exposure CANADA - ISED (Innovation, Science and Economic Development Canada) Labeling requirements Detachable antenna EUROPE (CE) Maximum power and frequency specications OEM labeling requirements Declarations of conformity Antennas Warranty 4 29 29 29 29 29 31 31 31 32 33 33 34 34 34 35 35 35 35 35 36 Revision History Revision A Date April 2019 Description Creation of document 5 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. Disclaimers Information in this document is subject to change without notice and does not represent a commitment on the part of Penteract Consulting Inc. Penteract provides this document as is, without warranty of any kind, expressed or implied, including, but not limited to, the implied warranties of tness or merchantability for a particular purpose. Penteract may make improvements and/or changes in this manual or in the product(s) and/or the program(s) described in this manual at any time. 6 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 certied, 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. They are designed for applications requiring small bandwidth, large number of sensors, ultra-
low power consumption, near-realtime control and monitoring and always available response without any requirement for o-cycle. The emMesh uses Microchip MRF89A chipset which is amplied up to 26db and with reception sensitivity of up to -103 dbm allowing up to 16km distance between two line of sight devices. Secured, proprietary Mesh technologies uses fast FHSS patterns with payload encryption allowing fast and reliable communications. Document related rmware and hardware The following document refer to emMesh hardware revision 1.31 and rmware version 2.160. 7 Technical Specications Form factor 8 General Specications Frequencies Americas: ISM 902-926 Mhz (emMesh v.1.31) Europe: 863 to 870 Mhz (emMesh v.1.31e) Nombre d'units Bandwidth FHSS Lithium battery charger Internal memory Antenna connector Up to 64006 in a single network P2P: 19200 bps 15.6 ms, 50 channels Up to 10 volts of input. Ready for 6 volt solar panels 2 Mbits Flash UFL (50 Ohm) Interfaces UART 3.3 V I/O SPI USART ADC I/O PWM 1 communication UART, 1 debug UART 10 Programmable inputs/outputs Up to 1Mbps I2C 2-Input 12-bit analog inputs 0-2v 10 Programmable inputs/outputs 5 PWM Outputs 9 Specications Dimensions Operating temperature Storage temperature Operating voltages 34 mm x 21 mm x 10 mm
-20C to 70C
-40C to 85C From 3.3 V to 5.5 V Consumption Typical: 4 mAh Antenna connector Integrated Antenna Transmitting power Sensitivity 26 dBm
-103 dBm Regulatory conformity summary United States
(FCC Part 15.247) Canada Innovation, Science and Economic Development Canada (ISED) FCC/IC test transmit power output range Europe
(CE) FCC ID : 2ASI4EMMESH emMesh 1.31 FW: 2.160 IC : 24776-EMMESH emMesh 1.31 FW: 2.160 0 to +26dBm Yes emMesh 1.31e FW: 2.160e RoHS Compliant Technical Drawing 10 11 GPIOs 16 pins connector Pins 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 Name Ground PPR Ground TX2 BAT+
RX2 TX AN1 AN2 RX SDI PWM2 CHG_IN SDO 3.3V SCK Type P O P I/O O P I/O I I/O O I/O I/O I I/O I I/O I I/O I I/O P O P O Description Ground reference for logic and I/O pins Power present state 0V when power present at CHG_IN [open drain]
Ground reference for logic and I/O pins I/O pin (0-3.3V) UART TX (0-3.3V) Positive supply (3.4 to 5.5Vdc) I/O pin (0-3.3V) UART RX (0-3.3V) I/O pin (0-3.3V) UART TX (0-3.3V) I2C SDA pin I/O pin (0-3.3V) Analog input (0-3.3V) I/O pin (0-3.3V) Analog input (0-3.3V) I/O pin (0-3.3V) UART RX (0-3.3V) I2C SCL pin SPI data input I/O pin (0-3.3V) LI-ION or LI-Po battery charger input power (4.2-10Vdc) SPI serial data output 3.3V DC output (max 200mA) SPI serial data clock 12 8 pins connector Pins 1 2 3 4 5 6 7 8 Name nMCLR 3.3V GND PGD PGC GND PWM1 nCHG Type I P P I/O I/O P O O Description Master reset not (reset emMeah with 0V) 3.3V output (max 200mA) Ground reference for logic and I/O pins Programmation interface I/O pin (0-3.3V) Programmation interface I/O pin (0-3.3V) Ground reference for logic and I/O pins Status LED control pin 0V when charging(open drain) 13 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. Board layout The emMesh is designed to be used as a standalone device or integrated in another board, thus, it does not has any board layout requirement other than usual practice for pcb design. Antenna performance The following suggestions help you achieve optimal antenna performance. Point the antenna up vertically (upright). Position the antennas away from metal objects whenever possible. If you place the device inside a metal enclosure, use an external antenna. Do not place any ground planes or metal objects above or below the antenna. For the best results, mount the device at the edge of the host PCB. Ensure that the ground, power, and signal planes are vacant immediately below the antenna section. 14 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 dened by two mode: Simplied protocol and Advanced Protocol. Description of both mode could be found later in that document. Choosing the protocol that is more suitable for your needs can lead to simplistic to more complex implantation requirements. 15 Generic message structure Both mode, simplied or advanced are using the same base structure. Both are meant to be ecient 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. Transport layers such as IP, Serial or Bluetooth are completely transparent and rely on a Mesh reality which held, depending on protocols on a system of relay which allowed a packet to switch from one type of transport to the other without the system needing to know it. This is coming with some limitation like payload size with is maintained fairly small as it allows smaller capacity type of transport such as emMesh and BLE to be able to participate as said mesh reality. Although said payload could be increased if protocol is only used in IP, knowing which device will be used as relay is fairly important to allows said behaviour and we do not recommend it. 16 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. sync sync length msg type +
encryption Payload type Data Data Data Data 0x24 0x24 0x0F 0x00 0x02 0x41 0x41 0x41 0x41 Data Data Data Data 0x48 0x45 0x4C 0x4C Data 0x4F checksum Byte termination Byte termination 0x40 0x0D 0x0A Table 1: example of a simplied type of message In the example on Table 1, byte[1 & 2] are the sync characters which are alway, whether in simplied or advanced mode, $$. byte[3] Length:
This byte is a computation of the size of the payload the msgType and itself. byte[4] Msg Type & Encryptio:
This byte is created by mixing the binary values [MSB 1bits Advanced=1 Simplied=0][LSB 7 bits Encryption Type]
Exemple:
Encryption_Type = 0x01;
Msg_Type = 0x01;
byte[4] = Msg_Type<<7 + Encryption_Type;
byte[4] = 0x81 Please see MsgType and Encryption type section for more infos. byte[n-3] Checksum:
The checksum is calculated over payload using and 8 bits exclusive or (XOR) sequence. It is done prior to encryption and include payload type. byte[n-2] & byte [n-1] Ender:
Each message must be terminated by \r\n (0x0D, 0x0A). This allowes both packet end but also correlation of length on which if both values are not equals, message is discarded. Encryption (6 bits) Encryption Type <6: 0>
No Polymorphism Rijndael [CBC]
AES 256bits RSA 2048 256 bits ECC User Dened Message Type (1 bit) Message Type <7>
Simplied Advanced 17 Value 0x00 0x01 0x02 0x03 0x04 0x05 Description Raw message, no encryption Simple light cypher algorithm based on polymorphism of paraphrase. Rijndael implentation cypher. (Not on emMesh) AES-256 standard (Not on emMesh) To come To come 0x06 to 0x7F Supported only by certain devices Value 0x00 0x01 Description Set following message as being in simplied mode Set following message as being in advanced mode 18 Simplied Mode In simplied mode, the associated device using is acting a a slave accessories. Using that protocol ease the integration by simply allowing Message types The dierence between the simplied 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". The simplied type of messages can only use the types of payload dataWithoutAck and dataWithAck Payload: Simplified Message type 0 1 2 3 BYTE 4 n - 4 n - 3 n - 2 n- 1 Value 0x24 0x24 0-n 0x00 0x00-0x7F 0x0D 0x0A Description Bytetiming synchronization Byte message size Message Type < 7>
encryption Type <6: 0>
Payload []
Checksum ender byte 1 ender byte 2 Table 2: Structure of a simplied message type Message Type advanced BYTE 4-7 8 11 0 1 2 3 12 13 14 Value 0x24 0x24 0-n 0x01 0x00-0x7F 0x00-0xFF 0x00-0xFF 0x00-0xFF 19 Description Bytetiming synchronization Byte message size Message Type <7>
encryption Type <6: 0>
destination P2P P2P origin Message Type Mesh Message ID Mesh message reception conrmation ID Mesh Mesh origin Mesh Destination 15-18 19-22 24 to n - 4 n - 3 n - 2 n - 1 23 0x00-0xFF level compared to sending the message 0x0D 0x0A Payload []
ChkSum Ender byte 1 Ender byte 2 Table 3: Structure of an advanced type of message 20 Description Encryption Types Encryption Type <6: 0>
No Polymorphism RijndaelManaged[CBC]
RSA 2048 bits Value 0x00 0x01 0x02 0x03 21 Payload Payload has a variable maximum size of 38 bytes. The rst 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. Payload [0] PayloadType <4: 0>
type payload <4: 0>
TypeID Refresh DataWithoutAck DataWithAck FileTransfer undened event return Get set value 0x00 0x01 0x02 0x03 0x04 0x05 to 0x1B 0x1C 0x1D 0x1E 0x1F Description Return of identication information Backinformation about theModule Back / Send data without receiving conrmation Back / Send data with conrmation of receipt Sends data with ale transfer protocol event Type type return type get Type set Table 5: List of types of payload payload [0] PayloadType <7: 5>
The encryption index is sent on 3 bit at index 0 of the payload. See the section Payload encryption. 22 TypeID Returns module identication 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, rmware 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. The rest of the payload is variable depending on the module, see the documentation on the module concerned for details. Payload []
0 1 6 2 to 5 7 to... Value 0x01 Description Typepayload 0x00 - 0x1E (invalid: 0x1F) level compared to the original 0x00 - 0xFF (default: 0xFF) Relay Group ID Module Based. Table 6: Structure of the refresh type payload DataWithoutAck Back / Sends data without reception conrmation. DataWithAck Back / Send data with conrmation of receipt. Upon receipt of a message type dataWithAck a message subtype ackData will be sent to the origin. 23 FileTransfer Sends data with a le 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 modication, see subtypes changes for details. Payload [1]: sub-type <7: 0>
24 Return Type AckData RoutingTableInfo TableLvl1 DebugInfos Settings RSSI MasterID NackInfos DecryptionError WrongParameter Value 0x03 0x20 0x21 0x22 0x23 0x24 0x25 0x2B 0x2C 0x2D Description Receipt Conrmation ID and level of known modules ID of this module in the level table 1 Module Settings signal strength between two modules master ID Conrmation not received Error decryption Invalid Parameter AckData 0x03 Message receipt Conrmation. The message ID of the header "Mesh" is returned in the payload to indicate which message is conrmed. RoutingTableInfo 0x20 List ID and level 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. If the 3 destinations are received 0xFFFFFFFF, it means that the module has not other destinations in its routingTable from this index. 0x1D 0x20 Index Max Dest [4]
relay [4]
Level Dest [4]
relay [4]
Level Dest [4]
relay [4]
Level 25 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. See the documentation on the module concerned for details. MasterID 0x25 Returns the master ID. NackInfos 0x2B Conrmation of non-receipt of the message. The message ID of the header "Mesh" is returned in the payload to indicate which message failed. DecryptionError 0x2C Decryption error detected. The message ID of the header "Mesh" is returned in the payload to indicate on what message the error occurred. 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. 26 27 Payload [1]: subType <7: 0>
Application Type TypeID Refresh value 0x00 0x01 RoutingTableInfo 0x20 TableLvl1 DebugInfos settings RSSI MasterID 0x21 0x22 0x23 0x24 0x25 Description Request of identifications information Request information from aModule Request ID and the modules known Request the IDs of the modules present in the level 1 table module parameters Application Request signal strength between two modules request of the master ID TypeID 0x00 Request of identications of the information module. See the documentation on the module concerned for details. Refresh 0x01 Application of module information. For each index requested 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. 28 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. See the documentation on the module concerned for details. Settings 0x23 Request module parameters. See the documentation on the module concerned for details. Rssi 0x24 Returns signal strength. See the documentation on the module concerned for details. MasterID 0x25 Request the master ID. Type of change value Description Settings MasterID ForceRelay Password ResetMcu CloseDevice 0x23 0x25 0x26 0x26 0x28 0x29 module parameters Modifications Changing the master ID Changing IDforced relay Changing the password RestartModule Module Closing 29 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. Provide the unit of time (see Table 11) on a byte tracking time of 2 bytes (MSB followed by the LSB). Example: 4096 minutes = 0x02 0x10 0x00 Time unit Milliseconds Seconds minutes Hours value 0x00 0x01 0x02 0x03 Table 11 30 31 Regulatory Informations United States (FCC) emMesh 1.31 RF Modules comply with Part 15 of the FCC rules and regulations. Compliance with the labeling requirements, FCC notices and antenna usage guidelines is required. To fulll FCC Certication, 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 nal product. RF Modules may only be used with antennas that have been tested and approved for use with the modules. OEM labeling requirements As an Original Equipment Manufacturer (OEM) you must ensure that FCC labeling requirements are met. You must include a clearly visible label on the outside of the nal product enclosure that displays the following content:
Contains FCC ID: 2ASI4EMMESH This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: (1.) this device may not cause harmful interference and (2.) this device must accept any interference received, including interference that may cause undesired operation. 32 FCC notices IMPORTANT: emMesh 1.31 RF Modules have been certied by the FCC for use with other products without any further certication (as per FCC section 2.1091). Modications not expressly approved by Penteract could void the user's authority to operate the equipment. IMPORTANT: OEMs must test nal product to comply with unintentional radiators
(FCC section 15.107 & 15.109) before declaring compliance of their nal product to Part 15 of the FCC Rules. IMPORTANT: The RF module has been certied for remote and base radio applications. If the module will be used for portable applications, the device must undergo SAR testing. This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection Regulatory information United States (FCC) emMesh 1.31 Module User Guide against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment o and on, the user is encouraged to try to correct the interference by one or more of the following measures:
Re-orient or relocate the receiving antenna, Increase the separation between the equipment and receiver, Connect equipment and receiver to outlets on dierent circuits, or Consult the dealer or an experienced radio/TV technician for help. 33 FCC-approved antennas The modules are FCC approved for xed base station for the channels indicated in the tables below. If the antenna is mounted at least 25 cm (10 in) from nearby persons, the application is considered a mobile application. Antennas not listed in the table must be tested to comply with FCC Section 15.203 (Unique Antenna Connectors) and Section 15.247 (Emissions). The antennas in the tables below have been approved for use with this module. Cable loss is required when using gain antennas as shown in the tables. Antennas External Internal Supplier Pulse Electronics NA Part Number W1063 AWG24 Wire 85mm length (1/4 wave monopole) Gain 3.0 dBi 3.0 dBi RF exposure If you are an integrating the emMesh into another product, you must include the following Caution statement in OEMproduct manuals to alert users of FCC RF exposure compliance:
CAUTION! To satisfy FCC RF exposure requirements for mobile transmitting devices, a separation distance of 20 cm or more should be maintained between the antenna of this device and persons during device operation. To ensure compliance, operations at closer than this distance are not recommended. The antenna used for this transmitter must not be colocated in conjunction with any other antenna or transmitter. 34 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 nal 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. B and Industry Canada accepts FCC test report or CISPR 22 test report for compliance with ICES-003. Detachable antenna Under Industry Canada regulations, this radio transmitter may only operate using an antenna of a type and maximum (or lesser) gain approved for the transmitter by Industry Canada. To reduce potential radio interference to other users, the antenna type and its gain should be so chosen that the equivalent isotropically radiated power (EIRP) is not more than that necessary for successful communication. Conformment la rglementation d'Industrie Canada, le prsent metteur radio peut fonctionner avec une antenne d'un type et d'un gain maximal (ou infrieur) approuv pour l'metteur par Industrie Canada. Dans le but de rduire les risques de brouillage radiolectrique l'intention des autres utilisateurs, il faut choisir le type d'antenne et son gain de sorte que la puissance isotrope rayonne quivalente (p.i.r.e.) ne dpasse pas l'intensit ncessaire l'tablissement d'une communication satisfaisante. 35 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 nal 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 le as described in the Radio Equipment Directive. Furthermore, the manufacturer must maintain a copy of the emMesh 1.31e Module user guide documentation and ensure the nal product does not exceed the specied power ratings, antenna specications, and/or installation requirements as specied in the user guide. Maximum power and frequency specifications Maximum power: 26.5 dBm Equivalent Isotropically Radiated Power (EIRP)at normal condition. OEM labeling requirements The CE marking must be axed to a visible location on the OEM product. The following gure shows CE labeling requirements. The CE mark shall consist of the initials CE taking the following form:
If the CE marking is reduced or enlarged, the proportions given in the above graduated drawing must be respected. The CE marking must have a height of at least 5 mm except where this is not possible on account of the nature of the apparatus. The CE marking must be axed visibly, legibly, and indelibly. Penteract customers assume full responsibility for learning and meeting the required guidelines for each country in their distribution market. Refer to the radio regulatory agency in the desired countries of operation for more information. Declarations of conformity Penteract has issued Declarations of Conformity for the emMesh concerning emissions, EMC, and safety. Antennas Please refer to FCC list of Antennas 36 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. Any damage resulting in faulty usage or integration of current module could be used against Penteract and will automatically void the warranty. Usage not based in respect of following document will also void the warranty automatically. Some states do not allow limitations or exemption for incidental or consequential damages or restriction of guarantees. In this case, this limitation or exclusion may not apply. This written warranty gives you specic legal rights. According to the state or province, it is possible that you have other rights.