开云体育

I HAVE THE SAME THING. NO TRACE, ONLY A BLACK STRAIT LINE AT 0 DBm

On Mon, Sep 21, 2020 at 10:23 AM, Erik Kaashoek wrote: Yes. It will only possible to set the minimum number of gridlines. [No problem.? I'll get used to it.] I guess the "20MHz/" at the center bottom

Please post a screenshot

Hi all,? I downloaded this app but am unable to get it to show a valid trace from the device. Are there any settings I should be changing to have it read? All it does is give a black solid trace at

Thanks Cathy, I'm sure the spectrum analyzer branch of NanoVNA-App is in capable hands with Erik.? Also, good to know he has your ear if the things get muddled. - Herb

Just received my tinySA - it's on charge at the moment. A new noise has showed it's ugly head a few weeks ago at my QTH. A wide pulsing burst occurring about every 1-2 seconds at S7 !! And swamps?

What now needs to happen Herb is for Erik to take all the code and create a new separate TinySA-App branch as I don't want to go any further into changing my program into a spectrum analyser program.

Hi Walt, welcome! Its a big step from a 141 to a tinySA, you will miss the narrow RBW filters but at least the tinySA has a stable LO. Don't drop it inside one of the Hallicrafters, you will never

Yes. It will only possible to set the minimum number of gridlines. I guess the "20MHz/" at the center bottom is OK? There is at least one other thing I want to add to the config part, an option to

Good morning group, I got my tinySA three days ago. I have downloaded tinysa.exe and paired my tinySA to a TAB PRO S tablet. I was guided to this site in a discussion about the tiny on another site. I

Erik, No rush to respond as I know you are on travel.? With V1.0-86 Changes: specifically the increase in minimum number of frequency grid lines to be shown, the variable horizontal grid line spacing

The marker placement issue happens when the total scanned points is large than the amount of pixels in the graph As I am traveling the coming days updating will be slow

Erik, I just tried Cathy's latest main NanoVNA-App branch, which adds your changes for communication with the tinySA, and it does not have the marker placement issue.? You might want to merge her

Erik, Correction per your notes to me: [2] = MSB(measured value) binary format Should be: [2] = LSB(measured value) binary format LSB and MSB are 16-bit values. - Herb

yeah all done now thanks for your reply

Hi Bill, Thanks for your reply. Hello from across the pond. Our daughter in law and son live here in Manchester UK. She is American and hopes, COVID willing, to visit her mother in Kansa City over

Thanks! I may have missed some of your changes in capitalization. scanraw returns a stream of bytes [0] = '{' [1] = 'x' [2] = MSB(measured value) binary format [3] = MSB(measured value) binary format

Hi Eirk I'm just adding the changes you've made into my code (with some changes). Just a word of caution, C and C++ is 99% case sensitive (100% in some cases), so you need to be very careful of that.

Not sure what you mean with "not correct". * Not the same as set in the tinySA? * The frequency of the markers displayed in tinySA.exe is wrong? I do suggest you use nanoVNA-app.exe as found at

I have reported a small bug regarding the PC version of tinySA.exe using GitHub. ?The bug has to with markers not displaying the correct frequency. Is there support for this program or it is now