Scribd
Upload
40 views3 pages

BuildFile Instructions

The document provides instructions for writing build files that can be converted into Uniden GPS binary files. The build files use GPS coordinates and data to define alerts that are compiled into the binary files using WriteBIN software. The build files require a specific format including commands to define alert types like speed or red light cameras along with latitude, longitude, camera details, and other metadata separated by commas or semicolons on new lines. Comments can also be included to annotate the file.

Uploaded by

Omer Shenhav
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
40 views3 pages

BuildFile Instructions

The document provides instructions for writing build files that can be converted into Uniden GPS binary files. The build files use GPS coordinates and data to define alerts that are compiled into the binary files using WriteBIN software. The build files require a specific format including commands to define alert types like speed or red light cameras along with latitude, longitude, camera details, and other metadata separated by commas or semicolons on new lines. Comments can also be included to annotate the file.

Uploaded by

Omer Shenhav
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

Instructions for writing build files for conversion into Uniden gps

binary files.

These instructions provide a means of writing a file which uses more


comprehensible gps coordinates and data which can then be converted
directly into uniden binary. Mithheru’s own WriteBIN software program
using Mithheru’s BinLIB library (currently BinLib V8 last updated 24
September 2019) is the program that is used to read the file and build
the new database.

The requirements for the build file are as follows:

1) Create a plain or richtext text file. The very first line should have
"MODE US" and nothing else. All commands used in the file are case
sensitive.

2) Each command must start on a separate line and defines a new alert
to be built into the binary file. The commands all start with a ‘//‘

There are two main commands that can be used to build new camera
alerts:

“//kmh” - Builds a speed or redlight camera with units of km/h


“//mph” - Builds a speed or redlight camera with units of mph

Note: Even for redlight cameras, you need to choose one of these
commands to start the line, as the speed units need to be defined even
for a redlight camera.

3) For each of the above “//kmh” and “//mph” commands, the GPS
Coordinates come next and need to be specified in the order
Latitude,Longitude. These must be in digital format as an angle (i.e.
latitude goes +90.00 -> -90.00, longitude goes from -180.00 -> 180.00).
The complete file itself needs to be ordered by latitude from North to
South, so generally it is a good idea to order the data before you start.

4) The individual points of alert information for each command need to be


separated either by a comma (,) or semicolon (;).

5) After the gps coordinates, the camera type code comes next: ADRL =
All direction redlight; BDRL = Bidirectional redlight; MDRL = Mono-
directional redlight; ADSP = All directional speed; BDSP = Bidirectional
speed; MDSP = Mono-directional speed.
6) Next comes camera direction: This can be specified as N, NE, E, SE,
S, SW, W, NW (For ADSP and ADRL - do not specify the direction). Or can
also be specified as an exact angle in degrees using “D” followed by a
number. E.g. D15 = 15 degrees, D90 (due East), D355 = 355 degrees
etc.. The angle is measured from due North. D values must range
1-359. D0 and D360 are not allowed and will generate an error when
built (Use ’N’ instead).

7) The next variable to include is the speed limit (this sets the overspeed
alert). This has to be a number between 0 and 255 the units mph / km/h
are determined from the type of command which has been used. If its a
redlight camera alert do not put a number in here, just ignore this and set
the next variable.

8) If you are building from a previous file and you want to keep some
sequences of binary, these can be included and will be copied across into
the new file. However, these have to fit in the ordering sequence of
latitude. Mithheru’s other program BintoGPS can prepare a file with
binary and digital gps which can be used directly as the source of the new
WriteBIN file. Each line of binary being in Uniden format consisting of
four sets of 8hex characters. Lines of binary can also end with
comments. Generally this feature is for advanced users only and can be
ignored for many builds.

10) Special commands:

The latest version supports two new commands:

“//kcb” - Builds a copy of the previous camera alert at the same location
and direction but allows a different camera type to be added at the same
location (units of km/h).

“//mcb” - As above, but with (units of mph).

These commands should then include the details of the new camera alert
to be built at the same location e.g. “//kcb MDSP, 60” Would build a
mono-directional speed camera (60 km/h limit) at the same location as
the previous entry in the file (note these two commands can be applied to
the previous line which may be a //mph, //kmh command, or even a line
of binary.

These commands are therefore particularly useful if you know there is


already a camera at the location and simply want to upgrade it to do both
redlight and speed.

11) Comments: You can add comments into the file. Any line of
comments must start with a ‘**’.
You can also use a pair of commands //** and **// to mark a whole block
of text, paragraphs as part of a comment.

The following is an example can be used as a guide for creating the file
and formatting the data:

MODE US

** This is a test! This is a comment line marked with a **.


** Now lets get to the data:

//kmh 32.18519,34.93303,ADRL
//kmh 32.18069,34.93303,MDSP,D5,50
//mph 32.12345,34.34567,BDRL,SE
//mph 30.12345,-122.34567,BDSP,SE,100
1C5665B7 42474F06 E30451F3 580256FD This is a binary sequence with a comment
//mph 29.12345,-118.34395,MDRL,D122
//mcb MDSP,60

** That is the end of the example test file (another comment line).

//**

All of this next text is included


in a comment block and will be ignored by the build program!

**//

You might also like