[Steve Kovarik]

Hi Alex

Yes, the Conduit can be configured as a Wi-Fi Access Point.
Login and select ‘Wireless’ then ‘Wi-Fi Access Point’ and ‘enable’ the
enabled check-box. Create a SSID and select ‘Security Options’ then
select the desired security mode (WPA/WPA2-PSK) and configure a password if necessary.
Then perform a “Save & Restart” and wait for the Conduit to reboot before
trying to get your phone to join the Wi-Fi Access Point.

-Best Regards

[Steve Kovarik]

Hi Alex

A cell phone can be used as a Wi-Fi hotspot to provide Internet access to a Conduit that has Wi-Fi capabilities.
To accomplish that login to the Conduit and select ‘Wireless’ then
‘WiFi as WAN’. Select ‘enable’ then ‘Add Network’ and enter a name, and the hotspot SSID
then select the ‘Security Mode’ and enter a ‘password’ if required then
perform a ‘Save & Restart’. After the Conduit re-boots look at the ‘Home’
screen to see if ‘Wi-Fi as WAN’ connects to your Wi-Fi hotspot (phone).

-Best Regards

[Steve Kovarik]

Hi William

Quick answer is no.
The new CAT-4 Conduits (L4N1) are not backwards compatible because the older
Conduit AEP firmware did not support the new CAT-4 (L4N1) modems.

-Best Regards

[Steve Kovarik]

Hi Omri
MultiTech does not manufacture a 433MHz transceiver LoRa endpoint.
Nor do I have a good recommendation for one.

-Best Regards

[Steve Kovarik]

Hi Pedro
I re-visited this today.
Without a SIM card installed in the modem the result to the ‘at+clac’ command is ERROR, and the modem is not locked up, I can issure additional commands.

Today I installed a valid SIM card in the modem and the modem and the result to the ‘at+clac’ command was several lines of valid commands followed by
‘OK’. And the modem did not lock-up. I am communicating with the modem using
Teraterm with the modem in a MultiTech developer board.

-Best Regards

[Steve Kovarik]

Hello Pedro

The AT Command ‘at+clac’ doesn’t work on any of my modems either, so I deduct
that Telit (Radio Module Vender) has not implemented this command.

-Best Regards

[Steve Kovarik]

Hi Pat

For AppEUI use at+ni=0,xxxxxxxxxxxxxxxx
For AppKEY use at+nk=0,xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
where hex Byte = xx

https://www.multitech.com/documents/publications/reference-guides/s000643.pdf

[Steve Kovarik]

Hi George

It would be better to open Support Portal case on this topic.
Could you please open a ticket at the link below.
https://support.multitech.com/support/login.html

-Best Regards

[Steve Kovarik]

Hi Pat

The MTDOT-BOX is not limited to MultiTech LoRaWAN Gateways, the MTDOT-BOX
can be configured to work with any LoRaWAN compliant Gateway.
The MTDOT-BOX does come pre-configured from the factory, but can be
reconfigured to work with other 3rd party LoRaWAN Gateways.
See the link below for how to configure the MTDOT-BOX.

Configuration Mode

-Best Regards

[Steve Kovarik]

Hi Akash

Is the device new out of the box, or has it been programmed before?
I would recommend holding in the ‘reset’ micro switch for 35 seconds
then allow the device a few minutes to boot-up.
Configure your PC for DHCP client and see if you can obtain an IP from
the Conduit then try the web administration at https://192.168.2.1
If you are unsuccessful please open a support portal ticket at the link below.

https://support.multitech.com/support/

-Best Regards

[Steve Kovarik]

Hi Jot4p

No, it not possible to know the power consumption by code, in the Conduit console or in a application.

-Best Regards

[Steve Kovarik]

Hi Nicola

The MultiConnect rCell is a cellular router and does have a serial interface
for PAD functionality (packet assembler/disassembler) which is most
commonly used to create a transparent serial connection over TCP/IP.
The rCell does not have any GPIO to interface to sensors.

The rCell has an industrial temperature operating range but would need to be
installed into a NEMA enclosure to be used outside.

Let me know any other questions you have.

-Best Regards

[Steve Kovarik]

Hi Jot4p

For the MTCDTIP we recommend a POE injector that is ‘802.3at Type 2’ rated.
Recommended Phihong model POE29U-1AT has a DC output voltage of 56V.

-Best Regards

[Steve Kovarik]

Hi Joe

Your configuration looks good.
With your laptop plugged into the Conduit can you try bringing up a command
prompt and issuing the command ipconfig /release then ipconfig /renew

[Steve Kovarik]

Hello

Redirection to HTTPS is not the cause.

It is because the device uses a self-signed website certificate,
your browser shows a certificate error or warning.
It is recommended to ignore the warning and add an exception
or add your device address to the trusted sites.
Another solution would be to upload a CA certificate as
described in the rCell Software Guide at the link below (p.67)

https://www.multitech.com/documents/publications/software-guides/s000720%20-%20mPower%20Edge%20Intelligence%20MTR%20Software%20Guide.pdf

[Steve Kovarik]

Hi Chad

It would be recommended to use the same model.
It is possible to manually edit the configuration (json) file without a Conduit,
I generally don’t recommend it because there is more room for error.

[Steve Kovarik]

Hi Chad

To remotely configure/enable the SMS command feature you would use deviceHQ
and download the Conduit configuration file, load it on local Conduit and
enable SMS feature (submit/save & restart) then pull the configuration file
and upload it to deviceHQ so you can schedule it to be installed into the
remote Conduit on next check-in.

Link to documentation below, starting on page 71.

http://www.multitech.net/developer/wp-content/uploads/2019/07/s000727-mPower-Edge-Intelligence-Conduit_AEP_software_guide.pdf

[Steve Kovarik]

Hi Nicolas

“Local Network settings” is an alternative that can be used and will work.
However that only allows for a single AppEUI and AppKEY to be configured.
When I configure multiple LoRa endpoints I like to use different AppEUI and
AppKEY for different endpoints. Configuring “local end-device credentials”
allows me to do that.

-Best Regards

[Steve Kovarik]

For an “Over The Air”(OTA) join, the LoRa endpoint will need a DevEUI, AppEUI and AppKEY. Program the LoRa end node DevEUI, AppKEY and AppEUI into
the Conduit_AEP “LoRaWAN” “Key Management” local end-device credential so the
LoRa endpoint can successfully “join” over the air. “LoRaWAN” “Network settings”
“Network Mode” should be configured for “Public LoRaWAN” and the
“Join delay” configured for 5 seconds.

-Best Regards

[Steve Kovarik]

Hi Bob

Having success using the LoRa Network Server on the Conduit proves you have
configured both the Elsys and Conduit correctly.
When using the Conduit as a Packet Forwarder you will need to configure the
Elsys and Semtech server with appropriate keys. If the Elsys fails OTAA
join are you able get any logging or error messages from the Semtech server?

If you enable ssh on the Conduit you can monitor “packets” being sent by doing a tcpdump on the WAN interface. If Ethernet is WAN then tcpdump -i eth0 -AUq port 20000

[Steve Kovarik]

Hi Robert

The GPS antenna will need a clear view of the sky to work.
If “TCP Server” is selected, then submitted and “save & restarted”
Then to get coordinates use a TCP Client like Putty and initiate a
raw TCP Socket to the IP Address of the Conduit on the defined port
(port 5445 is default)
If “TCP/UDP Client” is selected, then GPS coordinates will be sent to a
TCP/UDP Server (Remote Host) on the defined port over the configured WAN port.
The NMEA Configuration defines which NMEA sentences are sent.

[Steve Kovarik]

Aside from using Node-Red in the Conduit to view received LoRa packets
you could enable SSH on the Conduit and SSH into the Conduit with Putty
and use MQTT to view incoming packets as directed in the link below.

Conduit mLinux: LoRa Communication

[Steve Kovarik]

Hi William

You would acquire a cellular SIM card with SMS capabilities from the cellular carrier.
There will be a phone number associated with the SIM for SMS.
SMS can be used for wake-up or other specific deined SMS commands.
If configured for SMS commands, an example might be to send a SMS text
from your phone to the phone number of the SIM installed in the Conduit
with the body of the message being #reboot to reboot the Conduit.

Hope that helps.

[Steve Kovarik]

Hi Jot4p

For MultiTech’s IP67 Base Stations we recommend a POE injector that is 802.3at Type2 compliant.
It appears that the Tycon Power 12v-48v DC- DC Converter and PoE Injector
model TP-DCDC-1248 will work.

-Best Regards

[Steve Kovarik]

Hi Amir

Yes, that will allow you to make API calls into deviceHQ from your server.

-Best Regards

[Steve Kovarik]

Hi Ben

Both the mDot and Server need to be configured for it to work.
You would first configure the mDot with appEUI (at+ni) and appKey (at+nk)
to successfully “join” the LoRa Network Server on the Conduit.
You would also need to configure the Conduit with the DevEUI, appEUI and appKey so the Conduit will accept mDot join.
Next have the mDot perform a join (at+join).
After successfully joined you can send data packets.

Getting Started with LoRa Conduit AEP (LoRa Configuration)

[Steve Kovarik]

Hello Amir

MultiTech provides DeviceHQ as a free cloud based device management service
for our networking devices.
DeviceHQ is hosted on AWS and we strive for 99.999% uptime.
At this time there is not an enterprise version of deviceHQ available with
a SLA.
We feel deviceHQ is the best choice for remotely managing MultiTech’s networking devices.

-Best Regards

[Steve Kovarik]

If you log into the device and go to ‘administration’ then ‘firmware upgrade’
uncheck (disable) signed firmware validation” then ‘submit’ and ‘save & restart’
Conduit_AEP firmware version 1.6.4 is available at the link below.

Downloads

download it, extract the file then log into the Conduit and go to ‘administration’ then ‘firmware upgrade’ and perform the downgrade.

-Best Regards

[Steve Kovarik]

Hello Salvatore

STEP files are provided through our Support Portal.
Please open a ticket and request the STEP file at the following link.

https://support.multitech.com/support/login.html

-Best Regards

[Steve Kovarik]

Mark

For a successful packet data connection you would need to program the APN
associated with the SIM card into the modem with the command at+cgdcont=1,”IP”,”yourAPN”

Then in Linux the dial number should be *99***1#

[Author]

Posts