Rx Channel Filter file format

Hi Henning, 

Uploading a custom channel filter in .txt or .csv format is just a list of the coefficients. You do have to make sure they are 24-bit signed integers.
To generate a file that you can upload to through the GUI, just have a list of comma separated coefficients in your .txt file. 

Regards

The custom filter file I have tried is according to your specificiation (shown on the right side). Is there some additional rules to follow when entering the filter length or amplitude on the coefficients (beyond that they need to be within the limits of 24-bit signed)?

Note that this filter is just an example, and not a realistic filter, merely for the exercise of testing the upload custom filter function.

Regards,

Henning

Hi Henning, 

It is a 128 tap PFIR filter so if you put in less than 128 coefficients it will populate the rest with 0. 

Hi!

Yes, that is what is stated in the documentation, and this is totally acceptable. I have tried to increase the number of taps of this filter to 128, but still experience the same error message thrown by TES GUI.

As mentioned earlier, this is just a bogus-filter, just to verify the input file (csv or txt).

Regards,

Henning

Hi Henning, 

I have attached a sample filter .txt file here. I have tried this with the TES 0.11.0 version and it loads without errors. 
2061.SampleFilter.txt

Hi again!

Thank you for the provided sample file. I see now that the only difference is the horizontal orientation on the comma separated values, and that the TES GUI does not handle the newline character inbetween each sample very well. An example file should be added to the documentation for clarification.

Henning

Hello Henning,

Following your suggestions we have written a user tutorial on EngineerZone detailing how people can design and upload their own PFIR coefficients:
https://ez.analog.com/wide-band-rf-transceivers/tes-gui-software-support-adrv9001-adrv9007/w/documents/15492/loading-rx-pfir-coefficients

I will also make a comment for our Software team to see if this functionality can be made more robust and account for more file formats.

Thanks very much for your continued interest!

Best Regards,
Oisín.