rpygate Datasheet Version 1.1 go invent go invent 12.0 Mechanical Specications 13.0 Ordering information 13.1 Bundles 14.0 Packaging 15.0 Certication 15.1 15.2 15.2.1 15.2.2 15.2.3 15.3 15.3.1 15.3.2 15.4 EU Regulatory Conformance Federal Communication Commission Compliance Statement Federal Communication Commission Interference Statement RF Warning Statement End Product Labelling ISED Regulatory Approval ISED RSS warning/
ISED RF Exposure Statement Manual Information to the End User 16.0 Revision History 24 25 25 25 26 26 26 26 26 26 27 27 27 27 28 ygate Overview Featur e s Specications Hardware conguration Power supply options Available signals on headers Wireless connectivity options Absolute maximum ratings 1.0 2.0 3.0 3.1 3.2 3.3 3.4 3.5 5.1 5.2 5.3 5.4 6.0 6.1 6.2 6.3 4.0 Block Diagram 5.0 Pinout PyEthernet socket pinout Lithium battery connector pinout Module (WiPy3, GPy or LoPy4) socket pinout POWER and UART from/to the Pycom module header pinout Pi n Details PyEthernet socket pin details Lithium battery connector pinout Module (WiPy 3, GPy or LoPy4) socket pinout 6.4 POWER and UART from/to the module header pinout 6.5 Synchronization signal from a GPS receiver. API overview 7.0 8.0 Conguring PyGat e 9.0 Programming the device 10.0 Power 11.0 Memor y Map 11.1 11.2 11.3 11.3.1 11.4 11.5 11.5.1 Supported features Reception Paths Characteristics Packet Engine and Data Buffers Receiver Packet Engine Transmitter Packet Engine Receiver IF Frequencies Cong uration PyGate Using 2 x SX1257 Radios 03 04 04 04 04 04 04 04 05 06 07 07 08 08 09 09 09 10 12 12 13 13 14 14 14 14 14 15 15 17 21 21 Version 1. 1 02 ygate go invent VCP over USB to configure gateway from a terminal console LED on when pic is powered
(green light) to lithium battery Tact switch to enter save boot LoRa antenna U.FL connector Tact switch to enter programming mode battery charging in progress indication led lithium battery charger 4.2v / 450ma sockets to pyethernet module with on board power over ethernet(poe) receiver digital baseband chip handling LoRa/
(G)FSK packets LoRa Tx/Rx activity indication leds RF front-end with integrated Rf Tx power amplifier (PA) and Rx low noise amplifier
(LNA)V sockets to one of pycom modules such as Wipy3, Gpy, Lopy4 low power digital i and q rf multi-phy mode tranceiver Size: 42mm x 20mm x 3.5mm Version 1.1 03 ygate go invent 1.0 Overview 3.2 Power supply options:
- Micro USB.
- PoE (Power Over Ethernet) via the optional adapter board.
- LiPo or Li-Ion battery.
- LiPo battery charging via the USB or the PoE ports. 3.3 Available signals on headers:
- VCC supply.
- 3.3V from the Pycom module.
- VCC supply that goes off when the system enters sleep mode.
- 3V3 from the Gateway subsystem.
- UART Tx and UART Rx.
- GPS PPS input for adding an external GPS
- GND 3.4 Wireless connectivity options:
- WiFi: In combination with the WiPy3, LoPy4 or the GPy.
- Ethernet: In combination with the Ethernet adapter board. This also requires a Pycom module to provide the TCP stack.
- LTE: In combination with the GPy.
- Bluetooth. 3.5 Absolute maximum ratings:
- Operating temperature range depends on edition (please check with your distributor):
- Commercial temperature range: 0 to 70 C
- Industrial temperature range: -40 to +85 C
- Maximum RF Input Level: -10 dBm (0.1 mW) The Pygate is a super low-cost 8-channel LoRaWAN gateway that comes in the shape of a shield. Its got the well-known form factor from our other shields and you can connect your much loved WiPy3, LoPy4 or a GPy to it. Hook in your Pycom development boards up and you have yourself a nifty little decentralized IoT network in one go. Pygate also ts inside the Universal IP67 Case so you dont have to limit yourself to indoors. 2.0 Features
- Dual SX1257 transceivers for a total of 8 channels support simultaneously
- Ability to work in hostile RF environments such as close to mobile phones, Wi-Fi Routers and Bluetooth devices.
- Frequencies: 863-870 MHz and 902-928 MHz
- Baseband processor: SX1308
- Compatible with WiPy3, GPy and LoP4
- Ultra-low power standby mode
- Ethernet with PoE via the optional daughter board
- Powered via USB, LiPo Battery and Power over Ethernet (PoE) injector via the optional daughter board
- 2mm pitch JST header for PHR-2 battery connector
(pin 1 [+], pin 2 [-])
- LiPo battery charging (BQ24040) via the USB port or Ethernet PoE daughter board
- USB to serial connection for the Pycom module with auto programming features
- Same form factor as the Expansion Board v3.x
- Dimensions: 65mm (L) x 50mm (W) x 16mm (H)
- Fits the universal IP67 Case for outdoor use 3.0 Specications 3.1 Hardware conguration:
- Transceivers: Dual Semtech SX1257 transceivers for a total of 8 channels support.
- Baseband processor: Semtech SX1308 running @
133MHz.
- Frequency range: 863-870 MHz and 902-928 MHz
- LoRaWAN regions: EU868, US915, AU915, AS923, IN865
- Ultra low power standby mode allows backup battery operation.
- Same form factor as the expansion board.
- Compatible with WiPy3, GPy and LoPy4.
- USB to serial connection for the Pycom module with auto-programming features. Version 1.1 04 ygate go invent 4.0 Block Diagra m sx 1308 concentrator tx i/q rx i/q sx 1257 radio_a clkhs 133MHz XO osc. 32mhz clki32m tcxo rx i/q clko32m sx 1257 radio_b uart spi One of Boards:
WiPy 3.0 LoPy4 GPy saw lter 3dB PAD RF Tx RF Rx saw lter Z optimum LPF NC SE2435L FE module saw lter vcc power power manager uart<->usb vcp
(microchip pic) uUSB connector PyEthernet Ethernet
IEEE 802.3bt/802.3af PoE receiver RJ45 connector Figure 1
- Pygate Block Diagram
* blocks shown with a dashed outline are modules that are plugged into the Pygate
** PyEthernet module is not mandatory for the gateway operation, but recommended when Ethernet connectivity or Power over Ethernet functionality needed. Version 1.1 05 ygate go invent 5.0 Pinout 1. PyEthernet 3. Module
(WiPy3,GPy or LoPy4) RESET 2. Lithium battery
(Optional) Figure 2 Pygate pins and connectors 5. USB VCP Module UART RX/TX line jumpers (normally suppose to be snapped on) 4. POWER and UART from/to the Module Version 1.1 06 ygate go invent 5.1 PyEthernet socket pinout PyEthernet shield with PoE(Power over Ethernet) VCC_ETH PWR_FLAG J4 J8 3V3_MOD ETH_RST ETH_MISO 1 2 3 4 5 1 2 3 4 5 ETH_MOSI ETH_CSN ETH_SCK Conn_01x05 Conn_01x05 GND GND 3V3_MOD R36 100K ETH_INT Figure 3 Socket to PyEthernet 5.2 Lithium battery connector pinout BATTERY LiPo 3.6...4.2V
+BATT J2 GND Conn_JST_01x02 Figure 4 JST (S2B-PH-K-S) Header to Lithium battery Version 1.1 07 ygate go invent 5.3 Module (WiPy3, GPy or LoPy4) socket pinout WiPy3, GPy, LoPy4 VCC RESET UART_RX UART_TX RCO HOST_CSN FEM_EN C71 56pF 100R R31 X X X SX1257_RST HOST_MOSI HOST_SCK SX1308_RST GND SAFE_BOOT J5 J7 1 2 3 4 5 6 7 8 9 10 11 12 13 14 1 2 3 4 5 6 7 8 9 10 11 12 13 14 3V3_MOD ETH_MOSI ETH_CSN ETH_SCK RFPWR_EN ETH_RST ETH_INT ETH_MISO HOST_MISO RX_ON TX_ON BAT_MON Conn_01x14 Conn_01x14 SW1 B3U-1000P GND 3V3_MOD Figure 5 Socket to Pycom module 5.4 POWER and UART from/to the Pycom module header pinout
+3V3 VCC_RF VCC PWR/UART J6 1 2 3 4 5 6 7 8 3V3_MOD UART_RX UART_TX GPS_IN Conn_01x08 GND Figure 6 Header with Power, UART, Sync from a GPS signals Version 1.1 08 ygate go invent Pin 6.0 details The tables below provide description of the pins. Pin direction given from Py gate board point of view. 6.1 PyEthernet socket pin details Table 1 - J4 socket to a PyEthernet shield Pin Pin Name Type Description VCC_ETH Power In (+5V) Power coming from PoE of PyEtherent 3V3_MOD Power Out (+3.3V) Power to PyEthernet from a Pycom module ETH_RST Output ETH_MISO Input Ethernet PHY reset Ethernet PHY SPI MISO GND Power (GND) Ground 1 2 3 4 5 1 2 3 4 5 Pin 1 2 Table 2 - J8 socket to a PyEthernet shield Pin Type Pin Name ETH_CSN Output ETH_INT Input ETH_SCK Output 6.2 Lithium battery connector pinout Table 3 - J2 Battery connector pins Pin Name Type ETH_MOSI Output Ethernet PHY SP I MOSI Description Ethernet PHY SPI chip select Ethernet PHY i nterrupt line Ethernet PHY SP I clock GND Power (GND) Ground Description
+BA TT Power In (+3.7 V) Power coming fr om Lithium Polymer battery GND Power (GND) Ground Version 1.1 09 ygate go invent 6.3 Module (WiPy3, GPy or LoPy4) socket pinout Table 4 - J5 socket to a Pycom module Pin Type Pin Name Description RESET Output Pycom Module reset, active low 4 RC0 Input/Output 1 2 3 5 6 7 8 9 10 11 12 13 14 UART_RX Output UART_TX Input HOST_CSN Input FEM_EN Input NC NC NC Floating Floating Floating SX1257_RST Input HOST_MOSI Input HOST_SCK Input SX1308_RST Input SAFE_BOOT Output Module UART RX used for communication with PC and to program module in bootloader mode. Module UART TX used for communication with PC and to program module in bootloader mode. If tied to GND during boot, the decice will enter bootloader mode. Connected to the on-board RGB LED LoRa packets processor SPI chip select Power enable of RF Front-End Module Reserved Reserved Reserved Reset of IQ RF Transceivers LoRa packets processor SPI Master Output Slave Input LoRa packets processor SPI clock LoRa packets processor RESET To make Pycom module to enter the safe boot mode. Version 1.1 10 ygate go invent Table 5 - J7 socket to a Pycom module Pin Name Type VCC Power Out (+VCC) Description GND Power (GND) Ground 3V3_MOD Power Input (+3.3V) Pin 1 2 3 4 5 6 7 8 9 10 11 12 13 14 ETH_MOSI Input ETH_CSN Input ETH_SCK Input RFPWR_EN Input ETH_RST Input ETH_INT Output ETH_MISO Output HOST_MISO Output TX_ON Output BAT_MON Output VCC is combined power from thre e sources , USB, Power-over-Ethernet or Lithium battery. Once USB and PoE power is not available lithium battery will supply the Py gate, else the battery will be charged with charging current 450mA.
+3. 3V power coming from the Pycom module voltage regulator PyEthernet shield SPI Master Output Slave Input PyEthernet shield SPI Chip Select PyEthernet shield SPI Clock RF power ON/OFF control signal PyEthernet shield reset PyEthernet shield interrupt line PyEthernet shield SPI Master Input Slave Output LoRa packets processor SPI Master Input Slave Output LoRa TX activity signal (TX LED) VCC Voltage Monitor (100k + 100k voltage divider) RX_ON Output LoRa RX activity signal (RX LED) Version 1.1 11 ygate go invent 6.4 POWER and UART from/to the Module header pinout Table 6 - J6 header pins Pin Type Pin Name Description VCC Power Out (+VCC) VCC is combined power from thre e sources , USB, Power-over-Ethernet or Lithium battery. VCC_RF Power Out (+VCC_RF) VCC power controlled by RFPWR_EN signal
+3V3 Power Out (+3V3) 3V3_MOD Power Out (+VCC_MOD)
+3. 3V coming form voltage regulator supplied by VCC_RF
+3. 3V power coming from the Pycom module voltage regulator UART_RX Input See J5 pin 2 description UART_TX Output See J5 pin 3 description GPS_IN Input
*Optional 1 pulse-per-second synchronization signal from a GPS receiver. GND Power (GND) Ground 1 2 3 4 5 6 7 8 6.5 Synchronization signal from a GPS receiver Figure 7 1 pulse-per-second synchronization signal from a GPS receiver UTC 12:00:00m UTC 12:00:01 PPS 100 mS 1 Sec Version 1.1 12 ygate go invent 7.0 API overview For details about software please visit:
https://docs.pycom.io/firmwareapi/pycom/
machine/pygate/
8.0 Conguring Py gate For details about conguration please visit:
https://docs.pycom.io/tutorials/all/pygate/
Version 1.1 13 ygate go invent 9.0 Programming the device IF0 to IF7 LoRa Channels Refer to WiPy3, Gpy or LoPy module users manual 10.0 Power AVG (no radio) 45mA AVG (TTN gateway) 565mA MIN (TTN gateway) 220mA MAX (TTN gateway) 750mA 11.0 LoRa 11.1 Supported features Table 15 - J2 Battery connector pins 11.2 Reception Paths Characteristics The SX1308/ SX1301 digital baseband chip contains 10 programmable reception paths. Those paths have differentiated levels of programmability and allow different use cases. It is important to understand the differences between those demodulation paths to make the best possible use from the system. IF8 LoRa Channel This channel can be connected to Radio A or B using any arbitrary intermediate frequency within the allowed range. This channel is LoRa only. The demodulation bandwidth can be congured to be 125, 250 or 500 kHz. The data rate can be congured to any of the LoRa available data rates
(SF7 to SF12) but, as opposed to IF0 to 7, ONLY the congured data rate will be demodu -lated. This channel is intended to serve as a high speed backhaul link to other gateways or infrastructure equipment. This demodulation path is compatible with the signal transmitted by the SX1272 & SX1276 chip family. IF9 (G)FSK Channel Same as previous except that this channel is connected to a GFSK demodulator. The channel bandwidth and bitrate can be adjusted. This demodulator offers a very high level of congurability, going well beyond the scope of this document. The demodulator characteristics are essentially the same than the GFSK demodulator implemented on the SX1232 and SX1272 Semtech chips. This demodulation path can demodulate any legacy FSK or GFSK formatted signal. Those channels can be connected individually to Radio A or B. The channel bandwidth is 125 kHz and cannot be modied or congured. Each channel IF frequency can be individually congured. On each of those channels any data rate can be received without prior conguration. Several packet using different data rates may be demodulated simultaneously even on the same channel. Those channels are intended to be used for a massive asynchronous star network of 10000s of sensor nodes. Each sensor may use a random channel (amongst IF0 to 7) and a different data rate for any transmission. Typically sensor located near the gateway will use the highest possible data rate in the xed 125kHz channel bandwidth (e.g. 6 kbit/s) while sensors located far away will use a lower data rate down to 300 bit/s
(minimum LoRa data rate in a 125 kHz channel). The SX1308/ SX1301 digital baseband chip scans the 8 channels (IF0 to IF7) for preambles of all data rates at all times. The chip is able to demodulate simultaneously up to 8 packets. Any combination of up to 8 packets is possible (e.g. one SF7 packet on IF0, one SF12 packet on IF7 and one SF9 packet on IF1 simultaneously). The SX1308/ SX1301 can detect simultaneously preambles corresponding to all data rates on all IF0 to IF7 channels. However it cannot demodulate more than 8 packets simultaneously.This is because the SX1308/ SX1301 architecture separates the preamble detection and acquisition task from the demodulation process. The number of simultaneous demodulation (in this case 8) is an arbitrary system parameter and may be set to any value for a customer specic circuit. The unique multi data-rate multi-channel demodulation capacity of channels 0 to 7 allow innovative network architecture to be implemented:
- End-point nodes can change frequency with each transmission in a random pattern. This provides vast improvement of the system in term of interferer robustness and radio channel diversity
- End-point nodes can dynamically perform link rate adaptation based on their link margin without adding to the protocol complexity. There is no need to maintain a table of which end point uses which data rate, because all data rates are demodulated in parallel.
- True antenna diversity can be achieved on the gateway side. Allows better performance for mobile nodes in difcult multi-path environments. Packet Engine and Data Buffers Version 1.1 14 ygate go invent 11.3 Packet Engine and Data Buffers 11.3.1 Receiver Packet Engine Each time any of the demodulators decodes a packet, it is tagged with some additional information and stored in a shared data buffer (the data buffer size is 1024 bytes). For this purpose a specic data buffer management block reserves a segment with the necessary length in the data buffer and at the same time, stores the start address and the length of the packet eld in a small FIFO type structure (named the access FIFO). The FIFO can contain up to 16
(start_addr, length) pairs. A status register contains at any moment the number of packets currently stored in the data buffer
(and in the access FIFO). To retrieve a packet, Pycom module (host) rst advances 1 step in the access FIFO by writing 1 to the next bit. Then reads the (start_addr, length) information. Now Pycom module can retrieve in one SPI burst operation the entire packet and associated meta-data by reading length+16 bytes starting at address start_addr in the data buffer .. To do so, rst position the HOST address pointer to start-addr, then read length + 16 bytes from the packet_data register. At the end of each byte the HOST address pointer is automatically incremented. Access FIFO
(start_addr1, lenght1) Data buffer Data... 1:Read start_addr and lenght Modem address Modem data HOST address HOST data 2:Retrieve Packet from data buffer Figure 8 Access FIFO and Data Buffer Version 1.1 15 ygate go invent The packet data is organized as follows:
Table 7 LoRa Packet data elds Offset from strart pointer Data stored Comment Packet Buffer data organization PAYLOAD PAYLOAD DATA 0
... .. .. .. payload size -1 payload size CHANNEL 1 to 10 as described by block diagram
+1 payload size SF[3:0],CR[2:0],CRC_EN
+2 payload size SNR Average averaged SNR in dBon the packet lenght
+3 payload size SNR MIN
+4 payload size SNR MAX
+5 payload size RSSI
+6 payload size TMESTAMP[7:0]
+7 payload size TMESTAMP[15:8]
+8 payload size TMESTAMP[23:16]
+9 payload size TMESTAMP[31:24]
+10 payload size CRC Value[7:0] CRC
+11 payload size Value[15:8]
+12 payload size MODEM ID minimum SNR (dB)recorded d uring packet lenght maximum SNR recorded during packet lenght Channel signal strenghtin dB averaged during packet 31 bit time stamp, 1 us step Value of the computet CRC 16
+13 payload size RX MAX BIN POS[7:0] RX
+14 payload size MAX BIN POS[15:8]
Correaltion peak position Version 1.1 16 ygate go invent
+15 payload size RX CORP SNR Detection correlation SNR desired acknowledge packet. This allows very tight reception interval windows on the battery powered end points hence improved battery life.
+16 payload size RESERVED
+17 payload size RESERVED This means that the host has to read 16 additional bytes on top of each packet to have access to all the meta-data. If the host is only interested in the payload itself + the channel and the data rate used, then payload + 2bytes is enough. 11.4 Transmitter Packet Engine The Pyg ate transmitter c an be used to s end packets. The following parameters can be dynamically programmed with each packet:
- Radio channel
- FSK or LoRa modulation
- Bandwidth, data rate, coding rate (in LoRa mode), bit rate and Fdev (in FSK mode)
- RF output power
- Time of departure (immediate or differed based on the gateway hardware clock with 1us accuracy) All those dynamic parameter elds are sent alongside the payload in the same data buffer. The data buffer can only hold a single packet at a time (next packet to be sent). The scheduling and ordering task is let to the host micro-processor. The host micro-processor can program the exact time of departure of each packet relative to the gateway hardware clock. The same clock is used to tag each packet received with a 32bits timestamp. The same 32bits time stamp principle is used in TX mode to indicate when to transmit exactly. This removes the real time constraint from the host micro-processor and allows very precise protocol timing.( For example, if the protocol running on the end point expects and acknowledge exactly one sec after the end of each packet of its uplink). The host micro-processor pulls the uplink packet from the RX packet engine, realizes that it must send an acknowledge, takes the uplink packet time stamp, simply increments it by 1 sec and uses that value to program the time of departure of the acknowledge packet. Exactly one second (+/- 1us) after the uplink packet was received, the gateway will transmit the Version 1.1 17 ygate go invent The packet structure for trans mission is as follow:
Table 8 - Packet structure for transmission Byte Sube ld Description Comment Channel Frequency Fchan/32MHz*2^19 23:16 15:8 7:0 31:24 23:16 15:8 7:0 7:6 5:5 4:4 3:0 0 1 2 3 4 5 6 7 8 Start Time Value at the timer at which the modem has to start (in us) Modulation Type 0:LoRa, 1: FSK Select radio A (0) or B (1)
>7:20dBm, otherwize 14dBm Reserved Radio select Tx power Reserved Version 1.1 18 ygate go invent LoRa:
11 12 13 14 15 7:7 6:4 3:0 7:3 2:2 1:0 15:8 7:0 Byte Sub eld Description Comment Payload CRC16 enable Enables CRC16 9 Coding Rate Coding Rate =4/(4+CR) SF 6 to12 10 7:0 Payload lenght numbers of bytes Modulation Bandwidth 2:500, 1:250, 0:125 kHz Preamble symbol number Number of symbols in the preamble Reserve Implicit header enable Reserved Reserved Version 1.1 19 ygate go invent FSK:
9 10 7:0 7:0 0 Byte Sub eld Description Comment FSK frequency deviation Frequency deviation in kHz Payload length Number of bytes Packet mode 1 CRC enable 11 3:2 Dcfree ENC 4 Crc IBM 15:8 7:0 15:8 7:0 12 13 14 15 16 FSK Preamble Size FSK Preamble Size FSK Bit Rate FSK Bit Rate 0-> xed lenght 1-
>variable lenght 0-> No CRC 1->CRC 00-> DC free encoding off 01->Manchester encoding 10-> Whitening encoding 1->Reserved 0-> CCITT CRC 1->IBM CRC The number of preamble bytes send over the airbefore the sync pattern bit rate=32e6/(FSK bit rate) Payload rst byte up to 128 bytes Version 1.1 20 ygate go invent For words of more than 1 byte, MSBs are sent rst. Bytes 9 to 15 vary depending whether the FSK or the LoRa TX modem is being used. The user payload starts at byte 16. This is the rst byte that will be received by the end point. Bytes 0 to 15 are not transmitted and are just used to dynamically congure the gateway prior to emission. where:
- Radio A PLL is set to 867.0 MHz
- Radio B PLL is set to 868.4 MHz
- The system uses 8 separate 125 kHz LoRa channels for star connection to sensors
- One high speed 250 kHz LoRa channel for connection to a relay
- One high speed 200 kHz GFSK channel for meshing 11.5 Receiver IF Frequencies Conguration Each IF path intermediate frequency can be programmed independently from -2 to +2 MHz. The following sections give a few programming examples for various use cases. 11.5.1 PyGate Using 2 x SX1257 Radios The SX1257 RX PLLs can be congured to any frequency inside the 868/900 MHz ISM band with a 61 Hz step. The SX1257 streams I/Q samples through a 2 wire digital interface. The bits stream corresponds directly to the I/Q sigma delta ADCs outputs sampled at 32 MSps. This delta sigma stream must be low-passed and decimated to recover the available 80dB dynamic of the ADCs. After decimation the usable spectrum bandwidth is 400 kHz centered on the RX PLL carrier frequency. The following plot gives the spectral power content of the I/Q bit stream. Figure 9 - SX1257 Digital I/Q Power Spectral Density The quantization noise raises sharply outside the
-400 to+400 kHz range. For more details on the SX1257 radio specications please consult the specic product datasheet. The following plot represents a possible use case Version 1.1 21 ygate go invent IF1-250 kHz xed data rate LoRa back-haul channel IF2 64 kbit/sec GFSK channel IF3-6 LoRa Channels Multi-data rates IF7-10 LoRa Channels Multi-data rates 866.6 867.4 MHz 868.0 868.8 MHz Radio A Radio B In the previous example the various IF frequencies would be set as follow:
Figure 10 - Radio Spectrum Table 9 IF Frequency Set LoRa backhaul, xed dada-rate GFSK backhaul A: -312.5 kHz LoRa multi-data rate channel IF8 IF9 IF0 IF1 IF2 IF3 IF4 IF5 IF6 IF7 A: -125 kHz B: 0 kHz A: 62.5kHz A: 187.5 kHz A: 312 kHz B: - 312 kHz B: - 187 kHz B: 187.5 kHz B: 312.5 kHz If for example, 8 contiguous 125 kHz LoRa channels are desired the following conguration may be used:
- Radio A PLL is set to 867 MHz
- Radio B PLL is set to 876.5 MHz The two radio baseband spectrum overlap a little bit. Version 1.1 22 ygate go invent IF1 500kHz xed data rate LoRa back-haul superposed with sensor channels IF3-6 LoRa Channels Multi-data rates IF7-10 LoRa Channels Multi-data rates Radio B 867.1 - 867.1 MHz Radio A 866.6 -
867.4 MHz LoRa backhaul, xed dada-rate GFSK backhaul B: -187.5 kHz LoRa multi-data rate channel Figure 11 - Radio Spectrum The following IF frequencies are used:
Table 10 IF Frequency Used IF8 IF9 IF0 IF1 IF2 IF3 IF4 IF5 IF6 IF7 A: 0 kHz Not used B: -62.5kHz B: 62.5 kHz B: 187.5 kHz A: -187.5 kHz B: - 187 kHz A: 62.5 kHz A: 187.5 kHz Note : As shown in this example the 500 or 250 kHz IF1 LoRa channel may overlap with the multidata rate IF3 to 10 channels. Transmissions happening in the IF7 to 10 channels will be noise like for the IF1 LoRa demodulator and reciprocally. It is however better from a performance point of view to separate as much as possible different channels mainly when the associated signal powers are very different (like between a backhaul link which usually enjoys line-of-sight attenuation and sensor link with very low signal levels). Version 1.1 23 ygate go invent 12.0 Mechanical Specications Figure 12 - Mechanical drawing (top down view) Units: mm
* Tallest component: 12 mm Version 1.1 24 ygate go invent 13.0 Ordering information Table 1- Ordering information Product EAN Description 604565285904 604565285973 604565285911 PyGate 868 Mhz PyGate 915 Mhz PoE Adapter for PyGate Description Contents PyGate 868 Mhz with PoE PyGate 915 Mhz with PoE PyGate 604565285904 and PoE 604565285911 PyGate 604565285973 and PoE 604565285911 13.1 Bundles Table 12 Bundles 14.0 Packaging Figure 10 Mechanical drawing of packaging Units: mm The module will come inside a reusable antistatic bag. If the module has Total weight inc. packaging (with he aders): __g Total headers it will also be ins erted into antistatic foam. weight inc. packaging (with out headers): __g Version 1.1 25 ygate go invent 15.0 Certication Certification of Pygate cover
- RED Directive
- CE
- FCC
- IC
- RCM Regulatory Information 15.1 EU Regulatory Conformance Hereby, Pycom Ltd declares that this device is in compliance with the essential requirements and other relevant provisions of Directive 1999/5/EC 15.2 Federal Communication Commission Compliance Statement ID: 2AJMTPYGATE) LoRa gateway, Pygate (FCC must contain one of the authorized co-located support for normal operation and modules simultaneous transmission:
-WiPy 3.0 (FCC ID: 2AJMTWIPY3R) for WiFi 2.4GHz/
BLE/BT
-LoPy4 1.0 (FCC ID: 2AJMTLOPY4R) for WiFi 2.4GHz/
BLE/BT
-GPy 1.0 BLE/BT/LTE
(FCC ID: 2AJMTGPY01R) for WiFi 2.4GHz/
15.2.1 Federal Communication Commission Interference Statement 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. 2. This device must accept any interference received, including interference that may cause undesired operation. CAUTION: Changes or modications not expressly approved by the party responsible for compliance could void the users authority to operate the equipment. NOTE:
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 against harmful interference in a residential installation. This equip-ment 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 off and on, the user is encouraged to try to correct the interference by one or more of the following measures:
- Reorient or relocate the receiving antenna.
- Increase the separation betwee n the equipment and receiver.
- Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.
- Consult the dealer or an experienced radio/TV technician for help. 15.2.2 RF Warning Statement To comply with FCC RF exposure compliance requirements, the antennas used for this transmitter must be installed to provide a separation distance of at least 20 cm from all persons and must not be colocated or operating in conjunction with any other antenna or transmitter not authorized.
-The device uses an external monopole antenna with maximum gain of 0.87dBi for LoRa. 15.2.3 End Product Labelling This device complies with Part 15 of FCC rules. Operation is subject to the following two conditions:
- this device may not cause harmful interference and
- this device must accept any interference received, including interference that may cause undesired operation. Version 1.1 26 ygate go invent 15.3 ISED Regulatory Approval 15.3.2 ISED RF exposure statement:
This radio transmitter [22263-PYGATE] has been approved by Innovation, Science and Economic Development Canada to operate with the antenna types listed below, with the maximum permissible gain indicated. Antenna types not included in this list that have a gain greater than the maximum gain indicated for any type listed are strictly prohibited for use with this device.
-The device uses an external monopole antenna with maximum gain of 0.87dBi for LoRa. This equipment complies with ISED radiation exposure limits set forth for an uncontrolled environment. This equipment should be instal led and operated with minimum distance 20cm between the radiator& your body. This tra nsmitter must not be colocated or operating in conjunction with any other antenna or transmitter. Le rayonnement de la classe b repecte ISED fixaient un environnement non contrls.Installation et mise en uvre de ce matriel devrait avec changeur distance minimale entre 20 cm ton corps.Lanceurs ou ne peuvent pas coexister cette antenne ou capteurs avec dautres. 15.4 Manual Information to the End User The maximum operating ambient temperature of the equipment declared by the manufacturer is 0 70 C Receiver category 3. Pygate is an end product that does not require a case, but inside the plastic Pycom it can t Universal IP67 Case for outdoor use. It is up to the purchaser to decide whether to use it with the case, but if it is used with a non-plastic case, the measurement needs to be re-evaluated. Pygate (IC: 22263-PYGATE) LoRa gateway, must contain one of the authorized co-located modules for normal operation and support simultaneous transmission:
-WiPy 3.0 (IC: 22263-WIPY3R) for WiFi 2.4GHz/BLE/
BT
-LoPy4 1.0 (IC: 22263-LOPY4R) for WiFi 2.4GHz/BLE/
BT
-GPy 1.0 (IC 22263-GPY01R) for WiFi 2.4GHz/BLE/BT/
LTE 15.3.1 ISED RSS Warning ISED RSS Warning: This device complies with Innovation, Science and Economic Development Canada licence-
exempt RSS standard(s). Operation is subject to the following two conditions:
(1) this device may not cause interference, and
(2) this device must accept any interference, including interference that may cause undesired operation of the device. Le prsent appareil est conforme aux CNR d'ISED applicables aux appareils r adio exempts de licence. L'exploitation est autorise aux deux conditions suivantes:
(1) l'apparei l ne doit pas produire de brouillage, et (2) l'utilisateur de l'appareil doit accepter tout brouillage radiolectrique subi, mme si le brouillage est susceptible d'en compromettre le fonctionnement. Version 1.1 27 ygate go invent 16.0 Revision History Table 12 Document revision history Revision / Date Description Rev 0.1 / 11.11.2019 Rev 0.1 / 11.11.2019 First DRAFT release Rev 1.0 / 11.04.2020 First Release Rev 1.1 / 10.01.2022 Amends to First R elease Version 1.1 28