"Bob (VE5AG)" wrote in message ...
I tried the "vehicle.nec" and the "grdplane?.nec". According
to the notes, these models were converted to nec2 by K6STI.

No, that's not quite true. The original models were created by K6STI.
These models then were converted by myself to (4)nec2 models already
some years ago, using the 4nec2 program.

least right out of the box, they both produced errors. By looking at
the Validation log, these errors were associated with adjacent segment
lengths, or length to radius in segments. My question...since I am new
to Nec2 (but not to Elnec or Mininec), did I miss something in the Nec2
program setup, or do these (2) models not normally run without tweaking
them?

No, you did not miss something. When converting Antenna-Optimizer
files to (4)nec2 input files, 4nec2 used a maximum of 10 segments per
half-wave. For the vehicle file, this produced big changes in segment
lengths for the elements at the backside of the car, which in turn
could produce Nec-2 inaccuracies. To avoid this problem, you could
manually tweak the segment count(s) or length(s).

I made a slight change in the new 3.4 version, so in the near future
one is also able to specify the nr of segments per haf wave when
converting AO files.

Another workaround for this drawback is to convert the *.ant file,
then open the corresponding *.nec file using the geometry editor,
select the whole structure and move it a short distance to the left or
right. This way the segment counts for all elements will be
recalculated according the segment density as specified in the
'segmentation' option.

Concerning the GndPlane file the vertical element was originally
specified as 1 inch in diameter, the sloping elements are specified as
#12. The change in radius for these connected elements can produce
error's when used with Nec2.

**

Furthermore, thanks for the message, because this also anbled me to
detect and solve a bug, related to the use of temporary files on
windows-XP.

Greetings from the Netherlands,
Arie.