davenakasone / rsa306b_api_applications

Interfaces with the Tektronix RSA306B Spectrum Analyzer to aquire, process, and store signals of interest

Program Concept

• program that can interface with the Tekronix RSA306B Spectrum Analyzer
• partial discharges can be found by scanning a range of 0.5 GHz to 1.5 GHz
• examining IF, IQ, and spectrum data confirms or denys the presence of partial discharges
• field testing allows the user to configure the software to measure signals of interest
• this program is designed to monitor power generation equipment for partial discharges
• major sections: instrument managment, data acquisition, processing, and storage
• use for any application where time domain and frequency domain data is needed [up to 6.2 GHz]

Resources

• this repository : here
• youtube : here
• pictures and video : here
• additional documentation : here

File Structure

rsa306b_api_applications/

ARCHIVED          // work and experiments from the past
stored_program    // where the main program is located

API Information

• API Version : 1.0.0014
• FPGA Version : V2.1
• Firmware Version : V1.7
• Hardware Version : V7
• Nomenclature : RSA306B
• Serial Number : B037150

License

• Contact us for details here

rsa306b_api_applications's Issues

antennas

need to put the E and H field antennas on a vector network analyzer to get the s-parameters
need to find out optimal settings for their use
so far, they don't hit on much, but the bluetooth looks good (-70 dBm on a -110 dBm noise floor?)

if deep-space registers around -90 dBm, I am not sure how much I trust noise floors past -100 dBm

slow upload speeds

the ocamel utility for Ubuntu 20.04 LTS is very slow uploading data from the NUC i7 to google drive

see the spread in the time stamps:
google drive

during this session, the program was running; writing data to the same directory as ocamel worked to upload
there may have been a few race conditions for the mutex/semaphore to the file directory

also, the file sizes were very large, even for < 10ms of data

should try:

1. making a pass to a dedicated directory
2. having a file manager work separate to upload files after writing, then delete them
3. seek alternative solutions to telemeter data

wchar_t

turn it into a std::string or char* as quickly as possible
see the "IQSTREAM" group