.NET Micro Framework Toolkit

Commented Issue: NodeIdentifier returns with the first character missing [12911]

WeegieBoy — Thu, 09 May 2013 12:13:21 GMT

I have noticed that if I set a NI in the Zigbee module and do a node indentifier search, I always get back the NODE ID string missing the first character.

Eg, I set NI in the module to WATTAGE and when a search and then read NodeIdentifier I see ATTAGE. This is repeatable with all Zigbee modules I have.

I am using XBP24BZ7 modules.
Comments: ** Comment from web user: WeegieBoy **

As a follow up, it looks like the software is decoding the signal strength from the packet.

Looking at the Digi documentation, this byte is not in the packet.

By commenting out this line in NodeDiscover.cs the code now decodes the string identifier correctly.

Created Issue: NodeIdentifier returns with the first character missing [12911]

WeegieBoy — Thu, 09 May 2013 09:57:07 GMT

Source code checked in, #81799

Project Collection Service Accounts — Mon, 01 Oct 2012 21:57:23 GMT

Upgrade: New Version of LabDefaultTemplate.xaml. To upgrade your build definitions, please visit the following link: http://go.microsoft.com/fwlink/?LinkId=254563

Source code checked in, #81798

Project Collection Service Accounts — Mon, 01 Oct 2012 21:51:05 GMT

Checked in by server upgrade

Source code checked in, #77811

interactive — Wed, 23 May 2012 18:23:41 GMT

fixed some small bugs in Pop3/Smtp

Source code checked in, #77646

interactive — Thu, 17 May 2012 18:22:23 GMT

Patch Applied: #7583

jcsaez — Sat, 28 Apr 2012 19:08:00 GMT

jcsaez has applied patch #7583.

Comment:
Applied on 76819

Patch Applied: #9438

jcsaez — Sat, 28 Apr 2012 19:07:46 GMT

jcsaez has applied patch #9438.

Comment:
Applied on 76819 changeset

Patch Applied: #10635

jcsaez — Sat, 28 Apr 2012 19:07:14 GMT

jcsaez has applied patch #10635.

Comment:
Applied on 76819 changeset

Closed Issue: XBee crash when checksum error [10944]

jcsaez — Sat, 28 Apr 2012 19:05:25 GMT

I was dealing with this problem a little time and finally found the source. In XBee.cs class, private void ReceiveData() method, private MemoryStream _readBuffer didn't discart fake frames when checksum error. The thread still received data and drove _readBuffer "outofmemory".

I have solved checking length and checksum separately, with new GetLenth() and Checksum() methods, and some corrections in do{} while block.

Find attached the new XBee.cs for testing
Comments: Resuelto con el conjunto de cambios 76819.

Closed Issue: XBeeAddress64.Value setter masks out bytes [10320]

jcsaez — Sat, 28 Apr 2012 19:05:20 GMT

The XBeeAddress64 class's Value property masks out the high word of the LSB half of the address.
var x64 = new XBeeAddress64(0x1234567812345678)
generates an address of 0x1234567800005678

This is because the Value setter:
_lsb = (uint)(value & 0xFFFF);
should be
_lsb = (uint)(value & 0xFFFFFFFF);

Off topic, but having Equals() overrides are great too:

public override bool Equals(object obj)
{
XBeeAddress64 that = obj as XBeeAddress64;
return (that != null) && that._msb == this._msb &&that._lsb == this._lsb;
}

public override int GetHashCode()
{
return (int)_lsb;
}
Comments: Resuelto con el conjunto de cambios 76819.

Source code checked in, #76819

jcsaez — Sat, 28 Apr 2012 19:05:16 GMT

Some proposed patches applied. Working correctly.

Commented Issue: XBee crash when checksum error [10944]

hellokitty9999 — Thu, 09 Feb 2012 06:24:34 GMT

Hi, may I know how this program works?

New Post: XBEE Series 2

tdragger — Sat, 21 Jan 2012 14:15:58 GMT

I'm pretty new with XBee but my understanding is that once you configure the modem to use the API you cannot send it AT commands. Have you tried configuring it using Router AT to see if it responds?

New Post: ZCL Support

awaiK — Fri, 20 Jan 2012 15:21:59 GMT

Hi,

is there a document which describe the commands supported by Digi' XBee devices?

New Post: XBEE Series 2

ipq — Tue, 03 Jan 2012 13:08:40 GMT

Hi!

I've been racking my brains with a strange issue since one week.

I have a XBEE S2 configured in API mode as a ROUTER (FW 23A0) attached to a Netduino Plus through COM2.

The issue is that every time I try to send a command to the module I get no answer (but I can receive), instead, I get a timeout. I've debugged the code until reaching the point where line serialport.write(bytes[],0,bytes.lenght) in xbee.cs (within function ExecuteNonQuery(XBeeRequest request)) is executed unsuccessfully. (BTW the method serial_port.isopen() is true )

I have checked the the content of bytes[] and is correct, moreover I've sent them successfully using X-CTU.

Is there any option in the constructor I missed?

I've tryed the following:

XBeeModule myXbee = new XBeeModule(SerialPorts.COM2, 9600, ApiType.Enabled);

//I have even tryed to use class XBee instead of XBeeModule!!! -> same result!

//and setting parity, stopbytes and etc. -> no result!

myXbee.FrameReceived += new FrameReceivedEventHandler(myXbee_FrameReceived);

myXbee.ModemStatusChanged += new ModemStatusChangedEventHandler(myXbee_ModemStatusChanged);

myXbee.Open();

And in another method I call: myXbee.Execute(new AtCommand("MY"));

Then...fatality! Timeout!

I know the module is well configured because I wrote the code by myself and the module was answering.

It's a pity...hope somebody has a clue to figure out where's the mistake:(

Thanks and happy new year!!!

Reviewed: Release 10.11.8 (Dec 11, 2011)

laith928 — Mon, 12 Dec 2011 06:42:50 GMT

Rated 3 Stars (out of 5) - have not used it yet.

New Post: xbee receiving samples from end device

hillaerts — Mon, 07 Nov 2011 22:27:50 GMT

Hi,

I got one xbee ("slave") configured to send sample data every 5 seconds to a second xbee ("master"). I see activity on the usb explorer board of the master every 5 seconds but the event FrameReceived is never triggered. Directly using the SerialPort class does work, every 5 seconds I'm receiving data. If I execute a remote AT command from the master to the slave then the FrameReceived event is triggered with the data from the slave.

Should receiving sample data from the slave be handled in a different way?

BTW, I'm using XBee's Series 1.

Thanks,

Steven

Patch Uploaded: #10635

jcsaez — Wed, 19 Oct 2011 17:14:59 GMT

jcsaez has uploaded a patch.

Description:
As CapnBry said:
" The XBeeAddress64 class's Value property masks out the high word of the LSB half of the address.
var x64 = new XBeeAddress64(0x1234567812345678)
generates an address of 0x1234567800005678

This is because the Value setter:
_lsb = (uint)(value & 0xFFFF);
should be
_lsb = (uint)(value & 0xFFFFFFFF);
"

File for patch upload

New Post: MFSnmp

juliusfriedman — Thu, 29 Sep 2011 19:42:36 GMT

I have released a preview version of this library at the above link which is in the Net MF Issue Tracker..

http://netmf.codeplex.com/workitem/1232

Please post all feedback in that thread.