FARRUKH

Forum Replies Created

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • in reply to: Point to Point #17351
    FARRUKH
    Participant

    after you type AT+SD,
    whatever you type, it is received on connected radio modules.
    I’ve tested and it works.

    in reply to: mDot data transmission constraints #16543
    FARRUKH
    Participant

    I’m using mDot 868, Serial Data mode, 0.25kbps data rate.
    Channel selection is automatic while using serial mode, right?
    I’m still unable to locate issue, one mDot sends packet to other, and other one replies back, whole process taking four seconds, packet is always sent after about two seconds of writing it from COM port at 9600 baud. There may be some timeout parameter that isn’t mentioned in AT command manual.

    in reply to: Peer To Peer mode #16403
    FARRUKH
    Participant

    i used the node id. Each mdot has its own node id of 8 bytes (see the label). this ID is located into the flash.

    But that will require handling all packets in user-application layer, Peer to Peer network not necessarily means BROADCASTING each and every packet, I’m not getting why addressing individual nodes at hardware-level is missing.

    in reply to: Peer To Peer mode #16387
    FARRUKH
    Participant

    You have three dots addressed as 1, 2, 3

    for 2 to send to 1

    AT+NA=1
    AT+SEND=DATA
    AT+NA=2

    I understand that, three are mentioned for example only, in field, there will be many mDots,
    I’ve to program same firmware for all slaves, so all slave mDots must have same NA, and other issue is, when each slave will be powered up, it will send a status message to master, slave must have same NA otherwise master will never receive message.

    in reply to: Peer To Peer mode #16385
    FARRUKH
    Participant

    i am developing hybrid system (canbus and rf in peer to peer) and i used one master (display) and up to 4 slaves (RF sensors). I use a my specific protocol. My master knows each address of each sensor. And i have my own ack (ex. 0xAA, ID low, ID high, CS).

    Right sir, that simply means there is no way to send Unicast messages, I have one master and around ten or even more slaves, all have same mDot, so is no option for slave to send unicast message destined for master, is troublesome, I’ve used low cost cc1101 chip before, that supports address field also.

    in reply to: Peer To Peer mode #16383
    FARRUKH
    Participant

    AT+NA (Network Address) can be different on each device.
    Set the AT+NSK and AT+DSK to the same values.

    Then only AT+NA needs to be changed to address a specific dot.

    NA is for network address, how two mDots can communicate with each other if set different NA?

    in reply to: Peer To Peer mode #16377
    FARRUKH
    Participant

    Can you please check which AT command to use for configuring mDot’s address? I’m unable to find any in AT command manual.

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