mftoolkit Issue Tracker Rss Feed

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

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.

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?

Closed Issue: XBee crash when checksum error [10945]

jcsaez — Wed, 08 Jun 2011 16:28:43 GMT

Duplicated

Created Issue: XBee crash when checksum error [10945]

jcsaez — Thu, 19 May 2011 17:34:52 GMT

Created Issue: XBee crash when checksum error [10944]

jcsaez — Thu, 19 May 2011 17:34:30 GMT

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

CapnBry — Wed, 09 Mar 2011 20:41:29 GMT

Created Issue: Is C6820 library actually working? [9951]

innovactive — Sat, 27 Nov 2010 07:24:01 GMT

Hi. We tried to drive a C6820 module using mftoolkit library, but it seems that something is wrong in sources.

First of all, we couldn't find any _serialport.Open() call.

We also noted that _serialport.ReadTimeout is set where it cannot be set, since even opening serialport on C6820 ctor, such property has to be set before opening port, but it could be an issue due to a different behavior of MF 4.1.

Does anybody ever tried to use this library with a real C6820 module?

Commented Issue: changed OnPacketReceived to FrameReceived not in DLL?? [8201]

Ophoopfansegen — Tue, 09 Nov 2010 04:18:40 GMT

I just started a new project using XBee. I am sending a message from a
xbee connected to an arduino microcontroller to a xbee connected to my
laptop.

I am writing the laptop application in C#, and am using this library for it.
I've allready established a connection succesfully. I've got an OnPacketReceived
handler, but for every message that is send to the xbee connected to C# I
get the following message in my Console:
"Could not handle API message 129";

First of all I would like to know what this message means exactly (129??). I went
to checkout the documentation (Source Code -> Browse). There I found that the
OnPacketReceived handler was changed to FrameReceived. When I check the
dll I am using OnPacketReceived is still in there, and FrameReceived isn't. How come?
I've got the most recent dll I can download here.

I hope someone can give me some usefull information.

Greetings Ophoopfansegen
Comments: ** Comment from web user: Ophoopfansegen **

It's been a long time since I worked with this project.

We managed to fix our problems, allthough the performance of the library was very bad when
handeling a lot of messages. Instead of the published dll we used the available source code and
made some changes to the library and created a dll ourselves. We also made som changes in the
library regarding the performance issues, it improved a bit but still not completely fluent.

I can't remember what issues we ran into exactly or what we changed. I can include an attachment
of the source code of the zigbee library as we changed it. You can check what changes we made
as improvements.

Closed Issue: HTTPS/SSL implementation [4293]

interactive — Mon, 08 Nov 2010 12:50:39 GMT

Hi Michael,

I'm trying to get HTTPS/SSL working in netmf. I know the emulator does not support SSL, and it is available as a library. Do you have any plans to implement SSL?

Cheers,

Armand
Comments:

SSL will not be available in the future, sorry.

Closed Issue: ZigBee : AtCommand ctor does not allow to set register? [4218]

interactive — Mon, 08 Nov 2010 12:46:51 GMT

I think that public constructor "public AtCommand(string command, byte[] value)" misses in its implemetation of following assignment: "this.Value = value;".

Without it every AT command that tries to set a register fails, since it is given back the current register value.

Same issue arises even when using AtRemoteCommand's ctors that use the aforementioned ATCommand ctor.

I suspect that another issue could arise in CheckFrame() method of XBee class, since it does'n manage correctly responses about Api types other than AtCommandResponse (i.e AtRemoteCommandResponse or ZigBeeTransmitStatus).
Comments: Resolved with changeset 59005.

Closed Issue: HttpRequest.ReadSocket method spinning [4318]

interactive — Mon, 08 Nov 2010 12:41:27 GMT

Hi, First of all, thank you very much for your effort and great work on this toolkit. I am using the latest released source (23728) and have a WebServer using HttpService (non-MF) with an ajax type method that I'm calling from within a timer in IE7 using jQuery, which recurs at about 2 second rate. After about 1000 to 2000 such requests, the server appears to melt down with many "Client Worker Process" threads spinning inside HttpRequest.ReadSocket(). - In this case spinning with the first while(true) loop in the method, at line 404 -- if(avail == 0) { continue (with a commented // Thread.Sleep(10);

I suspect that the connection went bad, or IE7 got sick and the socket.Poll() method did not detect the problem, so the thread kept spinning in a tight loop - with no mechanism to see the problem. I'm wondering if anyone else has seen this and has any suggestions for a fix or hack? Was wondering about a DateTime.Now type timeout on the loop that would either throw an exception or similar? I do believe that the client or network is somehow causing the original problem, but I see this as a robustness issue with the server.

I believe that I've seen a similar behavior on the MF version of my server as well, but am not sure.

Again, thanks for the great work and thanks in advance for comments or advice.

Don
Comments: Resolved with changeset 59004.

Closed Issue: XBeeAddress64.Value returns incorrect value [6894]

interactive — Mon, 08 Nov 2010 12:37:50 GMT

The get accessor for XBeeAddress64.Value is incorrect. My SH is 0x0013A200 and SL is 0x40318112. The returned value is 0x40452312, but it should be 0x0013A20040318112.

Currently the accessor is implemented like this: get { return (ulong)(_msb << 32) + _lsb; }

But correct would be get { return ((ulong)_msb << 32) + _lsb; }
Comments: Resolved with changeset 59003.

Commented Issue: changed OnPacketReceived to FrameReceived not in DLL?? [8201]

interactive — Mon, 08 Nov 2010 12:34:38 GMT

Hi velias,

could you please send me an example how you get the error message for API type 129?

Regards,
Michael

Closed Issue: XBEE "+++" to get into AT Command mode not working? [7436]

interactive — Sat, 06 Nov 2010 19:16:19 GMT

It seems like it sends a 0x0d after the "+++" string to get into transparent mode and waits for an "OK" back.
I've noticed, at least with the XBEE pro 802.15.14 OEM modules that I use, they don't like the 0x0d after the +++ and will not return an OK.
I can test this with hyperterminal by typing a +++ with carriage returns enabled so it gets the "+++" 0x0d and no OK is sent back from my XBEE module.
When I type a simple "+++" and nothing else, it does return the OK

I'm not sure if this is a issue with the XBEE module or it's firmware revision or maybe it was worked that way with older XBEE firmware (I'm using 10E6)
Has anyone else noticed this?
Comments:

Commented Issue: XBEE "+++" to get into AT Command mode not working? [7436]

interactive — Sat, 06 Nov 2010 19:16:04 GMT

New release published.

Closed Issue: compil with .net 1.1 [8412]

interactive — Sat, 06 Nov 2010 19:07:46 GMT

My aim is to compile Zigbee's project to .Net 1.1.

I use Visual Studio 2008 and modify it (http://devlicio.us/blogs/ziemowit_skowronski/archive/2008/08/22/working-with-net-1-1-in-visual-studio-2008-and-team-server.aspx)
I obtain Xbee.dll but i used this dll's file it it a message indicate that it's version 2.0.

There are solution to compile Zigbee project to .net 1.1

Thanks.
Comments:

Will not be supported by author.

Commented Issue: compil with .net 1.1 [8412]

interactive — Sat, 06 Nov 2010 19:07:12 GMT

Well, you need to change some parts of the source code to get it running with older frameworks.

Michael