Current situation:
We are coding a TCP client on C++/debian 6 that connects to the gateway(ConnectPort X2D) to be able to send and receive API pakets to/form the digimesh network
API frames sent from the TCP client to the mesh network arrives correctly to the Xbee modules.
The problems:
- The API frames arrive segmented to the TCP client, on two TCP packet. The splinting location is at random.
- One byte MSB form the length is lost and just 7 bytes form source address arrive instead of 8.
For example a Transmit Request is sent form a Xbee module with address:
Module : 00:13:A2:00:40:62:F3:2F
Destination: 0xFFFF (Broadcast)
On the TCP client the following packet arrives:
-
If the API frame is NOT splited into 2 packets
7e, 0, 90, 0, a2, 0, 40, 62, f3, 2f, ff, fe, 2, 0, 2, 0, 0, 0, f5,
LSB form location and byte 1 (0x13) form source address are missing -
If the API frame is splited into 2 pakets
TCP packet 1
7e, 0, 90, 0,
TCP packet 2
a2, 0, 40, 62, f3, 2f, ff, fe, 2, 0, 2, 0, 0, 0, f5,
LSB form location and byte 1 (0x13) form source address are missing
Actions taken:
- We have check that the API frame arrives properly to other Xbee modules connected to a microcontroler.
- We have try to upload firmware 82002162_B2.bin obtaining the message : Unable to update firmware: image does not support this hardware
Help needed:
-We would like to know if this is a normal behaviour of the gateway or not.
-If this is not normal, we will appropriate to bee pointed to the appropriate solution.
System Specifications:
Model: ConnectPort X2D
Firmware Version: 2.14.0.3 (Version 82002549_C 06/24/2011)
Boot Version: 1.1.3 (release_82002547_A)
POST Version: 1.1.3 (release_82002548_A)
Product VPD Version: release_82002550_A
Product ID: 0x00B2
Hardware Strapping: 0x0775
System Configuration:
Enable serial access to the gateway radio. (enabled)
Port 1 TCP Sockets 115200 8N1
Gateway working on API mode and AO Standard Data Frames format