开云体育

I had a similar issue with an H4. A firmware upgrade fixed it, and improved the menu access, as well as the softkeys for setting frequencies.

Have you tried loosening the screws that hold the display in place? There may be a short-circuit underneath. Mike - M0MLM ------------------------------------------------------------------------

I recently found that I-PEX has some very explicit mating instructions. https://www.i-pex.com/sites/default/files/downloads/pdf/manual_mhf_i_lk_him-17020-01.pdf I realize the method is provided for

Perhaps something else is using COM10? The NanoVNA-Saver or whatever? David -- SatSignal Software - Quality software for you Web: https://www.satsignal.eu Email: david-taylor@... Twitter:

Roger, Thank you for your assistance and advice. I was able to actually communicate with the NanoVNA and pass along commands. It is quite an incredible tool! My soncere gratitude for the talent and

Attached is an annotated screenshot showing what some of the buttons do in NanoVNA app. It should be enough to get new users started. Roger

If you connect to a NanoVNA with a terminal program you need to set the baud rate to 115200 and no flow control. Roger

If you have problems... --------------- 1. There are not two wizards for the drivers. There are four drivers in the zip file - two for Win 8 and two for WIn7. You have to pick one of the four and only

If you have problems... --------------- 1. There are not two wizards for the drivers. There are four drivers in the zip file - two for Win 8 and two for WIn7. You have to pick one of the four and only

This topic is for NanoVNA app so please post Putty questions in your Putty thread so we don't hijack this topic. I will reply to your Putty inquiries there... Roger

I believe you are using WIN 7. The problem could be that you do not have the correct driver installed for Windows 7. Windows 10 has the correct driver for the NanoVNA ready to go (or update will

Try 115,200 for the baud rate. 73 Stan KM4HQE

Please show us the list of COM ports listed in the Windows 7 Device Manager after plugging in the nanovna. It may assign a different number than you expect.

Roger, Appreciate your assistance. Well, it seems that my COM10 port./driver has disappeared and only COM1, COM2, and LPT1 were left behind. I followed your link to the Box validation, obtained an ID

Here is a link to the WIN 7 and WIN 8 drivers for the NanoVNA on my Box drive. Download button in upper right hand corner. (Note: These are NOT the DFU drivers required for updating firmware)

NanoVNA app is not seeing your COM10 from the NanoVNA. I think you reported this with Putty as well. I suspect Saver will have the same issue. I believe you are using WIN 7. The problem could be that

"You select the COM port from the drop down list..." OK..how about this? (See attached.) -- William, k6whp -------------------- "Cheer up, things could get worse. So I cheered up and things got

If you use the latest publicly available version of the DiSlord NanoVNA-D v1.1.00 firmware and calibrate in the NanoVNA-App-v1.1.209-OD10 it will use "raw data" from the NanoVNA. That means that

If you want to use NanoVNA app you have to be using a recent version of the firmware (last year or so). The reason is that NanoVNA app uses the binary (not ASII) transfer protocol to transfer data. If

You select the COM port from the drop down list. Then press button below to Connect. You need to select where calibration is done from the drop down list. You can transfer Stimulus range settings from