Murata Electronics North America DNT90 Manual Do Utilizador
Preliminary
www.RFM.com
Technical support +1.678.684.2000
Page 45 of 80
© 2010-2012 by RF Monolithics, Inc.
E-mail:
tech_sup@rfm.com
DNT90 Integration Guide - 05/10/12
can be lost. Note - if this mode is used in a multipoint network, one remote that has lost link will shut down
the entire network if the base is trying to send it data.
LinkDropThreshold - this is the number of consecutive beacons missed by a remote that causes the re-
mote to restart a link acquisition search. Please contact RFM technical support before making changes to
the parameter.
P2PReplyTimeout - this parameter sets the reply timeout for peer-to-peer messages sent from one node
to 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 variation
than 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 reply
from its recipient. If a reply returns sooner than the timeout, the remote will send a TxDataReply indicating
success (ACK) to its host as soon as it is received, and cancels the timeout. If a reply does not come
back before the timeout expires, the remote will send a TxDataReply to its host indicating failure (NAK). If
a 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 a
parent device will preserve the Transaction ID (TID) history for that child. The TID is used to filter out du-
plicate packets. After a registry timeout occurs, the TID history is discarded.
NumBaseParms - this parameter controls the number of cycled parameters sent in the base station bea-
con. It must be left in its default value of 21 until all nodes in a DNT90 system have received all cycled
parameters and stored them locally in EEPROM. At this point the number of cycled parameters can be
set to 9, which will significantly speed up future system resynchronizations.
7.4.3 Bank 0x02 - Status Parameters
the entire network if the base is trying to send it data.
LinkDropThreshold - this is the number of consecutive beacons missed by a remote that causes the re-
mote to restart a link acquisition search. Please contact RFM technical support before making changes to
the parameter.
P2PReplyTimeout - this parameter sets the reply timeout for peer-to-peer messages sent from one node
to 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 variation
than 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 reply
from its recipient. If a reply returns sooner than the timeout, the remote will send a TxDataReply indicating
success (ACK) to its host as soon as it is received, and cancels the timeout. If a reply does not come
back before the timeout expires, the remote will send a TxDataReply to its host indicating failure (NAK). If
a 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 a
parent device will preserve the Transaction ID (TID) history for that child. The TID is used to filter out du-
plicate packets. After a registry timeout occurs, the TID history is discarded.
NumBaseParms - this parameter controls the number of cycled parameters sent in the base station bea-
con. It must be left in its default value of 21 until all nodes in a DNT90 system have received all cycled
parameters and stored them locally in EEPROM. At this point the number of cycled parameters can be
set to 9, which will significantly speed up future system resynchronizations.
7.4.3 Bank 0x02 - Status Parameters
Bank
Location
Name
R/W
Size
Range
Default
0x02 0x00
MacAddress
R
0x03 0..0xFFFFFF
Fixed
value
0x02 0x03
CurrNwkID
R
0x01
0..63, 255
Current Value
0x02 0x04
CurrFreqBand
R
0x01
0..2, 255
Current Value
0x02 0x05
LinkStatus
R
0x01 0..5 Current
status
0x02 0x06
RemoteSlotSize
R
0x01 0..109
Current
Value
0x02 0x07
SlotNumber
R
0x01 0..7
Current
Value
0x02 0x08
HardwareVersion
R
0x01
0x41..0x5A
0x43 = Rev “C”
0x02 0x09
FirmwareVersion
R
0x01
0x00..0xFF
Current FW load
0x02 0x0A
FirmwareBuildNum R
0x02
0..65535
Current FW load
0x02 0x0C
FirmwareBuildDate R
0x03
BCD (“YYMMDD”)
Current FW load
0x02 0x0F
FirmwareBuildTime R
0x03
BCD (“HHMMSS”)
Current FW load
0x02 0x12
RssiIdle
R
0x01 -128..127
Current
Value
0x02 0x13
RssiLast
R
0x01 -128..127
Current
Value
0x02 0x14
AvgBeaconPower
R
0x01 -128..127
Current
Value
0x02 0x15
ParentMacAddress R
0x03 0..0xFFFFFF
Current
Value
0x02 0x18
ModelNumber
R
1 0x90 indicates
DNT90
Table 7.4.3.1