Steve Kovarik
Forum Replies Created
-
AuthorPosts
-
Steve Kovarik
ModeratorHi Manuel
Please look at “Network Architecture” at the link below and let us know
any additional questions you have.Steve Kovarik
ModeratorHello Lucian
MultiTech does not use Eagle CAD so we do not have an Eagle CAD library.
Regarding a confirmation, we can not vouch for accuracy of what is
posted at the link you provide, however the footprint appears correct.-Best Regards
Steve Kovarik
ModeratorHi Boyku
Although I would expect that you would see some signal with the RG58U cable
for best results it would be recommended to use a low loss RG213 or LMR240/LMR400 cable.January 17, 2018 at 9:41 am in reply to: Accessing Conduit (MTCDT-LAT1-246A-US) remotely over cellular #22358Steve Kovarik
ModeratorHi John
First you would need to approach AT&T and request a SIM card that supports
“mobile terminated data”. One way this is accomplished is for AT&T to
provision the SIM with a public, static IP address. Once you have an AT&T
SIM correctly provisioned with the capability to accept inbound connections
next configure the Conduit AEP to accept inbound connections over cellular
by logging in and selecting the “administration” tab then “access configuration”.
Under HTTPS enable the checkbox “via WAN”
For remote SSH access enable the checkbox “via WAN” under SSH.
Scroll to the bottom of the screen select “submit”
then select “Save & Restart”Steve Kovarik
ModeratorHello Martin
The MTCDTIP-LVW2-266L-915 Gateway is limited to Verizon, any other carriers
SIM cards (Sprint/AT&T) would not work in this device.
-Best RegardsSteve Kovarik
ModeratorHi Jose
Are you looking for a battery operated LoRaWAN GPS tracking device like the
one at the link below.
http://digitalmatter.com/OYSTER-LoRa-BATTERY-GPS-TRACKER#62811-specifications-Best Regards
Steve Kovarik
ModeratorHi Ian
Can you try a ssh client like putty and try and ssh into the Conduit at 192.168.2.1
Steve Kovarik
ModeratorHi Ian
Yes, you do need to set your PC IP address to static on the same subnet.
If you can successfully ping the gateway at 192.168.2.1
have you tried browsing to it using https https://192.168.2.1Steve Kovarik
ModeratorHi Vqa
We have known bug if you change the http port. You will need to factory
default the device to recover it. After you recover the device, we recommend
that you do not change the http port. The conduit enforces https access to
the web administration, so changing the http port has no benefit.-Best Regards
Steve Kovarik
ModeratorHi vqa nguyen
I would recommend that you straighten out a paperclip and use it to hold
the reset (microswitch) on the front panel “in” for 35 seconds to
factory default the device.However based on your changes, I would have thought you could successfully
browse to https://192.168.2.1 the LAN IP Address of the device to administer it.-Best Regards
Steve Kovarik
ModeratorHi Julien
Try the instructions at the link below. Let us know if this does not work for you.
http://www.multitech.net/developer/products/multiconnect-conduit-platform/conduit/connecting-to-the-debug-interface/-Best Regards
Steve Kovarik
ModeratorHi Mary
Some things to verify.
Windows device Manager should show two COM ports enumerated.
XR21V and ST Link Virtual.
You would select ST Link Virtual to issue AT Commands to the EVB.
On the EVB be sure you scroll to and select “Configuration” on the EVB
LCD menu screen to issue AT Commands.
Other than that, the orientation of the ribbon cable is critical and use
115200, 8, N, 1 Terminal settings.-Best Regards
Steve Kovarik
ModeratorHi Julien
It sounds like you have installed the SIM card correctly.
We would recommend that you open a Support case at the link below.
https://support.multitech.com/support/login.html
Going to “Stats&logs” then “Statistics” then “show PPP trace” is the next step to try and determine why.-Best Regards
November 14, 2017 at 9:14 am in reply to: Connection failed; try to connect m/xdot to a conduit AEP #21742Steve Kovarik
ModeratorHi William
Yes, if configuring a Dot with AT Commands the commands are the same for
for a mDot and xDot. If you are still unsuccessful to “join” and “send”
data to the Conduit we would recommend you open a Support Portal case
so we can review the Dot settings (at&v) and the Conduits LoRa Network settings. Let us know how it goes.-Best Regards
November 13, 2017 at 8:54 am in reply to: Connection failed; try to connect m/xdot to a conduit AEP #21727Steve Kovarik
ModeratorHi William
If you have the Conduit AEP you should follow the instructions at this
link http://www.multitech.net/developer/software/lora/getting-started-with-lora-conduit-aep/The video at the link below should also be helpful.
https://www.youtube.com/watch?v=H18pVF8qIaY-Best Regards
October 24, 2017 at 9:41 am in reply to: How to dectypt the messages sent by mDot box in Lora demo mode #21267Steve Kovarik
ModeratorHi Richard
Thank you for taking the time to provide feedback, it is through the insight
from those on the outside looking in that we are able to truly improve our
customers experience. I thank you for that. I will personally see to it that
future videos are more detailed and complete. Thanks for using MultiTech!-Best Regards
Steve Kovarik
ModeratorHi Davy
Today MultiTech’s Conduit Gateways support….
a) Single Conduit acting as Packet FW + Lora ServerThis allows our customers to create their own private LoRa Network.
d) Multiple gateways / Cloud LoRaWAN server
This allows our customers to use multiple gateways as packet forwarders
in a public LoRa Network environment where multiple gateways are needed
to add scale.We are currently working on solutions that address the other scenarios you
describe. However I am unable to describe in detail until we are closer to
release in early 2018. Hope this is helpful.-Best Regards
October 23, 2017 at 11:59 am in reply to: How to dectypt the messages sent by mDot box in Lora demo mode #21252Steve Kovarik
ModeratorHi Richard
My apology, our developer site, videos and forums are intended to help
developers of all skill levels use our products. Unfortunately it is very
difficult for us to cover every possible use case in these mediums.By default all survey data is stored on the MTDOT-BOX and can be viewed on
the screen or downloaded off the device for analysis. This is documented on
our developer site http://www.multitech.net/developer/software/dot-box-and-evb-software/survey-sweep/We are happy to provide a path for our customers to “ask” and obtain answers
due to the myriad of applications that our Development Platform can be used
in. We are open to any recommendations that you may have to help us help you
(our customers) better.-Best Regards
Steve Kovarik
ModeratorHi Daniel
Yes, it is possible to do using the same conversion procedure.
However we require that you open a support portal case to get
access to the needed files.-Best Regards
October 13, 2017 at 11:56 am in reply to: How to dectypt the messages sent by mDot box in Lora demo mode #21174Steve Kovarik
ModeratorVinesh
Using the MTDOT-BOX outside in “Single Survey” or “Survey Sweep” modes can
send GPS data to the Conduit. You must first configure the MTDOT-BOX to
send data to the Conduit using the command AT+DATA=1 and save with AT&W
You will also need to insert a micro SD memory card behind the Conduit front
panel to store survey data. Here is a link to DOTBOX_GOOGLE Node Red flow
that can be imported and used to view GPS data on Google maps. As shown at
the 14:40 time in the video at this link https://www.youtube.com/watch?v=r7ez4pd9N2c
https://webfiles.multitech.com/mmm/DotBox_Google.txtOctober 10, 2017 at 9:21 am in reply to: What is the model number of LoRa radio present in MTAC-LoRa Cards #21155Steve Kovarik
ModeratorHello Vinesh
The MTAC-LORA card utilizes a Semtech SX1301 transceiver.
October 5, 2017 at 4:52 pm in reply to: How to dectypt the messages sent by mDot box in Lora demo mode #21114Steve Kovarik
ModeratorHi Vinesh
Another option is to follow the video at this link https://www.youtube.com/watch?v=r7ez4pd9N2c
The code to create the function node at the 6 minute mark is at this link
https://webfiles.multitech.com/mmm/LoRaDemoFnNode.txt
-Best Regards
Steve Kovarik
ModeratorEdgar,
Thank you for the update. We would recommend a 50 Ohm, low loss RF antenna coax cable if the Conduit is located 30 meters away from the antenna.Steve Kovarik
ModeratorHi Mikael
So after factory defaulting the device you can log into the Conduit web administration but still can not successfully log into Node-Red?
If so, I may encourage you to register and open a Support Portal case for next steps.
https://support.multitech.com/support/login.htmlSteve Kovarik
ModeratorHello Edgar
I am not aware of anyone using that specific antenna, but based on the
specifications it looks to be good performer. You can directly connect the
antenna without the need for any amplification equipment. What height do
you intend to mount the antenna.Steve Kovarik
ModeratorHello Davy
The MultiConnect® Conduit Access Point (AP) is positioned as a lower cost
LoRa Gateway with a consumer temperature range for indoor use (-10 +60C).
When this device is used with a public LoRa Network Server it can provide
improved service level agreement (better reception coverage) for indoor use.
Because this product family is brand new, it is just making its way into the
distribution channel.-Best Regards
September 29, 2017 at 9:43 am in reply to: How to dectypt the messages sent by mDot box in Lora demo mode #21024Steve Kovarik
ModeratorHello Vinesh
Assuming you have a MultiTech Conduit Gateway AEP version that has Node-Red,
once you are in Node-Red drag a “LoRa in” node, a “Function” node and the
“Debug out” node onto the canvas then connect the “LoRa in” to the “Function”
node and connect the “Debug out” node to the “Function node”. Next double click
on the “Function” node and delete [return msg;] on line 2. Then copy and
paste the code at the link below into the Function node.
Then select “OK” and “Deploy”. Now as LoRa packets are received and show up
in the debug tab you should notice “temp”, “x,y,z”, “baro_preasure” and “lux”
with decrypted data sent from the MTDOT-BOX in LoRa Demo mode.
https://webfiles.multitech.com/mmm/EVBParserLatest.txt-Best Regards
Steve Kovarik
ModeratorHi Mikael
What I suggested and what you have done should be all that is needed to
access Node-Red remotely. My only other suggestion would be to upgrade
the Conduit firmware to the latest version 1.4.3 and then factory default
the device by using a paperclip and holding in the micro switch “Reset”
button on the front panel for 30 seconds. Then reconfigure and see if the
issue persists. The latest AEP firmware is available at this link.Steve Kovarik
ModeratorHello Mikael
Assuming your SIM card is provisioned to allow “mobile terminated data”
if you log into the Conduit web administration and select the “Administration” tab
then select “Access Configuration” you will see a Node-Red section and you
should enable the checkbox labeled “via WAN” then scroll to the bottom
and select “Submit” then “Save & Restart”. Also as a mobile terminated data
test, on the same screen (upper right) under HTTPS enable the checkbox
labeled “via WAN” (submit then save & restart) and you should be able to browse to the public IP address of the Conduit and get to the web
administration remotely.-Best Regards
Steve Kovarik
ModeratorHello Norman
Class B has not been implemented on MultiTech’s LoRa endpoints (xDot/mDot)
or in the Conduit Gateway, so it is not possible to test Class B yet
using MultiTech equipment. -
AuthorPosts