开云体育

New FW release Version V1.4197 For all tinySA Ultra and Ultra+ versions Changes: - Added CONFIG/EXPERT CONFIG/MORE/AUDIO AGC option. When disabled the PCB edge point PA4 will in listen mode have a voltage linear with the signal level in dBm Useful for integration of tinySA as selective power meter - Reduced level of internally generated spurs on multiples of 10 MHz not being multiples of 30 MHz (ZS-407 only) -- Designer of the tinySA For more info go to https://tinysa.org/wiki

I've been trying to align some HT's this week. After a lot of messing about I concluded that some of the commonly available "ham"style meters were somewhat variable in quality. So I decided to try using the Tiny SA as a power meter with suitable attenuation and calculations. I *think* that so far this has ended up being more accurate but I'd still like to hear of other folks experiences using this method. As an aside, the sig gen function has been invaluble for setting up squelch levels and determining sensitivity too. I learnt quite a bit by using the sig gen function to set up my Quansheng squelches, there's three squelch service menus, get them wrong and you get a disaster on your hands. (Maybe a topic for another forum!) Whilst doing various tests I was surprised to see that my old Wouxun UVD1 dual bander HT was 6db less sensitive than my Quansheng's. Thank heavens for having a Tiny SA to hand - thanks Erik ! And Murphy's always strikes when using various cheap cables / sma connectors. Oh man, those cheapo SMA's can out of tolerance causing odd losses and not mating properly, grrr ! 73 de Andy

The following items have been updated in the Files area of the [email protected] group. //tinysa-ultra-upgrade.sh By: Rob, W9LOT <rjgebis@...> Description: Debian/Ubuntu Linux and MacOSX (Intel and arm64) shell script to upgrade tinySA Ultra versions firmware # Download to your machine and change permissions cd ~/Downloads/ chmod 750 ./tinysa-ultra-upgrade.sh # Example ./tinysa-ultra-upgrade.sh --program tinySA4_v1.4-196-g1e9c187.bin --erase # Output == Using firmware binary: firmware/tinySA4_v1.4-196-g1e9c187.bin Checking for DFU utilities... ========================================================= Before upgrading, run self test to make sure the device is OK 1. Connect a loop cable between CH0 and CH1 ports 2. Select Config / Self Test ========================================================= Did the self-test succeed? (y/n): y ========================================================= tinySA Ultra 1. Press and hold jog button before switching on the tinySA Ultra 2. Switching on, the screen will stay black ========================================================= Continue with upgrade? (y/n): y Checking for device in DFU mode... == Running lsusb to detect DFU device... Bus 001 Device 013: ID 0483:df11 STMicroelectronics STM32 BOOTLOADER Serial: XXXXXXXXXXXX == Device found in DFU mode. == Programming firmware... It takes around 30 sec == Firmware update completed successfully. ========================================================= Reset & Calibration Connect a loop cable between CH0 and CH1 ports 1. Config / More / Clear Config: 1234 2. Config / Level Cal / Reset Calibration 3. Config / Level Cal / Select Range 4. Config / Self Test # Check tinysa-ultra-upgrade.log for all output

Hello Erick, I was trying to update the both units today with latest tinySA4_v1.4-196-g1e9c187.bin Following your your Firmware Upgrade page I did run $ dfu-util -a 0 -s 0x08000000:leave -D tinySA4_v1.4-196-g1e9c187.bin This produced following output. The bottom output if from my shell script wit reset steps. dfu-util 0.11 Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc. Copyright 2010-2021 Tormod Volden and Stefan Schmidt This program is Free Software and has ABSOLUTELY NO WARRANTY Please report bugs to http://sourceforge.net/p/dfu-util/tickets/ dfu-util: Warning: Invalid DFU suffix signature dfu-util: A valid DFU suffix will be required in a future dfu-util release Opening DFU capable USB device... Device ID 0483:df11 Device DFU version 011a Claiming USB DFU Interface... Setting Alternate Interface #0 ... Determining device status... DFU state(10) = dfuERROR, status(10) = Device's firmware is corrupt. It cannot return to run-time (non-DFU) operations Clearing status Determining device status... DFU state(2) = dfuIDLE, status(0) = No error condition is present DFU mode device DFU version 011a Device returned transfer size 2048 DfuSe interface name: "Internal Flash " Downloading element to address = 0x08000000, size = 186256 Erase [=========================] 100% 186256 bytes Erase done. Download [=========================] 100% 186256 bytes Download done. File downloaded successfully Submitting leave request... Transitioning to dfuMANIFEST state Reset & Calibrarion # Connect a loop cable to CH0 and CH1 # 1. Config / Self Test 2. Config / More / Clear Config: 1234 3. Config / Level Cal / Reset Calibration 4. Config / Level Cal / Select Range 5. Config / Self Test As you see I am running version 0.11 on my MacOS 15.3. The interesting lines are dfu-util: Warning: Invalid DFU suffix signature dfu-util: A valid DFU suffix will be required in a future dfu-util release and DFU state(10) = dfuERROR, status(10) = Device's firmware is corrupt. It cannot return to run-time (non-DFU) operations The first one I fixed by running and when refreshing the first message was gone. $ dfu-suffix -a tinySA4_v1.4-196-g1e9c187.bin -v 0483 -p df11 -d 0100 Then I did try to erase flash by running putting the device back DFU mode $ dfu-util -a 0 -s 0x08000000:mass-erase:force Which produced following output Opening DFU capable USB device... Device ID 0483:df11 Device DFU version 011a Claiming USB DFU Interface... Setting Alternate Interface #0 ... Determining device status... DFU state(10) = dfuERROR, status(10) = Device's firmware is corrupt. It cannot return to run-time (non-DFU) operations Clearing status Determining device status... DFU state(2) = dfuIDLE, status(0) = No error condition is present DFU mode device DFU version 011a Device returned transfer size 2048 DfuSe interface name: "Internal Flash " Performing mass erase, this can take a moment Next I did try to flush again which produced a better result Match vendor ID from file: 0483 Match product ID from file: df11 Opening DFU capable USB device... Device ID 0483:df11 Device DFU version 011a Claiming USB DFU Interface... Setting Alternate Interface #0 ... Determining device status... DFU state(2) = dfuIDLE, status(0) = No error condition is present DFU mode device DFU version 011a Device returned transfer size 2048 DfuSe interface name: "Internal Flash " Downloading element to address = 0x08000000, size = 186256 Erase [=========================] 100% 186256 bytes Erase done. Download [=========================] 100% 186256 bytes Download done. File downloaded successfully Submitting leave request... Transitioning to dfuMANIFEST state If you approve these steps, I can upload my shell script her to files for your approval. Robert

Hello, I want to connect to tinySA from macOS. I did it previously for updating a firmware (dfu-util) and now tried tinySA.py following the steps according to athome.kaashoek.com/tinySA/python/. Capturing the display was ok. The device is tinySA Basic with 1.4175 firmware. Now I'd like to issue other commands, explicitly to calibrate the low output level. But don't know which scripts are used in the drivers. I only found info that there are windows and linux drivers. Would like to try to install from source to macOS. Could someone provide a link? I searched github but appears that Ho-Ro/nanovna-tools are not the right ones. Radek

For a new product I'm looking for a number of testers, preferably in Europe The product is tiny and has a high resolution dual time stamping and frequency/phase measurement capability Frequency/time/phase reference can be external or internal using a built in gpsdo. The accuracy is less then the tinyPFA but it has much more functionality No specific test equipment availability is required but it's important to have a project that can benefit from the above functionality to ensure actual usage. If you are motivated to join the testing and do have sufficient time to frequently load, test and report on firmware updates, please send me a private reply with some info on your project and how you intend to use the product. If available, you can add some info on your experience and relevant test equipment Replies to the list will be ignored. -- Designer of the tinySA For more info go to https://tinysa.org/wiki

Here's an update on the SVHFS 2025 Conference; Deadline for papers has been extended to March 17 Conference & hotel registration is open; details are in the attached file. Thanks, Robin Midgett K4IDC

tinySA App does not display the RBW or attenuation when they are set to AUTO; perhaps they could be displayed on the status bar along the bottom. I also do not see a control nor display for VBW. Having all 3 displayed on screen shots would be valuable for documentation purposes, VBW control/display would be more "nice to have" as most leave it untouched. Thanks and best regards, Don Brant

Hello there, I am using the Tiny SA Ultra+ (ZS-406, firmware 1.4-196) and sending scan and scanraw commands to retrieve spectrum data, however I was wondering Is there any way to stop or abort an ongoing scan or scanraw command before it completes? From my tests, it seems that once the command is sent, the device continues the process until completion. But in certain cases, I would like to interrupt the scan early (e.g., if the user cancels the operation in my application). Thanks in advance! Juan, M0WWA

Thanks to chri5k for adding DFU-Buddy to the files section. I wasted about 20 minutes trying to get my windows machine to recognize my TinySA. Windows wouldn't even recognize the SA or let me install the DFuse drivers. Then I remembered seeing DFU-Buddy I had seen when I was browsing the files section. I grabbed my Mac and installed the software (you do have to go into system settings and give permission to install the software) and the rest was easy. Opened the software, found my TinySA, selected the dfu file I had downloaded and installed the firmware. Done and dusted in way less time than I had fought with the PC. Terry

Hello. I have Tinysa Ultra (1st hardware version), & using it as panadaptor to my ICOM7100 ...... It's built-in lithium battery is expired & I searched in my country, Iraq, for new original replacement but I couldn't find ! I found original power bank of smart type that has "smart" charging controller & support multiple types of voltage output (5V, 9V, 12V, 15V, 20V, 5 - 11V) with maximum power output of 85W. The "smart" power bank "automatically" determine needed voltage for the device .... I asked about it & one of my friends (YI6AT) asked me to never using it to power my Tinysa Ultra or my antenna analyzer because it can destroy such devices ! Due to my failure to find original replacement for battery of my TinySA Ultra & because the "smart" power bank is original & of high quality I prefer to ask about it's safety to be used with my TinySA Ultra. So, please help me about this. Data about power bank: - CUKTECH Power Bank - 20000mAh 85W Specifications (from it's paper user manual): - Model: PB200 - Battery Type: Lithium-ion cell - Battery Energy (Rated/Typical): 72Wh/73.44Wh 14.4V 5000mAh/5100mAh - Rated Capacity: 11000mAh (5V DC 3A) - Input Port: Type-C - Output Port: USB-A/Type-C - Input: IN1(Type-C1) 5V DC 3A, 9V DC 3A, 21V DC 3A, 15V DC 3A, 20V DC 3.25A - Output: 85W MAX (The maximum output peak power is 85W (OUT1 20V DC 3.25A OUT2 9V DC 2.22A), subject to the actual testing method adopted by CUKTECH lab. * OUT1 (Type-C1) 5V DC 3A, 9V DC 3A, 12V DC 3A, 15V DC 3A, 20V DC 3.25A, 5 - 11V DC 6.1A 67W MAX * OUT2 (Type-C2) 5V DC 3A, 9V DC 3A, 5 - 11V DC 3A 33W MAX * OUT3 (USB-A1) 5V DC 3A, 9V DC 3A, 5 - 11V DC 3A 33W MAX * Multi-Port: 5V DC 3A (OUT1 5V DC 1A OUT2 5V DC 1A OUT3 5V DC 1A) 9V DC 6A (OUT1 9V DC 3A OUT2 9V DC 3A) 12V DC 3A 15V DC 3A 20V DC 3.25A www.cuktech.com https://cuktech.com/collections/frontpage/products/cuktech-15se-power-bank-20000mah-85w-max Can I use this power bank to power my TinySA Ultra while I'm using it connected to my ICOM7100 ?? (we added IF output port for this station: YI1ZQ made such customization for his STN & for my STN) Any help is appreciated !

New FW release Version V0.1340 Changes: - External gating working again. External gating can only be activated using: Counter 1 using input A with gating from input B or counter 2 using input B with gating from input A. Not all illegal configurations are yet block (using counter 1 with A gated by B and then select counter 2 to use input A) -- Designer of the tinySA For more info go to https://tinysa.org/wiki