[Steve Kovarik]

Hi Mark

Aside from providing power and ground, please ground any low active inputs
RTS (Pin33) and DTR (pin40).
Also issue AT Commands to the modem at 115200bps, 8, none, 1

-Best Regards

[Steve Kovarik]

Load the XR driver first, then plug in the MTUDK2-ST-MTDOT developer board.

Click this link to download and install the appropriate Windows USB driver for EXAR xr21b1411 on the Exar website at: https://www.exar.com/content/document.ashx?id=1596

[Steve Kovarik]

Let me know the case number.
Thanks

[Steve Kovarik]

Which Windows OS?
Did you load drivers?
Does the mDot successfully enumerate the two ports (USB Serial device and XR USB Port)
It should also show up as a drive on windows.
For example… MULTITECH(D:)

You should open a support ticket.
https://support.multitech.com/support/login.html

[Steve Kovarik]

Hi Brandberg

If we consider this a possible physical SIM slot issue the next step would
be to open a support portal case at the link below. We would likely assign
a RMA and need the whole device shipped back for warranty service.
https://support.multitech.com/support/login.html

[Steve Kovarik]

Hi Brandberg

The log shows that the SIM card is physically detected (#SIMDET:2,1)
but the MTCDTIP can not read the SIM. The installation guide correctly
states “cut corner to the left and the SIM contacts facing towards the USB port”
Can you confirm that you have tried that SIM card orientation in the MTCDTIP?

[Steve Kovarik]

Hi
Are you using the mDot in a MultiTech MTUDK2-ST-MDOT Developer board?
Teraterm should be configured for 115200, 8, none, 1 with hardware flow
control disabled.
If using in a MTUDK2-ST-MDOT with a physical DB9 serial port, you are
required to issue AT Commands through the DB9 serial interface.
If you have a MTUDK2-ST-MDOT with just the micro USB interface, the board
should enumerate two virtual serial ports.(USB Serial device and XR USB Port)
Use the “XR USB Port” to issue AT Commands to the mDot.

-Best Regards

[Steve Kovarik]

Hi Alex

From that we are to determine that the xDot successfully “Joined” the
network, and the Conduit received the (UpCnf) xDot uplink confirmed packet
requesting the ACK.
And in response the Conduit sent a (DnCnf) downlink (confirmed) ACK back to the xDot.

[Steve Kovarik]

Hi Alex

When looking at LoRaWAN/Packets on the AEP interface, what is the packet “Type” of the received packets from the xDot?

-Best Regards

[Steve Kovarik]

Hello Viv

Regarding the GPIO card.
All digital outputs have TVS protection (transient voltage suppression)up to 70 Volts peak for 10ms.
Digital inputs are optical-isolated (no TVS) with diode protection up to 70 Volts (for 10ms) peak pulse 50mA.
Analog input supports 0-5VDC direct to op-amp with no protection.
Opto Isolator Isolation voltage level is 3750 Vrms.
On the MTAC card, the EXT_IN_GND pin is fully isolated from all other grounds.
Clearance of the EXT_IN_GND on the MTAC-GPIO board is only 25 mils.
Because of the size, the MTAC-GPIO was not designed for high voltage isolation.
The ANALOG_IN_GND pin is connected to the Conduit GND through a ferrite bead.

[Steve Kovarik]

Hi Jessica

I can’t explain that. This may be more of a technical support issue.
Would you consider opening a support portal case on the device behavior.
https://support.multitech.com/support/login.html

[Steve Kovarik]

Hi Jessica

Do you know the firmware version? In MTCDT AEP firmware 1.7.3, it was identified that when the Ethernet cable was unplugged and plugged back in, the IP address would revert to the factory default setting (192.168.2.1) instead of the customer-defined IP address. This issue has been corrected
in firmware version 1.7.4
You could factory default the device and upgrade firmware to 1.7.4

-Best Regards

[Steve Kovarik]

Hello Danny

Yes, both the xDot and mDot were designed with the same functionality.
The xDot also works in peer-to-peer mode of operation.

-Best Regards

[Steve Kovarik]

In Conduit AEP configured as LoRa Network Server, to add OTA endpoints
select “LoRaWAN” tab, then “Key Management” tab and “Add New” for
local end device credentials.

To add ABP endpoints select “Devices” tab and “Add New” for End devices and Sessions.

[Steve Kovarik]

Hi Rick

19056321 shows version 2.0.16
I feel that the 20 series my have some settings that default differently then previous versions.
I may have you open a Support Portal case to discuss further.

-Best Regards

[Steve Kovarik]

Hi Rick

Sounds like you’re doing everything right.
After reverting a mDot to an older revision an AT command is not required to complete the software revision.
mDot serial number 19056321 shipped with firmware 2.0.16
mDot serial number 20121591 shipped with firmware 3.1.0

It is unclear why you can not communicate with the mDot in the developer board using AT Commands.
Are you able to successfully issue AT Commands to 19056321 in a developer board?

[Steve Kovarik]

Hi Rick

If the AT Command firmware is programmed onto the mDot, you would use
AT Commands to verify the version (ati) and also configure the mDot to join
a specific LoRa Network by programming the necessary parameters (AppEUI,
AppKEY,frequency sub-band, Public/Private Network mode, join delay, ect).

When using the MTUDK2-ST-CELL developer board first power the board with the
9VDC power supply then plug the micro USB to your Windows 10. You will need
to issue AT commands through the physical RS232 DB9 serial interface.
I suspect your Windows10 does not have native serial interface so you are
likely using a USB-to-Serial adapter…correct?
In Device Manager under “Ports” which port are you selecting in TeraTerm?
Be sure in TeraTerm Flow Control is se to None.

[Steve Kovarik]

Hi Rick

Can you try and recover the mDot by programming the latest version 3.1.0 and see what happens.

Downloads

[Steve Kovarik]

Hi Rick

Can you verify your developer board model (MTUDK2-ST-MDOT or MYTDK2-ST-CELL)
Is TeraTerm configured for 115200, 8, None, 1, Flow Control – None.
Is the mDot brand new (running AT Command firmware) or has it been programmed
before?
Does the mDot successfully enumerate as a drive on Windows 10.

-Best Regards

[Steve Kovarik]

Hello Fernando

You will need to enable “Remote Access” on the Conduit by selecting the
“Administration” tab, then “Access Configuration” and on the right side of
the screen under HTTPS enable (check checkbox) “Via WAN” then scroll to the
bottom and select “Submit” then “Save & Restart”.After the Conduit reboots
please verify that you can remotely access the Conduit web admin via the
public/dynamic IP address. If you can not access the web admin remotely,
it’s because the public/dynamic IP is firewalled for inbound access, meaning
that your SIM account is not provisioned for Remote Terminated data.

-Best Regards

[Steve Kovarik]

Hi Fernando

Multiple options were discussed based on how your SIM card was provisioned.
Are you asking about the deviceHQ option for cloud based management?

[Steve Kovarik]

Hi Fernando

US915 supports Spreading Factors SF7 through SF10.
The Spreading Factor is configured in the LoRa endpoint.
SF10 has a limitation of 11 Bytes payload, but provides longest range.
SF7, SF8, SF9 all provide larger payload. See Spreading Factor and Bandwidth
table at the link below.

Introduction to LoRa

-Best Regards

[Steve Kovarik]

Hello Fernando

This is most commonly accomplished by arranging with your SIM provider to have
a public/static IP address assigned to the SIM card then enabling remote access
on the Conduit AEP.

If the SIM provider can provide public/dynamic IP address the Conduit AEP
supports a DDNS (Dynamic DNS) feature that you would sign-up for https://dyn.com/
that can assign the Conduit AEP a host name that will resolve to the public
dynamic IP address.

Most commonly SIM cards are assigned private/dynamic IP addresses that are
firewalled and do not allow remote access to the Conduit AEP. In this case
MultiTech provides DeviceHQ which is a cloud based device management solution.
https://www.multitech.com/brands/devicehq

[Steve Kovarik]

Hello Jigar

For starters we can help you verify the modem is functioning properly.
I suggest that you open a Support Portal ticket at the following link
where we can help troubleshoot.

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

-Best Regards

[Steve Kovarik]

Hello Sleung

To subscribe to the local MQTT Broker the Conduit, the Conduit needs to be
configured as the “LoRa Network Server”.
When the Conduit Gateway is configured as a “Packet Forwarder” all packets
are forwarded to the LoRa Network Server (TTN) and Mosquitto can not be used
to view any LoRa packets traversing the Gateway nor is there any logging of
LoRa end-device packets.

-Best Regards

[Steve Kovarik]

Hi William

I see that you have an open Support Portal case on this same topic, so we will continue this dialog in the Support Poratal.

-Best Regards

[Steve Kovarik]

Hi William

I feel that once deployed and no customer access to web administration that
DeviceHQ would need to be used. When the Conduit “checks-in” it can upload
its current configuration file to DeviceHQ. You could download that
configuration file, load it into a Conduit you have, configure Wi-Fi as WAN
save the new config file, upload it to DeviceHQ for download to another Conduit.
I am not aware of a way to use Bluetooth for Conduit configuration.

-Best Regards

[Steve Kovarik]

Hi William

1) No, once “Wi-Fi as WAN” is enabled and configured, the Conduit connects to
the AP which disrupts the Wi-Fi “web administration” session so you can not
disable “Wi-Fi Access Point” mode or perform a “Save & Restart”.
2) No, that would forfeit our FCC certifications.

-Best Regards

[Steve Kovarik]

Hi William

1) No concurrent “Wi-Fi as WAN” and “Wi-Fi AP”
2) Yes, any browser can be used to access the Web Admin over Wi-Fi.

-Best Regards

[Steve Kovarik]

Hi William

In your commercialized deployment will all Conduits be identically configured?
Each Conduit will need to be touched, I feel that your options are;
1) log into the web administration and “restore” a full configuration file.
2) Configure Conduit for DeviceHQ, after successful check-in schedule configuration file download/installation.
3) Create AEP API script. Conduits ship with default IP 192.168.2.1
4) Contact MultiTech Sales for $$ quote to load configuration file at factory.

5) Yes, it is possible for your customer to log into the Conduit web
administration to enable and configure Wi-Fi parameters.

-Best Regards

[Author]

Posts