{"id":10632,"date":"2015-12-28T15:05:01","date_gmt":"2015-12-28T21:05:01","guid":{"rendered":"http:\/\/www.multitech.net\/developer\/?page_id=10632"},"modified":"2018-05-09T15:53:38","modified_gmt":"2018-05-09T20:53:38","slug":"configuration-mode","status":"publish","type":"page","link":"https:\/\/www.multitech.net\/developer\/software\/dot-box-and-evb-software\/configuration-mode\/","title":{"rendered":"Configuration Mode"},"content":{"rendered":"<p>The following\u00a0three images\u00a0below\u00a0and on the left\u00a0apply for connecting:<\/p>\n<ul>\n<li>the <strong>MTDOT-BOX<\/strong> to the <strong>MDK<\/strong> (model: MTMDK-ST-MDOT)<\/li>\n<li>the <strong>MTDOT-EVB\u00a0<\/strong> to the <strong>MDK<\/strong> (model: MTMDK-ST-MDOT)<\/li>\n<\/ul>\n<p><strong>For\u00a0UDK2 users (who received a note regarding the<br \/>\nprogramming cable):\u00a0<\/strong>Due to\u00a0supplier error\u00a0on some devices,<br \/>\nthe connection\u00a0is the opposite way for connecting (see second UDK2<br \/>\nimage on the right):<\/p>\n<ul>\n<li>the<strong> MTDOT-BOX <\/strong>to<strong>\u00a0<strong>UDK2 <\/strong><\/strong>(model: MTUDK2-ST-MDOT<strong><strong>)<\/strong><\/strong><\/li>\n<li>the\u00a0<strong>MTDOT-EVB <\/strong>to <strong>UDK2<\/strong> (model: MTUDK2-ST-MDOT)<\/li>\n<\/ul>\n<p>For these users, the red wire on the 8 position programming<br \/>\ncable\u00a0indicates pin position 8 (on both\u00a0the<strong> devi<\/strong><strong>ce<\/strong> and <strong>UDK2<\/strong>).<\/p>\n<p><img decoding=\"async\" alt=\"\" src=\"https:\/\/www.multitech.net\/developer\/wp-content\/uploads\/2018\/04\/Micro-UDK-Prog-Cable-Exploded.png\" width=\"600px\" height=\"419\" \/><\/p>\n<p><img loading=\"lazy\" decoding=\"async\" alt=\"\" src=\"https:\/\/www.multitech.net\/developer\/wp-content\/uploads\/2018\/04\/UDK-2.0-Prog-Cable-Exploded-How-to-Connect-Right-Wrong.png\" width=\"700\" height=\"250\" \/><\/p>\n<p>This picture (above) shows the correct UDK2 connection (left) versus the incorrect one (right). Refer to the note for UDK2 users near the top of this page.<\/p>\n<p><a href=\"https:\/\/www.multitech.net\/developer\/wp-content\/uploads\/2016\/02\/MTDOT-EVB-View-4-Prog-Cable-web.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-11506\" alt=\"MTDOT-EVB View 4 Prog Cable web\" src=\"https:\/\/www.multitech.net\/developer\/wp-content\/uploads\/2016\/02\/MTDOT-EVB-View-4-Prog-Cable-web.png\" width=\"491\" height=\"307\" srcset=\"https:\/\/www.multitech.net\/developer\/wp-content\/uploads\/2016\/02\/MTDOT-EVB-View-4-Prog-Cable-web.png 491w, https:\/\/www.multitech.net\/developer\/wp-content\/uploads\/2016\/02\/MTDOT-EVB-View-4-Prog-Cable-web-300x187.png 300w\" sizes=\"auto, (max-width: 491px) 100vw, 491px\" \/><\/a><\/p>\n<p style=\"text-align: left;\">If you want to configure or reprogram the device, you must order a <b>Micro Developer Kit (MDK)<\/b>, model: MTMDK-ST-MDOT, (pictured above) which is sold separately. (Alternatively, a UDK2 can also work.) For programming instructions and more details, visit the mbed.org site at:\u00a0 <a href=\"http:\/\/developer.mbed.org\/getting-started\/\">http:\/\/developer.mbed.org\/getting-started\/<\/a>\u00a0and <a href=\"https:\/\/developer.mbed.org\/platforms\/mdotevb\">https:\/\/developer.mbed.org\/platforms\/mdotevb<\/a><\/p>\n<p><b>Note:<\/b> If you do not want to configure the device, configure your gateway to match these device default network parameters:<\/p>\n<ul>\n<li><b>name:<\/b> MultiTech<\/li>\n<li><b>phrase:<\/b> MultiTech<\/li>\n<li><b>sub band: <\/b>1 (only applies to US\/915 MHz Frequency Band)<\/li>\n<li><strong>region: <\/strong>US915<\/li>\n<\/ul>\n<p>For Windows users only, you must install the device driver for the configuration port. From the host, use an application such as TeraTerm with a baud rate of 115,200. If the USB driver does not automatically install, do the following:<\/p>\n<ul>\n<li>Unplug the USB cable.<\/li>\n<li>Click this link to download and install the appropriate\u00a0Windows USB driver\u00a0for EXAR xr21b1411 on the <a href=\"https:\/\/www.exar.com\/\">Exar website\u00a0<\/a>at:\u00a0\u00a0 <a href=\"https:\/\/www.exar.com\/content\/document.ashx?id=1596\" target=\"_blank\">https:\/\/www.exar.com\/content\/document.ashx?id=1596<\/a><\/li>\n<li>Plug the USB cable back into the housing.<\/li>\n<li>From the host, access the EVB&#8217;s USB COM port.<\/li>\n<\/ul>\n<p>If you have the USB driver already installed, do the following for Configuration Mode:<\/p>\n<ol>\n<li>As shown above, connect the device to the <b>MDK<\/b> or <strong>UDK2<\/strong> using the 8-pin flat programming or ribbon cable (with its red stripe facing you). Note: the <strong>MDK<\/strong> reset button resets both the <strong>MDK<\/strong> and the connected device<strong>. <\/strong>But the <strong>UDK2<\/strong>reset button only resets the\u00a0<strong>UDK2 <\/strong>itself, not the connected device.<\/li>\n<li>Connect the <b>MDK or UDK2<\/b>\u00a0to a\u00a0<b>computer<\/b> (via its <b>USB connector<\/b>) after powering up the device. Note: The MTUDK2-ST-CELL requires an external power\u00a0supply (not powered\u00a0via USB).<\/li>\n<li>Using your <b>computer<\/b>, connect to the new TTY\/COM port at 115200 bps.<\/li>\n<li>Press <b>SW2<\/b> to select <b>Configuration<\/b> from the <strong>M<\/strong><b>ain Menu.<br \/>\n<\/b><\/p>\n<ul id=\"ul_qmb_cq5_45\">\n<li>A help screen displays how to connect.<\/li>\n<li>A second help screen displays a message\u00a0about connecting to a PC.<\/li>\n<li>A third help screen displays a message to connect to the new TTY\/COM port at 115200 bps.<\/li>\n<\/ul>\n<\/li>\n<li>Enter the AT command you wish to execute. To see information on the entire set of commands, enter <b>help<\/b> or <b><b><b>? <\/b><\/b><\/b>(without an AT prefix)<b><b><b>. <\/b><\/b><\/b>Below are some commonly-used AT commands.<\/li>\n<\/ol>\n<table class=\"alignleft\" style=\"height: 36px; width: 495px; padding-left: 60px;\" border=\"0\">\n<tbody>\n<tr>\n<td><strong>AT+NI=1,&lt;name&gt;<\/strong><\/td>\n<td>Change the Network Name to match your gateway<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<table style=\"height: 29px; width: 495px;\" border=\"0\">\n<tbody>\n<tr>\n<td><strong><b>AT+NK=1,&lt;phrase&gt;<\/b><\/strong><\/td>\n<td>Change the Network Passphrase to match your gateway<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<table style=\"height: 12px; width: 495px;\" border=\"0\">\n<tbody>\n<tr>\n<td><strong>AT+freq=&lt;region&gt;\u00a0<\/strong><\/td>\n<td><strong><strong><b><b><\/b><\/b><\/strong><\/strong>Change the Region to match your gateway (ex: AT+freq=US915) &#8211; available regions include:US915, AS923, AS923-JAPAN, AU915, KR920, EU868, or IN865<\/td>\n<\/tr>\n<tr>\n<td><strong><b><b>AT+FSB=&lt;sub band&gt;<\/b><\/b><\/strong><\/td>\n<td><strong><strong><b><b><\/b><\/b><\/strong><\/strong>Change the Frequency Sub Band to match your gateway (only applies to US\/915 mHz Frequency Band )<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<table style=\"height: 1px; width: 495px; padding-left: 30px;\" border=\"0\">\n<tbody>\n<tr>\n<td><strong><b><b>AT&amp;W<\/b><\/b><\/strong><\/td>\n<td>Save the configuration changes<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>6.\u00a0\u00a0\u00a0\u00a0 Hold <b>SW1<\/b> or use <b>AT+EXIT <\/b>to return to the <strong>Main Menu<\/strong>.<\/p>\n<p><strong>AT Commands<\/strong><\/p>\n<p>All commands have a help message that describes the command and how to use it. Enter <strong>help<\/strong> or <strong>? (<\/strong>without an AT prefix<strong>)<\/strong>\u00a0to display information for the entire set of commands. The <strong>+EXIT\u00a0<\/strong>command\u00a0closes <strong>Configuration Mode<\/strong> and goes back to the main menu.<\/p>\n<p><strong>Survey Modes Only<\/strong><\/p>\n<p>The <strong>+MINSIZE<\/strong> and <strong>+MAXSIZE<\/strong> commands restrict the <strong>Survey Sweep<\/strong>\u00a0to a subset of the available data rates based on the specified minimum and maximum payload sizes.<\/p>\n<table border=\"0\">\n<tbody>\n<tr>\n<td><strong>AT+MINSIZE<\/strong><\/td>\n<td>Set\/View the minimum payload size (11 &#8211; 242, Default: 11)<\/td>\n<\/tr>\n<tr>\n<td><strong>AT+MAXSIZE<\/strong><\/td>\n<td>Set\/View the maximum payload size (11 &#8211; 242, Default: 242)<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>The <strong>+MINPWR<\/strong> and <strong>+MAXPWR<\/strong> commands restrict the <strong>Survey Sweep<\/strong> to a subset of the available power levels.<\/p>\n<table border=\"0\">\n<tbody>\n<tr>\n<td><strong>AT+MINPWR<\/strong><\/td>\n<td>Set\/View the minimum transmit power (2 &#8211; 20, Default: 2)<\/td>\n<\/tr>\n<tr>\n<td><strong>AT+MAXPWR<\/strong><\/td>\n<td>Set\/View the maximum transmit power (2 &#8211; 20, Default: 20)<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>The <strong>+DATA<\/strong> command enables or disables transmission of data packets during survey operations. This is relevant with the EU\/868 MHz frequency band where the duty cycle limitations are more restrictive. Users may not want to use 50% of their potential transmissions to send data to the gateway after a successful survey.<\/p>\n<table border=\"0\">\n<tbody>\n<tr>\n<td><strong>AT+DATA<\/strong><\/td>\n<td>\u00a0Enable transmission of data packet after successful survey (0: off , 1: on, Default: off )<\/td>\n<\/tr>\n<tr>\n<td><strong>AT+GSDF<\/strong><\/td>\n<td>Get survey data file contents<\/td>\n<\/tr>\n<tr>\n<td><strong>AT+DSDF<\/strong><\/td>\n<td>\u00a0Delete survey data file<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><strong>LoRa Demo Mode Only<\/strong><\/p>\n<table border=\"0\">\n<tbody>\n<tr>\n<td><strong>AT+TXDR<\/strong><\/td>\n<td>\u00a0Set\/View the transmit data rate (7 &#8211; 10 US, 7 &#8211; 12 EU, Default: 7)<\/td>\n<\/tr>\n<tr>\n<td><strong>AT+TXP<\/strong><\/td>\n<td>Set\/View the transmit power (2 &#8211; 20, Default: 11)<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><strong>Survey and LoRa Demo Modes<\/strong><\/p>\n<table border=\"0\">\n<tbody>\n<tr>\n<td><strong>AT<\/strong><\/td>\n<td>\u00a0Attention<\/td>\n<\/tr>\n<tr>\n<td><strong>ATI<\/strong><\/td>\n<td>Show firmware version information<\/td>\n<\/tr>\n<tr>\n<td><strong>AT+DI<\/strong><\/td>\n<td>View the device ID<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>The <strong>+FSB<\/strong> command is only applicable for the US\/915 mHz frequency band. If the device is operating in public network mode, set the <strong>+FSB<\/strong> command to <strong>0<\/strong> so the device hops all 64 channels. If the device is operating in private network mode, set the <strong>+FSB<\/strong> command to 1 &#8211; 8 and match the gateway configuration. If the frequency sub band doesn&#8217;t match the gateway&#8217;s configuration, the gateway does not receive packets from the device.<\/p>\n<table border=\"0\">\n<tbody>\n<tr>\n<td><strong>AT+FSB<\/strong><\/td>\n<td>Set\/View the frequency sub band (0, 1 &#8211; 8, Default: 1)<\/td>\n<\/tr>\n<tr>\n<td><strong>AT+FREQ<\/strong><\/td>\n<td>View the frequency band (FB 915 or FB 868)<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>The <strong>+NI<\/strong> and <strong>+NK<\/strong> commands each allow the credential to be configured as a string or in hexadecimal. Enter hexadecimal <strong>network ID<\/strong> and <strong>network key<\/strong> as shown below.<\/p>\n<table border=\"0\">\n<tbody>\n<tr>\n<td><strong>AT+NI=0,&lt;hex ID&gt;<\/strong><\/td>\n<td>&lt;hex ID&gt; = 8 bytes<\/td>\n<\/tr>\n<tr>\n<td><strong>AT+NK=0,&lt;hex key&gt;<\/strong><\/td>\n<td>&lt;hex key&gt; = 16 bytes<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Enter\u00a0string <strong>network name<\/strong> and <strong>network passphrase<\/strong> as shown below.<\/p>\n<table border=\"0\">\n<tbody>\n<tr>\n<td><strong>AT+NI=1,&lt;name string&gt;<\/strong><\/td>\n<td>&lt;name string&gt; = 8-128 characters (default = MultiTech)<\/td>\n<\/tr>\n<tr>\n<td><strong>AT+NK=1,&lt;passphrase string&gt;<\/strong><\/td>\n<td>=\u00a0\u00a08-128 characters (default = MultiTech)<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>The <strong>+NJM<\/strong> command controls how the device joins the network. In <strong>Manual<\/strong> mode, there is no join request sent and the device must be manually configured with a <strong>network address (+NA<\/strong>), a <strong>network session key<\/strong> (<strong>+NSK<\/strong>), and a <strong>data session key<\/strong> (<strong>+DSK<\/strong>). The device must be provisioned with the network server as well. In <strong>OTA<\/strong> mode, the device only needs to be configured with a<strong> network name<\/strong> (<strong>+NI<\/strong>=1,name) and <strong>network passphrase<\/strong> (+<strong>NK<\/strong>=1,passphrase). The network session key, data session key, and network address are all automatically configured.<\/p>\n<table border=\"0\">\n<tbody>\n<tr>\n<td><strong>AT+NJM<\/strong><\/td>\n<td>Set\/View the network join mode<\/td>\n<td>0: MANUAL<\/td>\n<td>1: OTA<\/td>\n<td>\u00a0Default: OTA<\/td>\n<\/tr>\n<tr>\n<td><strong>AT+NSK<\/strong><\/td>\n<td>Set\/View the network session key<\/td>\n<td>hex 16 bytes<\/td>\n<td><\/td>\n<td><\/td>\n<\/tr>\n<tr>\n<td><strong>AT+JD<\/strong><\/td>\n<td>Set join delay in seconds<\/td>\n<td><\/td>\n<td><\/td>\n<td><\/td>\n<\/tr>\n<tr>\n<td><strong>AT+DSK<\/strong><\/td>\n<td>\u00a0Set\/View the data session key<\/td>\n<td>hex 16 bytes<\/td>\n<td><\/td>\n<td><\/td>\n<\/tr>\n<tr>\n<td><strong>AT+NA<\/strong><\/td>\n<td>Set\/View the network address<\/td>\n<td>hex 4 bytes<\/td>\n<td><\/td>\n<td><\/td>\n<\/tr>\n<tr>\n<td><strong>AT+PN<\/strong><\/td>\n<td>Set\/View public network mode<\/td>\n<td>0: Private MTS<\/td>\n<td>1: Public<\/td>\n<td>2:Private LoRaWAN<\/td>\n<\/tr>\n<tr>\n<td><strong>AT+EXIT<\/strong><\/td>\n<td>Exit back to the main menu<\/td>\n<td><\/td>\n<td><\/td>\n<td><\/td>\n<\/tr>\n<tr>\n<td><strong>AT&amp;V<\/strong><\/td>\n<td>View current configuration<\/td>\n<td><\/td>\n<td><\/td>\n<td><\/td>\n<\/tr>\n<tr>\n<td><strong>AT&amp;W<\/strong><\/td>\n<td>Save current configuration<\/td>\n<td><\/td>\n<td><\/td>\n<td><\/td>\n<\/tr>\n<tr>\n<td><strong>AT&amp;F<\/strong><\/td>\n<td>Revert to factory default configuration<\/td>\n<td><\/td>\n<td><\/td>\n<td><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p><strong style=\"font-size: 16px;\"><br \/>\nMDK\/UDK2 Troubleshooting<\/strong><\/p>\n<h4>&#8220;There is not enough space on MULTITECH&#8221;<\/h4>\n<ul>\n<ul>\n<li>Unplug\u00a0the MDK\/UDK2 from USB\u00a0and plug it back in.<\/li>\n<li>If using\u00a0UDK2, disconnect the USB cable and power supply. First, reconnect the power supply, and then reconnect the USB cable.<\/li>\n<\/ul>\n<\/ul>\n<h4>Windows prompts me to install drivers<\/h4>\n<ol>\n<ul>\n<li>Cancel any driver installation prompts. The MDK\/UDK2 mounts as the MULTITECH drive without drivers.<\/li>\n<li>Drivers are only needed for the virtual USB COM port. Installation instructions and files are available on the <a href=\"https:\/\/developer.mbed.org\/teams\/st\/wiki\/ST-Link-Driver\">ARM mbed site<\/a>.<\/li>\n<\/ul>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"<p>The following\u00a0three images\u00a0below\u00a0and on the left\u00a0apply for connecting: the MTDOT-BOX to the MDK (model: MTMDK-ST-MDOT) the MTDOT-EVB\u00a0 to the MDK (model: MTMDK-ST-MDOT) For\u00a0UDK2 users (who received a note regarding the programming cable):\u00a0Due to\u00a0supplier error\u00a0on some devices, the connection\u00a0is the opposite way for connecting (see second UDK2 image on the right): the MTDOT-BOX to\u00a0UDK2 (model: MTUDK2-ST-MDOT) [&hellip;]<\/p>\n","protected":false},"author":1478,"featured_media":0,"parent":10894,"menu_order":5,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_bbp_topic_count":0,"_bbp_reply_count":0,"_bbp_total_topic_count":0,"_bbp_total_reply_count":0,"_bbp_voice_count":0,"_bbp_anonymous_reply_count":0,"_bbp_topic_count_hidden":0,"_bbp_reply_count_hidden":0,"_bbp_forum_subforum_count":0,"footnotes":""},"class_list":["post-10632","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/www.multitech.net\/developer\/wp-json\/wp\/v2\/pages\/10632","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.multitech.net\/developer\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/www.multitech.net\/developer\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/www.multitech.net\/developer\/wp-json\/wp\/v2\/users\/1478"}],"replies":[{"embeddable":true,"href":"https:\/\/www.multitech.net\/developer\/wp-json\/wp\/v2\/comments?post=10632"}],"version-history":[{"count":133,"href":"https:\/\/www.multitech.net\/developer\/wp-json\/wp\/v2\/pages\/10632\/revisions"}],"predecessor-version":[{"id":10660,"href":"https:\/\/www.multitech.net\/developer\/wp-json\/wp\/v2\/pages\/10632\/revisions\/10660"}],"up":[{"embeddable":true,"href":"https:\/\/www.multitech.net\/developer\/wp-json\/wp\/v2\/pages\/10894"}],"wp:attachment":[{"href":"https:\/\/www.multitech.net\/developer\/wp-json\/wp\/v2\/media?parent=10632"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}