[Steve Kovarik]

Hello Nicolas

Here is a link to a Node-Red “flow” that will decrypt the “LoRa Demo” sensor
data from the MTDOT-BOX.
https://webfiles.multitech.com/mmm/LoRa_Demo_ParserFlow.txt

If the Conduit’s inherent “LoRa Network Server” is disabled, and the
device is configured as a simple packet forwarder to TTN, I don’t think
Node-Red will work, because all packets are simply forwarded to TNN.

Survey messages are stored on the MTDOT-BOX and can be extracted using a
Developer Board as described at the link below.
http://www.multitech.net/developer/software/dot-box-and-evb-software/configuration-mode/

Use the command AT+GSDF to get the Survey Data from the MTDOT-BOX

-Best Regards

[Steve Kovarik]

Hi Greg

By default the MTDOT-BOX does not send data to the gateway,
you will need a developer board to use the MTDOT-BOX in
configuration mode and issue the commands at+data=1 and at&w
as out lined at this link http://www.multitech.net/developer/software/dot-box-and-evb-software/configuration-mode/

Also you will only be able to get a GPS lock outside with a clear view
of the sky, and blinking LED 2 will go solid when a GPS lock is achieved.

-Best Regards

[Steve Kovarik]

Hi Chad

I am not aware of anyone experiencing this issue before. How are the devices powered? Something you can try….once you have reconfigured the Conduits, in the GUI go to “Administration” then “Save/Restore” and Set Current Configuration As User-Defined Default. Then let us know if it happens again.

-Best Regards

[Steve Kovarik]

Hi Alberto

Thanks for upgrading your mDot firmware to the latest.
It now appears the Conduit is receiving packets from the mDot.
If you ssh into the Conduit Ethernet port and login with admin/admin
and you can verify the Conduit is receiving packets using MQTT as shown at
this link http://www.multitech.net/developer/software/lora/conduit-mlinux-lora-communication/
The “data” in the received packet is in a Base64 format so you would need to
convert it back to ASCII http://www.hcidata.info/base64.htm

Regarding Node-Red, try deleting your flow, “Deploy” it, reboot the Conduit
then try re-creating the flow with a LoRa-input node, and debug-output node than “Deploy” and retest.

[Steve Kovarik]

Hello Alberto

You configuration looks OK. If you log into the Conduit and select “status & logs”
then “statistics” and then select the “LoRa” tab, do you see a device show up
under Node Address? Do you see any Pkts-up or Pkts-down.
If you issue ati to the mDot, what is the firmware level?

[Steve Kovarik]

Hello Frank

Yes, it is possible to cable to an external antenna outdoors. I would recommend that you use low loss coax cable 240 Series cabled to an outdoor rated omnidirectional antenna, for example model Laird FG9023. I feel the antenna cable would be “RP SMA male to N-male”.
-Best Regards

[Steve Kovarik]

Hi Jaco

If you are able to issue “AT” and receive an “OK”, I would recommend issuing the command AT&F then AT&W then ATZ. Your Dot is not at factory default, it appears to be running a program or be in some mode of operation. Without knowing what mode it is in, it is harder to recover. If by chance it is in Serial Data Mode, issue +++ while holding the reset button on the Developer Board (MTUDK@-ST-MDOT) to take it out of that mode. By chance have you tried any of the mDot sample programs at developer.mbed.org?

[Steve Kovarik]

OK, let’s try this.

Go to the MultiTech page on YouTube and select the video
MultiTech MultiConnect ConduitAEP

https://www.youtube.com/user/MultiTechSystems/videos

[Steve Kovarik]

[Steve Kovarik]

Hello Srikanth

Maybe this video on YouTube will be helpful.
look at time 17:45 thru 22:00

-Best Regards

[Steve Kovarik]

Joao

MultiTech model MTDOT-EVB-868 does not have an inherent GPS receiver
so it is not possible to get GPS coordinates with that device.
MultiTech model MTDOT-BOX-G-868-B does have the GPS receiver.
http://www.multitech.com/models/99999210LF

-Best Regards

[Steve Kovarik]

Hi Mohamed

We do not have enough information to help you.
What Multitech devices do you have?
How have the devices specifically been configured?

-Best Regards

[Steve Kovarik]

Hi Pascal

If the Conduit IP Address is static at 192.168.1.28 and DHCP is off,
I would recommend that you statically configure the IP Address on your
laptop NIC card to 192.168.1.111 and see if you can web into it at
192.168.1.28 or Ping it.

If it is not responding, is it possible it lost power?
Do you run a power cable up the mast to power it?

-Best Regards

[Steve Kovarik]

Hello Ajay

In the vast majority of 4G Verizon installations the APN is already
programmed into the modem from the factory, in a unique case where you have
requested from Verizon “mobile terminated data” and Verizon assigns a public
static IP Address, the modem will download the custom APN from the Verizon
network upon registration. In situations where a custom APN needs to be
programmed into the modem, you would create a case in out Support Portal to
get that procedure.

-Best Regards

[Steve Kovarik]

Hello TaeYang

Looking at the specification details of the ANT-915-05-RPSMA this antenna is
optimized for ISM Band 915MHz used in North America. Just to be sure…..
Where do you intend to use this antenna?
Specifically, which Multitech model would you use this antenna with?

The antenna does meet the requirements of a “similar antenna, with like
characteristics” of the LoRa antenna that was certified.

-Best Regards

[Steve Kovarik]

Hello Dibya

What firmware version is running on your Conduits?
1.3.3 is current and I would have you update the firmware in your Conduits.
Latest AEP firmware is here http://www.multitech.net/developer/downloads/

If you login and navigate to “Statistics & Logs” and select “Statistics”
then select the “LoRa” tab, do you see joined “Node Addresses” as well as
sent packets and received packets?

Something else to try is to power down remove the LoRa mcard from the
Conduit and re-install the mCard in the other slot, see if that makes a
difference.

-Best Regards

[Steve Kovarik]

Hi Dibya

I recommend that you re-register both Conduits to DeviceHQ and then make
sure to generate some LoRa data on both. The next time they check-in, the
the LoRa tab should be there. If it is not, please provide Conduit node ID
or Serial Numbers so we can research from here.

-Best Regards

[Steve Kovarik]

Hi Dibya

I don’t have another explanation for that behavior at this time.
Would you be able to provide a screen shot if the homepage of the other
Conduit that doesn’t show the LoRa tab in device HQ.

-Best Regards

[Steve Kovarik]

Hello Dibya

One possible cause would be if the other Conduit does not have or detect
an installed LoRa mCard.

If you log into the GUI of the other Conduit Gateway on the home page it
will show any installed mCards on lower right side of the screen.
Let us know what you see.

-Best Regards

[Steve Kovarik]

Hello Mark

Page 25 in the Developers Guide at the link below give some mDOt power
consumption numbers.

http://www.multitech.com/documents/publications/manuals/s000612.pdf

-Best Regards

[Steve Kovarik]

Hello Author

I do see the Australian power supply and power plug in our accessories
guide. http://www.multitech.com/documents/publications/marketing-guides/wireless-products-accessories-ordering-guide-release-1.6.pdf

I also see that one of our distributors Digikey also carries the power
supply. http://www.digikey.com/products/en?keywords=PS-9VCB-LBC-U-AU%2FNZ

You should be able to contact Multitech (sales) or Digikey to get what you
need.

-Best Regards

[Steve Kovarik]

Julien

Thanks for the screen shot. [10.47.137.30 is private dynamic]
The IP Address assigned to the Conduit by the cellular carrier is a
private dynamic IP address that is being firewalled by the cellular
carrier. To get to the Conduit remotely, you would need to work with the
cellular carrier to assign the Conduit a public IP Address that is
accessible from the Internet. Or in other words, tell the cellular carrier
you need a SIM card capable of “mobile terminated data”.

-Best Regards

[Steve Kovarik]

Hello Michael

I recommend that you Register then open a Support Portal case on this.
https://support.multitech.com/support/login.html

-Best Regards

[Steve Kovarik]

Hi Michael

Your MTDOT-BOX and Conduit settings seem to be optimized for the longest range.

However if you feel there may be problem with the hardware
you could try this test, but would need to use a mDot in the Developer Board.

1) Place Conduit & mDot 1.5 Meters away from each other.
2) Take antennas off mDot & Conduit.
3) Set Conduit Tx power to 26.
4) Set mDot Tx power to 20 (AT+TXP=20).
5) Set the mDot Spreading Factor to 7 with command at+txdr=3.
6) With antenna’s off, set antenna gain to zero on both mDot and Conduit.
5) Have mDot join network (AT+JOIN).
6) On mDot issue, AT+PING then AT+RSSI repeat issuing AT+PING and AT+RSSI a half dozen times, and send us the output of these two commands.

-Best Regards

[Steve Kovarik]

Here’s the link https://webfiles.multitech.com/mmm/starterKIT_bluemixFLOW.txt

[Steve Kovarik]

Hello Michael

If you double click on the “LoRa In” node and change data type from “Bytes”
to “UTF-8” is your payload legible.

Below is a link to the default IBM Bluemix Flow that ships with the Conduit
Starter Kit. Delete or export your current flow if you want to save it. To
import, go to the hamburger menu at the top right of the Node Red screen and
select import to clipboard and paste the flow. You can download it from the
link below.

starterKIT_bluemixFLOW.txt

Keep in mind that the Bluemix flow is specific to the MTDOT-BOX used in
LoRa Demo mode.

[Steve Kovarik]

Hi Michael

The MultiConnect Conduit Starter Kit For LoRa Technology ships from the
factory with a MTDOT-BOX and can send sensor data to the Conduit which
has a preconfigured Node Red flow that can send the MTDOT-BOX sensor
data to IBM Bluemix where it is visualized. I can also verify by the
serial number of the Conduit Gateway located on the bottom of the device.
http://www.multitech.com/brands/multiconnect-conduit-lora-starter-kits

If you had this, you would have noticed an existing Node Red flow in the
Node Red portion of the Conduit, and would need to use the MTDOT-BOX in
“LoRa Demo” mode of operation.

[Steve Kovarik]

Hi Akshay

That’s very strange, never experienced that.
In the Conduit if you go to “Statistics & Logs” and select “Statistics” then
select the LoRa tab. Once there select “Clear History”.

In the MTDOT-BOX select “LoRa Demo”, once successfully joined
select “trigger” then periodically select “send”

In the Conduit do you see “Pkts Up” increment that would correspond to
selecting “send” on the DOT-BOX and the Conduit receiving packets?

[Steve Kovarik]

Hello Mike

Unfortunately not, MTCDT-LVW2-210L-US will only work with Verizon.

-Best Regards

[Steve Kovarik]

Hi Akshay

I just downloaded and installed the flow from the FTP link I provided, and
it worked fine. Another idea is to drag out a “Debug Output” node and
connect it to the “LoRa Input” node and see if you receive anything in the
debug tab. This will prove the gateway is receiving LoRa packets and can
display them in the debug tab.

[Author]

Posts