Serkan

Forum Replies Created

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • in reply to: mDot Device Class C work flow #15448
    Serkan
    Participant

    Thank you.

    Class C problem solved.

    But you said that “if we send msg without EUI, all devices in same network will receive that message.”

    So, in new msg format i need EUI and Payload . What should i set EUI to send all devices. iş there a format like 00:00:00 or do i need to leave it empty?

    { EUI : "", Payload : "test" }

    and when i debug complete msg object there are lots of fields. Should i use that fields? Channel number, band, timestamp etc.
    i am only interested in Payload and not to giving EUI filtering.

    Best regards

    in reply to: mDot Device Class C work flow #15436
    Serkan
    Participant

    Hi Jason,

    Awesome, same network, all of our devices can receive packets that we sent from server.

    We can check downlink frame counter with AT+DLC. It’s OK for our situation. We don’t need any events or triggers.

    Q1: We are using, Conduit AEP, Node-Red. Devices in admin panel shows Device Class A, but we changed it to device C in mDot, do we need to register again that devices?

    Q2: In Node-Red, Lora Out Node could not send a payload with a function node. In function node we return new { Payload : “test data” } format. But not sent. If we connect Lora in to Lora Out, when we AT+SEND we can get Echo of that message. I need to create proper new MSG format. How can i do it?

    Thank you for fast response.

Viewing 2 posts - 1 through 2 (of 2 total)