AA-35

开云体育

开云体育

开云体育

开云体育

Hi Andy,

Yes, the full range is always used. You cannot reduce it.
In fact, the wider the range, the more accurate the result we will get.

Regards, Alex

When doing the cable loss measurements, does it always scan from 0 > 1gig or can the scan width be narrowed down as well as increasing the level of loss on the left side of the screen?

Andy? K9ATX

开云体育

Hi Bruce, hello everyone.

The AntScope2 software, when working with RigExpert analyzers, accepts input data from the analyzer in two ways:
1 - via the HID interface. This option is possible only when the analyzer is physically connected to a PC via a USB cable. Works only for analyzers of the Zoom and Stick family.
2 - via the COM port. This works for old models of analyzers and when the analyzer is connected via Bluetooth with the Classic protocol.
The Bluetooth module with the classic protocol has only the analyzer AA-55 Zoom of the first revision (serial number type 1.**).
All other analyzers have a BLE module that "cannot" create serial ports.

The AntScope2 software was created in the qt5 framework in the C ++ language.
The implementation of the BLE protocol stack in Windows 10 must be carried out in the .NET framework.

This requires a complete redesign of the program, which is difficult and time-consuming.

Our programmers are looking for an alternative way - the creation of an intermediate module that can communicate both with the core of the operating system and with AntScope2 to implement the capabilities of the BLE analyzer connection.

As soon as we have the results, we will report.

Best regards, Alex Antonov /UT2UM/

An update, I received a Asus BT500 dongle today and installed the Asus

driver downloaded from their site.? This is a Bluetooth 5.0 unit.

I plugged in the unit and paired it to the 650 ZOOM.

In Device Manager it shows up in the Bluetooth tree and looking at the

properties it indicates as working correctly with no errors.

The driver install package did install Bluetooth LE drivers because these also

show up in the Bluetooth tree.

Running the AntScope2 it shows that no analyzer is connected although all other

indicators have the Bluetooth connection working properly.

This is on a Win 8.1 64 bit laptop that does not have Bluetooth built in.

The question is why the AntScope2 program does not detect the ZOOM unit?

The spec indicates 4.2 LE so the BT500 does cover this entirely via the drivers.

I have the latest 1.7 firmware loaded in the ZOOM unit and the latest AntScope 1.2.2.

When can we expect to download a package that includes all necessary files

in order to work correctly between the 650 ZOOM and the AntScope program?

Bruce? N7XGR?

On Fri, Jul 30, 2021 at 2:49 AM Alex RigExpert via <support=[email protected]> wrote:

Dear friends!
A couple of minutes of your attention. Important information.

Bluetooth, as a wireless connection protocol, has two branches:
- Bluetooth Classic (BC)
- Bluetooth Low Energy (BLE)

Connection via the BC protocol creates a virtual serial port.
The BLE connection does not create virtual serial ports.

All RigExpert analyzers (except for AA-55 Zoom of the first revision) use Bluetooth modules with BLE protocol.

RigExpert analyzers with Bluetooth are designed to connect to mobile gadgets (Android and iOS).
Until recently, the Windows OS at the kernel level could not work with devices using the BLE protocol. This opportunity has recently appeared.
At the moment, our developers are working to ensure that analyzers with the BLE module can work natively with AntScope2.

Sincerely, Alex Antonov

30.07.2021 5:01, Keith Ballow KN5G пишет:

There was only the one COM Port device to choose from and it only appeared in the ANTScope2 software after I jumped through all the hoops to pair the 650 Zoom and assign a COM Port to it.?

I removed the “Paired” device and associated COM Port from the Microsoft Surface Pro with the intention of adding it again just to see if I got any different results.

I received this message when I tried to connect to the 650 Zoom. Not sure what this message is trying to tell me. Maybe that the software sees a COM Port but there isn’t anything talking over it?

I did notice that after I removed and then added the 650 Zoom back into the list of Bluetooth devices on the Surface Pro that it is now reporting as an “AA-55 Zoom”. That seems odd to say the least.

Unless I am doing something wrong in the setup/configuration of the Bluetooth Device on the Surface Pro (and that is totally possible), I have to conclude that there is a glitch somewhere in the Bluetooth implementation and the 650 Zoom and the Surface Pro are having problems setting up a solid Bluetooth communications link between them.

I probably will not send a lot more time trying to get these to talk to each other and just use the USB cable, unless or until there is a firmware upgrade to the 650 Zoom that might address this issue. I still love the Analyzer and I’m hoping that eventually it will be able to talk via Bluetooth to the Surface Pro laptop because the iPad just leaves a little to be desired compared to a full blown laptop.

Keith

-.- -. ..... --.?

KN5G

On Jul 29, 2021, at 6:45 PM, Roger Need via <sailtamarack@...> wrote:

?On Thu, Jul 29, 2021 at 04:08 PM, Keith Ballow KN5G wrote:

I fooled around on the Surface and got it to “Pair” with the 650 Zoom, and even managed to get the Surface to assign the 650 Zoom a COM Port.

?

In the AntScope2 software settings, the COM 3 port shows up and I can click on the “Connect Analyzer” button but the software never seems to connect to the 650 Zoom. The top line of the software continues to show, “Analyzer Not Connected”.

If you look in the drop down menu is there another COM port other than COM3 assigned to the Zoom?? If so try select that port and try it.?

Roger

--

Hi Ken,

To exchange data with a PC, the analyzers use an FTDI chip.

You can download the drivers on the website of the manufacturer of this chip:

Regards, Alex

开云体育

Hi Ken,

To exchange data with a PC, the analyzers use an FTDI chip.
You can download the drivers on the website of the manufacturer of this chip:

Regards, Alex

Thanks Alex. I suspected as much. I re-installed Antscope 1.0 v0435 but can't get it to connect to the AA-230. Device Manager shows the AA-230 under Other Devices with no drivers installed. Where are the drivers?

-ken-

Sent From My Desktop Via EMClient.

开云体育

Dear Ken,

Alas, but through AntScope2, it will not be possible to load the saved data from the memory of the AA-200/230/500/520 analyzers.
These analyzer models use a binary data format that is not supported in AntScope2.

You can save data via AntScope. And then use a special utility to convert files into an understandable format for AntScope2.

Best regards, Alex Antonov

I haven't used Antscope with the AA-230 PRO for a long time. I want to transfer the saved data to the PC. I don't see anything in the Antscope 2 V1.2.2 menues about loading data from the analyzer.

开云体育

Keith

-.- -. ..... --.?

KN5G?

开云体育

Dear friends!
A couple of minutes of your attention. Important information.

Bluetooth, as a wireless connection protocol, has two branches:
- Bluetooth Classic (BC)
- Bluetooth Low Energy (BLE)

Connection via the BC protocol creates a virtual serial port.
The BLE connection does not create virtual serial ports.

All RigExpert analyzers (except for AA-55 Zoom of the first revision) use Bluetooth modules with BLE protocol.

RigExpert analyzers with Bluetooth are designed to connect to mobile gadgets (Android and iOS).
Until recently, the Windows OS at the kernel level could not work with devices using the BLE protocol. This opportunity has recently appeared.
At the moment, our developers are working to ensure that analyzers with the BLE module can work natively with AntScope2.

Sincerely, Alex Antonov

There was only the one COM Port device to choose from and it only appeared in the ANTScope2 software after I jumped through all the hoops to pair the 650 Zoom and assign a COM Port to it.?

I removed the “Paired” device and associated COM Port from the Microsoft Surface Pro with the intention of adding it again just to see if I got any different results.

I received this message when I tried to connect to the 650 Zoom. Not sure what this message is trying to tell me. Maybe that the software sees a COM Port but there isn’t anything talking over it?

I did notice that after I removed and then added the 650 Zoom back into the list of Bluetooth devices on the Surface Pro that it is now reporting as an “AA-55 Zoom”. That seems odd to say the least.

Unless I am doing something wrong in the setup/configuration of the Bluetooth Device on the Surface Pro (and that is totally possible), I have to conclude that there is a glitch somewhere in the Bluetooth implementation and the 650 Zoom and the Surface Pro are having problems setting up a solid Bluetooth communications link between them.

I probably will not send a lot more time trying to get these to talk to each other and just use the USB cable, unless or until there is a firmware upgrade to the 650 Zoom that might address this issue. I still love the Analyzer and I’m hoping that eventually it will be able to talk via Bluetooth to the Surface Pro laptop because the iPad just leaves a little to be desired compared to a full blown laptop.

Keith

-.- -. ..... --.?

KN5G

On Jul 29, 2021, at 6:45 PM, Roger Need via groups.io <sailtamarack@...> wrote:

?On Thu, Jul 29, 2021 at 04:08 PM, Keith Ballow KN5G wrote:

I fooled around on the Surface and got it to “Pair” with the 650 Zoom, and even managed to get the Surface to assign the 650 Zoom a COM Port.

?

In the AntScope2 software settings, the COM 3 port shows up and I can click on the “Connect Analyzer” button but the software never seems to connect to the 650 Zoom. The top line of the software continues to show, “Analyzer Not Connected”.

If you look in the drop down menu is there another COM port other than COM3 assigned to the Zoom?? If so try select that port and try it.?

Roger

开云体育

I removed the “Paired” device and associated COM Port from the Microsoft Surface Pro with the intention of adding it again just to see if I got any different results.

I received this message when I tried to connect to the 650 Zoom. Not sure what this message is trying to tell me. Maybe that the software sees a COM Port but there isn’t anything talking over it?

I did notice that after I removed and then added the 650 Zoom back into the list of Bluetooth devices on the Surface Pro that it is now reporting as an “AA-55 Zoom”. That seems odd to say the least.

Unless I am doing something wrong in the setup/configuration of the Bluetooth Device on the Surface Pro (and that is totally possible), I have to conclude that there is a glitch somewhere in the Bluetooth implementation and the 650 Zoom and the Surface Pro are having problems setting up a solid Bluetooth communications link between them.

I probably will not send a lot more time trying to get these to talk to each other and just use the USB cable, unless or until there is a firmware upgrade to the 650 Zoom that might address this issue. I still love the Analyzer and I’m hoping that eventually it will be able to talk via Bluetooth to the Surface Pro laptop because the iPad just leaves a little to be desired compared to a full blown laptop.

Keith

-.- -. ..... --.?

KN5G