开云体育

Mega and Giga are STANDARD abbreviations for powers of 10. Mega = 1E+6 Giga = 1E+9. Pico - 1E-12. Micro = 1E-6. These are all STANDARD engineering notations! Oh, yes, and picoFarad =

In the example, k is correct but K wouldn't lead to confusion because the capital rule applies to *units* (Hz in this example) and k is a *prefix* (scaling factor if you will). Raymond

Your question has insufficient information.? Explain what you are doing and what your observations are.? Not getting any results makes no sense.? What readings don't change?? What are the

That is true. Engineering notation conforms to the SI unit system. Engineering notation applies to *prefixes*, not *units*. Hertz is a *unit* in the SI, milli, mega etc. are *prefixes* (to

Also note: dB deci-Bell Not DB dBm decibels above one milliwatt Not DBM Hasan wrote:

No, there isn't. The rule applies to *units* in the SI. Mega, giga, milli, pico, deci etc. are *prefixes*. Raymond

the capital M is to properly differentiate between lower case m = milli or 1/1000 and M Mega, one million. Google Engineering Notation for Frequency and you will find the standards. 73,

Yes, but there is an inconsistency, as I do not recall any scientist named Mega or Giga, so it should be gHz and mHz........ Errrrr.... sTEVE l. (Woops Steve is my name so it should be Steve)

By SI convention, all units named after people are to be spelled with an uppercase first letter, so Hz, not hz (the unit Hz is named after Heinrich Hertz). Also mHz, kHz, MHz, GHz, *not* mhz, khz,

As in mA as well, thanks for the reminder and since Hertz is a name, the H should be capitalized. ...and it is kHz not KHz, as capital K is for Kelvin, not 1000 ...although in resistance values it

Martin, I upgraded my SAA-2N FW to ver 20200926, works fine on instrument, however I have the same issue with NanoVNA-Saver, as well as some other anomalies (program sweep runs on 1 step but hangs on

What about a balun. If I connect two wires directly to any measuring device without a balun, I don't get any results. Readings don't change no matter what I do.

Dear Alan, Thankyou. We are a little way down the message ladder, so this refers to several messages back. Thankyou for an injection of sanity (to me, anyway). I will continue to play, plod on, and

Jeff, interesting question that you ask. I remember, back when I had to implement TOSM (=SOLT) calibration with arbitrary standards, including a fully-known but non-ideal through standard, I was too

To avoid confusion, please note (conform) to the following *standard* notation in emails: mHz or mhz = *MILLI*hertz = 1E-3 Hz (subsonic) MHz or Mhz = *MEGA*hertz = 1E+6 Hz GHz or Ghz = *GIGA*hertz

Thanks very much, Christian. That is a great help. Pivoting slightly...I have a question for the group regarding SOLT errors and calibration, but this has to do with the THRU standard, rather than

I have the same issue. VNA 2_2 Version: git-20200617-1a9a11d Build Time: Jun 19 2020

Be careful with large plugs. I already broke. I had to temporarily rewire from another port.

I m The The nand oand noonioonno noo ? in 73, KB5WCK ________________________________ Sent: Tuesday, October 6, 2020 3:38:17 PM To: [email protected] <[email protected]> Subject:

John's and Jeff's posts make me reconsider my previously posted plot. Unfortunately, it contained an error - or rather something I forgot about my old MATLAB script. For that plot I calculated an