{"id":2375,"date":"2020-08-06T10:30:37","date_gmt":"2020-08-06T15:30:37","guid":{"rendered":"http:\/\/blog.espol.edu.ec\/girni\/?p=2375"},"modified":"2026-07-22T05:51:02","modified_gmt":"2026-07-22T10:51:02","slug":"lorawan-gateway-modulo-htm01","status":"publish","type":"post","link":"https:\/\/blog.espol.edu.ec\/girni\/lorawan-gateway-modulo-htm01\/","title":{"rendered":"2. LoRaWan - Gateway con m\u00f3dulo HELTEC HT-M01"},"content":{"rendered":"\n<p>El m\u00f3dulo HT-M01 tiene la opci\u00f3n de conectarse al Raspberry mediante SPI en la parte posterior.<\/p>\n\n\n\n<figure class=\"wp-block-image alignright\"><a href=\"http:\/\/blog.espol.edu.ec\/girni\/files\/2020\/12\/HT-M01_SPI_conector01.png\"><img loading=\"lazy\" decoding=\"async\" width=\"300\" height=\"283\" src=\"http:\/\/blog.espol.edu.ec\/girni\/files\/2020\/12\/HT-M01_SPI_conector01-300x283.png\" alt=\"\" class=\"wp-image-3368\" srcset=\"https:\/\/blog.espol.edu.ec\/girni\/files\/2020\/12\/HT-M01_SPI_conector01-300x283.png 300w, https:\/\/blog.espol.edu.ec\/girni\/files\/2020\/12\/HT-M01_SPI_conector01.png 672w\" sizes=\"auto, (max-width: 300px) 100vw, 300px\" \/><\/a><\/figure>\n\n\n\n<p>Para facilitar la conexi\u00f3n, el fabricante ofrece una placa para montar en un Raspberry Zero.<\/p>\n\n\n\n<figure class=\"wp-block-embed\"><div class=\"wp-block-embed__wrapper\">\nhttps:\/\/heltec.org\/product\/m01-converter\n<\/div><\/figure>\n\n\n\n<figure class=\"wp-block-image\"><a href=\"http:\/\/blog.espol.edu.ec\/girni\/files\/2020\/12\/HTM01Adaptador01.png\"><img loading=\"lazy\" decoding=\"async\" width=\"625\" height=\"298\" src=\"http:\/\/blog.espol.edu.ec\/girni\/files\/2020\/12\/HTM01Adaptador01.png\" alt=\"\" class=\"wp-image-2868\" srcset=\"https:\/\/blog.espol.edu.ec\/girni\/files\/2020\/12\/HTM01Adaptador01.png 625w, https:\/\/blog.espol.edu.ec\/girni\/files\/2020\/12\/HTM01Adaptador01-300x143.png 300w\" sizes=\"auto, (max-width: 625px) 100vw, 625px\" \/><\/a><\/figure>\n\n\n\n<p><\/p>\n\n\n\n<p>En caso de no disponer de la placa, es posible realizar la conexi\u00f3n siguiendo el dise\u00f1o de Robo Zero One.<\/p>\n\n\n\n<figure class=\"wp-block-embed is-type-wp-embed is-provider-robot-zero-one wp-block-embed-robot-zero-one\"><div class=\"wp-block-embed__wrapper\">\n<blockquote class=\"wp-embedded-content\" data-secret=\"sVRdiBOGYf\"><a href=\"https:\/\/robotzero.one\/heltec-lora-gateway-things-network\/\">Heltec HT-M01 LoRa Gateway on the Things Network<\/a><\/blockquote><iframe loading=\"lazy\" class=\"wp-embedded-content\" sandbox=\"allow-scripts\" security=\"restricted\" style=\"position: absolute; visibility: hidden;\" title=\"&#8220;Heltec HT-M01 LoRa Gateway on the Things Network&#8221; &#8212; Robot Zero One\" src=\"https:\/\/robotzero.one\/heltec-lora-gateway-things-network\/embed\/#?secret=BGT8DVH95P#?secret=sVRdiBOGYf\" data-secret=\"sVRdiBOGYf\" width=\"500\" height=\"282\" frameborder=\"0\" marginwidth=\"0\" marginheight=\"0\" scrolling=\"no\"><\/iframe>\n<\/div><\/figure>\n\n\n\n<figure class=\"wp-block-image\"><a href=\"http:\/\/blog.espol.edu.ec\/girni\/files\/2020\/12\/HTM01Adaptador02.png\"><img loading=\"lazy\" decoding=\"async\" width=\"772\" height=\"408\" src=\"http:\/\/blog.espol.edu.ec\/girni\/files\/2020\/12\/HTM01Adaptador02.png\" alt=\"\" class=\"wp-image-2867\" srcset=\"https:\/\/blog.espol.edu.ec\/girni\/files\/2020\/12\/HTM01Adaptador02.png 772w, https:\/\/blog.espol.edu.ec\/girni\/files\/2020\/12\/HTM01Adaptador02-300x159.png 300w, https:\/\/blog.espol.edu.ec\/girni\/files\/2020\/12\/HTM01Adaptador02-768x406.png 768w\" sizes=\"auto, (max-width: 772px) 100vw, 772px\" \/><\/a><\/figure>\n\n\n\n<p><\/p>\n\n\n\n<p>Durante la implementaci\u00f3n realizada, no se dispon\u00eda del adaptador por lo que se prob\u00f3 construir un adaptador usando una placa perforada, teniendo los mismos resultados que con la placa de HELTEC.<\/p>\n\n\n\n<p>El Kit de conexi\u00f3n del fabricante como referencia se muestra a continuacion:<\/p>\n\n\n\n<figure class=\"wp-block-image\"><a href=\"http:\/\/blog.espol.edu.ec\/girni\/files\/2020\/01\/LoraModuloGtwHeltecHT_m01.png\"><img loading=\"lazy\" decoding=\"async\" width=\"1079\" height=\"717\" src=\"http:\/\/blog.espol.edu.ec\/girni\/files\/2020\/01\/LoraModuloGtwHeltecHT_m01.png\" alt=\"\" class=\"wp-image-2778\" srcset=\"https:\/\/blog.espol.edu.ec\/girni\/files\/2020\/01\/LoraModuloGtwHeltecHT_m01.png 1079w, https:\/\/blog.espol.edu.ec\/girni\/files\/2020\/01\/LoraModuloGtwHeltecHT_m01-300x199.png 300w, https:\/\/blog.espol.edu.ec\/girni\/files\/2020\/01\/LoraModuloGtwHeltecHT_m01-768x510.png 768w, https:\/\/blog.espol.edu.ec\/girni\/files\/2020\/01\/LoraModuloGtwHeltecHT_m01-1024x680.png 1024w, https:\/\/blog.espol.edu.ec\/girni\/files\/2020\/01\/LoraModuloGtwHeltecHT_m01-272x182.png 272w\" sizes=\"auto, (max-width: 1079px) 100vw, 1079px\" \/><\/a><\/figure>\n\n\n\n<p><\/p>\n\n\n\n<p>Para el m\u00f3dulo HT-M01, el fabricante Heltec public\u00f3 una aplicaci\u00f3n para gestionar los paquetes denominado packet-forwarder, encargada de reenviar los paquetes a un administrador de gateways.<\/p>\n\n\n\n<figure class=\"wp-block-image\"><a href=\"http:\/\/blog.espol.edu.ec\/girni\/files\/2020\/09\/PacketForwarder01.png\"><img loading=\"lazy\" decoding=\"async\" width=\"1191\" height=\"549\" src=\"http:\/\/blog.espol.edu.ec\/girni\/files\/2020\/09\/PacketForwarder01.png\" alt=\"\" class=\"wp-image-3785\" srcset=\"https:\/\/blog.espol.edu.ec\/girni\/files\/2020\/09\/PacketForwarder01.png 1191w, https:\/\/blog.espol.edu.ec\/girni\/files\/2020\/09\/PacketForwarder01-300x138.png 300w, https:\/\/blog.espol.edu.ec\/girni\/files\/2020\/09\/PacketForwarder01-768x354.png 768w, https:\/\/blog.espol.edu.ec\/girni\/files\/2020\/09\/PacketForwarder01-1024x472.png 1024w\" sizes=\"auto, (max-width: 1191px) 100vw, 1191px\" \/><\/a><\/figure>\n\n\n\n<p>Los datos recibidos por el m\u00f3dulo gateway son reenviados por SPI o el puerto USB hacia la red local o internet usando el aplicativo instalado en un Raspberry Pi.<\/p>\n\n\n\n<p>En las pruebas con USB se encontr\u00f3 que para reiniciar el m\u00f3dulo HT-M01 es necesario presionar el bot\u00f3n Reset, mientras que en el modo SPI se pod\u00eda realizar de forma remota, por lo que <strong>se prefiere configurar el modo SPI<\/strong>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Activar interface SPI<\/h2>\n\n\n\n<p>En Raspberry OS la interface SPI requiere activarse para su uso con la siguiente instrucci\u00f3n:<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">sudo raspi-config<\/pre>\n\n\n\n<p>Que permite seleccionar de una ventana las opciones de interface<\/p>\n\n\n\n<figure class=\"wp-block-image\"><a href=\"http:\/\/blog.espol.edu.ec\/girni\/files\/2020\/09\/CS_PacketForwarder01.png\"><img loading=\"lazy\" decoding=\"async\" width=\"1286\" height=\"745\" src=\"http:\/\/blog.espol.edu.ec\/girni\/files\/2020\/09\/CS_PacketForwarder01.png\" alt=\"\" class=\"wp-image-2860\" srcset=\"https:\/\/blog.espol.edu.ec\/girni\/files\/2020\/09\/CS_PacketForwarder01.png 1286w, https:\/\/blog.espol.edu.ec\/girni\/files\/2020\/09\/CS_PacketForwarder01-300x174.png 300w, https:\/\/blog.espol.edu.ec\/girni\/files\/2020\/09\/CS_PacketForwarder01-768x445.png 768w, https:\/\/blog.espol.edu.ec\/girni\/files\/2020\/09\/CS_PacketForwarder01-1024x593.png 1024w\" sizes=\"auto, (max-width: 1286px) 100vw, 1286px\" \/><\/a><\/figure>\n\n\n\n<p>para luego activar SPI<\/p>\n\n\n\n<figure class=\"wp-block-image\"><a href=\"http:\/\/blog.espol.edu.ec\/girni\/files\/2020\/09\/CS_PacketForwarder02.png\"><img loading=\"lazy\" decoding=\"async\" width=\"1287\" height=\"744\" src=\"http:\/\/blog.espol.edu.ec\/girni\/files\/2020\/09\/CS_PacketForwarder02.png\" alt=\"\" class=\"wp-image-2861\" srcset=\"https:\/\/blog.espol.edu.ec\/girni\/files\/2020\/09\/CS_PacketForwarder02.png 1287w, https:\/\/blog.espol.edu.ec\/girni\/files\/2020\/09\/CS_PacketForwarder02-300x173.png 300w, https:\/\/blog.espol.edu.ec\/girni\/files\/2020\/09\/CS_PacketForwarder02-768x444.png 768w, https:\/\/blog.espol.edu.ec\/girni\/files\/2020\/09\/CS_PacketForwarder02-1024x592.png 1024w\" sizes=\"auto, (max-width: 1287px) 100vw, 1287px\" \/><\/a><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">Conexi\u00f3n mediante SPI<\/h2>\n\n\n\n<p>Las instrucciones paso a paso se describen m\u00e1s adelante, para la ultima instrucci\u00f3n hay que tener disponible la configuraci\u00f3n de regi\u00f3n. Para el caso de Ecuador es US915.<\/p>\n\n\n\n<p>Cada instrucci\u00f3n se debe realizar en secuencia, el el pen\u00faltimo paso se obtiene el Gateway _id, que ser\u00e1 usado para registrar el mini gateway en el servidor de red&nbsp; y aplicaciones.<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">mkdir lora<br>cd lora<br>sudo apt-get update<br>sudo apt-get install git<br>git clone https:\/\/github.com\/Lora-net\/lora_gateway.git<br><span style=\"color: #ff0000\"># LoRa Gateway drivers<\/span><br>git clone https:\/\/github.com\/Lora-net\/packet_forwarder.git<br><span style=\"color: #ff0000\"># packet forwarding software<\/span><br>git clone https:\/\/github.com\/HelTecAutomation\/lorasdk.git<\/pre>\n\n\n\n<p><em><strong>Nota<\/strong><\/em> 2026-03: En Raspbian OS se recomienda usar un nombre de usuario diferente de \"<strong>pi<\/strong>\", por lo que se deben ajustar las direcciones en las instrucciones al usuario en las ultimas instrucciones.&nbsp;<\/p>\n\n\n\n<p>En el directorio \"lorasdk\" Edite el archivo \"<strong>install.sh<\/strong>\" y \"<strong>lrgateway.service<\/strong>\" para evitar errores de donde se encuentra el archivo. Por ejemplo en install.sh, se editan las l\u00edneas con sudo nano <strong>install.sh<\/strong><\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">sudo sh .\/reset_pkt_fwd.sh start local_conf.json<br>sudo cp -f ${dir}\/reset_pkt_fwd.sh \/home\/<strong><mark class=\"has-inline-color has-luminous-vivid-orange-color\">pi<\/mark><\/strong>\/lora\/packet_forwarder<br>sudo cp -f ${dir}\/reset_pkt_fwd.sh \/home\/<strong><mark class=\"has-inline-color has-luminous-vivid-orange-color\">pi<\/mark><\/strong>\/lora\/packet_forwarder\/lora_pkt_fwd<br>sudo cp -f ${dir}\/local_conf.json \/home\/<strong><mark class=\"has-inline-color has-luminous-vivid-orange-color\">pi<\/mark><\/strong>\/lora\/packet_forwarder\/lora_pkt_fwd<\/pre>\n\n\n\n<p>en el caso de \"<strong>lrgateway.service<\/strong>\", se editan las l\u00edneas con sudo nano <strong>lrgateway.service<\/strong><\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">[Service]<br>Restart=always<br>RestartSec=30<br>WorkingDirectory=\/home\/<strong><mark class=\"has-inline-color has-luminous-vivid-orange-color\">pi<\/mark><\/strong>\/lora\/packet_forwarder\/lora_pkt_fwd<br>ExecStartPre=\/home\/<strong><mark class=\"has-inline-color has-luminous-vivid-orange-color\">pi<\/mark><\/strong>\/lora\/packet_forwarder\/reset_pkt_fwd.sh start \/home\/<mark class=\"has-inline-color has-luminous-vivid-orange-color\"><strong>pi<\/strong><\/mark>\/lora\/packet_forwarder\/lora_pkt_fwd\/local_conf.json<br>ExecStart=\/home\/<strong><mark class=\"has-inline-color has-luminous-vivid-orange-color\">pi<\/mark><\/strong>\/lora\/packet_forwarder\/lora_pkt_fwd\/lora_pkt_fwd<br>ExecStopPost=\/home\/<strong><mark class=\"has-inline-color has-luminous-vivid-orange-color\">pi<\/mark><\/strong>\/lora\/packet_forwarder\/reset_pkt_fwd.sh stop<\/pre>\n\n\n\n<p>actualizado los archivos, se puede continuar con las correcciones en los directorios:<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"># This package will create a \"lrgateway\" service in Raspberry Pi<br>cd \/home\/<strong><mark class=\"has-inline-color has-luminous-vivid-orange-color\">pi<\/mark><\/strong>\/lora\/lora_gateway<br>make clean all<br>cd \/home\/<strong><mark class=\"has-inline-color has-luminous-vivid-orange-color\">pi<\/mark><\/strong>\/lora\/packet_forwarder<br>make clean all<br>cd \/home\/<strong><mark class=\"has-inline-color has-luminous-vivid-orange-color\">pi<\/mark><\/strong>\/lora\/lorasdk<br>chmod +x install.sh <br>.\/install.sh<br>#Run the script. After the script is run, it will create a <br># service named \"lrgateway\". The purpose is to make the lora driver <br># and data forwarding program run automatically at startup.<br>sudo cp -f \/home\/<strong><mark class=\"has-inline-color has-luminous-vivid-orange-color\">pi<\/mark><\/strong>\/lora\/lorasdk\/<mark class=\"has-inline-color has-vivid-purple-color\"><strong>global_conf_US915<\/strong>.<\/mark>json \/home\/<strong><mark class=\"has-inline-color has-luminous-vivid-orange-color\">pi<\/mark><\/strong>\/lora\/packet_forwarder\/lora_pkt_fwd\/global_conf.json<br>#the \"<mark class=\"has-inline-color has-vivid-purple-color\">global_conf_US915<\/mark>.json\" may need change to your need.<\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Cambios para Raspberry pi OS Trixie 2026-03<\/h2>\n\n\n\n<p>En la versi\u00f3n Bookworm y Trixie, las instrucciones para manejar <strong>GPIOs <\/strong>han migrado a <strong>pinctrl<\/strong>, por lo que se debe actualizar el archivo \/lora\/packet_forwarder\/lora_pkt_fwd.sh<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\"># Force bypassing auto update of Gateway_ID in JSON conf file<br>IOT_SK_GWID_UPDATE=true<br><br># The reset pin of SX1301 is wired with RPi GPIO2<br>IOT_SK_SX1301_RESET_PIN=17<br><br>WAIT_GPIO() {<br>    sleep 1<br>}<br><br>iot_sk_init() {<br>    # setup GPIO 17<br>    echo \"iot_sk_init \"$IOT_SK_SX1301_RESET_PIN\" ...\" <strong><mark class=\"has-inline-color has-vivid-purple-color\">#<\/mark><\/strong>&gt; \/sys\/class\/gpio\/export; WAIT_GPIO<br><br>    # set GPIO 17 as output<br>    echo \"out\" <strong><mark class=\"has-inline-color has-vivid-purple-color\">#<\/mark><\/strong>&gt; \/sys\/class\/gpio\/gpio$IOT_SK_SX1301_RESET_PIN\/direction; WAIT_GPIO<br><br>    # write output for SX1301 reset<br>    <strong><mark class=\"has-inline-color has-luminous-vivid-orange-color\">pinctrl <\/mark><\/strong>set 17 op dh<br>    WAIT_GPIO<br>    pinctrl get 17<br>    echo \"1\" <mark class=\"has-inline-color has-vivid-purple-color\"><strong>#<\/strong><\/mark>&gt; \/sys\/class\/gpio\/gpio$IOT_SK_SX1301_RESET_PIN\/value; WAIT_GPIO<br>    <mark class=\"has-inline-color has-luminous-vivid-orange-color\"><strong>pinctrl <\/strong><\/mark>set 17 op dl<br>    pinctrl get 17<br>    WAIT_GPIO<br>    echo \"0\" <mark class=\"has-inline-color has-vivid-purple-color\"><strong>#<\/strong><\/mark>&gt; \/sys\/class\/gpio\/gpio$IOT_SK_SX1301_RESET_PIN\/value; WAIT_GPIO<br>    # set GPIO 17 as input<br>    <mark class=\"has-inline-color has-luminous-vivid-orange-color\"><strong>pinctrl <\/strong><\/mark>set 17 ip<br>    pinctrl get 17<br>    WAIT_GPIO<br>    echo \"in\" <mark class=\"has-inline-color has-vivid-purple-color\"><strong>#<\/strong><\/mark>&gt; \/sys\/class\/gpio\/gpio$IOT_SK_SX1301_RESET_PIN\/direction; WAIT_GPIO<br>}<br><br>iot_sk_term() {<br>    echo \"iot_sk_term\"<br>    # cleanup GPIO 17<br>    <mark class=\"has-inline-color has-luminous-vivid-orange-color\"><strong>pinctrl <\/strong><\/mark>get 17<br>    echo  \" term reiniciando\"<br>    if [ -d \/sys\/class\/gpio\/gpio$IOT_SK_SX1301_RESET_PIN ]<br>    then<br>        <mark class=\"has-inline-color has-luminous-vivid-orange-color\"><strong>pinctrl <\/strong><\/mark>get 17<br>        echo \" iot_sk_term en if \"$IOT_SK_SX1301_RESET_PIN\" ...\" <mark class=\"has-inline-color has-vivid-purple-color\"><strong>#<\/strong><\/mark>&gt; \/sys\/class\/gpio\/unexport; WAIT_GPIO<br>    fi<br>}<\/pre>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">Conexi\u00f3n al puerto USB<\/h2>\n\n\n\n<p>Las instrucciones son muy semejantes al proceso anterior, para la ultima instrucci\u00f3n hay que tener disponible la configuraci\u00f3n de regi\u00f3n. Para el caso de Ecuador es US915.<\/p>\n\n\n\n<p>Cada instrucci\u00f3n se debe realizar en secuencia, el el pen\u00faltimo paso se obtiene el Gateway _id, que ser\u00e1 usado para registrar el mini gateway en el servidor de red&nbsp; y aplicaciones<\/p>\n\n\n\n<p>Si el m\u00f3dulo fue instalado en el proceso anterior, no es necesario ejecutar esta secci\u00f3n<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">mkdir lora\n<span class=\"nb\">cd<\/span> lora\nsudo apt-get update\nsudo apt-get install git\ngit clone https:\/\/github.com\/Lora-net\/picoGW_hal.git\ngit clone https:\/\/github.com\/Lora-net\/picoGW_packet_forwarder.git\ngit clone https:\/\/github.com\/HelTecAutomation\/picolorasdk.git\n<span class=\"nb\">cd<\/span> \/home\/pi\/lora\/picoGW_hal\nmake clean all\n<span class=\"nb\">cd<\/span> \/home\/pi\/lora\/picoGW_packet_forwarder\nmake clean all\n<span class=\"nb\">cd<\/span> \/home\/pi\/lora\/picolorasdk\nchmod +x install.sh\n.\/install.sh\n<span style=\"color: #ff0000\">#Run this script will create a service named \"lrgateway\". The purpose is to make the lora driver and data forwarding program run automatically at startup.<\/span>\nsudo cp -f \/home\/pi\/lora\/picolorasdk\/global_conf_US915.json \/home\/pi\/lora\/picoGW_packet_forwarder\/lora_pkt_fwd\/global_conf.json\n<span style=\"color: #ff0000\">#Put the configuration file on the specified path<\/span><\/pre>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">Estado de Packet-forwarder<\/h2>\n\n\n\n<p>Las instrucciones de instalaci\u00f3n se encuentran en:<\/p>\n\n\n\n<p>HT-M01 Mini LoRa Gateway Quick Start. Heltec.org. Revisado Septiembre 2023<\/p>\n\n\n\n<p><a href=\"https:\/\/docs.heltec.org\/en\/gateway\/ht-m01\/quick_start.html#summary\">https:\/\/docs.heltec.org\/en\/gateway\/ht-m01\/quick_start.html#summary<\/a><\/p>\n\n\n\n<p>Estado de la aplicaci\u00f3n se obtiene con la instrucci\u00f3n:<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">sudo systemctl status lrgateway\n<\/pre>\n\n\n\n<p>obteniendo un mensaje semejante a:<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">pi@GirniLrGw1:~ $ sudo systemctl status lrgateway\n\u25cf lrgateway.service - packet forwarder\n   Loaded: loaded (\/etc\/systemd\/system\/lrgateway.service; enabled; vendor preset: enabled)\n   Active: <strong><span style=\"color: #008000\">active (running)<\/span><\/strong> since Tue 2021-06-29 08:05:25 -05; 15min ago\n  Process: 7763 ExecStartPre=\/home\/pi\/lora\/packet_forwarder\/reset_pkt_fwd.sh start \/home\/pi\/lora\/pa\n Main PID: 7797 (lora_pkt_fwd)\n    Tasks: 5 (limit: 2062)\n   CGroup: \/system.slice\/lrgateway.service\n           \u2514\u25007797 \/home\/pi\/lora\/packet_forwarder\/lora_pkt_fwd\/lora_pkt_fwd\n<\/pre>\n\n\n\n<p>En caso de requerir reiniciar se cambia \"status\" por \"restart\".<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">sudo systemctl restart lrgateway\n<\/pre>\n\n\n\n<h2 class=\"wp-block-heading\">Archivos de Configuraci\u00f3n de Packet_forwarder<\/h2>\n\n\n\n<p>Se crean dos archivos: \"global\" y \"local\" que son complementarios en el siguiente directorio:<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">cd\ncd lora\/packet_forwarder\/lora_pkt_fwd \nls\n<\/pre>\n\n\n\n<p>obteniendo el siguiente resultado<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">cfg  global_conf.json  inc  local_conf.json \nlora_pkt_fwd  Makefile  obj  readme.md  src \nupdate_gwid.sh\n<\/pre>\n\n\n\n<p>El archivo local contiene la identificaci\u00f3n del gateway obtenida luego de ejecutar la l\u00ednea <code>.\/install.sh<\/code> del proceso anterior. El archivo global contiene la informaci\u00f3n de la regi\u00f3n y las frecuencias usadas.<\/p>\n\n\n\n<p>se editan los archivos con<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">sudo nano global_conf.json\n\nsudo nano local_conf.json<\/pre>\n\n\n\n<h1 class=\"wp-block-heading\">Conexi\u00f3n a ChirpStack-gateway-bridge<\/h1>\n\n\n\n<p>El archivo \"global_conf.json\" se configura el servidor donde se encuentra el gateway-bridge usando el par\u00e1metro \"server_address\". Si se encuentra en el mismo Raspberry Pi que el Packet-forwarder se usa \"localhost\", sino con la direcci\u00f3n IP respectiva. Tambi\u00e9n hay que actualizar los par\u00e1metros para el \"gateway_ID\" obtenido al final del proceso al instalar el packet-forwarder.<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">    \"gateway_conf\": {\n        \"gateway_ID\": \"3532363324003700\",\n        \/* change with default server address\/ports, or overwrite in local_conf.json *\/\n        \"server_address\": \"192.168.10.50\",\n        \"serv_port_up\": 1700,\n        \"serv_port_down\": 1700,\n        \/* adjust the following parameters for your network *\/\n        \"keepalive_interval\": 10,\n        \"stat_interval\": 30,\n        \"push_timeout_ms\": 100,\n        \/* forward only valid packets *\/\n        \"forward_crc_valid\": true,\n        \"forward_crc_error\": false,\n        \"forward_crc_disabled\": false\n    }\n<\/pre>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\" \/>\n\n\n\n<h1 class=\"wp-block-heading\">Conexi\u00f3n a TTN<\/h1>\n\n\n\n<p>El archivo \"global_conf.json\" se configura para un servidor TTN de la reg\u00edon, revisar los datos apropiador para \"gateway_ID\" y \"server_address\".<\/p>\n\n\n\n<pre class=\"wp-block-preformatted\">    \"gateway_conf\": {\n        \"gateway_ID\": \"3532363324003700\",\n        \/* change with default server address\/ports, or overwrite in local_conf.json *\/\n        \"server_address\": \"router.us.thethings.network\",\n        \"serv_port_up\": 1700,\n        \"serv_port_down\": 1700,\n        \/* adjust the following parameters for your network *\/\n        \"keepalive_interval\": 10,\n        \"stat_interval\": 30,\n        \"push_timeout_ms\": 100,\n        \/* forward only valid packets *\/\n        \"forward_crc_valid\": true,\n        \"forward_crc_error\": false,\n        \"forward_crc_disabled\": false\n    }\n<\/pre>\n\n\n\n<p><em><strong>Referencia<\/strong><\/em>: <a href=\"https:\/\/www.chirpstack.io\/gateway-bridge\/install\/debian\/\">https:\/\/www.chirpstack.io\/gateway-bridge\/install\/debian\/<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>El m\u00f3dulo HT-M01 tiene la opci\u00f3n de conectarse al Raspberry mediante SPI en la parte posterior. Para facilitar la conexi\u00f3n, el fabricante ofrece una placa para montar en un Raspberry Zero. En caso de no disponer de la placa, es posible realizar la conexi\u00f3n siguiendo el dise\u00f1o de Robo Zero One. Durante la implementaci\u00f3n realizada, [&hellip;]<\/p>\n","protected":false},"author":8043,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1447338],"tags":[602214,1457736],"class_list":["post-2375","post","type-post","status-publish","format-standard","hentry","category-chirpstack-broker","tag-iot","tag-lorawan"],"_links":{"self":[{"href":"https:\/\/blog.espol.edu.ec\/girni\/wp-json\/wp\/v2\/posts\/2375","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.espol.edu.ec\/girni\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.espol.edu.ec\/girni\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.espol.edu.ec\/girni\/wp-json\/wp\/v2\/users\/8043"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.espol.edu.ec\/girni\/wp-json\/wp\/v2\/comments?post=2375"}],"version-history":[{"count":39,"href":"https:\/\/blog.espol.edu.ec\/girni\/wp-json\/wp\/v2\/posts\/2375\/revisions"}],"predecessor-version":[{"id":4307,"href":"https:\/\/blog.espol.edu.ec\/girni\/wp-json\/wp\/v2\/posts\/2375\/revisions\/4307"}],"wp:attachment":[{"href":"https:\/\/blog.espol.edu.ec\/girni\/wp-json\/wp\/v2\/media?parent=2375"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.espol.edu.ec\/girni\/wp-json\/wp\/v2\/categories?post=2375"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.espol.edu.ec\/girni\/wp-json\/wp\/v2\/tags?post=2375"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}