EZNEC v. 6.0 Update List

This is a list of changes or of problems which were fixed in each EZNEC v. 6.0 update. Each update also contains all the changes listed below it. For example, 6.0.3 contains all the items listed for 6.0.3, 6.0.2, and 6.0.1 (the first revision). Updates for all EZNEC v. 6.0 program types are shown.

When wires were selected before choosing Split Wires and '1' was entered as the number of wires to split them into, the program would crash with Error 13 (Type mismatch).
[EZNEC Pro only]: Program would crash on startup (BSOD was reported) when running on Windows 10 version 2400. This revision installs an updated hardware key driver to correct the issue.

On some systems, v. 6.0.27 would repetitively report Error 76: Path Not Found at startup.

The only operational change is to the demo program: In EZNEC demo v. 6.0.24 - 26, when a model had exactly 20 segments and one or more virtual segments, running a calculation would result in Stop Error 225.

In Currents display, the end connection text would run into the magnitude data when wire numbers of single segment wires exceeded 99. This bug was introduced in v. 6.0.25 where connections to both ends of single segment wires were first shown.

Enabled Near Field analysis with MININEC-type ground.
Results from near H field analysis could be significantly in error when Real, High Accuracy ground was specified. This occurred only with NEC-2 calculating engines and not with EZNEC Pro/4 when using NEC-4.
The reported "Total" Near Field could be incorrect, with the error greatest when all components are equal in amplitude and not in phase. The error was negligible when one component dominated or components were approximately in phase. Note that this is now the correct RMS value of the total field which is not necessarily the peak value divided by the square root of two.
The Near Field Setup data entry order has been rotated 90 degrees to make the layout more consistent with other data entry dialogs.
When doing Near Field sweep with spherical coordinates, number of steps would be incorrect and azimuth wouldn't be stepped if the stop angle was less than the start angle and the step size was negative. Similar problems would occur in some other cases when the angle convention was compass bearing.
Connections to both ends of single segment wires are now shown in the Currents display.
Made a minor correction to the manual.

This version contained several bugs, one of which would cause a crash when the Undo feature was used. All known bugs were corrected in the v. 6.0.25 update. I apologize to those few people who downloaded an update or the demo program during the few hours this version was available.

Defective data were stored in .PF3 (3D trace) files, resulting in bare axes when viewing in TraceView, if 3D trace file was saved when the 3D window Highlight choice was Azimuth. Problem would also occur if saving was done after Azimuth choice was turned off, unless Elevation was selected afterward and before the plot was saved.
Improved smoothness of Wire Information window operation.
When the Angle Convention was changed in the Options Menu, the numerical value would stay the same; for example, if the compass bearing of the cursor was 30 degrees, the conventional (CCW from +X axis) angle would be 30 degrees after changing the angle convention. This resulted in the cursor or 3D elevation slice changing position. Now, the numerical value is changed so that the cursor position in a 2D plot and selected 3D elevation slice stay the same when changing the convention.
When elevation slices derived from a recalled 3D trace file were shown on a 2D plot, the indicated slice angle in the list at upper left didn't change when the angle convention changed.
When the primary trace and added traces are displayed in a TraceView 2D plot, the primary trace is now identified in the list at the upper left by the file name, like the other traces, rather than as "Primary". This change wasn't made when not in TraceView because the primary trace isn't necessarily associated with any file.
Made a number of minor changes, additions, and corrections to the manual.

When printing a plot to a PDF file (a printer choice in Windows 10), file selection window would continually re-open when Cancel was clicked. When printing text to a PDF file, an invalid error message would appear.
View Antenna wire operations (Add Conn Wires, Move Wire Ends) didn't work when Special Option WireInfoDist was set to -1 to make the Wire Info popup display open with <Ctrl>-right-click instead of hovering cursor.
Windows would always open on the primary monitor of multiple monitor systems, even if positioned on other than the primary monitor when last closed.
On some multiple-monitor systems the Wire Info popup would not appear if the View Antenna window was positioned on other than the primary monitor of multiple-monitor systems.
In the Wires Window, program would crash with Error 9 if the small button at the left of the add row (the empty row at the bottom of the grid) was right-clicked after a value was added to one of the columns of the add row and before the row was finalized.
Made additions and minor corrections to the manual.
[EZNEC Pro only]: Modified wire grid creation form to select text in boxes when they get focus or are double-clicked, like other EZNEC forms.
Increased the number of wire grid wires which can be created from 20,000 to 45,000. The total number of segments in a model is still limited to 45,000 for calculation.

When starting TraceView mode, displayed wire loss stayed the same as before TraceView was started, rather than showing the value in the opened trace file.
[EZNEC Pro only]: When displaying Far Field data in comma delimited format in locations where the decimal delimiter is a comma(,) some phase angles incorrectly were shown as zero.

Improved detection and reporting of folder and file access errors, particularly ones caused in Windows 10 by Controlled Folder Access.

In v. 6.0.15 - 17, an Error 5 (Invalid Procedure Call) crash would occur when used in locations where the decimal delimiter is a comma(,) when attempting to save an IONCAP/VOACAP file, and sometimes when showing data in comma delimited format. This revision has no effect when the program is used in locations such as the U.S. where a decimal point(.) is used as the decimal delimiter.

If a small (less than about 1/1000 of a segment length) change was made to a the coordinates of a wire end connected to other wires, the change was immediately reversed by EZNEC's automatic coordinate matching feature unless the changed wire was the lowest numbered one in the connected group. The changed coordinates are now applied to all connected wires regardless of the number of the changed wire, provided that Preserve Connections is off.
Numerous minor corrections were made to the manual.
[EZNEC Pro only]: NEC format files can now be opened by dragging and dropping onto EZWPro.exe or by including on the command line.
[EZNEC Pro only]: When reading NEC format files, some LD 5 (wire loss) "cards" weren't translated correctly. In particular, an LD 5 "card" representing wire loss included in a file saved by EZNEC Pro wasn't incorporated in the model at all.

Various system permission and other restrictions would cause crashes (usually Error 75 or 76) on startup. Also, Windows 10 was recently updated to allow the user to turn on a feature (Controlled Folder Access) which would cause these crashes by preventing EZNEC from writing into the Documents folder. The program now traps those errors and shows an error message explaining the problem rather than crashing. If the problem was caused by Controlled Folder Access in Windows 10, the user has the option of opening a web page which has instructions for preventing the problem.

In regions where the decimal delimiter is a comma (e.g., 6-1/2 is written '6,5'), an error message would appear preventing entering wire insulation thickness in any of the Custom value sets in the Wire Insulation Characteristics dialog. There is no change in program operation when used in the U.S. or other regions where the decimal delimiter is a period (e.g., 6-1/2 is written '6.5').

Program would crash (Error 401) if display polarization was changed between circular and linear in Desc Options when the FF Table window was open.
Reduced the time taken to format some numbers for display. This will be most apparent when viewing tabular 3D far field results with small step size. Note that some displayed results might differ from previous versions by one least significant digit due to changes in rounding routines.

Program would crash (Error 9) when Load Dat was clicked if model included a parallel-connected load with impedance magnitude less than 1E-10 ohms placed on a virtual segment.
New topic "Plus Octane Fill Up" added to the Test Drive chapter of the manual. It gives step by step instructions for creating a wire grid and other structures using EZNEC+ and shows how to use several EZNEC+/EZNEC Pro features.
Made some minor corrections and enhancements to the manual.

In EZNEC-generated Touchstone (.s1p) files, the last field of the first non-comment line of the header was changed from 50 (or alternate Z0 if set with Special Option S1PZ0) to 1 when the parameter type is set to Z (via Special Option S1PParamType). Unlike s-parameter values, impedance values are not normalized, so the appropriate field value is 1 rather than Z0 when tabulating impedances.
[EZNEC Pro only]: Program would crash with Error 5 when calculations were run on a machine having a 64 bit operating system and less than 2GB of reported total RAM.

In v. 6.0.7 - 6.0.11, when a phase angle was exactly 180 degrees, program would show zero degrees instead.
When segments at both ends of an insertion object were different lengths than the object's segment, no warning was given.
When Add Connecting Wires was selected in the View Antenna display, sometimes the New Wires Dia box caption didn't show the correct units (although the value in the box was interpreted as being in the correct units).
Resolution of the Stepped Diameter Correction (SDC) calculation has been improved so program now makes smoother SWR curves when SDC is being applied. This will result in slightly different results than before for models where SDC is used. This change does not apply to EZNEC Pro/4 when using an NEC-4 calculating engine because SDC is not needed or used with NEC-4 engines.

There are no operational differences between v. 6.0.10 and 6.0.11 for non-Pro program types.
[EZNEC Pro only]: Program would crash (Error 9) after reading an NEC format description file containing a GN "card" with first parameter 3 (NEC-4.2 Sommerfeld ground).
[EZNEC Pro only]: When installing EZNEC Pro on a 64 bit system in some dual boot installations having also a 32 bit system, 64 bit calculating engines wouldn't be installed. This resulted in error messages at program startup and inability of the program to continue.

When a 2D trace created as a "slice" of a 3D plot is saved, an incorrect Plot Angle (elevation angle of an azimuth plot or azimuth angle of an elevation plot) was saved in the file. The only effect is that the incorrect Plot Angle value will be shown in the main program window if the trace is opened in Trace View mode, and in the 2D data portion of the 2D Plot Window if the trace is added to a 2D display; none of the other trace values or characteristics are affected. Unfortunately there is no way to correct files saved with previous program versions and they will continue to show the incorrect values when opened.
[EZNEC+, EZNEC Pro only]: Specifying a color for the text (numbers) had no effect when done in the Smith Chart display. Note that color changes were and are common among all SWR display types -- for example, changing a color while viewing the Return Loss graph will also change the colors of the SWR, Reflection Coefficient, and Smith Chart graphs.

Insertion object placement test was being done only on end one of single segment wires containing an insertion object.
Changed color of insertion object placement warnings from red (warning) to orange (caution).
If the Wires Window was extended to show more wires and a wire was added at the bottom, the grid and window would snap back to the default height.
Printing a 2D plot would make the right hand column of data in the data box disappear from the screen display although it was printed.
Fixed bug that would very occasionally cause a "Type Mismatch" error message to appear only very briefly then prematurely ending the calculation.
Made minor revisions and corrections to the manual.
[EZNEC Pro only]: Program would crash when saving a description file if the model had more than 32,767 wires.
[EZNEC Pro only]: Program would give obviously incorrect results with some combinations of very large models and a large amount of installed RAM if the disk was being used for virtual RAM.

Improved detection and correction of missing directories encountered on some systems.
[EZNEC Pro only]: When using a plane wave source, necessary recalculation of currents did not occur when switching ground type between Perfect and Real, MININEC-type. No change was made to operation with conventional (V, I) sources where recalculation isn't necessary when switching between the two ground types.
[EZNEC Pro only]: Updated the hardware key driver which might be required for current Windows 10 revisions.

The phase angles of very small currents and voltages were sometimes incorrectly shown as 180 degrees instead of the correct phase angles in some displays.
Diameters of wires imported from an ASCII file weren't processed correctly when adding to the description. The diameters of the imported wires would be transferred to the first existing wires in the list and the diameters of the added wires would be incorrect.
[EZNEC Pro only]: On some 64 bit systems, an "Allocation error" message would appear when an attempt was made to run a calculation.
[EZNEC Pro/4 on 32 bit or XP systems only]: v. 6.0.4 - 6.0.6 updates were not updating 32 bit NEC-4 calculating engines, so various problems including no implementation of some bug fixes would occur if the original installation was prior to v. 6.0.5 and updates to v. 6.0.4 - 6.0.6 were applied.

Program would crash (Error 9) when splitting wires if the model contained any insertion objects placed on virtual segments.
Split Wires was incorrectly in the menu of several windows other than the Wires Window. Crashes would occur if an attempt was made to use it in those other windows.

Calculating engines and several DLLs were recompiled for better compatibility with some machines. There were no operational changes, and no need to apply this update if you are not encountering error messages at startup or when starting calculations.

Program would sometimes end with no error message or possibly show other errors when running a calculation where Stepped Diameter Correction (SDC) was being used. This did not affect NEC-4 engines with EZNEC Pro/4 where SDC is usually off.
Recompiled DLLs with latest compiler revision and replaced all run time dlls with updated versions to reduce rare compatibility problems.

In locales where a comma is used as the decimal delimiter, it was used as the delimiter in the frequency and alternate Z0 values in the .s1p files. This file correctly uses only a decimal point delimiter in all locales.
[EZNEC Pro/4 only]: Calculating engine error would occur when running an NEC-4 calculating engine if the EZNEC output file folder had been changed from the default.
When a wire under the ground produced a Segmentation Check warning, the maximum or minimum length shown in the message list was incorrect although the correct value was used for the check.
Some old description files did not automatically convert from High to Extended Accuracy ground when the automatic conversion option is in force.

Insertion object placement check modification in v. 6.0.1 failed to suppress some messages involving single segment wires with more than one object.
Several minor corrections made to the manual.
Installer now installs Microsoft Visual Studio runtimes when necessary. These are required for program operation on some Windows 8.1 and later operating systems.
[EZNEC Pro only]: Corrected problems which could produce errors on 64 bit operating systems.

Insertion object placement test showed errors when objects were placed on one-segment wires. An error is no longer shown when the object is a transmission line or more than one insertion object is on a one-segment wire. While placing objects on one-segment wires has not been necessary in most cases since the introduction of virtual segments, it shouldn't show a placement error.