mdot class C manual activation probel
- This topic has 1 reply, 2 voices, and was last updated 9 years ago by .
Viewing 2 posts - 1 through 2 (of 2 total)
Viewing 2 posts - 1 through 2 (of 2 total)
- You must be logged in to reply to this topic.
Tagged: mdot class C manual activation
Hello to everyone
I am trying to setup an mdot as a class C device using manual activation (ABP).
I am using conduit AEP and I have used lora-querry app in order to provision the Dot on the gateway. The dot can send data to the conduit but can not receive the ones send from the conduit (like a class C device should). I have log info in trace but nothing appears on the serial console when I send packets from the conduit (it’s like that the mdot is not in listening state). However on another mdot’s(let’s say mdot B) serial console that joined the network using OTA, I can see that the packet transmitted from the conduit has been received from the mdot’s radio(mdot B) and dropped because of the address. If I change the join method to OTA for the first mdot, packets transmitted from the conduit are received normally, but I want it to work with manual activation. For this experiment I have used the class_c_example from dot-examples and changed the join method to Manual. I have also changed the appropriate configuration variables(nwskey,dataskey(appskey) and net address to match the ones on the conduit). I cannot figure out what is wrong 🙁 any help will be really appreciated
Thank you in advance
Hello Evangelos,
Do you have resolve your problem ? I tried to connect my mdot 868 in manual configuration but nothing.
Thanks you