Murata Electronics North America DNT90E DNT90E User Manual 16 0152 Exhibit Cover

Murata Electronics North America DNT90E 16 0152 Exhibit Cover

Manual

5015 B.U. Bowman Drive Buford, GA 30518 USA Voice: 770-831-8048 Fax: 770-831-8598 Certification Exhibit FCC ID: HSW-DNT90E IC: 4492A-DNT90E FCC Rule Part: 15.247 IC Radio Standards Specification: RSS-247 ACS Project Number: 16-0152 Manufacturer: Murata Electronics North America Models: DNT90EC, DNT90EP Manual
www.Murata.comRF Product Department.Technical support +1.678.684.2000E-mail: tech_sup@murata.comPage 1 of 80DNT90E Integration Guide - 04/13/16DNT90E Series900 MHz Spread SpectrumWireless TransceiversIntegration Guide
www.Murata.comRF Product Department.Technical support +1.678.684.2000E-mail: tech_sup@murata.comPage 2 of 80DNT90E Integration Guide - 04/13/16Important Regulatory InformationMurata Product FCC ID: HSW-DNT90E IC 4492A-DNT90ENote: This equipment has been tested and found to comply with the limits for a Class Bdigital device, pursuant to Part 15 of the FCC Rules. These limits are designed to providereasonable pro- tection against harmful interference in a residential installation. Thisequipment generates, uses and can radiate radio frequency energy and, if not installed andused in accordance with the in- structions, may cause harmful interference to radiocommunications. If this equipment does cause harmful interference to radio or televisionreception, which can be determined by turning the equipment off and on, the user isencouraged to try to correct the interference by one or more of the following measures:1) Re-orientate or relocate the receiving antenna,2) Increase the separation between the equipment and the radiator,3) Connect the equipment into an outlet on a circuit different from that to which the receiver is connected,4) Consult the dealer or an experienced radio/TV technician for help.Warning: Changes or modifications to this device not expressly approved by MURATA could void the user’s authorityto operate the equipment.FCC Antenna Gain Restriction and MPE Statement:The DNT90E has been designed to operate with any dipole antenna of up to 5 dBi of gain, or any Yagi ofup to 6dBi gain.This equipment complies with FCC radiation exposure limits set forth for an uncontrolled environment. Thisequipment should be installed and operated with minimum distance 21 cm between the radiator and yourbody. This transmitter must not be co-located or operating in conjunction with any other antenna ortransmitter.Cet équipement est conforme aux limites d'exposition aux radiations définies pour un environnement noncontrôlé. Cet équipement doit être installé et utilisé à une distance minimale de 21 cm entre le radiateur etvotre corps. Cet émetteur ne doit pas être situé ou opérant en conjonction avec une autre antenne ouémetteur.Notices:WARNING: This device operates under Part 15 of the FCC rules. Any modification to this device, notexpressly authorized by MURATA, Inc., may void the user’s authority to operate this device.FCC NOTICE: This device complies with Part 15 of the FCC rules. Operation is subject to the following twoconditions: (1) this device may not cause harmful interference, and (2) this device must accept anyinterference received, including interference that may cause undesired operation.
www.Murata.comRF Product Department.Technical support +1.678.684.2000E-mail: tech_sup@murata.comPage 3 of 80DNT90E Integration Guide - 04/13/16Innovation, Science, and Economic Development (ISED) Canada Notice: This device complies with ISEDCanada’s licence-exempt RSSs. 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 ofthe device.Le présent appareil est conforme aux CNR ISED Canada applicables aux appareils radioexempts de licence. L'exploitation est autorisée aux deux conditions suivantes :(1) l'appareil ne doit pas produire de brouillage, et(2) l'utilisateur de l'appareil doit accepter tout brouillage radioélectrique subi, même si le brouillage estsusceptible d'en compromettre le fonctionnement.ISED RSS-247 Detachable Antenna Gain Restriction:This radio transmitter (DNT90E), has been approved by ISED Canada to operate with the antenna typeslisted below with the maximum permissible gain and required antenna impedance for each antenna typeindicated. Antenna types not included in this list, or having a gain greater than the maximum gain indicatedfor that type, are strictly prohibited for use with this device.Le présent émetteur radio (DNT90E ) a été approuvé par ISED Canada pourfonctionner avec les types d'antenne énumérés ci-dessous et ayant un gain admissible maximalet l'impédance requise pour chaque type d'antenne. Les types d'antenne non inclus dans cetteliste, ou dont le gain est supérieur au gain maximal indiqué, sont strictement interdits pourl'exploitation de l'émetteur.Antennas not included in this list or having a gain greater than 6 dB are strictly prohibited for use withthis device. The required antenna impedance is 50 ohms:OMNI095 Omnidirectional Dipole Antenna, 5 dBiYAGI099 Directional Antenna, 6 dBiSee Section 6.8 of this manual for regulatory notices and labeling requirements. Changes or modifica-tions to a DNT90E not expressly approved by MURATA may void the user’s authority to operate themodule.
www.Murata.comRF Product Department.Technical support +1.678.684.2000E-mail: tech_sup@murata.comPage 4 of 80DNT90E Integration Guide - 04/13/16Table of Contents1.1 DNT90E Introduction........................................................................................................................ 61.2 Why Spread Spectrum?............................................................................................................. 61.3 Frequency Hopping versus Direct Sequence ............................................................................ 72.1 DNT90E System Overview............................................................................................................... 82.2 Point-to-Point Systems .............................................................................................................. 82.3 Point-to-Multipoint Systems ....................................................................................................... 92.4 Store-and-Forward Systems...................................................................................................... 92.5 RF Channel Access ................................................................................................................. 102.6 DNT90E Addressing ................................................................................................................ 112.7 Network Linking and Slot Registration ..................................................................................... 112.6.1 Fast Linking Techniques ................................................................................................... 122.7 Transparent and Protocol-formatted Serial Data ..................................................................... 123.1 DNT90E Application Interfaces ...................................................................................................... 133.2 Serial Ports .............................................................................................................................. 133.3 SPI Port.................................................................................................................................... 133.4 Digital I/O ................................................................................................................................. 163.5 Analog I/O................................................................................................................................ 163.6 I/O Event Reporting and I/O Binding........................................................................................ 174.1 DNT90E System Configuration ...................................................................................................... 184.2 Configuration Parameters........................................................................................................ 184.3 Configuring a Basic Point-to-Point System .............................................................................. 184.4 Configuring a Basic Point-to-Multipoint System....................................................................... 184.5 Configuring a Customized Point-to-Point or Point-to-Multipoint System.................................. 194.6 Configuring a Store-and-Forward System................................................................................ 204.7 Slot Buffer Sizes, Number of Slots, Messages per Hop and Hop Duration ............................. 215.1 DNT90E Application Interface Configuration. .....................................................................................235.2 Configuring the Serial Port....................................................................................................... 235.3 Configuring the SPI Port .......................................................................................................... 245.4 Configuring Digital I/O.............................................................................................................. 245.5 Configuring Analog I/O............................................................................................................. 245.6 Configuring I/O Event Reporting and I/O Binding .................................................................... 255.7 Configuring Sleep Mode .......................................................................................................... 266.1 DNT90E Hardware......................................................................................................................... 276.2 Electrical Specifications ........................................................................................................... 286.3 Module Pin Out ........................................................................................................................ 296.4 Antenna Connector.................................................................................................................. 306.5 Power Supply and Input Voltages............................................................................................ 316.6 ESD and Transient Protection ......................................................................................................316.7 Interfacing to 5 V Logic Systems ............................................................................................. 316.8 Mounting and Enclosures ........................................................................................................ 316.9 Labeling and Notices ............................................................................................................... 327.1 DNT90E Protocol-formatted Messages.......................................................................................... 337.2 Protocol Formats...................................................................................................................... 337.3 Message Types........................................................................................................................ 337.4 Message Format Details.......................................................................................................... 34
www.Murata.comRF Product Department.Technical support +1.678.684.2000E-mail: tech_sup@murata.comPage 5 of 80DNT90E Integration Guide - 04/13/167.5 Configuration Parameter Registers.......................................................................................... 417.5.1 Bank 0x00 - Transceiver Setup......................................................................................... 417.5.2 Bank 0x01 - System Settings ............................................................................................ 447.5.3 Bank 0x02 - Status Parameters ........................................................................................ 457.5.4 Bank 0x03 - Serial and SPI Settings ................................................................................. 477.5.5 Bank 0x04 - Host Protocol Settings................................................................................... 487.5.6 Bank 0x05 - I/O Parameters.............................................................................................. 497.5.7 Bank 0x06 - I/O Settings ................................................................................................... 507.5.8 Bank 0x0FF - Special Functions........................................................................................ 557.5 Protocol-formatted Message Examples................................................................................... 567.5.1 Data Message ................................................................................................................... 567.5.2 Configuration Message ..................................................................................................... 577.5.3 Sensor Message ............................................................................................................... 577.5.4 Event Message.................................................................................................................. 588.1 DNT90EDK Developer’s Kit............................................................................................................ 598.2 DNT90EDK Kit Contents.......................................................................................................... 598.3 Additional Items Needed.......................................................................................................... 598.4 Developer’s Kit Default Operating Configuration...................................................................... 598.5 Developer’s Kit Hardware Assembly........................................................................................ 608.6 DNT90E Utility Program........................................................................................................... 618.7 Initial Kit Operation................................................................................................................... 628.6.1 Serial Communication and Radio Configuration................................................................ 658.7 DNT90E Interface Board Features .......................................................................................... 719.1 Troubleshooting.............................................................................................................................. 739.2 Diagnostic Port Commands ..................................................................................................... 7310.1 Appendices..................................................................................................................................... 7410.2 Ordering Information................................................................................................................ 7410.3 Technical Support.................................................................................................................... 7410.4 DNT90E Mechanical Specifications......................................................................................... 7510.5 DNT90E Development Board Schematic................................................................................. 7711.0Warranty......................................................................................................................................... 80
www.Murata.comRF Product Department.Technical support +1.678.684.2000E-mail: tech_sup@murata.comPage 6 of 80DNT90E Integration Guide - 04/13/161.1DNT90E IntroductionDNT90E transceivers provide highly-reliable wireless connectivity for point-to-point, point-to-multipoint andstore-and-forward radio applications. Frequency hopping spread spectrum (FHSS) technology ensuresmaximum resistance to multipath fading and robustness in the presence of interfering signals, while oper-ation in the 900 MHz ISM band allows license-free use in North America, South America and Australia.The DNT90E supports serial data rates for host communications from 1.2 to 250 kbps, plus three SPIdata rates from 125 to 500 kbps. On-board data buffering plus an error-correcting radio protocol providesmooth data flow and simplify the task of integration with existing applications. Key DNT90E features in-clude:Multipath fading resistant frequency hoppingtechnology with up to 52 frequency chan-nels, 902.76 to 927.24 MHzReceiver protected by low-loss SAW filter,providing excellent receiver sensitivity andinterference rejection important in outdoorapplicationsSupport for point-to-point, point-to-multipoint,peer-to-peer and store & forward networksFCC 15.247 and ISED RSS-247 certifiedfor license-free operationFive mile plus range with omnidirectionalantennas (antenna height dependent)Transparent ARQ protocol with databuffering ensures data integrityAnalog and Digital I/O supports wirelesssensing applicationsAd Hoc TDMA operating mode supports alarge number of remotes with low latencyfor burst data streamingSimple interface handles both data and con-trol at up to 250 kbps on the serial port or500 kbps on the SPI portAES encryption provides protection fromeavesdroppingNonvolatile memory stores DNT90Econfigura- tion when powered offSelectable +16 dBm (40 mW) or +25 dBm(316 mW) transmit power levelsAutomatic I/O event reporting mode simplifiesapplication developmentI/O binding mode provides wireless transmis-sion of analog and digital values1.1 Why Spread Spectrum?A radio channel can be very hostile, corrupted by noise, path loss and interfering transmissions from oth-er radios. Even in an interference-free environment, radio performance faces serious degradation from aphenomenon known as multipath fading. Multipath fading results when two or more reflected rays of thetransmitted signal arrive at the receiving antenna with opposing phases, thereby partially or completelycanceling the signal. This problem is particularly prevalent in indoor installations. In the frequency do-main, a multipath fade can be described as a frequency-selective notch that shifts in location and intensityover time as reflections change due to motion of the radio or objects within its range. At any given time,multipath fades will typically occupy 1% - 2% of the band. From a probabilistic viewpoint, a conventionalradio system faces a 1% - 2% chance of signal impairment at any given time due to multipath fading.Spread spectrum reduces the vulnerability of a radio system to both multipath fading and jammers by dis-tributing the transmitted signal over a larger region of the frequency band than would otherwise be neces-sary to send the information. This allows the signal to be reconstructed even though part of it may be lostor corrupted in transmission.
www.Murata.comRF Product Department.Technical support +1.678.684.2000E-mail: tech_sup@murata.comPage 7 of 80DNT90E Integration Guide - 04/13/16Narrow-band versus spread spectrum transmissionFigure 1.1.11.2 Frequency Hopping versus Direct SequenceThe two primary approaches to spread spectrum are direct sequence spread spectrum (DSSS) and fre-quency hopping spread spectrum (FHSS), either of which can generally be adapted to a given applica-tion. Direct sequence spread spectrum is produced by multiplying the transmitted data stream by a muchfaster, noise-like repeating pattern. The ratio by which this modulating pattern exceeds the bit rate of thebase-band data is called the processing gain, and is equal to the amount of rejection the system affordsagainst narrow-band interference from multipath and jammers. Transmitting the data signal as usual, butvarying the carrier frequency rapidly according to a pseudo-random pattern over a broad range of chan-nels produces a frequency hopping spectrum system.Forms of spread spectrum - direct sequence and frequency hoppingFigure 1.1.2
www.Murata.comRF Product Department.Technical support +1.678.684.2000E-mail: tech_sup@murata.comPage 8 of 80DNT90E Integration Guide - 04/13/16One disadvantage of direct sequence systems is that due to design issues related to broadband transmit-ters and receivers, they generally employ only a minimal amount of spreading, often no more than theminimum required by the regulating agencies. For this reason, the ability of DSSS systems to overcomefading and in-band jammers is relatively weak. By contrast, FHSS systems are capable of hoppingthroughout the entire band, statistically reducing the chances that a transmission will be affected by fad-ing or interference. This means that a FHSS system will degrade gracefully as the band gets noisier,while a DSSS system may exhibit uneven coverage or work well until a certain point and then give outcompletely.Because it offers greater immunity to interfering signals, FHSS is often the preferred choice for co-locatedsystems. Since direct sequence signals are very wide, they can offer only a few non-overlapping chan-nels, whereas multiple hoppers can interleave, minimizing interference. Frequency hopping systems docarry some disadvantages, in that they require an initial acquisition period during which the receiver mustlock on to the moving carrier of the transmitter before any data can be sent, which typically takes severalseconds. In summary, frequency hopping systems generally feature greater coverage and channel utiliza-tion than comparable direct sequence systems. Of course, other implementation factors such as size,cost, power consumption and ease of implementation must also be considered before a final radio designchoice can be made.2.0 DNT90E System OverviewA DNT90E radio can be configured to operate in one of three modes - base, remote or router. A basecon- trols a DNT90E system, and interfaces to an application host such as a PC or Internet gateway. Aremote functions to transmit or receive serial, digital (state) and analog data. A router alternates betweenfunc- tioning as a remote on one hop and a network base on the next hop. When acting as a remote, therouter stores messages it receives from its parent, and then repeats the messages to its child radioswhen act- ing as a network base. Likewise, a router will store messages received from its child radioswhen acting as a base, and repeat them to its parent when acting as a remote. Any message addresseddirectly to a router is processed by the router rather than being repeated.2.1 Point-to-Point SystemsA DNT90E system contains at least one network. The simplest DNT90E topology is a point-to-pointsystem, as shown in Figure 2.1.1. This system consists of a base and one remote forming a singlenetwork. Point- to-point systems are often used to replace wired serial connections. Point-to-pointsystems are also used to transmit switch positions or analog signals from one location to another.Figure 2.1.1
www.Murata.comRF Product Department.Technical support +1.678.684.2000E-mail: tech_sup@murata.comPage 9 of 80DNT90E Integration Guide - 04/13/162.2 Point-to-Multipoint SystemsFigure 2.2.1 shows the topology of a point-to-multipoint (star) system, which consists of a base and morethan one remote in a single network. Point-to-multipoint systems are typically used for data, sensor andalarm systems. While most traffic in a point-to-multipoint system is between the base and the remotes,DNT90E technology also allows for peer-to-peer communication from one remote to another.Figure 2.2.12.3 Store-and-Forward SystemsFigure 2.3.1 shows the topology of a store-and-forward system, which consists of a base, one or morerouters, one or more remotes, and two or more networks. Networks in a store-and-forward system formaround the base and each router. The base and the routers are referred to as the parents of the networksthey form. The rest of the radios in each network are referred to as child radios. Note that a router is achild of the base or another router while being the parent of its own network. Each network parent trans-mits beacons to allow child radios to synchronize with its hopping pattern and join its network. Differentfrequency hopping patterns are used by the parent radios in a system, minimizing interference betweennetworks.Store-and-forward systems are used to cover larger areas than is possible with point-to-point or point to-multipoint systems. The trade-off in store-and-forward systems is longer delivery times due to receivingand retransmitting a message several times. Store-and-forward systems are especially useful in applica-tions such as agriculture where data is only collected periodically.
www.MURATA.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@Murata.comPage 10 of 80DNT90 Integration Guide - 08/09/12S y s t e m / N e t w o r kM e s s ag e s t oC o n t r o l N e tw o r k C h i l d r e nM e ss a g esf r o mC h i l dOAO2.4 RF Channel AccessFigure 2.3.1The time a DNT90E network stays on each frequency in its hopping pattern is called the hop duration ordwell time, which can be configured from 8 to 100 ms. Radio communication during each dwell is orga-nized as a time division multiple access (TDMA) frame. A DNT90E frame begins with a base-modebeacon, followed by 1 to 8 time slots used by the network children to transmit to their parent, as shown inFigure2.4.1. A base-mode beacon can include up to 8 messages addressed to one or more child radios. Thenumber of slots is chosen accommodate the number of children that need to send messages each hop.E x a m p l e D N T 9 0 C o m m u n i c a t i o n Fr a m eB a s e -M o d epens s i g n e dp e nB e a co nSl otS l otS lo tFigure 2.4.1Each beacon includes the status of all slots - either registered (assigned) or open. When a child radio hasinformation to transmit to its parent, it randomly selects one of the open slots and transmits all or the firstpart of its data. If the parent successfully receives the transmission, it includes the child’s MAC address inthe next beacon. This signals the child radio that the slot is temporarily registered to it, allowing the childto efficiently stream any remaining data to the base hop-by-hop until it is all sent.If a child radio does not see its address in the next beacon following its transmission, it again randomlyselects an open slot and retransmits its data. During times when there are no open slots, a child radio
www.MURATA.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@Murata.comPage 11 of 80DNT90 Integration Guide - 08/09/12keeps its data queued and continues to look for an open slot in each beacon until at least one slot be-comes available. The access method the DNT90E uses is referred to as Ad Hoc TDMA.2.5 DNT90E AddressingEach DNT90E has a unique MAC address. The MAC address can be read or bar-code scanned fromthe label on top of each radio. A DNT90E radio in any mode (base/router/remote) can be addressedusing its MAC address. A DNT90E base can be addressed using either its MAC address or address0x000000. A DNT90E can send a message to all other DNT90E’s in its system by using the broadcastaddress 0xFFFFFF.The base and all routers (parents) hold base-mode network IDs, which are transmitted in every beacon.All routers and remotes hold parent network IDs and optionally alternate parent network IDs to compareagainst the base-mode network IDs in the beacons they receive. A child router or remote is allowed tojoin a parent if its parent network ID or alternate parent network ID matches the parent’s base-mode net-work ID, or with any parent when its parent network ID is set to 0xFF (wildcard).In a point-to-point or point-to-multipoint system, the default base-mode network ID of 0xFF (wildcard) canbe used. In a store-and-forward system, however, the base-mode network IDs of all routers must be setto different values between 0x00 to 0x3F. If the base-mode network ID of 0x00 is assigned to a router, thebase must be assigned an unused base-mode network ID between 0x01 and 0x3F. Leaving all parentnetwork IDs in a store-and-forward system set to the default value of 0xFF allows networks to automati-cally form, and self-repair if a parent router fails. Enabling the alternate parent network ID also providesself-repairing message routing.All DNT90E radios hold a system ID that can be used to distinguish systems that physically overlap. In aDNT90E system, the system ID must be different from those used by overlapping systems to providemes- sage filtering. Also, using different base-mode network IDs for all networks in overlapping systemshelps reduce hopping pattern collisions.The store-and-forward path between the base and any other radio in a system can be determined byreading the radio’s ParentMacAddress parameter. If this address is not the base, then reading theParentMacAddress parameter of its parent, grandparent, etc., in succession reveals the complete path tothe base. Path determination is useful in optimizing and troubleshooting systems during commissioningand maintenance.2.6 Network Linking and Slot RegistrationWhen first turned on, a DNT90E router or remote rapidly scans all frequency channels in its operatingband to acquire synchronization and link to a parent based on a system ID match plus a base-modenetwork ID to parent network ID/alternate parent network ID match (or by using a wildcard (0xFF) parentnetwork ID).In addition to the slot status and the MAC addresses of child radios holding slot registrations, each base-mode beacon includes one of a number of cycled control parameters. The cycled parameters are collect-ed by child radios, allowing them to register with a parent, and to later follow any control parameterchanges. When a router or remote has collected a full set of cycled parameters, it can issue an optionalinitial heartbeat message and then optional periodic heartbeat messages which allow an application tomaintain the status of all routers and remotes in its DNT90E system.
www.MURATA.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@Murata.comPage 12 of 80DNT90 Integration Guide - 08/09/12When a router/remote has data to send to its parent, it picks an open slot at random and transmits. It thenlooks for its MAC address in the next beacon. If its MAC address is present in the beacon, it is temporarilyregistered to the slot and continues to use it until all current data is sent, or its MAC address drops off thebeacon.2.6.1 Fast Linking TechniquesMinimizing linking time is important in certain applications. For example, when the remotes in a systemare battery powered and wake from sleep occasionally to report data. Minimizing linking time increasesthe operating battery life of the remotes. The basic techniques to reduce linking time include:- use no more hop duration (dwell time) than necessary- use no more slots than necessary for the application- use no larger base slot size (BSS) than necessary- transmit only dynamic cycle parameters once system nodes have static parametersOnce a complete set of cycled parameters has been receive by all routers and remotes in a system andstored in memory, it is not necessary to send all of them again during a re-linking, as long as the systemconfiguration remains stable.As discussed in Section 7.4.1, the base station in a DNT90E system can be configured to transmit “fastbeacons” for a period of time when powered up, reset or triggered with the FastBeaconTrig parameter.Fast beacons are sent using a very short hop dwell time, facilitating fast system linking.2.7 Transparent and Protocol-formatted Serial DataA DNT90E remote can directly input and output data bytes and data strings on its serial port. This is re-ferred to as transparent serial port operation. In a point-to-point system, the base can also be configuredfor transparent serial port operation.In all other cases, serial data must be protocol formatted:- configuration commands and replies- I/O event messages- announcement messages including heartbeatsProtocol-formatted messages are discussed in detail in Section 7. Briefly, protocol-formatted messagesinclude a start-of-messages character, message length and message type information, the destinationaddress of the message, and the message payload.Transparent data is routed using a remote transparent destination address. In a remote, this address de-faults to the base, 0x000000, and in the base this address defaults to broadcast, 0xFFFFFF. These de-faults can be overridden with specific radio addresses. For example, it is possible to set up transparentpeer-to-peer routing between two remotes in a point-to-multipoint or store-and-forward system by loadingspecific MAC addresses in each radio’s remote transparent destination address.
www.MURATA.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@Murata.comPage 13 of 80DNT90 Integration Guide - 08/09/123.0 DNT90E Application InterfacesA DNT90E module provides a variety of application interfaces including two serial ports, an SPI port, sixdigital I/O ports (logic state), three 12-bit ADC input ports, and two 12-bit DAC output ports. Each of theseinterfaces is discussed below.3.1 Serial PortsThe DNT90E includes two serial ports, one for communication and an optional one for diagnostics. Thecommunication port is a full-duplex UART interface with hardware flow control on two of the digital I/Opins an optional feature. One digital I/O pin can also be configured as an RS485 enable function. The se-rial communication port can be configured with baud rates from 1.2 to 250 kbps, with 9.6 kbps the defaultbaud rate. The DNT90E communication port transmits/receives 8-bit data with a choice of even, odd or noparity and 1 or 2 stop bits. The default configuration is no parity and one stop bit. See Section 5.1 for rec-ommendations on configuring the communication port, and Section 7.4.4 for detailed information on con-figuration parameters. The diagnostic port is enabled as an alternate function on two digital I/O pins, andcan be configured with baud rates from 1.2 to 250 kbps, with 9.6 kbps the default baud rate. The diagnos-tic port transmits/receives 8-bit data with no parity and 1 stop bit. See Section 7.4.8 for diagnostic portconfiguration details.3.2 SPI PortThe DNT90E serial peripheral interface (SPI) port can operate either as a master or a slave. The portincludes the four standard SPI connections - MISO, MOSI, SCLK and /SS, plus three signals used tosupport SPI slave mode operation - /HOST_RTS, /HOST_CTS and DAV. The serial port and SPI mastermode can run simultaneously. Serial port operation is disabled when the SPI port is configured for slavemode. Note that all SPI slave mode messages must be protocol formatted.D N T 9 0 S P I M a s t e r M o d e S i g n a l i ngFigure 3.2.1The DNT90E SPI port can run at three clock rates in master mode - 125, 250 or 500 kbps. There are twomessage sources available to a DNT90E SPI master, a protocol-formatted RxData message or a storedcommand. The DNT90E master will clock a message from either source into its slave and return the bytesclocked out as a protocol-formatted TxData message. The DNT90E event timer triggers sending thestored command to the DNT90E’s slave. The stored command can be up to 16 bytes in length. FigureP e r i p he r a lD N T 90M O S IS C L K/ S SMI SO
www.MURATA.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@Murata.comPage 14 of 80DNT90 Integration Guide - 08/09/123.2.1
www.MURATA.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@Murata.comPage 15 of 80DNT90 Integration Guide - 08/09/12shows the required SPI master mode-signal connections, and Figure 3.2.2 shows the SPI master-modetiming.D N T 9 0 S P I M a s t e r M o d e O p e r a t i o n/ S SS C L KM O S IM I S OFigure 3.2.2In SPI slave mode, the host can stream data into DNT90E at up to 250 kbps, provided the host suspendsclocking within 10 bytes following a low-to-high transition on /HOST_CTS. The host can clock data intothe DNT90E at up to 4 Mbps for data bursts of up to 50 bytes, provided the interval from the end of oneburst to the start of the next burst is at least 2 ms, and the host suspends clocking on a low-to-high transi-tion on /HOST_CTS. See Figure 3.2.4D N T 9 0 S P I S l a v e M o d e S i g n a l i ngH o s tMISOD N T9 0MOS ISCLK/ S S/ HOSTRTS/ HOSTCTSDA VFigure 3.2.3
www.MURATA.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@Murata.comPage 16 of 80DNT90 Integration Guide - 08/09/12D N T 9 0 S P I S l a v e M o d e M e s s a g e L o a d/ S S/ H O S T C T SS C L KM O S IFigure 3.2.4The host should use the following steps to fetch data from a DNT90E SPI slave, as show in Figure 3.2.5:1. The host sets the /HOST_RTS signal high to allow the DNT90E to signal data available.2. The DNT90E sets the data available (DAV) high to signal the host it has data.3. The host set the /SS signal low to enable SPI operation.4. The host clocks in one dummy byte (ignore the output byte) and then sets /HOST_RTS low.5. The host begins to clock out the data, which can include several messages.6. The host continues to clock out data until a 0x00 byte occurs in the byte stream where a 0xFBstart-of-message would be expected.7. The host has now clocked out all messages and the 0x00 is discarded.8. The host sets /HOST_RTS and /SS high to allow the DNT90E to signal DAV the next timeit has data.Note that the DAV signal can go low before the last message is clocked out. It is not a reliable indicationthat the last byte of the message(s) has been clocked out. See Section 5.2 for recommendations on con-figuring the SPI port, and Section 7.4.4 for detailed information on SPI port configuration parameters.D N T 9 0 S P I S l a v e M o d e R X M e s s a g e R e t r i e v a lD A V/ S S/ H O S T R T SS C L KM I S OFigure 3.2.5S P I B i t C l o c kM e s s a g e t o D NT 9 0S P I C l o c kP r o t o c o l F o r m a t t e d R X M e ss a g eL e n g t h B y t e0 x F B S t a r t o f M e s s a g e
www.MURATA.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@Murata.comPage 17 of 80DNT90 Integration Guide - 08/09/123.3 Digital I/OThe DNT90E’s six digital (state) I/O ports are labeled GPIO0 through GPIO5. GPIO5 has an alternatefunc- tion of /HOST_ RTS and GPIO4 of /HOST_CTS, providing hardware handshaking for the serialport and SPI slave mode operation. If serial port hardware handshaking is not required and SPI slavemode is not enabled, GPIO4 and GPIO5 can be used for other digital I/O functions. When SPI slavemode is enabled, GPIO5 and GPIO4 must be used for /HOST_RTS and /HOST_CTS respectively, andGPIO3 must be used to provide the DAV signal (SPI slave mode overrides any other configuration forthese ports). Ex- cept in SPI slave mode, GPIO0 through GPIO5 are available for customer-definedfunctions:- The direction of each GPIO pin can be set for both active and sleep modes.- The initial state (power on) of all GPIO pins configured as outputs can be set.- The state of all GPIO pins configured as outputs in sleep mode can be set.- GPIO triggering of I/O event reporting can be configured.- GPIO level control of sleep hold-off can be configured.See Section 5.3 for recommendations on configuring the digital I/O, and Sections 7.4.6 and 7.4.7 for de-tailed information on GPIO parameters.3.4 Analog I/OThe DNT90E’s three ADC input channels are labeled ADC0 through ADC2. The ADC can be disabled ifunused to reduce current consumption. The ADC can be operated in either single-ended mode or differ-ential mode. In single-ended mode, up to three sensor inputs can be measured. The negative sensor in-puts are connected to ground and the positive sensor inputs are connected to ADC0, ADC1 and ADC2respectively. Single-ended measurements are unsigned 11-bit values. In differential mode, one or twosensor inputs can be measured as 12-bit signed values. The first differential measurement is the differ-ence between the voltage on ADC1 and the voltage on ADC0, and is referred to as the ADC0 differentialmeasurement. The second differential measurement is the difference between ADC2 and ADC0, and isreferred to as the ADC1 differential measurement. Operating the ADC in differential mode takes ad-vantage of common mode rejection to provide the best measurement stability. Differential mode also in-corporates a programmable gain preamplifier function, with gains settings from 1 to 64 available.There are two options for the ADC full-scale reference:1. The DNT90E regulated supply voltage divided by 1.6, or about 2.06 V2. A low impedance voltage source applied to the DNT90E’s ADC_EXT_REF input pin, 2.7 Vmaxi- mum. If no connection is made to this pin, a voltage equal to about 2.7 V will be present.Note that when differential ADC mode is used, the maximum output voltage available from the preamplifi-er at any gain setting is 2.4 V, so the maximum ADC reading that can be made using a 2.7 V ADC refer-ence will be about 88.9% of full scale. The ADC channels are read each ADC sample interval, which isconfigurable. High and low measurement thresholds can be set for each ADC channel to trigger I/O eventreporting messages.
www.MURATA.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@Murata.comPage 18 of 80DNT90 Integration Guide - 08/09/12The DNT90E’s two DAC outputs are labeled DAC0 and DAC1. The DACs can be disabled if unused tore- duce current consumption. The DAC settings have 12-bit resolution. There are two options for theDAC full-scale reference:1. The DNT90E regulated supply voltage, about 3.3 V2. A low impedance voltage source applied to the DNT90E’s ADC_EXT_REF input pin, 2.7 Vmaxi- mum. If no connection is made to this pin, a voltage equal to about 2.7 V will be present.See Section 5.4 for recommendations on configuring the analog I/O, and Sections 7.4.6 and 7.4.7 for de-tailed information on analog I/O parameters.3.5 I/O Event Reporting and I/O BindingThe DNT90E’s I/O event reporting function can generate a protocol-formatted RxEvent message whentriggered by one of the following I/O events:- A specific state change of GPIO0, GPIO1, GPIO2 or GPIO3.- Firing of the periodic event report timer.- A high or low threshold exceeded on a measurement by ADC0, ADC1 or ADC2.An I/O report message includes:- The states of GPIO0 through GPIO5.- The latest measurements made by ADC0 through ADC2.- A set of flags indicating which event(s) triggered the I/O report.- The settings of DAC0 and DAC1.The I/O binding function works in conjunction with I/O event reporting. When I/O binding is enabled on aDNT90E, data received in an I/O event report it is mapped as follows:- GPIO2 will output the state of GPIO0 in the last received event report.- GPIO3 will output the state of GPIO1 in the last received event report.- DAC0 will output the voltage read by ADC0 in the last received event report.- DAC1 will output the voltage read by ADC1 in the last received event report.I/O binding is used to transmit switch positions or analog signals from one location to another. Note thatI/O binding cannot be used in a DNT90E when SPI slave mode is enabled or differential ADC mode isused. See Section 5.4 for recommendations on configuring I/O event reporting and binding, and Sections7.4.6 and 7.4.7 for detailed information on I/O reporting and binding parameters.
www.MURATA.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@Murata.comPage 19 of 80DNT90 Integration Guide - 08/09/124.0 DNT90E System ConfigurationDNT90E radios feature an extensive set of configuration options that allows them to be adapted to a widerange of applications. Configuration defaults have been carefully selected to minimize the configurationeffort for most applications, while providing the ability to individually adjust the configuration of each radioto achieve highly optimized system operation.4.1 Configuration ParametersThe configuration of a DNT90E is controlled by a set of parameters (registers). Parameters that address aparticular aspect of operation are grouped into a bank. All parameters can be accessed through a mod-ule’s serial port and over the radio link. Most parameters are read/write. Read-only parameters includefixed values such a MAC addresses, firmware version numbers and parameters that are dynamically ad-justed during system operation such as link status. Write-only parameters include security keys and cer-tain action triggers such as reset. Incorrectly configuring certain parameters can disable a module’s radiolink, but the configuration can always be corrected through the serial port. The organization of the param-eter register banks and the details of each parameter are covered in Section 7.4 of this guide. Sections4.2 through 5.7 discuss which parameters apply to various aspects of configuring a DNT90E system, net-work or application interface.4.2 Configuring a Basic Point-to-Point SystemA basic DNT90E point-to-point system is suitable for many serial data applications. The defaultconfig- uration of a DNT90E is a remote with the serial port configured for transparent operation at 9.6kbps, 8N1. To configure a basic point-to-point system:1. Configure one of the modules as a base by setting the DeviceMode parameter in Bank 0 to 0x01.2. Set the MemorySave parameter in Bank 0xFF to 0xD2, which will save the DeviceMode parame-ter to EEPROM and reset the module, enabling base operation.3. All other parameters may be left at their default values.4.3 Configuring a Basic Point-to-Multipoint Point SystemA basic DNT90E point-to-multipoint point systems is suitable for many serial data applications wheremultiple remotes are used. The default configuration of a DNT90E is a remote with the serial port con-figured for transparent operation at 9.6 kbps, 8N1. To configure a basic point-to-multipoint system:1. Configure one of the modules as a base by setting the DeviceMode parameter in Bank 0 to 0x01.2. If the host application driving the base will individually communicate each remote, set the Proto-colMode parameter in Bank 4 of the base to 0x01. This step is not required if messages from thebase to the remotes will always be broadcast and/or the base does not need to know the MACaddress of the remote sending a message.3. Set the MemorySave parameter in Bank 0xFF to 0xD2, which will save the DeviceMode parame-ter to EEPROM and reset the module, enabling base operation.4. All other parameters may be left at their default values.
www.MURATA.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@Murata.comPage 20 of 80DNT90 Integration Guide - 08/09/125. If the host application driving the base will individually communicate each remote, read or scanthe MAC addresses from the label on top of each remote and load the addresses in the host ap-plication data base.4.4 Configuring a Customized Point-to-Point or Point-to-Multipoint SystemThe DNT90E includes many configuration parameters that allow extensive customization of a point-to-point or point-to-multipoint system. Most applications will require only a few of these parameters bechanged from their default values. But for those applications that need them, MURATA recommends thefollowing con- figuration sequence. Skip the configuration steps where the default parameter value issatisfactory.1. Configure one of the modules as a base by setting the DeviceMode parameter in Bank 0 to 0x01.2. Set the optional AES security key in all system radios by loading your selected 16-byte string intothe SecurityKey parameter in Bank 0 (the default is 16 bytes of 0x00).3. Select the frequency band of operation by setting the FrequencyBand parameter in Bank 1 of thebase radio as desired (the default is Band 0).4. Set the transmitter power level as needed in all radios by setting the TxPower parameter inBank 0 (the default is 158 mW).5. Configure the system ID in all radios by setting the SystemID parameter in Bank 0 (the default isOK if there is no chance of overlapping systems).6. Load the parent network ID in all remotes in the ParentNetworkID parameter in Bank 0 as needed(wildcard default is OK for point-to-point and point-to-multipoint systems).7. Set the BaseModeNetID parameter in the base to match the ParentNetworkID parameter in theremotes if the default BaseModeNetID is not used in the base and the wildcard default Parent-NetworkID is not used in the remotes.8. For a point-to-multipoint system where DNT90E MAC addressing will be used, set the Proto-colMode parameter in Bank 4 of the base to 0x01. Set the protocol mode as needed in the baseand remote of a point-to-point system, and as needed in the remotes in a point-to-multipoint sys-tem. If SPI slave mode will be used, protocol mode must be enabled in all system radios. Notethat if the application data includes addressing information for individual remote hosts, theDNT90E broadcast mode can be used instead of the DNT90E protocol mode.9. If using transparent serial mode in the system:a. Set the remote transparent destination address in the RmtTransDestAddr parameter,Bank 0, in each remote if the destination is not the base (the base address is the defaultdestination).b. Set the transparent point-to-point mode to select either the RmtTransDestAddr address(default) or the address of the originator of the last received message as the remote des-tination address. The parameter that controls this destination address is the Trans-PtToPtMode in Bank 4. Set in all remotes as needed.c. Set the timeout for transmission of transparent data in the remotes as needed. The pa-rameter that controls the timeout is the TxTimeout in Bank 4 (the default is no timeout).
www.MURATA.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@Murata.comPage 20 of 80DNT90 Integration Guide - 08/09/12d. Set the minimum message length for transmission of transparent data in the remotes asneeded. The parameter that controls the length is the MinPacketLength in Bank 4 (thedefault is one byte).10. Refer to Section 4.6 below which discusses how to coordinate the values of the following fourparameters:a. Set the maximum number of messages that can be sent in a hop on each system radio.The parameter that controls this number is MsgsPerHop in Bank 4. The default is 8 mes-sages.b. Load the required base slot size into the BaseSlotSize parameter, Bank 1, in the base.The default is 40 bytes.c. Configure the number of child slots per hop on the base by setting the NumSlots parame-ter. The default is 3 slots.d. Set the required hop duration on the base. The HopDuration parameter in Bank 0 con-trols hop duration. The default is 20 ms.11. Configure the slot lease on the base by setting the SlotLease parameter. The default is 4 hops.12. Set the heartbeat interval as required in each system radio. The parameter that controls heart-beats is the HeartBeatIntrvl in Bank 0. The default is 20 seconds/heartbeat.13. Enable end-to-end message ACKs where required by setting the EndToEndAckEnable parameterin Bank 0 to 1. Enabling this parameter provides a confirmation that a message has reached itsdestination in peer-to-peer or store-and-forward routing. The default is disabled.14. Set the message retry limit on the base with the ArqAttemptLimit parameter in Bank 1. The de-fault value is 6 retries.15. Set the link drop threshold on the base by setting the LinkDropThreshold in Bank 1. This parame-ter sets the number of sequential hops without receiving a beacon that will trigger a child to re-synchronize and re-link to its parent. The default is 10 hops.16. Set the point-to-point reply timeout on the base in the P2PReplyTimeout parameter in Bank 1.The default is 16 hops. See Section 7.4.2 for parameter details.17. Configure the registration timeout on the base by setting the RegistryTimeout parameter inBank 1. The default timeout is 50 hops. See Section 7.4.2 for a discussion of this parameter.18. Load an optional “friendly description” in each system radio in the UserTag parameter, Bank 0.4.5 Configuring a Store-and-Forward SystemThe following additional parameters must be set to configure a DNT90E store-and-forward system:1. Configure the DNT90E radios designated to be routers by setting the DeviceModeparameter in Bank 0 to 0x02.2. Enable store-and-forward operation on all system radios by setting the Store&ForwardEnparameter in Bank 0 to 0x01.
www.MURATA.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@Murata.comPage 21 of 80DNT90 Integration Guide - 08/09/123. In each router, load a unique base-mode network ID into the BaseModeNetID parameter in Bank0, and into the base if a router is set to 0x00.4. To configure a specific system topology, set the parent network ID parameter, ParentNwkID, andoptionally the alternate parent network ID parameter, AltParentNwkID, in all routers and remotes.Note that a store-and-forward system topology can be formed either automatically ormanually, based on the settings of the ParentNetworkID and optionally the AltParentNwkIDparameters:- Setting the ParentNwkID parameter to 0xFF in all routers and remotes allows eachrouter and remote to automatically link to a parent, causing the system to formautomatically (child routers picking each other as a parent cannot occur). In this case, theAltParent-NwkID parameter should be set to 0xFF, which disables it.- Setting the ParentNwkID and optionally the AltParentNwkID parameters to specific val-ues in each router and remote allows full manual control of the network topology.The benefit of automatic system formation is self-healing. If a parent router fails, its child nodescan re-link to any other parent router they can receive. However, automatic topology formationcan result in an unnecessary number of hops between routers or remotes and the base.The benefit of manual system topology formation is to avoid unnecessary extra hops in the sys-tem, and to balance the number of children supported by each parent router. If a parent routerfails and an active alternate parent network ID has not been assigned, all children downstreamfrom the failure will be off the system until the failed router is repaired or replaced.4.6 Slot Buffer Sizes, Number of Slots, Messages per Hop and Hop DurationThe base slot size (BSS) sets the maximum number of payload bytes the base can transmit during a sin-gle hop when the base is sending one message per hop. The maximum BSS is 105 bytes when aDNT90E system is configured for one slot. Adding additional slots reduces the maximum BSS by threebytes per slot.The BSS buffer is set nine bytes larger than the BSS, to a maximum of 114 bytes.Thebase can po- tentially send more than one message per beacon, up to the limit set by its MsgsPerHopparameter value. Each message in the BSS buffer occupies nine header bytes plus the payload.For example, the base can send three messages per hop when the BSS is 90 bytes, provided the totalpayload bytes in the three messages is 72 bytes or less:slot size = 90buffer= 90 + 9 = 993 headers = 3*9 = 27net for payload = 99 - 27 = 72The BSS must be large enough to accommodate any protocol-formatted message that may be sent overthe wireless link, as each protocol-formatted message must be sent in a single transmission.The remote slot size (RSS) is the maximum number of payload bytes a child can transmit during a singlehop when it is sending one message per hop. The RSS is the same for all slots. The maximum RSS is109 bytes. The RSS buffer is set nine bytes larger than the RSS, to a maximum of 118 bytes.A child canpotentially send more than one message in a slot, up to the limit set by its MsgsPerHop parameter value.Each message in the transmit buffer occupies nine header bytes plus the payload. For example, a child
www.MURATA.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@Murata.comPage 22 of 80DNT90 Integration Guide - 08/09/12can send two messages per hop when the RSS is 73 bytes, provided the total payload in the two mes-sages is 64 bytes or less:slot size = 73buffer= 73 + 9 = 822 headers = 2*9 = 18net for payload = 82 - 18 = 64Note that the RSS is calculated by all DNT90Es in a system, rather than being a user configured parame-ter. The slot size depends on the current values of the following parameters:- base slot size- hop duration- number of slots in a frameThe system must be configured such that the RSS is big enough to hold the longest protocol message aremote will send. This is done by setting the appropriate hop duration for the chosen BSS and number ofslots. The required hop duration for a specific number of slots, base slot size and remote slot size is cal-culated as follows:HD hop duration in µsNS number of slotsBSS base slot size in bytesRSS remote slot size in bytesHD = NS*(80*RSS + 2440) + 80*BSS + 3280 (round HD up to an even multiple of 500 µs)Example:NS = 4BSS = 96RSS = 109HD = 4*(80*109 + 2440) + 80*96 + 3280HD = 44640 + 7680 + 3280HD = 55600 round to 56000 µs = 56 msExcelFormatted Equations (load the Excel analysis ToolPak add-in for the QUOTIENT function):ABCDE1SlotsBSSRSSHop Duration in µsHop Duration in ms, Rounded2Up to the next 0.5 ms Step312020=A3*(80*C3+2440) + 80*B3 + 3280=0.5*QUOTIENT((D3+499),500)For transparent serial port operation without using hardware flow control, the BSS and RSS must be largeenough to accommodate all message bytes that can accumulate between transmissions. The requiredBSS and RSS for protocol-formatted messages sent over the wireless link are shown in Table 7.3.1. Forexample, the BSS and RSS size required for a TxData protocol-formatted message is three bytes lessthan the value in the length byte field of the formatted message.The default BSS is 40 bytes, number of slots is 3 and hop duration is 20 ms. These parameter settingsprovide a 25 byte RSS. These default settings are suitable for point-to-point and small to medium point-to-multipoint systems operating with protocol-formatted and/or transparent messages. To accommodate
www.MURATA.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@Murata.comPage 23 of 80DNT90 Integration Guide - 08/09/12all configuration commands, replies, event messages and announce messages, a 20 byte minimum slotsize is required.The NumSlots and the MsgsPerHop parameters both affect the number of messages that can be sent oneach hop. The distinction between these parameters is as follows:- The NumSlots parameter controls the maximum number of individual children that can sendmessages to a parent on each hop.- The MsgsPerHop parameter controls the maximum number of messages a parent or child cansend on each hop.The NumSlots parameter is configurable only for the base. The base then communicates the NumSlotsvalue to all other radios in its system. The NumSlots parameter can be set to one for a point-to-point sys-tem, as there is only one child radio. The NumSlots parameter can be set to allow up to eight children tosend messages to their parent during a hop. As discussed above, the hop duration must be increased asthe number of slots are increased to achieve a specific RSS. The default NumSlots parameter value ofthree is suitable for many applications.De facto TDMA operation (guaranteed bandwidth) can be implemented for up to 8 remotes by setting theSlotLease parameter to a value greater than any gaps in data being sent to a remote by its local host.This will insure that the base keeps each remote’s slot reserved for it even when there is a gap in the da-ta.The MsgsPerHop parameter is configurable for each DNT90E in a system. This parameter is usually setto a high value in the base and the routers, allowing traffic between a parent and multiple children oneach hop. The MsgsPerHop parameter has little effect in remotes except when a remote needs to sendmulti- ple peer-to-peer messages during a hop. To support sending multiple messages on each hop, theBSS and RSS must be sized accordingly, requiring a longer hop duration. Note that the messages mustbe protocol messages and all messages to be sent on a single hop must be in the module before themodule begins to transmit.5.0 DNT90E Application Interface ConfigurationDNT90E modules include a comprehensive set of application interfaces and related options that supporta wide range of applications including wireless RS232/485 cable replacements, wireless sensornetworks, wireless alarm systems and industrial remote control applications. Recommendedconfiguration steps for each application interface are discussed in Sections 5.1 through 5.7 below.5.1 Configuring the Serial PortThe default serial port configuration is 9.6 kbps, 8-bit data, no parity and 1 stop bit.1. Configure the serial data rate as required from 1.2 to 250 kbps by setting the SerialRateparameter in Bank 3.2. Configure the parity and number of stop bits by setting the SerialParams parameter in Bank 3.3. Enable/disable serial port hardware flow control as required by setting the GpioAlt parameter inBank 6. Hardware flow control is disabled by default, but is recommended when operating athigher baud rates and/or sending large blocks of data.
www.MURATA.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@Murata.comPage 24 of 80DNT90 Integration Guide - 08/09/125.2 Configuring the SPI Port1. Enable either SPI master mode or SPI slave mode by setting the SpiMode parameter in Bank 3.The serial port remains operational in SPI master mode but is disabled in SPI slave mode.2. If using SPI master mode:a. Select the SPI clock rate by setting the SpiRateSel parameter in Bank 3 (defaultis 125 kbps)b. Set the SPI master command string and string length by setting the SpiMasterCmdStrand SpiMasterCmdLen parameters respectively in Bank 3.3. Configure the edge trigger direction, bit-sampling edge and bit-order options by setting theSpiOptions parameter in Bank 3.5.3 Configuring Digital I/O1. GPIO2 through GPIO 5 have configurable alternate functions as discussed in Section 7.4.7. Se-lect either digital (state) functionality or alternate functionality for each of these pins by setting theGpioAlt parameter in Bank 6. Note that selecting SPI slave mode overrides the GpioAlt parametersetting for GPIO3 though GPIO5.2. Configure the direction of each GPIO pin as needed by setting the GpioDir parameter in Bank 6(the default is all inputs).3. Configure the direction of each GPIO pin for sleep mode as needed by setting the GpioSleepDirparameter in Bank 6 (the default is all inputs).4. Set the initial state (power on) of all GPIO pins configured as outputs by setting the GpioInit pa-rameter in Bank 6 (the default is all logic low).5. Set the state of all GPIO pins configured as outputs in sleep mode by setting the GpioSleepStateparameter in Bank 6 (the default is all logic low).6. GPIO0 through GPIO3 can trigger I/O event reporting when functioning as digital inputs. Enableevent report triggering and optional sleep hold-off for these pins by setting the GpioEdgeTriggerparameter in Bank 6.5.4 Configuring Analog I/O1. Select the ADC full-scale reference by setting the AdcReference parameter in Bank 6. This set-ting applies to all ADC channels. The default is the ADC_EXT_REF input. If ADC operation is notneeded, setting this parameter to 0x03 disables ADC operation, reducing current consumption.2. Select the ADC mode, either single-ended or differential by setting the AdcDiffMode parameter inBank 6. The default is single-ended ADC operation.3. If differential ADC mode is selected, set the desired ADC preamplifier gain for each ADC channelwith the AdcGainCh0 and AdcGainCh1 parameters in Bank 6. The default gain is 1. Note that thefull scale output voltage from the preamplifier is 2.4 V.
www.MURATA.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@Murata.comPage 25 of 80DNT90 Integration Guide - 08/09/124. Reconfigure the ADC measurement interval as needed by setting the AdcSampleIntvl parameter.The default is 100 ms, and applies to all ADC channels.5. Set the AdcAveSelect parameter to the number of ADC readings to be averaged to produce ameasurement. The larger the AdcAveSelect parameter is set, the greater the noise filtering effect,but the longer it takes to produce a measurement. Setting this parameter to 8 or more when theADC is operating in single-ended mode is especially helpful in stabilizing ADC measurements.6. Measurements on each ADC input can be compared to high/low threshold values, triggering anI/O event report if the measurements go above/below the respective thresholds. The thresholdsfor each ADC channel are set by loading the AdcXThresholdLo and AdcXThresholdHi, where Xrefers to the ADC channel designator, 0 through 2. When the ADC is operating in differentialmode, the ADC1 to ADC0 differential measurement is compared to the “0” high and low thresh-olds, and the ADC2 to ADC0 differential measurements is compared to the “1” high and lowthresholds. In this case the “2” threshold values are not used.7. Set the IoPreDelay parameter as needed in Bank 6 to allow signals to stabilize following a mod-ule wakeup event.8. Set the AdcSkipCount parameter in Bank 6 as needed to allow internal transients in the ADCsample-and-hold circuit to settle out. This parameter must be set to at least 3 when AdcDiffModeis selected. Note that the IoPreDelay parameter discussed above provides a delay to allow sig-nals external to the DNT90E to settle following an event, while AdcSkipCount skipsmeasurements that may be distorted because the internal voltage on the ADC sample-and-holdhas not settled.9. Select the DAC full scale reference by setting DacReference in Bank 6. This setting applies toboth DAC channels. The default is the ADC_EXT_REF input. If DAC operation is not needed, set-ting this parameter to 0x03 will disable DAC operation, reducing current consumption.10. Configure the initial (power on) output level for DAC0 and DAC1 by loading the initial settings inthe Dac0Init and Dac1Init parameters respectively.The ADC and DAC channels are factory calibrated. It may be desirable to fine tune these calibrationsafter the DNT90E has been integrated with the customer’s hardware in some applications. For analogcalibration support, contact MURATA technical support.5.5 Configuring I/O Event Reporting and I/O Binding1. Select the analog, digital and timing events that will trigger an I/O event report by setting therespective bits in the IoReportTrigger parameter in Bank 6. The default is no triggers set.2. Configure the trigger behavior bits in the GpioEdgeTrigger parameter, Bank 6, for each GPIOinput selected to generate an I/O event report.3. For each ADC channel selected to generate an I/O event, set the high and low measurementthreshold values. The AdcThreshold parameters are in Bank 6. When the ADC is operating in dif-ferential mode, the ADC1 to ADC0 differential measurement is compared to the “0” high and lowthresholds, and the ADC2 to ADC0 differential measurements is compared to the “1” high and lowthresholds. In this case the “2” threshold values are not used.4. If the periodic timer has been selected to generate an event report, load the required timer reportinterval into the IoReportInterval parameter in Bank 6. The default timer interval is 30 seconds.
www.MURATA.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@Murata.comPage 26 of 80DNT90 Integration Guide - 08/09/125. Set the MaxQueuedEvents parameter in Bank 6 as needed to limit the number of Event Reportsthat can be queued at one time by a DNT90E. This parameter is used to prevent a router devicefrom clogging up its outbound queue with its own pending transmissions if it has having troubleobtaining link or an available slot from its parent.6. If I/O binding operation is desired, set the IoBindingEnable parameter in Bank 6 to 0x01.I/O binding is disabled by default, and cannot be used when the ADC is operating indifferential mode.5.6 Configuring Sleep ModeSleep mode can be used in conjunction with I/O reporting to greatly extend battery life on DNT90Ere- motes. At least one I/O report trigger must be enabled to allow sleep mode to be used. Note thatthe base and routers cannot be configured for sleep mode.1. Enable sleep mode as desired in each remote by setting the SleepModeEn parameter in Bank 0 to 1.2. Configure the timeout for a remote to attempt to link to its parent when triggered awake. This is doneby setting the WakeLinkTimeout parameter in Bank 0. The default timeout is 5 seconds.3. Configure the maximum time a remote in sleep mode will remain awake following linking, receiving anACK, processing a message addressed to it, or receiving a serial or SPI message by setting theWake-ResponseTime parameter. The default response time is 500 ms. Note that the setting of thisparameter is overridden by some GpioEdgeTrigger parameter settings.
www.MURATA.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@Murata.comPage 27 of 80DNT90 Integration Guide - 08/09/126.0 DNT90E HardwareD N T 9 0E B l o c k D i a g r a mG N D 1A C T ( D I A G T X ) 2/ D C D ( D I A GR X ) 3G P I O 0 4R A D I O T X D5R A D I O R X D6G P I O 4 ( / H OS T C T S ) 7G P I O 5 ( / H OS T R T S ) 8D A C 0 9M i c r o co n t r o l l erI R Q 0I R Q 1/ D C LK D A TAP L LL O CK S C KS D IS D OT RC 1 03S A WF i l te r an dP o w e r A m pG P I O 2 1 0G P I O 1 1 1G P I O 3 ( D A V)1 2D A C 1 1 3V C C 1 4G N D 1 5n S S D A T An S S C O N F I G+ 3 . 3 V R e g1 6 1 7 1 8 1 9 2 0 2 12 2 2 3 2 4 2 5 26 2 7 2 8 2 9 3 0Figure 6.0.1The major components of the DNT90E include an MURATA TRC103 900 MHz FHSS transceiver and alow cur- rent 8-bit microcontroller. The DNT90E operates in the 902 to 928 MHz ISM band. There are fourse- lectable hopping patterns providing compatibility with frequency allocations in North America, SouthAmerica and Australia. The DNT90E also has two selectable RF output power levels: +16 dBm (40 mW)and +25 dBm (316 mW).The DNT90E receiver is protected by a low-loss SAW filter, providing an excellent blend of receiversensi- tivity and out-of-band interference rejection that is especially important in outdoor applications.The DNT90E provides a variety of hardware interfaces. There are two serial ports plus one SPI port. Eitherthe primary serial port or the SPI port can be selected for data communications. The second serial port isdedicated to diagnostics. The primary and diagnostic serial ports support most standard baud rates up to250 kbps. The SPI port supports data rates up to 500 kbps. Also included are three ADC inputs, two DACoutputs and six general-purpose digital I/O ports. Four of the digital I/O ports support an optional interrupt-from-sleep mode when configured as inputs. The radio is available in two mounting configurations. TheDNT90EC is designed for solder reflow mounting. The DNT90EP is designed for plug-in connector mount-ing.GNRSVGNRSVRSVA D C EX T R E3 . 3 VO USCL/SMOSMI SADCADC/ RE SEGN
www.MURATA.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@Murata.comPage 28 of 80DNT90 Integration Guide - 08/09/126.1 SpecificationsAbsolute Maximum RatingValueUnitsPower Supply Input-0.5 to +6.5VAll Input/Output Pins-0.5 to +3.3VInput Power to RFIO Port0dBmNon-operating Ambient Temperature Range-40 to +85oCTable 6.1.1Operating CharacteristicSymMinimumTypicalMaximumUnitsOperating Frequency Range902.76927.24MHzHop Duration8100msNumber of RF Channels25, 26 or 52ModulationFSKRF Data Transmission Rate100kbpsReceiver Sensitivity, 10-5 BER-100dBmTransmitter RF Output Power40 or 158mWOptimum Antenna Impedance50ΩRF ConnectionU.FL ConnectorNetwork TopologiesPoint-to-Point, Point-to-Multipoint,Peer-to-Peer and Store-and-ForwardAccess SchemeAd Hoc TDMAADC Input Range02.7VADC Input Resolution12bitsADC Sample Rate100HzSignal Source Impedance for ADC Reading10KΩADC External Reference Voltage Range1.02.7VDAC Output Range03.3VDAC Output Resolution12bitsPrimary and Diagnostic Serial Port Baud Rates1.2, 2.4, 4.8, 9.6, 19.2, 14.4 28.8, 38.4,57.6, 115.2, 230.4, 250kbpsMaster Serial Peripheral Interface Data Rate125250500kbpsSlave Serial Peripheral Interface Data Rate4000kbpsDigital I/O:Logic Low Input LevelLogic High Input LevelLogic Input Internal Pull-up Resistor-0.50.8V2.453.3V20KΩPower Supply Voltage RangeVCC+3.3+5.5VdcPower Supply Voltage Ripple10mVP-PPeak Transmit Mode Current, 158 mW Output170mAAverage Operating Current, 158 mW TX Output:Base, Continuous Data StreamRemote, Linked, No DataRemote, Continuous Data Stream110mA15mA25mASleep Current36µAOperating Temperature Range-4085oCOperating Relative Humidity Range (non condensing)1090%Table 6.1.2
www.MURATA.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@Murata.comPage 29 of 80DNT90 Integration Guide - 08/09/126.2 Module Pin OutElectrical connections to the DNT90EC are made through the I/O pads and through the I/O pins on theDNT90EP. The hardware I/O functions are detailed in the table below:PinNameI/ODescription1GND-Power supply and signal ground. Connect to the host circuit board ground.2ACT(DIAG_TX)O(O)This pin’s default configuration is data activity output. On a base, this signal blinks when a validpacket is received. On a remote, this signal blinks when a packet is transmitted. On a router, thissignal blinks when a valid upstream packet is received or a downstream packet is transmitted.Alternate pin function is the diagnostic serial port output.3/DCD(DIAG_RX)O(I)This pin’s default configuration is a data carrier detect output. On a base, this signal is assertedwhen any valid packet is received, and is cleared if no packets are heard for the configured rout-er/remote registration time-out interval. On a router or remote, this signal is asserted when theradio obtains hopping pattern synchronization, and remains asserted until no beacons are heardfor 50 hops. Alternate pin function is the diagnostic serial port input.4GPIO0I/OConfigurable digital I/O port 0. When configured as an input, an internal pull-up resistor can beselected and direct interrupt from sleep can be invoked. When configured as an output, the power-on state is configurable. In sleep mode the pin direction, input pull-up selection or output state arealso separately configurable.5RADIO_TXDOSerial data output from the radio.6RADIO_RXDISerial data input to the radio.7GPOI4(/HOST_CTS)I/O(O)GPIO4 with the same configuration options as GPIO2. Alternate pin function is UART/SPI flowcontrol output. The module sets this line low when it is ready to accept data from the host on theRADIO_RXD or MOSI input. When the line goes high, the host must stop sending data.8GPIO5(/HOST_RTS)I/O(I)GPIO5 with the same configuration options as GPIO2. Alternate pin function is UART/SPI flowcontrol input. The host sets this line low to allow data to flow from the module on the RADIO_TXDpin. When the host sets this line high, the module will stop sending data to the host.9DAC0O12-bit DAC 0 output. Full scale can be referenced to the voltage at pin 25, or the 3.3 V regulatedmodule bus voltage.10GPIO2I/OConfigurable digital I/O port 2. Same configuration options as GPIO0.11GPIO1I/OConfigurable digital I/O port 1. Same configuration options as GPIO0.12GPIO3(DAV)I/O(O)Default pin function is GPIO3 with the same configuration options as GPIO0. When SPI slavemode operation is enabled, a logic high on this pin indicates when data is available to be clockedout by the SPI master.13DAC1O12-bit DAC 1 output. Same specifications and configuration options as DAC0.14VCCIPower supply input, +3.3 to +5.5 Vdc.15GND-Power supply and signal ground. Connect to the host circuit board ground.16GND-Power supply and signal ground. Connect to the host circuit board ground.17/RESETIActive low module hardware reset.18ADC0IADC input 0. This pin is a direct ADC input when the ADC is operating in single-ended mode, or thedifferential negative input for positive inputs applied to ADC1 or ADC2 when the ADC is operat- ingin differential mode. Full-scale reading can be referenced to Pin 25 for ratiometric measure- ments.For absolute measurements, the ADC can use the regulated supply voltage divided by 1.6 (about2.06 V), or an external voltage applied to Pin 25. In single-ended mode, ADC measure- mentsare 11-bit unsigned values with full scale nominally 2.7 V when referenced to a 2.7 V input onPin 27. In differential mode, ADC measurements are 12-bit signed values.19ADC1IADC input 1. Direct input when the ADC is operating in single-ended mode, positive differentialinput relative to ADC0 when the ADC is operating in differential mode.20MISOI/OThis pin is the SPI master mode input or slave mode output.21MOSII/OThis pin is the SPI master mode output or slave mode input.22/SSI/OSPI active low slave select. This pin is an output when the module is operating as a master, and aninput when it is operating as a slave.23SCLKI/OSPI clock signal. This pin is an output when operating as a master, and an input when operating asa slave.
www.RFM.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@rfm.comPage 30 of 80DNT90 Integration Guide - 08/09/12PinNameI/ODescription (continued)24ADC2IADC input 2. Direct input when the ADC is operating in single-ended mode, positive differentialinput relative to ADC0 when the ADC is operating in differential mode.25ADC_EXT_REFI/OADC external reference voltage pin. The voltage at this pin can be used by the ADCs as a refer-ence for ratiometric measurements. With no external voltage or load applied, this pin presents anominal 2.7 V output through a 2.126 K source resistance. A low impedance external referencevoltage in the range of 1.0 to 2.7 V may be applied to this pin as an option.26RSVD-Reserved pin. Leave unconnected.27RSVD-Reserved pin. Leave unconnected.28GND-Connect to the host circuit board ground plane.29RSVD-Reserved pin. Leave unconnected.30GND-Connect to the host circuit board ground plane.6.3 Antenna ConnectorTable 6.2.1A U.FL miniature coaxial connector is provided on both DNT90E configurations for connection to theRFIO port. A short U.FL coaxial cable can be used to connect the RFIO port directly to an antenna. Inthis case the antenna should be mounted firmly to avoid stressing the U.FL coaxial cable due to antennamounting flexure. Alternately, a U.FL coaxial jumper cable can be used to connect the DNT90E moduleto a U.FL connector on the host circuit board. The connection between the host circuit board U.FLconnector and the antenna or antenna connector on the host circuit board should be implemented as a50 ohmC i r c u i t B o a r d S t r i p l i n e T r a c e D e t a i lF o r 5 0 o h m i m p e d a n c e W = 1 . 7 5 * HFigure 6.3.1Trace Separation from50 ohm MicrostripLength of Trace RunParallel to Microstrip100 mil125 mill150 mil200 mil200 mil290 mil250 mil450 mil300 mil650 milTable 6.3.2stripline. Referring to Figure 6.3.1, the width of this stripline depends on the thickness of the circuit boardbetween the stripline and the groundplane. For FR-4 type circuit board materials (dielectric constant of4.7), the width of the stripline is equal to 1.75 times the thickness of the circuit board. Note that other cir-C o pp e rS t r ip l i ne T r ac eC op p erG r ou n dP l an eF R - 4P C BM a te r i al
www.RFM.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@rfm.comPage 31 of 80DNT90 Integration Guide - 08/09/12D N T5 0 0cuit board traces should be spaced away from the stripline to prevent signal coupling, as shown in Table6.3.2. The stripline trace should be kept short to minimize its insertion loss.6.4 Power Supply and Input VoltagesDNT90E radio modules can operate from an unregulated DC input (Pad 19) in the range of 3.3 to 5.5 Vwith a maximum ripple of 5% over the temperature range of -40 to 85 °C. Applying AC, reverse DC, or aDC voltage outside the range given above can cause damage and/or create a fire and safety hazard. Fur-ther, care must be taken so logic inputs applied to the radio stay within the voltage range of 0 to 3.3 V.Signals applied to the analog inputs must be in the range of 0 to ADC_EXT_REF (Pad/Pin 25). Applying avoltage to a logic or analog input outside of its operating range can damage the DNT90E module.6.5 ESD and Transient ProtectionThe DNT90EC and DNT90EP circuit boards are electrostatic discharge (ESD) sensitive. ESD precautionsmust be observed when handling and installing these components. Installations must be protected fromelectrical transients on the power supply and I/O lines. This is especially important in outdoor installations,and/or where connections are made to sensors with long leads. Inadequate transient protection can resultin damage and/or create a fire and safety hazard.6.6 Interfacing to 5 V Logic SystemsAll logic signals including the serial ports on the DNT90E are 3.3 V signals. To interface to 5 V signals,the resistor divider network shown in Figure 3.7.1 below must be placed between the 5 V signal outputsand the DNT90E signal inputs. The output voltage swing of the DNT90E 3.3 V signals is sufficient todrive 5 V logic inputs.5 VL o g i c6.7 Mounting and EnclosuresFigure 6.6.1DNT90EC radio modules are mounted by reflow soldering them to a host circuit board. DNT90EPmodules are mounted by plugging their pins into a set of mating connectors on the host circuit board.Refer to Sec- tion 8.3 and/or the DNT90E Data Sheet for DNT90EP connector details.DNT90E enclosures must be made of plastics or other materials with low RF attenuation to avoid compro-mising antenna performance where antennas are internal to the enclosure. Metal enclosures are not suit-able for use with internal antennas as they will block antenna radiation and reception. Outdoor enclosuresmust be water tight, such as a NEMA 4X enclosure.DNT902 .2K4 .3K
www.RFM.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@rfm.comPage 32 of 80DNT90 Integration Guide - 08/09/126.8 Labeling and NoticesDNT90E FCC Certification - The DNT90E hardware has been certified for operation under FCC Part 15Rules, Section 15.247. The antenna(s) used for this transmitter must be installed to provide a separationdistance of at least 21 cm from all persons and must not be co-located or operating in conjunction withany other antenna or transmitter.DNT90E FCC Notices and Labels - This device complies with Part 15 of the FCC rules. Operation is sub-ject to the following two conditions: (1) this device may not cause harmful interference, and (2) this devicemust accept any interference received, including interference that may cause undesired operation.A clearly visible label is required on the outside of the user’s (OEM) enclosure stating the following text:Contains FCC ID: HSW-DNT90EContains IC: 4492A-DNT90EMURATA (Insert Model Designation DNT90EC or DNT90EP depending on the model used)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 interferencereceived, including interference that may cause undesired operation.WARNING: This device operates under Part 15 of the FCC rules. Any modification to this device, notexpressly authorized by MURATA, Inc., may void the user’s authority to operate this device.This apparatus complies with Health Canada’s Safety Code 6 /ISED RSS 247.ISED RSS-247 Notice - Operation is subject to the following two conditions: (1) this device may notcause interference, and (2) this device must accept any interference, including interference that maycause un- desired operation of the device.ICES-003This digital apparatus does not exceed the Class B limits for radio noise emissions from digital apparatusas set out in the radio interference regulations of ISED Canada.Le present appareil numerique n’emet pas de bruits radioelectriques depassant les limites applicablesaux appareils numeriques de Classe B prescrites dans le reglement sur le brouillage radioelectriqueedicte par ISED Canada.
www.RFM.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@rfm.comPage 33 of 80DNT90 Integration Guide - 08/09/127.0 DNT90E Protocol-formatted Messages7.1 Protocol FormatsDNT90E modules can work in one of two serial data modes - transparent or protocol. Transparent moderequires no data formatting, but is limited to sending data to either a single destination or broadcastingdata to all destinations. A node that needs to send messages to individual destinations must use protocolformatting unless the data being sent includes addressing information. Protocol formatting is also requiredfor configuration commands and replies, and sensor I/O commands, replies and events. All protocol-formatted messages have a common header as shown in Figure 7.1.1:0123 …SOPLengthPktTypevariable number of arguments …The scale above is in bytes.Figure 7.1.1The Start-of-Packet (SOP) character, 0xFB, is used to mark the beginning of a protocol-formatted mes-sage and to assure synchronization in the event of a glitch on the serial port at startup.The Length byte is defined as the length of the remainder of the message following the length byte itself,or the length of the entire message - 2.The Packet Type (PktType) byte specifies the type of message. It is a bitfield-oriented specifier, decodedas follows:Bits 7..6 Reserved for future useBit 5 Event - this bit is set to indicate an event messageBit 4 Reply - this bit is set to indicate a message is a replyBits 3..0 Type - these bits indicate the message typeAs indicated, the lower four bits (3..0) specify a message type. Bit 4 indicates that the message is a reply.A reply message has the original command type in bits 3..0, with Bit 4 set to one. Bit 5 indicates an eventmessage. Arguments vary in size and number depending on the type of message and whether it is amessage sent from the host, or is a reply or event message from the radio. See Section 7.3 below.7.2 Message TypesMessages generated on the serial interface by the user are referred to as host messages. Messagesgenerated on the serial interface by the radio are referred to as reply or event messages. Host messagescarry commands. For most commands, there is a corresponding reply message. For example, when thehost sends a TxData command message, the radio can return a TxDataReply message to indicate thestatus of the transmission - whether it succeeded or failed. To assist in interpreting the command-replydata flow, the direction is indicated by the high nibble in the message type. For example, an EnterProto-colMode command from the host is a message type 0x00, and the EnterProtocolModeReply from the ra-dio is a message type 0x10.Event messages from a DNT90E, such as received data or status announcements make up a thirdcatego- ry of messages. Event messages, including RxData,RxEvent and Announce packets areindicated by 0x20 in the high nibble of the type byte.If multiple arguments are to be provided, they are tobe concate- nated in the order shown in Section 7.3 below. Little-Endian byte order is used for all multi-byte
www.RFM.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@rfm.comPage 34 of 80DNT90 Integration Guide - 08/09/12arguments except text strings. Little-Endian byte order places the lowest order byte in the left-most byteof the argument and the highest order byte in the right-most byte of the argument.7.3 Message Format DetailsTable 7.3.1 below summarizes the DNT90E protocol-formatted messages:CommandReplyEventTypeDirectionMin Slot Size0x00--EnterProtocolModefrom HostN/A-0x10-EnterProtocolModeReplyfrom RadioN/A0x01--ExitProtocolModefrom HostN/A0x02--DeviceResetfrom HostN/A-0x12-DeviceResetReplyfrom RadioN/A0x03--GetRegisterfrom HostN/A-0x13-GetRegisterReplyfrom RadioN/A0x04--SetRegisterfrom HostN/A-0x14-SetRegisterReplyfrom RadioN/A0x05--TxDatafrom Hostlength value -0x03-0x15-TxDataReplyfrom Radio0x010x06--GetRemoteRegisterfrom Host0x03-0x16-GetRemoteRegisterReplyfrom Radio0x140x07--SetRemoteRegisterfrom Host0x13-0x17-SetRemoteRegisterReplyfrom Radio0x04--0x26RxDatafrom Radiolength value -0x03--0x27Announce/Errorfrom Radio0x07--0x28RxEventfrom Radio0x0DTable 7.3.1EnterProtocolMode command and reply format details are presented in Tables 7.3.2 and 7.3.3:Enter Protocol Mode CommandByte OffsetFieldDescription0x00Start-of-Packet0xFB = Indicates start of protocol formatted message0x01Length0x07 = Number of bytes in message following this byte0x02Packet Type0x00 = EnterProtocolMode0x03 - 0x08PayloadString = “DNTCFG” or 0x44 0x4E 0x54 0x43 0x46 0x47Table 7.3.2Enter Protocol Mode ReplyByte OffsetFieldDescription0x00Start-of-Packet0xFB = Indicates start of protocol formatted message0x01Length0x01 = Number of bytes in message following this byte0x02Packet Type0x10 = EnterProtocolModeReplyTable 7.3.3
www.RFM.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@rfm.comPage 35 of 80DNT90 Integration Guide - 08/09/12ExitProtocolMode command format details are shown in Table 7.3.4:Exit Protocol Mode CommandByte OffsetFieldDescription0x00Start-of-Packet0xFB = Indicates start of protocol formatted message0x01Length0x01 = Number of bytes in message following this byte0x02Packet Type0x01 = ExitProtocolModeTable 7.3.4DeviceReset command and reply format details are shown in Tables 7.3.5 and 7.3.6:Device Reset CommandByte OffsetFieldDescription0x00Start-of-Packet0xFB = Indicates start of protocol formatted message0x01Length0x02 = Number of bytes in message following this byte0x02Packet Type0x02 = DeviceReset0x03Reset Type0x00 = Normal Device Reset0x01 = Reset to Serial Bootloader0x02 = Reset to Over-the-Air BootloaderTable 7.3.5Device Reset ReplyByte OffsetFieldDescription0x00Start-Of-Packet0xFB = Indicates start of protocol formatted message0x01Length0x01 = Number of bytes in message following this byte0x02Packet Type0x12 = DeviceResetReplyTable 7.3.6GetRegister command and reply format details are shown in Tables 7.3.7 and 7.3.8:Get Register CommandByte OffsetFieldDescription0x00Start-of-Packet0xFB = Indicates start of protocol formatted message0x01Length0x04 = Number of bytes in message following this byte0x02Packet Type0x03 = GetRegister0x03Register OffsetRegister offset in its bank0x04Register BankRegister bank number0x05Register SizeRegister size in bytes, only one parameter at a time (wrong register size willproduce an error response)Table 7.3.7
www.RFM.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@rfm.comPage 36 of 80DNT90 Integration Guide - 08/09/12Get Register ReplyByte OffsetFieldDescription0x00Start-of-Packet0xFB = Indicates start of protocol formatted message0x01Length0x05 to 0x20 = Number of bytes in message following this byte0x02Packet Type0x13 = GetRegisterReply0x03Register OffsetRegister offset in its bank0x04Register BankRegister bank number0x05Register SizeRegister size in bytes0x06 - 0x15Register ValueRegister value, all bytes in the register (only one parameter at a time)Note: an Error message will be returned instead of a GetRegisterReply in case of a format error.Table 7.3.8SetRegister command and reply format details are shown in Tables 7.3.9 and 7.3.10:Set Register CommandByte OffsetFieldDescription0x00Start-of-Packet0xFB = Indicates start of protocol formatted message0x01Length0x05 to 0x20 = Number of bytes in message following this byte0x02Packet Type0x04 = SetRegister0x03Register OffsetRegister offset in its bank0x04Register BankRegister bank number0x05Register SizeRegister size in bytes0x06 - 0x15Register ValueRegister value, all bytes in the register (only one parameter at a time)Table 7.3.9Set Register ReplyByte OffsetFieldDescription0x00Start-of-Packet0xFB = Indicates start of protocol formatted message0x01Length0x01 = Number of bytes in message following this byte0x02Packet Type0x14 = SetRegisterReplyNote: an Error message will be returned instead of a SetRegisterReply in case of a format error.Table 7.3.10TXData command and reply format details are shown in Tables 7.3.11 and 7.3.12:TX Data CommandByte OffsetFieldDescription0x00Start-of-Packet0xFB = Indicates start of protocol formatted message0x01Length= Number of bytes in message following this byte0x02Packet Type0x05 = TxData0x03 - 0x05Destination MAC AddressDestination MAC address, in Little Endian byte order0x06 - 0x72Tx DataUp to 109 bytes of data to Base, or 105 bytes from BaseTable 7.3.11
www.RFM.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@rfm.comPage 37 of 80DNT90 Integration Guide - 08/09/12TX Data ReplyByte OffsetFieldDescription0x00Start-of-Packet0xFB = Indicates start of protocol formatted message0x01Length0x07 = Number of bytes in message following this byte0x02Packet Type0x15 = TxDataReply0x03 - 0x05Destination MAC AddressDestination MAC address, in Little Endian byte order0x06Status0x00 = ACK received from destination0x01 = no ACK received from destination (NAK)0x02 = “Device Not Linked” error0x07RSSIPacket RX power in dBm, -128 to 126 or 127 if invalidNote: TxDataReply messages are only returned to the host when the EndToEndAckEnable parameter is set to 0x01.Table 7.3.12GetRemoteRegister command and reply details are shown it Tables 7.3.13 and 7.3.14:Get Remote Register CommandByte OffsetFieldDescription0x00Start-of-Packet0xFB = Indicates start of protocol formatted message0x01Length0x07 = Number of bytes in message following this byte0x02Packet Type0x06 = GetRemoteRegister0x03 - 0x05Destination MAC AddressDestination MAC address, in Little Endian byte order0x06Register OffsetRegister offset in its bank0x07Register BankRegister bank number0x08Register SizeRegister size in bytes, only one parameter at a time (wrong register size willproduce an error response)Table 7.3.13Get Remote Register ReplyByte OffsetFieldDescription0x00Start-of-Packet0xFB = Indicates start of protocol formatted message0x01Length0x0A to 0x25 = Number of bytes in message following this byte0x02Packet Type0x16 = GetRemoteRegisterReply0x03StatusError status (0x00 = No Error, 0xE1 = Invalid Argument)0x04 - 0x06Originator MAC AddressOriginator’s MAC address, in Little Endian byte order0x07RSSI(-128 to 126 or 127 if invalid)0x08Register Offset*Register offset in its bank0x09Register Bank*Register bank number0x0ARegister Size*Register size in bytes0x0B - 0x1ARegister Value*Register value, all bytes in the register (only one parameter at a time)*Bytes eight through the end of the message will not be returned in case of an errorTable 7.3.14
www.RFM.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@rfm.comPage 38 of 80DNT90 Integration Guide - 08/09/12SetRemoteRegister command and reply format details are shown in Tables 7.3.15 and 7.3.16:Set Remote Register CommandByte OffsetFieldDescription0x00Start-of-Packet0xFB = Indicates start of protocol formatted message0x01LengthNumber of bytes in message following this byte0x02Packet Type0x07 = SetRemoteRegister0x03 - 0x05Destination MAC AddressDestination MAC address, in Little Endian byte order0x06Register OffsetRegister offset in its bank0x07Register BankRegister bank number0x08Register SizeRegister size in bytes0x09 - 0x18Register ValueRegister contentsTable 7.3.15Set Remote Register ReplyByte OffsetFieldDescription0x00Start-of-Packet0xFB = Indicates start of protocol formatted message0x01Length0x06 = Number of bytes in message following this byte0x02Packet Type0x17 = SetRemoteRegisterReply0x03StatusError status: 0x00 = no error, 0xE1 = invalid argument0x04 - 0x06Originator MAC AddressOriginator’s MAC address, in Little Endian byte order0x07RSSIPacket RX power in dBm, -128 to 126, or 127 if invalidTable 7.3.16RxData event packet format details are shown in Figure Table 7.3.17:RX Data PacketByte OffsetFieldDescription0x00Start-of-Packet0xFB = Indicates start of protocol formatted message0x01Length0x00 to 0x6D = Number of bytes in message following this byte0x02Packet Type0x26 = RxData event message0x03 - 0x05Originator MAC AddressOriginator’s MAC address, in Little Endian byte order0x06RSSIPacket RX power in dBm, -128 to 126, or 127 if invalid0x07 - 0x73Rx DataUp to 105 bytes of data from Base, up to 109 bytes from Router or RemoteTable 7.3.17
www.RFM.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@rfm.comPage 39 of 80DNT90 Integration Guide - 08/09/12Announce/Error message format details are shown in Tables 7.3.18 through 7.3.21:Startup Announcement or Error CodeByte OffsetFieldDescription0x00Start-of-Packet0xFB = Indicates start of protocol formatted message0x01Length0x02 = Number of bytes in message following this byte0x02Packet Type0x27 = Indicates this is an Announce/Error message0x03Announce Status0xA0 = Startup initialization complete0xA1 = Synchronized to fast beacon0xE1 = Invalid argument0xE4 = Register read only error0xEC = Brownout reset0xED = Watchdog reset0xEE = Hardware Error (Crystal or Radio Error)Table 7.3.18Join AnnouncementByte OffsetFieldDescription0x00Start-of-Packet0xFB = Indicates start of protocol formatted message0x01Length0x06 = Number of bytes in message following this byte0x02Packet Type0x27 = Indicates this is an Announce/Error message0x03Announce Status0xA3 = Joined network0x04Network IDID of network that was joined0x05 - 0x07Parent MAC AddressMAC address of parent, in Little Endian byte orderTable 7.3.19Exit AnnouncementByte OffsetFieldDescription0x00Start-of-Packet0xFB = Indicates start of protocol formatted message0x01Length0x03 = Number of bytes in message following this byte0x02Packet Type0x27 = Indicates this is an Announce/Error message0x03Announce Status0xA4 = Exited network0x04Network IDID of network that was exitedTable 7.3.20Heartbeat AnnouncementByte OffsetFieldDescription0x00Start-of-Packet0xFB = Indicates start of protocol formatted message0x01Length0x0C = number of bytes in message following this byte0x02Packet Type0x27 = Indicates this is an Announce/Error message0x03Announce Status0xA8 = Heartbeat message0x04 - 0x06Device MAC AddressMAC address of originator, in Little Endian byte order0x07 - 0x09Parent MAC AddressMAC address of parent, in Little Endian byte order0x0AParent Network IDNetwork ID of device’s parent0x0BBase Mode Network IDNetwork ID if device is a router, otherwise 0xFF0x0CBeacon RX PowerAverage beacon RX power in dBm, uses 0.0625 “alpha” averaging filter,-128 to 126 or 127 if invalid0x0DParent RX PowerRX power of packet as received by device’s parent in dBm, -128 to 126 or127 if invalidTable 7.3.21
www.RFM.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@rfm.comPage 40 of 80DNT90 Integration Guide - 08/09/12RxEvent message format details are shown in Table 7.3.22:RX Event PacketByte OffsetFieldDescription0x00Start-of-Packet0xFB = Indicates start of protocol formatted message0x01Length0x12 = number of bytes in message following this byte0x02Packet Type0x28 = RxEvent0x03 - 0x05Originator MAC AddressOriginator’s MAC address, in Little Endian byte order0x06RSSIPacket RX power in dBm (-128 to 127)0x07GPIO ReadingsBit Field (GPIO0..GPIO5) indicating GPIO readings0x08 - 0x09ADC0 ReadingADC0 Reading, 0x0000 - 0x0FFF, in Little Endian byte order0x0A - 0x0BADC1 ReadingADC1 Reading, 0x0000 - 0x0FFF, in Little Endian byte order0x0C - 0x0DADC2 ReadingADC2 Reading, 0x0000 - 0x0FFF, in Little Endian byte order0x0E - 0x0FEvent FlagsBit Field Indicating which events have occurred:Bit 0: GPIO0 TriggeredBit 1: GPIO1 TriggeredBit 2: GPIO2 TriggeredBit 3: GPIO3 TriggeredBit 4: Periodic Report IntervalBit 5: ADC0 Threshold TriggeredBit 6: ADC1 Threshold TriggeredBit 7: ADC2 Threshold TriggeredBits 8-15: Unused (0)0x10 - 0x11DAC0 SettingDAC0 setting, 0x0000 - 0x0FFF, in Little Endian byte order0x12 - 0x13DAC1 SettingDAC1 setting, 0x0000 - 0x0FFF, in Little Endian byte orderTable 7.3.22
www.RFM.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@rfm.comPage 41 of 80DNT90 Integration Guide - 08/09/127.4 Configuration Parameter RegistersThe configuration parameters in a DNT90E module are stored in a set of variable length registers. Mostregisters are read-write, with a few read-only or write-only. Changes made to the register settings aretemporary until a MemorySave command is executed. Resetting or power-cycling the module will clearany changes that have not been saved to permanent memory using the MemorySave command.DNT90E modules can be configured to start in protocol mode at power-up, in which case theEnterProtocolMode command is not required.7.4.1 Bank 0x00 - Transceiver SetupBankLocationNameR/WSizeRangeDefault0x000x00DeviceModeR/W0x010..20 (remote)0x000x01HopDurationR/W0x0116..20040 (20 ms)0x000x02ParentNwkIDR/W0x010..63, 255255 (any parent)0x000x03SecurityKeyR/W0x100..2^128-100x000x13SleepModeEnR/W0x010..20 (off)0x000x14WakeResponseTimeR/W0x020..30000500 (500 ms)0x000x16WakeLinkTimeoutR/W0x010..2555 (5 s)0x000x17AltParentNwkIDR/W0x010..63, 255255 (disabled)0x000x18TxPowerR/W0x010..11 (+22 dBm)0x000x19UserTagR/W0x10string“DNT90E”0x000x29RmtTransDestAddrR/W0x030x000000 (Base)0x000x2CStore&ForwardEnR/W0x010..10 (disabled)0x000x2DBaseModeNetIDR/W0x011..63, 2552550x000x2EHeartbeatIntrvlR/W0x020..655350xFFFF (disabled)0x000x30SystemIdR/W0x010..25500x000x31EndToEndAckEnableR/W0x010..10 (disabled)0x000x32LinkRetryIntervalR/W0x020..655350 (disabled)0x000x34FastBeaconCountR/W0x020..655350 (off)0x000x36FastBeaconTrigR/W0x010..2550 (off)Table 7.4.1.1DeviceMode - this parameter selects the operating mode for the radio:0x00 = remote (default)0x01 = base0x02 = router (store and forward system)Note that changing this setting does not take effect immediately. It must be followed by a MemorySavecommand and then either a hardware reset or a power off/on cycle. A router without a valid BaseMode-NetID operates as a remote.HopDuration - this parameter sets the duration of the hop frame, and can only be set on the base. Theduration is an 8-bit value, 0.5 ms/count. The valid range is from 8 to 100 ms. Changing the hop durationon the base must be followed by a MemorySave command to allow the change to persist through a resetor power cycle. A HopDuration change takes effect immediately. Child radios will re-link following aHopDuration parameter change as they receive the updated hop duration value from the base.
www.RFM.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@rfm.comPage 42 of 80DNT90 Integration Guide - 08/09/12ParentNwkID - this parameter specifies the parent (BaseModeNetID) that a child radio is allowed to join.The valid range of this parameter is 0 to 63 (0x00 to 0x3F), plus 255 (0xFF). Setting the ParentNwkID to255 allows connection to any parent. This parameter is applicable only to remotes and routers. Also seethe discussion of AltParentNwkID below.Security Key - this 16-byte parameter sets the 128-bit AES encryption key. To protect the key, it is a write-only parameter for the user. It always reads back as 0x2A.SleepModeEn - this parameter enables/disables sleep mode (remotes only). Sleep mode is used in con-junction with the automatic I/O reporting feature to wake up a remote on specific triggers. The default val-ue for this parameter is 0 (off). Setting this parameter to 1 invokes sleep mode immediately. Setting thisparameter to 2 invokes sleep mode following reset, allowing this and other parameter updates to bestored before sleep mode is invoked.WakeResponseTime - this parameter set how long sleep is deferred in a DNT90E remote configured forsleep mode after:link acquisitionreceiving an ACK from the device’s parentreceiving a packet that requires processing by the deviceafter receiving a protocol packet from the device’s local host.WakeLinkTimeout - this parameter sets the maximum length of time that a remote in sleep mode willspend trying to acquire a link to its parent before going back to sleep, from a minimum of 1 to 255 se-conds in 1 second steps. If this value is set to 0, the remote will stay awake and continue trying to link toits base indefinitely.AltParentNwkID - this parameter specifies an alternate parent (BaseModeNetID) that a child radio isallowed to join. This parameter is used to provide more robust message routing when setting the Parent-NwkID to its 0xFF wildcard value is not appropriate. The valid range of this parameter is 0x00 to 0x3F,plus 0xFF. Rather than specifying wildcard operation, setting the AltParentNwkID to 0xFF disables theselection of an alternate parent. This parameter is applicable only to remotes and routers.TxPower - this parameter sets the transmit power level (default is 0x01):0x00 = +16 dBm or 40 mW0x01 = +22 dBm or 158 mWUserTag - this parameter is a user definable field intended for use as a location description or other iden-tifying tag such as a “friendly name”.RmtTransDestAddr - this parameter holds the default destination for transparent mode data packets andevent packets. This parameter defaults to the base station’s address (0x000000) except on a base sta-tion, where at startup it will be changed to the broadcast address (0xFFFFFF) if the firmware detects thatit is set to 0x000000. Note - if a module’s configuration is changed from a base to a remote or router, thisparameter must be set back to 0x000000 or the module will send broadcast packets in transparent modeor for event packets.Store&ForwardEn - setting this parameter to 0x01 enables store-and-forward system operation. Store-and-forward operation is disabled by default.BaseModeNetID - applicable to the base and routers only, this parameter specifies the network ID of adevice’s own network when acting as parent. A child is allowed to join a network when its ParentNwkID
www.RFM.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@rfm.comPage 43 of 80DNT90 Integration Guide - 08/09/12parameter matches a parent’s BaseModeNetID. The valid range of this parameter is 0x00 to 0x3F. A val-ue greater than 0x3F is invalid, and will be forced to 0x00 on a base. A router with an invalid Base-ModeNetID will be forced to operate as a remote.HeartbeatInterval - When set to 0, all heartbeats are disabled, including the initial heartbeat issued afterlink acquisition. When set to 0xFFFF (default), periodic heartbeats are disabled but the initial linkupheartbeat is enabled. The periodic heartbeat interval is scaled 1 second/count, and applies to DNT90Eswhere sleep mode is disabled. Remotes with sleep mode enabled must have periodic reports and/or ADCsampling enabled for heartbeats to be generated.SystemId - this parameter holds the ID for a DNT90E system. DNT90E systems that may physicallyoverlap must have different system IDs.EndToEndAckEnable - when this parameter is set to 1 and the DNT90E is in protocol mode, theoriginator will indicate in its transmitted packet that an ACK is expected from the packet’s destinationnode. Setting this parameter to 0x00 reduces network congestion in a store-and-forward system, but noTxDataReply will be sent from the destination to confirm reception.LinkRetryInterval - when a remote enters sleep mode with an unsent packet in its queue, the remote willwake up after the number of seconds held in this parameter and try to link so that pending packets can betransmitted. When this parameter is set to 0, this feature is disabled.FastBeaconCount - this parameter controls the fast beacon mode, which is used to speed up networksynchronization. Fast beacon mode is especially useful for multi-level store-and-forward networks that areconfigured with long hop durations. Fast beacon mode is controlled by the base station. If the Fast-BeaconCount parameter is set to a non-zero value, when the base is reset, powered up or the Fast-BeaconTrig parameter is set to a non-zero value, it will output the number of 6 ms beacons specified inthe FastBeaconCount parameter. The base and all of its children will synchronously decrement a versionof the parameter in their beacons, such that it will reach 0 simultaneously on all devices. This allows allnodes in the DNT90E system to simultaneously transition to using the configured base slot size and num-ber of slots. The beacons also inform all child devices that the network is in Fast beacon mode, so that allchildren will observe the FastBeaconCount and assume, in addition to the 6ms hop timing, a base slot sizeof 0 and a number of slots equal to 1. If the cycled base station operating parameters transmitted inthe beacons, including the BaseSlotSize and NumSlots (see Bank 0x01 parameters) are stable, then afurther speedup of synchronization can be achieved by setting the NumBaseParms on the base station to8. However, this should be done only after all child devices are known to have configuration parametersidentical to the base station’s saved in their EEPROM. The first 9 parameters contain the AES counterand MAC address that are needed to synchronize encryption, along with NumBaseParms.FastBeaconTrig - when this parameter is set to any non-zero value on a base station, fast beacon modestarts if the fastBeaconCount register is already set to a non-zero value. It auto-clears on a base stationand will read back as 0 after it is cleared. On a router or remote, it would do nothing and will not clearexcept after reset.
www.RFM.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@rfm.comPage 44 of 80DNT90 Integration Guide - 08/09/127.4.2 Bank 0x01 - System SettingsBank 1 holds configuration parameters to be input to the base only. The base passes these parameters tothe routers and remotes as needed. The exception is InitFrequencyBand parameter which can also be setin routers and remotes.BankLocationNameR/WSizeRangeDefault0x010x00InitFrequencyBandR/W0x010..3, 2550 (US)0x010x01NumSlotsR/W0x011..830x010x02BaseSlotSizeR/W0x016..105400x010x03SlotLeaseR/W0x011..2552 (hops)0x010x04BcstAttemptLimitR/W0x010..25410x010x05ArqAttemptLimitR/W0x011..25560x010x06LinkDropThresholdR/W0x011..25510 (hops)0x010x07P2PReplyTimeoutR/W0x010..255100 (hops)0x010x08RegistryTimeoutR/W0x010..25550 (hops)0x010x09NumBaseParmsR/W0x018..2121Table 7.4.2.1InitFrequencyBand - this parameter sets the range of frequencies and channel spacing over which theDNT90E system will initially operate. Four bands are available:0x00Band 0: 902.76 to 927.24 MHz, 52 channels, 480 kHz spacing0x01Band 1: 902.76 to 926.76 MHz, 26 channels, 960 kHz spacing0x02Band 2: 915.72 to 927.74 MHz, 25 channels, 480 kHz spacing0x03Band 3: 902.76 to 914.76 MHz, 26 channels, 480 kHz spacing0xFFwildcard - will accept any bandBands 0, 1, 2 and 3 can be used in North and South America (902 to 928 MHz band), with Band 2 usablein Australia.NumSlots - this parameter sets the number of slots available for child transmissions following the parent’sbeacon transmission on a hop.BaseSlotSize - this parameter set the maximum number of payload bytes that the base can send on asingle hop. The default value is 40 bytes.SlotLease - this parameter set the number of hops a parent radio will reserve a slot for a child after re-ceiving a message from that child. Small values such as 2 are suited to short data bursts, and larger val-ues are generally a better choice when devices send a stream of non-continuous data across consecutivehops. The minimum value is 1, assuring that a child can receive an ACK on the next hop after it transmits.BcstAttemptLimit - setting this parameter to 0 enables automatic broadcast message repeats based onthe ArqAttemptLimit parameter value. Setting this parameter to a value between 1 and 254 specifies thenumber of broadcast message repeats independent of the ArqAttemptLimit. This parameter should not beset to 0 if ArqAttemptLimit is set to 255.ArqAttemptLimit - this sets the maximum number of attempts that will be made to send a message on theRF link. Setting this parameter to the maximum value of 255 is a flag value indicating that there should beno limit to the number of attempts to send each packet (infinite number of attempts). This mode is intend-ed for point-to-point networks in serial data cable replacement applications where absolutely no packets
www.RFM.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@rfm.comPage 45 of 80DNT90 Integration Guide - 08/09/12can be lost. Note - if this mode is used in a multipoint network, one remote that has lost link will shut downthe entire network if the base is trying to send it data.LinkDropThreshold - this is the number of consecutive beacons missed by a remote that causes the re-mote to restart a link acquisition search. Please contact MURATA technical support before makingchanges to the parameter.P2PReplyTimeout - this parameter sets the reply timeout for peer-to-peer messages sent from one nodeto another. Because each leg of the journey from one node to another and back may take multiple trans-mit attempts, the length of time to confirm receipt and issue a TxDataReply is subject to more variationthan a transmission directly between a base and a remote. When AckEnable is selected, the P2PReply-Timeout parameter specifies the maximum number of hops or hop pairs that a remote will wait for a replyfrom its recipient. If a reply returns sooner than the timeout, the remote will send a TxDataReply indicatingsuccess (ACK) to its host as soon as it is received, and cancels the timeout. If a reply does not come backbefore the timeout expires, the remote will send a TxDataReply to its host indicating failure (NAK). Ifa reply should come back after the timeout expires the remote will ignore it, as a TxDataReply has al-ready been sent. The units of this parameter are in hops for point-to-point and point-to-multipoint opera-tion and in hop pairs for store-and-forward operation.RegistryTimeout - this parameter sets the number of hops without contact from a child device for which aparent device will preserve the Transaction ID (TID) history for that child. The TID is used to filter out du-plicate packets. After a registry timeout occurs, the TID history is discarded.NumBaseParms - this parameter controls the number of cycled parameters sent in the base station bea-con. It must be left in its default value of 21 until all nodes in a DNT90E system have received all cycledparameters and stored them locally in EEPROM. At this point the number of cycled parameters can beset to 9, which will significantly speed up future system resynchronizations.7.4.3 Bank 0x02 - Status ParametersBankLocationNameR/WSizeRangeDefault0x020x00MacAddressR0x030..0xFFFFFFFixed value0x020x03CurrNwkIDR0x010..63, 255Current Value0x020x04CurrFreqBandR0x010..2, 255Current Value0x020x05LinkStatusR0x010..5Current status0x020x06RemoteSlotSizeR0x010..109Current Value0x020x07SlotNumberR0x010..7Current Value0x020x08HardwareVersionR0x010x41..0x5A0x43 = Rev “C”0x020x09FirmwareVersionR0x010x00..0xFFCurrent FW load0x020x0AFirmwareBuildNumR0x020..65535Current FW load0x020x0CFirmwareBuildDateR0x03BCD (“YYMMDD”)Current FW load0x020x0FFirmwareBuildTimeR0x03BCD (“HHMMSS”)Current FW load0x020x12RssiIdleR0x01-128..127Current Value0x020x13RssiLastR0x01-128..127Current Value0x020x14AvgBeaconPowerR0x01-128..127Current Value0x020x15ParentMacAddressR0x030..0xFFFFFFCurrent Value0x020x18ModelNumberR10x90indicates DNT90ETable 7.4.3.1
www.RFM.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@rfm.comPage 46 of 80DNT90 Integration Guide - 08/09/12MacAddress - this parameter holds the radio's unique 24-bit MAC address.CurrNwkID - this parameter holds the ID of the network the radio is currently assigned to or connected to.A value of 255 (0xFF) means the radio has powered up and is scanning for a network but has not yetjoined one.CurrFreqBand - this parameter holds the frequency band of the network that the radio is currently as-signed to or connected to. A value of 0xFF means the radio has powered up and is scanning for a net-work but has not yet joined one.LinkStatus - this parameter holds the link status of a router or remote:0x00 = idle0x01 = lost link0x02 = acquiring link0x03 = collecting parameters from the base0x04 = registering0x05 = registeredRemoteSlotSize - this parameter holds the current remote slot size, defined as the maximum number ofmessage bytes a remote can send on a single hop. The RemoteSlotSize is calculated by each radio in asystem based on the values of the HopDuration, BaseSlotSize, and NumSlots parameters.SlotNumber - this parameter holds the current slot number assigned to a router or remote.HarwareVersion - this parameter holds an identifier indicating the hardware revision (ASCII character). Avalue of 0x43 is defined for the DNT90E Revision Chardware.FirmwareVersion - this parameter holds the firmware version of the radio in 2-digit BCD format.FirmwareBuildNum - this parameter holds the firmware build number, in binary format.FirmwareBuildDate - this parameter holds the date of firmware build in MM/DD/YY format.FirmwareBuildTime - this parameter holds the time of the firmware build in HH:MM:SS format.RssiIdle - this 2’s compliment parameter holds the last RSSI measurement in dBm made during a timewhen the RF channel was idle. This parameter is useful for detecting interferers.RssiLast - this 2’s compliment parameter holds the last RSSI measurement in dBm made during the re-ceipt of an RF packet with a valid CRC. This parameter is useful for network commissioning/diagnostics.AvgBeaconPower - this 2’s compliment parameter holds the alpha-filtered beacon power (dBm) receivedfrom a device’s parent, where alpha = 0.0625.ParentMacAddress - this parameter holds the MAC address of a DNT90E’s parent.ModelNumber - this parameter specifies the DNT model, in this case a DNT90E.
www.RFM.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@rfm.comPage 47 of 80DNT90 Integration Guide - 08/09/127.4.4 Bank 0x03 - Serial and SPI SettingsBankLocationNameR/WSizeRangeDefault0x030x00SerialRateR/W0x010..103 (9600 baud)0x030x01SerialParamsR/W0x010..70 (8-N-1)0x030x02SpiModeR/W0x010..20 (SPI disabled)0x030x03SpiRateSelR/W0x010..20 (125 kHz)0x030x04SpiOptionsR/W0x010..700x030x05SpiMasterCmdLenR/W0x010..1600x030x06SpiMasterCmdStrR/W0x100..16 byte stringAll 0x00 bytesTable 7.4.4.1SerialRate - this parameter sets the serial data rate as shown below:Setting Serial rate0x001.2 kbps0x012.4 kbps0x024.8 kbps0x039.6 kbps0x0414.4 kbps0x0519.2 kbps0x0628.8 kbps0x0738.4 kbps0x0857.6 kbps0x09115.2 kbps0x0A230.4 kbps0x0B250.0 kbpsSerialParams - this parameter sets the serial mode options for parity and stop bits:Setting Mode0x00No parity, 8 data bits, 1 stop bit (default)0x01No parity, 8 data bits, 2 stop bits0x02Reserved0x03Reserved0x04Even parity, 8 data bits, 1 stop bit0x05Even parity, 8 data bits, 2 stop bits0x06Odd parity, 8 data bits, 1 stop bit0x07Odd parity, 8 data bits, 2 stop bitsNote that 8-bit data with no parity is capable of carrying 7-bit data with parity for compatibility without lossof generality for legacy applications that may require it.SpiMode -this parameter sets the SPI operating mode:Setting Mode0x00SPI disabled - serial UART mode (default)0x01SPI Slave mode0x02SPI Master modeSpiRateSel - this parameter sets the SPI master mode clock rate:Setting Mode0x00125 kbps0x01250 kbps0x02500 kbps
www.RFM.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@rfm.comPage 48 of 80DNT90 Integration Guide - 08/09/12SpiOptions - this parameter allows the SPI to be configured with the following options:Setting Option0x00Leading edge rising, sample leading edge, MSBs sent first0x01Leading edge rising, sample falling edge, MSBs sent first0x02Leading edge falling, sample leading edge, MSBs sent first0x03Leading edge falling, sample falling edge, MSBs sent first0x04Leading edge rising, sample leading edge, LSBs sent first0x05Leading edge rising, sample falling edge, LSBs sent first0x06Leading edge falling, sample leading edge, LSBs sent first0x07Leading edge falling, sample falling edge, LSBs sent firstSpiMasterCmdLen - this parameter sets the length for the SPI master command string that will be used tointerrogate the slave peripheral, when SPI master mode is selected with periodic I/O reporting enabled.SpiMasterCmdStr - this parameter holds the SPI master command string that is used to interrogate theslave peripheral when SPI master mode is selected and periodic I/O reporting is enabled.7.4.5 Bank 0x04 - Host Protocol SettingsBankLocationNameR/WSizeRangeDefault0x040x00ProtocolModeR/W0x010..10 (Transparent)0x040x01TxTimeoutR/W0x010..2550 (No timeout)0x040x02MinPacketLengthR/W0x010..2551 (byte)0x040x03TransPtToPtModeR/W0x010..11 (Last RX)0x040x04MsgsPerHopR/W0x011..88Table 7.4.5.1ProtocolMode - this parameter selects the host protocol mode. The default is 0x00, which is transparentmode, meaning the radio conveys whatever characters that are sent to it transparently, without requiringthe host to understand or conform to the DNT90E's built-in protocol. This setting is recommended forpoint- to-point applications for legacy applications such as wire replacements where another serialprotocol may already exist. Setting this parameter to 0x01 enables the DNT90E protocol formatting. It isnot necessary to define the same protocol mode for all radios in a network. For example, it is frequentlyuseful to configure all the remotes for transparent mode and the base for protocol mode. Note that it ispossible for the host to switch the radio from transparent mode to protocol mode and back as required bytransmitting an EnterProtocolMode command.TxTimeout - this parameter is used to group transparent data to be sent in a single transmission ratherthan being split over two hops. Messages sent over two hops can have gaps in the received data streamthat can cause problems for the receiving application - for example, Modbus RTU. This parameter is thetransmit timeout used for determining message boundaries in transparent data mode. Parameter unitsare in milliseconds. A message boundary is determined whenever a gap between consecutive charactersis equal to or greater than the TxTimeout value, or the number of bytes reaches the MinPacketLength.Either condition will trigger a transmission. The default TxTimeout value is 0 ms which will have the radiosend whatever data is in its transmit buffer as soon as possible.MinPacketLength - this parameter is similar to TxTimeout except it uses the number of bytes receivedinstead of the amount of time without receiving a byte. The default is one byte. A transmission is triggeredwhen either the number of bytes reaches MinPacketLength or a gap is detected between consecutive
www.RFM.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@rfm.comPage 49 of 80DNT90 Integration Guide - 08/09/12characters greater than TxTimeout. If this parameter is set larger than the applicable slot size, the slotsize overrides this parameter and a transmission is triggered when the slot size is filled.TransPtToPtMode - when this parameter is set to 0x00, the destination address of transparent modepackets will be the configured RemoteDestAddr. When set to 0x01, the address initializes to Remote-DestAddr and then updates to the most recent RX packet processed.MsgsPerHop - this parameter sets the maximum number of messages a DNT90E can send in each hopframe. The default value is 8 messages, which is suitable for most applications. Setting MsgsPerHop to alow value allows message flow rate to be controlled.7.4.6 Bank 0x05 - I/O ParametersBankLocationNameR/WSizeRange In BitsDefault0x050x00All-IOR/W0x0D104N/A0x050x0DGpio0R/W0x01100x050x0EGpio1R/W0x01100x050x0FGpio2R/W0x01100x050x10Gpio3R/W0x01100x050x11Gpio4R/W0x01100x050x12Gpio5R/W0x01100x050x13Adc0R0x0212N/A0x050x15Adc1R0x0212N/A0x050x17Adc2R0x0212N/A0x050x19EventFlagsR/W0x0216N/A0x050x1BDac0R/W0x021200x050x1DDac1R/W0x02120Table 7.4.6.1All-IO - this 13-byte parameter packs all the following parameters into a single value. Note that the infor-mation in parameters GPIO0 through GPIO5 is compressed into a single byte to save space in the All-IOparameter. When the ADC is operating in differential mode, the ADC1 to ADC0 differential reading isstored in the ADC0 position, and the ADC2 to ADC0 differential reading is stored in the ADC1 position.The ADC2 reading is not used in ADC differential mode and this position is set to 0.Gpio0 through Gpio5 - if a pin is configured as an output, writing to its corresponding parameter to setsthe pin’s logic state. If a pin is configured as an input, writing to its corresponding parameter enables ordisables the pin’s internal pull-up. Reading these registers returns the current level detected on the corre-sponding pins.Adc0 through Adc2 - read-only parameters that return the current reading for the selected ADC channel(Little-Endian byte order). When the ADC is operating in differential mode, the ADC1 to ADC0 differentialreading is stored in the ADC0 position, and the ADC2 to ADC0 differential reading is stored in the ADC1position. The ADC2 reading is not used in ADC differential mode and this position is set to 0. Also, seethe discussion of the AdcSampleIntvl parameter below.EventFlags - used with the automatic I/O reporting feature, this parameter indicates which I/O eventshave been triggered since the last report (write 0x0000 to reset):
www.RFM.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@rfm.comPage 50 of 80DNT90 Integration Guide - 08/09/12bits 15..8 Reservedbit 7 ADC2 high/low threshold excursionbit 6 ADC1 high/low threshold excursionbit 5 ADC0 high/low threshold excursionbit 4 Periodic timer reportbit 2 GPIO2 edge transitionbit 1 GPIO1 edge transitionbit 0 GPIO0 edge transitionDac0 through Dac1 - sets the DAC outputs. The range of this parameter is 0x0000 to 0x0FFF.7.4.7 Bank 0x06 - I/O SettingsBankLocationNameR/WSizeRange In BitsDefault0x060x00GpioDirR/W0x0160x00 (All inputs)0x060x01GpioInitR/W0x0160x00 (All zeros)0x060x02GpioAltR/W0x0160x000x060x03GpioEdgeTriggerR/W0x0180x010x060x04GpioSleepModeR/W0x0160x00 (Off)0x060x05GpioSleepDirR/W0x0160x00 (All inputs)0x060x06GpioSleepStateR/W0x0160x00 (All zero)0x060x07Dac0InitR/W0x02120x00000x060x09Dac1InitR/W0x02120x00000x060x0BAdcSampleIntvlR/W0x04320x0A (100 ms)0x060x0FAdc0ThresholdLoR/W0x02120xF8000x060x11Adc0ThresholdHiR/W0x02120x07FF0x060x13Adc1ThresholdLoR/W0x02120xF8000x060x15Adc1ThresholdHiR/W0x02120x07FF0x060x17Adc2ThresholdLoR/W0x02120xF8000x060x19Adc2ThresholdHiR/W0x02120x07FF0x060x1BIoReportTriggerR/W0x0180x01 (GPIO0)0x060x1CIoReportIntervalR/W0x043230000 (ms)0x060x20IoPreDelayR/W0x0188 (ms)0x060x21IoBindingEnableR/W0x0110 (Disabled)0x060x22DacReferenceR/W0x0120 (ADC_EXT_REF)0x060x23AdcReferenceR/W0x0120 (ADC_EXT_REF)0x060x24AdcAveSelectR/W0x0180x010x060x25ExtAdcScaleFactorR/W0x02160x80000x060x27ExtAdcOffsetR/W0x02160x00000x060x29ExtDacScaleFactorR/W0x02160x80000x060x2BExtDacOffsetR/W0x02160x00000x060x2DVccAdcScaleFactorR/W0x02160x80000x060x2FVccAdcOffsetR/W0x02160x00000x060x31VccDacScaleFactorR/W0x02160x80000x060x33VccDacOffsetR/W0x02160x00000x060x351VAdcScaleFactorR/W0x02160x80000x060x371VAdcOffsetR/W0x02160x00000x060x391VDacScaleFactorR/W0x02160x80000x060x3B1VDacOffsetR/W0x02160x00000x060x3DAdcDiffModeR/W0x0180 (single-ended)0x060x3EAdcGainCh0R/W0x0180 (gain = 1)
www.RFM.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@rfm.comPage 51 of 80DNT90 Integration Guide - 08/09/12BankLocationNameR/WSizeRange In BitsDefault0x060x3FAdcGainCh1R/W0x0180 (gain = 1)0x060x40AdcDiffScaleFactorCh0R/W0x02160x80000x060x42AdcDiffOffsetCh0R/W0x02160x00000x060x44AdcDiffScaleFactorCh1R/W0x02160x80000x060x46AdcDiffOffsetCh1R/W0x02160x00000x060x47FastAdcPrescalerR/W0x011 byte, range 1..75 (128)0x060x48SlowAdcPresccalerR/W0x011 byte, range 0..72 (16)0x060x49MaxQueuedEventsR/W0x011 byte, range 0..208 (reports)0x060x4AAdcSkipCountR/W0x011 byte0 (samples)Table 7.4.7.1GpioDir - this parameter is a bitmask that sets whether each GPIO is an input (0) or outputs (1). The de-fault is all inputs.GpioInit - this parameter is a bitmask that sets the initial value for any GPIOs which are enabled as out-puts. For GPIOs enabled as inputs, this sets the initial pull-up setting.GpioAlt - Specifies which GPIO pins will have their alternate functions enabled: Bit 2 - diversity toggle en-able, Bit 3 - RS485 enable, Bit 4 - /HOST_CTS enable, Bit5 - /HOST_RTS enable.BitAlternate FunctionDefaultBit Mask0(none)00x011(none)00x022Diversity Toggle00x043RS485 (N/A in SPI Slave mode)00x084/Host_CTS (N/A in SPI Slave mode)10x105/HOST_RTS (N/A in SPI Slave mode)10x20Table 7.4.7.2GpioEdgeTrigger -This parameter consists of a set of four 2-bit fields that define when GPIO triggers areenabled for I/O event reporting:bits 7..6 GPIO3 edge functionbits 5..4 GPIO2 edge functionbits 3..2 GPIO1 edge functionbits 1..0 GPIO0 edge functionThe bit values for each GPIO map to the following settings:ValueGPIO edge behavior11Rising edge trigger, neither level keeps remote awake10Bidirectional edge trigger, neither level keeps remote awake01Rising edge trigger, holding high keeps remote awake00Falling edge trigger, holding low keeps remote awakeTable 7.4.7.3GpioSleepMode - this parameter is a bitmask that enables configuring the I/O direction and state ofGPIO0..GPIO5 when the module is sleeping. Bits 0..5 correspond to GPIO0..GPIO5. Setting a Gpio-SleepMode bit to 1 enables sleep mode configuration of the corresponding GPIO. Setting a GpioSleep-Mode bit to 0 causes the corresponding GPIO to remain configured as in active mode. Note that when the
www.RFM.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@rfm.comPage 52 of 80DNT90 Integration Guide - 08/09/12GpioAlt bit is set for GPIO4, the corresponding GpioSleepMode bit is ignored and GPIO4 is controlleddirectly by the GpioSleepState parameter bit 7.GpioSleepDir - when GpioSleepMode is enabled, this parameter functions to set the direction of theGPIOs during a device’s sleep period. This enables the user to provide alternate configurations duringsleep that will help minimize current consumption. Bits 0..5 correspond to GPIO0..GPIO5. Setting aGpioSleepDir bit to 1 to specifies an output; 0 specifies an input.GpioSleepState - when GpioSleepMode is enabled, this parameter functions as a bitmask to control thestates of the GPIOs, the RADIO_TXD output, and the /HOST_CTS and /DCD outputs during a device’ssleep period. This allows the user to set alternate configurations during sleep to minimize current con-sumption. Bits 0..5 correspond to GPIO0..GPIO5 respectively. Bit 6 sets the state of RADIO_TXD, and bit7 sets the states of /HOST_CTS and /DCD. A sleep state bit is set to 1 to specify a high output or an in-ternal pull-up on an input, or to 0 to specify a low output or no internal pull-up on an input. Bit 6 must beset low in order to achieve minimum sleep current (high impedance load assumed), and the other bitsmay need to be set low or high depending on their external loads. When bit 6 is set low, expect a serial“break” condition to occur as the module wakes from sleep. The serial break condition can be eliminatedby setting bit 6 high, but sleep current will be increased.Dac0Init - this parameter sets the initial value for DAC0 at startup.Dac1Init - this parameter sets the initial value for DAC1 at startup.AdcSampleIntvl - this parameter sets the frequency (sample interval) of ADC measurements used to de-termine if a threshold has been exceeded or in calculating an average measurement value. The ADCchannels are read on each ADC cycle, along with the states of GPIO2 and GPIO3. Each AdcSampleIntvlcount equals 10 ms. The default is 100 ms. This interval will be the worst-case latency for ADC generatedinterrupts. Note that AdcSampleIntvl is independent of IoReportInterval as the ADCs are read on bothintervals.Adc0..2ThresholdLo/Hi - these parameters set the thresholds to trigger an I/O report based on ADCmeasurements. If I/O reporting is enabled, a single event report containing the contents of the I/O bank isgenerated when a threshold is crossed. Reporting is edge-triggered with respect to threshold boundaries,not level-triggered. Additional reports are not triggered unless the ADC measurement first returns insidethe threshold boundary and then crosses the threshold again. Triggers occur whenever one of the follow-ing inequalities is satisfied:ADCx< ADCx_ThresholdLoADCx> ADCx_ThresholdHiIoReportTrigger - a trigger event on any enabled trigger source will cause a DNT90E router or remote tosend an event message to the base containing the entire current values of the Bank 5.bit 7 ADC2 high/low thresholdsbit 6 ADC1 high/low thresholdsbit 5 ADC0 high/low thresholdsbit 4 Periodic timerbit 3 GPIO3 edgebit 2 GPIO2 edgebit 1 GPIO1 edgebit 0 GPIO0 edgeI/O reporting is supported for remotes and routers only, not the base.
www.RFM.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@rfm.comPage 53 of 80DNT90 Integration Guide - 08/09/12IoReportInterval - when periodic timer I/O reporting is enabled, this parameter sets the interval betweenreports. The parameter scaling is 10 ms/count, and the default report interval is every 30 seconds.IoPreDelay - this parameter sets the time in milliseconds to delay collection of ADC readings after a mod-ule wakeup event occurs, to allow settling of ADC input voltages.IoBindingEnable - this parameter enables I/O binding. Setting this parameter to 0x00 disables I/O binding(I/O mirroring) from a remote device. Setting this parameter 0x01 enables I/O mirroring. When enabled,the data from any received event report is used to drive the device’s own outputs. GPIO2 will be set to theevent report’s GPIO0 reading, GPIO3 will be set to the event report’s GPIO1 reading, and DAC0 andDAC1 will be set with the ADC0 and ADC1 readings respectively. Note that if the AdcDiffMode parameteris set to 1,I/O binding cannot be used.DacReference - this parameter selects the reference voltage for the DACs:Setting Reference0x00ADC_EXT_REF0x01AVVC (Analog Vcc)0x02Reserved0x03Disable DAC operationAdcReference - this parameter selects the reference voltage for the ADCs:Setting Reference0x00ADC_EXT_REF0x01Internal Vcc divided by 1.60x02Reserved0x03Disable ADC operationAdcAveSelect - this parameter selects the number of ADC measurements to average to produce eachADC reading, from 1 to 255 samples. Averaging over a larger number of measurements increases noisefiltering but also increases the time it takes to generate a set of readings:ADC ModeModule AwakeModule SleepingSingle-ended, reading all three channels216 µs381 µsDifferential, reading both channels160 µs273 µsTable 7.4.7.4ExtAdcScaleFactor - this parameter is the scale factor applied to an ADC measurement when the ADCreference is an external voltage. The scale factor parameter is multiplied by 32768. for example, the pa-rameter value for a scale factor of 1.12 = 1.12 * 32768 = 36700.16 or 0x8F5C.ExtAdcOffset - this parameter is the 2’s complement offset added to the scaled ADC measurement whenthe ADC reference is an external voltage.ExtDacScaleFactor - this parameter is the scale factor applied to a DAC measurement when the DACreference is an external voltage. The scale factor parameter is multiplied by 32768. for example, the pa-rameter value for a scale factor of 1.12 = 1.12 * 32768 = 36700.16 or 0x8F5C.ExtDacOffset - this parameter is 2’s complement the offset added to the scaled DAC measurement whenthe DAC reference is an external voltage.
www.RFM.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@rfm.comPage 54 of 80DNT90 Integration Guide - 08/09/12VccAdcScaleFactor - this parameter is the scale factor applied to an ADC measurement when the ADCreference is Vcc/1.6. The scale factor parameter is multiplied by 32768. for example, the parameter valuefor a scale factor of 1.12 = 1.12 * 32768 = 36700.16 or 0x8F5C.VccAdcOffset - this parameter is the 2’s complement offset added to the scaled ADC measurement whenthe ADC reference is derived from Vcc/1.6.VccDacScaleFactor - this parameter is the scale factor applied to a DAC measurement when the DACreference is Vcc. The scale factor parameter is multiplied by 32768. for example, the parameter value fora scale factor of 1.12 = 1.12 * 32768 = 36700.16 or 0x8F5C.VccDacOffset - this parameter is the 2’s complement offset added to the scaled DAC measurement whenthe DAC reference is Vcc.1VAdcScaleFactor - this parameter is the scale factor applied to an ADC measurement when the ADCreference is the 1 V internal reference. The scale factor parameter is multiplied by 32768. For example,the parameter value for a scale factor of 1.12 = 1.12 * 32768 = 36700.16 or 0x8F5C.1VAdcOffset - this parameter is the 2’s complement offset added to the scaled ADC measurement whenthe ADC reference is the 1 V internal reference.1VDacScaleFactor - this parameter is the scale factor applied to a DAC measurement when the DAC ref-erence is the 1 V internal reference. The scale factor parameter is multiplied by 32768. for example, theparameter value for a scale factor of 1.12 = 1.12 * 32768 = 36700.16 or 0x8F5C.1VDacOffset - this parameter is the 2’s complement offset added to the scaled DAC measurement whenthe DAC reference is the 1 V internal reference.AdcDiffMode - a parameter value of 0 selects single-ended ADC mode. In this mode, negative sensorinputs are connected to ground and positive sensor inputs to ADC0, ADC1 and ADC2 respectively. ThreeADC measurements are made in this mode with a range of 0x0000 to 0x07FF. A parameter value of 1selects signed differential mode with gain. In this mode, the negative sensor inputs are connected toADC0 and the positive inputs are connected to ADC1 and ADC2. Two ADC measurements are made inthis mode, ADC1 to ADC0 and ADC2 to ADC0, with a range (signed) from 0xF800 to 0x07FF. In differen-tial mode, the AdcGainCh0 and AdcGainCh1 parameters can change the selected gain for the two ADCreadings, and the AdcDiff scale factors and offsets, both supplied by the customer, are used.AdcGainCh0 - this parameter sets the preamplifier gain applied when making a differential measurementof ADC1 relative to ADC0. Setting this parameter to 0x00 sets the gain to 1, 0x01 sets the gain to 2, 0x02sets the gain to 4 and so on, up to 0x06 which sets the gain to 64. Note that the preamplifier output volt-age saturates at 2.4 V regardless of the gain setting.AdcGainCh1 - this parameter sets the gain applied when making a differential measurement of ADC2relative to ADC0. Setting this parameter to 0x00 sets the gain to 1, 0x01 sets the gain to 2, 0x02 sets thegain to 4 and so on, up to 0x06 which sets the gain to 64. Note that the preamplifier output voltage satu-rates at 2.4 V regardless of the gain setting.AdcDiffScaleFactorCh0/1 and AdcDiffOffsetCh0/1 - these parameters are applied to the raw ADC read-ings in differential mode. These values are not factory calibrated, but can be calibrated by the user.
www.RFM.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@rfm.comPage 55 of 80DNT90 Integration Guide - 08/09/12FastAdcPrescaler - this parameter is the system clock divisor used to generate the ADC clock when thesystem is being clocked at 16 MHz. Default value is 0x05 (system clock 128). Higher values corre-spond to slower ADC clock rates. For example, 0x07 = 512, and 0x00 = 4. Note that larger prescalerswill increase the amount of time it takes to collect all readings. DIV4 is not valid when running at 16 MHzbecause the maximum ADC clock rate is 2 MHz, so DIV8 is the lowest allowed.SlowAdcPrescaler - System clock divisor used to generate the ADC clock when the system is beingclocked at 2 MHz, when exiting sleep mode. Default value is 0x02 (system clock 16). Higher values cor-respond to slower ADC clock rates. For example, 0x07 = DIV512, and 0x00 = DIV4.MaxQueuedEvents - this parameter sets the maximum number of Event Reports that can be queued atone time by a DNT90E. This parameter is used to prevent a router device from clogging up its outboundqueue with its own pending transmissions if it has having trouble obtaining link or an available slot from itsparent. This parameter defaults to 8, with a maximum value of 20.AdcSkipCount - this parameter sets the number of measurements to skip (discard) when switching to anew ADC channel. The skipped measurements allow transients in the ADC sample-and-hold circuit tosettle out. This parameter must be set to at least 0x03 when AdcDiffMode is selected. Note that theIoPreDelay parameter discussed above provides a delay to allow signals external to the DNT90E to settlefollowing a wake up event, while AdcSkipCount skips measurements that may be distorted because theinternal voltage on the ADC sample-and-hold has not settled.7.4.8 Bank 0xFF - Special FunctionsBankLocationNameR/WSizeRangeDefault0xFF0x00UcResetW0x010..2N/A0xFF0x01MemorySaveW0x010xD0..0xD2N/A0xFF0x04DiagSerialRateR/W0x010..107 (38400 kbps)0xFF0x0CForceDiscoverW0x03(See Text)N/A0xFF0x0EDiagPortEnR/W0x010..10 (disabled)Table 7.4.8.1UcReset - writing a 0 to this parameter initiates a full reset, writing 1 to initiates a reset to the serial boot-loader, or writing a 2 to initiates a reset to the OTA bootloader client.MemorySave - writing 0xD0 to this parameter load default values, writing 0xD1 saves settings toEEPROM, or writing 0xD2 to save settings to EEPROM and resets the module.DiagSerialRate - this parameter sets the diagnostic port serial data rate as shown below:Setting Serial rate0x001.2 kbps0x012.4 kbps0x024.8 kbps0x039.6 kbps0x0414.4 kbps0x0519.2 kbps0x0628.8 kbps0x0738.4 kbps (default)
www.RFM.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@rfm.comPage 56 of 80DNT90 Integration Guide - 08/09/120x0857.6 kbps0x09115.2 kbps0x0A230.4 kbps0x0B250.0 kbpsForceDiscoverRegister - a write to this register, typically using a broadcasted Set Remote Register com-mand, will force a heartbeat reply if a device's parent has the specified base-mode network ID (or 0xFFwildcard), and the least significant byte of the device’s MAC address is within a specified min/max range.The payload consists of 3 bytes: NWKID (NN), minimum MAC address (LL), and maximum MAC address(XX). In Little Endian hexadecimal format this would appear as “XXLLNN”.DiagPortEn - setting this parameter to 0x01 enables diagnostic port operation.7.5 Protocol-formatted Message Examples7.5.1 Data MessageIn this example, the ASCII text “Hello” is sent from the base to a remote using the TxData command.The MAC address of the remote is 0x123456. The protocol formatting for the host message is:SOPLengthPktTypeLo MACMACHi MAC“H”“e”“l”“l”“o”0xFB0x090x050x560x340x120x480x650x6C0x6C0x6FThere are 9 bytes following the length byte, so the length byte is set to 0x09. Note that the 0x123456network address is entered in Little-Endian byte order, 56 34 12. When an ACK to this message is re-ceived from the remote, the base outputs a TxDataReply message to its host:SOPLengthPktTypeLo MACMACHi MACStatusRSSI0xFB0x070x150x560x340x120x000xB0The 0x00 TxStatus byte value indicates the ACK reception from the remote. The RSSI value of the re-ceived ACK is 0xB0, indicating a received signal strength of approximately -80 dBm .The ASCII “Hello” message is output at the remote as a 0x26 RxData event. The address field containsthe originator’s address, 0x00 0x00 0x00, which is the base. The RSSI value of the received message is0xB4, indicating a received signal strength of approximately -76 dBm. The data following the RSSI valueis the “Hello” text.SOPLengthPktTypeLo MACMACHi MACRSSI“H”“e”“l”“l”“o”0xFB0x0A0x260x000x000x000x350x480x650x6C0x6C0x6FNote that if the remote was in transparent mode, only the “Hello” text would be output.
www.RFM.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@rfm.comPage 57 of 80DNT90 Integration Guide - 08/09/127.5.2 Configuration MessagesIn this example, the remote with MAC address 0x123456 is configured by the base (MAC address0x000000) to generate RxEvent messages every 10 seconds. To do this, the IoReportInterval in the re-mote is set to 10 seconds and the periodic report timer bit in the IoReportTrigger parameter is set ON.The IoReportInterval and the IoReportTrigger parameters are loaded using SetRemoteRegister com-mands. The command to set the IoReportInterval to 10 seconds is:SOPLengthPktTypeLo MACMACHi MACRegBankSizeLo ValValValHi Val0xFB0x0B0x070x560x340x120x1C0x060x040x100x270x000x00The IoReportInterval parameter starts in location 0x1C of Bank 6. The report interval scaling is1 ms/count, so a 10 second report interval is 10,000 units or 0x00002710 (Little-Endian format 10 27 0000). The IoReportInterval parameter is updated and SetRemoteRegisterReply is returned:SOPLengthPktTypeStatusLo MACMACHi MACRSSI0xFB0x060x170x000x000x000x000xB2The command to set the periodic report timer bit in IoReportTrigger is:SOPLengthPktTypeLo MacMACHi MACRegBankSizeVal0xFB0x080x070x560x340x120x1B0x060x010x10The IoReportTrigger parameter is in location 0x1B of Bank 6. The periodic report timer bit in IoReport-Trigger is located in bit position four (00010000b) or 0x10. The IoReportTrigger parameter is updated andSetRemoteRegisterReply is returned:SOPLengthPktTypeStatusLo MACMACHi MACRSSI0xFB0x060x170x000x000x000x000xB47.5.3 Sensor MessageIn this example, the base host requests an ADC1 reading from a remote using the GetRemoteRegistercommand, type 0x06. The MAC address of the remote is 0x123456. The current ADC1 measurementparameter is read starting at register location 0x15 and Bank 5. The ADC reading spans two bytes. Theprotocol formatting for this command is:SOPLengthPktTypeLo MacMACHi MACRegBankSize0xFB0x070x060x560x340x120x150x050x02Note the remote MAC address is entered in Little-Endian byte order, 56 34 12.The ADC reading is returned in a GetRemoteRegisterReply message:Substantial information is returned in the message. The last two byes of the message give the ADC read-ing in Little-Endian format, 7B 08. The ADC reading is thus 0x087B (2171). The RSSI value is the byteSOPLengthPktTypeStatusLo MACMACHi MACRSSIRegBankSizeLo ValHi Val0xFB0x0B0x160x000x000x000x000xB70x1C0x060x020x7B0x08
www.RFM.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@rfm.comPage 58 of 80DNT90 Integration Guide - 08/09/12following the address, 0xB7 (-73 dBm). The TxStatus byte to the right of the GetRemoteRegisterReplyPacket Type is 0x00, showing the packet was acknowledged on the RF channel.7.5.4 Event MessageThe configuration example shown in Section 7.5.2 above causes the remote with MAC address 0x123456to start sending event messages every 10 seconds as shown in the log below:FB1228563412B8007A013601FF01100020014001FB1228563412B00079013501C001100020014001FB1228563412A90072013501D301100020014001FB1228563412AC0075013601E701100020014001The first received message in the above log is constructed as follows:SOPLengthPktTypeAddrAddrAddrRSSIData0xFB0x120x280x560x340x12B8GPIOADC0ADC1ADC2Event FlagsDAC0DAC10x000x7A0x010x360x01FF0x010x100x000x200x010x400x01RxEvent messages are PktType 0x28. The message payload consists of the states of GPIO0 throughGPIO5, the input voltages measured by ADC0 through ADC2, the event trigger(s), and the DAC outputsettings. Note the ADC readings, event flags and DAC settings are presented in Little-Endian order. Theremote is assumed to be always ON in this example. If the remote is placed in periodic sleep mode(SleepMode = 1), a suitable value of the WakeResponseTime parameter should be set to allow the baseapplication to analyze the I/O report and send back a command to the remote as needed.
www.RFM.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@rfm.comPage 59 of 80DNT90 Integration Guide - 08/09/128.0 DNT90EDK Developer’s KitFigure 8.0.1 shows the main contents of a DNT90EDK Developer’s kit:Figure 8.0.18.1 DNT90EDK Kit ContentsTwo DNT90EP radios installed in DNT90E interface boards (labeled Base and Remote)Two 9 V wall-plug power suppliers, 120/240 VAC, plus two 9 V batteries (not show above)Two RJ-45/DB-9F cable assemblies and two A/B USB cablesTwo installed U.FL coaxial jumper cablesTwo 2 dBi dipole antennas with two MMCX-to-RSMA coaxial adaptor cablesOne DNT90EDK documentation and software CD8.2 Additional Items NeededTo operate the kit, the following additional item is needed:One PC with Microsoft Windows XP, Vista or Windows 7 operating system. The PC must beequipped with a USB port or a serial port capable of operation at 9600 bps.8.3 Developer’s Kit Default Operating ConfigurationThe default operating configuration of the DNT90EDK developer’s kit is point-to-point with transparentseri- al data at 9600 bps, 8N1. One DNT90EP is preconfigured as a base and the other as a remote.Labels on the bottom of the interface boards specify Base or Remote. The defaults can be overridden totest other operating configurations using the DNT90E Demo utility discussed in Section 8.5.
www.RFM.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@rfm.comPage 60 of 80DNT90 Integration Guide - 08/09/128.4 Developer’s Kit Hardware AssemblyObserve ESD precautions when handling the kit circuit boards. When shipped, the DNT90EP radios andU.FL coax jumper cables are installed in the interface boards, as shown in Figure 8.4.1. If a DNT90EP ra-dio and/or the U.FL jumper cable has been unplugged after receipt, confirm the DNT90EP is correctlyplugged into its interface board with the radio oriented so that its U.FL connector is next to the U.FL con-nector on the interface board, as shown in Figure 8.4.2. Also check the radio’s alignment in the socket onthe interface board. No pins should be hanging out over the ends of the connector. Next, screw each di-pole antenna into and adaptor cable and “snap” the other end of the adaptor cable into the MMCX RFconnector on the development board as shown in Figure 8.4.2.Figure 8.4.1 Figure 8.4.2As shown in Figure 8.4.3, confirm there is a jumper on J10 (this jumper can be removed later and acurrent meter connected across J10 to measure just the DNT90E’s current consumption duringoperation). Note: DNT90P is shown, DNT90PE application is identical.Figure 8.4.3J P1 0
www.RFM.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@rfm.comPage 61 of 80DNT90 Integration Guide - 08/09/12There are three serial connectors and a power connector on the end of each interface board, as shown inFigure 8.4.4. The RJ-45 connector provides an RS232 interface to the DNT90EP’s main serial port. TheUSB connector provides an optional interface to the radio’s main serial port. The RJ-11 connector pro-vides an RS232 interface to the radio’s optional diagnostic port. The DNT90E Demo utility program runson the radio’s main port.Figure 8.4.4Many desktop PCs have a built-in serial port capable of operation at 9600 bps. The kit can be run satis-factorily at the 9600 bps data rate, but not at its fastest throughput. Use the RJ-45 to DB-9F cable as-semblies for serial port operation.Optionally, the kit development boards can be run from USB ports. Plugging in the USB cable automati-cally switches operation from the RJ-45 connector. The USB interface is based on an FT232RL serial-to-USB converter IC manufactured by FTDI. The FT232RL driver files are located in the i386 and AMD64folders on the kit CD, and the latest version of the drivers can downloaded from the FTDI website,www.ftdichip.com. The drivers create a virtual COM port on the PC. Power the Base using one of thesupplied wall-plug power supplies. Next connect the Base to the PC with a USB cable. The PC will findthe new USB hardware and open a driver installation dialog box. Enter the letter of the drive holding thekit CD and click Continue. The installation dialog will run twice to complete the FT232R driver installation.8.5 DNT90E Utility ProgramThe DNT90E utility program requires only one PC for initial kit operation and sensor applications (ADC,DAC and digital I/O). Two serial/USB ports are required for bidirectional serial communications. Section8.6 below covers using the DNT90E Demo utility program for initial kit operation and familiarization. Section8.6.1 covers serial message communication and radio configuration.
www.RFM.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@rfm.comPage 62 of 80DNT90 Integration Guide - 08/09/128.6 Initial Kit OperationCreate a file folder on the PC and copy the contents of the kit CD into the folder.Connect the Base to the PC and power up the Base using a wall-plug power supply.The DNT90E Demo utility program is located in the PC Programs folder. The DNT90E Demo utility programrequires no installation and can be simply copied to the PC and run. Start the utility program on the PC.The start-up window is shown in Figure 8.6.1.Figure 8.6.1
www.RFM.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@rfm.comPage 63 of 80DNT90 Integration Guide - 08/09/12Click on Connect to open the Select Comm Port Settings dialog box, as shown in Figure 8.6.2. Ifnecessary, set the baud rate to 9600 bps. Set the CommPort to match the serial port connected to theBase, either the hardware port or the USB virtual serial port. Then click OK to activate the serialconnection.Figure 8.6.2At this point the utility program will collect data from the Base, filling in the Local Radio column as shownin Figure 8.6.3. Next, power-up the Remote using a wall-plug power supply. The Remote will transmit a“heartbeat” message on power up as shown in the Status Window. Click on the drop-down box at the topof the Radio 1 column and load the MAC Address for the Remote from the heartbeat message. Nextpress the Start button using the default 1 second Refresh Delay.Figure 8.6.3
www.RFM.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@rfm.comPage 64 of 80DNT90 Integration Guide - 08/09/12The utility program will display updated data on the Remote in the Radio 1 column, including bar graphsof RSSI signal strength in dBm and percent packet success rate, as shown in Figure 8.6.4. Adjusting thelarge pot on the Remote can be observed on the Potentiometer (ADC0) row.Figure 8.6.4Note: If the Remote is powered up before the DNT90E Demo program is running and connected to theBase, the initial Remote heartbeat will be missed and it will be necessary to manually enter the Remote’sMAC address in the MAC Address field under Radio 1 and then press the Enter key to display the Re-mote information.If any difficulty is encountered in setting up the DNT90EDK development kit, contact MURATA’s moduletech- nical support group. The phone number is +1.678.684.2000. Phone support is available from 8:30AM to 5:30 PM US Eastern Time Zone, Monday through Friday. The E-mail address istech_sup@Murata.com.
www.RFM.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@rfm.comPage 65 of 80DNT90 Integration Guide - 08/09/128.6.1 Serial Communication and Radio ConfigurationConnect PCs to both the Base and the Remote for serial communication testing (alternately one PC canbe used with two serial ports and two instances of the DNT90E Demo program running). Click the Stopbutton under the Refresh Delay label on the I/O Tools tab and move to the Transmit Tools tab, as shownin Figure 8.6.1.1.Figure 8.6.1.1Pressing the Transmit button on this screen sends the message in the Data to Transmit text box to theselected MAC Address. Note that the MAC address a remote uses for the base is 0x000000. Data sent tothe local radio is displayed in the Received Data text box. Received data can be displayed as ASCII(default) or in Hexadecimal format by checking the Hex Mode check box. When the Transmit Interval isset to zero, Data to Transmit is sent once when the Transmit button is clicked. When the Transmit Intervalis set to a positive number, Pressing the Transmit button once will cause a transmission each transmitinterval (seconds) until the button is pressed again.
www.RFM.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@rfm.comPage 66 of 80DNT90 Integration Guide - 08/09/12Returning to the I/O Tools tab, the multi-tab Configuration window for each radio can be accessed byclicking on its Config button. The data presented on the first six tabs corresponds to configuration registerBanks 0 through 5 as discussed in Section 4.2 above, with the data on the next two tabs corresponding toconfiguration register Bank 6.Figure 8.6.1.2The Transceiver Setup Tab is shown in Figure 8.6.1.2 and corresponds to Bank 0. The current values ofeach Bank 0 parameter are displayed and can be updated by selecting from the drop-down menus orentering data from the keyboard, and then pressing the Apply Changes button. Note that data isdisplayed and entered in Big-Endian order. The utility program automatically reorders multi-byte data toand from Little-Endian order when building or interpreting messages.
www.RFM.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@rfm.comPage 67 of 80DNT90 Integration Guide - 08/09/12Figure 8.6.1.3Figure 8.6.1.3 shows the System tab contents, corresponding to Bank 1. The current values of each pa-rameter are displayed and can be updated by selecting from the drop-down menu or entering data fromthe keyboard, and then pressing the Apply Changes button. Note that Bank 1 holds configuration parame-ters for the base only except for Broadcast Mode, which applies to both the base and the remotes.Figure 8.6.1.4Figure 8.6.1.5 shows the Status tab contents, corresponding to Bank 2. Note the Status tab containsread-only parameters.
www.RFM.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@rfm.comPage 68 of 80DNT90 Integration Guide - 08/09/12Figure 8.6.1.5Figure 8.6.1.5 shows the Serial tab contents corresponding to the serial parameters in Bank 3. The val-ues shown are the defaults for serial port operation.Figure 8.6.1.6Figure 8.6.1.6 shows the Protocol tab contents, corresponding to Bank 4. Transparent serial data com-munication is currently chosen.
www.RFM.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@rfm.comPage 69 of 80DNT90 Integration Guide - 08/09/12Figure 8.6.1.7Figure 8.6.1.7 shows the I/O Parameters tab contents, corresponding to Bank 5. All GPIO ports are con-figured as inputs. The 12-bit ADC input readings and DAC output settings are given in Big-Endian byteorder. Event flags are presented on the right side of the window.Figure 8.6.1.8Figure 8.6.1.8 shows the first I/O Settings tab contents, corresponding to Bank 6 GPIO configurationsother than alternate GPIO functions. This tab allows the direction of the GPIO ports to be set both for ac-tive and sleep modes, and in the case of GPIO outputs, the initial power up states and sleep mode statesto be set. When GPIO ports 0 - 3 are configured as inputs, event interrupts can be set for them with checkboxes. The type of interrupt trigger is selected from the drop-down boxes to the right of the check boxes.Periodic I/O reporting, reporting interval and enable/disable sleep I/O states and I/O binding can also beconfigured under this tab.
www.RFM.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@rfm.comPage 70 of 80DNT90 Integration Guide - 08/09/12Figure 8.6.1.9Figure 8.6.1.9 shows the second I/O Setup tab contents, corresponding to Bank 6 ADC input and DACoutput parameters. The ADC and DAC reference voltages, the ADC sampling interval, the high and lowADC thresholds for event reporting and event reporting triggers on each ADC channel can be set, alongwith the initial output values for each DAC channel. The event reporting I/O predelay and alternate GPIOfunctions can also be set from this tab.The DNT90E Demo Utility File,Options and Help menus are shown in Figure 8.7.8.Figure 8.7.8
www.RFM.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@rfm.comPage 71 of 80DNT90 Integration Guide - 08/09/128.7 DNT90E Interface Board FeaturesThe locations of the LEDs on the interface board that are used by the DNT90E are shown in Figure 8.8.1.Figure 8.8.1DCD LED, D11, illuminates on a router or remote to indicate it is registered with its parent and can partic-ipate in RF communications. The DCD LED illuminates on the base when one or more routers or remotesare registered to it, unless the base has been configured to assert DCD on power up. In this case it will beon as long as the development board is powered. Activity LED, D10, illuminates when transmitting or re-ceiving RF data. Power LED, D1, illuminates when the DNT90E and its interface board are powered.GPIO2 LED, D5, and GPIO3 LED, D4, can be controlled by configuring GPIO2 and GPIO3 as outputs onthe DNT90E. These LEDs are illuminated with a logic high signal.Figure 8.8.2Figure 8.8.2 shows the connectors and switches to the right of the DNT90EP mounting socket. Note:DNT90P is shown, DNT90PE application is identical. JP3 and JP4 normally have shorting plugsinstalled as shown in Figure 8.8.2. JP3 connects ADC0 to the yellow potentiometer. Clockwise rotationof the potentiometer increases the voltage. JP4 connects ADC1 to a thermistor temperature sensor.The DNT90E has its own boot loader utility that allows the protocol firm-
www.RFM.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@rfm.comPage 72 of 80DNT90 Integration Guide - 08/09/12ware to be installed with a terminal program that supports YMODEM. The boot loader is activated with ashorting plug on JP13. Pin strip J6 provides access to various DNT90E pins as shown on the silkscreen.Pressing switch SW3 will reset the DNT90EP. Switch S4 is not used with the DNT90E.Figure 8.8.3Figure 8.8.3 shows the connectors to the left of the DNT90EP mounting socket. Pressing switch SW1switches GPIO0 from logic high to low, and pressing SW2 switches GPIO1 from logic high to low. TheDNT90EP interface board includes a 5 V regulator to regulate the input from the 9 V wall-plug power sup-ply. Do not attempt to use the 9 V wall-plug power supply to power the DNT90EP directly. The maximumallowed voltage input to the DNT90EP is 5.5 V.
www.RFM.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@rfm.comPage 73 of 80DNT90 Integration Guide - 08/09/129.0 TroubleshootingDNT90E not responding - make sure /RESET is not asserted (logic low). Make sure the host serial portsettings match the DNT90E serial port settings.Can not enter protocol mode - make sure the host data rate is correct. The DNT90E defaults to 9.6 kbps.If using the EnterProtocolMode command, send the complete protocol format for this command.A remote never detects carrier (DCD) - check that the base is running, and that the remote’s Sys-temNwkID is the same as the base, and that the ParentNwkID parameter is the same as the base, or isset to 0xFF. Also make sure that the security keys are the same.Carrier is detected, but no data appears to be received - if /HOST_RTS is enabled, make sure it is as-serted (logic low) to enable character flow from the DNT90E.Range is extremely limited - this is usually a sign of a poor antenna connection or the wrong antenna.Check that the antenna is firmly connected. If possible, remove any obstructions near the antenna.9.1 Diagnostic Port CommandsThe diagnostic port shares its RX and TX signal lines with the Activity and DCD indications, respectively.Consequently, the debug port feature must be enabled before being used (Bank 0xFF). The change mustbe saved and the module then needs to be reset for this to take effect. The diagnostic port is defaulted to38.4 kbps, 8N1.The diagnostic port supports the following user commands:rbr <bank> <reg> <span> - read a parameter register’s value from the module.rbw <bank> <reg> <span> <value> [<value> <value>] - write a parameter register’s valuewith a span of up to 3 bytesstat <option> - option = 0 is off, option = 1 displays DataTx/AckRx for a hopsequence in time order, and option = 2 displays any packet RX or packet error for a hopsequence in frequency order.base <0 or 1> - For a router, this determines whether the stat option displays dataassociated with its operation as a base (1) or as a remote (0).
www.RFM.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@rfm.comPage 74 of 80DNT90 Integration Guide - 08/09/1210.0 Appendices10.1 Ordering InformationDNT90EC: transceiver module for solder-pad mountingDNT90EP: transceiver module for pin-socket mounting10.2 Technical SupportFor DNT90E technical support call MURATA at (678) 684-2000 between the hours of 8:30 AM and 5:30PM Eastern Time
www.RFM.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@rfm.comPage 75 of 80DNT90 Integration Guide - 08/09/1210.3 DNT90E Mechanical SpecificationsD N T 9 0 C O u t l i n e a n d M o u n t i n g Di m e n s i o n s1 . 4 5 0( 3 6 . 8 )1 50 . 0 5 0 ( 1 . 2 7 )1T o p V i e w0 . 9 8 0( 2 7 . 9 )1 6 3 00 . 1 2 5( 3 . 1 8 )0 . 4 5 0 ( 1 1 . 4 ) 0 . 3 0 0( 7 . 6 2 )0 . 0 9 0D i m e n s i o n s i n i n c h e s ( m m )Figure 10.3.1D N T 9 0 C S o l d e r P a d D i m e n s io n sD i m e n s i o n s i n i n c h e s ( m m )Figure 10.3.21 . 4 5 0( 3 6 . 8 )0 . 0 5 0( 1 . 2 7 )0 . 0 6 0( 1 . 5 2)150 . 0 3 5( 0 . 8 9 )1T o pV i ew0 . 9 8 01 . 0 4 0( 2 4 . 9 )( 2 6 . 4 )1630
www.RFM.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@rfm.comPage 76 of 80DNT90 Integration Guide - 08/09/120 . 10 0( 2 .5 4)0 . 05 0( 1 .2 7)0 . 80 0( 20 . 3)C o n n e c t o r sa r e S A M T E CS L M - 1 1 5 - 0 1- G - So r E q u i v a l en t0 .7 00( 17 .80 . 98 0( 24 . 9)D N T 9 0 P O u t l i n e a n d M o u n t i n g D i m en s i o n s0 . 0 6 0( 1 . 5 2 )1 . 4 5 0( 3 6 . 8 )0 . 0 5 0 ( 1 . 2 7 )0 . 9 8 0( 2 4 . 9 ) 1 . 1 0 0( 2 7 . 9 )0 . 4 5 0 ( 1 1 . 4 ) 0 . 3 0 0 ( 7 . 6 2 )D i m e n s i o n s i n i n c h e s ( m m )Figure 10.3.3D N T 9 0 P I n t e r fa c e C o n n e c t o rP C B L a y o u t D et a i l)D i m e n s i o n s a r e i n i n c h e s ( m m )Figure 10.3.40 . 12 5( 3 .1 8)0 . 09 0( 2 .2 9)0 . 22 5( 5 .7 2)3016115T o pV i ew
www.RFM.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@rfm.comPage 77 of 80DNT90 Integration Guide - 08/09/1210.4 DNT90E Development Board Schematic
www.RFM.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@rfm.comPage 78 of 80DNT90 Integration Guide - 08/09/12
www.RFM.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@rfm.comPage 79 of 80DNT90 Integration Guide - 08/09/12
www.RFM.com© 2010-2012 by RF Monolithics, Inc.Technical support +1.678.684.2000E-mail: tech_sup@rfm.comPage 80 of 80DNT90 Integration Guide - 08/09/1211.0 WarrantySeller warrants solely to Buyer that the goods delivered hereunder shall be free from defects in materialsand workmanship, when given normal, proper and intended usage, for twelve (12) months from the dateof delivery to Buyer. Seller agrees to repair or replace at its option and without cost to Buyer all defectivegoods sold hereunder, provided that Buyer has given Seller written notice of such warranty claim withinsuch warranty period. All goods returned to Seller for repair or replacement must be sent freight prepaidto Seller’s plant, provided that Buyer first obtain from Seller a Return Goods Authorization before anysuch return. Seller shall have no obligation to make repairs or replacements which are required by normalwear and tear, or which result, in whole or in part, from catastrophe, fault or negligence of Buyer, or fromimproper or unauthorized use of the goods, or use of the goods in a manner for which they are not de-signed, or by causes external to the goods such as, but not limited to, power failure. No suit or action shallbe brought against Seller more than twelve (12) months after the related cause of action has oc-curred. Buyer has not relied and shall not rely on any oral representation regarding the goods sold here-under, and any oral representation shall not bind Seller and shall not be a part of any warranty.THE PROVISIONS OF THE FOREGOING WARRANTY ARE IN LIEU OF ANY OTHER WARRANTY,WHETHER EXPRESS OR IMPLIED, WRITTEN OR ORAL (INCLUDING ANY WARRANTY OR MER-CHANT ABILITY OR FITNESS FOR A PARTICULAR PURPOSE). SELLER’S LIABILITY ARISINGOUT OF THE MANUFACTURE, SALE OR SUPPLYING OF THE GOODS OR THEIR USE OR DISPO-SITION, WHETHER BASED UPON WARRANTY, CONTRACT, TORT OR OTHERWISE, SHALL NOTEXCEED THE ACTUAL PURCHASE PRICE PAID BY BUYER FOR THE GOODS. IN NO EVENTSHALL SELLER BE LIABLE TO BUYER OR ANY OTHER PERSON OR ENTITY FOR SPECIAL, IN-CIDENTAL OR CONSEQUENTIAL DAMAGES, INCLUDING, BUT NOT LIMITED TO, LOSS OF PROF-ITS, LOSS OF DATA OR LOSS OF USE DAMAGES ARISING OUT OF THE MANUFACTURE, SALEOR SUPPLYING OF THE GOODS. THE FOREGOING WARRANTY EXTENDS TO BUYER ONLY ANDSHALL NOT BE APPLICABLE TO ANY OTHER PERSON OR ENTITY INCLUDING, WITHOUT LIMI-TATION, CUSTOMERS OF BUYERS.Part # M-0090-0002, Rev H

Navigation menu