Quantcast
Channel: Wireless Connectivity
Viewing all articles
Browse latest Browse all 116964

Forum Post: Digi XBee and CC2530 Communication Problems

$
0
0

Hello,

i followed some Steps from this:

http://e2e.ti.com/support/low_power_rf/f/158/t/17420.aspx

and now it seems that my XBP24 joins as an EndDevice my Network with CC2530 as a Coordinator.

I am running the CC2530-Coordinator from the CC2530ZDK-ZNP-MINI Kit and tried all Coordinator Examples which are included in CC2530ZNPMiniKit Examples (preferring the "Basic Communications Example - COORDINATOR - using AFZDO". I think that all of these Examples should print out all received pakets, so any paket from XBP24 should be printed out as "unknown paket" is this right?

In X-CTU i can see the correct Operating PAN and Channel which the Coordinator generated, so i think the joining procedure was successful.

After joining i can mostly see a received paket like "Rx: 0D 45 C1 07 07 07 07 B6 6D 6C 40 00 A2 13 00 80" in my coordinators output. This seems to be a received paket from XBP24 since it includes it's Serialnumber (with reversed byteorder than i see the number in X-CTU) somehow.

Now i want to transmit some Data from XBP24 to the coordinator. For this the XBP24 runs the "ZIGBEE END DEVICE AT" V2841 Configuration from X-CTU. Is this the right Configuration for this? As i understood i should be able to type any characters in the Terminalwindow of X-CTU which should be transmitted. When i do so nothing happens on coordinators side. No pakets seem to be received. When i enter many bytes (>500) on terminalwindow of X-CTU the green-RSSI LED on the XBP24 adapter-board lights up for a short time (indicating that something is beeing transmitted?), but nothing happens on coordinators side, too.

The DH and DL params from XBP24 are set to zero (indicating a transmission to the coordinator, right?)

What goes wrong here?


Viewing all articles
Browse latest Browse all 116964

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>