Murata Electronics North America DNT24 Spread Spectrum Wireless Transceiver User Manual Rev 2

Murata Electronics North America Spread Spectrum Wireless Transceiver Users Manual Rev 2

Contents

Users Manual Rev 2

www.Murata.com Technical support +1.678.684.2000 Page 1 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/15DNT24 Series2.4 GHz Spread SpectrumWireless TransceiversIntegration Guide
www.Murata.com Technical support +1.678.684.2000 Page 2 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/15Important Regulatory InformationRFM Product FCC ID: HSW-DNT24IC 4492A-DNT24Note: This equipment has been tested and found to comply with the limits for a Class B digit aldevice, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable pro-tection against harmful interference in a residential installation. This equipment generates, usesand can radiate radio frequency energy and, if not installed and used in accordance with the in-structions, may cause harmful interference to radio communications. If this equipment doescause harmful interference to radio or television reception, which can be determined by turningthe equipment off and on, the user is encouraged to try to correct the interference by one or moreof 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.FCC Antenna Gain Restriction:The DNT24 has been designed to operate with any dipole antenna of up to 12 dBi of gain, any patch an-tenna of up to 12 dBi gain, or any chip antenna of up to 1.7 dBi gain. The antenna(s) used for this trans-mitter must be installed to provide a separation distance of at least 20 cm from all persons and must notbe co-located or operating in conjunction with any other antenna or transmitter.IC RSS-210 Detachable Antenna Gain Restriction:This radio transmitter, IC 4492A-DNT24, has been approved by the Industry Canada to operate with theantenna types listed below with the maximum permissible gain and the required antenna impedance foreach antenna type indicated. Antenna types not included in this list, having a gain greater than the maxi-mum gain indicated for that type, are strictly prohibited for use with this device.Le présent émetteur radio IC 4492A-DNT24 a été approuvé par Industrie Canada pour fonctionneravec les types d'antenne énumérés ci-dessous et ayant un gain admissible maximal et l'impédance req-uise pour chaque type d'antenne. Les types d'antenne non inclus dans cette liste, ou dont le gain est su-périeur au gain maximal indiqué, sont strictement interdits pour l'exploitation de l'émetteur.TypeModel NumberGainImpedanceOmnidirectionalOD12-240012 dBi50 ohmPatchPA241212 dBi50 ohmChipFR05-S1-N-0-1021.7 dBi50 ohm
www.Murata.com Technical support +1.678.684.2000 Page 3 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/15Under Industry Canada regulations, this radio transmitter may only operate using an antenna of a typeand maximum (or lesser) gain approved for the transmitter by Industry Canada. To reduce potential radiointerference to other users, the antenna type and its gain should be so chosen that the equivalent isotrop-ically radiated power (e.i.r.p.) is not more than that permitted for successful communication.Conformément à la réglementation d'Industrie Canada, le présent émetteur radio peut fonctionneravec une antenne d'un type et d'un gain maximal (ou inférieur) approuvé pour l'émetteur par IndustrieCanada. Dans le but de réduire les risques de brouillage radioélectrique à l'intention des autres utilis-ateurs, il faut choisir le type d'antenne et son gain de sorte que la puissance isotrope rayonnée équivalen-te (p.i.r.e.) ne dépasse pas l'intensité nécessaire à l'établissement d'une communication satisfaisante.This device complies with Industry Canada licence-exempt RSS standard(s). Operation is subject to thefollowing two conditions: (1) this device may not cause interference, and (2) this device must accept anyinterference, including interference that may cause undesired operation of the device.Le présent appareil est conforme aux CNR d'Industrie Canada applicables aux appareils radio exemptsde licence. L'exploitation est autorisée aux deux conditions suivantes : (1) l'appareil ne doit pas produirede brouillage, et (2) l'utilisateur de l'appareil doit accepter tout brouillage radioélectrique subi, même si lebrouillage est susceptible d'en compromettre le fonctionnement.See Section 6.8 of this manual for regulatory notices and labeling requirements. Changes or modifica-tions to a DNT24 not expressly approved by RFM may void the user’s authority to operate the module.
www.Murata.com Technical support +1.678.684.2000 Page 4 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/15Table of Contents1.0 DNT24 Introduction .......................................................................................................................... 61.1 Why Spread Spectrum? ............................................................................................................ 61.2 Frequency Hopping versus Direct Sequence............................................................................ 72.0 DNT24 System Overview................................................................................................................. 82.1 Point-to-Point Systems.............................................................................................................. 82.2 Point-to-Multipoint Systems....................................................................................................... 92.3 Store-and-Forward Systems...................................................................................................... 92.4 RF Channel Access................................................................................................................. 102.5 DNT24 Addressing .................................................................................................................. 112.6 Network Linking and Slot Registration .................................................................................... 112.6.1 Fast Linking Techniques ................................................................................................... 122.7 Transparent and Protocol-formatted Serial Data..................................................................... 123.0 DNT24 Application Interfaces ........................................................................................................ 133.1 Serial Ports .............................................................................................................................. 133.2 SPI Port ................................................................................................................................... 133.3 Digital I/O ................................................................................................................................. 163.4 Analog I/O................................................................................................................................ 163.5 I/O Event Reporting and I/O Binding ....................................................................................... 174.0 DNT24 System Configuration ........................................................................................................ 174.1 Configuration Parameters........................................................................................................ 174.2 Configuring a Basic Point-to-Point System ............................................................................. 184.3 Configuring a Basic Point-to-Multipoint System ...................................................................... 184.4 Configuring a Customized Point-to-Point or Point-to-Multipoint System................................. 184.5 Configuring a Store-and-Forward System............................................................................... 204.6 Slot Buffer Sizes, Number of Slots, Messages per Hop and Hop Duration ............................ 215.0 DNT24 Application Interface Configuration.................................................................................... 235.1 Configuring the Serial Port ...................................................................................................... 235.2 Configuring the SPI Port.......................................................................................................... 235.3 Configuring Digital I/O ............................................................................................................. 235.4 Configuring Analog I/O ............................................................................................................ 235.5 Configuring I/O Event Reporting and I/O Binding.................................................................... 245.6 Configuring Sleep Mode .......................................................................................................... 256.0 DNT24 Hardware ........................................................................................................................... 276.1 Electrical Specifications........................................................................................................... 286.2 Module Pin Out........................................................................................................................ 296.3 Antenna Connector.................................................................................................................. 306.4 Power Supply and Input Voltages ........................................................................................... 316.5 ESD and Transient Protection................................................................................................. 316.6 Interfacing to 5 V Logic Systems............................................................................................. 316.7 Mounting and Enclosures ........................................................................................................ 316.8 Labeling and Notices ............................................................................................................... 327.0 DNT24 Protocol-formatted Messages............................................................................................ 337.1 Protocol Formats ..................................................................................................................... 337.2 Message Types ....................................................................................................................... 337.3 Message Format Details.......................................................................................................... 34
www.Murata.com Technical support +1.678.684.2000 Page 5 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/157.4 Configuration Parameter Registers ......................................................................................... 417.4.1 Bank 0x00 - Transceiver Setup......................................................................................... 417.4.2 Bank 0x01 - System Settings............................................................................................ 447.4.3 Bank 0x02 - Status Parameters ........................................................................................ 467.4.4 Bank 0x03 - Serial and SPI Settings................................................................................. 477.4.5 Bank 0x04 - Host Protocol Settings .................................................................................. 487.4.6 Bank 0x05 - I/O Parameters ............................................................................................. 497.4.7 Bank 0x06 - I/O Settings ................................................................................................... 517.4.8 Bank 0x0FF - Special Functions ....................................................................................... 567.5 Protocol-formatted Message Examples .................................................................................. 577.5.1 Data Message ................................................................................................................... 577.5.2 Configuration Messages ................................................................................................... 587.5.3 Sensor Message ............................................................................................................... 587.5.4 Event Message ................................................................................................................. 598.0 DNT24DK/DNT24ADK Developer’s Kits........................................................................................ 608.1 Kit Contents ............................................................................................................................. 608.2 Additional Items Needed ......................................................................................................... 608.3 Developer’s Kit Default Operating Configuration..................................................................... 608.4 Developer’s Kit Hardware Assembly ....................................................................................... 618.5 Utility Program ......................................................................................................................... 628.6 Initial Kit Operation .................................................................................................................. 628.6.1 Serial Communication and Radio Configuration............................................................... 658.7 Interface Board Features......................................................................................................... 729.0 Troubleshooting ............................................................................................................................. 749.1 Diagnostic Port Commands..................................................................................................... 7410.0 Appendices .................................................................................................................................... 7510.1 Ordering Information................................................................................................................ 7510.2 Technical Support.................................................................................................................... 7510.3 DNT24/DNT24A Mechanical Specifications............................................................................ 7610.4 DNT24 Development Board Schematic .................................................................................. 8011.0 Warranty......................................................................................................................................... 83
www.Murata.com Technical support +1.678.684.2000 Page 6 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/151.0 DNT24 IntroductionDNT24 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, whileoperation in the 2.4 GHz ISM band allows license-free use in most regions of the world. The DNT24 sup-ports serial data rates for host communications from 1.2 to 250.0 kbps, plus three SPI data rates from 125to 500 kbps. On-board data buffering plus an error-correcting radio protocol provide smooth data flow andsimplify the task of integration with existing applications. Key DNT24 features include:Multipath fading resistant frequency hoppingtechnology with up to 24 frequency chan-nels, 2406 to 2475 MHzReceiver protected by low-loss SAW filter,providing excellent receiver sensitivity andinterference rejection important in outdoorapplications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.0 kbps on the serial port or500 kbps on the SPI portSupport for point-to-point, point-to-multipoint,peer-to-peer and store & forward networksAES encryption provides protection fromeavesdroppingFCC 15.247,IC RSS-210 and ETSI certifiedfor license-free operationNonvolatile memory stores DNT24 configura-tion when powered offFive mile plus range with omnidirectionalantennas (antenna height dependent)Selectable 10 or 63 mW transmit power levelsTransparent ARQ protocol with databuffering ensures data integrityAutomatic I/O event reporting mode simplifiesapplication developmentAnalog and Digital I/O supports wirelesssensing applications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 frequencydomain, a multipath fade can be described as a frequency-selective notch that shifts in location andintensity over time as reflections change due to motion of the radio or objects within its range. At any giv-en time, multipath fades will typically occupy 1% - 2% of the band. From a probabilistic viewpoint, a con-ventional radio system faces a 1% - 2% chance of signal impairment at any given time due to multipathfading.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.com Technical support +1.678.684.2000 Page 7 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/15Narrow-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.com Technical support +1.678.684.2000 Page 8 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/15One 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 DNT24 System OverviewA DNT24 radio can be configured to operate in one of three modes - base, remote or router. A base con-trols a DNT24 system, and interfaces to an application host such as a PC or Internet gateway. A remotefunctions to transmit or receive serial, digital (state) and analog data. A router alternates between func-tioning as a remote on one hop and a network base on the next hop. When acting as a remote, the routerstores messages it receives from its parent, and then repeats the messages to its child radios when act-ing as a network base. Likewise, a router will store messages received from its child radios when actingas a base, and repeat them to its parent when acting as a remote. Any message addressed directly to arouter is processed by the router rather than being repeated.2.1 Point-to-Point SystemsA DNT24 system contains at least one network. The simplest DNT24 topology is a point-to-point system,as shown in Figure 2.1.1. This system consists of a base and one remote forming a single network. Point-to-point systems are often used to replace wired serial connections. Point-to-point systems are also usedto transmit switch positions or analog signals from one location to another.Figure 2.1.1
www.Murata.com Technical support +1.678.684.2000 Page 9 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/152.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,DNT24 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 Technical support +1.678.684.2000 Page 10 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/15Figure 2.3.12.4 RF Channel AccessThe time a DNT24 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 DNT24 frame begins with a base-mode beacon,followed by 1 to 8 time slots used by the network children to transmit to their parent, as shown in Figure2.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.Figure 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 in
www.Murata.com Technical support +1.678.684.2000 Page 11 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/15the 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 radiokeeps its data queued and continues to look for an open slot in each beacon until at least one slotbecomes available. The access method the DNT24 uses is referred to as Ad Hoc TDMA.2.5 DNT24 AddressingEach DNT24 has a unique MAC address. The MAC address can be read or bar-code scanned from thelabel on top of each radio. A DNT24 radio in any mode (base/router/remote) can be addressed using itsMAC address. A DNT24 base can be addressed using either its MAC address or address 0x000000. ADNT24 can send a message to all other DNT24’s in its system by using the broadcast address 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 DNT24 radios hold a system ID that can be used to distinguish systems that physically overlap. In aDNT24 system, the system ID must be different from those used by overlapping systems to provide mes-sage filtering. Also, using different base-mode network IDs for all networks in overlapping systems helpsreduce 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 the Parent-MacAddress parameter of its parent, grandparent, etc., in succession reveals the complete path to thebase. Path determination is useful in optimizing and troubleshooting systems during commissioning andmaintenance.2.6 Network Linking and Slot RegistrationWhen first turned on, a DNT24 router or remote rapidly scans all frequency channels in its operating bandto acquire synchronization and link to a parent based on a system ID match plus a base-mode network IDto parent network ID/alternate parent network ID match (or by using a wildcard (0xFF) parent network 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 parameter
www.Murata.com Technical support +1.678.684.2000 Page 12 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/15changes. 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 DNT24 system.When 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- use no more hops in the hopping pattern than are necessary- transmit only dynamic cycle parameters once system nodes have static parametersIn the United States and Canada, the DNT24 complies with DTS (DSSS) regulations based on the band-width of its transmitted spectrum. In this case, frequency hopping is optional and when frequency hoppingis used there is no minimum requirement on the number of hopping channels that can be used. As dis-cussed in Section 7.4.2., there are two 5-channel hopping patterns that can be used to help minimize link-ing time. All DNT24’s in a system must be preset to one of these 5-channel hopping patterns in order toachieve fast linking. Note that the 5-channel hopping patterns cannot be used in Europe.Once 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 DNT24 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 DNT24 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 or in multi-point systems whenbroadcast addressing is used, the base can also be configured for transparent serial port operation.In all other cases, serial data will 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.
www.Murata.com Technical support +1.678.684.2000 Page 13 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/15Transparent data is routed using a remote transparent destination address. In a remote, this addressdefaults to the base, 0x000000, and in the base this address defaults to broadcast, 0xFFFFFF. Thesedefaults 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.3.0 DNT24 Application InterfacesA DNT24 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 DNT24 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 as an optional feature. One digital I/O pin can also be configured as an RS485 enable function. Theserial communication port can be configured with baud rates from 1.2 to 250.0 kbps, with 9.6 kbps thedefault baud rate. The DNT24 communication port transmits/receives 8-bit data with a choice of even,odd or no parity and 1 or 2 stop bits. The default configuration is no parity and one stop bit. See Section5.1 for recommendations on configuring the communication port, and Section 7.4.4 for detailed infor-mation on configuration parameters. The diagnostic port is enabled as an alternate function on two digitalI/O pins, and can be configured with baud rates from 1.2 to 250.0 kbps, with 9.6 kbps the default baudrate. The diagnostic port transmits/receives 8-bit data with no parity and 1 stop bit. See Section 7.4.8 fordiagnostic port configuration details.3.2 SPI PortThe DNT24 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.Figure 3.2.1
www.Murata.com Technical support +1.678.684.2000 Page 14 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/15The DNT24 SPI port can run at three clock rates in master mode - 125, 250 or 500 kbps. There are twomessage sources available to a DNT24 SPI master, a protocol-formatted RxData message or a storedcommand. The DNT24 master will clock a message from either source into its slave and return the bytesclocked out as a protocol-formatted TxData message. The DNT24 event timer triggers sending the storedcommand to the DNT24’s slave. The stored command can be up to 16 bytes in length. Figure 3.2.1shows the required SPI master mode-signal connections, and Figure 3.2.2 shows the SPI master-modetiming.Figure 3.2.2In SPI slave mode, the host can stream data into DNT24 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 DNT24 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.4Figure 3.2.3
www.Murata.com Technical support +1.678.684.2000 Page 15 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/15Figure 3.2.4The host should use the following steps to fetch data from a DNT24 SPI slave, as show in Figure 3.2.5:1. The host sets the /HOST_RTS signal high to allow the DNT24 to signal data available.2. The DNT24 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 DNT24 to signal DAV the next time ithas 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.Figure 3.2.5
www.Murata.com Technical support +1.678.684.2000 Page 16 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/153.3 Digital I/OThe DNT24’s six digital (state) I/O ports are labeled GPIO0 through GPIO5. GPIO5 has an alternate func-tion of /HOST_ RTS and GPIO4 of /HOST_CTS, providing hardware handshaking for the serial port andSPI slave mode operation. If serial port hardware handshaking is not required and SPI slave mode is notenabled, GPIO4 and GPIO5 can be used for other digital I/O functions. When SPI slave mode is enabled,GPIO5 and GPIO4 must be used for /HOST_RTS and /HOST_CTS respectively, and GPIO3 must beused to provide the DAV signal (SPI slave mode overrides any other configuration for these ports).Except in SPI slave mode, GPIO0 through GPIO5 are available for customer-defined functions:- 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 fordetailed information on GPIO parameters.3.4 Analog I/OThe DNT24’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 sensorinputs 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 DNT24 regulated supply voltage divided by 1.6, or about 2.06 V2. A low impedance voltage source applied to the DNT24’s ADC_EXT_REF input pin, 2.7 V maxi-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.The DNT24’s two DAC outputs are labeled DAC0 and DAC1. The DACs can be disabled if unused to re-duce current consumption. The DAC settings have 12-bit resolution. There are two options for the DACfull-scale reference:1. The DNT24 regulated supply voltage, about 3.3 V
www.Murata.com Technical support +1.678.684.2000 Page 17 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/152. A low impedance voltage source applied to the DNT24’s ADC_EXT_REF input pin, 2.7 V maxi-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 fordetailed information on analog I/O parameters.3.5 I/O Event Reporting and I/O BindingThe DNT24’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 aDNT24, 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 DNT24 when SPI slave mode is enabled or differential ADC mode is used.See Section 5.4 for recommendations on configuring I/O event reporting and binding, and Sections 7.4.6and 7.4.7 for detailed information on I/O reporting and binding parameters.4.0 DNT24 System ConfigurationDNT24 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 DNT24 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 dynamicallyadjusted during system operation such as link status. Write-only parameters include security keys andcertain action triggers such as reset. Incorrectly configuring certain parameters can disable a module’sradio link, but the configuration can always be corrected through the serial port. The organization of the
www.Murata.com Technical support +1.678.684.2000 Page 18 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/15parameter register banks and the details of each parameter are covered in Section 7.4 of this guide. Sec-tions 4.2 through 5.7 discuss which parameters apply to various aspects of configuring a DNT24 system,network or application interface.4.2 Configuring a Basic Point-to-Point SystemA basic DNT24 point-to-point system is suitable for many serial data applications. The default config-uration of a DNT24 is a remote with the serial port configured for transparent operation at 9.6 kbps,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 DNT24 point-to-multipoint point systems is suitable for many serial data applications wheremultiple remotes are used. The default configuration of a DNT24 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.5. If the host application driving the base will individually communicate with each remote, the MACaddress for each remote can be obtained from announce packets, heartbeat packets, aForceDiscover command, or by reading or scanning the MAC address from the label on top ofeach remote.4.4 Configuring a Customized Point-to-Point or Point-to-Multipoint SystemThe DNT24 includes many configuration parameters that allow extensive customization of a point-to-pointor point-to-multipoint system. Most applications will require only a few of these parameters be changedfrom their default values. But for those applications that need them, RFM recommends the following con-figuration sequence. Skip the configuration steps where the default parameter value is satisfactory.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).
www.Murata.com Technical support +1.678.684.2000 Page 19 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/153. 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 63 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 DNT24 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, the DNT24broadcast mode can be used instead of the DNT24 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 to send assoon as possible).d. 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.
www.Murata.com Technical support +1.678.684.2000 Page 20 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/15c. 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 toresynchronize 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 DNT24 store-and-forward system:1. Configure the DNT24 radios designated to be routers by setting the DeviceMode parameterin Bank 0 to 0x02.2. Enable store-and-forward operation on all system radios by setting the Store&ForwardEnparameter in Bank 0 to 0x01.3. 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 andremotes. 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.
www.Murata.com Technical support +1.678.684.2000 Page 21 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/15- 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 nodes can re-link to any other parent router they can receive. However, automatic topology formation can result in anunnecessary number of hops between routers or remotes and the base. The benefit of manual systemtopology formation is to avoid unnecessary extra hops in the system, and to balance the number of chil-dren supported by each parent router. If a parent router fails and an active alternate parent network IDhas not been assigned, all children downstream from the failure will be off the system until the failed rout-er 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 a DNT24system is configured for one slot. Adding additional slots reduces the maximum BSS by three bytes perslot.The BSS buffer is set nine bytes larger than the BSS, to a maximum of 114 bytes.The base can po-tentially send more than one message per beacon, up to the limit set by its MsgsPerHop parameter 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 totalnumber of payload 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 childcan send two messages per hop when the RSS is 73 bytes, provided the total number of payload bytes inthe two messages 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 DNT24s in a system, rather than being a user configured parameter.The slot size depends on the current values of the following parameters:- base slot size- hop duration- number of slots in a frame
www.Murata.com Technical support +1.678.684.2000 Page 22 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/15The 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 accommodateall 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 to
www.Murata.com Technical support +1.678.684.2000 Page 23 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/15send 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 data.The MsgsPerHop parameter is configurable for each DNT24 in a system. This parameter is usually set toa high value in the base and the routers, allowing traffic between a parent and multiple children on eachhop. The MsgsPerHop parameter has little effect in remotes except when a remote needs to send multi-ple peer-to-peer messages during a hop. To support sending multiple messages on each hop, the BSSand RSS must be sized accordingly, requiring a longer hop duration. Note that the messages must beprotocol messages and all messages to be sent on a single hop must be in the module before the modulebegins to transmit.5.0 DNT24 Application Interface ConfigurationDNT24 modules include a comprehensive set of application interfaces and related options that support awide range of applications including wireless RS232/485 cable replacements, wireless sensor networks,wireless alarm systems and industrial remote control applications. Recommended configuration steps foreach 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.0 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.5.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.
www.Murata.com Technical support +1.678.684.2000 Page 24 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/155.3 Configuring Digital I/O1. GPIO2 through GPIO 5 have configurable alternate functions as discussed in Section 7.4.7.Select either digital (state) functionality or alternate functionality for each of these pins by settingthe GpioAlt parameter in Bank 6. Note that selecting SPI slave mode overrides the GpioAlt pa-rameter setting 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.4. 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.
www.Murata.com Technical support +1.678.684.2000 Page 25 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/157. 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 DNT24 to settle following a wake up event, while AdcSkipCount skips meas-urements that may be distorted because the internal voltage on the ADC sample-and-hold hasnot 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 DNT24 has been integrated with the customer’s hardware in some applications. For analogcalibration support, contact RFM 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.5. Set the MaxQueuedEvents parameter in Bank 6 as needed to limit the number of Event Reportsthat can be queued at one time by a DNT24. 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.
www.Murata.com Technical support +1.678.684.2000 Page 26 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/155.6 Configuring Sleep ModeSleep mode can be used in conjunction with I/O reporting to greatly extend battery life on DNT24 remotes.At least one I/O report trigger must be enabled to allow sleep mode to be used. Note that thebase 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 Technical support +1.678.684.2000 Page 27 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/156.0 DNT24 HardwareFigure 6.0.1The major components of the DNT24 series modules include a 2.4 GHz FHSS transceiver and a lowcurrent 8-bit microcontroller. The DNT24 modules operate in the 2.4 GHz MHz ISM band. There are 12selectable hopping patterns providing compatibility with frequency allocations in most regions of theworld. DNT24 modules also have two selectable RF output power levels: 10 mW and 63 mW.The DNT24 modules provide a variety of hardware interfaces. There are two serial ports plus one SPIport. Either the primary serial port or the SPI port can be selected for data communications. The secondserial port is dedicated to diagnostics. The primary and diagnostic serial ports support most standardbaud rates up to 250.0 kbps. The SPI port supports data rates up to 500 kbps. Also included are threeADC inputs, two DAC outputs and six general-purpose digital I/O ports. Four of the digital I/O ports sup-port an optional interrupt-from-sleep mode when configured as inputs.There are four module configurations in the DNT24 Series:- The DNT24C is designed for use with an external antenna and for solder reflow mounting.- The DNT24P is designed for use with an external antenna and for plug-in connector mounting.- The DNT24CA has a built-in chip antenna and is designed for solder reflow mounting.- The DNT24PA has a built-in chip antenna and is designed for plug-in connector mounting.
www.Murata.com Technical support +1.678.684.2000 Page 28 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/156.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 Range24062475MHzHop Duration8100msNumber of RF Channels15 or 24ModulationFSKRF Data Transmission Rate250kbpsReceiver Sensitivity, 10-5 BER-100dBmTransmitter RF Output Power10 or 63mWOptimum Antenna Impedance, DNT24C and DNT24P50ΩRF Connection, DNT24C and DNT24PU.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, 250.0kbpsMaster Serial Peripheral Interface Data Rate125250500kbpsSlave Serial Peripheral Interface Data Rate4000kbpsDigital I/O:Logic Low Input Level-0.50.8VLogic High Input Level2.453.3VLogic Input Internal Pull-up Resistor20KΩPower Supply Voltage RangeVCC+3.3+5.5VdcPower Supply Voltage Ripple10mVP-PPeak Transmit Mode Current, 63 mW Output140mAAverage Operating Receive Current:Base or Remote, Continuous Data Stream55mARemote, Linked, No Data15mASleep Current36µAOperating Temperature Range-4085oCOperating Relative Humidity Range (non condensing)1090%Table 6.1.2
www.Murata.com Technical support +1.678.684.2000 Page 29 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/156.2 Module Pin OutElectrical connections to the DNT24C are made through the I/O pads and through the I/O pins on theDNT24P. 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 GPIO0. 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 GPIO0. 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, orthe differential negative input for positive inputs applied to ADC1 or ADC2 when the ADC is operat-ing in 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(about 2.06 V), or an external voltage applied to Pin 25. In single-ended mode, ADC measure-ments are 11-bit unsigned values with full scale nominally 2.7 V when referenced to a 2.7 V inputon Pin 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.Murata.com Technical support +1.678.684.2000 Page 30 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/15PinNameI/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.Table 6.2.16.3 Antenna ConnectorA U.FL miniature coaxial connector is provided on both DNT24 configurations for connection to the RFIOport. A short U.FL coaxial cable can be used to connect the RFIO port directly to an antenna. In this casethe antenna should be mounted firmly to avoid stressing the U.FL coaxial cable due to antenna mountingflexure. Alternately, a U.FL coaxial jumper cable can be used to connect the DNT24 module to a U.FLconnector on the host circuit board. The connection between the host circuit board U.FL connector andthe antenna or antenna connector on the host circuit board should be implemented as a 50 ohmFigure 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-
www.Murata.com Technical support +1.678.684.2000 Page 31 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/15cuit 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 VoltagesDNT24 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 DNT24 module.6.5 ESD and Transient ProtectionThe DNT24C and DNT24P 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 DNT24 are 3.3 V signals. To interface to 5 V signals, theresistor divider network shown in Figure 3.7.1 below must be placed between the 5 V signal outputs andthe DNT24 signal inputs. The output voltage swing of the DNT24 3.3 V signals is sufficient to drive 5 Vlogic inputs.Figure 6.6.16.7 Mounting and EnclosuresDNT24C and DNT24CA radio modules are mounted by reflow soldering them to a host circuit board.DNT24P and DNT24PA modules are mounted by plugging their pins into a set of mating connectors onthe host circuit board. Refer to Section 8.3 for DNT24P connector details.DNT24 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.DNT24
www.Murata.com Technical support +1.678.684.2000 Page 32 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/156.8 Labeling and NoticesDNT24 FCC Certification - The DNT24 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 20 cm from all persons and must not be co-located or operating in conjunction withany other antenna or transmitter.DNT24 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-DNT24Contains IC: 4492A-DNT24RFM (Insert Model Designation DNT24C, DNT24CA, DNT24P or DNT24PA depending on the modelused): This device complies with Part 15 of the FCC Rules. Operation is subject to the following two con-ditions: (1) This device may not cause harmful interference, and (2) this device must accept any interfer-ence received, 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 RFM, Inc., may void the user’s authority to operate this device.This apparatus complies with Health Canada’s Safety Code 6 / IC RSS 210.IC RSS-210 Notice - Operation is subject to the following two conditions: (1) this device may not causeinterference, and (2) this device must accept any interference, including interference that may cause 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 Industry 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 Industrie Canada.
www.Murata.com Technical support +1.678.684.2000 Page 33 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/157.0 DNT24 Protocol-formatted Messages7.1 Protocol FormatsDNT24 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 multiple individual destinations must useprotocol formatting unless the data being sent includes addressing information. Protocol formatting is alsorequired for configuration commands and replies, and sensor I/O commands, replies and events. All pro-tocol-formatted messages have a common header as shown in Figure 7.1.1:0123 …SOPLengthPktTypevariable number of arguments …Figure 7.1.1The scale above is in bytes.The 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 sent to the module on the serial interface by the user are referred to as host messages. Mes-sages generated on the serial interface by the radio are referred to as reply or event messages. Hostmessages carry commands. For most commands, there is a corresponding reply message. For example,when the host sends a TxData command message, the radio can return a TxDataReply message to indi-cate the status of the transmission - whether it succeeded or failed. To assist in interpreting the com-mand-reply data flow, the direction is indicated by the high nibble in the message type. For example, anEnterProtocolMode command from the host is a message type 0x00, and the EnterProtocolModeReplyfrom the radio is a message type 0x10.Event messages from a DNT24, such as received data or status announcements make up a third catego-ry of messages. Event messages, including RxData,RxEvent and Announce packets are indicated by0x20 in the high nibble of the type byte.If multiple arguments are to be provided, they are to be concate-nated in the order shown in Section 7.3 below. Little-Endian byte order is used for all multi-byte
www.Murata.com Technical support +1.678.684.2000 Page 34 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/15arguments 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 DNT24 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.Murata.com Technical support +1.678.684.2000 Page 35 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/15ExitProtocolMode 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.Murata.com Technical support +1.678.684.2000 Page 36 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/15Get 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.Murata.com Technical support +1.678.684.2000 Page 37 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/15TX 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.Murata.com Technical support +1.678.684.2000 Page 38 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/15SetRemoteRegister 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.Murata.com Technical support +1.678.684.2000 Page 39 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/15Announce/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.Murata.com Technical support +1.678.684.2000 Page 40 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/15RxEvent 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.Murata.com Technical support +1.678.684.2000 Page 41 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/157.4 Configuration Parameter RegistersThe configuration parameters in a DNT24 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. DNT24modules can be configured to start in protocol mode at power-up, in which case the EnterProtocolModecommand 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“DNT24”0x000x29RmtTransDestAddrR/W0x030x000000 (Base)0x000x2CStore&ForwardEnR/W0x010..10 (disabled)0x000x2DBaseModeNetIDR/W0x011..63, 2550xFF0x000x2EHeartbeatIntrvlR/W0x020..655350xFFFF (disabled)0x000x30SystemIdR/W0x010..25500x000x31EndToEndAckEnableR/W0x010..10 (disabled)0x000x32LinkRetryIntervalR/W0x020..655350 (off)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 or software reset or a power off/on cycle. A router without a validBaseModeNetID 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.ParentNwkID - 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 to
www.Murata.com Technical support +1.678.684.2000 Page 42 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/15255 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. When encryption is enabled on the device, theuser's payload data will be encrypted. AES-128 is the same form of encryption used in WiFi networks.The encryption key will also limit which radios can join the network. The encryption must match on bothdevices for the radios to link with each other. This is one way to make sure that rogue devices cannotjoin the network.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 DNT24 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 sec-onds in 1 second steps. If this value is set to 0, the remote will stay awake and continue trying to link to itsparent 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 = +10 dBm or 10 mW0x01 = +18 dBm or 63 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 station,where at startup it will be changed to the broadcast address (0xFFFFFF) if the firmware detects that it isset to 0x000000. Note - if a module’s configuration is changed from a base to a remote or router, this pa-rameter must be set back to 0x000000 or the module will send broadcast packets in transparent mode orfor event packets.Store&ForwardEn - setting this parameter to 0x01 enables store-and-forward system operation. Store-and-forward operation is disabled by default.
www.Murata.com Technical support +1.678.684.2000 Page 43 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/15BaseModeNetID - 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 ParentNwkIDparameter 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 DNT24swhere 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 DTN24 system. DNT24 systems that may physically overlapmust have different system IDs.EndToEndAckEnable - when this parameter is set to 1 and the module is in protocol mode, the originatorwill indicate in its transmitted packet that an ACK is expected from the packet’s destination node. Settingthis parameter to 0x00 reduces network congestion in a store-and-forward system, but no TxDataReplywill be sent from the destination to confirm reception.LinkRetryInterval -when a remote enters sleep mode with any packet unsent in its transmit queue, if thisparameter is set to a non-zero value, the remote will wake up after the specified number of seconds andtry to link so that pending packets can be transmitted. When 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 DNT24 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 slotsize of 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 8 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.Murata.com Technical support +1.678.684.2000 Page 44 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/157.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..11, 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 theDNT24 system will initially operate. Twelve bands are available:SubbandChannelsFrequency Range(s)Notes0x00242406 - 2475 MHzGeneral purpose 24 channel band0x01152433 - 2475 MHz15 channel band, avoids 802.11b/g channels 1-20x02152406 - 2475 MHz15 channel band, avoids 802.11b/g channels 30x03152406 - 2475 MHz15 channel band, avoids 802.11b/g channels 40x04152406 - 2475 MHz15 channel band, avoids 802.11b/g channels 50x05152406 - 2475 MHz15 channel band, avoids 802.11b/g channels 60x06152406 - 2475 MHz15 channel band, avoids 802.11b/g channels 70x07152406 - 2475 MHz15 channel band, avoids 802.11b/g channels 80x08152406 - 2475 MHz15 channel band, avoids 802.11b/g channels 90x09152406 - 2475 MHz15 channel band, avoids 802.11b/g channels 100x0A152406 - 2475 MHz15 channel band, avoids 802.11b/g channels 110x0B152406 - 2448 MHz15 channel band for operation in France0x0C52406 - 2466 MHz5 channel band for fast linking, use US and Canada only0x0D52415 - 2475 MHz5 channel band for fast linking, use in US and Canada only0xFFAutoAutoAutoscan for remote to match baseTable 7.4.2.2
www.Murata.com Technical support +1.678.684.2000 Page 45 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/15NumSlots - 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 afterreceiving a message from that child. Small values such as 2 are suited to short data bursts, and largervalues are generally a better choice when devices send a stream of non-continuous data across consecu-tive hops. The minimum value is 1, assuring that a child can receive an ACK on the next hop after ittransmits.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 packetscan 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 theremote to restart a link acquisition search. Please contact RFM technical support before making changesto 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 comeback before 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 outduplicate 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 DNT24 system have received all cycledparameters and stored them locally in EEPROM. At this point the number of cycled parameters can beset to 8, which will significantly speed up future system resynchronizations.
www.Murata.com Technical support +1.678.684.2000 Page 46 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/157.4.3 Bank 0x02 - Status ParametersBankLocationNameR/WSizeRangeDefault0x020x00MacAddressR0x030..0xFFFFFFFixed value0x020x03CurrNwkIDR0x010..63, 255Current Value0x020x04CurrFreqBandR0x010..2, 255Current Value0x020x05LinkStatusR0x010..6Current 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 Value0x020x18ModelNumberR0x010x24, 0x900x24 = DNT240x020x19TxQueueR0x010..1Current ValueTable 7.4.3.1MacAddress - 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 currentlyassigned to or connected to. A value of 0xFF means the radio has powered up and is scanning for anetwork 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 = registered0x06 = linked in fast beacon modeRemoteSlotSize - 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 DNT24 Revision Chardware.FirmwareVersion - this parameter holds the firmware version of the radio in 2-digit BCD format.
www.Murata.com Technical support +1.678.684.2000 Page 47 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/15FirmwareBuildNum - 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 DNT24’s parent.ModelNumber - this parameter specifies the DNT model, in this case a DNT24.TxQueue - this parameter indicates if the transmitter queue is currently holding bytes to transmit.If bytes are present in the queue the value is 1. If the queue is empty the value is 0.7.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 rate0x00 1.2 kbps0x01 2.4 kbps0x02 4.8 kbps0x03 9.6 kbps0x04 14.4 kbps0x05 19.2 kbps0x06 28.8 kbps0x07 38.4 kbps0x08 57.6 kbps0x09 115.2 kbps0x0A 230.4 kbps0x0B 250.0 kbps
www.Murata.com Technical support +1.678.684.2000 Page 48 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/15SerialParams - this parameter sets the serial mode options for parity and stop bits:Setting Mode0x00 No parity, 8 data bits, 1 stop bit (default)0x01 No parity, 8 data bits, 2 stop bits0x02 Reserved0x03 Reserved0x04 Even parity, 8 data bits, 1 stop bit0x05 Even parity, 8 data bits, 2 stop bits0x06 Odd parity, 8 data bits, 1 stop bit0x07 Odd 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 Mode0x00 SPI disabled - serial UART mode (default)0x01 SPI Slave mode0x02 SPI Master modeSpiRateSel - this parameter sets the SPI master mode clock rate:Setting Mode0x00 125 kbps0x01 250 kbps0x02 500 kbpsSpiOptions - this parameter allows the SPI to be configured with the following options:Setting Option0x00 Leading edge rising, sample leading edge, MSBs sent first0x01 Leading edge rising, sample falling edge, MSBs sent first0x02 Leading edge falling, sample leading edge, MSBs sent first0x03 Leading edge falling, sample falling edge, MSBs sent first0x04 Leading edge rising, sample leading edge, LSBs sent first0x05 Leading edge rising, sample falling edge, LSBs sent first0x06 Leading edge falling, sample leading edge, LSBs sent first0x07 Leading 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.1
www.Murata.com Technical support +1.678.684.2000 Page 49 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/15ProtocolMode - 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 DNT24's built-in protocol. This setting is recommended for point-to-point applications for legacy applications such as wire replacements where another serial protocol mayalready exist. Setting this parameter to 0x01 enables the DNT24 protocol formatting. It is not necessary todefine the same protocol mode for all radios in a network. For example, it is frequently useful to configureall the remotes for transparent mode and the base for protocol mode. Note that it is possible for the hostto switch the radio from transparent mode to protocol mode and back as required by transmitting anEnterProtocolMode 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 theamount of time the DNT24 will wait without receiving a byte through the serial port before transmitting thedata. Parameter units are in milliseconds. A message boundary is determined whenever a gap betweenconsecutive characters is equal to or greater than the TxTimeout value, or the number of bytes reachesthe MinPacketLength. Either condition will trigger a transmission. The default TxTimeout value is 0 mswhich will have the radio send 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 consecutivecharacters 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 destination address will first bethe RemoteDestAddr, but then will update to the originator of the most recent RX packet processed.MsgsPerHop - this parameter sets the maximum number of messages a DNT24 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.1
www.Murata.com Technical support +1.678.684.2000 Page 50 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/15All-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):bits 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.
www.Murata.com Technical support +1.678.684.2000 Page 51 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/157.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)0x060x3FAdcGainCh1R/W0x0180 (gain = 1)0x060x40AdcDiffScaleFactorCh0R/W0x02160x80000x060x42AdcDiffOffsetCh0R/W0x02160x00000x060x44AdcDiffScaleFactorCh1R/W0x02160x80000x060x46AdcDiffOffsetCh1R/W0x02160x00000x060x47FastAdcPrescalerR/W0x011 byte, range 1..75 (128)0x060x48SlowAdcPresccalerR/W0x011 byte, range 0..72 (16)
www.Murata.com Technical support +1.678.684.2000 Page 52 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/15BankLocationNameR/WSizeRange In BitsDefault0x060x49MaxQueuedEventsR/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 toggleenable, 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 theGpioAlt 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.
www.Murata.com Technical support +1.678.684.2000 Page 53 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/15GpioSleepState - 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 aninternal 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 todetermine if a threshold has been exceeded or in calculating an average measurement value. The threeADC channels are read on each ADC cycle, along with the states of GPIO2 and GPIO3. Each AdcSam-pleIntvl count equals 10 ms. The default is 100 ms. This interval will be the worst-case latency for ADCgenerated interrupts. Note that AdcSampleIntvl is independent of IoReportInterval as the ADCs are readon both intervals.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 DNT24 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.IoReportInterval - 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 anevent occurs, to allow settling of ADC input voltages.
www.Murata.com Technical support +1.678.684.2000 Page 54 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/15IoBindingEnable - 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 Reference0x00 ADC_EXT_REF0x01 AVVC (Analog Vcc)0x02 Reserved0x03 Disable DAC operationAdcReference - this parameter selects the reference voltage for the ADCs:Setting Reference0x00 ADC_EXT_REF0x01 Internal Vcc divided by 1.60x02 Reserved0x03 Disable 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.VccAdcScaleFactor - 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.
www.Murata.com Technical support +1.678.684.2000 Page 55 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/15VccAdcOffset - 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.Murata.com Technical support +1.678.684.2000 Page 56 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/15FastAdcPrescaler - 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 correspondto slower ADC clock rates. For example, 0x07 = 512, and 0x00 = 4. Note that larger prescalers will in-crease the amount of time it takes to collect all readings. DIV4 is not valid when running at 16 MHz be-cause 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 DNT24. 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 DNT24 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 rate0x00 1.2 kbps0x01 2.4 kbps0x02 4.8 kbps0x03 9.6 kbps0x04 14.4 kbps0x05 19.2 kbps0x06 28.8 kbps0x07 38.4 kbps (default)0x08 57.6 kbps0x09 115.2 kbps0x0A 230.4 kbps0x0B 250.0 kbps
www.Murata.com Technical support +1.678.684.2000 Page 57 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/15ForceDiscoverRegister - 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.7.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 Val0xFB0x0B0x070x560x340x120x1C0x060x040x100x270x000x00
www.Murata.com Technical support +1.678.684.2000 Page 58 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/15The 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:SOPLengthPktTypeStatusLo MACMACHi MACRSSIRegBankSizeLo ValHi Val0xFB0x0B0x160x000x000x000x000xB70x1C0x060x020x7B0x08Substantial 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 bytefollowing 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.
www.Murata.com Technical support +1.678.684.2000 Page 59 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/157.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:FB 12 28 56 34 12 B8 00 7A 01 36 01 FF 01 10 00 20 01 40 01FB 12 28 56 34 12 B0 00 79 01 35 01 C0 01 10 00 20 01 40 01FB 12 28 56 34 12 A9 00 72 01 35 01 D3 01 10 00 20 01 40 01FB 12 28 56 34 12 AC 00 75 01 36 01 E7 01 10 00 20 01 40 01The 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.Murata.com Technical support +1.678.684.2000 Page 60 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/158.0 DNT24DK/DNT24ADK Developer’s KitsFigure 8.0.1 shows the main contents of a DNT24DK Developer’s kit:Figure 8.0.18.1 Kit ContentsDNT24DK - 2 DNT24P radios installed in DNT24 interface boards, labeled Base and RemoteDNT24DK - 2 patch antennas and two 2 dBi dipole antennas with MMCX/RSMA adaptor cablesDNT24ADK - 2 DNT24PA radios installed in DNT24 interface boards, labeled Base and RemoteAll Kits - 2 wall-plug power suppliers, 9 VDC, 120/240 VAC, plus 2 batteries, 9 VDC (not showabove)All Kits - 2 RJ-45/DB-9F cable assemblies and two A/B USB cablesAll Kits - 1 DNT24DK/DNT24ADK 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 DNT24DK developer’s kit is point-to-point with transparentserial data at 9600 bps, 8N1. One DNT24 is preconfigured as a base and the other as a remote. Labelson the bottom of the interface boards specify Base or Remote.
www.Murata.com Technical support +1.678.684.2000 Page 61 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/158.4 Developer’s Kit Hardware Assembly1. Figure 8.4.1 shows a DNT24P radio installed on an interface board, and a patch antenna. ObserveESD precautions when handling the kit circuit boards. Install a patch antenna on each interface board bypressing the antenna into the interface board RF connector with moderate pressure until the antennasnaps onto the connector, as shown in Figure 8.4.2. Note that no external antenna is required when usingthe DNT24PA radios supplied in the DNT24A Kits.2. As shown in Figure 8.4.3, there are three serial connectors and a power connector on the end of eachinterface board. The RJ-45 connector provides an RS232 interface to the DNT24 main serial port. TheUSB connector provides an optional interface to the radio’s main serial port.Figure 8.4.1Figure 8.4.2Figure 8.4.33. If using a serial cable, connect the Base interface board to the PC using a RJ-45/DB-9F cable assem-bly (labels on the bottom of the interface boards specify Base or Remote). Then power the Base with asupplied wall-plug power supply. Continue at Step 5 below.
www.Murata.com Technical support +1.678.684.2000 Page 62 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/154. If using a USB cable continue with this Step to install the USB drivers, else continue at Step 5. Plug-ging in the USB cable automatically switches operation to the USB connector. The USB interface isbased on an FT232RL serial-to-USB converter IC manufactured by FTDI. The FT232RL driver files arelocated in the i386 and AMD64 folders on the CD, and the latest version of the drivers can be down-loaded from the FTDI website, www.ftdichip.com. The drivers create a virtual COM port on the host PC.a. Power the Base using one of the supplied wall-plug power supplies.b. Next connect the Base to the PC with a USB cable. The PC will find the new USB hardware andopen a driver installation dialog box. Enter the letter of the drive holding the kit CD and click Continue.The installation dialog will run twice to complete the driver installation.8.5 Utility ProgramThe DNT Demo 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 DNT24 Demo utility program for initial kit operation and familiarization. Section8.6.1 covers serial message communication and radio configuration.8.6 Initial Kit OperationThe DNT Demo utility program is located in the PC Programs folder on the kit CD. The DNT Demorequires no installation and can be simply copied to the PC and run.Figure 8.6.11. Start the Demo on the PC. The Demo program start-up window is shown in Figure 8.6.1.
www.Murata.com Technical support +1.678.684.2000 Page 63 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/152. Click 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 connection.Figure 8.6.23. At this point the utility program will collect data from the Base, filling in the Local Radio column asshown in Figure 8.6.3.Figure 8.6.34. Next power up the Remote using a wall-plug power supply. The Remote will transmit a “heartbeat”message on power up.5. Click on the drop-down box at the top of the Radio 1 column and click on the MAC Address (preloadedwhen the Remote is turned on after the Base), or load the MAC Address for the Remote from theheartbeat message.
www.Murata.com Technical support +1.678.684.2000 Page 64 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/156. Next press the Start button using the default 1 second Refresh Delay.Figure 8.6.47. The Demo will display data on the Remote in the Radio 1 column, including bar graphs of RSSI (signalstrength) and percent packet success rate, as shown in Figure 8.6.4. Adjusting the pot on the Remotecan be observed in the Potentiometer (ADC0) data. You can change the Refresh setting from the dropdown menu at the bottom left. Adjusting the pot on the base can be observed in the Potentiometer(ADC0) data in the Local Radio column.If any difficulty is encountered in setting up the DNT24DK development kit, contact RFM’s module tech-nical support group. The phone number is +1.678.684.2000. Phone support is available from 8:30 AM to5:30 PM US Eastern Time Zone, Monday through Friday. The E-mail address is tech_sup@rfm.com.
www.Murata.com Technical support +1.678.684.2000 Page 65 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/158.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 DNT24 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.Murata.com Technical support +1.678.684.2000 Page 66 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/15Returning 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.Murata.com Technical support +1.678.684.2000 Page 67 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/15Figure 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.Murata.com Technical support +1.678.684.2000 Page 68 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/15Figure 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.Murata.com Technical support +1.678.684.2000 Page 69 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/15Figure 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 foractive and sleep modes, and in the case of GPIO outputs, the initial power up states and sleep modestates to be set. When GPIO ports 0 - 3 are configured as inputs, event interrupts can be set for themwith check boxes. The type of interrupt trigger is selected from the drop-down boxes to the right of thecheck boxes. Periodic I/O reporting, reporting interval and enable/disable sleep I/O states and I/O bindingcan also be configured under this tab.
www.Murata.com Technical support +1.678.684.2000 Page 70 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/15Figure 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.Figure 8.6.1.10Figure 8.6.1.10 shows the third I/O Setup tab contents, corresponding to Bank 6 ADC input and DAC out-put scaling, offset and related parameters. These parameters should not be changed from their defaultsunless precision inputs are available to calibrate the ADC and DAC functions.
www.Murata.com Technical support +1.678.684.2000 Page 71 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/15The Demo Utility File,Options and Help menus are shown in Figure 8.6.1.11.Figure 8.6.1.11
www.Murata.com Technical support +1.678.684.2000 Page 72 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/158.7 Interface Board FeaturesThe locations of the LEDs on the interface board that are used by the DNT24 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 orremotes are registered to it, unless the base has been configured to assert DCD on power up. In thiscase it will be on as long as the development board is powered. Activity LED, D10, illuminates whentransmitting or receiving RF data. Power LED, D1, illuminates with the DNT24 and its interface board arepowered. GPIO2 LED, D5, and GPIO3 LED, D4, can be controlled by configuring GPIO2 and GPIO3 asoutputs on the DNT24. 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 DNT24P mounting socket. JP3 andJP4 normally have shorting plugs installed as shown in Figure 8.8.2. JP3 connects ADC0 to the yellowpotentiometer. Clockwise rotation of the potentiometer increases the voltage. JP4 connects ADC1 to athermistor temperature sensor. The DNT24 has its own boot loader utility that allows the protocol firm-
www.Murata.com Technical support +1.678.684.2000 Page 73 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/15ware 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 DNT24 pins as shown on the silkscreen.Pressing switch SW3 will reset the DNT24P. Switch S4 is not used with the DNT24.Figure 8.8.3Figure 8.8.3 shows the connectors to the left of the DNT24P mounting socket. Pressing switch SW1switches GPIO0 from logic high to low, and pressing SW2 switches GPIO1 from logic high to low. TheDNT24P 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 DNT24P directly. The maximumallowed voltage input to the DNT24P is 5.5 V.
www.Murata.com Technical support +1.678.684.2000 Page 74 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/159.0 TroubleshootingDNT24 not responding - make sure /RESET is not asserted (logic low). Make sure the host serial portsettings match the DNT24 serial port settings.Can not enter protocol mode - make sure the host data rate is correct. The DNT24 defaults to 9.6 kbps. Ifusing 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 System-NwkID is the same as the base, and that the ParentNwkID parameter is the same as the base, or is set to0xFF. 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 DNT24.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.Murata.com Technical support +1.678.684.2000 Page 75 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/1510.0 Appendices10.1 Ordering InformationDNT24C: transceiver module for solder-pad mounting, for use with external antennaDNT24P: transceiver module for pin-socket mounting, for use with external antennaDNT24CA: transceiver module for solder-pad mounting, includes on-board chip antennaDNT24PA: transceiver module for pin-socket mounting, includes on-board chip antenna10.2 Technical SupportFor DNT24 technical support call RFM at (678) 684-2000 between the hours of 8:30 AM and 5:30 PMEastern Time
www.Murata.com Technical support +1.678.684.2000 Page 76 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/1510.3 DNT24 Mechanical SpecificationsFigure 10.3.1Figure 10.3.2
www.Murata.com Technical support +1.678.684.2000 Page 77 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/15Figure 10.3.3Figure 10.3.4
www.Murata.com Technical support +1.678.684.2000 Page 78 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/15Figure 10.3.2
www.Murata.com Technical support +1.678.684.2000 Page 79 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/15Figure 10.3.3
www.Murata.com Technical support +1.678.684.2000 Page 80 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/1510.4 DNT24 Development Board Schematic
www.Murata.com Technical support +1.678.684.2000 Page 81 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/15
www.Murata.com Technical support +1.678.684.2000 Page 82 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/15
www.Murata.com Technical support +1.678.684.2000 Page 83 of 83© 2015 by Murata Manufacturing Co. Ltd. E-mail: tech_sup@murata.com DNT24 Integration Guide – 03/04/1511.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 actionshall be 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 ORMERCHANT ABILITY OR FITNESS FOR A PARTICULAR PURPOSE). SELLER’S LIABILITY ARISINGOUT OF THE MANUFACTURE, SALE OR SUPPLYING OF THE GOODS OR THEIR USE ORDISPOSITION, WHETHER BASED UPON WARRANTY, CONTRACT, TORT OR OTHERWISE, SHALLNOT EXCEED 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,INCIDENTAL OR CONSEQUENTIAL DAMAGES, INCLUDING, BUT NOT LIMITED TO, LOSS OFPROFITS, LOSS OF DATA OR LOSS OF USE DAMAGES ARISING OUT OF THE MANUFACTURE,SALE OR SUPPLYING OF THE GOODS. THE FOREGOING WARRANTY EXTENDS TO BUYERONLY AND SHALL NOT BE APPLICABLE TO ANY OTHER PERSON OR ENTITY INCLUDING,WITHOUT LIMITATION, CUSTOMERS OF BUYERS.Part # M-0024-0002, Rev F

Navigation menu