Steve Kovarik
Forum Replies Created
-
AuthorPosts
-
Steve Kovarik
ModeratorHi William
In the ConduitAEP under “Setup” then “WAN” if you have multiple WAN’s
configured you set priority for a primary WAN and a secondary WAN to
failover to. An ICMP (10 count ping) failure will trigger a WAN failover.Steve Kovarik
ModeratorHello Christian
DeviceHQ uses TCP ports 5798, 5799 and because the hostname points to
Amazon AWS I cannot provide an IP range.-Best Regards
Steve Kovarik
ModeratorHi Dayanna
Based on the LED description there may be a problem.
You should (register/login) open a support ticket in our Support Portal
for more help.
https://support.multitech.com/support/login.html-Best Regards
Steve Kovarik
ModeratorHello Chandan
Please provide a “serial number” and model number of the device you cannot log into.
-Best Regards
Steve Kovarik
ModeratorHi Bob
In the Conduit “Remote Management” screen if SSL is unchecked (disabled)
then TCP port 5799 is used. If SSL is checked (enabled) then TCP port 5798 is used to check-in to DeviceHQ.-Best Regards
Steve Kovarik
ModeratorHi Dayanna
I would like you to try it as private by disabling (unchecking) “Public”
then “submit” at the bottom, then perform a “save & restart”. After the
Conduit has rebooted try the mDot Box/EVB.Steve Kovarik
ModeratorIn the LoRaWAN Network Server Configuration there is also a check-box to
enable “Public”. I suggest to change that setting from what it is now, then
submit at the bottom of the screen then perform a “save & restart”.
A couple of minutes after the Conduit Gateway reboots, try to have the MDot
Box/EVB to “Join” again.-Best Regards
Steve Kovarik
ModeratorHi Dayanna
Your mDot Box/EVB is attempting to “join” a LoRaWAN network with the NI, NK
and FSB parameters you posted. To solve the problem, you would need a
“LoRa Network Server” configured to accept a “Join” using the same parameters.
Do you have a “MultiTech Conduit” or some other “LoRa Network Server” server
for the MDot Box/EVB to Join.
If so how is it configured?-Best Regards
Steve Kovarik
ModeratorHi Colas
For that application to work you would need to change device A gateway to be the modem.
You didn’t mention device C, the main network router and gateway on the LAN.
I am unaware of any other solution.Steve Kovarik
ModeratorHello Nick
What did you configure in the Conduit for the Network Name and Passphrase
and what did you set the sub band to. In the Conduit LoRa Network settings
there is also a private/public setting, try changing that first.-Best Regards
Steve Kovarik
ModeratorHello Scott
MultiTech’s Conduit latest firmware release supports a master/slave
configuration for extending range using Ethernet/Wi-Fi or cellular.
However we do not have a range extending or repeater solution for very
remote areas that may not have cellular coverage. A third party wireless
Ethernet bridge may be an option if that would work for your application.-Best Regards
June 19, 2018 at 11:53 am in reply to: What is the correct antenna matching network for 915 MHz? #23896Steve Kovarik
ModeratorHi Adam
You are correct, if an external antenna is used interfaced to the U.FL
connector of the xDot, no antenna matching network is needed. It is
recommended to remove C23 to remove the chip antenna from the circuit.-Best Regards
June 19, 2018 at 9:09 am in reply to: What is the correct antenna matching network for 915 MHz? #23890Steve Kovarik
ModeratorHello Adam
The actual matching network you need is C22(4.7pf) and C26(82pf).
It would be our recommendation to add C22(4.7pf) to your design.-Best Regards
Steve Kovarik
ModeratorHello Hisham
You are generally ok if use the same antenna type with similar specifications
to the antenna that the modem passed certifications with. If you are willing, we would like to review the specifications of any alternate antennas
you consider using. We would prefer you open a support portal case to provide
alternate antenna options.-Best Regards
Steve Kovarik
ModeratorHi William
For the Conduit serial number try the Linux command mts-io-sysfs show /device-id-Best Regards
Steve Kovarik
ModeratorHello Adam
The power supply in the standard MTCDT Conduits does not have power to reliably power two LoRa cards. Only the Conduit IP67 Base Station models
MTCDTIP can reliably power two LoRa cards. The default MTCDTIP software
shipped does not include the sample script files needed to support 2 LoRa
cards but can be requested via our Support Portal. Using two LoRa cards in
the MTCDTIP is the equivalent of running two separate 8-channel packet forwarders, each on its own frequency sub-band.-Best Regards
Steve Kovarik
ModeratorHello William
The best resource for MTDOT-BOX is located at http://www.multitech.net/developer/products/multiconnect-dot-series/multiconnect-mdot-box-and-evb/
Steve Kovarik
ModeratorHi Bob
There was fix for this in the latest Conduit AEP firmware version 1.4.16,
what version of firmware is your Conduit at, and if a previous version,
could you upgrade to the latest firmware version and retest.Steve Kovarik
ModeratorHi Errin
With AT Commands the xDot only transmits when performing an OTA “Join”
or when sending data using the AT+SEND command. Other than that, while
the xDot is sitting idle it is not transmitting.There are no specific
AT Commands stop/abort a started transmission.-Best Regards
Steve Kovarik
ModeratorHi Christopher
You will need to install the MTQ-H5-B01 into a MultiTech Developer Board
model MTUDK2-ST-CELL to have the Dragonfly show up as a USB storage device.
The MTUDK2-ST-CELL allows you to plug in the communications device and use
it for testing, programming and evaluation.https://www.multitech.com/brands/socketmodem-dragonfly-dev-kit
Steve Kovarik
ModeratorHello Yoshihiro
Once you SSH into the Conduit, at the command prompt try the ‘version’ command.
Example: admin@mtcdt:~#versionMarch 1, 2018 at 12:07 pm in reply to: Accessing Conduit (MTCDT-LAT1-246A-US) remotely over cellular #22725Steve Kovarik
ModeratorHi John
Yes, AT&T does offer static IP’s associated with a SIM for “mobile terminate data”
You won’t get this at you local AT&T store. You need to talk with a M2M/IOT
division of AT&T that provides this service. AT&T contacts are regional, so
I can not provide a direct contact. Ours are provisioned through our
corporate account. Look at the i2gold APN definition at this link https://developer.att.com/technical-library/apns/apn-descriptions-and-characteristics
Your best bet may be to reach out to the AT&T small business solutions and
have a local rep contact you. https://www.att.com/smallbusiness/explore/internet.htmlAnother method to remotely monitor/manage Conduits is our free cloud based
device management solution called deviceHQ. https://www.multitech.com/brands/devicehqMarch 1, 2018 at 12:07 pm in reply to: Accessing Conduit (MTCDT-LAT1-246A-US) remotely over cellular #22726Steve Kovarik
ModeratorHi John
Yes, AT&T does offer static IP’s associated with a SIM for “mobile terminate data”
You won’t get this at you local AT&T store. You need to talk with a M2M/IOT
division of AT&T that provides this service. AT&T contacts are regional, so
I can not provide a direct contact. Ours are provisioned through our
corporate account. Look at the i2gold APN definition at this link https://developer.att.com/technical-library/apns/apn-descriptions-and-characteristics
Your best bet may be to reach out to the AT&T small business solutions and
have a local rep contact you. https://www.att.com/smallbusiness/explore/internet.htmlAnother method to remotely monitor/manage Conduits is our free cloud based
device management solution called deviceHQ. https://www.multitech.com/brands/devicehqSteve Kovarik
ModeratorHello Diego
Yes, we are making progress. This GPS feature in the AEP will be fixed in
the next firmware release. The anticipated release at this time is early March 2018.
-Best RegardsSteve Kovarik
ModeratorHi Ajay
Looking at the mDot/xDot example programs, both the OTA and AUTO_OTA example
programs have ACKs disabled, but network link checks are configured –
if enough link checks are missed, the Dot will no longer be considered
joined to the network and will attempt to rejoin before transmitting more data.
https://os.mbed.com/teams/MultiTech/code/Dot-Examples/?platform=MTS-mDot-F411-Best Regards
Steve Kovarik
ModeratorHi Paul
We offer 3D models in file formats of STEP, IGES and possibly DXF
however these need to be requested through our Support Portal.
Please “Register” and create portal request starting at the link
https://support.multitech.com/support/login.html-Best Regards
Steve Kovarik
ModeratorHi Ajay
For fringe nodes consuming more power, the main factor (with ADR enabled) is
that LoRa endpoints further away need to transmit at a higher power level
and/or a longer on air time to overcome the greater distance.
I would expect LoRa endpoints further away to consume more power to help
ensure successful transmission. Regarding the use of ACKs, there is also
trade-offs (power usage, network capacity) for ensuring data integrity.
To get around this, some developers perform data integrity checks at the
application level rather than the RF level. An alternative to enabling ACKs
for all packets is periodic connectivity checking using “link check count”
with “link check threshold”. This is used to detect when the network is not
available or the session information has been reset at the server.
Link count check defines a number of packets sent before a link check is
performed. Link count threshold sets the threshold for the number of
consecutive link check failures to tolerate before setting the join status
to not joined.
-Best RegardsSteve Kovarik
ModeratorHello Ajay
With Acks set to 5, any Acks not received by the LoRa endpoint will cause a
retransmit. Multiple retransmissions can cause the endpoint to consume more
power. Also if Adaptive Data Rate (ADR) is enabled, further distance LoRa
endpoints can increase transmit power and spreading factor (increasing time on air)
resulting in more power consumption.
-Best RegardsSteve Kovarik
ModeratorHello Alejandro
The hardware is the same between MTXDOT-NA1-A01 and MTXDOT-AU1-A01.
The difference is the firmware on each respective device.
-Best RegardsFebruary 9, 2018 at 11:52 am in reply to: Differences between MTAC-LORA-1.0 and MTAC-LORA-H-1.5 #22556Steve Kovarik
ModeratorHello Etienne
MTAC-LORA-1.0 has a USB interface and supports Semtech’s hardware reference
design 1.0
MTAC-LORA-1.5 has a SPI interface and supports Semtech’s hardware reference
design 1.5 (1.5 adds features like Spectral Scan Utility, and listen before
talk for channel plans that require it). Going forward we recommend the use
of the newer MTAC-LORA-1.5 design.
-Best Regards -
AuthorPosts