Thankyou for taking the time to try it out. I am surprised there is not more variation in amplitude of different signals, but it does depend on the time of day. It also looks as if it would work without the LNA. I would be interested in using it as a bandscope when operating a military backpack radio (Clansman 320) which is a pain to tune across the band. It was intended for use on prearranged frequencies which were changed every day.

However, at least the LNA is a sacrificial protection in case you press transmit without disconnecting the Tinysa first! Even leaving it connected but switched off overnight could smoke it as a half size G5RV is big enoug to acquire quite a lot if static in inclement weather.

Steve L G7PSZ

Some people want to know if it is possible to use the tinySA as a kind of band scope.
Using the LNA as explained on the wiki and a half size G5RV I get this

开云体育

On 9/12/20 1:14 PM, dekagon wrote:

thank you. Found the typo in sa_core.c at line 20 :)
Now it compiled to the .elf file...

???? I figured out a week or so ago that Erik was doing all his firmware in Windows, when I found that it wouldn't compile in Linux Mint.? Windows isn't case sensitive, Linux is.

All the TinySA tests now run properly when HI and LOW are connected via the jumper cable ...
--
73, Bernie, VE3FWF
(most typos in this message were generated by highly sophisticated auto-correction software)

Short answer, the repository has been deleted.

73, Stay Safe,

Robin, G8DQX

I did not know that I needed to connect HI and LOW together.?

Newbie problem, for sure. ?Read The ?F... Manual, Bernie!
--
73, Bernie, VE3FWF
(most typos in this message were generated by highly sophisticated auto-correction software)

Sorry for the confusion. ?

I meant to display an FM broadcast station and see the modulation - not actually hear the audio!


--
73, Bernie, VE3FWF
(most typos in this message were generated by highly sophisticated auto-correction software)

On Sun, Sep 13, 2020 at 03:25 PM, Robert Entwistle wrote:

Self-test failures aside, I'd love to know how to decode FM band using the tinySA!? Any tips and/or info you could share?
================================================

Robert,?
? Before you get too excited, I believe by decode Bernie meant that he can display the FM band on the low input.? The tinySA does not have a demodulated output.

? I'd love to be wrong though.

?- Herb

On Sun, Sep 13, 2020 at 03:01 PM, Ham Radio wrote:

I have self test failures 3,4,7,10 ?out-of-the-box — unit was purchased in June, 2020

The tinySa can decode the FM band nicely in LO band but I can not get the USB port to stay up in DFU mode.

30 MHz calibration signal from HP141 looks good.

Bad hardware? Bad config?

Bernie,
? The DFU mode is a special mode that allows the STM driver to flash the firmware to the tinySA.? In the DFU mode the tinySA is no longer recognized as a USB CDC device.? It is normal that you have to cycle power on the tinySA after flashing the firmware to exit DFU mode and go back to the normal CDC virtual com port operating mode.

? I'm not sure what's going on with with the self test errors.? Self test is run with the high and low ports connected together.? A -25dBm calibration signal is output from the high port is used for during self-testing of the low port.? Not a lot can go wrong unless the calibration signal level is off (earlier firmware had that issue) or the connection between the low and high port is faulty.

?1. I would first check to ensure the latest firmware is installed, 1.0-82 will be displayed in the tinSA status pane if you have installed the latest update.
?2. If the latest firmware is installed and you still have selftest errors, then I would use the second sma cable to run the selftest.? If swapping cables solves the problem then you have a bad cable.
?3. If neither of the above work, then Erik can guide you through further troubleshooting.

?Erik is in a different time zone so it will be a few hours before he reads your post.
?
- Herb
??

2020-09-11 08:58

105K

?

Hi Bernie,

Self-test failures aside, I'd love to know how to decode FM band using the tinySA!? Any tips and/or info you could share?

73,

Robert, WA2T

I have self test failures 3,4,7,10 ?out-of-the-box — unit was purchased in June, 2020

The tinySa can decode the FM band nicely in LO band but I can not get the USB port to stay up in DFU mode.

30 MHz calibration signal from HP141 looks good.

Bad hardware? Bad config?

--
73, Bernie, VE3FWF
(most typos in this message were generated by highly sophisticated auto-correction software)

From a couple of days I'm getting error 404 when trying to access OneOfEleven repositories for the nanoVNA programs.?? Have they been moved or deleted?

Regards,
Ignacio EB4APL

--
El software de antivirus Avast ha analizado este correo electrónico en busca de virus.

A short video explaining the Marker Menu and how to position the markers

Erik,
Thanks for all your efforts with the videos, they are extremely helpful. Between your videos and the ones by Imsai Guy its been a blast/

--
73 de k1jbd
bammi

It's there, you just have to hover over the word "video" in your original post to see it and click it to go to it. I think if you just paste the link in the text without using the link button most stuff will pick it up as a url just fine. Like:??(no link button used to create this even in the groups.io editor)

I spoke with them by phone a couple of days ago.? They placed an order for 200 and got about 20 in... more to follow.? They have orders to use all the next expected shipment.? Your best bet is to place the order and get in line.? It may be a while.? Not sure if they will bill the card when the order is place or when it ships.

Erik,
thank you. Found the typo in sa_core.c at line 20 :)
Now it compiled to the .elf file...

Chris

There is probably a typo in the source file
Upper,lowercase probably?
Try changing to si4432.h

Hi Erik,
do you have some tips for building the tinySA Firmware by myself under Kubuntu LTS 20.04?
I prepared everything as described under thwec readme in your github.com/erikkaashoek/tinySA/readme.md file...
But after running make I got the following error:
...
Compiling nvic.c
Compiling hal_lld.c
Compiling stm32_dma.c
Compiling hal_st_lld.c
Compiling hal_adc_lld.c
Compiling hal_dac_lld.c
Compiling hal_ext_lld.c
Compiling hal_ext_lld_isr.c
Compiling hal_pal_lld.c
Compiling hal_spi_lld.c
Compiling hal_gpt_lld.c
Compiling hal_usb_lld.c
In file included from ChibiOS/os/rt/include/ch.h:82,
???????????????? from ChibiOS/os/hal/osal/rt/osal.h:32,
???????????????? from ChibiOS/os/hal/include/hal.h:28,
???????????????? from ChibiOS/os/hal/ports/STM32/LLD/USBv1/hal_usb_lld.c:27:
ChibiOS/os/hal/ports/STM32/LLD/USBv1/hal_usb_lld.c: In function 'usb_lld_init_endpoint':
ChibiOS/os/rt/include/chdebug.h:129:6: warning: this statement may fall through [-Wimplicit-fallthrough=]
?? if (CH_DBG_ENABLE_ASSERTS != FALSE) {???????????????????????????????????? \
????? ^
ChibiOS/os/hal/osal/rt/osal.h:241:34: note: in expansion of macro 'chDbgAssert'
?#define osalDbgAssert(c, remark) chDbgAssert(c, remark)
????????????????????????????????? ^~~~~~~~~~~
ChibiOS/os/hal/ports/STM32/LLD/USBv1/hal_usb_lld.c:588:5: note: in expansion of macro 'osalDbgAssert'
???? osalDbgAssert(false, "isochronous support disabled");
???? ^~~~~~~~~~~~~
ChibiOS/os/hal/ports/STM32/LLD/USBv1/hal_usb_lld.c:590:3: note: here
?? case USB_EP_MODE_TYPE_BULK:
?? ^~~~
Compiling board.c
Compiling chprintf.c
Compiling memstreams.c
Compiling nullstreams.c
Compiling usbcfg.c
Compiling main.c
In file included from main.c:934:
sa_core.c:20:10: fatal error: SI4432.h: No such file or directory
?#include "SI4432.h"? // comment out for simulation
????????? ^~~~~~~~~~
compilation terminated.
make: *** [ChibiOS/os/common/startup/ARMCMx/compilers/GCC/rules.mk:216: build/obj/main.o] Fehler 1

Thank you in advance for your help.

Chris