Home > Best Practices

Getting Started

The MultiConnect® ConduitTM platform consists of programmable hardware and software components that can be configured to your unique IoT application.  As such, there are many ways to use the Conduit platform which can cause confusion for both experienced and inexperienced users.  This best practices session will focus on the very basics of getting started with either an mLinux or AEP Conduit for use in a LoRa® proof of concept:  what products you’ll need to get up and running and how to ensure your Conduits and mDots can communicate with each other by using the latest firmware.  We finish this session with links on how to get started with your Conduit.  

If you want to skip steps or find detailed information on other aspects of the Conduit platform, please visit the MultiTech developer site at www.multitech.net.  Additionally, here are two specific links to getting started with MultiConnect Conduits:


Conduit Platform Pre-requisites:

Required Products
The following are the minimum products needed to create a proof of concept application using MultiTech’s Conduit platform:  1 Conduit, 1 MTAC LORA mCard, 1 LoRA antenna, 1 mDot, 1 Developer Kit

Description

  Order Part Number

Qty

  Notes

MultiConnect mLinux Conduit

 

 

Choose either the mLinux or AEP development environment; and either a radio or no radio Conduit, according to your needs.

  H5 Radio

  MTCDT-H5-210L-US-EU-GB

1

  No Radio (Ethernet only backhaul)

  MTCDT-210L-US-EU-GB

1

MultiConnect AEP Conduit

  AEP is the only Conduit that   works with DeviceHQ and Node-   RED

 

  H5 Radio

  MTCDT-H5-210A-US-EU-GB

1

  No Radio (Ethernet only backhaul)

  MTCDT-210A-US-EU-GB

1

MTAC-LORA Accessory Card

 

 

Choose either 868MHz (EU) or 915MHz according to your location needs.  Note:  mCard frequency needs to match mDot frequency

  EU Market

MTAC-LORA-868

1

  North American Market

MTAC-LORA-915

1

LoRa Antenna

AN868-915A-1HRA

1

 

MultiConnect mDot (Programmable)

 

 

We have listed the programmable mDot part numbers as they are best for PoC, Pilots or development efforts. Note:  mDot frequency needs to match mCard frequency

  EU Market

MTDOT-868-X1P-SMA-1

1

  North American Market

MTDOT-915-X1P-SMA-1

1

1 Developer Kit

 

 

Choose only one of the developer kits according to your needs.

MultiConnect mDot Developer Kit: 

MTUDK2-ST-MDOT

1

Micro mDot Developer Kit

MTMDK-ST-MDOT (not available until Q4 2015)

1

 

Firmware Compatibility
It is imperative that your Conduits and mDots are running the latest firmware/software!  At the very least, you need to ensure that both products are running compatible firmware.  The easiest way to ensure compatibility is to upgrade both products to the latest firmware.  This facilitates the easiest path to getting your units up and running and also saves a lot of time when requesting support from MultiTech.
 

LoRa Compatibility Requires These Versions or Greater:
mDot AT Command Firmware 0.1.2
libmDot 0.0.7
Conduit AEP  1.0.33
Conduit mLinux 3.1.0 with LoRa Network Server upgraded to 0.0.7


Here are links on how to upgrade firmware:

mLinux:  www.multitech.net/developer/software/mlinux/using-mlinux/flashing-mlinux-firmware-for-conduit

AEP:  www.multitech.net/developer/software/aep/upgrading-the-aep-firmware

Now that you have the right products ordered and have ensured they have the correct firmware versions for communication, you can get started using your equipment.  There are slight variations on using the mLinux or AEP versions of the Conduit for use in a LoRa application and these links will take you to the next steps:


Getting started with mLinux Conduit:
www.multitech.net/developer/software/mlinux/getting-started-with-conduit-mlinux

Getting started with AEP Conduit:  
www.multitech.net/developer/software/aep/getting-started-aep