[Darrik Spaude]

The image is behind OneDrive, so this site isn’t able to display it. I gave Jason the link to the image.

[Darrik Spaude]

Testing images

[Darrik Spaude]

Hi,

Which model is it?

Which firmware is programmed into the IP67 gateway (AEP/mPower or mLinux) and which version?

Which LED is red?

See page 17-18 in this guide if it is the MTCDTIP-x-26x family: https://www.multitech.com/documents/publications/manuals/S000665.pdf

If L1 is red, it CAN mean that it has 1 bar of signal strength on the cellular radio (if using AEP/mPower) but not connected (radio CD is off) or 3 bars if L2 is red AND green.

[Darrik Spaude]

I see that you have a support case already, so let’s keep working through that case.

[Darrik Spaude]

Are you able to stop the reboot? There is a point right away in U-boot where if you press a key it will stop the boot and stay at the U-boot> prompt.

[Darrik Spaude]

Hi Liam,

Are you asking this question because you already have the MTXDOT-AU1-A01-100 and just want to add the U.FL? From what I can see in the design, the only difference is the U.FL. There are no other components missing between A01 and A00.

[Darrik Spaude]

Keep in mind that if you downgrade a Conduit model that has the newer radios such as L4E1, then the cellular connection won’t work in the older version of the firmware. I saw that you had a request in our Support Portal in regard to this for the L4E1, so a downgrade is not recommended.

[Darrik Spaude]

If trying to log in to a new device that has mPower (formerly called AEP) 5.0 or newer installed, then you need to go through the web interface to “commission” the device first before you can log in via USB debug port. Also, SSH is disabled by default on mPower 5.0, so that would also need to be enabled if you want to try to log in via SSH.

[Darrik Spaude]

Hi,

Please create a support case at https://support.multitech.com and include the serial number of the Conduit. The Actility firmware locks down the security of the Conduit and recovery back to the stock MultiTech firmware will likely require you to open the chassis which will void the warranty. However, it is up to you to do that and we can provide instructions on how to recover unless you would prefer to send it in for repair. Either way, please create a support case.

Best Regards,
Darrik

[Darrik Spaude]

Hi,

The process for factory default is the following:
—-
For Factory Default of Conduit (MTCDT), Conduit IP67 (MTCDTIP), Conduit AP (MTCAP), rCell (MTR), or OCG (MTCDP or MT100EOCG):

1. Power on device
2. Wait for ST or STATUS LED to start flashing with a heartbeat rhythm
3. Press in and hold in the RST or RESET button for over 30 seconds
4. Release the RST or RESET button
5. Wait for device to reboot (ST or STATUS LED will go on solid after Linux shutdown process and then will start flashing again after it has finished powering up)
—-

If the Conduit had mPower (AEP) 5.0 or newer installed, then by default you won’t be able to use SSH and you won’t be able to log in via USB debug port. For mPower 5.0 and newer you need to use a web browser (192.168.2.1 by default) to “commission” the device (meaning you will configure the username/password). You cannot log into the device until you have gone through the commissioning mode.

If the web display seems to get stuck, then try doing a refresh of the login page ( by default, https://192.168.2.1 ).

Let us know if that helps,
Darrik

[Darrik Spaude]

Hi Chris,

It is a statement of caution. The Conduit’s/rCell’s Ethernet interface is best used behind a firewall and not placed on the public Internet. On the cellular interface (if enabled), the cellular carrier usually offers a private and a public option. Again, ideally the cellular interface should be on a private network. If the cellular interface is put on a public network, there could be data usage consequences due to infiltration/intrusion attempts.

Let us know if that helps explain it,
Darrik

[Darrik Spaude]

Hi Pierre,

I saw this answer circling around, but hasn’t been posted out to you yet. I don’t know if they are still thinking about an answer, but thought you would like to see this sooner rather than later:
———
A reasonable virtual machine provisioning for DeviceHQ might look like:

ram: 4GB
hd: 100GB
cpu: 2 cores

The vm image is provided with OS included (it uses ubuntu 18.04).

[Darrik Spaude]

Hi Pierre,

There is such a thing, but you’ll need to contact MultiTech’s sales group for more information.

https://www.multitech.com/about-us/global-locations

[Darrik Spaude]

Hi,

You could try accessing the Conduit via SSH and try the following instructions:

1) To see why the packet forwarder is not getting started, look at output of forwarder when run from the command line:

# /etc/init.d/lora-network-server stop
# cd /var/run/lora/1/
# ./lora_pkt_fwd

See troubleshooting guide in Downloads on this page.

Troubleshooting LoRa Communication

2) Try to manually reload the FPGA firmware. If this is not functioning as shown below, then there is a hardware issue:

# mts-io-sysfs store lora/creset 0
# mts-io-sysfs show lora/cdone
0 <<-- Expected output # mts-io-sysfs store lora/creset 1 # mts-io-sysfs show lora/cdone 1 <<-- Expected output

[Darrik Spaude]

Hi Frank,

Yes, it mostly has to do with the version of AEP. Since you have AEP 1.3.2, then you should upgrade to 1.4.3 first, then to 1.6.4, and then you may upgrade to mPower 5.0. Back up your configuration first just in case. Maybe even back up your config after each upgrade. The instructions on the following page say you need 1.4.4, but good luck finding that. AEP 1.4.3 was the version that was released for your Conduit (MTCDT). AEP 1.4.4 was a bug fix release for the Conduit IP67 (MTCDTIP) and other than that it is identical to AEP 1.4.3 (I’ll make a documentation ticket to have the changelog corrected).

mPower Firmware Changelog

If you run into trouble, then create a support case on our web site ( https://support.multitech.com ). There IS a way to upgrade straight to mPower 5, but it involves completely erasing the NAND flash (and thus all configuration changes).

Best Regards,
Darrik

[Darrik Spaude]

As far as I can tell by looking at the schematics, there is no way for the processor to read voltage or power consumption information from the POE circuit.

[Darrik Spaude]

Hi William,

No, for the LVW2 model you would need to use a Verizon SIM card. The radio firmware is specific to Verizon.

The MTCDT-L4N1-247A would work with either AT&T or Verizon via software config.

https://www.multitech.com/models/94557593LF

https://www.multitech.com/models/94557594LF (with LoRa mCard)

Best Regards,
Darrik

[Darrik Spaude]

Yes, the MTR (rCell) would be a good choice.

[Darrik Spaude]

Hi Mike,

“I was going to contact the company but I see it is $360 !!!!”

The fee you mention is likely from the FaxFinder.net support site and that is only for FaxFinder (fax server) customers. If you don’t have a question about FaxFinder, then continue to the login for MultiTech’s Support Portal. MultiTech’s support is free. FaxFinder’s support is no longer free.

[Darrik Spaude]

Hi John,

At this time the functionality is not installed and will probably not be enhanced until some time next year.

[Darrik Spaude]

This is currently a known problem. We don’t have a resolution for it yet.

[Darrik Spaude]

I’m assuming the resolution in the support case worked as you stated it had and the device is no longer scrap, correct?

[Darrik Spaude]

The term “standard” changes from generation to generation, so just to be specific, the Conduit uses the Mini-SIM format:

https://en.wikipedia.org/wiki/Subscriber_identity_module#Formats

[Darrik Spaude]

Hi Chad,

One of the engineers had this suggestion:

Simplest solution would be to use a series Schottky diode to reduce the input voltage. Most Schottky diodes have at least a 250 mV drop across them.

LP5907 is 14 uA quiescent current and drop out is ~50 mV at 100 mA draw.
MIC5501 is 38 uA quiescent current and drop out is ~80 mV at 150 mA draw.

[Darrik Spaude]

Hi Johann,

Create a support case at https://support.multitech.com and request instructions on how to switch from mLinux to AEP and we’ll get you those instructions and binaries.

Thanks,
Darrik

[Darrik Spaude]

Hi Chad,

There isn’t a regulator on the xDot, so your input voltage is routed to all components. Several of the components can accept higher voltages, but some do not. We recommend that you try to add a regulator that can supply 3.3 V. The batteries are going to provide lower voltages over time, so the regulator should also boost the voltage back to 3.3 V. Above 3.6 V the product could be unreliable.

That said, for testing/development, 3.62 V is right on the edge of recommended and would probably work okay. Energizer shows that the lithium AA typically outputs 1.7 V max (but could peak at 1.8 V) while nominal is 1.5 V. Keep in mind that the voltage could be higher or lower depending on the battery. For long term/production application, we still recommend a regulator.

Hope that helps,
Darrik

[Darrik Spaude]

Hi Ajay,

Would you create a support case at our Support Portal (same login as here)? We can then include other people including our sales and product management groups who could possibly set up a custom SKU for you or include the manufacturing group for more information.

https://support.multitech.com/

Thanks,
Darrik

[Darrik Spaude]

Hi Scott,

The 3.4.5 firmware for the 2G/3G models is here:
https://webfiles.multitech.com/wireless/mtr/mtr-2g-3g_v3.4.5_upgrade.zip

I don’t know which carrier your model uses (N2=Sprint, N3=Verizon, N16=Aeris), but it’s the same firmware for all of them.

http://www.multitech.com/brands/multiconnect-rcell-100-series

Best Regards,
Darrik

[Darrik Spaude]

From what I heard, the xDot developer guide should be available soon if not by tomorrow morning:

xDot

[Darrik Spaude]

At what voltage are the mDots being powered?

[Author]

Posts