To better assist you with imaging requirements of this highly customizable system, the table below is provided for specific driver and device association. This document describes the modules that are supported on Embedded PC Platforms and the corresponding Linux and Windows 10 OS driver modules associated with each of the hardware modules in the Embedded PC.
Linux drivers are integrated with the Linux OS images that are supported for the platform and are available upstream. To better assist you with imaging, the following matrix describes the requirements of this highly customizable system and illustrate the specific driver and device association:.
Linux and Windows 10 OS driver modules. Use the following steps to install the Telegesis ZigBee drivers: 1. All trademarks, registered trademarks and products names are the sole property of their respective. All information is correct at time of issue.
Telegesis UK. The default S-register settings lead to a network that is easy to set up and to which extra devices. Not only can malicious devices intrude themselves,. The use of a. More specific applications such as Smart Energy. The default register settings produce the following behaviour when a device establishes a PAN.
A sniffer can now no longer read the Network Key and use it to decrypt your messages, because. You can choose a Network Key and write it into S08 in the coordinator, but there is not much point. The other devices ignore S08 as they receive the key from the coordinator, and if the. A pre-defined Network. The process of bootloading an application file through the serial port or over the air is described. For convenience the main points are. Other terminal applications can be used. In order to upgrade the firmware of the ETRX35x module using the serial bootloader, issue the.
After entering the bootloader, the connection parameters need to be changed to bps, 8. After checking that the. When the transfer has been completed successfully, press Enter again in order to return to the. If the application. Selecting option 2 instead of option 1 just runs the existing firmware without any changes. It is. R AT Commands With a few excepti. R AT Commands 4. R AT Commands Figure 4. File Tra. Integration into a wide range of applications is made easy using a simple AT -style software interface and advanced hardware design.
No RF experience or expertise is required to add this powerful wireless networking capability to your products. Telegesis ZigBee Modules fast integration opportunities and the shortest possible time to market for your product. The Development Kit Product Manual s contain all of the information required to set up your development kit and run firmware upgrades where necessary. There do not have to be any routers other than the coordinator, which functions as a router or end devices in any given network.
Each router can support up to 16 end devices 6 on the ETRX3 series in any combination of non-sleepy, sleepy and mobile End Devices. The network is always formed as a mesh according to the ZigBee PRO featureset of the ZigBee standard; the tree structure is not available. By default the module joins a PAN as a router, but modifying register S0A allows you to define it as an end device.
The coordinator is simply the device that first establishes the PAN, and it should not be allowed to leave the PAN as it is not possible for a node that is already joined to the PAN to take over the role of a coordinator or Trust Centre. This certification includes tests guaranteeing that: - Modules running the Telegesis AT - Command set will not interfere with existing ZigBee Networks in a malicious way - Modules running the Telegesis AT - Command set can join a 3rd party ZigBee PRO network and use its routing capabilities - Modules running the Telegesis AT - Command set can allow 3rd party nodes to join into a network consisting of Telegesis nodes and use its routing capabilities In addition to implementing a manufacturer specific application profile the AT - Command set allows for transparency allowing communication with 3 rd party nodes running any public application profile.
In addition to this a transparent endpoint has been added allowing a host processor to implement any public application profile in fully transparent mode. If you want to use the term ZigBee or the ZigBee Logo in your product documentation the current regulations state that you have to i Be at least an adopting member of the ZigBee Alliance in the year you release your product ii Implement a public application profile If you intend to get your product certified feel free to contact Telegesis for additional information.
Also if you intend to build a product compliant to a public application profile e. Home Automation, Smart Energy feel free to contact us to discuss your options. R2xx firmware will not run on the ETRX3 series of modules. If unused the pad can be left floating and a pull-up is not required.
Interoperability with other devices that use the ZigBee PRO featureset is limited to a number of transparent commands. Also, it is not compatible with the ZigBee Smart Energy profile as it lacks the required security key. It will still be a member of its original PAN, assuming that PAN still exists, though an end device may need to find a new parent and it may have missed an update of the network key.
Any data not following this pattern is either not accepted by the module or will cause an error message in response. Every command must be terminated with a , they cannot be concatenated. Example: AT S00? Any data which is prompted to the user is delivered in the format. Unless disabled in S0E or S0F prompts may appear whenever the corresponding event occurs.
Example: A prompt intersecting a command being entered will not affect the command itself. Optional hardware handshaking can be enabled as described in the register description of S12 in section 4. This command executes routines of the module and returns parameters Table 1: Types of AT commands When bit 7 of S12 is set each individual reply or prompt is additionally started with the STX and ended with the ETX character to aid the interpretation of the incoming strings on a host processor.
Optional parameters are marked with square brackets […]. XX 8-bit hexadecimal number. Most of the prompts can be disabled using register S0E and S0F. Only end devices should be put into a low-power state because routers and the coordinator must always be powered up to maintain the network connectivity. ZigBee End Devices do not poll for data, instead their incoming messages are relayed immediately by their parent without being buffered.
This means that ZEDs must not be put into a sleep mode. When a node is defined as a sink by setting S10 bit 4, it can broadcast its address to the rest of the network. This simplifies the application software since it is not necessary to know the EUI64 of the sink in advance.
To reduce traffic to end devices they do not receive the advertisement broadcasts, but will be informed of the sink address when they join the PAN. Otherwise, you should set bit 8 of S10 on end devices. This is flashed on to the chip at manufacture and cannot be changed by the user. This is allocated to the device when it joins the PAN and cannot be changed or preset, except that 0x is always the coordinator. It is analagous to a temporary IP address.
Entry FE causes a search of the table for the first entry whose source endpoint and cluster ID matches registers S40 and S In many commands address FF represents the local device.
This does not affect the functionality of the module. A description of the bootloading process can be found in the Development Kit Product Manual. Please note that the bootloader will run at a baudrate of k2, no parity, 8 data bits regardless of the current serial port settings.
A description of the cloning process can be found in the Development Kit Product Manual. This command clones the firmware of the local node to a remote node within the same PAN, whose address is given by. After completion a soft reset is caused on the remote end. A description of the passthrough process can be found in the Development Kit Product Manual ; it is the same procedure as cloning.
In case the target device has been reset channel 13 must be used for recovering. For more information on over-the-air firmware upgrading please refer to the Development Kit Manual. Examples AT S00? AT S0AE? AT S? XX is the S-Register which is to be read. As an option for all 16 bit registers it is also possible to address an individual bit only by specifying the bit number [x]. All and bit registers can also be accessed bit by bit.
In order to do this [x[x]] may specify the bit which is to be read. The result when reading a single bit will always be 0 or 1. See S-Register description for details. Some S-Registers are read-only and will return an error if you are trying to write to them. When writing an individual bit by specifying [x[x]], can only be either 0 or 1. The data is written to S-register number XX and if applicable stored in non-volatile memory. The data format for each individual S Register is given in the S-Register description.
For all and bit registers individual bits can also be set or cleared by specifying the bit using hexadecimal [x[x]] and setting it to either 0 or 1. As an option for all 16 bit registers it is also possible to address an individual bit only by specifying the bit number [X].
For all 32 bit registers it is possible to address an individual bit by specifying the bit number in hexadecimal [xx] The result when reading a single bit will always be 0 or 1. Note: Also the local node can be the target of this command e.
The contents of the remote S-Register are following in case of a successful read only. As an option for all and bit registers it is also possible to address an individual bit only by specifying the bit number [x[x]]. Only in case the errorcode is 00 the write operation has been completed successfully. Notes Some S-Registers require a password for write access.
Some S-Registers are read-only and cannot be written to. You cannot display all the registers of a remote device. The data format for each individual S Register is given in the S-Register description in section 4. XX represents the average energy on the respective channel see description in Section 8. Channels masked out in S00 are not scanned. The node gives a list of all PANs found. The node does not join any of the seconds.
PANs found. Note When issuing this command the local device becomes a Coordinator and Trust Centre. Establishing a PAN can take up to 16 seconds. This command can only be executed if the local node is not part of a PAN already. The local node becomes a coordinator and performs an energy scan on all channels selected in S The local node scans all channels selected in register S00 for the existence of a PAN. All data required to enter the network is provided to the node, so that no joining procedure itself is required.
The node will appear in the target network without any joining procedure given the supplied data is correct. It is assumed that the key-sequencenumber of the network key is 0 when issuing this command. Instruct local device to leave the PAN. It will not be able to rejoin the PAN represents the error code explained in section 3. Instruct device to leave the PAN. Can be used to find the identity of all ZigBee devices in the network including non- Telegesis devices.
Prompt example NTable:, Length No. In case the table contains more than three entries it may be required to repeat this command and increase the index count until the full table is derived. In case of an error an errorcode other than 00 will be displayed and the prompt will end after the errorcode. Prompt example RTable:, Length No.
Dest Next Status When the table contains more than the displayed entries it may be required to repeat this command and increase the index count until the full table is derived.
The status shown is as described in table 2. In case an index number is provided, an extended response is requested asking the remote device to list its associated devices ie children. Prompt AddrResp:[,,] [nn. In case an extended addresses the local node response has been requested the requested NodeIDs from the associated devices list are listed as well.
XX is an optional index number. Prompt AddrResp:[,,] [dd. In case an extended response has been requested the requested NodeIDs from the associated devices list are listed. In addition the node descriptor is displayed. The individual fields of the Node Descriptor are described in section 2. In addition the power descriptor is displayed as a 16 bit hexadecimal number as described in section 2. In addition all active endpoints are listed as 8-bit hexadecimal numbers separated by commas.
In addition all active endpoints are listed as 8 bit hexadecimal numbers separated by commas. If a remote node has a matching ProfileID and matches at least one of the specified clusters it will respond to this broadcast listing the matching endpoint s. Prompt MatchDesc:,,XX,… In case of an error an errorcode other than 00 will be displayed and the prompt will end after the errorcode.
In addition all endpoints of this node matching the search criterion are listed as 8 bit hexadecimal numbers separated by commas.
For a description of the LQI reading please see section 7. Stores route information for up to 30 hops which will be used when sending any message to a remote node, which is part of the listed devices. Furthermore functionality and make use of this command. Source route messages may also be displayed. Can only be used if no other device in the network is Trust Centre i.
By default the COO is the Network Manager, but any other router in the network can take over this responsibility. Ideally S00 should be identical for all nodes on a network. The user can overwrite it to manually select a different sink.
The address table is volatile and its contents are lost if the device is powered down. The Address Table contains nodes which can be addressed by referring to the corresponding address table entry.
Response No. ID EP 00 01 01 00 02 00 03 00 04 00 OK The multicast table contains all multicast IDs which The multicast table is cleared by a reset will be received by the local node.
For the AT - Command interface operation the endpoint should always be set to Parameters nn ranging from 00 to 30 Note: Use broadcasts sparingly!
The ZigBee specification only allows any node to repeat or originate up to 8 broadcasts in every 8 second interval. Broadcasts use a lot of bandwidth. A maximum of 82 bytes are sent with attached EUI only 74 bytes. The response OK shows successful transmission. Successful transmission does not guarantee successful reception. To make sure data has been received by a specific node use a unicast message. Only neighbours which are up to nn hops away will receive the broadcast.
Use on All Devices Note This command is particularly useful if the data may contain and characters. In case bit 9 of S10 is set a timeout error is generated if no character is received for 1 second. Parameters XX ranging from 00 to 52 hexadecimal nn ranging from 00 to 30 decimal A maximum of 82 bytes are sent with attached EUI only 74 bytes. The maximum payload is 82 bytes.
It is reduced by 8 bytes when appending the EUI to the network header default and also it is reduced by 2 bytes per hop in case a source route is known. The latter event can neither be suppressed nor foreseen. A NACK does not guarantee that the message has not reached its destination. Use on All Devices Notes This command is particularly useful if the data may contain and characters.
Up to 82 bytes are sent to the node with address. Use on All Devices Notes - When bit 8 of S10 is set, if a sink cannot be reached for three consecutive transmissions the sink is assumed unavailable and a new one is sought. By default, if a sink is already known and no better sink is found, no prompt will be displayed. A sink which is already known can be found at index 05 of the address table. They are a form of broadcast so any node may only repeat or originate up to 8 multicasts in every 8 second interval.
Where represents the error code explained in section 3. Parameters nn ranging from 00 to 30 Up to 82 bytes are sent to the multicast group.
Instead of a bit multicast ID an 8 bit binding table entry can be specified. Use multicasts sparingly!
Parameters XX ranging from 00 to 52 hex nn ranging from 00 to 30 Up to 82 bytes are sent to devices up to nn hops away. Only if the errorcode equals 0 the data mode will open. Plays a tune on a remote devboard if the Beeper is connected.
Useful to identify remote nodes. See devkit manual for details about connecting a buzzer to the ETRXn. The application needs to handle addressing, error checking, retries and acknowledgements. End Devices do not receive raw data. Raw data will only travel one hop. Use with great care.
0コメント