LE910-NA1 Tx Pwr reporting

5 thoughts on “LE910-NA1 Tx Pwr reporting

  1. Hi,

    I would like to read the Tx power level from the modem module (LE910-NA1). Base on the AT command guide, there is a AT command (AT#RFSTS) that will report the . However, when I type it in, the command always reports TXPwr of 0.

    The document indicates that it’s for “In traffic only”. I am wondering what that means? I tried to set up a data call and issue the RFSTS and I still get 0 for TxPwr.

    What do I need to do to enable the TxPwr reporting?

    Thanks

    Augustine

    1. Response that I got from the module:

      #RFSTS: “302 610″,925,-113,-77,-15.0,2bdc,FF,0,0,19,1,”1BA2B2A”,”302610016730170″,”Bell”,3,2

    2. Hi Augustine,

      Can you please confirm that you are usng the firmware release of 20.00.522 on your LE910-NA1?  The note of “In traffic only” for the TXPWR parameter relates to that parameter will only be present/populated during an active transmission of data (traffic).  Your result from the #RFSTS command shows that the module is Idle (19) by looking at the MM parameter.  I would expect the MM value to be a 6 or 21 before you would see the TXPWR parameter populate, since that would be an indication that your connection is active.

      Please contact TS-Americas@telit.com if you need to get the latest approved firmware release for the LE910-NA1.

      Regards,
      Matthew

      1. Hi Matthew,

        Thanks for your response. I am using the 20.00.522 firmware. 

        A data connection was set up and I was doing a ping test at the background when I send the RFSTS command.  Do you think that’s sufficicent for the RFSTS to report the TxPwr?

        If not, can you suggest a better test setup?

        Thanks

        Augustine

        1. Hi Augustine,

          I would recommend doing a test that could take longer on the transmit side to complete, maybe an upload of a file via a FTP or PPP connection.  From my short testing I am seeing the same results when doing Ping tests, I have not been able to catch the MM parameter to be an 6 or 21 during Ping testing.

          Regards,
          Matthew