Giter Site home page Giter Site logo

xbee-api's People

Contributors

andrewrapp avatar

xbee-api's Issues

Implementing SE Profile: Joining PAN via Encrypted Comms

Greetings,

I am working on setting up a ZigBee SE experiment. So far I have been able to 
successfully implement the Link Key establishment mechanism to include the 
validation of an Installation code with CRC and MMO for generating the Link 
Key, assigning the link key to the SED and providing the link key to the 
coordinator in anticipation of a Join Request. Now, I wanted to know if there 
is a way to send a join request between an XBEE-S2 setup using the Coordinator 
API Function set under XB24-ZB FW: 21A7 and an XBEE-S2 setup using the Router 
API Function Set under XB24-ZB FW: 23A7. I was under the impression that once 
the Link Key was generated and written to both the Coordinator and the 
Router/SED that the XBEE firmware would take over from there and automatically 
send an encrypted join request to the Coordinator using the Link Key who would 
in turn decrypt, verify and send the Network key encrypted using the link key 
to the Router/SED who would then decrypt, assign to itself and start comms. But 
clearly this is not the case because neither the MicroChip Sniffer or the Atmel 
RZUSBSTICK with the killerbee firmware piping traffic through a named piped to 
Wireshark detect anything other than a broadcast from the coordinator.  

I've looked through the XBEE-API and I haven't found anything that would 
facilitate initiating a join request to the coordinator; or maybe I have over 
looked it.

Has anyone using a similar scenario I described above successfully joined a 
Router/SED to a Pan using encrypted comms?

Thanks in advance.

Original issue reported on code.google.com by [email protected] on 29 Mar 2013 at 2:59

StackOverflowError at com.rapplogic.xbee.api.wpan.IoSample.isD7On

Sorry, I use a machine translation.

What steps will reproduce the problem?
1. I tried to execute Examples(Receive I/O samples from a remote 802.15.4
XBee) of Project Home. 

What do you see instead?
Exception in thread "XBee Packet Parser Thread" java.lang.StackOverflowError
    at com.rapplogic.xbee.api.wpan.IoSample.isD7On(IoSample.java:175)

What version of the product are you using? On what operating system?
xbee-api-0.5 + JDK6_u11
Microsoft Windows XP Professional SP3

Please provide any additional information below.
http://code.google.com/p/xbee-api/source/browse/trunk/src/com/rapplogic/xbee/api
/wpan/IoSample.java
176:    public Boolean isD7On() {
175:        if (this.isD7On()) {
Is only here different from another?

I'm sorry. I don't know what I should write especially:(
thx.

Original issue reported on code.google.com by [email protected] on 20 Jan 2009 at 1:20

Unknown radio type

What steps will reproduce the problem?
1.used the code provided in the book "Building Wireless Sensor Networks"
2.Configured the coordinator and router accordingly.
3.Built the sensor network.
4.ran the code in Processing.

What is the expected output? What do you see instead?
the thermometers should appear and they should show the readings of the data 
sent from router to coordinator.

I see:

[2012-05-28 18:58:37,640] [Animation Thread] [WARN] 
[com.rapplogic.xbee.api.XBee] Unknown radio type (HV): 30

What version of the product are you using? On what operating system?
Xbee Pro Series 2 (s3b); Windows 7

Please provide any additional information below.

Original issue reported on code.google.com by [email protected] on 28 May 2012 at 4:06

Attachments:

xbee timeout exception in apiatexample

to use the xbee-api library and run the ApiAtExample
1.import xbee api on eclipse
2. when i do the : run as java application i got this exception:

Exception in thread "main" com.rapplogic.xbee.api.XBeeTimeoutException
   at com.rapplogic.xbee.api.XBee.sendSynchronous(XBee.java:236)
   at com.rapplogic.xbee.api.XBee.sendAtCommand(XBee.java:159)
   at com.rapplogic.xbee.examples.ApiAtTest.<init>(ApiAtTest.java:74)
   at com.rapplogic.xbee.examples.ApiAtTest.main(ApiAtTest.java:108)


I'm using Xbee 802.15.4 Serie 1 , tried the O.9 version , i got the 
xbee.sendAtcommand() with sendAtcommand stroke out , but when i tried the O.5.5 
the sendAtCommand is accepted but this exception is always there :(
please help cause i didn't get where the problem is. It's been almost a month 
that i'm trying to fix it out but no way :(


Thank you so much for responding

Original issue reported on code.google.com by [email protected] on 20 May 2013 at 1:15

New XBee Radio type

What steps will reproduce the problem?
1. Connect one of the new XBee PRO S2B radios
2. Run any of the test programs

What is the expected output? What do you see instead?
I expected: XBee radio is Series 2B Pro
I saw: Unknown radio type (HV): 30

What version of the product are you using? On what operating system?
Checkout from CVS 06-Jan-2011 / MacOS 10.6.5

Please provide any additional information below.
New XBeePRO S2B radios hardware version start with 0x1e

so I added another case statement to com.rapplogic.xbee.api.Xbee.java

                case 0x1e:
                    log.info("XBee radio is Series 2B Pro");
                    this.type = RadioType.SERIES2;
                    break;


Original issue reported on code.google.com by [email protected] on 7 Jan 2011 at 10:48

Xbee API LIBRARY: getsupplyvoltage() doesn't work correctly

What steps will reproduce the problem?
1. One Xbee is powered by two batteries AA. I have programmed the instruction 
V+FFFF in order to get in each frame the supply voltage. I send also the 
temperature I get from a PT100.
2.The other Xbee is connected to my PC using an Arduino Board(without 
microcontroller) via USB.
3.Running Processing on my computer. I use function: ioSample.getAnalog0();to 
get the temperature, values seem correct, and
data.supplyVoltage = ioSample.getSupplyVoltage(); to get the supply voltage.
Finally I post data to pachube.

What is the expected output? What do you see instead?
I expect to get the correct supply voltage of my Xbee ( usually between 2.7 and 
3.3 V, in mV), but the value it returns it is between 368  or 342...Is it 
because it returns only 3 numbers???

What version of the product are you using? On what operating system?
I use Processing 1.5.1.
Xbee Api Library: 0.5.5 and 0.9, both of them but separately.( Once at first, 
and the other once later)
Operating System: W7 64bits
Please provide any additional information below.
I contact with you because I have some problems with the library Xbee Api for 
processing, particularly with the funcion ioSample.getSupplyVoltage(); it does 
not work good, because it returns the value it is not real supply voltage. In 
fact, when I review the sample with the XCTU, I can see the correct value in 
the frame, but this value is not the same that I get with the funcion 
ioSample.getSupplyVoltage();...I don't know how it works and if there is any 
other method to measure supply voltage.
Do you know? Can you help me?
I attach you my Processing program...I hope it will help you
Thanks
Anton

Original issue reported on code.google.com by [email protected] on 7 Dec 2011 at 6:04

Attachments:

Automatic sample not recognize analog inputs, but forced sample do it

What steps will reproduce the problem?
1. set xbee to auto sample when a pin is triggered, also with an analog input
2. this is a ZNetIoSampleResponse without analog sample

What is the expected output?
a sample response with analog samples

What do you see instead?
analog mask = 0 (empty) so any analog sample is detected

What version of the product are you using?
the latest

On what operating system?
3x XBeeS2: one on a pir ad light sensor, the second one on Arduino, and the 
third on a pc with Windows.

Please provide any additional information below.
If a force a sample with IS command, the ZNetIoSampleResponse is correct: has 
the analog channel mask and values inside.


Original issue reported on code.google.com by [email protected] on 1 Dec 2014 at 10:48

Occasional XBeeParseException: Read -1 from input stream while reading packet

The issue arises when xbee-api tries to read a byte from a input stream and 
there are no bytes available. Instead of blocking it returns -1 causing the 
exception. This might be because of RXTX version mismatch.

I have attached a patch that solves this issue for me(revision info is for my 
local repository, unsure how to diff with xbee-api repository). The new code 
makes the parser wait until the needed amount of bytes is available before 
trying to read the data. It has a timeout which probably needs to be modified 
for general use cases.

What steps will reproduce the problem?
1. Send packets to local XBee from a remote XBee.
2. A few parse attempts throws XBeeParseException: Read -1..

What is the expected output? What do you see instead?
No exceptions. I see exceptions.

What version of the product are you using? On what operating system?
xbee-api-0.9.zip
WARNING:  RXTX Version mismatch
    Jar version = RXTX-2.2pre1
    native lib Version = RXTX-2.2pre2

Please provide any additional information below.
Exception example:

[ERROR] [2011-12-04] [reamThread] api.PacketParser.parsePacket - Failed due to 
exception. Returning ErrorResponse. bytes read: 0x00,0x54,...,0x0ffffffff
com.rapplogic.xbee.api.XBeeParseException: Read -1 from input stream while 
reading packet!
     at com.rapplogic.xbee.api.PacketParser.read(PacketParser.java:239)
     at com.rapplogic.xbee.api.PacketParser.read(PacketParser.java:206)
     at 
com.rapplogic.xbee.api.PacketParser.readRemainingBytes(PacketParser.java:303)
     at 
com.rapplogic.xbee.api.zigbee.ZNetRxResponse.parse(ZNetRxResponse.java:56)
     at 
com.rapplogic.xbee.api.PacketParser.parsePacket(PacketParser.java:164)
     at 
com.rapplogic.xbee.api.InputStreamThread.run(InputStreamThread.java:151)
     at java.lang.Thread.run(Thread.java:662)
[ WARN] [2011-12-04] [3-thread-1] comm.Connection.processResponse - XBee error: 
Read -1 from input stream while reading packet!
[ WARN] [2011-12-04] [reamThread] api.InputStreamThread.run - expected start 
byte but got this 0x73, discarding

Original issue reported on code.google.com by [email protected] on 4 Dec 2011 at 3:33

Attachments:

RxTx 2.2 compatibility

What steps will reproduce the problem?
1.Run Java program that uses xbee-api.

It shows that it is using 2.1, while system library is 2.2, and fails. I added 
libRXTX 2.2 files to the project and it seems to run fine, but doesn't connect 
to the device. I'm guessing something is incompatible with the newer libRXTX?

What version of the product are you using? On what operating system?

Latest version with Ubuntu 64-bit.

Original issue reported on code.google.com by [email protected] on 12 Mar 2012 at 5:51

The option in ZNetRxBaseResponse is maybe not modelled/parsed correctly

In the ZNetRxBaseResponse class the option property should not be an 
enumeration (single value) but rather a bit masked field. The way the class is 
designed it seems to indicate that it's either null, PACKET_ACKNOWLEDGED, or 
BROADCAST_PACKET. But in reality it can be PACKET_ACKNOWLEDGE and 
BROADCAST_PACKET at the same time.

Original issue reported on code.google.com by [email protected] on 20 Feb 2014 at 6:32

profileId incorrectly set in parseZNetRxResponse()

What steps will reproduce the problem?
1. Run ZNetExplicitSenderExample
2. Receive a ZigBee Explicit Rx Indicator (Frame Type:0x91)

What is the expected output? What do you see instead?
Look at the "received response" INFO message and see the profileId(msb) will be 
set to what the lsb should be and the profileId(lsb)=0x00

What version of the product are you using? On what operating system?
xbee-api-0.9.zip

Please provide any additional information below.
Typo in PacketParser.java line 344 profileId.setMsb() is used twice

            DoubleByte profileId = new DoubleByte();
            profileId.setMsb(this.read("Reading Profile Id MSB"));
            profileId.setMsb(this.read("Reading Profile Id LSB"));
            ((ZNetExplicitRxResponse)response).setProfileId(profileId);


Original issue reported on code.google.com by [email protected] on 7 Jan 2011 at 2:29

Invisible ConcurrentModificationException thrown when PacketListener removes itself

What steps will reproduce the problem?
1. Add a packetListener that prints some string and the response,
    and then removes itself (you can grab any example suitable to your env)
2. Add another packet listener that prints another string and the response
3. Communicate with a sensor.

What is the expected output? What do you see instead?
In the 1st notification, output from both packet listeners is printed; 
subsequently only the one from the second.

Instead, in the first notification, only output from the 1st pl is printed 
(after that, a swallowed CME prevents calling the second. Subsequently, the 

What version of the product are you using? On what operating system?
I'm using version f49adc0eebfe.

Please provide any additional information below.
I have created a clone containing a proposal for a fix:
https://code.google.com/r/hartmutbenz-xbeeapi/source/detail?r=a1590a02637d581267
cc3503d4ee846cc60fecc6&name=development

Original issue reported on code.google.com by [email protected] on 6 Jul 2014 at 1:37

at commands

You say to set One ZNet or ZB Pro XBee with Coordinator API firmware and then 
you write at commands to it. I cant write at commands to a xbee which I have 
set to ZNET coordinator API or ZNET coordinator router/end device. Any advice 
would be great thanks

Original issue reported on code.google.com by [email protected] on 23 Feb 2011 at 1:00

NullPointerException in ErrorResponse.toString() created from an exception

What steps will reproduce the problem?
1. run the example at 
http://code.google.com/p/xbee-api/source/browse/trunk/src/com/rapplogic/xbee/exa
mples/wpan/NodeDiscoverTest.java

2. Observe NullPointerException upon timeout expiration: 

java.lang.NullPointerException
    at com.rapplogic.xbee.api.XBeeResponse.toString(XBeeResponse.java:105)
    at com.rapplogic.xbee.api.ErrorResponse.toString(ErrorResponse.java:63)
    at java.lang.String.valueOf(String.java:2826)
    at java.lang.StringBuilder.append(StringBuilder.java:115)
    at net.sf.dz3.device.sensor.impl.xbee.XBeeDeviceFactory$1.processResponse(XBeeDeviceFactory.java:175)
    at com.rapplogic.xbee.api.XBee.handlePacket(XBee.java:284)
    at com.rapplogic.xbee.api.XBeePacketParser.newPacketNotification(XBeePacketParser.java:159)
    at com.rapplogic.xbee.api.XBeePacketParser.run(XBeePacketParser.java:121)
    at java.lang.Thread.run(Thread.java:619)

3.

What version of the product are you using? On what operating system?

Current SVN code, platform independent

Please provide any additional information below.

Patch below fixes the situation:


Index: src/com/rapplogic/xbee/api/XBeeResponse.java
===================================================================
--- src/com/rapplogic/xbee/api/XBeeResponse.java    (revision 216)
+++ src/com/rapplogic/xbee/api/XBeeResponse.java    (working copy)
@@ -102,7 +102,7 @@

    public String toString() {
        return "apiId=" + this.apiId +
-           ",length=" + length.get16BitValue() + 
+           ",length=" + (length == null ? "?" : length.get16BitValue()) + 
            ",checksum=" + ByteUtils.toBase16(checksum) +
            ",error=" + this.error;
    }

Original issue reported on code.google.com by vadim.tkachenko on 29 Jul 2010 at 4:13

Checksum computation

What steps will reproduce the problem?
1. Retrieve an actual packet.
2. Compute its checksum using Checksum object
3. Compare result with checksum in the frame

What is the expected output? What do you see instead?

The two results should be equal, and the verify method should return true.

Please provide any additional information below.

Using the full following frame 
7e.00.11.10.01.00.13.a2.00.40.56.48.7e.ff.fe.05.00.f2.00.2a.bf

We have a checksum: 0xBF

Using the Checksum object provided in the api: 
computed checksum is base10=191,base16=0xbf,base2=10111111

But then the verify method returns false.

Original issue reported on code.google.com by [email protected] on 16 Apr 2013 at 12:14

ZBTxRequest doesn't work properly on ZB S2B chips

What steps will reproduce the problem?
1. Program two arduinos (coordinator and router) with ZB examples from the 
library (receive and send).
2. Let them to associate themselves.
3. Look serial monitor for received data.

What is the expected output? What do you see instead?
The data send by the router. Nothing, the coordinator doesn't receive anything.

What version of the product are you using? On what operating system?
I'm working with ZB S2B on Arduino Mega2560, with the latest ZB library (API 
0.9).

Please provide any additional information below.
- I tried making the frames by myself and send them by x-ctu software, and it 
works fine!! Also the checksum is right. 
- Moreover, I send the handmade frame by x-ctu (from router) and I receive it 
(to coordinator). [I have problems showing the entire data, but this is my 
fault).
- In the other way, sending data with API and receiving it without it, it 
doesn't work.

I can't find what is the code problem.

Original issue reported on code.google.com by [email protected] on 17 Apr 2012 at 1:54

Delay in asynchronous request when there is an unreachable request (NO_RESPONSE)

What steps will reproduce the problem?
1. send multiple asynchronous request to two different xbees (one of them must 
not be accessible -> NO_RESPONSE)

What is the expected output? What do you see instead?
The messages to the reachable xbee should be sent immediately after the method 
call, but it has a delay of 2, 3 seconds because of the messages sent to the 
xbee out of range.

What version of the product are you using? On what operating system?
xbee-api-0.9
Ubuntu 11.04

Please provide any additional information below.
Here is a sample code for this issue:

XBee xbee = new XBee();
xbee.open("COM5", 9600);
String XBEE_OK_ADDR = "00 13 a2 00 40 61 19 11";
String XBEE_OUT_ADDR = "00 13 a2 00 40 61 19 00";
xbee.sendAsynchronous(new RemoteAtRequest(new XBeeAddress64(XBEE_OK_ADDR), 
"D4", new int[] {5}));
xbee.sendAsynchronous(new RemoteAtRequest(new XBeeAddress64(XBEE_OUT_ADDR), 
"D4", new int[] {5}));
xbee.sendAsynchronous(new RemoteAtRequest(new XBeeAddress64(XBEE_OK_ADDR), 
"D4", new int[] {4}));
xbee.sendAsynchronous(new RemoteAtRequest(new XBeeAddress64(XBEE_OUT_ADDR), 
"D4", new int[] {4}));
xbee.sendAsynchronous(new RemoteAtRequest(new XBeeAddress64(XBEE_OK_ADDR), 
"D4", new int[] {5}));
xbee.sendAsynchronous(new RemoteAtRequest(new XBeeAddress64(XBEE_OUT_ADDR), 
"D4", new int[] {5}));
xbee.sendAsynchronous(new RemoteAtRequest(new XBeeAddress64(XBEE_OK_ADDR), 
"D4", new int[] {4}));
xbee.sendAsynchronous(new RemoteAtRequest(new XBeeAddress64(XBEE_OUT_ADDR), 
"D4", new int[] {4}));

When this code runs only with the xbee in range, the IO 4 turns on/of 
immediately. But when there is a request to an xbee out of range, there is a 
delay of 2, 3 seconds to send the messages to the xbee in range. This delay 
appears to increase according to the number of NO_RESPONSE requests.


Original issue reported on code.google.com by [email protected] on 22 Aug 2011 at 8:46

Packet length greater than 255

Package: xbee-api-0.9

Problem: 
Bytes are lost when packet length > 255;

Cause:
Although the whole framework is prepared to receive packets with a length 
greater than 255, the line that prints the length to the debug log is not!

PacketParser.java #105 (#167 on trunk) :
log.debug("packet length is " + ByteUtils.formatByte(length.getLength()));

ByteUtils.formatByte() throws  IllegalArgumentException when length > 0xff.

Suggested Solution:
log.debug("packet length is " + length.getLength() + 
String.format("[0x%04X]",length.getLength()));


Attached a log showing a 268 length packet.

Original issue reported on code.google.com by [email protected] on 21 Jan 2013 at 3:28

Attachments:

Constant stream of "RXTX error in serialEvent method" log messages

What steps will reproduce the problem?
Not sure how to reproduce but if I run my application on Raspberry Pi that 
receives data every 15 seconds from a remote Arduino with XBee then I get a 
infinite loop of:
RXTX error in serialEvent method
java.io.IOException: Input/output error in nativeavailable
    at gnu.io.RXTXPort.nativeavailable(Native Method)
    ...
This causes the entire Pi to lock up when it pins the CPU.

What version of the product are you using? On what operating system?
Using f49adc0eebfe snapshot of the code.
Operating system is Raspbian which is up to date with all updates as of June.

Please provide any additional information below.

Original issue reported on code.google.com by [email protected] on 29 Jul 2014 at 12:48

Can't run xbee-api on Windows 64-bit

1: Try to run an Xbee based java project on Windows 64-bit, api 0.9 from this 
site...
2: Instead of running, it gives an error, and says the rxtx dll is 32-bit.

After trying a newer 64-bit rxtx-serial dll (the 64-bit dll found in the 
gps_0.2rc4.zip from 
http://sourceforge.net/projects/jump-pilot/files/OpenJUMP_plugins/GPS%2CCTS%20Ex
tensions/gps_0.2rc4.zip/download), it starts to run, but says device is not 
connected.

WARNING: RXTX Version mismatch
Jar version = RXTX-2.1-7
native lib Version = RXTX-2.2-20081207 Cloudhopper Build rxtx.cloudhopper.net

Later it gives an exception, java.lang.IllegalStateException: XBee is not 
connected.

Is there a good way to fix an Eclipse project to work on both 64-bit and 
32-bit? I couldn't find any help on this in the documentation...

Original issue reported on code.google.com by [email protected] on 4 Nov 2011 at 11:00

Using maximum speed of Xbee Znet

What steps will reproduce the problem?
1. Try to transmit a file (+-200Kb) to a remote Xbee.

What is the expected output? What do you see instead?
Work with 1150200 speed and the file be trasmited without corruption.

What version of the product are you using? On what operating system?
Xbee Znet 2.5

Please provide any additional information below.


Original issue reported on code.google.com by [email protected] on 18 Jul 2008 at 11:35

Line 344 in PacketParser.java; setting msb again instead of lsb

What steps will reproduce the problem?
1.Opening the file and going to line 344
2.Move the cursor over character 26
3.

What is the expected output? What do you see instead?
The profile ID msb is being set as the msb and then again as the lsb because 
the wrong method is being called

What version of the product are you using? On what operating system?
version xbee-api-0.9, windows 7 64bit

Please provide any additional information below.


Original issue reported on code.google.com by [email protected] on 4 Nov 2014 at 8:13

Data from RxTxSerialCom seems to be unavailable when parsing!

I have a problem which causes a java.lang.OutOfMemoryError

Normally when I receive packets with no error I get the following log output:

[2014-01-17 17:25:21,217] [InputStreamThread] [INFO] 
[com.rapplogic.xbee.api.PacketParser] Handling ApiId: ZNET_RX_RESPONSE (0x90) 
183895465 [InputStreamThread] INFO com.rapplogic.xbee.api.PacketParser  - 
Handling ApiId: ZNET_RX_RESPONSE (0x90)
[2014-01-17 17:25:21,243] [InputStreamThread] [INFO] 
[com.rapplogic.xbee.api.InputStreamThread] Received packet from XBee: 
apiId=ZNET_RX_RESPONSE 
(0x90),length=29,checksum=0xf4,error=false,remoteAddress64=0x00,0x13,0xa2,0x00,0
x40,0x61,0x64,0x5d,remoteAddress16=0x23,0x9c,option=null,data=0x57,0x01,0x02,0x0
3,0x04,0x05,0x0e,0x01,0x11,0x11,0x19,0x00,0x57,0x5d,0x00,0x00,0x00 
183895491 [InputStreamThread] INFO com.rapplogic.xbee.api.InputStreamThread  - 
Received packet from XBee: apiId=ZNET_RX_RESPONSE 
(0x90),length=29,checksum=0xf4,error=false,remoteAddress64=0x00,0x13,0xa2,0x00,0
x40,0x61,0x64,0x5d,remoteAddress16=0x23,0x9c,option=null,data=0x57,0x01,0x02,0x0
3,0x04,0x05,0x0e,0x01,0x11,0x11,0x19,0x00,0x57,0x5d,0x00,0x00,0x00

But sometimes I have the problem that RxTxSerial Com returns that no data is 
available:

[2014-01-17 17:30:12,082] [InputStreamThread] [INFO] 
[com.rapplogic.xbee.api.PacketParser] Handling ApiId: ZNET_RX_RESPONSE (0x90) 
184186330 [InputStreamThread] INFO com.rapplogic.xbee.api.PacketParser  - 
Handling ApiId: ZNET_RX_RESPONSE (0x90)
[2014-01-17 17:30:21,960] [Thread-5] [WARN] [com.rapplogic.xbee.RxTxSerialComm] 
We were notified of new data but available() is returning 0 
184196208 [Thread-5] WARN com.rapplogic.xbee.RxTxSerialComm  - We were notified 
of new data but available() is returning 0
[2014-01-17 17:30:21,965] [InputStreamThread] [INFO] 
[com.rapplogic.xbee.api.InputStreamThread] Received packet from XBee: 
apiId=ZNET_RX_RESPONSE 
(0x90),length=69,checksum=0x2e,error=false,remoteAddress64=0x00,0x13,0xa2,0x00,0
x40,0x61,0x64,0x5d,remoteAddress16=0x49,0xf6,option=null,data=0x55,0x01,0x02,0x0
3,0x04,0x05,0x0e,0x01,0x11,0x11,0x1e,0x00,0x07,0x00,0x00,0x00,0x03,0x42,0xc9,0xc
0,0x8f,0x00,0x01,0x42,0xc6,0x79,0x4a,0x00,0x05,0x40,0x84,0x7a,0xe0,0x00,0x04,0x4
2,0xba,0x23,0x4b,0x00,0x0a,0x40,0x40,0x00,0x00,0x00,0x0b,0x40,0x05,0xfc,0xb2,0x0
0,0x0c,0xba,0x34,0x00,0xb4 
184196213 [InputStreamThread] INFO com.rapplogic.xbee.api.InputStreamThread  - 
Received packet from XBee: apiId=ZNET_RX_RESPONSE 
(0x90),length=69,checksum=0x2e,error=false,remoteAddress64=0x00,0x13,0xa2,0x00,0
x40,0x61,0x64,0x5d,remoteAddress16=0x49,0xf6,option=null,data=0x55,0x01,0x02,0x0
3,0x04,0x05,0x0e,0x01,0x11,0x11,0x1e,0x00,0x07,0x00,0x00,0x00,0x03,0x42,0xc9,0xc
0,0x8f,0x00,0x01,0x42,0xc6,0x79,0x4a,0x00,0x05,0x40,0x84,0x7a,0xe0,0x00,0x04,0x4
2,0xba,0x23,0x4b,0x00,0x0a,0x40,0x40,0x00,0x00,0x00,0x0b,0x40,0x05,0xfc,0xb2,0x0
0,0x0c,0xba,0x34,0x00,0xb4

After this I get a java java.lang.OutOfMemoryError Exception...

Has anyone an idea how to fix this?


Original issue reported on code.google.com by [email protected] on 18 Jan 2014 at 2:02

Processing Not Run Library

What steps will reproduce the problem?
1.I am following of steps for installing xbee-api-0.9 in processing but at run 
the examples find in http://code.google.com/p/xbee-api/wiki/Processing, at 
running in processing, shows me the following error:

in line: XBee xbee;
message processing: cannot find class or type named "XBee"
2.
3.

What is the expected output? What do you see instead?


What version of the product are you using? On what operating system?

Window7 32bits
Processing2.0b6 and Processing1.5.1


Please provide any additional information below.

Original issue reported on code.google.com by [email protected] on 5 Nov 2012 at 3:11

Attachments:

Response not captured by PacketListener

The request in function sendSynchronous (XBee.java) is sent before the 
PacketListener is attached. This caused errors in my application because I 
managed to receive a response before the listener was attached. (it will cause 
an XBeeTimeoutException because the response is never received by the newly 
created PacketListener)

This issue was fixed by moving lines 325-327 after line 343.

Original issue reported on code.google.com by [email protected] on 24 Jun 2013 at 9:21

NoSuchMethod exception when invoking getPacketBytes on XBeeResponse

What steps will reproduce the problem?
1.XBeeResponse r = xbee.sendAtCommand(new AtCommand("DN", 
nodeIdentifierAsIntArray)); 
2. r.getPacketBytes();
3.

What is the expected output? What do you see instead?
it should return the contents of the packet .

What version of the product are you using? On what operating system?
0.5.1 MacOSX

Please provide any additional information below.
If I cast the XBeeResponse to an AtCommandResponse and use .getValue() I can 
access the 
packet contents. But still if getPacketBytes cannot be uses other kind of 
exception should be 
thrown. 

Original issue reported on code.google.com by [email protected] on 2 Mar 2009 at 7:14

XBeeAddress64 objects with equal address do not have the same hashcode

I am using a HashMap with XBeeAddress64 objects as keys, and overwriting the 
mapped values for those keys upon the reception of new data.  However, since 
the address objects do not return the same value for hashCode(), the HashMap 
created a new entry with each new value.  I fixed this by overriding hashCode() 
in XBeeAddress64.java with the following function:

    public int hashCode() {
        int val = 0;
        for (int i = 0; i < 4; i++) {
            val |= address[i] << (i * 8);
        }
        return val;
    }

Which should set the hashcode as the least significant 32-bits of the address.

I hope this is useful information for this project.  Thank you for all of your 
work on this API, it is proving to be extremely beneficial.

Original issue reported on code.google.com by LIGC90 on 28 Jun 2010 at 5:47

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.