开云体育

I had that problem too. I initially gave up but tried a day or two later ( maybe a different Aliexpress trader and got my town on the dropdown. I am waiting for imminent arrival.

As far as working at 1.3ghz, I cannot give any authoratitive opinion as I am away from home with a 3.2” screen v2 ( even the 3.2” screen is easier to use than the 2.8”). However it seems to calibrate nicely and do appropriate things on the Smith chart etc with various bits attached, up to 3ghz and even up to 4.4ghz.

Go for it.

Steve L. G7PSZ

I could not get Alibaba order form to understand how a Swedish mobile phone number looks like... so I ordered via AliExpress and payed with PayPal without any problems.
Now just wait and see....
/Lars SM0TGU

I did the same as it was not possible to pay with PayPal at Alibaba. It looks like it is the same seller anyway in the background.
We cross our fingers and wait!

Anders - SM5EPC

You can pay with paypal on Alibaba, just start a chat with Maggie and request instructions.

--
NanoVNA Wiki: /g/nanovna-users/wiki/home
NanoVNA Files: /g/nanovna-users/files
Erik, PD0EK

On Sat, Aug 1, 2020 at 01:24 PM, Hugen wrote:

There is no innovation, just a new shell.
Since this group has been dissatisfied with the SMA connector and the 2.8-inch
display, we installed the N-type RF connector and the 4-inch LCD on the
original SAA2 and fixed it with a metal shell. The increase in cost mainly
comes from N-type connectors and radio frequency cables containing N-type
connectors. In order to avoid confusion with the next-generation products that
may appear, we temporarily call it SAA-2N.
The N-type connector is very heavy, and the total shipment is 1kg. The
logistics company may need to charge a logistics fee of 1.5kg, so the
logistics cost is much higher. We are waiting for the MSDS report of the new
battery. After the MSDS test is completed, we will provide DHL shipping
methods.

As some users cannot complete payment in alibaba, we have activated aliexpress
and support paypal payment.



hugen

Hi Hugen
can you show the exact hardware inside this new unit? I mean the schematic and a picture of the board?

the original SAA-2, which has a 2.8" display, has a completely different hardware/schematic than all other nanovna.

On Sat, Sep 5, 2020 at 04:08 AM, amirb wrote:

Hi Hugen
can you show the exact hardware inside this new unit? I mean the schematic and a picture of the board?
the original SAA-2, which has a 2.8" display, has a completely different hardware/schematic than all other nanovna.
=============================================
As hugen posted, there have been no changes to the original SAA-2 design, only layout changes to accommodate the addition of a 4" display. The schematics are the same as the original open source project.

I just received the SAA-2N that I ordered and will be posting a review on the V2 user group after I have verified its performance. So far the un-boxing experience has been positive.

- Herb

Looks nice!

Does it use the same serial commands as the v1 I wonder ?

On Sat, Sep 5, 2020 at 07:51 AM, OneOfEleven wrote:

Looks nice!

Does it use the same serial commands as the v1 I wonder ?
========================================================

OneOfEleven,
Since the new changes are only in display size and packaging, it brings along with it the same V2 serial commands - meaning it is not backwards compatible with programs written for the NanoVNA and NanoVNA-H4.

- Herb

I not see any reason use in SAA2 1024 not calibrated point mode for CPU send (this need a lot of ram)
I test speed on H4 (on V2 result should be some) (thanks OneOfEleven for add points/sec measure):
1 segment 401 uncalibrated point - 570 points/sec
2 segments 802 uncalibrated point - 560 points/sec
4 segments 1601 uncalibrated point - 560 points/sec
8 segments 3201 uncalibrated point - 560 points/sec
This points/sec points received from device (in device speed more beeg, not need send data, i measure 401 points on CH0 and CH1 in 620ms so speed ~650 points/second, for only one channel ~930)

So no matter how many you measure points in one time (yes if enable calibration in device 1/3 time lost on calc interpolation for segment, but V2 not do this) in segment scan

So 1024 points not give result, but grab a lot of memory, this memory can be used for increase device points count