Part Number:LAUNCHXL-CC1310
Hi,
I have 6lbr (Router mode) running with RaspPi + CC1310 launchpad (slipradio).
I got one more cc1310 launchpad into WSN. This end node is discovered and I am able to open web page to it.
I couldn't find it on IBM quickstart page.
I enabled prints in cc26xx-web-demo.bin and found from serial logs that it is stuck in MQTT connecting phase itself:
I don't see any packets in the output of tcpdump for port 1883 on RaspPi:
pi@raspberrypi:~ $ sudo tcpdump -i eth0 port 1883
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes
However, I see some packets in 6lbr.log with IP address matching the IBM quickstart messaging server (MQTT broker) with debug level increased to 8:
2018-03-27 1:04:46.797544: PACKET: SLIP: read: 73
2018-03-27 1:04:46.797676: DUMP: SLIP:
61dc1ccd abec63a4 13004b12 006e63a4
13004b12 007af000 000064ff 9b000000
00000000 00b8ac7c bd060063 04001e02
00040507 5b000000 64000000 00600200
809a8700 00020400 80
I tried reducing debug level also to understand if logging is leading to any timing issue. It didn't solve.
Not sure if IP64 setting in 6lbr also comes into picture for this behavior. But i have enabled IP64 as well.
Can I get some help on this ?
Is this because IBM quickstart broker IP is not reachable from my network ? OR
is the tcpdump indicating something is wrong in mqtt message communication in WSN itself ?
MORE INFO:
==========
Logs on end node indicating MQTT Connection attempts:
Starting Contiki-3.x-3343-gbc2e445
With DriverLib v0.47020
TI CC1310 LaunchPad
IEEE 802.15.4: No, Sub-GHz: Yes, BLE: No, Prop: No
Net: sicslowpan
MAC: CSMA
RDC: ContikiMAC, Channel Check Interval: 16 ticks
RF: Channel 25
Node ID: 25454
CC26XX Web Demo Process
CC26XX Web Server
CC26XX CoAP Server
6LBR Client Process
CC26XX MQTT Client Process
CC26XX Net UART Process
Init
Registered. Connect attempt 1
Connecting (1)
Connecting (1)
Connecting (1)
Connecting (1)
Connecting (1)
Connecting (1)
Connecting (1)
Connecting (1)
Connecting (1)
Connecting (1)
Connecting (1)
Connecting (1)
Connecting (1)
Connecting (1)
Connecting (1)
Connecting (1)
Connecting (1)
Connecting (1)
Connecting (1)
Connecting (1)
Connecting (1)
Connecting (1)
Connecting (1)
Connecting (1)
Connecting (1)
Connecting (1)
Connecting (1)
Connecting (1)
Connecting (1)
Connecting (1)
Connecting (1)
Connecting (1)
Connecting (1)
Connecting (1)
Connecting (1)
Connecting (1)
Connecting (1)
Connecting (1)
Connecting (1)
Connecting (1)
Connecting (1)
Connecting (1)
Connecting (1)
Connecting (1)
Connecting (1)
Connecting (1)
Connecting (1)
Connecting (1)
Connecting (1)
Connecting (1)
Connecting (1)
Connecting (1)
Connecting (1)
Connecting (1)
Connecting (1)
Connecting (1)
UDP-CLIENT: address destination: fd00::212:4b00:13a4:63ec
Created a connection with the server fd00::212:4b00:13a4:63ec local/remote port 1028/3000
Client sending to: fd00::212:4b00:13a4:63ec (msg: 1 | fe80::0212:4b00:13a4:63ec)
Response from the server: '1'
Connecting (1)
Connecting (1)