Post Go back to editing

TES software, changed carrier frequencies on my profile but the created json and stream image are the same as they were before

Thread Summary

The user encountered a 2.3 GHz carrier frequency instead of the expected 4 GHz when using TES to create a 1Rx, 1Tx, FDD profile. The final answer indicates that the LO frequency must be manually set, as it is not included in the profile or stream image files. The default carrier frequency in TES is 900 MHz, while the non-OS setup might default to 2.3 GHz. The user should use the API to set the carrier frequency after initialization. Relevant products: ADRV9001, TES, zcu102 example code.
AI Generated Content
Category: Software
Product Number: ADRV9002
Software Version: Transceiver Evaluation Software 0.28.0

Hello,

I used the TES to create a 1Rx, 1Tx, FDD profile with carrier frequencies at 4 GHz. I was able to run the headless.c file from the zcu102 example on my custom hardware, and get past initialization, and actually see the device transmit and receive, however the tone I saw was at 2.3 GHz. Then as I debugged some of the zcu102 example code, I saw where if a "c->carrier" wasn't set, it would default the carrier to 2.3 GHz ? Looking back at my profile, I didn't see anything about carrier frequency. Then as a test, I changed the carriers to something else in the TES, created a new json and new stream image, and compared them to my previous ones and they are the exact same.  So does that mean that the json/stream image do not set an initial carrier frequency? Why does the no-os C code have a default value of 2.3 GHz? Is it expecting me to use the API to change the carrier after initialization?

These are the version numbers from the changelog in the TES download.

### TES components
- FPGA image 8.3.23
- Device Driver API 68.16.2
- Device Driver Client 68.16.2
- Firmware 0.22.49
- Profile Generator 53.11.0
- Stream Generator 0.7.15
- Transceiver Evaluation Software 0.28.0
- ADRV9001 Plugin 0.28.0

Thanks,

Allen 

Thread Notes