开云体育

Hi Bob, There is a document in the hardware mods section of the forum's files that tells how it was done..?

Steve, can you point me toward that display, and any instructions to retrofit? Thank you. Bob K6DDX

Ok, I just read the Whole msg: you've reflowed around the ribbon cable. Did you do a continuity check from the digitizer input pins on the uP to the solder pads? It's not a software issue. Either the

I had an interesting experience with a touchscreen. It was actually a working nano v2 for which I bought a 3.2” screen with the same interface via Ebay. On plugging it in, all worked except the

Dear Gary, Agree wholeheartedly. My stable of nano devices consists of an original v2, a v2 with 3.2” screen (much easier to use) and a v2 with 4” screen and n connectors about to arrive.....and a

Regarding this post from Gary from yesterday, a few quick explanations that may be obvious to some. Also a bit of what should be considered wild speculation on my part. Some nanovna firmware uses the

1: Try made calibration first Use leveler select Config->Touch cal Touch top+left screen side Touch bottom+right screen side After check work, use Config->Touch Test If all good - Save config

Hello - I have some advanced troubleshooting questions in regards to touch screen operations - The touch screen operation hasn't worked since day one on one of my NanoVNA's, likely a clone (no shields

Measured on my HP spectrum analyzed. No attempt at precision, and so not calibrated instrumentation results. Relative (between firmware revisions) levels are fine and adequate for the intended

Gary, So, exactly how did you measure those power levels? Did you somehow only measure that component of the incident signal that was at the frequency of interest? I totally agree with all sentiments

Hi Jerry; The power levels I posted are measured at the CH0 port. I haven’t been ambitious enough to try digging into the source code to see where the levels were set. Measuring takes less effort.

Minor correction to my last post: < 1.5 volts into 50+50=100 ohms, so 1.5/100 = 0.015 ma. Jerry, KE7ER

No, it's not the latest firmware. I'd recommend going to the io.group's files, go to DiLlard's NanoVNA-H Firmware, go to NanoVNA v0.8.2_96kHzIF_3.2kHz_sweep_points.rar, and extract NanoVNA-H4

That's done with a spectrum analyzer, not a VNA. >

Ahh I see! Makes sense now! But what if you want to analyze the performance of let's say a complex receiver? Don't you need a high bandwith resolution to see the spurs and intermodulation products and

Newbie NanoVNA-H4 user here with some questions: 1) My unit arrived a couple days ago with firmware version 0.5.0. Is this the latest for the H4 model? 2) Has anyone using macOS with Parallels running

Gary, I'm guessing you might have gotten the -7 and -17 dBm figures from the nanovna firmware, and that this jump at 301mhz is due to a switch from the fundamental to using harmonics. So there is

Roger; With Hugen’s NanoVNA-H-AA installed, the output power of port 0 measures ~ -7 dBm up through 300 MHz. At 301 MHz it drops to -17 dBm and holds pretty tight to that up through 900 MHz. The 900

Thanks all for your great answers! There was indeed no ground, so stupid me :) One of the antennas was a groundplane antenna, and I would have expected somewhat better behaviour there. It was for 2m

If you don't want to mess with console commands could calibrate with a 3dB pad in the cable for the S11 measurement. The round trip attenuation for the reflection would then be 6dB. The bridge is