MDEV-868-PRC datasheet(14/55 Pages) LINX

14 / 55 page

–

Addressing Modes

The module has very flexible addressing methods selected with the

ADDMODE register. It can be changed during operation. The transmitting

module addresses packets according to the addressing mode

configuration. The receiving module processes all addressing types

regardless of the ADDMODE configuration. If the received message

matches the addressing criteria, it is output on the UART. Otherwise it is

discarded. The ADDMODE configuration also enables assured delivery.

There are three addressing modes: DSN, User and Extended User. Each

mode offers different communications methods, but all use source and

destination addressing. The source address is for the transmitting unit,

the destination address is the intended receiver. Each mode uses different

registers for both the source and destination addresses.

Extended User Addressing mode uses the four user destination address

bytes (UDESTID[3-0]) as a destination address. The module’s local address

is contained in the four user source ID registers (USRCID[3-0]).

In normal operation, each module has a user ID mask (UMASK[3-0]) that

splits the 32 address bits into up to three fields to provide a network

address and address fields for sub-networks, supporting both individual

addressing and broadcast addressing within the user’s network.

The HumPRCTM Series is normally configured using the Join Process,

which sets the addressing mode to Extended User mode. The other modes

would normally only be used if the HumPRCTM Series is being implemented

in a mixed system that also uses the HumPROTM Series modules.

Please see the HumPROTM Series data guide for a description of the

other addressing modes. A detailed explanation and examples for each

addressing mode are given in Reference Guide RG-00105.

Reading the Transmitter Address

The HumPRCTM Series modules do not require any software for basic

operation. There is no compiler to get, no code to write and download into

the module. However, the built-in Command Data Interface (CDI) can be

used to add additional or advanced functionality to a system.

One such feature is the ability to read out of the receiver the identity of the

transmitter that sent the commands. This allows an external processor to

log access attempts or set additional controls over which transmitters are

allowed to activate the product outside of the module.

By default, the module automatically configures itself to respond to the

transmitting module (AUTOADDR = 0x07). This configuration takes the

source address from the received packet and writes it to the UDESTID

registers UDESTID[0-3]. Reading these registers after a valid transmission

has been received indicates the transmitter that sent the command.

Restore Factory Defaults

The transceiver is reset to factory default by taking the PB line high briefly

4 times, then holding PB high for more than 3 seconds. Each brief interval

must be high 0.1 to 2 seconds and low 0.1 to 2 seconds. (1 second

nominal high / low cycle). The sequence helps prevent accidental resets.

Once the sequence is recognized, the MODE_IND line blinks in groups

of three until the PB line goes low. After PB goes low, the non-volatile

configurations are set to the factory default values and the module is

restarted. The default UART data rate is 9,600bps.

If the timing on PB does not match the limits, the sequence is ignored.

Another attempt can be made after lowering PB for at least 3 seconds.

MDEV-868-PRC Datasheet(PDF) 14 Page - Linx Technologies

MDEV-868-PRC Datasheet(HTML) 14 Page - Linx Technologies

Html Pages

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55

Datasheet Download

Link URL