开云体育

On Fri, Sep 4, 2020 at 11:35 AM, OneOfEleven wrote:

Hi Erik

I was just wondering what the coax is you use on the short coax patch leads you include with each TinySA you sell, but more so what the velocity factor is ?

I like your patch leads as they are extremely flexible, and just wanted to confirm the measured velocity factor (with the NanoVNA) with the actual velocity factor, but don't know what coax type you use.

Cathy,
? They are the black RG-174 cables included with all hugen's products spec'd? up to 1GHz.? The NanoVNA-H4 is supplied with? high quality beige?RG-316 cables, and the V2 is delivered with even higher quality blue ss-401 cables.

?The velocity factor for the RG-174 cable is 0.66.

?-Herb

They are RG174 PE cables

Hi Erik

I was just wondering what the coax is you use on the short coax patch leads you include with each TinySA you sell, but more so what the velocity factor is ?

I like your patch leads as they are extremely flexible, and just wanted to confirm the measured velocity factor (with the NanoVNA) with the actual velocity factor, but don't know what coax type you use.

Cathy

On Fri, Sep 4, 2020 at 09:26 AM, hwalker wrote:

The output mode, of course.? It doesn't get the attention it should.

IMSAIGuy made a video about output mode. Sometimes you need some help to pay attention

On Fri, Sep 4, 2020 at 07:59 AM, Erik Kaashoek wrote:

Euh, a portable FM/AM (SW) radio?
It's about the output mode
LIstening on the tinySA to demodulated AM is not (yet) possible

The output mode, of course.? It doesn't get the attention it should.

- Herb

Euh, a portable FM/AM (SW) radio?
It's about the output mode
LIstening on the tinySA to demodulated AM is not (yet) possible

On Fri, Sep 4, 2020 at 07:19 AM, Erik Kaashoek wrote:

New FW released
Version V1.0-69

Changes:
- Removed the modulation interruption causing a rather unpleasant sound

During one of the recent code changes a bug was introduced that caused the modulation to be interrupt a couple of times per second which made the modulation rather unpleasant to listen to.

Erik,
? That raises the question of where is the audio output you were listening at?

?- Herb

New FW released
Version V1.0-69

Changes:
- Removed the modulation interruption causing a rather unpleasant sound

During one of the recent code changes a bug was introduced that caused the modulation to be interrupt a couple of times per second which made the modulation rather unpleasant to listen to.

On Fri, Sep 4, 2020 at 05:25 AM, hwalker wrote:

1. The new build is showing up in the status panel and version screen as 1.0-66.? The version screen shows the correct build date.?

Argh... Forgot to clean the project before building

2. If an actual signal is measured that is in the spur avoidance table, does avoidance get cancelled if the level is above a predetermined level for the spur?

The avoidance algorithm knows when certain combinations of internal frequencies can lead to spurs and choses alternate combination to avoid the otherwise substantial spur. This mechanism is totally transparent and has (should have) no impact on the measurement performance. So it does NOT mask small signals at certain frequencies. It avoid spurs are created.

3. I assume the MCU clock related signals are not considered spurs as I didn't see any change from the previous version.

Indeed, no real signal are impacted in any way, so also not the MCU related signals.

On Fri, Sep 4, 2020 at 04:06 AM, Erik Kaashoek wrote:

New FW release
Version v1.0-67

Changes:
- Updated spur avoidance table

After receiving some feedback about possible spurs I made an update of the spur avoidance table
This update could make the scanning a little bit slower.

1. The new build is showing up in the status panel and version screen as 1.0-66.? The version screen shows the correct build date.?

2. If an actual signal is measured that is in the spur avoidance table, does avoidance get cancelled if the level is above a predetermined level for the spur?

3. I assume the MCU clock related signals are not considered spurs as I didn't see any change from the previous version.

- Herb

New FW release
Version v1.0-67

Changes:
- Updated spur avoidance table

After receiving some feedback about possible spurs I made an update of the spur avoidance table
This update could make the scanning a little bit slower.

The tinySA has a table containing compensation for each of the 57 possible RBW filters

Erik,
? Did you read the following post on the HBTE group?
/g/HBTE/message/1551

? Have you performed a similar test on the tinySA? If so did you come to the same conclusion as the poster?

- Herb

The is an exe call tinySA.exe (see the wiki), no need to install, download and run.
And there is tinySA-saver, which is just a bunch of python files, no exe and no install when you already have nanoVNA-saver running on your PC

Sorry to show my ignorance (or just poor memory). I've just got my SA and updated the firmware and now want to install SA-Saver on my PC. I've already got nanoVNA running on the PC but I've forgotten how I installed nanoVNA Saver in those distant days before Covid.

I've downloaded the SA Saver source code files to my PC (Win10) but can't work out how to get an installation; thought I was supposed to be looking for a exe file according to Eric's Github site?? Maybe I missed the exe file somewhere?

I don't understand the instructions there but then I'm not really a software geek! Some plain English explanation would be helpful please?

regards

Nigel G8AYM

A very good product, one that I will grab on a regular basis. When I get back to normal ( ie access to my electronics den) I will fabricate a system to use an external lna for interference (qrm) tracing.

Another possible use may be sniffing/ monitoring my ( rare) transmissions. For this I think it would have to be in a metal box ( the plastic case may allow too much rf into the circuitry and at the worst, damage it) with a short on the unused sma and attenuator on the one being used with a “sniffing” aerial.

Few Radio Amateurs realise or know how much rf they spew out on other frequencies, near and far ( perhaps until a neighbour bangs on the door). At present I am using a Clansman 320 backpack radio, which should be quite clean. It will be interesting to see, and a good exercise to ensure that the intended output is not affecting the Tinysa and causing artifact spikes everywhere.

Steve L. G7PSZ

Thanks,? I added a hint to the wiki

Erik,
You may want to add a link to the follow-up video on the Wiki, as well as comment back to the HACKADAY sight, as reading the review as posted put the TinySA in a do not buy light.? That is far from the case as those of us that have had the hands-on experience can attest.? I did post a reply pointing out the follow-up video, but it is far down the list of comments.? Most will not see it, and not sure that the author will review and update the article.

A very good product in my opinion. One that I have been searching for in the last 2 years, and much better than other devices when coupled to the PC.

Good Job!??
Wishing you much success.
73
Evan
AC9TU

The mistakes he made in his first video where very helpful for me to understand how to make the tinySA more robust in the hands of an inexperienced user.
Once the additional attenuation was used when measuring AM and FSK modulation the tinySA performed surprisingly well against the HP, of course it could not match the 1kHz RBW but dynamic range and IIP3 where not worse.

Interesting. I also watched his follow up video with the comparison against an HP8921A which I found priced at ~$5k so the comparison of a $50 item against a$5000 piece of lab equipment seems a bit unfair it does you you an idea of what you can do with a tinySA compared to expensive lab equipment.
--
John Smyder - W5JWS