Y7GTGRF-3XXX-CWireless Data Logging System - 3000 Series

Tinytag Radio Data Loggers Technical Manual 1 Tinytag Radio Data Logger Technical Manual 01 1.1 About this Document This document describes the Tinytag radio data logger system. This document also describes characteristics of the Tinytag Explorer and the Radio Gateway Service that is installed alongside this software used with radio loggers. All users are encouraged to upgrade to the latest version and only version 4.7 is described in detail. 2 Table of Contents 02 1 Tinytag Radio Data Logger Technical Manual 1 1.1 About this Document 1 2 Table of Contents 2 3 Radio Gateway Service Computer Requirements 3 4 Radio System Component Overview 4 4.1 Tinytag Explorer 4 4.2 Radio Gateway Server 5 4.3 Receiver 6 4.4 Radio Logger 6 4.5 Repeater 6 4.6 Receiver Cables 6 4.7 Mesh Network 7 5 Point-to-Point Radio 8 6 Receiver Con! gurations 9 6.1 Direct 9 6.2 Multiple Receivers 9 6.3 Multiple Computers Running the Radio Gateway Service 9 Receiver Con! guration (Continued) 10 Receiver Con! guration (Continued) 11 6.4 Repeater 12 6.5 Back-to-Back Receivers 12 7 Mesh Network Behaviour 13 7.1 Switching On a Device 13 7.2 Moving a Device 13 7.3 Starting the Radio Gateway Service 13 7.4 Switching On the Receiver 13 7.5 Redundant Routing 13 Mesh Network Behaviour (Continued) 14 Mesh Network Behaviour (Continued) 15 Mesh Network Behaviour (Continued) 16 7.6 Radio Con! guration 17 7.6.1 Adjusting the Radio Range 17 7.6.2 Receive Sensitivity 17 7.6.3 Transmit Power 17 7.7 Very slow logging intervals 17 7.8 Very fast logging intervals 18 7.9 Data organisation 18 7.10 Alarms 18 8 Buttons and Lights 19 9 Rapid Installation 20 9.1 Introduction 20 9.2 Receiver First 20 9.3 Nearby Loggers Next 20 9.4 Distance Order 20 9.5 Don’t Rush It 20 9.6 Transplanting the Network to a New Location 20 10 Troubleshooting 21 10.1 Tinytag Explorer Status Bar Indicator Flashes Red 21 10.2 Firewall Con! guration 21 11 Data Logging 22 11.1 No stopping 22 11.2 Time zones 22 11.3 Current Readings 22 12 Other Radio Gateway Functions 23 12.1 Modbus 23 12.2 Data Export 23 12.3 Proprietary Radio Gateway Service Protocol 24 13 Modbus 25 13.1 Properties and Registers 25 13.2 Devices 25 13.3 Expected Values 25 13.4 Unit Identi! ers 25 13.5 Function Codes 25 13.6 32-bit Values 25 13.7 Freshness 25 13.8 Device Connection 25 13.9 Missing Properties 26 13.10 Concurrent Connections 26 13.11 Modsak 26 14 Power 27 14.1 Batteries 27 14.2 Low Power Warnings 27 14.3 The E# ect of the Mesh Network 27 15 Regulatory Compliance 28 Notes 29 3 Radio Gateway Service Computer Requirements 03 The requirements for running the Radio Gateway Service on a computer are shown below. Note that additional requirements apply if you are running Tinytag Explorer on the same computer. Operating System: Windows 2000, XP, Vista or Windows 7. Processor: 200MHz Pentium III processor or better Memory: 512Mb Hard Disk Space: At least 30Mb available Monitor for installation: Minimum 256 colours, resolution 800 x 600 The requirements for running the Radio Gateway Service on an existing server are shown below. CPU time: Negligible Memory: 20Mb Hard Disk Space: Typically 10Mb for programs, 5Mb for data. 4.1 Tinytag Explorer Software The radio edition of Tinytag Explorer is installed with the same installation disk as regular Tinytag Explorer but uses a di# erent activation code. This activation code adds the “radio” tab to the radio con! guration dialog box which allows the user to con! gure a Radio Gateway Server, which Tinytag Explorer can then connect to. The rest of Tinytag Explorer is unchanged. The graphing and data export features behave identically between wired and radio loggers. It is possible to create an overlay with data from mixed wired/radio sources, and it is possible to view this overlay on normal (non-radio) versions of Tinytag Explorer. This allows users with an existing investment in wired loggers to start using radio with minimal impact on their current processes. 4 Radio System Component Overview Tinytag Radio System Components Key Tinytag Radio Logger Tinytag Explorer Server Tinytag Repeater Tinytag Radio Gateway Service Master Tinytag Receiver Tinytag Receiver Cables Slave 04 4 Radio System Component Overview (Continued) 05 4.2 Radio Gateway Service The Radio Gateway Service is installed with Tinytag Explorer. The Radio Gateway is a windows service. This means it runs in the background as soon as the computer is turned on. Its purpose is to connect to the radio receiver, collate measurements, and make information available to Tinytag Explorer. The Radio Gateway Service bu# ers measurements (and other data) on disk in ! les with a .jf extension which use a proprietary ! le format. On a networked system, the Radio Gateway Service must be installed on the computer which is connected directly to the receiver. It then makes this information available to any networked computers running the radio edition of Tinytag Explorer. This can be used in various con! gurations: Note that this generally means there will only be one computer running the Radio Gateway Service in the system. It is possible to run it on more than one computer; this con! guration is described later in the “Receiver Con! gurations” section. NETWORK NETWORK 2. The Radio Gateway Service installed on a server. Many other users in the same o$ ce run Tinytag Explorer. 3. The Radio Gateway Service installed on one user’s computer. Many other users in the same o$ ce run Tinytag Explorer. 4. The Radio Gateway Service installed on one old computer in a dirty location near the receiver. Tinytag Explorer runs on a nice computer in a nice o$ ce. 1. Standalone. The Radio Gateway Service and Tinytag Explorer don’t have to be on the same computer, but they very often are. This con! guration is the most common, because it is the simplest. NETWORK 4 Radio System Component Overview (Continued) Ideally the Radio Gateway Service would be left running 24/7 to allow it to collate all data. No measurements will be lost if …

Text truncated - open the document above for the full version.

Company No. 1830348 VAT No: 643 3208 61 Gemini Data Loggers (UK) Ltd Scientific House, Terminus Road Chichester, PO19 8UJ UK t +44 (0) 1243 813000 f +44 (0) 1243 531948 e [email protected] w www.geminidataloggers.com DECLARATION TGRF-3XXX-C Wireless Data Logger family This product family is designed to provide monitoring of temperature, humidity, sensor voltages, currents or signals from various locations & relay the data back to a computer for analysis & logging. Any installation must comprise a minimum of 1 logger & 1 receiver, but typically would incorporate a large number of loggers, spread out over an area of 10s of thousands of square yards, each having up to 4 probes or signal inputs connected. The loggers automatically establish a wireless network between themselves, & learn their position & responsibilities within the network. The loggers only work with probes or input cables supplied by Gemini. The system is configured & controlled by custom software written by Gemini & supplied with the loggers. Without this software the system is inoperable. As with all the products produced by Gemini, it is intended for use by the industrial, commercial & scientific user only, & is marketed accordingly. We sell our products worldwide, through authorised distributors, & also direct to end- users. Our Terms & Conditions are published for distributors & end-users, printed on the back of all quotations, order acknowledgements and invoices, & include the clause: "The Gemini products mentioned in this document are for sale to & use by commercial, industrial or scientific users only." 15 th February 2010

Gemini Data Loggers (UK) Ltd Scientific House, Terminus Road Chichester, PO19 8UJ UK r +44 (0)1243 813000 t +44 (0)1243 531948 e [email protected] w www.geminidataloggers.com Request for Confidentiality Date: l gth January 201I Subject: Confidentiality Request for: YTGTGRF-3XXX-C Pursuant to FCC 47 CRF 0.457(d) and 0.459 and lC RSP-100, Section 10, the applicant requests that a part ofthe subject FCC application be held confidential. Type of Confidentiality Requ€stedExhibit Block Diagrams External Photos Intemal Photos Operation Description/Theory of Operation Paxts List & PlacementtsOM Tune-Up Procedr.re Schematics TFqt' qchrh Ph^t^c User's Manual I Short Term ! Short Term fl Short Term ! Short Term ! Short Term I Short Term Ll bnorT l erm ! Short Term ! Sho.t Tet* ! Permanent ! Permanent*r ! Permanent I Permanent I Permanent I Permanent ! Permanent* €tmrqrury Gemrnl Gemini Data Loggers (UK) Limited has spent substantial effort in developing this product and it is one ofthe first of its kind in industry. Having the subject information easily available to "competition" would negate the advantage th€y have achieved by developing this product. Not protecting the details ofthe design will result in financial hardship. Permanent Confi dentiality: The applicant requests the exhibits listed above as permanently confidential be permanently withheld from public review due to materials that contain trade seffets and proprietary information not customarily released to the public. Sincerelv. David Frioo - Technical Director DATA LOGGERS

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 FCC ID Y7GTGRF-3XXX-C 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 FCC ID Y7GTGRF-3XXX-C 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 FCC ID Y7GTGRF-3XXX-C 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 FCC ID Y7GTGRF-3XXX-C 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 FCC ID Y7GTGRF-3XXX-C 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 FCC ID Y7GTGRF-3XXX-C 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 FCC ID Y7GTGRF-3XXX-C 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 FCC ID Y7GTGRF-3XXX-C 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 FCC ID Y7GTGRF-3XXX-C 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 FCC ID Y7GTGRF-3XXX-C 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 FCC ID Y7GTGRF-3XXX-C 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 FCC ID Y7GTGRF-3XXX-C 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 FCC ID Y7GTGRF-3XXX-C 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 FCC ID Y7GTGRF-3XXX-C 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 FCC ID Y7GTGRF-3XXX-C 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 FCC ID Y7GTGRF-3XXX-C 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 FCC ID Y7GTGRF-3XXX-C 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 FCC ID Y7GTGRF-3XXX-C 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 FCC ID Y7GTGRF-3XXX-C 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 FCC ID Y7GTGRF-3XXX-C This device complies with part 15 of the FCC Rules. Operatio…

Text truncated - open the document above for the full version.

CIRCUIT DESCRIPTION - SCHEMATICS TGRF-3XXX-C Sheet 1 & 2 The Sheet 1 schematic covers the core of the logger; power supply, microcontroller, communications & radio transceiver. The Sheet 2 schematic covers the input signal processing. Sheet 1 SCHEMATIC: U1 is the MSP430F168 microcontroller, which controls the logger. The controlling firmware is programmed into its internal flash memory. The MSP430 also incorporates an 8-channel, 12 bit ADC, which is used for measuring the various inputs. The microcontroller is clocked by an internal 4MHz DCO. The firmware uses the external 32KHz clock (XTAL1) as a reference to keep the DCO on frequency. U3 is a 8KB FRAM memory, used as a buffer for logged data. U2 is a 512KB Flash memory used for storage of logged data. Q5 removes power from U2 when not required (to save battery power). The logger can be supplied with either a single 3.6v lithium cell or 2x 1.5v alkaline cells. There is a 4-way interconnect cable between the battery board & Conn6 on the logger board. If the alkaline option is fitted, the battery is connected between pins 1 & 3 of Conn6. Q10 connects pin 3 to ground if the polarity is correct (negative on pin 3), otherwise it remains off. Positive on pin 1 connects via Q9 to U7, a charge-pump power supply with 3.3v output. U10 is a voltage supervisor. If the input voltage rises above 3.4v its output goes high and switches off Q9, protecting U7 from excessive voltage. This is required in the event that a user fits lithium cells instead of alkaline. Q12 & R23, R24 are used by the microcontroller to apply a load to the alkaline battery when measuring the battery voltage via the ADC0 input. The regulated output of the charge pump is filtered by L6, C38 & connected via a link (pins 2 & 4) in the battery board cable to Q14 & Q7, which form the battery switch. The microcontroller can put U7 into "snooze mode" via R25, to reduce drain on the battery when current demand is low. If the lithium option is fitted, the cell is connected to pins 4 & 3 of Conn6. This connects the negative terminal to the polarity protection & the positive terminal to Q14, Q7. Q14, Q7 are controlled by the voltage at the junction of R5 & R6. If there is no external supply connected to the DC input socket then Q14 & Q7 will be on & Q6 will be off, connecting the battery supply through to Q8, the on/off switch, & disconnecting Q6, the external DC source. If a DC supply is connected to Conn5 or a PC is connected in the case of a logger configured as a receiver, then there will be a voltage (limited to 7v by zener D3) on the gates of Q6, Q7 & Q14. This will turn on Q6 & turn off the battery supply. U4 is an LDO regulator with 3.3v output. Q8 is used by the microcontroller, via Q11, to turn the logger on & off. R11 & C14 serve to temporarily turn on the power (& therefore boot the microcontroller) in the event of the power being lost & then restored again. The ON/OFF pushbutton signals the microcontroller that the user wishes to turn the logger on (or off). The microcontroller then actions the request via Q11. Q1 & Q2 are the RS-232 driver transistors, for communication with the PC (or another logger). Q3 & Q15 are the RS-232 receiver. Q13 is a pulse-counting input circuit, available to channel A via LK18. U9 is a magnetic sensor. It is monitored by the microcontroller during power-on boot-up. If the user swipes a magnet past the sensor position (adjacent to the LEDs) 8 times immediately after power-on then the factory default settings are reloaded (from program memory) & the data storage pointers are reset, effectively deleting all logged data. U6 is the integrated radio transceiver, a Chipcon (TI) CC1000. Its reference oscillator is driven by a 14.7456MHz crystal (XTAL2). Its operating frequency is generated by a phase-locked VCO. L1 is the VCO inductor. RF output from pin 4 is coupled to the 1/4 wave antenna via a low-pass pi-filter, L4, C18 & C19. Q4 allows the microcontroller to remove power from the transceiver when shutting down, which prevents any uncontrolled transmission. Pins 23 - 27 of U6 are the SPI bus connections to the microcontroller. These are used to both control the transceiver and to pass data. Pin 28 is the RSSI signal, monitored by ADC1 in the MSP430 to confirm that the frequency is clear prior to transmitting. The dual-colour LED (LED1) is for user-feedback. It flashes green once every 4s during normal operation & red if there is a problem, such as low-battery, not meshed with the network or an alarm threshold has been exceeded. Sheet 2 SCHEMATIC: The logger board has 4 5-pin I/O sockets, Conn1 - Conn4 for channels D to A. These are connected to the 5-pin connectors on the logger enclosure & used for all interconnection with external probes, signal inputs or PC communication. Solder-blob links are used on the board to connect various parts of the circuitry to these connectors, dependent on the required configuration. I/O pin connections: 1 - Ground 2 - Temperature probe (thermistor or RTD) on all channels, & Transmit RS-232 Data on channel A (via link LK10). 3 - Voltage input on all channels, & Clock output for external Humidity Probes on channels A & B (via links LK8 & LK17). 4 - Data from Humidity Probe on channels A & B (via links LK6 & LK15), Receive RS-232 Data on channel A (via link LK11). Unused on channels C & D. 5 - Power output for Humidity Probe on channels A & B (via links LK7 & LK16), DC power input (from RS-232 cable) on channel A (via link LK12). Unused on channels C & D. Links LK5, LK14, LK9 & LK13 connect shunt 59R resistors across the voltage inputs of the 4 channels, so that they can measure current instead. To conserve power, the supply voltage feeding the dividers for temperature measurements is only turned on only during the measurement cycle (Sensor_Pwr). TEMPERATURE The temperature sensor elements in the external probes form part of a resistive divider. If Pt1000 RTDs are to be used then the divider ratio is modified via links LK…

Text truncated - open the document above for the full version.

Hursley EMC Services Ltd. Unit 16, Brickfield Lane Chandlers Ford Hampshire. UK. SO53 4DP EMC TEST REPORT No. 10R363 CFR Issue#2: 8 th February 2011 Tel. +44 (0) 23 8027 1111 Fax. +44 (0) 23 8027 1144 e mail. [email protected] www.hursley-emc.co.uk EU Notified Body FCC & VCCI Registered BSMI Lab ID: SL2-IN-E-3008 FCC Part 15 Certification Report for the Gemini Data Logger (UK) Limited TinyTag Logger TGRF-3xxx-C (917.8 MHz) Project Engineer: R. P. St John James Approval Signatory Approved signatories: S. M. Connolly  J. A. Jones  The above named are authorised Hursley EMC Services engineers. . EMC TEST REPORT 10R363 CFR FCC Part 15 Certification Report Issue#2: 8 th February 2011 Page 2 of 16 Contents 1.0 DECLARATION ................................................................................................................................................3 1.1 STATEMENT OF COMPLIANCE................................................................................................................................3 1.2 RELATED SUBMITTAL(S) .......................................................................................................................................3 1.3 EUT MANUFACTURER..........................................................................................................................................3 2.0 EUT DESCRIPTION .........................................................................................................................................4 2.1 IDENTITY...............................................................................................................................................................4 2.2 PRODUCT OPERATION...........................................................................................................................................4 2.3 SUPPORT EQUIPMENT............................................................................................................................................4 2.4 EXERCISER PROGRAM...........................................................................................................................................4 3.0 MEASUREMENT PROCEDURE AND INSTRUMENTATION .................................................................5 3.1 EMI SITE ADDRESS & TEST DATE........................................................................................................................5 3.2 GENERAL OPERATING CONDITIONS......................................................................................................................5 3.3 RADIATED EMISSIONS...........................................................................................................................................6 3.4 CONDUCTED EMISSIONS........................................................................................................................................6 3.5 ENVIRONMENTAL AMBIENT..................................................................................................................................7 3.6 EMC TEST EQUIPMENT.........................................................................................................................................7 3.7 FIELD STRENGTH CALCULATION EXAMPLES.........................................................................................................7 4.0 TEST DATA .......................................................................................................................................................8 4.1 TRANSMITTER – RADIATED EMISSIONS.................................................................................................................8 4.2 TRANSMITTER (STANDBY) – RADIATED EMISSIONS..............................................................................................9 4.3 MODULATION BANDWIDTH...................................................................................................................................9 5.0 TEST PLOTS....................................................................................................................................................10 5.1 TRANSMITTER EMISSION PLOT, 30 TO 1000 MHZ...............................................................................................10 5.2 TRANSMITTER EMISSIONS (STANDBY) PLOT, 30 TO 1000 MHZ..........................................................................11 5.3 TRANSMITTER EMISSIONS PLOT, 1.0 TO 10.0 GHZ..............................................................................................12 5.4 TRANSMITTER EMISSION (STANDBY) PLOT, 1.0 TO 10.0 GHZ.............................................................................13 5.5 BANDWIDTH PLOT...............................................................................................................................................14 6.0 PHOTO LOG....................................................................................................................................................15 7.0 FCC LETTER..................................................................................................................................................16 Document History Issue#1: 17 th December 2010 was withdrawn and replaced by Issue#2: Field Strength calculation Examples added. EMC TEST REPORT 10R363 CFR FCC Part 15 Certification Report Issue#2: 8 th February 2011 Page 3 of 16 1.0 DECLARATION 1.1 Statement of Compliance The Equipment Under Test (EUT), as described and reported within this document, complies with the Part 15 of the FCC CFR 47 regulations. The EUT operates at a frequency of 917.8 MHz and complies with the emission requirements. Note: The EUT is a battery-operated device and therefore only radiated emission measurements were performed in the frequency range 30.0 MHz to 10.0 GHz. 1.2 Related Submittal(s) This is a single application for certification of a 917.8 MHz Transmitter. Note: The receiver used with the …

Text truncated - open the document above for the full version.