dibya mohanty
Forum Replies Created
-
AuthorPosts
-
May 4, 2018 at 10:22 am in reply to: What is the new lora-query command for adding nodes in MTCAP #23365
dibya mohanty
Participantsomehow this link does not solve my problem. Is there some way i can debug this?
May 3, 2018 at 4:47 am in reply to: What is the new lora-query command for adding nodes in MTCAP #23354ParticipantHi Jason,
I was able to add all the keys based on the curl commands. Now when i see the LoraWan > Key Management i find my device and the keys associated to it.Now i fail to connect but in the log i find –
2018-05-03T11:57:26.094224+02:00 mtcap lora-network-server: GW:00-80-00-00-00-01-09-78|FRAME-RX|Parsing 1 packets
2018-05-03T11:57:26.095330+02:00 mtcap lora-network-server: GW:00-80-00-00-00-01-09-78|FRAME-RX|CRC-ERRORCan you help me out with what is going wrong here?
April 9, 2018 at 7:47 am in reply to: What is the new lora-query command for adding nodes in MTCAP #23048ParticipantThis is a bit strange… Can i at least GET a particular node based on deveui or does that also work by array index?
April 9, 2018 at 6:35 am in reply to: What is the new lora-query command for adding nodes in MTCAP #23043ParticipantThanks a lot. I was able to add a node using the curl commands and also list then using the curl get command. Now i want to delete a specific node using the curl delete command. How can i do that ?
April 6, 2018 at 2:56 pm in reply to: What is the new lora-query command for adding nodes in MTCAP #23035ParticipantI cannot use the UI for registration since i have to automate the process.
I have an AEP, so that means the curl command is the right way to register?
Restarting the network server everytime adds an additional overhead now.
ParticipantThanks John,
Now it works. Is there a new version of the firmware? Is a firmware upgrade required?Can i somehow install the admin GUI similar to the conduit? Earlier with the MTCDT we used Node-Red. Can i install Node-red and work with it?
ParticipantYes i solved it. I had to flash the firmware of the gateway and installed the packages freshly and everything works fine now. I guess i had some broken issues in the file system, so when i flashed the firmware and reinstalled everything afresh everything worked.
ParticipantHi Steve,
Re-registered both the Conduits on DeviceHQ and they are generating lora data. Still no LoRa tab for both.
Serial # for both – 18900316, 18721570
ParticipantHi Steve,
I tried every possible setting and config but could not get the LoRa tab for the gateway2. So de-registered the gateway1 which had the LoRa tab and re-registered it. Now i don’t see the LoRa tab for both of them. 🙁
Strange!!!ParticipantHi Steve,
It has an installed LoRa mCard since i am already using it to communicate to my Lora modules. So i think that might not be the problem somehow.
ParticipantProblem again. After flashing the gateway to the firmware 1.3.2, I set up the LORA network server with the same EUI and Key as before. But somehow the RN2483 boards give me an error JOIN denied when i do a mac join OTAA.
I set the appeui and appkey on the RN2483 boards by using the mac set commands. Then i do a mac save as usual. Has the connection mechanism changed with the firmware upgrade or am i missing something?ParticipantThanks a lot. Was able to flash it with AEP again with the help of the support guys. All up and running now 🙂
ParticipantHi Bryan,
Thanks for the info. Yes, the model number is 210A so I have a AEP model conduit. So i have a MTCDT-H5-210AParticipantAre you sure? Before reflashing I had used the following command – $cat /etc/mLinux-version and that had returned 3.1.0. Is that also the case in an AEP model conduit?
Participanti can ssh into the conduit now but still cannot access the login page 192.168.2.1 from the browser. Am i missing something?
ParticipantYes, on the boot console the conduit boots to login and I can login using root/root
ParticipantOk. I got how to get to the debug interface. I follow this oage – http://www.multitech.net/developer/products/conduit/connecting-to-the-debug-interface/
So i use Tera Term and use a baud rate of 115200. I get a Black screen with a cursor blinking
ParticipantHow do i get to the debug console? I was trying to go to the address 192.168.2.1 on the browser or ssh using root. Do I have to unscrew the front panel for the debug USB port ?
ParticipantUnable to fix the node issue, i decided to re-flash the conduit. I used a pre-built image and used the 2 files as mentioned in the Detailed Steps. Now after re-flashing the conduit doesnt take the default 192.168.2.1 IP. Cannot login or even ssh into it.
ParticipantIt’s getting more complicated. Since I already had v0.10.40 it does not downgrade it to 0.8.28. There is an option of force downgrade in opkg utility. So I did a force downgrade. Now I don’t have node as well as npm. If I do a node – v and npm -v I get a command not found. And ideas?
ParticipantI am running 3.1.0 mlinux. I used the link provided by you to go to the page –
http://www.multitech.net/mlinux/feeds/3.1/arm926ejste/
But i don’t find the corresponding nodejs-npm for 3.1.0. Is it named something else? Here are the existing nodejs packages for 3.1.0-
nodejs-dbg_0.8.28-r0.0_arm926ejste.ipk
nodejs-dev_0.8.28-r0.0_arm926ejste.ipk
nodejs-doc_0.8.28-r0.0_arm926ejste.ipk
nodejs_0.8.28-r0.0_arm926ejste.ipkParticipantcant i just install npm somehow ?
ParticipantHi Jeff,
Thanks for the response. I also have node-red-contrib-aws-iot installed and configured. I use the mLinux conduit. Can you check by installing the above mentioned module?
-
AuthorPosts