开云体育

There’s a picture of the various tinySAs on the wiki that implies that the Ultra+ is physically larger than the Ultra. If it is, what are its dimensions? I can’t find them in the specs. _._,_._,_

Hi Erik, I just noticed that the Ham Band shading is incorrect for three of the USA band allocations. (I didn't check bands above 800MHz.) The 75/80 Meter band is 3.5 MHz - 4.0 MHz, but is only shaded from 3.5-3.8. The 40 Meter band is 7.0 MHz - 7.3 MHz, but is only shaded from 7.0-7.2. The 6 Meter band is 50.1 - 54.0 MHz, but is only shaded from 50.0 - 52.0.

Hello, I bought my Tiny SA Ultra some time ago from the suggested supplier so I am led to believe it is genuine. I have been lurking here for some time and have seen many messages from people who have "stuffed" their Tiny SA ultra's because they bought a clone. I worry about upgrading mine, just healthy paranoia :) Is there something I can post about my Tiny that will tell me that it is an original before I upgrade the firmware. I know Erik knows. I'm not asking for the "secret" to determining clone v original, just want to confirm that mine is original. Thanks Mark

I once turned on Listen mode on my TinySA ultra and shut it down - now it starts up in Listen mode by default every time; I have to manually uncheck the "Listen" checkbox at each startup. It saves all settings (e.g. frequencies) except the now unchecked "Listen" mode Version: v1.4-137-g1806825 Is there a way to reset this behaviour to factory default (i.e. start up in normal display mode), without deleting the factory calibration data? Looked at the firmware changelog, couldn't find a bugfix for this particular issue.

I just received my ZS-407 from R&L Electronics. I do frequency coordination for large events and the most common frequency range for wireless devices is in the 470 MHz to 608 MHz UHF TV band. I set the ZS-407 for a start frequency of 470 MHz and a stop frequency of 608 MHz. The RBW was initially set for auto. With no antenna on the 407 it was just showing a noise floor that was around -90 dBm. When I changed the RBW to 100 kHz, it displayed a spurious signal around 533.8 MHz. As I drilled down into this signal and reduced the RBW even lower, it turned out to be two very narrow bandwidth spikes at 533.725 MHz and 533.775 MHz. My older TinySA Ultra with the exact same settings does not display these signals. I also tuned my Icom IC-R30 to those two frequencies in CW mode and confirmed that no signals were received. Can anyone else see these “birdies” on their ZS-407 or is it just mine? - Otto

Hi to all. Right now I'm using TinySA Ultra for conducting some test in order to reduce some harmonics around 700Mhz on my product. The issue is that the TBTC2 tem cell is able to catch a lot of interference in the area where I live. Everything is floating since the product is battery powered and the TEM Cell ground is connected to the shield of coax cable up to TinySA (used not connected to PC). Maybe grounding everything to the house earth could be a good or a terrible wrong idea? It could help? The conductive tent is a must? Can you help me in this? Thanks NH

Southeastern VHF Conference 2025 Announcement & Call For Papers Quality Inn, 3095 Wilma Rudolph Blvd, Clarksville, TN 37040 April 4th and 5th, 2025 Papers and presentations are solicited on both the technical and operational aspects of VHF, UHF and Microwave weak signal amateur radio. Some suggested areas of interest are: ? Transmitters, Receivers, Transverters ? RF Power Amplifiers, RF Low Noise Preamplifiers ? Antennas ? Construction Projects ? Test Equipment and Station Accessories ? Station Design and Construction ? Contesting, Roving, DX-peditions ? EME, Propagation (Sporadic E, Meteor Scatter, Troposphere Ducting, etc.) ? Digital Modes, Digital Signal Processing (DSP), Software Defined Radio ? (SDR) Amateur Satellites, Amateur Television In general papers and presentations on non-weak signal related topics such as FM repeaters and packet will not be accepted but exceptions may be made if the topic is related to weak signal. For example, a paper or presentation on the use of FM simplex in contests or on the use of APRS to track rovers during contests would be considered. Formats: All submissions for publication in the proceedings should be in Microsoft Word (.doc or .docx) formats. Submissions for presentation at the conference should be in Microsoft PowerPoint (.ppt or .pptx) format and delivered at the conference on a USB memory stick. Please understand that your PowerPoint Slide presentation will not be accepted to be published in the proceedings; only meaningful text will be published in the proceedings, not slides that need description for understanding. Paper: Size should be 81?2 x 11-inches. Margins: Top and sides should be 0.75 inches; bottom must be 1 inch. Font: You may choose your font, however, try and use standard fonts. The font should be clean and easy to read 12 pt. Layout: Either a one or two-column format. Page numbers: Do not include page numbers. Headers/Footers: Do not include Headers and/or Footers. Drawings: Drawings should be embedded in the files. Place them where you’d like them to appear. Photos: Color or black-and-white digital images if utilized should be embedded in text files. Place them where you’d like them to appear. Printing: We print what we receive. We do not copy edit (but will correct something if we notice it – or if you notice it and let us know). We try to make all papers somewhat uniform, but we do not rework each article. Page numbers are added as we prepare the files for our printer. The deadline for the submission of papers and presentations is February 15, 2025. Please indicate when you submit your paper or presentation if you plan to attend the conference and present your paper in person or if you are submitting solely for publication. Papers and presentations are being handled by Mike Stipick, KC4RI, and should be sent to: KCRI@.... Mike may be contacted at the same email address if you have any questions.

I just received the TinySA Ultra. As a first practical use, I want to measure spurious emissions from my various transmitters. However, I understand that there is a maximum of -25dbm on the low input, and a maximum 30dbm internal attenuator. By my calculations, this falls far short of even a 1w transmitter. Am I correct in assuming that connecting a 1w transmitter (an HT, say) to the TinySA via SMA cable to the low input will be definition require a minimum of a 25dbm attenuator plus the internal 30dbm attenuator to get a 1w signal under the -25dbm low input threshold?

Are there any service centers for the Ultra in the US. I need the attenuator replaced. -- Walt, WD0GOF, WD0GOF.COM

I am having trouble with frequency Markers and Presets, that hopefully someone can help with. I've set the markers with 'Search' -> 'Enter Frequency' and set the marker to 733MHz. 'Tracking' is turned off. This works fine, and the marker does what I want it to. Then I save it as a 'Preset', and later when I load that Preset the the marker frequency has changed. E.g. to 733.2MHz. Each time I reload the Preset, the Marker Frequency stays the same (e.g. always 733.2MHz), but is not the set frequency. But If I save the preset again, it might change to a different marker value (e.g. 736.6MHz) I've tried this with Presets on the device, and on the SD Card. I've also tried it with 'Save Settings' enabled and disabled. Should 'Enter Frequency' lock the marker, and should this be saved with the Preset? Many thanks to anyone for any advice that you might have.

Here's a video about TinySA Ultra+ ZS-407 Unboxing and Calibration TinySA Ultra+ ZS-407 Unboxing and Calibration

Workaround: Firmware update successful when using an external USB hub (USB 3 also). After successful flash, I try again without USB hub and gets stuck at 0%. With USB hub, success. Original message: Please help, dfu-util connection is working (finds device) but flash not responding. Bought from https://zeenko.aliexpress.com/store/1101394653 >1 year ago Self-test: 12/12 pass Firmware is from 2023 I try to update firmware. I follow https://tinysa.org/wiki/pmwiki.php?n=Main.UpdatingTheFirmware Ubuntu 24.04 LTS USB 3 port $ sudo apt install dfu-util (I also try manual dfu-util from provided link in wiki, same result) $ curl http://athome.kaashoek.com/tinySA/DFU/tinySA_v1.4-175-g1419a93.bin -o tinySA.bin $ dfu-util -a 0 -s 0x08000000:leave -D tinySA.bin (I censor vendor:device) 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 vendor:device 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 = 113244 Erase [ ] 0% 0 bytes Stuck at 0% forever. Verbose output with -v still stuck at 0% forever 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/ libusb version 1.0.27 (11882) 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 vendor:device Device DFU version 011a DFU attributes: (0x0b) bitCanDnload bitCanUpload bitWillDetach Detach timeout 255 ms 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 " Memory segment at 0x08000000 64 x 2048 = 131072 (rew) Downloading element to address = 0x08000000, size = 113244 Erasing page size 2048 at address 0x08000000, page starting at 0x08000000 If I try to read data, also stuck at 0% forever. $ dfu-util -a 0 -s 0x08000000:1024 -U newfile.bin Please help I tried for 2 hours no luck