Release Notes - Version 4.7
1. Version 4.7 issue of AviaDBM software includes communication via
USB, and facilities for uploading the Obstacle and VRP databases to units which
can accept them, either in native form or as a Batch of INTs. AOPA data can also
be listed.
2. GPS_USB is now fully working and tested on different combinations
of operating system and gps model. In addition to the facilities offered by
GPS_COM on the serial interfaces, GPS_USB includes the ability to upload VRP, Obstacle
or Terrain files from G496 updates. (It may also upload SafeTaxi and AOPA files
but nobody has tested this yet).
3. Apart from avdb image files, GPS_USB does not place any
restriction on which file you send to what unit, relying on the unit to
complain if it cannot accept the type of data chosen, or its size. For
instance, you can upload the European obstacles included in a G496 update to a
G96, G296, etc quite happily, whereas an attempt to upload a 221Mb terrain file
to a G296 will end in failure when the unit's memory becomes full.
4. Due to the changes in record format for G496 units, the
pre-compiled files sua.dat and tcc.dat in folder db45 are not transferable
between unit types. All the GEN programs recognise and report attempts to use
them in the wrong unit, so if you want to move their data (say from a 496 to a
296) you must Save them as ".all" text files using G496_GEN and
re-compile them with GPS_GEN. (These operations MUST take place without
changing the ISAM data).
5. New program GPS_OBS allows VRP, Obstacle and AOPA data to be
listed and saved in text format.
Obstacle and VRP data can also be saved in Batch format for use in units
which do not have these facilities. Editing and re-compiling is not possible
yet, while terrain and safe taxi are not accessible yet by this program.
6. GPS_OBS dumps obstacles as INTs with idents contrived to indicate
the max height amsl, while VRPs are dumped as INTs with idents built from their
descriptions. In both cases, where the generated ident conflicts with an
earlier one it is changed by altering the final character or characters as
necessary. These files are plain text and can be edited before applying them to
the ISAM database.
7. The SUA data of a G496 contains six new zone types, correcting
the anomalies seen recently in some European zones. Although these new SUA zone
types cannot be represented by earlier units, we think we have made a better
job of mapping them onto existing types, and non-496 GEN programs will make
these conversions if they find them in the data.
Release Notes - Version
4.6.6
1. A special version of GPS_GEN, G496_GEN is added to this issue.
This has been necessary due to the complete change of record formats introduced
to overcome the restriction in the total number of names, or more specifically,
the total length of the names table.
2. Following on from (1) above, all the GEN programs have been
updated to recognise the names table size limit. Previously if you added so
many names that the table became too long, the programs crashed. (Only one user
did this).
3. GPS_COM has been modified to upload G496 images, and their
co-located VRP/AirSports data, which takes the place of the loader segment
required by previous models.
4. "Brief" airports, being those with no runway direction
or comms frequency information, are handled better by the GEN programs.
Previously their City names were included in the city names index, which was
not strictly necessary. The large number of such items in the 496 database made
this shortcoming rather obvious.
5. GPS_DBM now allows the runway traffic pattern arrows to be set
to 'N' (absent) which I understand is valid on some units. Traffic arrows are
only available if the runway thresholds have been specified.
6. I have not added the G496 to the USR and Routes facilities of
GPS_DBM yet.
Release Notes - Version
4.6.5
1. New models 396 and iQue3600a are now supported.
2. GPS_GEN has the facility to create image files named
"0.dat", and for these files to have the unit serial number embedded
ready for hotsync to upload them to the iQue. The file should be placed in the
Palm\<userid>\Garmin folder for hotsync to find it, and you may find that
you have to do one normal Garmin update first. (Any previous cycle for which
you have a key will do).
3. UK Airways files in TNP format have taken a turn for the better,
as they now list only those parts of the airways which are "visible"
from the ground - just like the UK half-million charts. Program Convair has
been updated to handle the "points-only" format, and the new files
are included in the Batches folder.
4. The problem described in Documentation >
Compilation Errors > para 4b is still present in databases sold for the
GPS 92 and III Pilot, and is unlikely to be fixed before the units become
obsolete. The work-around is to treat them as obsolete already, and use a
database for a current unit.
5. An ISAM database created by GEN from affected updates will have
the corrupted names changed to **name ptr corrupt**, so that you can then make
a "clean" image if required.
6. GPS_DBM can now convert waypoint files between all models except
the iQue.
7. GPS_COM now reports the unit serial number correctly for all
units, and lists waypoint files from all unit types.
8. For users of serial ports higher than COM4, GPS_COM can be called
with a command line argument "-COMn" where 'n' is the required value.
This port will be added to the bottom of the dropdown list and pre-selected.
1. The main reason for this issue is that I have compiled everything
under Visual C++ version 6 instead of version 5. This will give me the ability
to write code for the USB interface in the future.
2. New models 296, 96, and 96C are now supported via their serial
interfaces. Their databases are identical to the 195/196/295 series.
3. Since the current models have standardised on the 195 format of
database, I have renamed G195_GEN to GPS_GEN which I hope is slightly less
confusing.
4. Most units have seven types of SUA(a) zones,
but the older models only use five of them. The remaining two types are
"Control Zone", and "Control Tower", and these types are
now converted to existing types "Control Area" and "Terminal
Ctrl" when creating an image for a 90 or 95.
5. The 96 and 96C have a new "Traffic Pattern" facility,
which takes the form of arrows which appear on the map display at the end of
each runway, indicating the normal circuit direction. Only runways with
pictures are affected, and it is not possible to omit these arrows, so every
runway direction is assigned either a "Left Hand" arrow or a
"Right Hand" arrow. Previous versions of AviaDBM correctly copied
this data, but assigned right hand arrows to new runways. GPS_DBM now allows
these arrow settings to be changed, and displays them in the form (L-R), (R-L),
(R-R), or (L-L) where the first letter refers to the low numbered end of the
runway.
6. SUA dumping and re-compilation had problems with areas which
cross the 180 meridian, a recent addition to the data. Version 4.5.4 fixed this
problem, but data dumped from previous versions still contain part of the
problem and have to be re-generated.
1. This version uses a modified ISAM database format which is incompatible
with the previous file format. To avoid confusion, the database directory name
has been changed to 'db45', and all the program names have had the final '32'
removed. If you need any data from an existing ISAM database in directory
'db32', you can use a version 4.4 program to dump it to a file which can be
re-input by version 4.5.
2. A significant bug in the ISAM library has been fixed, which was
responsible for strange happenings following some deletes. GEN Batch Updates
and DBM were affected, although image creation was not.
3. Create Image now allows you to exclude parts of the world by
specifying geographical limits, in the same way as for the compilation of SUA
and FSS/TCC sections. To make full use of this feature, you must first dump and
re-compile the SUA, FSS, and TCC sections applying the same limits, before
creating a new image, since these sections are kept in pre-compiled form. There
is also an option for including all the airports in the ISAM db, but only in
'brief' form if outside the chosen rectangle.
4. The GEN programs can now be run in automatic mode, by specifying
a Control File on the command line which contains all the runtime parameters.
The file format is explained in file C:\GPS\batches\GENcfexample.txt
5. RemDups can now be run in Control File mode also, see
DUPcfexample.txt in the same directory.
6. New program AutoGEN will create all the Control Files necessary to
create a world-wide ISAM database, and then make a new image using geographical
limits entirely of your own choosing (but see para 20 below). Instructions are
displayed when you run the program, which is a DOS type executable, and
currently creates a set of four control files and associated batch (.bat) files
to run the appropriate GEN program.
7. Records are no longer deleted from the ISAM database by the
CreateImage function, so that an image can be re-made with different limits
until the desired coverage is achieved. Names, countries, and waypoints remain
in the ISAM database even though they may not be included in the new image.
8. New function Compile APR Text is provided which reads approach
records and places the information in ISAM files. The text format is that
obtained when the approach section is dumped using SaveAs [*apr.all]. The text
file may be modified as required, and on re-input the information will be added
unless the approach exists, in which case the approach points are replaced.
9. There are two different formats in use for expressing lat/longs,
being Ndd~mm.mmm Eddd~mm.mmm for the main waypoint types and approaches, and
Nddmmss Edddmmss for the SUA, FSS, and TCC sections. In the former, the tilde
(~) character has been replaced by the degrees (°) character in all programs.
However, to retain compatibility with earlier listings, all input functions
(including dialog boxes) will now accept any of the characters hash, tilde, and
degrees ( # ~ ° ). The degrees character cannot be generated by a keyboard (as
far as I know), and has the value 0xb0.
10. Both of the co-ordinate formats are acceptable in GEN programs, but
DBM only accepts the dd~mm.mmm version.
11. The ISAM database is not opened by GEN programs until it is needed,
which means that more than one instance of a GEN program may be run provided
they are used only for listing image sections. A second benefit of this has
meant that the CreateISAM function, which starts by clearing the database, can
do this by deleting all the files instead of erasing every record.
15. Program dbview has been improved a little by the display of lat and
long as co-ordinates instead of semicircular units, and the inclusion of the
missing "lid" field in lwpt.dat. Searches on fields which are not the
primary index (top field) now search forward (or backward) for the same value
when a toolbar arrow is pressed, whereas previously they just displayed the
next record in primary index order. If no more records are found, the display
settles on the last record in the direction you were going.
16. The check on the number of countries in the database was
unnecessarily restrictive where it complained if a country serial number in the
ISAM file was >256. This situation can easily occur legally if you are
making images with optimised country tables, so the serial number check has
been removed.
17. The Listing flag in GEN programs has moved from the Compile Filters
dialog to the Setup dialog, thereby making it available to inhibit listings to
screen for Batch Update in addition to the Compile functions. Errors are still
reported when listing is inhibited, but you will probably then have to run the
operation with listing permitted to discover what the problem is exactly.
18. The Listing Filters dialog now has the same geographical limits
available as the Compile Filters dialog. You do have to remember when they are
set, because they do not appear in the bottom bar like the other filters.
20. There is a problem in the unit software which means that SUAs don't
work properly if the selected geographical inclusion rectangle has a large E/W
dimension. For instance, a rectangle including West Europe and East America
gives problems. There does not seem to be any N/S limit.
3. RWYs with an icon stripe value but not a full picture lost their
stripe value when dumped to text file, either normal or batch format. The
correct format for a stripe-only picture is 'xx 0000 00000000', and DBM and GEN
are changed to use this.
5. Unused names are no longer removed from the ISAM database when a
new image is created, although they are not included in the image unless
View/Optimise is switched off.
6. If an APT already had at least one full RWY description, a
'brief' RWY in a Batch update was added to the ISAM db when it should have been
ignored.
7. SaveAs file types have been modified and extended in the GEN
programs to:
Text [*.txt] Current scrollable screen in pain text
Batch [*bat.txt] Current scrollable screen in Batch format
Text Dump [*txt.all] All main waypoint types in
plain text
Batch Dump [*bat.all] All main waypoint types in
Batch format
SUA Dump [*sua.all] The whole SUA section in
re-compilable format
FSS/TCC Dump [*tcc.all] As for SUA, but FSS or TCC as
applicable
Approach Dump [*apr.all] The whole APPR section in
re-compilable format
Only appropriate types from this list are
offered, and the user's Filter settings are applied where applicable.
11. A new program "RemDups" is included, for removing
duplicated entries in sua.all, tcc.all, and apr.all text files. Although this
is primarily to overcome the problem of making a whole-world text file which
would contain many duplicated entries, it has in fact highlighted the presence
of duplicates in single databases. Entries are presumed to commence with three
characters chosen from "SUA", "FSS", "TCC", or
"APT". A summary is displayed, further files may be added, and a new
file is created at the user's request.
12. A new compile function is available in the GEN programs to convert
a tcc.all format file into a replacement for the tcc.dat file in the db32
directory, in a similar way to that already available for sua.dat files.
Although it would be possible to make changes to a tcc.all file, the primary
purpose of this compile facility is to enable the production of selected-area
databases, so the coordinate blocks associated with ARTCC centres are included
un-decoded. In fact, judging by the number of compile errors in existing Garmin
databases, the FSS and ARTCC data must be little used in practice. I also
intended to include a compile function for apr.all files, but this will now
have to wait for the next issue.
13. GEN programs now check that there are no more than 256 countries in
the ISAM db. This is a limitation in the manufacturer's image format which
might well cause problems in the future, for them as well as us. Currently they
use 252 of them.
1. SUA editing is here ! The GEN32 programs can re-compile a text
dump of the whole SUA section, making it possible for you to make changes using
a text editor.
2. Also included with this release is a program for converting TNP
format Airways files into 'sua.all' format for insertion into the SUA section.
Both these facilities are fully described in an accompanying "SUA
Manual", and a UK Airways.air file is included in the Batches folder.
3. In all programs, the Screen Font can be changed via a new View
Menu item, and the Printout Font via a new File Menu item. Only fixed pitch
fonts are permitted.
4. GPS_COM32 can now download and list Screen Dumps, although the
listing is only in hex at present. What is the point of that ? Well the
intention is to SaveAs these listings in Windows Bitmap [*.bmp] format, and in
fact this is working for the G3Pilot already. Other models will follow (some
may already work) when I receive some screen.gar files from their users -
contributions please !
1. GPS_COM32 is included for the first time. This program is a
complete re-write, and will operate at any baudrate between 9600 and 115200,
although many units will negotiate a maximum of 38400 baud. In the Setup
dialog, you choose the maximum your system can manage, so you have complete
control; if you get problems, try lowering the baudrate, shortening the cable,
or routing it away from electrical noise. If you choose 9600, or have a unit
which cannot change rate, then no attempts will be made to change it from 9600.
2. Uploads to the G295 and G196 have been changed to use the new
protocol only, and send a loader before the database, which is mandatory. A
copy of the original issue file (either .awp or .rg1) must be placed in the
same directory as your new image so that the loader can be extracted. Be
careful here, because the loader for the 196 and 295 is different, and .rg1
files do not specify which unit they were intended for.
3. The previous work-around for G295s, entailing the creation of
.rg1 and .rg2 files from the new image, had a bug which caused the upload
program to silently quit too early if the new image was longer than the
original. This facility remains available in G195_GEN32, and is fixed.
4. I am told that G3P units with software version > 2.10 (new
hardware units) upload the database with no problem if New Protocol is
selected. If this is proven, I could make this automatic.
5. When saving a file, the default extension is appended if you fail
to specify one. I hope I have found all the places in the package where this
was not done.
6. The Add APT Normal/Private/Military box in GPS_DBM32 now defaults
to Normal, and the WX checkbox can now be used to change the 'L' flag of an
NDB.
9. G195_GEN32 now silently removes approaches for which one
or more of the waypoints is absent. This allows you to delete INTs, NDBs, VORs,
and Runways using GPS_DBM32 or a Batch Update without causing the Create Image
function to crash because they appeared in an approach.
10. G195_GEN32 can be used for the new model 196, as well as 195 and
295, since they all use the same database (but NOT the same loader software !).
14. A File menu item has been added to all programs allowing the
internal debug value to be set/changed. Only registered users may set debug.
1. Most of the programs in this issue have been compiled in 32 bit
mode. They have the digits '32' as the last part of their name, and use an ISAM
database directory named 'db32'. This
means that they can co-exist with programs from an earlier issue, but naturally
require Windows 9x and above.
9. The 295 database upload protocol requires
the loader to supply some software before the database, and this is normally
held in the first part of the .rg1 file for 195/295 units, although it is only
used for uploads to a 295. G195_GEN32 has been given the capability to create a
pair of .rg files (.rg1 and .rg2) from an existing .img file.
10. To upload a new image to a 295 in this way,
you must have access to a copy of the manufacturer's floppy disk database
update, containing the updater program and an rg1 file. These should be copied
to your hard disk. Then in G195_GEN32 display the EPROM Header of the new image
file, choose File/SaveAs, and select the .rg1 file. You will see a dialog
describing exactly what is going to happen, and this should NOT ask if you wish
to overwrite the .rg1 file (if it does, you have made a mistake, so start
again). The floppy disks should then be recreated with the new .rg1 and .rg2
files, and the update run from there. Note that the floppy disk labels should
read UPDATE_DB for this software to function.
11. The USR and RTE facilities of GPS_DBM32 do not
work with .gar files downloaded from a 295 unit, due to a change of format.
GPS_COM may fail to list almanac.gar files, because nobody has sent me an
example.
2. G195_GEN (for 195 and 295 models) is now included in the main
download file. The program understands approaches, lists them, places the data
in the ISAM database, and remakes new images containing them. Unfortunately
there is no support yet in GPS_DBM for modification of the approach data.
4. Runway 'pictures' are now fully understood, and GPS_DBM displays
the underlying threshold coordinates and bearings, allowing you to make
additions and changes.
5. For people who like to convert data from one unit type to
another, the GEN programs will convert runways obtained from G3P and G195/295
databases into the old format for the remaining units. (The reverse is not the
case, however. Runway pictures from older units will be omitted when generating
images for the later ones).
6. DBVIEW is updated to display the new approach tables.
7. Single-ended runways, and runways where one end is not the
reciprocal of the other, are now handled correctly by GPS_DBM and all the GEN
programs. ISAM databases made by previous versions of the GEN programs will
still contain the errors.
8. The problem with mis-alignment of SUA 'Frequencies' information
after removal of a preceding APT is now fixed in all GEN programs.
9. For those of you who have purchased a database update from the
manufacturer's web site, you can obtain the underlying image file by running
WinZip 8.0 on the .exe file you downloaded and extracting the .awp file, which
your GEN program will convert into an image file the first time you view it.
Doc