开云体育

On Tue, Nov 19, 2019 at 02:56 PM, W5DXP wrote: "The 'H' on a NanoVNA-H supposedly means it is a Hugen device. Is there anything keeping the cloners from labeling their devices as -H ?"

Hi Run Aha, thank you for the info. That is a nasty one ? Then a value of 1 might me OK ? Kind regards Kurt -----Oprindelig meddelelse----- Fra: [email protected] <[email protected]>

Hi All, I used the battery from a Boefeng 888 which was broken down to make an Allstar node. Labelled as 2.2Ah, and includes a protection board. 73 Barry G4MKT

A number of forum members run their NanoVNA on Mac computers.?Please do some searching around the message topics and you will find a number of threads on this and the issues you might see.? ...

Hallo Karsten, Ja, if I read you correct, I 100% agree. Vy 73 de Andy

The 'H' on a NanoVNA-H supposedly means it is a Hugen device. Is there anything keeping the cloners from labeling their devices as -H ?

To the question "Trickle charge current is also mentioned on the spec sheet as being 100ma, not enough to kill a 400ma cell." If you read the datasheet fully, you find this lines: #Low Battery voltage

hi all, forgive me if I missed any previous post on this subject. Is it possible to run a nanoVNA on a MacBook, any problems, how to, s/ware etc ? thanks Wayne VK6EH

Agreed. But I was not saying that it should be the case, or was the case ;-) I believe that Li-Ion prefer a typical 0.5C most of the time, so at the worst case lets assume a NanoVNA charge controller

On Tue, Nov 19, 2019 at 12:56 PM, Andy wrote: Trickle charge current is also mentioned on the spec sheet as being 100ma, not enough to kill a 400ma cell. Am I missing something ?

#79: Three Animated-GIF/AVIs in Slow Motion Demonstrate, Step-by-Step, the Graphical Construction of Differential Error Regions Arising in the Measurements with [AnyVNA] Hello, Allow us, please, to

Quote from spec sheet - ?Charger ?Adaptive charging current control, Adaptive charging current control. Quote from spec sheet - Which in theory should regulate charging current. The world and his

Hello, This email message is a notification to let you know that the following files have been updated in the Files area of the [email protected] group. *

Yes, you can upgrade and there is no issue of 'bricking' your unit. Please refer to the Wiki and the User Guide (in the Files section) for info on how to upgrade and how to create a .dfu file if there

Hi Rune, Thanks! As a matter of fact by using NanoVNA v1.03 I got the following info (although I cant see FW version..): Kernel: 4.0.0 Compiler: GCC4.9.3 ... Architecture: ARMv6-M Core variant:

I wouldn't go as far as qbasic but I agree, whenever I see 'python' I anticipate frustration and trouble. It's a mess. It's a great example of why code re-use doesn't scale well. All too often it's

Hi Alessandro, Generally, this means your firmware is so old, there is no way to read the firmware version. -- Rune / 5Q5R

Hi all, I noticed that moving to NanoVNASaver 0.2.0 > About, the NanoVNA Firmware version displayed is: NanoVNA Version ? Has anyone noticed the same thing or I have something wrong? NanoVNAe works

Many have measured and tested it but found no noticeable difference between the variants. Probably the raw material comes from the same source, pcb is the same. So why would it differ unless the

Looking again at your pic from Amazon, I notice it is sold by KKMoon. I brought two NanoVNAs from this same seller there. When they arrived one was a clone and the other appears to be a hugen