[Steve Kovarik]

Happy New Year Sebastian

I have been successful upgrading mLinux firmware using the ‘detailed steps’ outlined at this link.

Flashing mLinux Firmware

You can use the ‘mlinux-base-image-mtcdt-20200612181315.rootfs.jffs2’ file and ‘uImage–4.9.87-r11.2-mtcdt-20200612181315.bin’ file at link http://www.multitech.net/mlinux/images/mtcdt/5.2.7/

MTCDT and MTCDTIP do use the same firmware.

-Best Regards

[Steve Kovarik]

Hi Tony
If the device is not properly booting-up you can try recovering it by holding in the ‘reset’ switch for 31 seconds to factory default the device.
If that doesn’t help then I recommend you ‘register’ and open a ticket on our support portal (link below) for additional instructions to recover the device.
https://support.multitech.com/support/login.html

-Best Regards

[Steve Kovarik]

Can you make any configuration changes in the Conduit GUI that are successfully applied after a “Save and Apply”?
Next step is to factory default the device then manually reconfigure.
I may also recommend to reload device firmware.

-Best Regards

[Steve Kovarik]

Hi Larry

I can offer this. https://github.com/trong63/python_mqtt_sample

[Steve Kovarik]

Hi Jon

Thanks for the link to US govt standards published in NIST 800-63-3.
In the mPower firmware (formally AEP) under ‘Administration’ and ‘User Accounts’ you have the ability to change the password complexity rules.
Configuring Complexity Mode for ‘Credit’ allows you to define a minimum number of complexity classes. Hope that helps.

-Best Regards

[Steve Kovarik]

Hi Rafeal

We would recommend that you first upgrade the MTCAP-L4E1 to the latest firmware version 5.3.0 then factory default the device by holding in the reset button for 10 seconds then reconfigure.
The MTCAP 5.2.0 firmware van be found at the link http://www.multitech.net/developer/downloads/

If the problem persists open a support ticket at https://support.multitech.com/support/dashboard.html

-Best Regards

[Steve Kovarik]

Hi Larry

You may want to open a support ticket on this if you have not resolved it yet.
Do you have the UDK and ribbon cable as shown at the link below to allow view/changing the MTDOT-BOX configuration?

Configuration Mode

This is likely a simple configuration mismatch.

-Best Regards

[Steve Kovarik]

Hi Ajay

My personal preference is to use PPP, I guess old habits are hard to break. With PPP you’ll usually enter the SIM APN and verify the dial number.
Whichever works best for you.

-Best Regards

[Steve Kovarik]

Hi Ajay

PPP and WWAN are two methods of accomplishing the same thing. PPP has been reliably supported in this device for quite some time. WWAN is a newer option that tends to provide faster data throughputs than the legacy PPP option.

-Best Regards

[Steve Kovarik]

Hi Christophe

Verify both Conduit Gateways ‘LoRa Network Server’ settings match as well as the Adeunis (DevEUI,AppEUI, AppKEY) credentials in the Conduit.
Enable logging in the Conduit LoRa Network Server to view “Join” requests.

http://www.multitech.net/developer/wp-content/uploads/downloads/2018/09/LoRaWANTroubleShootingGuide-09202018.pdf

-Best Regards

[Steve Kovarik]

Hello Christophe

That should work, assuming that both Conduit Gateways are configured the same.
Has your OTAA devices ever successfully ‘Joined’ the other Gateway?
If not, we should check that the Conduit Gateways LoRaWAN configurations are the same.

-Best Regards

[Steve Kovarik]

Hi Perico

Node-Red will take an additional 5 minutes to load after a reboot or power-up and is not accessible during that time.
For Node-Red access
If you configured Ethernet as WAN, go to “Administration” and “Access Configuration” and for Node-Red verify both “via LAN” and “via WAN” are enabled.
“Submit” at the bottom of the screen then “Save & Restart”
After the Conduit is fully booted, wait an additional 5 minutes then try to access Node-Red.

-Best Regards

[Steve Kovarik]

Hi Roger

For Node-Red access
If you configured Ethernet as WAN, go to “Administration” and “Access Configuration” and for Node-Red verify both “via LAN” and “via WAN” are enabled.
“Submit” at the bottom of the screen then “Save & Restart”

For ongoing Technical Support please register and open a case at the url below.
https://support.multitech.com/support/login.html

-Best Regards

[Steve Kovarik]

Hi Roger

What (TCP/IP) Protocol will your PC use to accept a connection from the Gateway to visualize data?

In the Conduit Gateway you can use Node-Red as a tool to create a flow to backhaul valid LoRa packets to server.

Select “Apps” and verify Node-Red is enabled.
I prefer to “Launch Node-Red” in another browser tab. Log-in to Node-Red.
Node-Red basics can be found at the link below.

Conduit mPower: LoRa Communication and Node-RED

-Best Regards

[Steve Kovarik]

Hi Zwang

What version of firmware is your 246AEP running?
This was a bug in an earlier firmware release that doesn’t affect the device operation,
but is recommended you upgrade the MTCDT-246A to the latest version.

-Best Regards

[Steve Kovarik]

Hi Roger

No, please do not add a device in device if doing OTA Join.
After your LoRa sensor successfully “Join” the Conduit, then it will automatically show-up in Devices.
After valid sensor packets arrive at the Conduit, we address how to show the data of the sensors.

-Best Regards

[Steve Kovarik]

Hi Roger

In your LoRaWAN configuration configure for “Network Server”, “Public LoRaWAN”, Join delay=5 sec.
To add your sensors to the Conduit as a LoRa Network Server
Select “Key Management” and for Local End-Device Credentials select “Add New”.
You’ll need the DevEUI, AppEUI and AppKEY of the sensor to add a local end-device.
Once configured, have the sensor perform a “Join” and refresh the “Packets” screen to verify successful join and uplink packets.

-Best Regards

[Steve Kovarik]

Hi Roger

These are two different LoRa Network architectures.
There can only be a single LoRa Network Server. Trying to run LoRa Network Server on the Conduit and trying to register to TTN (Public LoRa Network provider) is a direct conflict.
If you want to use TTN, the Conduit would need to be configured as a Packet Forwarder to the LoRa Network Server (TTN).
If you want to use the LoRa Network Server in the Conduit, TTN is not needed.

[Steve Kovarik]

Hi Noel

I can confirm that, that ‘gsm’ is the correct option file for the LAT1 4G LTE CAT3 Modem.

-Best Regards

[Steve Kovarik]

Hello

The Conduit Gateway is capable.
I would recommend that you register and open a support portal case at the link below and ask the question.
https://support.multitech.com/support/login.html

-Best Regards

[Steve Kovarik]

Hi

I would recommend that you register and open a support ticket at the url below for best assistance.
https://support.multitech.com/support/login.html

-Best Regards

[Steve Kovarik]

Hi LoraAAU

For ongoing Technical Support please register and open a support ticket at the link below.
The Support Portal is better platform for ongoing troubleshooting and information exchange.
https://support.multitech.com/support/login.html

-Best Regards

[Steve Kovarik]

Hi Rafael

End node session information is saved in the MTCAP every hour.
If power is pulled from the device prior to the Conduit saving session information, it is lost.
If you were to first gracefully ‘Save & Restart’ or ‘restart device’ or ‘save changes’ from the Conduit GUI then session information is saved and will persist through pulling the power.
So for your scenario, that was expected behavior.
Hope that helps.

-Best Regards

[Steve Kovarik]

Hi
Assuming that you want to interface the IP67 device as a DHCP Client to an Ethernet Network (as the DHCP Server) that provides Internet access.

To accomplish that you should go to “Setup” and “Network Interfaces” and configure etho as “WAN” with mode set to “DHCP Client” then submit & ‘save & restart’.
Also make sure that in “Administration” and “Access Configuration” that you enable HTTPS via WAN (on port 443) [submit then ‘save & restart’] or you can lock yourself out.

Once that is all configured and working how will you determine the IP address assigned to the IP67 Gateway from the DHCP Server?
Are you able to access the DHCP Server (Router) and query for DHCP Client addresses?

-Best Regards

[Steve Kovarik]

Hi Ajay

With radio reboot enabled, the keep alive feature will stop PPP, reboot the radio then re-start PPP if the ICMP/TCP keep alive check fails in the configured time interval. In the vast majority of installations using keep alive with radio reboot disabled is adequate to recover the link.
The cautionary note is for configuring too short of an interval and with radio reboot enabled could incur frequent registration and connection attempts.

[Steve Kovarik]

Hi Jerome

We would like you to register and open a Support Portal Case at the link below.

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

-Best Regards

[Steve Kovarik]

Hi Eric

There is not an option in the GUI to enable/disable roaming.
Also, I looked through the AT Command guide for the LAT1 modem and didn’t find a command to disable roaming.

-Best Regards

[Steve Kovarik]

With the latest firmware ssh in with username/password.
I sudo -s and re-enter the password.

Use the command mts-io-sysfs show uuid

[Steve Kovarik]

Hello

Please verify that you can successfully ping a host name like http://www.google.com
from the Conduit. If that works but still can not check-in to deviceHQ via
Ethernet, we find the most common reason is TCP/UDP port 5798 is blocked on
your network for outbound access. Please check with the network administrator
that TCP/UDP port 5798 is not firewalled for outbound access.

-Best Regards

[Steve Kovarik]

Hi William

Sorry, I looked, but was not able to find Conduit default configuration documented.
Are you looking for anything specific?

[Author]

Posts