Hi to all, im a little new to LoRaWAN technology but have gathered some of the information up til now. I have a multi tech gateway MTCDT-H5-210A-AU with a lora chip in it MTAC-LORA-915 and couple of Mdot devices also MTUDK2-ST-MDOT(included 915MHz antenna). But i dont know from where to start actually and how to set up the gateway and connect it to the ttn server to make it running. Please advice me how to start and get things working.
I’ll see what I can do to make conversion easier for AEP owners. Connecting the AEP to TTN would imply loosing AEP functions as having two backends (the EAP embedded one and TTN) control the radio is asking for trouble.
So are you saying using the AEP model makes it difficult/impossible to connect to TTN?
I am new to LoRa, so I can’t read into the subtlety of some answers.
Thank you.
I know it won’t be impossible because other people did it, I don’t think it will be difficult, but that opinion is based on documentation only, not practical experience trying to convert a gateway. If everything goes according to plan one of the forum users will help me convert a Linux conduit to AEP over the weekend so I can start working on some documentation or (hoping) adapt my installation script to work for AEP as well.
Hi Kersing thanks for your help i followed the same steps you mentioned here until the configuration of the installer.sh file but still we dont get the gateway on the TTN
And i am really confused about the instructions given on the TTN website to connect the gateway to TTN because i see that there are 3 links which give instructions on how to connect the gateway to the TTN
IS the same which you have given in the forum but we also got some steps after this configuration of the installer.sh file which are as follows:
Restart the installer to continue installation.
sh installer.sh Once the installer finished (without errors) the Conduit is connected to TheThingsNetwork.
I dont know which link to follow and what should i do after setting up the installer.sh file.
The instructions at 1 and 2 are old and require manual steps which the installer automates. If you use the installer.sh you need to run it twice. The first run performs a network setup, the second run uses the configured network to get additional files required for the installation.
My instructions do NOT contain this. Once the installer is finished after the second run your conduit is connected, there is no need to perform additional steps. Please do not mix different sets of instructions.
To check if your gateway is connected, check the staging status page @ http://staging.thethingsnetwork.org/gatewaystatus/ your gateway should be listed on that page. (The EUI of your gateway can be found in /var/config/lora/local_conf.json on the conduit)
BTW, you do not have to post screen shots, just select the text in putty and paste it in your message. (Between [ code ] and [ /code ] (skip the space) to keep the formatting intact.)
“No such file or directory” Please let me know what to do
The step no 3 which you have told by which we have to connect with the gateway the problem is if i use the ROOT username i dnt know the password i tried root but it doesnot work so i did everything by logging to the admin username is that ok
For AEP you need to use ‘admin’ so that is not a problem. Could you run the following commands (each line is a seperate command) and provide the output:
cat /var/config/.installer
ls -l /var/config/lora
cd
ls -l
Hi Kersing,…My gateway id is “008000000000B667” and it is on the network but still i cannot see the latitude and longitude of the gateway there it says 0,0 fo rlatitude and longitude what could be the problem is there anything i have to do more?
sh installer.sh
installer.sh: line 9: $’\r’: command not found
installer.sh: line 14: $’\r’: command not found
installer.sh: line 28: syntax error near unexpected token $'{\r'' 'nstaller.sh: line 28:say() {
@Irek
It looks like the installer script suffers from LF to CR/LF expansion. Please download it again and transfer it to the MultiTech in binary mode. Do not open in any windows tools.
Did you use the instructions for AEP Conduit or for mLinux? If not please use those.
@Kersing
Thanks for response. I was trying the script for mLinux, but in the meantime I upgraded conduit to AEP version. Of course with downloaded binary your script works properly Now I’m successfully connected to TNN.
Irek