New program version 650

[Bob]

This update has several significant new features:

1. A custom calibration procedure is available for special applications.
This allows the user to specify the frequency range over which the calibration
is done and also the spacing of the calibration points. This optimizes the
calibration for situations involving filters and complex transmission lines.
This procedure takes the place of 'ref to antenna method A'.
Method B is still available to use when it is not practical to calibrate at the far end of a cable.

A new section in the manual covers the custom calibration procedure in detail.

(The original calibration procedure still works the same and files with the
extension *.acal are still valid.)

2. The AIM can now be controlled easily by an external program. This makes it possible
to integrate the AIM with another program so it can be used as part of a
test system.

3. The last two scans are saved so you can flip back and forth between them with
the up/down arrow keys.

4. The crystal measurement routine has been improved and the data can be saved
in an Excel file. This makes it easier to match crystals that are used in filters.

5. Each trace on the graph can highlighted with special marks. This is especially
handy when graphs are printed in black and white. These marks are specified under
the Setup->Graph_Styles menu.

6. A comment can be entered when cal data or scan data are saved.

7. A status window (under the Help tab) displays file comments and pathnames.

8. The manual has been updated with information about these new features.

w5big.com/prog_update.htm

-- 73/ Bob

[Bob]

If you downloaded the new program early on Sunday morning Feb 3, you may notice a number in the upper left corner of the screen that increments continuously. This is related to the external control feature.

In the original zip package, the config file(s) had a parameter set to enable the external control. This doesn't hurt anything but it is distracting. To turn this off, edit the config file and change the following line:

3 external program control: 2=enable-don't display counter, 3=enable & show counter

TO:

1 external program control: 1=disable, 2=enable-don't display counter, 3=enable & show counter

Only the config file is involved, the exe file is ok.

I'm sorry for the mix up. This has been corrected as of Feb 3, 9:30am CST. If you download after this time, the counter is turned off by default.

73/ Bob

[dl4raj]

Hi Bob,

thanks for the new aim sw version.
I've notice several issues.
It doesn't cooperate properly with zplots any more
(zplots hangs),I've emailed about this also to Dan.

Distance to fault doesn't work any more with a shorted cable,
only with an open one (program hangs).
My older 623 version does both.

Another issue is that with a quite long RG58 line,about 74m
electrically long,the results of "distance to fault" and "measure cable" differ by about 3m which is essential.
This was also the case with my old version.

Any comments/help much appreciated.

73
Clemens
DL4RAJ

[Bob]

dl4raj said:

Hi Bob,

thanks for the new aim sw version.
I've notice several issues.
It doesn't cooperate properly with zplots any more
(zplots hangs),I've emailed about this also to Dan.

Distance to fault doesn't work any more with a shorted cable,
only with an open one (program hangs).
My older 623 version does both.

Another issue is that with a quite long RG58 line,about 74m
electrically long,the results of "distance to fault" and "measure cable" differ by about 3m which is essential.
This was also the case with my old version.

Any comments/help much appreciated.

73
Clemens
DL4RAJ

The file used to save the csv data should be called $AutoScan$.csv for Zplots.
You can change this in the config file. It's the "outputfile".
The config default puts it in a folder called C://temp but you can change the folder name.
It used to be put in the same folder with the exe file.

I'll take a look at the distance to fault problem and post an updata asap.
73/ Bob

[ac6la]

The following comment applies ONLY if you are using Zplots-AIM to control the AIM device. If you are using the standard Zplots program you can ignore this.

Zplots-AIM expects to find the $AutoScan$.csv file in the same folder as the main AIM program. That used to be the default location but now Bob allows the user to specify where the file will be placed. Therefore, in order to have the Zplots-AIM interface work correctly you must edit the AIM "default_config.cfg" file as follows:

Near the bottom of the file, change line

outputfile= C:\\temp\\$AutoScan$.csv output data csv file

to be

outputfile= xxx\$AutoScan$.csv output data csv file

where "xxx" is the folder that contains the AIM exe file. For example, if you have installed AIM_650.exe in folder "C:\AIM" then change the line to

outputfile= C:\AIM\$AutoScan$.csv output data csv file

Warning: Spaces are not allowed in this path name. Hence if you have installed AIM in, for example, C:\Program Files\AIM, you'll have to install it again in a different folder.

You can edit the "default_config.cfg" file using Notepad or, if you have AIM running already, you can use menu selection Help > Edit Config File. In either case it will be necessary to stop and then re-start the AIM software.

As before, if you have been using Zplots-AIM with a previous version of the AIM software and you install the new AIM software in a NEW folder, you should re-download a fresh copy of Zplots-AIM from www.ac6la.com/Zplots-AIM.zip. That is because Zplots-AIM "remembers" the AIM folder name. When you start with a fresh copy of Zplots-AIM you will be prompted to navigate to the correct (new) folder so that Zplots-AIM can "remember" it again.

Dan

[dl4raj]

Thanks, Bob and Dan!

Dan's detailed procedure works perfectly
but one has really to make absolutely sure that
the path contains not a single space in any folder's name
which is included in the path.


73
Clemens
DL4RAJ

[dl4raj]

Bob,

another "nice to have" feature which could be included in the next update is the possibility to save somehow the data which are created by the "measure cable" procedure .
This makes particularly sense when one compares the measured
antenna impedance in the shack with the results of a simulated line by a program like TLD (my favourite).
One needs the exact measured line parameters for the program otherwise the results may differ considerably.

73
Clemens
DL4RAJ

[k3ool]

Bob,
I'm trying to load a different config file in v6.50 and it causes the program to hang. I've tried to load the amradio_635.cfg from both the config files directory and the main directory and the result is the same. To terminate the program I must use taskmanager. I'm running windows xp pro. All the versions of the AIM4170 program up to 6.50 have worked just fine.

Any ideas?

73,
Craig K3OOL

[pa1pdr]

Nice to have a new version! I think there are some issues however.

When measuring a cable, I get different readings from 6.28 and also differences between open-short or short-open sequences. On a 50 ft RG58/U cable I get a loss of 0.153 dB/100m in V 6.28, regardless of open/short or short/open sequence.

If I measure the same cable in v6.50 however, it reports a loss (gain? ) of -0.015 dB/100m on a short/open sequence and -0.344 dB/100m on an open-short sequence.

A bug in 6.50?

Both versions report the same length differences on open/short vs short/open measurements:
o/s: 50.384 ft
s/o: 50.664 ft

Which one is right or is the truth in the middle

[k7buc]

On 650 or 628:
Using the "measure cable" function, it comes back in about 1/2 second as though its done its thing ok, but when the data is displayed, it shows a wild length. (like 625 feet or other random length). This seems to happen with my RG-8 jumper cable only. Its about 3.125 feet.
I've tried different frequencies, still doesn't work. No error message, just doesn't give correct results.
On this same cable, it seems to incorrectly compute the velocity factor also, so either way it fails. On other cables, no problem. Is there a 1 meter minimum length requirement for the cable functions? That would be a problem for stubs.
-Del

[k7buc]

Measure Cable function:
accidently enter a test freq that is outside the limits.
box pops up:
"WARNING! custom cal data point is out of range..."

Click OK

new box pops up:
"Cal problem 1254. The instrument needs to be calibrated"

Click OK
first box pops up:
"WARNING! custom cal data point is out of range..."

There is no way out of this loop except to kill the process via Windows Task Manager.
-Del

[Bob]

k7buc said:

Measure Cable function:
accidently enter a test freq that is outside the limits.
box pops up:
"WARNING! custom cal data point is out of range..."

Click OK

new box pops up:
"Cal problem 1254. The instrument needs to be calibrated"

Click OK
first box pops up:
"WARNING! custom cal data point is out of range..."

There is no way out of this loop except to kill the process via Windows Task Manager.
-Del

Right now in ver 650, the calok flag is set to zero when this error occurs. You can reload the cal file using File -> Load Calibration File

In the next update, I'll fix it so the calok flag does is not set to zero.

73/ Bob

[k7buc]

Ok, Bob, thanks.

Another issue.

I can't seem to set the Graph Style of Return Loss to anything except plain line. When I do, the line just disappears entirely until I set it back to plain line.
Is this intended?
-Del

[Bob]

k7buc said:

Ok, Bob, thanks.

Another issue.

I can't seem to set the Graph Style of Return Loss to anything except plain line. When I do, the line just disappears entirely until I set it back to plain line.
Is this intended?
-Del

I'm sorry this problem with RT was in the initial release. It's fixed now and the new update will be out soon.

-73/ Bob

[n9fyx]

I ran into something I believe is a problem. When you
startup AIM it displays the last scan, even if it wasn't saved
to a file. If you then do a swap file command, it seems to work
by getting the last file, but then if you swap again it toggles
back to the original trace but the file name of the previous
file is displayed, or junk is displayed sometimes. I also
had trouble saving the file once. It was when I left the
extension off, expecting that it would add the appropriate
extension. I haven't had time to try reproduce everything
very well, but thought you might be able to find it from this
description in time for the next release.