Steve Kovarik
Forum Replies Created
-
AuthorPosts
-
Steve Kovarik
ModeratorHi William
Today Wi-Fi is not part of the “partial configuration” feature in DeviceHQ.
For Wi-Fi capable Conduits you would need to upload to DeviceHQ a full
Conduit configuration file with desired Wi-Fi settings that would
become available to schedule for download to other Wi-Fi capable Conduits.-Best Regards
Steve Kovarik
ModeratorHi Christopher
Precise time stamp models are different hardware.
Why/what do you need precise time stamp for?-Best Regards
Steve Kovarik
ModeratorHello -C
IP67 Conduits with AEP do not support precise time stamping.
Currently only mLinux models MTCDTIP-xxx-275L-xxx support precise
time stamping for geolocation using TDoA.-Best Regards
Steve Kovarik
ModeratorHi Ian
Ok, I would recommend to factory default the Conduit by holding in the
“reset” micro switch on the front panel for 31 seconds. After it reboots
log in and reconfigure and see if that doesn’t solve the issue.-Best Regards
Steve Kovarik
ModeratorHi Ian
If the LoRa card is successfully detected by the Conduit it will show up
in the Home screen under Accessary Cards. Can you verify that.Steve Kovarik
ModeratorHi Cannuh
On the Starter Kits the mDot BOX was preconfigured at the factory to
successfully “Join” the Conduit. If you observe that the mDot BOX is stuck
at the joining phase we conclude the mDot BOX can not join the Conduit
most likely due to a configuration parameter. You can open a ticket at the
link below for additional help.
https://support.multitech.com/support/login.htmlSteve Kovarik
ModeratorMultiTech’s V2.1 Gateway for geolocation is a Packet Forwarder that is
intended to be used with a public “LoRa Network Server” that offers/provides
geolocation as a service. All packets are forwarded to the LNS that uses
TDoA to calculate location.Steve Kovarik
ModeratorSteve Kovarik
ModeratorHello Pascal
When ADR is enabled on a LoRa end node, the Network Server can adjust
the Datarate (Spreading Factor) and Transmit Power of the Lora end node
based on SNR values of a set of received packets on the Network Server.
A more detailed description can be found at the link below.
Steve Kovarik
ModeratorHello Towo
The reset is not needed, simply issue +++ (no carriage return) to escape
back into to “command mode” where you can exit Auto OTA mode with the
commands at+njm=1 then at&w (store to novram) and atz (reset).Steve Kovarik
ModeratorHi Jo4p
MultiTech’s Conduit Gateways currently support Semtech HW reference design v1.5
which does not provide accurate timing for geolocation. We do manufacture an
IP67 Conduit Gateway that provides accurate timing and supports Semtech HW
reference design V2.1 for geolocation support. See the link below for the
V2.1 Gateway referenced for geolocation support.
https://www.multitech.com/models/94557528LFSteve Kovarik
ModeratorHi Nicolas
DeviceHQ is for Conduit AEP models and currently not available for mLinux build options.-Best Regards
Steve Kovarik
ModeratorHi Kirk
I would recommend modifying the gateway_ID on the Conduit, save & restart
then login and save the configuration file to a pc and upload it to DeviceHQ.
Then you can go back and set the gateway_ID to what it was.Was re-zipped file uploaded to DeviceHQ tar.gz
Steve Kovarik
ModeratorHi Kirk
LoRa partial configuration using DeviceHQ is a known issue being worked on.
I recommend uploading a known good “configuration file” to DeviceHQ so it
is available to “push” to all gateways. Before saving the configuration
file to upload, modify the “gateway_ID” line in the JSON gateway_conf to add placeholder “gateway_ID”: “<WILL-BE-AUTO-REPLACED-WITH-LORA-EUI>”,Steve Kovarik
ModeratorHi Jonathan
MultiTech is currently working on the next generation Conduit Gateway that
will utilize a ARM Cortex A9. We anticipate availability towards the end of this year.-Best Regards
Steve Kovarik
ModeratorHello Julien
AEP versions of the ConduitAP have a configurable option to store up to a
maximum of 1000 sent and received SMS text messages. If you reach the limit the
oldest messages are overwritten.-Best Regards
December 20, 2018 at 10:59 am in reply to: LoRa network server Rx1 delay configuration not taken in account #26999Steve Kovarik
ModeratorHi Marine
If you upgrade your MTCDT-H5-210A to the latest firmware, there is a
configurable “Rx1 Delay” field in the LoRaWAN Network Settings Conduit GUI.
Shown on page 12 in the document at the link below.
http://www.multitech.net/developer/wp-content/uploads/downloads/2018/04/AEP-1.4.16-UpgradeGuide.pdf-Best Regards
Steve Kovarik
ModeratorHi Travis
When you enable “Network Server” from the dropdown do you select “submit” at the bottom of the screen
and then select “Save & Restart” so the changed settings take effect?Steve Kovarik
ModeratorHello Damon
In the vast majority of cases the Verizon APN is sent down over the air
to the modem upon network registration. That is why there is not an APN field
in the GUI of Verizon Conduit model MTCDT-LVW2-247A. In very rare cases where
Verizon indicates a custom APN is required to be configured into modem, it can be done, and would be suggested to open a Support Portal case.-Best Regards
Steve Kovarik
ModeratorHi Christos
My Conduit Gateway (firmware 1.6.2) behaves similar on “restart” where both
the Ethernet and cellular PPP are active after boot-up until the idle timeout
setting (180s) expires on the cellular dial-on demand settings. Then the
CD LED (Carrier Detect) on front panel goes off indicating the cellular packet data connection was terminated. What is the status of the CD LED on
your Conduit Gateway after the device sits for five minutes after a reboot?Steve Kovarik
ModeratorHi Christos
In addition to configuring cellular for “dial-on-demand” I would also suggest
under “Setup” then “WAN” for the Cellular entry, edit the failover configuration
“Monitoring Mode” to be Passive rather than active.-Best Regards
November 7, 2018 at 11:50 am in reply to: Dedpulication for Multiple Multitech Conduits running Network Server #26722Steve Kovarik
ModeratorHi Joe
In the scenario you describe you will need to configure the Conduit AP
and LoRaWAN sensors to “join” a specific single Conduit AP. With each LoRaWAN
sensor associated with a specific Conduit Gateway there wouldn’t be duplicate
messages. Unauthorized LoRaWAN sensor packets are filtered at the Conduit Gateway.Steve Kovarik
ModeratorHi Sebastien
Try the default password of admin/admin. If that doesn’t work hold
the “reset” micro switch in on the front panel with a paperclip for 31
seconds to factory default the device and try again.-Best Regards
Steve Kovarik
ModeratorIn the web administration go to “Administration” then “Access Configuration”.
Under Node-Red enable “Via WAN” then submit at the bottom then Save & Restart.Steve Kovarik
ModeratorHello William
Could you please upgrade the firmware in your MTCDTIP-LAT1-266A to the
latest version 1.6.2 and retest.This has fixed another customer of mine with same problem.
-Best Regards
Steve Kovarik
ModeratorHi Rick
I see that you have already registered in our Support Portal.
I’ll create a case for you and attach MTDOT-xxxX1-UFL STEP file.
You will need to log into the support portal to download the file.
Your email is your username.-Best Regards
Steve Kovarik
ModeratorHi Chad
If all your LoRa end devices are configured identically and you use the same
network name and passkey credentials in the Gateways it becomes difficult.
If using the LoRa Network Server in the Gateway one possibility is to configure
different Gateways for a different “frequency sub band (FSB)”. The Conduit has a FSB configuration setting between 1 and 8 and is an 8-channel hybrid of
64 total channels. Configuring adjacent Gateways for a different FSB is one
way to filter LoRa end devices. However for this to work you will need to
configure the (same) frequency sub band setting in the LoRa endpoint device
relative to the Gateway you want it to Join. The cloud key management is a
future feature release with no documentation available yet. Configuring
unique keys per LoRa end device and in each Gateway is another way to filter
LoRa end nodes per gateway.-Best Regards
Steve Kovarik
ModeratorHi Ardi
We recommend that you register and open a Support Portal ticket for your
MTAC-LoRa-H pinout request. Here’s a link https://support.multitech.com/support/login.html-Best Regards
Steve Kovarik
ModeratorHi
I would suggest that you try holding in the “reset” button for 31 seconds, or
until you see a change in the front panel LED’s. Then try root/root again.-Best Regards
Steve Kovarik
ModeratorHello ConduitHelp
Could you please email your contact information to salesfae@multitech.com
with the intent in having a brief conversation.-Best Regards
-
AuthorPosts