开云体育

Hi Rune -- Yes, I had done a sweep before the "short" calibration, but not the other two. It would be really nice if one could save a calibration to a file, so that he could recall the file on later

The marketing hype specifically says its the impedance, not the power level. I somewhat doubt any walkie talkie antenna would be damaged by 10 W of power. Certainly, the ones I have seen are just

i believe Google Translate is part of this conversation loop. progress! your transceiver is a Retevis Ailunce HD1 VHF/UHF DMR handheld. you report 3rd party antennas being damaged when used with this

Gentlemen, many thanks for your help. Python is now successfully installed and I can launch Rune's python code. The issue was that Python wasn't on the path (as several suggested). Fixed by checking

<pulaskite@...> wrote: At least on Windows the console works at much higher rates than 9600. I've been using it at 115200. I also put much of this information in this thread in the

Attached is a comparison of Return Loss measurements for four different loads, at three different frequencies. Devices testing were two NanoVNAs, a Rigol Spectrum Analyzer/RF bridge, and an AAI Vector

This sounds a combination of 1) Marketing rubbish to get you to use their antennas. 2) Poor engineering The output impedance of this transmitter is likely to be considerably less than 50 ohms. If the

Yes; I suggest reading this: https://blog.atollic.com/optimizing-code-size-with-the-gnu-gcc-compiler-for-stm32-and-other-arm-cortex-m-targets It is generally easier to find latest versions of gcc

Just a couple of thoughts about gcc. Is debugging information saved with -g? That will make the executable larger. Does changing optimisation level (-O, -O2 etc) change the size of the code? Would

My understanding is that STM32 DFU bootloader is NOT overwritten by download process, so that failures may be restarted/recovered.

Measuring nonlinear devices (e.g. ferrite cores, diodes and active devices) can be problematic with non-sinusoidal stimulation e.g. nanoVNA. While nanoVNA DSP can sort harmonics, DUT "sees" full

Thanks for the insight... Not good news as based on earlier messages I have ordered from TomTop and awaiting delivery :-( TomTop does offer a refund if item(s) not received or not as ordered /

Windows filesystems have an attribute for hiding content, which some malware exploits. Yes weird, AKA "security by obscurity". Here are procedures to "unhide" from file Explorer:

The reason for having in-app calibration rather than using the calibration on the device is to avoid these problems. The in-app calibration supports pretty much however many calibration points you're

As a matter of interest, should one get a power failure during the “download” does that render the device useless or can one just restart the process when power is restored? > Dave -- Dr. David

Currently NanoVNA has 4 calibration slots. How about limit sweep count up to 4? *User must calibrate done every 1/4 bandwidth then save 0 to 3 calibration slot. *nanovna-saver loads every 1/4

Does not have NanoVNA or professional lab gears. Also I'm not RF expert too. But... If lots of sweep count, calibrated data still acceptable/trustworthy? ie) 1-800MHz /w 10x => sweep every 1/10

A word of warning when using DfuSEDemo.exe Uploading means downloading from the device into your computer Upgrade/Verify is for loading new software into your device So ALWAYS first do a "Upload"

Thanks!!! All ok now

I don't know if the STM32F303 is pin-compatible with the existing chip, but I did check earlier that STM32F104 should be a direct drop-in, and offers slightly more RAM (20kB) and 128kB of flash memory