?

?

Hi Rick,

I have the AA-230 Zoom BLE. My computers are Windows 10 and Windows 11. I just installed AntScope2 v1.3.3 on both computers. I flashed the Rom in the AA-230 with version 1.120. Now AntScope2 on both computers will connect to the AA-230 but slightly different methods.

The Windows 10 AntScope2 starts with the USB/COM/BLE window open and detects the AA-230 under USB. It doesn't detect anything under COM or BLE (No Bluetooth Device on the computer). Window 10 Device Manager doesn't show a Com Port related to the AA-230. There is a USB Composite Device under USB Controllers but I can't tell if it is related to AA-230.

The Window 11 AntScope2 starts by automatically connecting to the AA-230 in USB mode. (I like that.) Opening the Setup tab brings up the USB/COM/BLE window and on that computer I can select BLE or USB to connect but not COM (Computer has Bluetooth). Windows 11 Device Manager doesn't show any related COM ports.

I'm happy with the operation. I hope these observations help someone else. 73. -ken-

?

[Edited Message Follows]

Well, now after a week, AntScope2 does not see the port for the AA230 and can't connect. When I plug the analyzer into a USB or unplug it, I hear the Ping from Windows 11. But I don't see any ports in Device Manager or AntScope2.

Update: I updated the firmware from 1.119 to 1.120 using the Flash Tool and now Antscope2 connects automatically to the AA230 (Don't have to open the Setup tab).

?

[Edited Message Follows]

The first time I connected my AA230 Zoom BLE to a USB port on my laptop and tried to connect with ANTSCOPE2, the AA230 shut down. It could not be started with the Panel On/Off button. I had to remove a battery to get it going again. Then when I plugged in to the USB port again, the AA230 stayed on and ANTSCOPE2 made the connection. My laptop has both USB2 and USB3 ports and I'm not sure which one I plugged into when it shut down but after that, either USB port works OK. Is this behavior common? Does the AA230 have to be plugged in before Antscope starts? Or the other way around?

?

Also,

Rick,

I am glad you have the AA-54 up and running on Antscope 2.??

Now, I could change the band designation bars that are gray from a color wheel that would be great!

?

Rick,

Thanks for the pointer.? I just did change it.

Question, can I customize the bars that show the band zones?? ?The are currently gray, but, I would like to change them to a different color?

Thanks Rick.

Mike

?

[Edited Message Follows]

Rick,

Good questions all:

So, I uninstalled antscope2-1.3.0 and dropped back to the version I had installed on Windows in June for Field Day, v.1.2.6 which had worked with my AA-54.

I just finished installing that along with the program that came on the CD for the AA-54,?cdm20824_setup-4.exe, (FTDI drivers to generate a COM port from a USB device).??

I checked device manager and it showed COM4 for the AA-54.? ?Then, I installed Antscope2 v.1.2.6 and opened it, went into Settings in the lower left, selected COM4 and boom.? Antscope2 not only launched but it connected!? ?I then scanned my 80m OCF successfully.

You can see the entire result including the graph at the virus free google photo link below.? In the upper left of the graph, you can clearly see that I am connected to Antscope 2 with the AA-54.



Unfortunately, for this first scan, I did not have the bands for America set.? I just did that, but, I will just leave the original image there.? ?

However, none of this is possible with Antscope2-1.3.0 because of the missing .dll (I think).? It will not launch.? ?At least for me.? ?

Thanks for your good responses Rick.? ?I think you can use the version of??Antscope2 v.1.2.6 as well.? You do have to install the FTDI drivers that enable generation of the COM port from the CD, cdm20824_setup-4.exe.? Once they are installed, and you might have to restart, check device manager to see if the COM Port has been generated.? If you only have one, then, just select that COM port in antscope, connect your AA-54 with a usb cable and you will see Antscope2 connect!

Mike

?

Rick,

Good questions all:

So, I uninstalled antscope2-1.3.0 and dropped back to the version I had installed on Windows in June for Field Day, v.1.2.6 which had worked with my AA-54.

I just finished installed that along with the program that came on the CD for the AA-54,?cdm20824_setup-4.exe, (FTDI drivers to generate a COM port from a USB device).??

I checked device manager and it showed COM4 for the AA-54.? ?Then, I installed Antscope2 v.1.2.6 and opened it, went into Settings in the lower left, selected COM4 and boom.? Antscope2 not only launched but it connected!? ?I then scanned my 80m OCF successfully.

You can see the entire result including the graph at the virus free google photo link below.? In the upper left of the graph, you can clearly see that I am connected to Antscope 2 with the AA-54.



However, none of this is possible with Antscope2-1.3.0 because of the missing .dll (I think).? It will not launch.? ?At least for me.? ?

Thanks for your good responses Rick.? ?I think you can use the version of??Antscope2 v.1.2.6 as well.? You do have to install the FTDI drivers that enable generation of the COM port from the CD, cdm20824_setup-4.exe.? Once they are installed, and you might have to restart, check device manager to see if the COM Port has been generated.? If you only have one, then, just select that COM port in antscope, connect your AA-54 with a usb cable and you will see Antscope2 connect!

Mike

?

[Edited Message Follows]

Rick, I do think I have the old software, however, I am running my old AA-54 on another Win 10 computer with Antscope 2.? ?I also ran the AA-54 on my old Windows 7 system with Antscope 2.? ?

Perhaps I installed something that I forgot to install now.? Let me look at the old disk.??

However, I was not trying to connect to the AA-54.? I was just running the software before I even tried to hook up the AA-54.? ?RigExpert software, as I recall, launched with or without access to the instrument.? Is that correct?

Thank you.??

Mike