This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Thingsquare 6LowPan MSP430 Running demo

Other Parts Discussed in Thread: CC1120, CC1101, CC1200

Hi,

I am using following webpage reference to build a MQTT example with nodes and edge router for 6LowPan network.

http://processors.wiki.ti.com/index.php/Thingsquare_6LoWPAN_MSP430

I have been able to build the node and the edge router however the node doesn't appear to be detecting the edge router.

Router Notification:

cc1120: write_txfifo timeout
Contiki 2.6
Rime addr 2.18.116.0.0.1.1.0
Starting up cc11xx radio at channel 26
Using freq directly from REG settings
Node id 1.
Netstack AES link layer encryption enabled
nullrdc/CSMA 128 26
IPv6 fe80:0000:0000:0000:0012:7400:0001:0100
Tentative global IPv6 address fc00:0000:0000:0000:0012:7400:0001:0100
AES encryption is enabled
cc11xx radio at channel 26
Using freq directly from REG settings
IPv6 addresses: fc00::12:7400:1:100
fe80::12:7400:1:100
Starting Router node
MAC addr 02:12:74:01:01:00
Starting DHCPv4
Inited
Requested
DHCP Configured with 192.168.1.134
cc11xx.c: write_txfifo txbytes underflow
cc1120: write_txfifo timeout
cc1120: write_txfifo timeout
cc1120: write_txfifo timeout
cc1120: write_txfifo timeout

Node notification:

Contiki 2.6
Rime addr 2.18.116.0.0.1.2.0
Starting up cc11xx radio at channel 26
Using freq directly from REG settings
Node id 2.
Netstack AES link layer encryption enabled
nullrdc/CSMA 128 26
IPv6 fe80:0000:0000:0000:0012:7400:0001:0200
Tentative global IPv6 address fc00:0000:0000:0000:0012:7400:0001:0200
AES encryption is enabled
cc11xx radio at channel 26
Using freq directly from REG settings
IPv6 addresses: fc00::12:7400:1:200
fe80::12:7400:1:200
Starting MQTT Example
random value 10002
ti/iot/device/10002
APP - Disconnected from MQTT broker
cc1120: write_txfifo timeout
APP - Disconnected from MQTT broker
APP - Disconnected from MQTT broker
cc1120: write_txfifo timeout
APP - Disconnected from MQTT broker

So what I'm expecting to get from the node is something like :

APP - Got a RPL route
APP - Application has a MQTT connection
APP - Application is subscribed to topic successfully

any ideas or pointers on this one?

Thanks

Tyler

  • Hello,

    As far as I can see everything is working as expected. If you publish something to the topic your device (node) has subscribed to, do you get the data on the node?

    Thanks,

    Jonas

  • Hi, 

    thanks for your response, I though I should get a few lines saying :

    APP - Got a RPL route
    APP - Application has a MQTT connection
    APP - Application is subscribed to topic successfully

    But the node is just saying :

    APP - Disconnected from MQTT broker

    I have tried several different brokers, but the only one I can even connect to from a browser is the one at:

    messagesight.demos.ibm.com (75.126.71.163)

    and using the client:
    http://m2m.demos.ibm.com/mqttclient/#connect

    however when I subscribe to topics or publish to topics I get nothing from the node, except that it says it is disconnected.

    as far as I can tell the node is not communicating with the edge router, any ideas

    thanks again

  • Ah! Yes - of course you are right, didn't read the post carefully enough. Sorry!

    Agree, it seems to me that you are not connected to the Edge Router successfully. 

    Please setup a sniffer and post the capture here.

    Here are instructions for building a sniffer for the trxeb1120 platform: http://processors.wiki.ti.com/index.php/Contiki-6LOWPAN#Packet_Sniffer

    -Jonas 

  • ok I will give that a go.

    looking at the Wiki, Should I build the sniffer onto my edge router? or do I need a third set up (I only have 2 Trxeb boards and 2xCC1101 and 2xCC1200)

    thanks very much! 

  • thanks again for your help,

    I built the sniffer for the Trxeb board i built the hex file in instant contiki using:

    make enc28j60-sniffer.hex TARGET=eth1101

    and it seems to be working, going by the output to teraterm:

    Contiki 2.6
    Rime addr 2.18.116.0.0.1.1.0
    cc1101 init
    Node id 1.
    Netstack AES link layer encryption enabled
    nullrdc/CSMA 128 26
    IPv6 fe80:0000:0000:0000:0012:7400:0001:0100
    Tentative global IPv6 address fc00:0000:0000:0000:0012:7400:0001:0100
    AES encryption is enabled
    IPv6 addresses: fc00::12:7400:1:100
    fe80::12:7400:1:100
    Starting Enc28j60 sniffer process

    however when I trun wire shark it only detects packet from the PC, looking for DHCP and stuff like that.

    really not sure where to go to from hear, any ideas?

    thanks

  • Hello,

    Sorry about the delay on this thread. 

    Yes, you would need an extra trxeb and ethernet DK in order to create the sniffer. 

    Seems your sniffer is working as expected. Connect the ethernet cable between your PC and sniffer Ethernet DK. You should set Wireshark so that it "sniffs/listens" on your Ethernet connection on your PC. 

    The sniffer basically sends out everything that it captures on the RF on the Ethernet interface. E.g. you should see RPL messages coming in from the other nodes.

    Can you copy your settings (CC1120-config.h) for all your devices here?

    Thanks,

    Jonas

  • Hey, 

    Thanks again.

    I have set up with 3 boards, one sniffer, one router and one node.

    However I am not getting any data in wireshark from the sniffer. I have tried building the sniffer with the CC1101 and CC1200 modules but I dont have a CC1120 module to try. I have used the CC1120 make settings for the CC1200 but I have adjusted the make settings for the CC1101 as per my earlier post.

    I have attached the settings files I have been using:

    0028.cc1120-config.h

    1348.cc1101-config.h

    thanks very much

  • Hello,

    The links appear to be broken.

    Can you post a picture of your setup? I want to verify you have built a sniffer like this: trxeb - CC1120EM - Ethernet DK.

    The only other thing I can think of is that the settings used on the different boards and not compatible, hence your devices will not hear each other.

    /Jonas