PYGATE PYCOM | Alldatasheet
Document overview
- Manufacturer or author: Provided By alldatasheet.com(free datasheet download site)
- PDF pages: 28
Technical content
Version 1.0
02Version 1.0 ygate go invent 1.0 03 2.0 04 3.1 04 3.2 04 3.3 04 3.4 04 3.5 04 15.1 26
13.1 Bundles 25
15.2 EU Regulatory Conformance Federal Communication Commission Interference Statement
15.2.1 RF Warning Statement 26
15.2.2 OEM integrator conditions 26
15.2.3 27 15.2.4 Manual Information to the End User 275.1 07 5.2 07 5.3 08 085.4 4.0 05 5.0 06 6.0 09 6.1 09 6.2 09 6.3 10 6.4 6.5 12 7.0 13 8.0 13 9.0 Overview Feature s Specifications Hardware configuration Power supply options Available signals on headers Wireless connectivity options Absolute maximum ratings Block Diagram 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 (WiPy3, GPy or LoPy4) socket pinout POWER and UART from/to the module header pinout Synchronization signal from a GPS receiver. API overview Configuring PyGate Programming the device 14
10.0 Power 14
11.0 Memor y Map 14
11.1 14 11.2 14 11.3 Supported features Reception Paths Characteristics Packet Engine and Data Buffers 15 11.3.1 15 11.4 Receiver Packet Engine Transmitter Packet Engine 17
11.5 Receiver IF Frequencies Config uration 21
11.5.1 PyGate Using 2 x SX1257 Radios 21
12.0 Mechanical Specifications 24
13.0 Ordering information
14.0 Packaging
15.0 Certification
16.0 Revision History
3.0
03Version 1.0 ygate go invent Tact switch to enter programming mode to lithium battery VCP over USB to configure gateway from a terminal console 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 LoRa antenna U.FL connector LED on when pic is powered (green light) Tact switch to enter save boot Size: 42mm x 20mm x 3.5mm
04Version 1.0 ygate go invent
1.0 Overview
The Pygate is a super low-cost 8-channel LoRaWAN gateway that comes in the shape of a shield. It’s 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 fits inside the Universal IP67 Case so you don’t 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 use3.1
3.0 Specifications
Hardware configuration: - 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.
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)
05Version 1.0 ygate go invent Figure 1 * 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. - Pygate Block Diagram
4.0 Block Diagram
XO osc. One of Boards: WiPy 3.0 LoPy4 GPy clki32m saw filter RF Tx RF Rx NC LPF 3dB PAD saw filter saw filter clko32m uart vcc power power manager uart<->usb vcp (microchip pic) uUSB connector RJ45 connector PyEthernet Ethernet IEEE 802.3bt/802.3af PoE receiver spi sx 1257 radio_a SE2435L FE module Z optimum 32mhz tcxo sx 1257 radio_b
06Version 1.0 ygate go invent
5.0 Pinout
- Lithium battery (Optional) 1. PyEthernet Figure 2 – Pygate pins and connectors 3. Module (WiPy3,GPy or LoPy4) RESET 4. POWER and UART from/to the Module 5. USB VCP Module UART RX/TX line jumpers (normally suppose to be snapped on)
07Version 1.0 ygate go invent
5.1 PyEthernet sock et pinout
5.2 Lithium batte ry connector p inout
Figure 3 – So cket to PyEthernet Figure 4 – JST (S2B-PH-K-S) Header to Lithium battery VCC_ETH PyEthernet shield with PoE(Power over Ethernet) R36 100K J4 J8 PWR_FLAG ETH_INT 3V3_MOD ETH_RST ETH_SCK ETH_CSN ETH_MOSI GND GND Conn_JST_01x02 +BATT BATTERY LiPo GND Conn_01x05 Conn_01x05 ETH_MISO 3V3_MOD
08Version 1.0 ygate go invent
5.3 Module (WiPy3, GPy or LoPy4) socket pinout
5.4 POWER and UART from/to the Pycom
Figure 5 – Socket to Pycom module Figure 6 – Header with Power, UART, Sync from a GPS signals +3V3 VCC_RF VCC PWR/UART 3V3_MOD UART_RX UART_TX GPS_IN 3V3_MOD GND Conn_01x08 WiPy3, GPy, LoPy4 RESET 3V3_MOD ETH_MOSI ETH_MISO BAT_MON ETH_CSN ETH_SCK ETH_RST ETH_INT RFPWR_EN J5 J7 VCC UART_RX HOST_CSN HOST_MOSI HOST_MISO RX_ON TX_ON HOST_SCK SX1257_RST SX1308_RST Conn_01x14 SW1 Conn_01x14 B3U-1000P FEM_EN UART_TX RCO C71 56pF 100R R31 SAFE_BOOT GND GND X X X
09Version 1.0 ygate go invent
6.0 Pin
The tables below provide description of the pins. Pin direction given from Pyg ate board point of view.
6.1 PyEthernet socket pin details
6.2 Lithium battery connector
Table 3 - J2 Battery connector pins Table 2 - J8 socket to a PyEthernet shield Pin Pin TypeName
Description
1 VCC_ETH Power In (+5V) Power coming from PoE of PyEtherent
Power to PyEthernet from a Pycom module Ethernet PHY reset Ethernet PHY SPI MISO Ground Power Out (+3.3V) Output Input Power (GND) 2 3V3_MOD
3 ETH_RST
4 ETH_MISO
5 GND
1 ETH_MOSI Output Ethernet PHY SP I MOSI
Ethernet PHY SPI chip select Ethernet PHY i nterrupt line Ethernet PHY SP I clock Ground Output Input Output Power (GND)
2 ETH_CSN
3 ETH_INT
4 ETH_SCK
1 +BATT Power In (+3.7 V) Power coming fr om Lithium Polymer battery GroundPower (GND)2 GND
10Version 1.0 ygate go invent
6.3 Module (WiPy3, GPy or LoPy4) socket pinout
Table 4 - J5 socket to a Pycom module Pin Pin TypeName
1 RESET Output Pycom Module reset, active low
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, t he decice will enter bootloader mode. Connected to the on-board RGB LED LoRa packets processor SPI chip select Output Input Input/Output Input
2 UART_RX
3 UART_TX
4 RC0
5 HOST_CSN
6 FEM_EN Input Power enable of RF Front-End Module
Reset of IQ RF Transceivers Floating Floating Floating Input 7 NC 8 NC 9 NC
10 SX1257_RST
11 HOST_MOSI Input LoRa packets processor SPI Master
LoRa packets processor SPI clockInput12 HOST_SCK
13 SX1308_RST Input LoRa packets processor RESET
To make Pycom module to enter the safe boot mode.Output14 SAFE_BOOT
11Version 1.0 ygate go invent Table 5 - J7 socket to a Pycom module Pin Pin TypeName
1 VCC Power Out (+VCC) VCC is combined power from three sources,
USB, Power-over-Ethernet or Lithium battery. Once USB and PoE power is not available lithium battery will supply the Pygate, else the battery will be charged with charging current 450mA. Ground PyEthernet shield SPI Master Output Slave Input PyEthernet shield SPI Chip Select Power (GND) Input Input
2 GND
+3.3V power coming from the Pycom module voltage regulatorPower Input (+3.3V)3 3V3_MOD
4 ETH_MOSI
5 ETH_CSN
6 ETH_SCK Input PyEthernet shield SPI Clock
RF power ON/OFF control signa l PyEthernet shield reset PyEthernet shield interrupt line PyEthernet shield SPI Master Input Slave Output Input Input Output Output
7 RFPWR_EN
8 ETH_RST
9 ETH_INT
10 ETH_MISO
11 HOST_MISO Output
LoRa packets processor SPI Master Input Slave Output LoRa RX activity signal (RX LED)Output12 RX_ON
13 TX_ON Output LoRa TX activity signal (TX LED)
VCC Voltage Mon itor (100k + 100k voltage divider)Output14 BAT_MON
12Version 1.0 ygate go invent
6.4 POWER and UART from/to the Module header pin out
6.5 Synchronization signal from a GPS receiver
UTC 12:00:00m UTC 12:00:01 100 mS PPS
1 Sec
Figure 7 – 1 pulse-per-second synchronization signal from a GPS receiver TypeName
1 VCC Power Out (+VCC) VCC is combined power from three sources, USB,
Power-over-Ethernet or Lithium battery. +3.3V coming form voltage regulator supplied by VCC_RF +3.3V power coming from the Pycom module voltage regulator Power Out (+VCC_RF) Power Out (+VCC_MOD) Input
2 VCC_RF VCC power controlled by RFPWR_EN signal
Power Out (+3V3)3 +3V3 4 3V3_MOD
5 UART_RX
6 UART_TX Output
*Optional 1 pulse-per-second synchronization signal from a GPS receiver. Ground Input Power (GND)
7 GPS_IN
8 GND
13Version 1.0 ygate go invent
7.0 API overview
8.0 Configuring Pygate
For details about configur ation please visit: https://docs.pycom.io/tutorials/all/pygate/ For details about software please visit: https://docs.pycom.io/firmwareapi/pycom/ machine/pygate/
14Version 1.0 ygate go invent
9.0 Programming the device
Refer to WiPy 3, Gpy or LoPy m odule users manual
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 configured to be 125, 250 or 500 kHz. The data rate can be configured to any of the LoRa available data rates (SF7 to SF12) but, as opposed to IF0 to 7, ONLY the configured data rate will be demodu-l ated. 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 configurability, 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. IF0 to IF7 LoRa Channels Those channels can be connected individually to Radio A or B. The channel bandwidth is 125 kHz and cannot be modified or configured. Each channel IF frequency can be individually configured. On each of those channels any data rate can be received without prior configuration. 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 10000’s 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 fixed 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 specific 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 difficult multi-path environments. Packet Engine and Data Buffers
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 pi ns
15Version 1.0 ygate go invent 1:Read start_addr and lenght 2:Retrieve Packet from data buffer Data buffer Modem address Modem data HOST address HOST data Access FIFO Data... (start_addr1, lenght1) 11.3 11.3.1 Figure 8 – Access FIFO and Data Buffer Packet Engine and Data Buffers Receiver Packet Engine Each time any of the demodulators decodes a packet, it is tagged with some additional information and stored in a s hared data buffer (the data buffer size is 1024 byte s). For this purpose a specific data b uffer management block reserves a segment with the necessary le ngth in the data buffer and at the same time, stores the start address and the length of the packet field in a small FIFO type structure (named the access FIFO). The FIFO can contain up to 16 (start_addr, length) pairs. A status regis ter contains a t any moment th e number of packe ts currently s tored in the d ata buffer (and in the access FIFO). To retrieve a p acket, Pycom module (host) first advances 1 step in the access FIFO by writing 1 to the ‘next’ bit. Then reads the (start_addr, length) information. N ow 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, firs t position the HOST address p ointer to ‘start-addr’, then read ‘length’ + 16 byte s from the ‘packet_data’ register. At the end of each byte the HOST address pointer is automatically incremented.
16Version 1.0 ygate go invent The packet dat a is organized as follows: Table 7 – LoRa Packet data fields Offset from strart pointer Data stored Comment SNR MIN SNR Average SF[3:0],CR[2:0],CRC_EN PAYLOAD CHANNEL PAYLOAD DATA minimum SNR (dB)recorded during packet lenght maximum SNR recorded during packet lenght Packet Buffer data organization Channel signal strenghtin dB averaged during packet Correaltion peak position SNR MAX MODEM ID RX MAX BIN POS[7:0] RX MAX BIN POS[15:8] 1 to 10 as described by block diagram RSSI ... ... ... ... payload size -1 payload size +1 payload size +2 payload size +3 payload size +4 payload size +5 payload size +6 payload size +7 payload size +8 payload size +9 payload size +10 payload size +11 payload size +12 payload size +13 payload size +14 payload size 31 bit time stamp, 1 us step averaged SNR in dBon the packet lenght Value of the computet CRC 16 TMESTAMP[7:0] TMESTAMP[15:8] TMESTAMP[23:16] TMESTAMP[31:24] CRC Value[7:0] CRC Value[15:8]
17Version 1.0 ygate go invent 11.4 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. Transmitter Packet Engine The Pygate 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 fields 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 desired acknowledge packet. This allows very tight reception interval windows on the battery powered end points hence improved battery life. Detection correlation SNR RESERVED RX CORP SNR RESERVED +15 payload size +16 payload size +17 payload size
18Version 1.0 ygate go invent Byte DescriptionSubfield Comment 0 23:16 Channel Frequency Fchan/32MHz*2^19 Value at the timer at which the modem has to start (in us) Start Time 1 15:8 2 7:0 3 31:24 4 23:16 5 15:8 Select radio A (0) or B (1) 0:LoRa, 1: FSK >7:20dBm, otherwize 14dBm Reserved Reserved Radio select Modulation Type Tx power 6 7:0 7:6 5:5 4:4 3:0 The packet struc ture for tran smission is a s follow: Table 8 - Pac ket structure for transmission
19Version 1.0 ygate go invent Byte DescriptionSubfield Comment 7:7 Coding Rate Payload CRC16 enable Payload lenght Enables CRC16 Coding Rate =4/(4+CR) 6 to12 2:500, 1:250, 0:125 kHz Reserve Implicit header enable Modulation Bandwidth 9 6:4 3:0 SF numbers of bytes10 7:0 7:3 11 2:2 Number of symbols in the preamblePreamble symb ol number Reserved Reserved 1:0 12 15:8 13 7:0 LoRa:
20Version 1.0 ygate go invent Byte DescriptionSubfield Comment 7:0 Payload length FSK frequency deviation FSK Preamble S ize The number of preamble bytes send over the airbefore the sync pattern bit rate=32e6/(FSK bit rate) up to 128 bytes FSK Preamble S ize FSK Bit Rate FSK Bit Rate Payload first byte Packet mode Frequency dev iation in kHz Number of bytes CRC enable 7:0 0 0-> fixed lengh t 1- >variable lenght 0-> No CRC 1->CRC 0-> CCITT CRC 1->IBM CRC 00-> DC free encoding off 01->Manchester encoding 10-> Whitening encoding 1->Reserved 3:211 Dcfree ENC Crc IBM 12 15:8 13 7:0 15:8 7:0 FSK:
21Version 1.0 ygate go invent Figure 9 - SX1257 Digital I/Q Power Spectral Density The SX1257 RX PLLs can be configured to any frequency insid e 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. The quantization noise raises sharply outside the -400 to+400 kHz range. For more details on t he SX1257 radio specifications please consult the specific product datasheet. The following plot represents a possible use case 11.5 For words of more than 1 byte, MSBs are sent first. 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 first byte that will be received by the end point. Bytes 0 to 15 are not transmitted and are just used to dynamically configure the gateway prior to emission. Receiver IF Frequencies Configuration 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
where: - Radio A PLL is s et 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
22Version 1.0 ygate go invent In the previous example the various IF frequencies would be set as follow: IF3-6 LoRa Channels Multi-data rates 866.6 Radio A 867.4 MHz 868.0 868.8 MHz Radio B IF7-10 LoRa Channels Multi-data rates IF1-250 kHz fixed data rate LoRa back-haul channel IF2 64 kbit/sec GFSK channel If for example, 8 contiguous 125 kHz LoRa channels are desired the following configuration 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. Figure 10 - Radio Spectrum Table 9 – IF Frequency Set IF8 IF9 IF0 IF1 IF2 IF3 IF4 IF5 IF6 IF7 A: -125 kHz B: 0 kHz A: -312.5 kHz LoRa backhaul, fixed dada-rate GFSK backhaul LoRa multi-data rate channel A: 62.5kHz A: 187.5 kHz A: 312 kHz B: - 312 kHz B: - 187 kHz B: 187.5 kHz B: 312.5 kHz
23Version 1.0 ygate go invent IF3-6 LoRa Channels Multi-data rates Radio B 867.1 - 867.1 MHz Radio A 866.6 -
867.4 MHz
IF1 500kHz fixed data rate LoRa back-haul superposed with sensor channels The following IF frequencies are used: Note : As show n 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 c hannels 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 Figure 11 - Rad io Spectrum Table 10 – IF Frequency Used possible diffe rent 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). IF8 IF9 IF0 IF1 IF2 IF3 IF4 IF5 IF6 IF7 A: 0 kHz Not used B: -187.5 kHz LoRa backhaul, fixed dada-rate GFSK backhaul LoRa multi-dat a rate channel 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
24Version 1.0 ygate go invent * Tallest component: 12 mm Figure 12 - Me chanical drawing (top down view) – Units: mm
12.0 Mechanical Specifications
Table 1- Ordering information
13.1 Bundles
Table 12 –Bundles Figure 10 – Mechanical drawing of packaging – Units: mm The module will come inside a reusable anti–static bag. If the module has headers it will al so be inserted into anti–static foam. Version 1.0 Total weight inc. packaging (with headers): __g Total weight inc. packaging (without headers): __g
604565285904 PyGate 868 Mhz
PyGate 868 Mhz with PoE PyGate 604565285904 and PoE 604565285911 PyGate 604565285973 and PoE 604565285911 PyGate 915 Mhz with PoE PyGate 915 Mhz PoE Adapter for PyGate 604565285973 604565285911
26Version 1.0 ygate go invent Certification of Pygate is ongoing. Please contact Pycom Sales for more details. To comply with FCC RF exposure compliance require-ments, 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 co–located or operating in conjunction with any other antenna or transmitter. 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 modifications not expressly approved by the party responsible for compliance could void the user’s authority to operate the equip- ment. 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.1 15.2
15.2.1 RF Warning Statement
Hereby, Pycom Ltd declares that this device is in compliance with the essential requirements and other relevant provisions of Directive 1999/5/EC Federal Communication Commission Interference Statement This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: This device is intended only for OEM integrators under the following conditions: - The antenna must be installed such that 20 cm is maintained between the antenna and users and - The transmitter module may not be co–located with any other transmitter or antenna. As long as the two conditions above are met, further transmitter test will not be required. However, the OEM integrator is still responsible for testing their end–product for any additional compliance requirements required with this module installed. To ensure compliance with all non– transmitter functions the host manufacturer is responsible for ensuring compliance with the module(s) installed and fully operational. For example, if a host was previously authorized as an unintentional radiator under the Declaration of Conformity procedure without a transmitter certified module and a module is added, the host manufacturer is responsible for ensuring that the after the module is installed and operational the host continues to be compliant with the Part 15B unintentional radiator requirements. The module is limited to OEM installation ONLY. The module is limited to installation in mobile or fixed application. We hereby acknowledge our responsibility to provide guidance to the host manufacturer in the event that they require assistance for ensuring compliance with the Part 15 Subpart B requirements. IMPORTANT NOTE: In the event that these conditions cannot be met (for example certain laptop configurations or co– location with another transmitter), then the FCC authorization is no longer considered valid and the FCC ID cannot be used on the final product. In these circumstances, the OEM integrator will be responsible for re– evaluating the end product (including the transmitter) and obtaining a separate FCC authorization.
15.2.2 OEM integrator conditions
27Version 1.0 ygate go invent This transmitter module is authorized only for use in device where the antenna may be installed such that 20 cm may be maintained between the antenna and users. The final end product must be labeled in a visible area with the following: “Contains FCC ID: 2AJMTPYGATE01”. The grantee’s FCC ID can be used only when all FCC compliance requirements are met. The following FCC part 15.19 statement has to also be available on the label: 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.The OEM integrator has to be aware not to provide information to the end user regarding how to install or remove this RF module in the user’s manual of the end product which integrates this module. In the user manual of the end product, the end user has to be informed that the equipment complies with FCC radio– frequency exposure guidelines set forth for an uncontrolled environment. The end user has to also be informed that any changes or modifications not expressly approved by the manufacturer could void the user’s authority to operate this equipment. The end user manual shall include all required regulatory information/warning as show in this manual. The maximum operating ambient temperature of the equipment declared by the manufacturer is 0 – 70 C Receiver category 3
15.2.4 Manual Information to the End User
15.2.3 End Product Labelling
28Version 1.0 ygate go invent Revision / Date Description Rev 0.1 / 11.11.2019 First DRAFT release
16.0 Revision Histo ry
Table 12– Document revi sion history