nRF51: IoT-MQTT Publisher Example problems

RE: nRF51: IoT-MQTT Publisher Example problems

bjorn-spockeli — Thu, 09 Mar 2017 13:55:50 GMT

Awesome! Glad to hear that you're up and running!

RE: nRF51: IoT-MQTT Publisher Example problems

Jim — Thu, 09 Mar 2017 13:52:08 GMT

Thank you for all the help. The last ifconfig fixed the problem.

RE: nRF51: IoT-MQTT Publisher Example problems

Jim — Thu, 09 Mar 2017 13:49:54 GMT

FINALLY it works. Used the 2001:db8::/64 address for the radvd config file and BT0. Set ifconfig BT0 add 2001:db8::1/64 and set 2001:db8::1 for the broker address in the program. Also used NON_SECURE setting and 1883 for the broker port. Ran mosquitto on the PI.

RE: nRF51: IoT-MQTT Publisher Example problems

Jim — Thu, 09 Mar 2017 10:59:10 GMT

Ok, I went back to the 2001:db8::/64 addresses used in the original instructions with the same result. The instructions in the IOT_SDK are rather unclear about where to run mosquitto. I have put in on the Raspberry PI. I have tried putting on a PC (with the FD00:b:: addresses) and that didn't work either. I assume if you put it on the PC you have to set up IPV6 routing there but it is NOT in the IOT_SDK instructions.

RE: nRF51: IoT-MQTT Publisher Example problems

Jim — Wed, 08 Mar 2017 13:42:56 GMT

Further work and I have found the 0C942 error code. This occurs in the button press for connect routine. It gets an error_code from mqtt_connect() and then calls APP_ERROR_CHECK(). The error code returned is 51522 = 0xC942. And APP_ERROR_CHECK() is a fron tend for app_error_handler() which sets all the LEDs ON and then enters a endless loop. And that effectively ends the program. So the connect is failing. Found the problem by tracing down into the code. It is failing on the tcp_connect() and fails because NO ROUTE TO HOST . I guess I need a route for the FD00:a:: to FD00:b::2 In the PI

RE: nRF51: IoT-MQTT Publisher Example problems

bjorn-spockeli — Wed, 08 Mar 2017 13:11:19 GMT

Hmm, I do not know if using a different prefix than the one we provide in the IoT SDK would cause this issue. Could you try to use the setup described in the doc, i.e. use the 2001:db8::1/64 prefix? I have not seen that the SoftDevice asserts upon connection to the mosquitto broker( rem.c is one of the internal source files of the SoftDevice). Are you stepping through the code when attempting to connect?

RE: nRF51: IoT-MQTT Publisher Example problems

Jim — Wed, 08 Mar 2017 10:44:40 GMT

These addresses are all based on this Article which I went through to get IPV6 working.

RE: nRF51: IoT-MQTT Publisher Example problems

Jim — Wed, 08 Mar 2017 10:42:16 GMT

I am using different IPV6 addresses (FD00:a::xx for the Nordic) FD00:b::1 for the PI and FD00:b::2 for the PC. but I have the line ifconfig bt0 add fd00:a::/64 and ifconfig eth0 add fd00:b::1/64 in my setup script. The problem is as soon as I try to make the connection I get the error deep in the Softdevice (file rem.c line 610) and it goes to the app_error_handler and into an infinite loop in that routine. This file doesn't seem to be in my IOT sources.

RE: nRF51: IoT-MQTT Publisher Example problems

bjorn-spockeli — Wed, 08 Mar 2017 10:33:43 GMT

Yes, I have been seeing that issue as well(same setup with an unsecured connection), the solution in my case was to repeatedly try to make a connection with the MQTT broker untill it returns NRF_SUCCESS. I also think that I spottet a mistake in my bash script, there should be a

sudo ifconfig btX add 2001:db8::1/64

after for loop that connects to the devices.

RE: nRF51: IoT-MQTT Publisher Example problems

Jim — Wed, 08 Mar 2017 10:27:59 GMT

I never see a message on the mosquitto on the pc that a connection is attempted. The Nordic board goes into an infinite loop after it gets the 0C942 error (app_error_handler())

RE: nRF51: IoT-MQTT Publisher Example problems

Jim — Wed, 08 Mar 2017 10:25:01 GMT

FWIW when I am connected I can ping6 the Nordic board from the PC (where I run mosquitto) so the routing seems to be correct. Also I am doing the development with Eclipse and the gcc makefile. I have changed the MQTT programs to use the non secure connection and changed the broker port to 1883. The mosquitto that I use comes up with 1883. I can use mosquitto_pub and mosquitto_sub on the Raspberry Pi and talk to the mosquitto on the PC.

RE: nRF51: IoT-MQTT Publisher Example problems

bjorn-spockeli — Wed, 08 Mar 2017 10:24:38 GMT

I was referring to the connection to the MQTT broker, i.e. mqtt_connect.

RE: nRF51: IoT-MQTT Publisher Example problems

Jim — Wed, 08 Mar 2017 10:00:59 GMT

I have no trouble connecting, it works on the first try every time. But I have now switched to a Nordic development board instead of the BMD-300 and it has exactly the same results. Cannot connect to with the Publisher and it fails with the 0xC942 error.

RE: nRF51: IoT-MQTT Publisher Example problems

bjorn-spockeli — Mon, 06 Mar 2017 14:02:15 GMT

I have observed that sometimes you have to repeatedly try to reconnect, so I've set up a timer that repeatedly tries to connect to the broker, e.g. every 10 seconds.

RE: nRF51: IoT-MQTT Publisher Example problems

Jim — Thu, 02 Mar 2017 09:27:26 GMT

The connection is never made. (Watching the output of mosquitto).

RE: nRF51: IoT-MQTT Publisher Example problems

bjorn-spockeli — Thu, 02 Mar 2017 09:07:50 GMT

Hi Jim, is it mqtt_connect that returns the 0xC942 error code?

RE: nRF51: IoT-MQTT Publisher Example problems

Jim — Wed, 01 Mar 2017 14:23:41 GMT

Further work, got the APP_LOG working. To do this I had to:

Add CFLAGS += -DENABLE_LOG_SUPPORT to the Make file
Edit app_trace.c to set the baud rate to 115200 and disable Flow control 3 Add a hardware USB<->Serial device (3V) TX -> pin 8 RX -> pin 6 With the board connected (I can ping6 it's address) and mosquitto running on the PC I get

[APPL]: Physical layer in connectable mode. [APPL]: Physical layer: connected`.

[APPL]: IPv6 Interface Up.

[** ASSERT **]: Error 0x0000C942, Line 0, File ?

RE: nRF51: IoT-MQTT Publisher Example problems

Jim — Mon, 27 Feb 2017 12:57:33 GMT

Had not thought of this before but I am using the RIGADO BMD-300 eval board 320-00050, is that part of my problem ? --jim schimpf

RE: nRF51: IoT-MQTT Publisher Example problems

Jim — Mon, 27 Feb 2017 10:24:42 GMT

Hi, I have duplicated your script and also followed this article link text. When I follow the article I get an IPV6 connection from my PC at FD00:b::2 -> FD00:b::1 (the PI) and can ping my Nordic card at FD00:a::02EF:0bFF:FEA4:88a6 . Then I run mosquitto on the PC (and change the address in the PUB program to FD00:b::2) and still no connection. I have checked the mosquitto on the PC by running mosquitto_pub and mosquitto_sub on the PI and they publish and subscribe just fine. When I press button 0 all four LED's come on and stay on. (have to reset to recover). Also single stepping in gdb (Eclipse) I cannot step through the process of connection as the program jumps to run on the connect step.

What is step 8 in the process, "Prepare the IPv6 global prefix for the btX interface." Is that where I assign FD00:b::1 to bt0 ?

RE: nRF51: IoT-MQTT Publisher Example problems

bjorn-spockeli — Wed, 22 Feb 2017 20:40:22 GMT

device_list=( "00:8B:5C:0C:09:AC" "00:C0:1E:C1:49:66" "00:BA:F2:90:B8:FB" )

#echo $PATH
export PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/usr/games

# 6lowpan Initialization
modprobe  bluetooth-6lowpan
echo 1 > /sys/kernel/debug/bluetooth/6lowpan_enable

# Enabling IPv6 Forwarding
echo 1 > /proc/sys/net/ipv6/conf/all/forwarding

# Restart radvd service
sudo service radvd restart

# Connect to devices in the list

for i in ${device_list[@]}; do
    con_grep=$(hcitool con | grep -o $i)
    if [ "$(hcitool con | grep -o $i)" = "$i" ]; then
        #echo $(hcitool con | grep -o $i)
        #echo "$i"
        echo "Already connected to: $i"
    else
        echo "Connecting to: $i"
        echo "connect $i 1" > /sys/kernel/debug/bluetooth/6lowpan_control
    fi
done

RE: nRF51: IoT-MQTT Publisher Example problems

Jim — Wed, 22 Feb 2017 15:49:00 GMT

Thank you again, my script is ( I have two boards)




modprobe bluetooth_6lowpan


echo 1 > /sys/kernel/debug/bluetooth/6lowpan_enable


hciconfig

hciconfig hci0 reset 

echo "Connecting.."

echo "connect 00:EF:0B:A4:88:A6 1" > /sys/kernel/debug/bluetooth/6lowpan_control

sleep 5

echo "connect 00:CB:11:CB:73:15 1" > /sys/kernel/debug/bluetooth/6lowpan_control

echo "Forwarding.."

echo 1 >  /proc/sys/net/ipv6/conf/all/forwarding

sleep 1

service radvd restart

sleep 1

ifconfig bt0 add 2001:db8::1/64


Also have you tried connecting to the log output of the Nordic board ?  I can connect but get only garbage at 115200, but nothing prints at 38400. Have tried on OSX and Windows and it's the same in both.

RE: nRF51: IoT-MQTT Publisher Example problems

bjorn-spockeli — Wed, 22 Feb 2017 14:36:36 GMT

Hmm, I'll post my bash script that does the configuration and connects to my nRF52 devices when I get home((my Raspberry Pi i setup there).

RE: nRF51: IoT-MQTT Publisher Example problems

Jim — Wed, 22 Feb 2017 14:14:23 GMT

Thank you very much for the help. I have done as you suggested and added the ifconfig line to my script also I do the forward cmd and restart of radvd. I have the producer using the default address of 2001:db8::1 and running mosquitto on my PI and still no connection. The bt0 shows inet6 addr: 2001:db8::1/64 Scope:Global.

RE: nRF51: IoT-MQTT Publisher Example problems

bjorn-spockeli — Wed, 22 Feb 2017 13:29:37 GMT

I have this running on a Raspberry Pi and I have to manually add the prefix, i.e. sudo ifconfig btX add 2001:db8::1/64 every time after I disconnect and want to re-connect to the broker. Also make sure that every time you run sudo echo 1 > /proc/sys/net/ipv6/conf/all/forwarding and sudo service radvd restart after you reboot your pi.