开云体育

Thanks, Rebel for a summary of all of these so-called "standards"!
--

Variant.

So many standard designs.

Reg

From what I understand the TinySA uses a SI4432 chip that has all the digital filtering options built-in (from around 2.6 kHz. to over 600 kHz.)

So there is not much that can be done in terms of changing how RBW works for this product.

Roger

Probably $$

One reason - PCB mount BNC connectors have a big footprint and are considerably larger? That means a bigger case.

Another one is that people tend to use bigger cables like RG58 with BNC connectors.? That would put more stress on a PCB mounted BNC.? Yes you could use a BNC with a coaxial cable and something like a u.FL to attach it to the board but that is more cost.? Then you have to mount it to a bigger case with nuts.? More assembly and a greater cost.?

So... SMA is lower cost and you can use a low cost plastic case.? Easy to replace too if you know how to solder.?

Roger

It is true that in some cases the orientation of the USB-C cable CAN make a difference.? I have a cheapo Chinese voltage/current meter that specifically states in the instructions to flip over the USB-C connector if it doesn't operate as expected!

At present, the tinySA has SMA connectors. ?The tinySA maximum frequency is less than 1 gig. ?SMA is somewhat delicate; we read only connect with a torque wrench - don't over tighten - make sure they are alined properly ... ?We've read that the connectors have broken off for whatever reason ...

I almost always connect my tinySA (and nanoVNA) to BNC connectors, do my calibrations and then do whatever I originally was wanting to do. ?I'm told BNC are sufficient to a few Gig after which you need SMA or N connections.

Why not ship the tinySA (and the nanoVNA) with BNC connectors?

Hopping not to be hammered into the ground, ? ? ? ? ?larry

Or so one would think...

https://www.theverge.com/tldr/2021/3/22/22344978/usb-c-ports-gadget-pim-de-groot-cursed-plug-reversible

Thanks for the responses guys!

I was not aware that USB-C connectors differ from Micro-USB connectors. From what I can determine, the TinySA does utilize a USB-C connector but many of my other devices (including my NanoVNA SAA-2) use a Micro-USB connector. I guess that I am a little bit smarter than I was yesterday. I will order a longer USB-C cable for my TinySA.

As it didn't seem anyone understood what I wrote last, I started work on a tutorial to explain only to realized it already existed:



if you have data which matches either the time or the frequency display, you are doing the transform in the time domain. To get rid of the side lobes pick a time domain window function that suits you. There is no justification other than lack of memory for not offering all of them plus user defined. You just need room for the tables.

BTW On a log scale sinc**2 doesn't look as attractive as it does on a linear scale. Sorry about that. I'm not as habituated to the log domain as are EEs.

Have Fun!
Reg

News to me,

Both original TinySA's I have feature standard USB-C connectors.

I never had any problems using a standard USB- C cable of any length. Just make sure you don't buy one of the Chinese charging only cables and you should be fine.

John

Looks like I had forgotten to use the "clearconfig 1234" command. Once this was done, the battery voltage is now working as expected on firmware v1.3-317.
After re-loading the firmware, I did a self test (all passed), and Level calibration. All appears to be working good now.

Agreed. Patience is important.

They seem to have no poll for wanted features for the larger (e.g. 4.3 inch) version. For example, I would like to see it have buttons, to replace the poor quality jogwheel.? For example, for the NanoVNA-F, they released both a wheel version and a newer button version (I use the latter).

As most of you already know, the supplied USB cable for the TinySA does not terminate in a standard USB-C connector at the TinySA end. I am interested in ordering a longer spare cable and was wondering what cable type to look for.

Any? help would be appreciated!

Thanks!
--

Hi Rudi, I will try the clearconfig command and report back...

On Fri, Aug 27, 2021 at 01:34 AM, Lane Wilson wrote:

There appears to be a problem with the latest firmware release v1.3-317 !

Hello Lane,
I am using firmware v1.3-317 and the battery voltage shows 4.27 V,
see tinySA_v1.3-317_Batter-4.27V.jpg.

Question: Did you "CLEAR CONFIG" after the firmware update?
Menu->CONFIG->EXPERT CONFIG->MORE->MORE->CLEAR CONFIG, enter 1234

73, Rudi DL5FA

I've been around computers long enough that I just know to try right-click when trying out software. As a former IBM OS/2 user right-click and I were good friends since long before Microsoft realized there was a right button....

73

-Jim
NU0C

On Fri, 27 Aug 2021 08:41:52 -0700
"Terry Perdue" <K8tp@...> wrote:

Oh, cool! How would anyone know to right-click the grid? Is there a Help
file somewhere?

On 8/26/2021 10:24 PM, Ted Chesley wrote:

Hi Terry, THX for the reply on the drivers, I remember I had to do that once. That info might help out someone with the same problem.

As to the TinySA interface with the TinySA-app, when connected, clicking on the four arrows next to the freq setting will set the application to agree with the TinySA, the start/stop freq , data points etc, but not the grid. You have to right click on the grid and enter the desired MIN/MAX settings with the manual set. The auto set can be used when there is a waveform in the screen.

Happy Hunting….Ted (KD7AQO)

On Aug 26, 2021, at 8:46 PM, Terry Perdue <K8tp@...> wrote:

?That’s precisely what I found out the hard way today.

On Aug 26, 2021, at 8:11 PM, Jim Shorney <jshorney@...> wrote:

?
The thing that seems to bite a lot of people is that the Tiny/Nano gadgets are different device when in DFU mode and need a different driver. When connected to the computer in DFU mode you should see a "STM Device in DFU Mode" device appear in your USB tree under Device Manager. This driver is part of the DfuSe_Demo package but is not installed automatically. You have to hunt it down in the DfuSe folders and install it manually if it is not showing up. I've been told that it is needed for the app to upload firmware but I can't say because I already had it installed before the app came around.

73

-Jim
NU0C

On Wed, 25 Aug 2021 20:45:07 -0700
"Terry Perdue" <K8tp@...> wrote:

I'm not sure I understand that, but I should mention that I see that
when using the tinySA app, it /automatically /puts the device in DFU
mode. That works. But as you can see, it appears to be unable to 'open'
the device to write the file to it. I've tried many times.

On 8/25/2021 8:04 PM, Ted Chesley wrote:
Hey Terry, also forgot to add: you must be connected to the TinySA app
before you can use the upgrade. I think that's the case but I haven't
tried it before connection.

-----------------------------------------

From: "Terry Perdue"
To: [email protected]
Cc:
Sent: Wednesday August 25 2021 7:05:52PM
Subject: Re: [tinysa] Can't update firmware

? I don’t see anything in the upgrade document about renaming any
file. Can you elaborate?

On Aug 25, 2021, at 5:08 PM, Larry Acklin <acklin@...> wrote:

?
I had the same issues. I used dfu-util, a bit of a PITA but
figured it out. You need to follow the how to and also rename the
file to what the batch file expects. It’s a DOS based process but
mine is running latest and works- passes self test and Cal.

And Windows 10 needed to recognize the tinySA as a usb device-
running zadig helped get it recognized.


Good Luck
Larry
KB3CUF

On Wed, Aug 25, 2021 at 7:25 PM <K8tp@...> wrote:

I've downloaded dfusedemo, version 3.0.6. With it running, I
connect the TinySA and put it in DFU mode, but the application
doesn't find it. If it's any help, when I enter DFU mode I get
the 'USB disconnect' sound.

I've viewed a couple of YouTube videos, and can't figure out
what I could be doing wrong. Also, if I click CHOOSE and
select the new .DFU file, the application reports that the
file doesn't have the correct format. Seems I have two
different issues.