[Bryan Tran]

I wrote this mqtt client echoing program in C++ and Python year ago. Hope this sample will save you sometimes.

https://github.com/trong63/mqtt_sample

[Bryan Tran]

Hi wojtek,

I am using USB version and with the old hardware V1.0 – MTAC-LORA card.

Thanks,

BT

[Bryan Tran]

Hi All,

I just upgraded my Microchip to version 1.0.1 and tested it against with AEP-1.3.3 and I have tried 10 times OTAA and it worked 10 times.

I am using the Lora Development Utility software to configure my Microchip using the software in the following link. Click on the ‘Download’ link.

https://www.thethingsnetwork.org/forum/t/ttn-uno-beta-release-documentation/290/46.

Below is my configuration.

Microchip – version – 1.0.1:
—————————-

Under LoraWan tab:

AppKey: 2b7e151628aed2a6abf7158809cf4f3c

AppEUI: 0000000000000000

Hit ‘Save’ button and then ‘Join’ button.

Conduit – AEP-1.3.3:
——————-

Channel Plan: EU868
Public: Enable.
EUI: 0000000000000000
Key: 2b7e151628aed2a6abf7158809cf4f3c

Everything else is at default.

Click on ‘Submit’ button.

May be, try to reload the firmware on the Microchip using the tutorial above and then reconfig it as above and see if it helps ?

If not, create a support case at http://www.multitech.com/support/support

Thanks,

BT

[Bryan Tran]

Hi nabil islam/Claude Favreau,

Please create support case at – http://www.multitech.com/support/support for further trouble shooting your issue.

Thanks,

BT

[Bryan Tran]

Hi Martin,

This define in mDot.h file.

typedef enum {
MDOT_OK = 0,
MDOT_INVALID_PARAM = -1,
MDOT_TX_ERROR = -2,
MDOT_RX_ERROR = -3,
MDOT_JOIN_ERROR = -4,
MDOT_TIMEOUT = -5,
MDOT_NOT_JOINED = -6,
MDOT_ENCRYPTION_DISABLED = -7,
MDOT_NO_FREE_CHAN = -8,
MDOT_TEST_MODE = -9,
MDOT_NO_ENABLED_CHAN = -10,
MDOT_AGGREGATED_DUTY_CYCLE = -11,
MDOT_MAX_PAYLOAD_EXCEEDED = -12,
MDOT_ERROR = -1024,
} mdot_ret_code;

Thanks,

BT

[Bryan Tran]

Hi Mitsos Minas,

The easiest is use the built in network server and use mqtt client lib to receive/send data to your motes.

Conduit:
——–

1. ssh into the Conduit and go to /etc/mosquitto and modify the mosquitto.conf with the following:

#bind_address 127.0.0.1 <–Put a hash sign infront of this line to commented it out.

2. Save and exit.

3. Then type: /etc/init.d/mosquitto restart <–Restart the moquitto

Remote PC:
———-

1. Install the mosquitto software – http://mosquitto.org/download/

2. mosquitto_sub -t lora/+/+ -v -h 192.168.2.1

Then on the mDot – Send some data – You should see it shows up on your remote PC.

http://www.multitech.net/developer/software/lora/lora-network-server/mqtt-messages/

Or you can write your own application with mqtt client lib. It has multiple programming language supported.

https://github.com/mqtt/mqtt.github.io/wiki/libraries

Thanks,

BT

[Bryan Tran]

Hi Aitor Gartziandia,

You need to wait at least a min to see it resets. You can also connect USB debug cable into the USB debug connector and type linux commands/monitor it.

http://www.multitech.net/developer/products/conduit/connecting-to-the-debug-interface/

Thanks,

BT

[Bryan Tran]

Vijay,

Did you actually ssh into the Conduit or type that command at the Conduit’s Terminal ?

http://www.multitech.net/developer/products/conduit/connecting-to-the-debug-interface/

Normally, you would see prompt liked:

root@mtcd:~#

Yours is: $

Thanks,

BT

[Bryan Tran]

Hi Andreas,

Could you please web into your Conduit and go to Setup -> LoRa Network Server -> Channel Plan -> Make sure it set to your require freq. Click on ‘Submit’ button and see if it helps ?

Thanks,

BT

[Bryan Tran]

Hi dibya,

Would you please web into the unit and go to Setup -> Lora network server -> channel plan -> Check to make sure it set to EU868.

Thanks,

BT

[Bryan Tran]

Hi frederic,

http://www.multitech.net/developer/forums/topic/upgrade-1-2-2-issue/

Thanks,

BT

[Bryan Tran]

Hi Chad,

Which version of the mbed-os that you are using right now ? If it is 5.2, then try to roll back to 5.1 and see if it helps ?

Thanks,

BT

[Bryan Tran]

Hi dibya mohanty,

If you did not do any conversion from AEP to mLinux or vice versa in the past. You can find:

a. The model number of the unit on the label at the bottom of the unit. If you have something liked: MTCDT-yyyy-210x (x is either an A or L)

210A: AEP

210L: mLinux

b. Issue the command: mts-io-sysfs show product-id

c. Or you can reboot the unit and look at the boot up messages (Product-id), it will tell you.

Thanks,

BT

[Bryan Tran]

Hi Eduardo Avelar,

The lora-query is a CLI interface to register nodes/motes/mDots to the LoRa Network Server that is running on the Conduit.

The DeviceHQ is meant for the Conduits to register them self to it so that you can check the stats of the Conduits, scheduling download firmware to the Conduits ..etc..

It is not a remote LoRa NetWork Server cloud base where you can register your motes/mDots/nodes to it likes the Things network (lora network server cloud base).

https://www.thethingsnetwork.org/

Hopes to answer your questions.

Thanks,

BT

[Bryan Tran]

Hi magouero,

Try it with: http://127.0.0.1/api/system/deviceId instead with the ipaddress: 192.168.2.3

Thanks,

BT

[Bryan Tran]

Hi Andreas Zolliker,

Could you try to issue the command: +++ and see if it helps ?

Thanks,

BT

[Bryan Tran]

Hi Sandoche Balakrichenan,

I am assuming that – You have tried what Andreas Zolliker did above (refresh the web page to reveal more options in Setup -> Lora Network Server web page – and set the ‘Channel Plan’ option (either EU868 or US915) according to your MTAC-LORA card) and it still did not work for you. If so, have you tried the following:

a. Factory default the Conduit and reconfigure it.

http://www.multitech.net/developer/products/conduit/resetting-the-device/

b. Factory default the mDot with the following commands:

at&f

at&w

Then reconfigure it

c. If it is still not helping, please create a support case at http://www.multitech.com

Thanks,

BT

[Bryan Tran]

Hi Chris,

It looks like you scp the firmware file to a wrong folder. It’s supposedly into the /var/tmp folder.

You can go ahead and remove the firmware that is currently in the /home/root/ folder with the following commands:

cd /home/root/ <–Change to /home/root/ directory

ls <–List out the content of this directory

rm conduit_AEP-1.3.2_upgrade.bin

And try to scp the firmware file to the /var/tmp folder and see if it helps ?

Thanks,

BT

[Bryan Tran]

Hi Chris,

You can try upload the new firmware via the SCP or WinSCP. See the following link:

http://www.multitech.net/developer/forums/topic/upgrade-1-2-2-issue/

Thanks,

BT

[Bryan Tran]

Hi Andreas Zolliker,

Can you refresh the web page – LoRa Network Server and see if it will display with more options on this page – i.e: ‘channel plan’ option ?

If so, could you make sure to set it to ‘EU868’ instead of ‘US915’.

If not, try to reboot the unit and check it again.

Also, what firmware version on your mDot ? Issue the command: ati

Otherwise, create a support portal case at http://www.multitech.com

Thanks,

BT

[Bryan Tran]

Hi Bob,

I would check the following:

a. Verify that you can type AT commands to the mDot using either MDK or UDK2 board.

b. Power on the mDot.

c. I would also connect Ground pin on the mDot to your USB to TTL cable too.

d. Crossed the TX and RX.

e. Bring up the Device Manager on your PC and expand the ‘Ports’ tree in the Device Manager and then unplug/replug the USB to TTL cable and see what COM port that the Device Manager is detecting.

Then set your Usart terminal software to that comport with baud rate 115200 – 8n1.

f. Try a different USB to TTL cable.

Thanks,

BT

[Bryan Tran]

Hi sabrine,

Are you trying to do OTAA from the mDot to the Conduit in public mode, or are you trying to do OTAA from the mDot to the third party LoRaWAN network based cloud server through the Conduit (Conduit is setup as a packet forwarder) ? For example, TTN (the things network..etc)

If you are doing it through a third party LoRaWAN network based cloud server, then you would get those values from them.

Otherwise, if you are doing the OTAA between the Conduit, then you can get these value by web into the Conduit and go Setup -> LoRa Network Server -> Name and pass phrase.

Thanks,

BT

[Bryan Tran]

Hi sabrine,

Q: for the DevEUI it is ok it is on the device. But for the AppKey and AppEUI I am confused, how can I found them and set them in my mdot?

MTS:

AT+NK == (App Key in LoRaWAN)

AT+NI == (App EUI in LoRaWAN)

Note: Type ‘help’ to get more info for other commands.

Thanks,

BT

[Bryan Tran]

Hi Shahab Rahimi,

1. Please, create a support portal case. http://www.multitech.com/.

2. It sounded like your mDot-BOX is not able to join the network.

Thanks,

BT

[Bryan Tran]

Hi Eric,

You can flash either mLinux image or AEP image on any Conduit. However, from the mLinux to AEP version, you need to contact our Support Portal for an instruction/script of converting from mLinux to AEP.

http://www.multitech.com/support/support

However, if you want to convert from AEP to mLinux, you can just follow this link.

http://www.multitech.net/developer/software/mlinux/using-mlinux/flashing-mlinux-firmware-for-conduit/

Thanks,

BT

[Bryan Tran]

Shahab Rahimi,

Q1: because my preferred scenario is using it with loriot, after using gateway as a network server, how can I resume the loriot functionality?

* I think you can restart the loriot software with the following command:

/opt/lrt/loriot-gw restart

Q2: My main goal for using the mDot Box is to evaluate lorawan network coverage, what is best mode of mDot Box for this purpose?

* There are two modes: Single survey, Survey sweep.

http://www.multitech.net/developer/software/dot-box-and-evb-software/

Think of the Single Survey mode as a manual mode where you can manually set and do a single test at different data rate and power combinations. While the Survey Sweep will automatically test over a range of power levels and data rates.

Q3: And Can I use the mDot Box with another gateways, or only multitech ones, any refrence?

* As long as the other GW is a LoRaWan compliance.

Thanks,

BT

[Bryan Tran]

Hi Tarek SAKET,

Could you please log into the Conduit via the web browser and then go to ‘Lora Network Server’ and set ‘Network server log’ to Maximum. Click on ‘Submit’ button.

Then open up another tab on your browser and issue the following commands:

https://192.168.2.3/api/loraNetwork?method=PUT&data={“log”:{“syslog”:false,”path”:”/var/log/lora-network-server.log”}}

https://192.168.2.3/api/command/save?method=POST

https://192.168.2.3/api/command/restart?method=POST

Notes: Replace the IP address to your Conduit’s IP address. Also, do not copy and paste the commands from here into your browser. You need to type it in manually.

Thanks,

BT

[Bryan Tran]

Hi Yogesh,

You can create a http node in node red and issue the following command to fetch the status of the ppp connection

http://127.0.0.1/api/stats/ppp

Thanks,

BT

[Bryan Tran]

Hi Aamir Shabbir Hussain,

https://wiki.openwrt.org/doc/techref/opkg

Thanks,

BT

[Bryan Tran]

Hi Aamir Shabbir Hussain,

There are two versions of the Lora Network server:

a. The Lora network server – Version 1.0.8-r0.0 is for normal US915.

b. The MTS Network Server – Version 1.0.8-AU915 is for Australia.

You can run either one. But not both at the same time. To see which version is currently running, you issue the following command:

/opt/lora/lora-network-server –version

and it will only return one version liked you have posted above.

—————————————–
admin@mtcdt:~# /opt/lora/lora-network-server –version
MTS Network Server – Version 1.0.8-AU915
—————————————–

However, you said you have:

—————————————–
Thanks Bryan…….i currently have
MTS Network Server – Version 1.0.8 – AU915
Lora network server – Version 1.0.8-r0.0
—————————————-

So, I thought you meant you have both of them offline and I don’t know which version you are currently want to run. So, this is why I explained all the versions as in my previous post.

Thanks,

BT

[Author]

Posts