Range Error

[mkarrei]

Hi,

I'm using xbee-api on my project, but I have a problem when the nodes (I'm using xbee-api for Arduino) send a information to controller (using node js). Sometimes (after a long time) I have a error:

Caught exception: RangeError: Trying to write outside buffer length - Line: undefined
RangeError: Trying to write outside buffer length
at RangeError ()
at checkInt (buffer.js:788:11)
at Buffer.writeUInt8 (buffer.js:794:5)
at XBeeAPI.parseRaw (/user/node_modules/xbee-api/lib/xbee-api.js:148:14)
at Object.parser (/user/node_modules/xbee-api/lib/xbee-api.js:119:10)
at Object.SerialPort.options.dataCallback (/user/node_modules/serialport/serialport.js:143:15)
at SerialPortFactory.SerialPort._emitData (/user/node_modules/serialport/serialport.js:312:20)
at afterRead (/user/node_modules/serialport/serialport.js:290:18)
at /user/node_modules/serialport/serialport.js:304:9
at Object.wrapper as oncomplete

I'm printing: console.log(S.b); console.log(S.offset); on file xbee-api.js, line 147, and after a long time values > 255 are received (495, 498, 499, 502, 495, 505, ...). Then I need to restart the application.

Thank's

[jankolkmeier]

Looks like it might be a bug. To be sure: Are you sending/receiving "a lot" of messages? Are you properly using the api_mode setting to match your XBee?

Could you share a minimal version of your program that reproduces the error? Or preferrably a dump of the incomming data that produce the error?

[duffmeister]

I had the same issue but it was resolved by making sure that the baud rate on the xbee and the initialization for the serial library matched (9600 in my case).

[mkarrei]

Hi,

Sorry for long time. Here is the code I use in my raspberry pi.

var xbee_api = require('xbee-api');
var SerialPort = require('serialport').SerialPort;

xbeeAPI = new xbee_api.XBeeAPI({
api_mode: 2,
module: "802.15.4",
raw_frames: false
});

serialPortBee = new SerialPort("/dev/ttyAMA0", {
baudrate: 9600,
parser: xbeeAPI.rawParser()
});

serialPortBee.on("open", function () {
console.log('xbeeStarted');
});

xbeeAPI.on("frame_object", function(frame)
{
var data = JSON.stringify(frame);
data = JSON.parse(data);
...
});

I'm printing on line 123 of file xbee_api.js

...
XBeeAPI.prototype.parseRaw = function(buffer) {
console.log(buffer);
console.log(''+buffer);
var S = this.parseState;
for(var i = 0; i < buffer.length; i++) {

}
...

The log file (forever) is at http://pastebin.com/wCrnJ0Wr

[xianlin]

Hi @jankolkmeier , I have the similar problem as the below:

buffer.js:788
    throw RangeError('Trying to write outside buffer length');
          ^
RangeError: Trying to write outside buffer length
    at RangeError (<anonymous>)
    at checkInt (buffer.js:788:11)
    at Buffer.writeUInt8 (buffer.js:794:5)
    at XBeeAPI.parseRaw (/home/user/node_modules/xbee-api/lib/xbee-api.js:155:14)
    at XBeeAPI.<anonymous> (/home/user/node_modules/xbee-api/lib/xbee-api.js:126:10)
    at Object.SerialPort.options.dataCallback (/home/user/node_modules/serialport/serialport.js:179:15)
    at SerialPortFactory.SerialPort._emitData (/home/user/node_modules/serialport/serialport.js:362:20)
    at afterRead (/home/user/node_modules/serialport/serialport.js:338:20)
    at /home/user/node_modules/serialport/serialport.js:354:9
    at Object.wrapper [as oncomplete] (fs.js:459:17)

the condition to reproduce this problem is my code:

var util = require('util')
var SerialPort = require("serialport").SerialPort
var xbee_api = require('xbee-api');

var C = xbee_api.constants;

var xbeeAPI = new xbee_api.XBeeAPI({
  api_mode: 1
});

var serialPort = new SerialPort("/dev/ttyUSB0", {
  baudrate: 57600,
  parser: xbeeAPI.rawParser()
});

// All frames parsed by the XBee will be emitted here
xbeeAPI.on("frame_object", function(frame) {
    console.log(">>", util.inspect(frame));
});

XBee Sending Setting -- This is the remote Xbee sending ADC sample IO data via 16bit address
API Mode 1, source address-0x31, dest address-0xFF, sample and send rate (IR) - 500ms

XBee Receiving Setting -- This is the XBee talking to the xbee-api Application.
API Mode 1, BD: 57600, source address-0xFF

above setup tested under X-CTU and the XBee can receive packets successfully from the remote XBee with IO sample data.

When I run the node-serialport test program to see the buffer:

var com = require("serialport");

var serialPort = new com.SerialPort("/dev/ttyUSB0", {
    baudrate: 57600,
    parser: com.parsers.raw
  });

serialPort.on('open',function() {
  console.log('Port open');
});

serialPort.on('data', function(data) {
    console.log(data);
});

I got the below output which shows a lot of zeroes ahead of the useful buffer data.

Port open
<Buffer 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ...>
<Buffer 83 00 31 32 00 01 06 04 00 04 03 ff 03 ff 06>
<Buffer 7e 00 0e 83 00 31 33 00>
<Buffer 01 06 04 00 04 03 ff 03 ff 05>
<Buffer 7e>
<Buffer 00 0e 83 00 31 32 00 01 06 04>
<Buffer 00 04 03 ff 03 ff>
<Buffer 06>
<Buffer 7e 00 0e 83 00 31>
<Buffer 37 00 01 06 04 00 04 03 ff 03 ff 01>
<Buffer 7e 00 0e 83 00 31 36 00 01 06 04 00>
<Buffer 04 03 ff 03 ff 02>
<Buffer 7e 00>
<Buffer 0e 83 00 31 34>
<Buffer 00 01 06 04 00 04 03>
<Buffer ff 03 ff 04>

Now I assume those leading zeros causes buffer length range errors and I don't know why so many leading zeros generated.
BTW, those leading zeros goes away after I exit my app and restart it.

Another strange thing is that if I enable "Encryption" on both XBee and set a 32-bit Hex String as the key and run the same app, it shows new errors:

assert.js:92
  throw new assert.AssertionError({
        ^
AssertionError: Out of Original Buffer's Boundary
    at BufferReader.MAKE_NEXT_READER.BufferReader.(anonymous function) [as nextUInt16BE] (/home/user/node_modules/xbee-api/node_modules/buffer-reader/index.js:77:9)
    at Object.frame_parser.Recieved16BitPacketIO (/home/user/node_modules/xbee-api/lib/frame-parser.js:241:40)
    at Object.frame_parser.(anonymous function) [as 131] (/home/user/node_modules/xbee-api/lib/frame-parser.js:298:16)
    at XBeeAPI.parseFrame (/home/user/node_modules/xbee-api/lib/xbee-api.js:110:27)
    at XBeeAPI.parseRaw (/home/user/node_modules/xbee-api/lib/xbee-api.js:189:40)
    at XBeeAPI.<anonymous> (/home/user/node_modules/xbee-api/lib/xbee-api.js:126:10)
    at Object.SerialPort.options.dataCallback (/home/user/node_modules/serialport/serialport.js:179:15)
    at SerialPortFactory.SerialPort._emitData (/home/user/node_modules/serialport/serialport.js:362:20)
    at afterRead (/home/user/node_modules/serialport/serialport.js:338:20)
    at /home/user/node_modules/serialport/serialport.js:354:9

The serial port test program shows output:

Port open
<Buffer 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ...>
<Buffer 31 2f 00 ff 04 b5 47 01 06 04 00 04 03 ff 03 ff 0a>
<Buffer 7e 00 12 83 00 31>
<Buffer 2f 00 ff 04 b5 47 01 06 04 00 04 03>
<Buffer ff 03 ff 0a>
<Buffer 7e 00 12 83>
<Buffer 00 31 2f 00 ff 04>
<Buffer b5 47 01 06 04 00>
<Buffer 04 03 ff 03 ff 0a>
<Buffer 7e 00 12>
<Buffer 83 00 31 2f 00 ff>
<Buffer 04 b5 47 01 06 04>
<Buffer 00 04 03 ff 03>
<Buffer ff 0a>
<Buffer 7e 00 12>
<Buffer 83 00 31 2f 00>
<Buffer ff 04 b5 47 01 06 04>
<Buffer 00 04 03 ff 03>
<Buffer ff 0a>

The difference is that this time the leading zeros will not go away and they occur every time when you run the app or the test program.

Anyone tried it with Encryption on with XBee Series 1 and get successful data output?

[jankolkmeier]

I never used encryption, so I cannot report on that, but in principle, it shouldn't matter.

It might be that the issue is related to a bug/curiosity in serialport. I do not think that writing any zero bytes just like that is part of the xbee specs.

Far fetched, but maybe it is an issue with the serial 2 usb converter you are using? Are you using an official shield with FTDI? Maybe a third party shield? @duffmeister @infomk did you happen to use something unusual?

Regardless, a fix would be something inside the parseRaw function that prevents writing to the working buffer unless we are inside a package, after we received a start byte. Could you check out if 889e588
fixes the issue?

[xianlin]

@jankolkmeier , Thank you and the Range error goes away by using the above fix
But the Assertions Error still persists:

assert.js:92
  throw new assert.AssertionError({
        ^
AssertionError: Out of Original Buffer's Boundary
    at BufferReader.MAKE_NEXT_READER.BufferReader.(anonymous function) [as nextUInt16BE] (/home/user/node_modules/xbee-api/node_modules/buffer-reader/index.js:79:9)
    at Object.frame_parser.Recieved16BitPacketIO (/home/user/node_modules/xbee-api/lib/frame-parser.js:241:40)
    at Object.frame_parser.(anonymous function) [as 131] (/home/user/node_modules/xbee-api/lib/frame-parser.js:298:16)
    at XBeeAPI.parseFrame (/home/user/node_modules/xbee-api/lib/xbee-api.js:113:27)
    at XBeeAPI.parseRaw (/home/user/node_modules/xbee-api/lib/xbee-api.js:198:26)
    at XBeeAPI.<anonymous> (/home/user/node_modules/xbee-api/lib/xbee-api.js:133:10)
    at Object.SerialPort.options.dataCallback (/home/user/node_modules/serialport/serialport.js:179:15)
    at SerialPortFactory.SerialPort._emitData (/home/user/node_modules/serialport/serialport.js:362:20)
    at afterRead (/home/user/node_modules/serialport/serialport.js:338:20)
    at /home/user/node_modules/serialport/serialport.js:354:9

I have put the console.log code into node_modules/buffer-reader/index.js line 74 onwards:

function MAKE_NEXT_READER(valueName, size) {
    valueName = cap(valueName);
    BufferReader.prototype['next' + valueName] = function() {
        // added debug code
        console.log(this.buf);
        console.log("Offset: " + this.offset + " Size: " + size + " Buf Length: " + this.buf.length);
        console.log("");

        assert(this.offset + size <= this.buf.length, "Out of Original Buffer's Boundary");
        var val = this.buf['read' + valueName](this.offset);
        this.offset += size;
        return val;
    };
}

Here are the outputs:

<Buffer 83 00 31 2d 00 ff 04 b5 47 01 06 04 00 00 02 15 00 ee>
Offset: 0 Size: 1 Buf Length: 18

<Buffer 83 00 31 2d 00 ff 04 b5 47 01 06 04 00 00 02 15 00 ee>
Offset: 3 Size: 1 Buf Length: 18

<Buffer 83 00 31 2d 00 ff 04 b5 47 01 06 04 00 00 02 15 00 ee>
Offset: 4 Size: 1 Buf Length: 18

<Buffer 83 00 31 2d 00 ff 04 b5 47 01 06 04 00 00 02 15 00 ee>
Offset: 5 Size: 1 Buf Length: 18

<Buffer 83 00 31 2d 00 ff 04 b5 47 01 06 04 00 00 02 15 00 ee>
Offset: 6 Size: 2 Buf Length: 18

<Buffer 83 00 31 2d 00 ff 04 b5 47 01 06 04 00 00 02 15 00 ee>
Offset: 8 Size: 2 Buf Length: 18

<Buffer 83 00 31 2d 00 ff 04 b5 47 01 06 04 00 00 02 15 00 ee>
Offset: 10 Size: 2 Buf Length: 18

<Buffer 83 00 31 2d 00 ff 04 b5 47 01 06 04 00 00 02 15 00 ee>
Offset: 12 Size: 2 Buf Length: 18

<Buffer 83 00 31 2d 00 ff 04 b5 47 01 06 04 00 00 02 15 00 ee>
Offset: 14 Size: 2 Buf Length: 18

<Buffer 83 00 31 2d 00 ff 04 b5 47 01 06 04 00 00 02 15 00 ee>
Offset: 16 Size: 2 Buf Length: 18

<Buffer 83 00 31 2d 00 ff 04 b5 47 01 06 04 00 00 02 15 00 ee>
Offset: 18 Size: 2 Buf Length: 18

Clearly when Offset=18 + Size=2 == 20 > Length=18 at the last row, the error will be triggered.

My serialport code still produces the below data from the serial port:

Port open
<Buffer 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ...>
<Buffer 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ...>
<Buffer 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ...>
<Buffer 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ...>
<Buffer 7e 00 12 83 00 31 2c 00 ff>
<Buffer 04 b5 47>
<Buffer 01 06 04 00 00 02 11 00>
<Buffer ee 14>
<Buffer 7e 00 12 83 00 31 2c>
<Buffer 00 ff 04 b5>
<Buffer 47 01 06 04 00 00>
<Buffer 02 13 00 ed 13>
<Buffer 7e 00 12 83 00>
<Buffer 31 2c 00 ff 04 b5 47 01 06 04 00 00 02 18 00>
<Buffer ed 0e>
<Buffer 7e 00 12 83 00 31>
<Buffer 2c 00 ff 04 b5>
<Buffer 47 01 06 04 00 00>
<Buffer 02 15 00 ed 11>
<Buffer 7e 00 12 83>
<Buffer 00 31 2c 00 ff 04>
<Buffer b5 47 01 06 04 00>
<Buffer 00 02 19 00 ed 0d>

Then I disabled the Encryption and here are the results:

<Buffer 83 00 31 2c 00 01 06 04 00 00 02 23 00 ed>
Offset: 0 Size: 1 Buf Length: 14

<Buffer 83 00 31 2c 00 01 06 04 00 00 02 23 00 ed>
Offset: 3 Size: 1 Buf Length: 14

<Buffer 83 00 31 2c 00 01 06 04 00 00 02 23 00 ed>
Offset: 4 Size: 1 Buf Length: 14

<Buffer 83 00 31 2c 00 01 06 04 00 00 02 23 00 ed>
Offset: 5 Size: 1 Buf Length: 14

<Buffer 83 00 31 2c 00 01 06 04 00 00 02 23 00 ed>
Offset: 6 Size: 2 Buf Length: 14

<Buffer 83 00 31 2c 00 01 06 04 00 00 02 23 00 ed>
Offset: 8 Size: 2 Buf Length: 14

<Buffer 83 00 31 2c 00 01 06 04 00 00 02 23 00 ed>
Offset: 10 Size: 2 Buf Length: 14

<Buffer 83 00 31 2c 00 01 06 04 00 00 02 23 00 ed>
Offset: 12 Size: 2 Buf Length: 14

>> { type: 131,
  remote16: '0031',
  rssi: 44,
  receiveOptions: 0,
  data:
   { sampleQuantity: 1,
     channelMask: 1540,
     channels: { ADC0: 1, ADC1: 1, DIO2: 1 },
     analogSamples: [ [Object] ],
     digitalSamples: [ '0' ] } }

The last row is 14=14, not exceeding 14 bytes, the difference between encryption and not encryption is 4 bytes.

I hope this can help further debug the problem cause I have no clue why the code cannot parse this 18 byte buffer <Buffer 83 00 31 2d 00 ff 04 b5 47 01 06 04 00 00 02 15 00 ee>

[jankolkmeier]

I briefly read into encryption. I am a bit confused. The xbee specs say that a frame send with encryption would carry a 0x20 byte in the transmit options, however none of the buffers you reported contain a 0x20 byte.

You are using series 1, right?
Are you operating in the right AP mode? (escaping disabled/enabled)?

Could you send me the complete frame that causes the issue, from start delimiter (0x7e) to checksum? And maybe a complete frame that does work?

[xianlin]

@jankolkmeier , here are my complete frame that causes the issue:

Serial Port Opend
<Buffer 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ...>
<Buffer 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ...>
<Buffer 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ...>
<Buffer 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ...>
<Buffer 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ...>
<Buffer 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ...>
<Buffer 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ...>
<Buffer 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 7e 00 12 83 00 31 2c 00 ff 04 b5 47 01 06 04 00 00>
<Buffer 01 dd 00 f6 41>
<Buffer 7e 00>
<Buffer 12 83 00 31 2c 00>
<Buffer ff 04 b5 47 01>
<Buffer 06 04 00 00 01 de>
<Buffer 00 f6 40>
<Buffer 7e 00 12 83 00>
<Buffer 31 2c 00 ff 04>
<Buffer b5 47 01 06 04 00>
<Buffer 00 01 dd 00 f6 41>
<Buffer 7e>
<Buffer 00 12 83 00 31 2c>
<Buffer 00 ff 04 b5 47>
<Buffer 01 06 04 00 00 01>
<Buffer dd 00 f5 42>
<Buffer 7e 00 12 83 00>
<Buffer 31 2c 00 ff 04 b5>
<Buffer 47 01 06 04 00 00>
<Buffer 01 dd 00 f5 42>

If I run my customized parser code I will get Assertion error:

Error:

assert.js:93
  throw new assert.AssertionError({
        ^
AssertionError: Out of Original Buffer's Boundary
    at BufferReader.MAKE_NEXT_READER.BufferReader.(anonymous function) [as nextUInt16BE] (/home/xianlin/Code/JS/XBee/node_modules/xbee-api/node_modules/buffer-reader/index.js:77:9)
    at Object.frame_parser.Recieved16BitPacketIO (/home/xianlin/Code/JS/XBee/node_modules/xbee-api/lib/frame-parser.js:243:40)
    at Object.frame_parser.(anonymous function) [as 131] (/home/xianlin/Code/JS/XBee/node_modules/xbee-api/lib/frame-parser.js:300:16)
    at XBeeAPI.parseFrame (/home/xianlin/Code/JS/XBee/node_modules/xbee-api/lib/xbee-api.js:113:27)
    at XBeeAPI.parseRaw (/home/xianlin/Code/JS/XBee/node_modules/xbee-api/lib/xbee-api.js:198:26)
    at XBeeAPI.<anonymous> (/home/xianlin/Code/JS/XBee/node_modules/xbee-api/lib/xbee-api.js:133:10)
    at Object.SerialPort.options.dataCallback (/home/xianlin/Code/JS/XBee/node_modules/serialport/serialport.js:179:15)
    at SerialPortFactory.SerialPort._emitData (/home/xianlin/Code/JS/XBee/node_modules/serialport/serialport.js:362:20)
    at afterRead (/home/xianlin/Code/JS/XBee/node_modules/serialport/serialport.js:338:20)
    at /home/xianlin/Code/JS/XBee/node_modules/serialport/serialport.js:354:9

The parser code is simply as:

var util = require('util')
var SerialPort = require("serialport").SerialPort
var xbee_api = require('xbee-api');

var C = xbee_api.constants;

var xbeeAPI = new xbee_api.XBeeAPI({
  api_mode: 1
});

var serialPort = new SerialPort("/dev/ttyUSB1", {
  baudrate: 57600,
  parser: xbeeAPI.rawParser()
});

// All frames parsed by the XBee will be emitted here
xbeeAPI.on("frame_object", function(frame) {
    console.log(">>", util.inspect(frame));
});

When I disabled the Encryption (EE=0), here are the complete frame that does the work.

Complete Frame Without Issue:

Serial Port Opend
<Buffer 7e 00 0e>
<Buffer 83 00 31 2b 00 01 06 04 00 00 01 c5>
<Buffer 00 f2 5d>
<Buffer 7e 00 0e>
<Buffer 83 00 31 2c 00 01>
<Buffer 06 04 00 00 01 c6>
<Buffer 00 f2 5b>
<Buffer 7e 00 0e>
<Buffer 83 00 31 2c 00 01>
<Buffer 06 04 00 00 01 c6>
<Buffer 00 f2 5b>
<Buffer 7e 00>
<Buffer 0e 83 00 31 2c 00>
<Buffer 01 06 04 00 00 01>
<Buffer c6 00 f2 5b>
<Buffer 7e 00>
<Buffer 0e 83 00 31 2c 00>
<Buffer 01 06 04 00 00 01>
<Buffer c6 00 f3 5a>
<Buffer 7e 00 0e 83 00 31>
<Buffer 2c 00 01 06 04 00>
<Buffer 00 01 c6 00 f2 5b>

After Parser:

>> { type: 131,
  remote16: '0031',
  rssi: 44,
  receiveOptions: 0,
  data:
   { sampleQuantity: 1,
     channelMask: 1540,
     channels: { ADC0: 1, ADC1: 1, DIO2: 1 },
     analogSamples: [ [Object] ],
 digitalSamples: [ '0' ] } }
>> { type: 131,
  remote16: '0031',
  rssi: 44,
  receiveOptions: 0,
  data:
   { sampleQuantity: 1,
     channelMask: 1540,
     channels: { ADC0: 1, ADC1: 1, DIO2: 1 },
     analogSamples: [ [Object] ],
     digitalSamples: [ '0' ] } }
>> { type: 131,
  remote16: '0031',
  rssi: 44,
  receiveOptions: 0,
  data:
   { sampleQuantity: 1,
     channelMask: 1540,
     channels: { ADC0: 1, ADC1: 1, DIO2: 1 },
     analogSamples: [ [Object] ],
     digitalSamples: [ '0' ] } }

I am using Series 1, AP mode = 2 (escaping enabled).
I don't know if there is a 0x20 byte for encryption, I only know 0x20 is for escaping XOR operation?

The serial port read code is as the below (Am I getting the full frame by using the below code?):

var SerialPort = require("serialport").SerialPort;

var serialport = new SerialPort("/dev/ttyUSB1", {
    baudrate: 57600
});

serialport.on('open', function(){
  console.log('Serial Port Opend');
  serialport.on('data', function(data){
      console.log(data);
  });
});

[jankolkmeier]

My mistake, the 0x20 is only in the series 2 transmit status fields!
Thank you for the frames, I'll have a look later if I can figure out what is going wrong!

[jankolkmeier]

The error is caused because the frames with encryption have a value of 0xff in the 9th byte. This indicates that there are 255 samples (instead of 0x01=one as in the frames without encryption).
This really has me puzzled, as there is nothing in the specs that explain this value.

The spec does mention that encrypted packets always use their 64 address as the src address for RF packets - but trying that gives an even less meaningful interpretation of the packet...

At this point, I'm clueless, sorry :(

[xianlin]

So the problem is that the RF Data part I got under Encryption mode is different from the Non-Encryption mode. It has 4 more bytes.

By right, the RF data content should remain the same content with OR without encryption. But the below results said NO and it puzzled us.

API Mode 2, 802.15.4 Series 1, firmware 10e6

0x83: Recieved Packet 16-bit Address I/O without encryption

Frame: 7E 00 0A 83 00 10 2D 00 01 02 00 01 CC 6F
RF Data: 01 02 00 01 CC


0x83: Recieved Packet 16-bit Address I/O with encryption

Frame: 7E 00 0E 83 00 10 2C 00 FF 04 B5 47 01 02 00 01 CC 71
RF Data: FF 04 B5 47 01 02 00 01 CC

Well, I will ask this on Digi forum and hopefully someone will answer it. Thanks. @jankolkmeier .

[jankolkmeier]

Keep me posted! :)

[nzfarmer1]

This may help in the interim:

Line 146:
if (!S.waiting && S.offset <128) { // Add range checking
S.buffer.writeUInt8(S.b, S.offset++);
}