[Peter Ferland]

Are you using HTTP request and response nodes? You should not require a login when using these nodes to handle a request.

[Peter Ferland]

We ran a similar example (modification of the loop in ota_example) overnight in a constant transmit/receive loop with a Conduit without going to sleep. Its still running after 45k packets.

The only other vector related thing that comes to mind to check is using a resize before the loop and then using array access instead of push_back. I’ll try one more experiment with running exactly your code and run that over the day.

[Peter Ferland]

Can you post a screen shot of the LoRa network server page in the web interface? ie, using the default IP https://192.168.2.1/lora_network.html

[Peter Ferland]

What is the 3rd party device? Is it listening on the correct channel for the join reply? Because the 915MHz conduit is a 8 channel, not a 64 channel gateway the device may be expecting a different frequency. See here: http://www.multitech.net/developer/software/lora/introduction-to-lora/

[Peter Ferland]

Double check that you’ve soldered your connections on the DK to the correct pad – on the UART_TX and UART_RX pins are not right above each other, TX is the 2nd closest to the USB port on the bottom of the board not the closest.

I only ask because I did it the first time I connected a UART on the xDot…

[Peter Ferland]

iptables will be blocking inbound connections over WAN by default. You can add a rule to allow connections over 880 in the firewall settings options in the web interface. ie, https:// /firewall.html

• This reply was modified 7 years, 3 months ago by Peter Ferland.

[Peter Ferland]

They have been tested in similar conditions without failure. I have seen memory leaks in similar conditions in customer code but we have not been able to reproduce a problem with the library on our own systems. Any extra info would be helpful.

• This reply was modified 7 years, 3 months ago by Peter Ferland.

[Peter Ferland]

Can you try using libmdot-dev-mbed5?

• This reply was modified 7 years, 3 months ago by Peter Ferland.

[Peter Ferland]

Can you share the code in your main loop where you’re creating and populating the vector?

[Peter Ferland]

The USB device connector provides a serial terminal so you could just use stdout there You’d need to handle the lora data as if you were on a mlinux conduit after installing the mosquitto mqtt pub/sub commands from the mosquitto-clients package. http://www.multitech.net/developer/software/lora/conduit-mlinux-lora-communication/
You can also try plugging in a USB serial adapter into the USB host connector, modules for some chips are available in the opkg feed. For example the pl2303’s module is provided by kernel-module-pl2303

[Peter Ferland]

The simplest method would be to use a MTAC-MFSER card. There is a node red output node for the MFSER module so the flow could be as simple as a LoRa input node, a function node that parses the message and the output node to the serial port. You can also interface to the serial port as you would any other at /dev/ttyAP1 or /dev/ttyAP2 depending on which accessory port you used. If you use the commandline you’ll need to set the mode using the mts-io-sysfs function described here:

MTAC-MFSER Usage

[Peter Ferland]

The Conduit is limited to listening on 8 channels at a time. There are 64 uplink channels in LoraWAN between 902.3MHz and 914.9 MHz for a total of 8 subbands. 910.9MHz is channel 43 in frequency sub band 5. If you set the Conduit to using frequency subband 1 it will be listening on the first 8 channels – 902.3MHz to 903.7MHz. Your device is listening for a response on receive channel 3 which is correct based on uplink channel 43, but if the Conduit was not configured for frequency subband 5 then it could not receive the transmission.

Try restricting your device to only using channels 0-7 (902.3-903.9MHz) and set the Conduit to frequency subband 1.

Introduction to LoRa

Conduit AEP: LoRa Use With Third-Party Devices

[Peter Ferland]

Correct, the MTMDK-ST-MDOT does not require a power adapter. Does your mDot have the programming header installed? mDots with this header installed have a part number of the form “MTDOT-xx-X1P-SMA”. The header that should be populated is the one opposite the antenna connector.

If this header is installed, do the PWR and D2 leds come on when you plug in the USB connector?

[Peter Ferland]

After the actility firmware is installed you will need to follow the mLinux instructions for flashing the firmware here: http://www.multitech.net/developer/software/mlinux/using-mlinux/flashing-mlinux-firmware-for-conduit/

You will need to extract the uImage.bin and rootfs.jffs2 files from the AEP bin. Simply treat the .bin as a tar.gz file to extract.

[Peter Ferland]

When an mbed USB drive such as the mDot’s shows 0KB available that usually means that the mbed programmer chip could not communicate with the target. There should be a text file labeled “FAIL” in the root of the drive.

Are you using the MTUDK2-ST development board? If so you will need to connect the external power adapter before plugging in the USB cable.

[Peter Ferland]

Actility has their own firmware image that they write to the Conduit. Either mLinux or AEP can be replaced with Actility’s firmware. When you log into ThingPark go to the FAQ, then the “Your Gateway” tab and follow the Multitech Conduit instructions under “How to connect your gateway?”

[Peter Ferland]

Microchip & Multitech did work together on interop testing around 1 year ago and all was working fine. I’m not aware of any regression with newer versions.

And the same 868/915 LoRa Motes are used to validate each Conduit LoRa software update. During an investigation of this issue it was found that we never updated the firmware on the motes so testing was always performed on firmware version 1.0.0 dated October 2015. Testing is now being done on RN2483 firmware 1.0.1. I will update you as soon as I get results.

[Peter Ferland]

The difference is regulatory – for the module to remain on Multitech’s FCC and CE certifications the product must leave our factory for one or the other regulatory environments.

If you are manufacturing a separately certified product then something may be able to be arranged. Contact your sales contact at Multitech or your distributor to get that conversation started.

• This reply was modified 7 years, 3 months ago by Peter Ferland.

[Peter Ferland]

Using the STM32L151CC’s full JTAG interface is not available because some of the pins that are multiplexed for JTAG are used to communicate with the LoRa radio. You are limited to SWD.

If you do not wish to use the JP1 connector on the MTMDK-XDOT, you can use an ST-LINK programmer http://www.st.com/en/development-tools/st-link-v2.html

[Peter Ferland]

The limiting factor is that google V8 dropped support for armv5 after V8 version 3.17. This means that versions of node.js that require later versions of V8 cannot be compiled for the Conduit.

• This reply was modified 7 years, 3 months ago by Peter Ferland.

[Peter Ferland]

pymodbus can be installed on the conduit however its not quite as simple as using minimalmodbus or pymodbustcp because it depends on the compiled python extension “twisted” for threading.

An ipk is not provided on the default package feed so you’ll have to cross compile it yourself using the bitbake environment documented on this page: http://www.multitech.net/developer/software/mlinux/mlinux-building-images/building-a-custom-linux-image/
The recipe name is python-twisted. You do not need to build an image, you can scp over the python-twisted-core ipk to the Conduit and install using opkg. After that you can use pip to install pymodbus.

[Peter Ferland]

Hi Prakash,
Can you try putting the set-rs485 call inside the python script after you open the tty like this:

import minimalmodbus
import os
instrument = minimalmodbus.Instrument('/dev/ttyAP2', 1)
os.system('set-rs485 /dev/ttyAP2 1')
reading = instrument.read_register(40605, 4)

[Peter Ferland]

Are you running mLinux or AEP? The API service is the major difference between mLinux and AEP. The API is not available on mLinux images.

• This reply was modified 7 years, 3 months ago by Peter Ferland.

[Peter Ferland]

In node red when you return an array it will actually output each message in the array one at a time. If your code works for one message, it should work for the array.

See the the official node-red documentation here: https://nodered.org/docs/writing-functions#multiple-messages

[Peter Ferland]

Since you’re using the AEP model you can make use of the device hq application management infrastructure by creating a custom application package using the following instructions: http://www.multitech.net/developer/software/aep/creating-a-custom-application/
Theres instructions for manual installation during development on this page: http://www.multitech.net/developer/software/aep/creating-a-custom-application/custom-development/

AEP is based on mlinux so you are free to create an init.d script that calls an application anywhere, say /opt/ or /usr/bin but you’ll have to manually reinstall after a firmware update. There is a very small partition that is not wiped out on firmware upgrades at /var/config but it is only 8MB and is intended for configuration files and the like.

• This reply was modified 7 years, 3 months ago by Peter Ferland.

[Peter Ferland]

I didn’t see your last post before my reply, sorry.

For that use case you could call a python script using an “exec” node that just passes your message as an argument. (msg.payload is the first argument by default)

[Peter Ferland]

As an alternative I’d recommend using python. I’ve used minimalmodbus for serial and pyModbusTCP for TCP. If you’re using mqtt a good, simple python mqtt client is paho-mqtt. Simple usage examples for pyModbusTCP are on the project’s page:
https://pypi.python.org/pypi/pyModbusTCP/
https://eclipse.org/paho/clients/python/

Paho-mqtt has a convenient method for single shot publishing: https://eclipse.org/paho/clients/python/docs/#id17
You can publish to a topic the mosquitto server running on the conduit at localhost:1883 without authentication. You can then subscribe to the topic you choose using a node-red input node. (Or publish directly to a remote server)

The easiest way to install all this on the Conduit is running these commands:
# opkg update
# opkg install python-pip
# curl https://bootstrap.pypa.io/ez_setup.py | python
# pip install pyModbusTCP
# pip install paho-mqtt

[Peter Ferland]

Is the RN2483 configured for OTAA or ABP joins?

[Peter Ferland]

Ok, can you post the output of a debug node on output of the LoRa node?

[Peter Ferland]

Can you post the node red flow?

[Author]

Posts