Hi,

A simple question, I'm porting the code to use on pic32 over Arduino, I've made some changes on the code but one doubt persists. Witch API mode should I use on the Xbee? I'm usin a XBee S2C witch has API 1 and 2.

Thanks!

Fails with following error:

src/lib/ProcessFramework.cpp:537:16: error: use of undeclared identifier
      'CLOCK_REALTIME'
        clock_gettime(CLOCK_REALTIME, &ts);
                      ^
src/lib/ProcessFramework.cpp:541:3: error: use of undeclared identifier
      'sem_timedwait'
                sem_timedwait(_psem, &ts);
                ^
src/lib/ProcessFramework.cpp:543:3: error: use of undeclared identifier
      'sem_timedwait'
                sem_timedwait(&_sem, &ts);

I changed this on ubuntu:
/----------- Select Platform ---------/
#ifndef ARDUINO
#define LINUX
//#define MBED
#endif

/--------- Select byte order ----------/
#define CPU_LITTLEENDIANN
//#define CPU_BIGENDIANN

/-------- Select Network -------------/
//#define NETWORK_XBEE
#define NETWORK_UDP <<<<-------------------uncomment this

/--- XBee Buffer Flow Control --/
#ifdef NETWORK_XBEE
//#define XBEE_FLOWCTL_CRTSCTS
#endif

but

lsw@leiqi:~/MQTT-SN/Client# ./Build/TomyClient -i ClientID -g 225.1.1.1 -p 1883 -c -t WillTopic -m WillMessage -k 300
Client start
argument error

hi i try to compile for openwrt but failed. Can you help?

I run example client with command in the README and got this message. Someone can tell me my what's wrong?

root@demo:~/dev# ./TomyClient -i ClientID -g 255.1.1.1 -p 1883 -c -t WillTopic -m WillMessage -k 300
Client start
argument error
root@demo:~/dev# 

Hi,

I came across multiple errors when I try to compile the client in the mbed platform. But right now I am stuck with that one. Here some little explanation.

First, src/lib/* and src/mbedClientSample.cpp have been added. I modified the pins for my XBEE and added the mbed library. I defined MBED and selected the XBEE network in the MQTTSN_Application.h. Then when I try to compile, here is my error:

Error: Undefined symbol theTopics (referred from mqttsnClient.cpp.KL25Z.o).

Any solutions ?

Thanks,

Rob

Hi,

I saw that you mentioned needing 3 Xbee S2 (coordinator, gateway, client).
What is the gateway type here?

I know that XBee has 3 types: coordinator, router and end-device.
Also I thought that I could use the Xbee connected to the MQTT gateway could be a zigbee coordinator as well.

Did I miss something?

Thanks,

Nicolas

While doing make inside a MQTTSNClient directory it is failing to compile it.
There is nothing mentaioned in the README.txt.
As below:

make
g++ -o Build/TomyClient Build/src/LinuxClientSample.o Build/src/lib/mqttsnClientAppFw4Linux.o Build/src/lib/mqttsn.o Build/src/lib/mqttsnClient.o Build/src/lib/zbeeStack.o Build/src/lib/udpStack.o Build/src/lib/mqUtil.o
Build/src/LinuxClientSample.o: In function f_publish_all()': LinuxClientSample.cpp:(.text+0x153): undefined reference toMqttsnClientApplication::publish(MQString_, Payload_, unsigned char)'
Build/src/LinuxClientSample.o: In function f_onRequest_01(MqttsnPublish*)': LinuxClientSample.cpp:(.text+0x344): undefined reference toMqttsnClientApplication::publish(MQString_, Payload_, unsigned char)'
Build/src/lib/mqttsnClientAppFw4Linux.o: In function MqttsnClientApplication::initialize(int, char**)': mqttsnClientAppFw4Linux.cpp:(.text+0x439): undefined reference totheAppConfig'
mqttsnClientAppFw4Linux.cpp:(.text+0x448): undefined reference to theAppConfig' mqttsnClientAppFw4Linux.cpp:(.text+0x45d): undefined reference totheAppConfig'
mqttsnClientAppFw4Linux.cpp:(.text+0x467): undefined reference to theAppConfig' mqttsnClientAppFw4Linux.cpp:(.text+0x46d): undefined reference totheAppConfig'
Build/src/lib/mqttsnClientAppFw4Linux.o:mqttsnClientAppFw4Linux.cpp:(.text+0x473): more undefined references to `theAppConfig' follow
collect2: error: ld returned 1 exit status
Makefile:34: recipe for target 'Build/TomyClient' failed

make: *** [Build/TomyClient] Error 1

Please help if any modifications in source code.
Thanks
Manjunath

• pthread, rt librairies to be linked.
• wiringPi (http://wiringpi.com/download-and-install/)

Hi, I'd like to know if the project is still under development, if yes, what is the final result you expect?
Because I got have the feeling that, we could turn the project into something bridges sensor network with mqtt broker(mosquitto) , not only xbee, but others. I think we should change the building process, so that it can be built and installed as *NIX server on background. We can even upload it into standard Linux repository, so that everyone can install by only command line "apt-get / yum ... "
What do you think?

I'd be very keen to hear from anyone running this in production using XBees. We have had the gateway working but it is currently stuck on SEARCHGW. No doubt a local config issue that we're yet to resolve, but I'm a little concerned how easily these seem to creep in and how hard they are to detect.

Hi:
I compiled MQTT-SN/Clint followed the README, the code was build fine. But when I execute "TomyClient", it showed that "Segmentation fault (core dumped)". I used GDB to find the problem. Messages as following:

Program received signal SIGSEGV, Segmentation fault.
strlen () at ../sysdeps/x86_64/strlen.S:106
106 ../sysdeps/x86_64/strlen.S: No such file or directory.
(gdb) where
#0 strlen () at ../sysdeps/x86_64/strlen.S:106
#1 0x00007ffff758382e in __GI___strdup (s=0x0) at strdup.c:41
#2 0x0000000000401b12 in MqttsnClientApplication::initialize(int, char**) ()
#3 0x000000000040123d in main ()

Do I lack something?

Thanks

wjungle