Code Categories

TOP Contributors

MIKROE (2762 codes)
Alcides Ramos (374 codes)
Shawon Shahryiar (307 codes)
jm_palomino (118 codes)
Bugz Bensce (90 codes)
S P (73 codes)
dany (71 codes)
MikroBUS.NET Team (35 codes)
NART SCHINACKOW (34 codes)
Armstrong Subero (27 codes)

Most Downloaded

Timer Calculator (139250 times)
FAT32 Library (71746 times)
Network Ethernet Library (57120 times)
USB Device Library (47429 times)
Network WiFi Library (43082 times)
FT800 Library (42403 times)
GSM click (29835 times)
mikroSDK (28074 times)
PID Library (26885 times)
microSD click (26198 times)

Package Manager

We strongly encourage users to use Package manager for sharing their code on Libstock website, because it boosts your efficiency and leaves the end user with no room for error. [more info]

< Back

Digimesh XBee PRO API mode interfacing

Rating:

Author: Pavol alias LQd

Last Updated: 2013-03-22

Package Version: 1.0.0.0

Category: ZigBee

Downloaded: 1354 times

Not followed.

License: MIT license

This library presents a bridge for interfacing XBee PRO modules in powerful but somewhat complicated API mode. Written in mB for AVR, but contains almost no AVR specifics.

I am ready to answer questions. Description in source code.

Do you want to subscribe in order to receive notifications regarding "Digimesh XBee PRO API mode interfacing" changes.

Do you want to unsubscribe in order to stop receiving notifications regarding "Digimesh XBee PRO API mode interfacing" changes.

Do you want to report abuse regarding "Digimesh XBee PRO API mode interfacing".

Information
Comments (3)

Download All [18.52KB]

DOWNLOAD LINK	RELATED COMPILER	CONTAINS
1362766698_digimesh_xbee_ap_mikrobasic_avr.zip [18.59KB]	mikroBasic PRO for AVR	lib src exa hlp hex sch pcb doc

Library Blog

This library presents a bridge for interfacing XBee PRO modules in powerful

but somewhat complicated API mode.

So far it implements:

XBee_TX
XBee_rx
XBee_AT_Command
XBee_AT_command_response
XBee_modem_status
XBee_transmit_status
XBee_receive_packet
Xbee_remote_command_response

This is not complete command set, it was written for another big project mainly,

so I have made what I was needed. Code was tested and successfully is working

about a year in few devices, so should be mainly OK. It is somewhat commented

but I have no time for writing help and example project, so it is as it is.

But I am ready to answer questions.

Packets are sent through XBee_TX function, command are made through calling

XBee_AT_command and response for the command will be picked up through calling XBee_rx which will then call user defined XBee_AT_command_response, general reception is made by periodically calling XBee_rx function. So it works like that, user call XBee_rx and this routine will check for new messages, will pick them up if any and decompose it to parameters and data passed to appropriate user defined routine depending on type of message.

Library accomodates hardware handshaking, so XBee module

is not transmitting serial data to uC as it comes, but is asked for data

by calling XBee_rx (thus this should be done as often as possible, modules

has some buffer, but if multiple packets will not be collected, some data

could be lost), this function returns status (no incoming data,

reception error...) and will call (and pass received data to) user defined

routines for handling incoming packet of certain type if any.

ALSO FROM THIS AUTHOR

Hex string to value

Converts HEX strings to value, from single chars through bytes to words and longwords. Written in mB for AVR but no AVR specifics used, so it should be fully multi platform usable.

[Learn More]

Circular buffer by LQd

Simple ready to use implementation of FirstIn-FrstOut type buffer for general use. Size can be easily adjusted as well as type of stored data. Current depth signalization available. Perfect for interrupt-driven receiving... Written in mB for AVR but no AVR speciffics used, just pure basic.

[Learn More]

Fast HD44780 8bit by LQd

Library for driving HD44780 in 8bit mode, purpose was to achieve maximal possible speed and library is optimized for this. May be you will need to tweak some waiting routines based on clock frequency of uP and used controller, some of them may not meet datasheet specification.

[Learn More]