NE50-868 minimum time period between two telemetry command.

10 thoughts on “NE50-868 minimum time period between two telemetry command.”

  1. Dear SIr,

     

    Our customer are using with NE50-868 module in one of the project.  When they are sending data from one device to onother device after 500ms duration, They are receiving same data as they are sending data.  

    data sent from cordnitor to E3 device    eE3HELLO DEAR<CR>     Transmitted data

    Normal
    0

    false
    false
    false

    EN-US
    X-NONE
    X-NONE

    MicrosoftInternetExplorer4

    data received by  E3 device                      eE3HELLO DEAR<CR>      Received data

     

    If we are sending data after 1000ms they we are receiving proper data. 

     ata sent from cordnitor to E3 device    eE3HELLO DEAR<CR>     Transmitted data

     

    data received by  E3 device                      eyyHELLO DEAR<CR>      Received data

     

    Can you explane, What is the minimum time period between two telemetry command.

     

    We have set serial time out 100ms.

     

     

    Regards,

    Diwakar Singh

     


     

    1. Hi 

      in Tx there is not timeout problem, important is to respect buffer size (to avoid lost data-buffer=256 bytes)

      In RX there is serial time out (it is configurable to 2mS as minimum value)

      Kindly could you give me all modules setting?

      do the modules have the same FW version? (which version?)

      1. Normal
        0

        false
        false
        false

        EN-US
        X-NONE
        X-NONE

        MicrosoftInternetExplorer4

        Dear Mr. Cosmin Buhu,

         

        Kindly find attached NE50-868 module initialization command.Customer are sending 110 75 byte in single transmittion.

         

        Module f/w is GC.M0A.03.174
         

        Let me know your suggestion.

        1. Hi

          so you are sending 11075 bytes in a single transmission

          I suppose the problem is due to packet size. 

          are you using flow control? ( without it, module buffer size is 256 bytes)

          I suggest to fragment the data to send or keep a timeout between transmission higher than 100mS.

          1. Dear Sir,

             

            Sorry for typing error.

            We are sending only 75 byte in single transmittion.

             

             

            Diwakar

             

          2. Hi,

            ok, I tested the same your issue and I saw that 0,3 sec is a right setting to get the correct message on ED.

            Is it a good timeout?

            Just a little updated.

            I used 3.17 FW version, are you using the same SW for both modules?

            Thanks

             


             

          3. Dear Sir,

             

            How many time you have tested it with 300ms duration. What
            is the failure rate?

            Is it possible to reduce this time?

             

             

             

            Regards,

            Diwakar Singh

          4. Dear Sir,

             

            Do we have any methods for power consumption calculation of NE50-868 module.

            Our client want to use NE50-868 module in battery (non-chargeable)  operated sensors, Where power consumption major factor. The sensors should run one year with single battery.   

             

             

             

            Regards,

            Diwakar Singh

             

          5. Hi,

            we have an excel file.

            it is in order to have an idea about power consumption.

            Maybe it can help you.