Post Go back to editing

ADRV9002 - Hopping table updating time

Hi all,

As I know, we are able to update hopping table B when table A is in use by real-time processing mode, is it correct?

How about the action mode above the condition? It updates one frequency by one frequency or updating 64 frequencies at once?

And how long about the updating time for 64 frequencies of one table or one frequency?

Best Regards

Top Replies

  • Hi, 

    Thanks for your questions, please find below some answers for you.

    As I know, we are able to update hopping table B when table A is in use by real-time processing mode, is it c

    This is correct. There are examples of this in our User Guide under the Frequency Hopping > Frequency Hopping Table Modes > Frequency Hopping Table Real-Time Process section.

    How about the action mode above the condition?

    I'm afraid I don't understand the question. Could you explain a bit more?

    It updates one frequency by one frequency or updating 64 frequencies at once?

    All frequencies are to be loaded at once. You must ensure it's fully loaded before you switch.

    And how long about the updating time for 64 frequencies of one table or one frequency?

    Unfortunately, I'm not able to provide this information to you. This is currently being characterized. I will update this thread when I have more information on that.

    Best Regards,

    Conrad

  • Thanks for your response.

    How about the action mode above the condition?

     →Sorry I didn't describe clearly, in here I want to know about the difference of two modes action while hopping table updating? 

    All frequencies are to be loaded at once. You must ensure it's fully loaded before you switch.

    How could I know the time about frequencies update fully? 

    Best Regards

  • The main difference between pre-processing mode and real-time processing mode is that in pre processing mode, all hop information is pre-defined where in real-time processing mode, information can be provided during the hopping process. This means that you can update the hop tables while hoping.

    When you call the API to load a hop table, it will return a code indicating success (ADI_COMMON_ACT_NO_ACTION). Once this has been returned, you can safely switch tables. You may want to time this on your own system.