¿ªÔÆÌåÓý

  1. Tinysa
  2. Topics

TinySA App CSV 10 dB difference #WindowsAPP #csv #software #tinysa

 

Hi everyone. I got a TinySA and I've been learning how to use the scans from the Windows App for coordinating wireless mics frequencies. A few days ago, I found out there is a difference of aproximately 10 dB when showing the same scan on the TinySA app and the mics coordinating app (WWB). Also, I've compared my tinySA scans with some others I made with a Shure Rx (QLXD4 model) and when importing onto WWB the TinySA ones are 10 dB lower. Is there something I am missing? Should I enter the dB difference as level gain so the noise floor matches between scans? What would you recommend in this situation?
My TinySA is calibrated as suggested in the web page (low input calibration with both sma connected with one cable) and the high port has been matched with a known frequency in the overlaping region between the High and the calibrated Low port, so it should perform well. Is there some scanning I am missing?
 

It depends on which instrument you trust, and the type of modulation in use.
?
It's difficult to tell from your screen grabs, but WWB seems to have a much higher noise floor, in relation to the peak signal level.
?
What is causing this difference ?
?
Is it the type of detector (peak, average etc.), or differences in bandwidth that are being used by each instrument ?
?
Try experimenting with different settings of TinySA bandwidth, sweep rate and LNA / attenuator values.
?
Regards,
?
Martin
?
On Sun, Sep 29, 2024 at 06:03 AM, <musicfordrumies@...> wrote:

A few days ago, I found out there is a difference of aproximately 10 dB when showing the same scan on the TinySA app and the mics coordinating app (WWB)
 

I'm sorry, here are the full screenshots this time.
I just opened the CSV file and found out that the correct values are in WWB, which means the if the tinySA-App shows a frequency peaking at -58.8dBm, the exported csv says it is peaking at -67.9dBm. Why is it? giving me everything off by almost 10 dB? Do I have a faulty unit?
Just to clarify, I made a scan with the app, saved the csv file and then imported it to WWB.?
 

This is a known bug and last I heard wasn't a priority to fix. I recommend checking out QtTinySA which is an open source python app which appears to export correctly. Cool thing is it's cross platform and works on Mac.?
?
https://github.com/g4ixt/QtTinySA
 

Oh no, so its a bug from the app itself? Would it be fine if I just level all the data up adding the 10dB on the csv file?
I tried the QtTinySA.py but I couldn't connect the SA. I click on browse but it shows me a box and then stops working.
 

Yeah, I believe of you multiply each value by .8686 it should be very close.?
 

Does QtTinySA show the device as being connected at the bottom left?? If not, you should get a message popping up to say it's not connected.? If it is, you should get this screen.? Only .bmp files are displayed, but all can be saved.
?
 

It says No Device No Voltage so I'm guessing it is not connected? Although the Windows App do recognizes it via COM5 port. When I click on File/Browse TinySA, it shows this window:
If I close it, nothing happens. If I click the text or the save button, the app freezes. Do I have to change something on the SA?
 

which version of Windows?
 

I'm on Windows 10 Home
 

could you send a clearer picture or copy/paste the contents of the cmd terminal screen please?

1 - 11 of 11