piyush s

Forum Replies Created

Viewing 13 posts - 1 through 13 (of 13 total)
  • Author
    Posts
  • May 23, 2017 at 11:20 pm in reply to: Resetting the Conduit to factory state #19284
    piyush s
    Participant

    Thanks Ajay, I did a quick check and it turned out that mini USB port at both front and back has the capability to do that.

    May 23, 2017 at 7:36 am in reply to: Problem with dhcp when there is a power failure #19269
    piyush s
    Participant

    Hi Mikel,

    Were you able to get your problem resolved? Did you modify the dhcp client (or its argument) to solve that or some other way?

    thanks,
    –Piyush

    May 23, 2017 at 7:34 am in reply to: Resetting the Conduit to factory state #19268
    piyush s
    Participant

    Hello Eric,

    Revisited this thread after a long time and saw your response. Can you tell me how did you flash the conduit using U-boot via debug cable? What debug cable you are referring to and how was it connected to the conduit? Did you use USB port and some USB-Serial converter for this purpose?

    thanks,
    –Piyush

    April 19, 2017 at 12:15 am in reply to: Resetting the Conduit to factory state #18349
    piyush s
    Participant

    Thanks Jeff, with your comment, I was able to locate the reset handler script running as daemon in /usr/sbin/reset-handler

    Appreciate the support.

    January 18, 2017 at 7:20 am in reply to: acknowledgement of downlink packets #16374
    piyush s
    Participant

    Could you please provide an example for this? This seems to be bit confusing to understand.

    thanks,

    January 18, 2017 at 4:07 am in reply to: MQTT topics behaviour #16367
    piyush s
    Participant

    Hello

    Did you get your queries answered ?

    thanks,

    January 18, 2017 at 3:50 am in reply to: Queue size and configuration #16366
    piyush s
    Participant

    The ‘nc’ utility is working fine, and I could set/get the queue size.
    But is there any way by which we could query and find the status of the queue, I mean how many slots are still open?
    Also I saw a downstream MQTT topic for clearing the queue-
    lora/<DEV-EUI>/clear
    I used it as below:
    mosquitto_pub -t lora/00:11:22:33:44:55:66:77/clear
    and I got an error “Error: Both topic and message must be supplied.”

    Can you please tell what I am missing here? Is there any other way to use this topic?

    thanks,

    January 18, 2017 at 3:10 am in reply to: acknowledgement of downlink packets #16365
    piyush s
    Participant

    Can we please have some response on this query?

    thanks,

    January 17, 2017 at 7:12 am in reply to: Queue size and configuration #16346
    piyush s
    Participant

    Thanks Jason,

    What is the default value for this nodeQueueSize?
    Also is there any way to print all the advanced Lora configurations using either lora-query or some other utility?

    thanks,

    January 5, 2017 at 7:16 am in reply to: Manually adding node via ABP #16222
    piyush s
    Participant

    Jason,

    I was mistakenly removing the space between NSK and DSK in lora-query command. Looked thoroughly to find that out. It worked. But it ‘d be good to know the difference between ‘/up’ and ‘/packet_recv’.

    thanks,

    January 5, 2017 at 7:09 am in reply to: Manually adding node via ABP #16221
    piyush s
    Participant

    Thanks Jason for the response.

    I queried with the ‘-c’ option and observed the different value ‘2b7e151628aed2a6abf7158809cf4f3c’ under the network session key. I guess this is because of the encryption. I even updated my lora-query -a command with these values, I get same error.
    There is no output under ‘/up’ but there is some output under ‘/packer_recv’ but not the correct one.
    Can you tell me what is the difference between
    lora/+/up & lora/+/packet_recv?

    January 5, 2017 at 3:35 am in reply to: Class B mDot firmware support #16215
    piyush s
    Participant

    Hello

    Can we have an update on this query ?

    thanks,

    January 4, 2017 at 12:20 am in reply to: Class B mDot firmware support #16196
    piyush s
    Participant

    Appreciate the quick response Jason.

    I confirmed the functionality of class C though. But I couldn’t understand the meaning of “Class B definition is not complete in LoRaWAN until 1.1”.
    Please confirm the below:

    The class B isn’t supported in firmware v 2.0.16 Is this the correct statement?
    If it is so, when do we expect the class B supported firmware? How soon can that be available?
    Do you mean that the exact definition of class B isn’t even complete in the protocol itself?

    thanks,

  • Author
    Posts
Viewing 13 posts - 1 through 13 (of 13 total)