Leica tps1100 User manual

GeoCOM
Reference Manual
TPS1100 - Version 1.05
© 1997-2000, Leica Geosystems AG,
Heerbrugg, Switzerland

GeoCOM Reference Manual Contents
TPS1100 - Version 1.05 I
1GeoCOM..................................................................................................1-1
1.1 Introduction...............................................................................................1-1
1.2 TPS1100 System Software........................................................................1-1
1.3 Principles of GeoCOM Operation.............................................................1-3
2General Concepts of Using GeoCOM....................................................2-1
2.1 General Concept of Operation...................................................................2-1
2.2 ASCII Protocol..........................................................................................2-2
2.3 Function Call Protocol - C/C++ ................................................................2-4
2.4 Function Call Protocol - VBA...................................................................2-5
3Fundamentals of Programming GeoCOM............................................3-1
3.1 ASCII Protocol Programming...................................................................3-1
3.2 C/C++ - Programming...............................................................................3-5
3.3 VBA - Programming.................................................................................3-8
3.4 Units of Values........................................................................................3-13
3.5 TPS1100 Instrument Modes of Operation...............................................3-13
3.6 Common Communication Errors ............................................................3-16
4Appendix................................................. Fehler! Textmarke nicht definiert.
5Remarks on the Description...................................................................4-1
5.1 Structure of Descriptions...........................................................................4-1
6Communication Settings.........................................................................5-4
6.1 Constants and Types..................................................................................5-4
6.2 General GeoCOM Functions.....................................................................5-5
6.3 Client Specific GeoCOM Functions..........................................................5-8
7Alt User - AUS.........................................................................................6-1
7.1 Usage.........................................................................................................6-1
7.2 Constants and Types..................................................................................6-1
7.3 Functions...................................................................................................6-1
8Automation - AUT...................................................................................7-8
8.1 Usage.........................................................................................................7-8
8.2 Constants and Types..................................................................................7-8
8.3 Functions.................................................................................................7-10
9Basic Applications - BAP........................................................................8-1
9.1 Constants and Types..................................................................................8-1
9.2 Functions...................................................................................................8-3
10 Basic Man Machine Interface - BMM...................................................9-1
10.1 Constants and Types..................................................................................9-1
10.2 Functions...................................................................................................9-1

GeoCOM Reference Manual Contents
TPS1100 - Version 1.05 II
11 Communications - COM.......................................................................10-1
11.1 Constants and Types................................................................................10-1
11.2 Functions.................................................................................................10-1
12 Central Services - CSV..........................................................................11-1
12.1 Usage.......................................................................................................11-1
12.2 Constants and Types................................................................................11-1
12.3 Functions.................................................................................................11-3
13 Controller Task - CTL..........................................................................12-1
13.1 Functions.................................................................................................12-1
14 Electronic Distance Measurement - EDM...........................................13-1
14.1 Usage.......................................................................................................13-1
14.2 Constants and Types................................................................................13-1
14.3 Functions.................................................................................................13-2
15 Motorisation - MOT..............................................................................14-1
15.1 Usage.......................................................................................................14-1
15.2 Constants and Types................................................................................14-1
15.3 Functions.................................................................................................14-2
16 Supervisor - SUP ...................................................................................15-1
16.1 Constants and Types................................................................................15-1
16.2 Functions.................................................................................................15-1
17 Theodolite Measurement and Calculation - TMC..............................16-1
17.1 Usage.......................................................................................................16-2
17.2 Constants and Types................................................................................16-3
17.3 Measurement Functions ..........................................................................16-7
17.4 Measurement Control Functions ...........................................................16-22
17.5 Data Setup Functions ............................................................................16-26
17.6 Information Functions...........................................................................16-39
17.7 Configuration Functions........................................................................16-42
18 WI - Registration - WIR......................................................................17-1
18.1 Constants.................................................................................................17-1
18.2 Functions.................................................................................................17-1
19 Porting a TPS1000 Application............................................................18-1
19.1 RPC Changes...........................................................................................18-1
19.2 Data Types and Constants Changes ........................................................18-2
19.3 New Returncodes ....................................................................................18-3
20 GeoCOM Releases.................................................................................19-4
20.1 Release 1.04 ............................................................................................19-4
20.2 Release 1.05 ............................................................................................19-5

GeoCOM Reference Manual Contents
TPS1100 - Version 1.05 III
Appendix.................................................................................................A-1
AReturn Codes..........................................................................................A-1
A-1 General Return Codes ..............................................................................A-1
BHardware interface ................................................................................ B-1
B-1 Serial Interface ......................................................................................... B-1
B-2 Debugging Utility..................................................................................... B-1
CProvided Samples...................................................................................C-1
C-1 Settings for Terminal Emulator................................................................ C-1
C-2 Program Frames ....................................................................................... C-2
DList of RPC’s...........................................................................................D-4
D-1 Alpha order...............................................................................................D-4
D-2 Numeric Order..........................................................................................D-7
Microsoft, MS, MS-DOS, Windows, Windows NT, Win32, Visual C++ and Visual Basic
are either registered trademarks or trademarks of Microsoft Corporation in the USA and
other countries.

GeoCOM Reference Manual GeoCOM
TPS1100 - Version 1.05 1-1
1 GEOCOM
1.1 INTRODUCTION
TPS1100 series Theodolites are modern geodetic measurement instruments. Most
of the main tasks can be fulfilled with these instruments implicitly by their
integrated applications. Now, to fulfil a broader spectrum of tasks and applications
an interface to the TPS1100 series sensor functions has been defined and will be
published with this document.
With this interface it will be possible to write client applications based on MS-
Windows and/or for any other platform which supports ASCII based
communications.
1.2 TPS1100 SYSTEM SOFTWARE
The TPS1100 system software organises and controls the interplay of several
sensor elements. Furthermore, it builds up a frame for applications, which can be
executed on the TPS1100 Theodolite.
This document concentrates on the main interface to the sensor elements of the
TPS1100 Theodolite. This main interface can be used to implement solutions for
special customer problems if the already existing solution does not provide the
needed functionality or just to enhance it.
1.2.1 Organisation of Subsystems
The TPS1100 system software is built around the sensor elements, which are parts
and/or optional add-ons of the TPS1100 Theodolite instrument. It provides a set of
functions to access sensors and calculated values. These functions are organised as
subsystems. We will keep this segmentation in this document.
These functions can be grouped in the following sections:
AUS The subsystem ‘Alt User’ mainly contains functions behind the “FNC”
button.
AUT Automatisation; a module which provides functions like the control of the
Automatic Target Recognition, Change Face function or Positioning
functions.
BAP Basic Applications; some functions which can easily be used to get
measuring data.

GeoCOM Reference Manual GeoCOM
TPS1100 - Version 1.05 1-2
BMM Basic Man Machine; functions which controls some basic input/output
functionality, e.g. set beep alarm, etc.
COMF Communication; a module which handles the basic communication
parameters. Most of these functions relate to both client and server side.
COM Communication; functions to access some aspects of TPS1100 control
which are close to communication. These functions relate either to the
client side or to the server side.
CSV Central Services; this module provides functions to get or set
central/basic information about the TPS1100 instrument.
CTL Control task; this module contains functions of the system control task.
EDM Electronic Distance Meter; the module which measures distances.
MOT Motorization; the part which can be used to control the movement and the
speed of movements of the instrument.
SUP Supervisor; functions to control some of the general values of the
TPS1100 instrument, e.g. set the lower limit temperature.
TMC Theodolite Measurement and Calculation; the core module for getting
measurement data.
WIR WI Registration; this module contains function for GSI recording.

GeoCOM Reference Manual GeoCOM
TPS1100 - Version 1.05 1-3
Picture (1) - Overview Client/Server Application
1.3 PRINCIPLES OF GEOCOM OPERATION
Communication takes place between two participants - a client and a server. The
medium of communication is a serial communication line. Refer to Appendix B
for further information about settings and needed hardware.
The idea of GeoCOM is based on SUN Microsystems’ Remote Procedure Call
(RPC) protocol.
On the low level of implementation, each procedure, which is executable on the
remote instrument, is assigned a remote procedure call identification number. This
number is used internally to associate a specific request, including the implicit
parameters, to a procedure on the remote device. On this level, GeoCOM provides
system software
SUPBMM
MOT TMC
CSV
AUT
BAP
EDM
PC application
GeoCOM
server
inclination
sensor angle senso
r
distance
senso
r
motorization basic
in/out
COM
GeoCOM
client
COMF
Serial Line
TPS
PC
WIR
CTL

GeoCOM Reference Manual GeoCOM
TPS1100 - Version 1.05 1-4
an ASCII interface, which can be used to implement applications on platforms,
which do not support MS-Windows.
On the high level, GeoCOM provides normal function call interfaces for C/C++
and MS-VBA to these remote functions. These interfaces enable a programmer to
implement an application as if it would be executed directly on the TPS1100
instrument.
Note: Further on we will refer to a remotely executable system function as a
RPC.
The TPS1100 instrument system software uses a multitasking operating system.
Nevertheless, only one request can be executed at once. This means in respect of
calling RPC’s GeoCOM works synchronously only.
On the low level interface the server buffers subsequent requests if current
request(s) has not been finished so far. If the queue is full then subsequent
requests will be lost.
Instead on the high level interface a function call will not return until it has been
completely finished.

GeoCOM Reference Manual General Concepts of Using GeoCOM
TPS1100 - Version 1.05 2-1
2 GENERAL CONCEPTS OF USING GEOCOM
Here we will describe several aspects of using GeoCOM. One of them is how to
execute a function at a TPS1100 instrument.
The current implementation of GeoCOM supports two (three) kinds of usage. We
can distinguish between a rather rudimentary ASCII protocol and a high level
function call interface.
The former - ASCII protocol - is made up of requests and replies. Using GeoCOM
in this way means that an application assembles a request, sends it over the serial
line to the listening TPS1100 instrument, wait for the answer and decode the
received reply.
The latter uses normal function calls either in C/C++ or in VBA. For explanation
purposes we will split it into two categories because the two supported
programming environments differ in relation to their type systems. Using
GeoCOM in this way means calling a function. Any necessary communication
will be handled by GeoCOM implicitly.
2.1 GENERAL CONCEPT OF OPERATION
Fundamentally, GeoCOM is implemented as a point to point communication
system. The two communication participants are known as the client (external
device) and the server (TPS1100 instrument). One communication unit consists of
a request and a corresponding reply. Hence, one communication takes place when
the client sends a request to the server and the server sends a reply back to the
client.
Picture 2-1: Basic communication
GeoCOM is implemented as synchronous communication. A request/reply pair
may no be interrupted by another request/reply. Instead, a communication unit
must be completed successfully before a new communication unit may be
initiated.
Client Server
request
reply

GeoCOM Reference Manual General Concepts of Using GeoCOM
TPS1100 - Version 1.05 2-2
Although the ASCII protocol allows sending the next request before the
corresponding reply has been received, it is not recommended to do that. Of
course, subsequent request will be buffered when the previous request has not
been finished so far. But if the buffer content reaches its limit in size then data
may be lost.
Note: In the current implementation, only one communication channel per
session will be supported. Hence, only one instrument can be connected at
a time. Nevertheless, the nature of the ASCII protocol makes it possible to
connect and communicate to more than one instrument at a time.
2.2 ASCII PROTOCOL
In sequence we will define the syntax first and then give some information about
how to use the ASCII protocol to call a function on the TPS1100 instrument.
The ASCII protocol is a line protocol, hence it uses a line terminator to distinguish
between different requests (replies). One request must be terminated by one
terminator.
2.2.1 ASCII Protocol Syntax
Syntax of an ASCII request:
[<LF>]%R1Q,<RPC>[,<TrId>]:[<P0>][,<P1>,...]<Term>
Optional items are in brackets []. The angled-brackets <> surround names or
descriptions. These names have variable values depending on their types and
meanings. The angled-brackets themselves are not part of the transferred text.
Characters not surrounded by brackets are literal text and are part of the GeoCOM
protocol.
<LF> An initial line feed clears the receiver buffer.
%R1Q GeoCOM request type 1.
<RPC> Remote Procedure Call identification number in
between 0 to 65535.

GeoCOM Reference Manual General Concepts of Using GeoCOM
TPS1100 - Version 1.05 2-3
<TrId> Optional transaction ID: normally incremented from
1 to 7. Same value in reply.
:Separator between protocol header and following
parameters.
<P0>,<P1>,... Parameter 0, Parameter 1, ...
<Term> Terminator string (default CR/LF, use
COM_SetTerminator to change the terminator). As
a common shortcut ‘^m’ will be used in examples.
Example:
The following example uses the RPC TMC_SetPrismCorr to set the prism
constant on 34.4mm (‘^m’ denotes the terminator):
%R1Q,2024:34.4^m
Note: Additional characters at the beginning of a request, between parameters or
at the end are not allowed. They might lead to errors during interpretation.
Syntax of an ASCII reply:
%R1P,<GRC>[,<TrId>]:<RC>[,<P0>,<P1>, ...]<Term>
Optional items are in brackets []. The angled-brackets <> surround names or
descriptions. These names have variable values as described in the types they
have. The angled-brackets themselves are not a part of the communication text.
Characters not surrounded by angled-brackets are literal text and are part of the
GeoCOM protocol.
%R1P GeoCOM reply type 1.
<GRC> GeoCOM return code. This value denotes the
success of the communication. 0 = RC_OK means the
communication was successful (see table ‘GeoCOM
return codes’ in the appendix for further
information).
<TrId> Transaction ID - identical to that of the request. If
the request had no Transaction ID then it will be 0.
:Separator between protocol header and following
parameters.

GeoCOM Reference Manual General Concepts of Using GeoCOM
TPS1100 - Version 1.05 2-4
<RC> Return code from the called RPC and denotes the
successful completion if it is set to 0 (see table ‘RPC
return codes’ in the appendix for further
information).
<P0>,<P1>,... Parameter 0, Parameter 1, … These parameters will
be valid only if <GRC> is equal to 0 (RC_OK).
<Term> Terminator string (default CR/LF, use
COM_SetTerminator to change the terminator).
Example:
The following example shows the reply to the RPC 5008 -
CSV_GetDateTime.
%R1P,0,0:0,1996,'07','19','10','13','2f'^m
¦ ¦ ¦ ----------------------------
¦¦¦ ¦ The values for month, day, hour,
¦ ¦ ¦ +--- minute and second are replied in the byte-
¦¦¦ format (see table communication parameter
¦¦¦ for further information)
¦ ¦ +------ Return code from the RPC: 0 means no error
¦¦ (see RPC return codes for further information)
¦ +----- The Transaction ID of the request. If there was no ID
¦the value returned is 0.
+---- Return code from GeoCOM: 0 means no error (see
GeoCOM return codes for further information)
2.3 FUNCTION CALL PROTOCOL - C/C++
The implementation of GeoCOM for C/C++ conforms to normal function calls.
GeoCOM itself handles all necessary communication. No intervention of the
programmer in respect to the communication is necessary with one exception. If
the GeoCOM reports a communication error the programmer has to make sure that
either the problem will be solved - by calling GeoCOM support functions - or no
further RPC’s will be called - by terminating the running task.
Nevertheless, the programmer has to initialise GeoCOM and set up the port’s
settings to make sure that communication can take place. Moreover the user has to
make sure that the TPS1100 instrument is well connected.
Example:
An example code fragment for using TMC_GetSimpleMea could be the following.
We do not take care of the necessary initialisation and set up of GeoCOM here.

GeoCOM Reference Manual General Concepts of Using GeoCOM
TPS1100 - Version 1.05 2-5
Please refer to chapter 3.2.3 Basic GeoCOM Application Frame for C/C++ for this
information.
RC_TYPE RetCode;
TMC_HZ_V_ANG Angles;
double dSlopeDist;
RetCode = TMC_GetSimpleMea( 1000, Angles,
dSlopeDist,
TMC_AUTO_INC );
if (RetCode == RC_OK)
{// do something - use values
}
else
{// handle error
}
2.4 FUNCTION CALL PROTOCOL - VBA
Here almost all is valid for VBA as for C/C++. Please refer to Chapter 2.3. The
only difference between VBA and C/C++ is that VBA has a different type system.
Hence, the defined data types differ slightly in their definition. Furthermore,
because of implementation reasons the RPC names must have an additional prefix,
which is “VB_” for the current implementation of GeoCOM.
Example:
We take the same example as in Chapter 2.3.
Dim RetCode As Integer
Dim Angles As TMC_HZ_V_ANG
Dim dSlopeDist As Double
RetCode = VB_TMC_GetSimpleMea( 1000, Angles,
dSlopeDist,
TMC_AUTO_INC )
If RetCode = RC_OK Then
' do something - use values
Else
' handle error
End If

GeoCOM Reference Manual Fundamentals of Programming GeoCOM
TPS1100 - Version 1.05 3-1
3 FUNDAMENTALS OF PROGRAMMING
GEOCOM
We will describe how programs can be written using the different protocols.
Certainly, the type system, where the main differences lie between the protocols,
will be described in more detail.
3.1 ASCII PROTOCOL PROGRAMMING
Implementing an application, which uses the ASCII protocol, is based on simple
data transfers using a serial line. The programmer is responsible to set up the serial
line parameters of the client such that they correspond to the settings of the
TPS1100 instrument. Then Remote calls are done by just sending the valid
encoded requests and receiving and decoding the replies of them.
For debugging purposes, it might be helpful to use a so-called Y-cable, which
enables you to observe the communication on the serial line using either a
terminal or a terminal emulator. For further details see Appendix B-2 Debugging
Utility.
Note: If the settings of the active COM port will be set by any software part and
if the server is online, then it is strongly recommended to use a leading
<LF> to clear the receiver buffer at the server side. This will reduce
unnecessary error messages of the next RPC.
3.1.1 Data Types in ASCII Protocol
Each parameter of a RPC has its own associated data type with it. There are
varieties of different data types, which have been defined for the set of published
functions. The ASCII protocol supports simple data types only. All data types,
which are different from the base, types in name and aggregated data types are
converted and reduced to there base types. Conversion means to serialise the
aggregated data into a comma-separated list of its elements. Therefore, the
programmer has the responsibility to interpret the values depending on the
associated data type.
The supported base types and their value range are defined below:

GeoCOM Reference Manual Fundamentals of Programming GeoCOM
TPS1100 - Version 1.05 3-2
Format Type Valid range Len Valid input
representations Typical output representations
boolean 0 = false
1 = true 1 0,1 0,1
byte 0...255 2 (4) ‘00’,’FF’,’ff’,’7a’,
’A7’ ‘00’,’FF’,’ff’, ’7a’,’A7’
string - <512 ”abc\x0d\x0a” ”abc\x0d\x0a”
double ±2.225E-308...
±1.797E+308 17+3 1, 1.0, 1.0e4, -0.1e-07, -2 -0.1234567+e67
long (-231)...(231-1) 11 0x7FFFFFFF,
-54321 15, -154836, 900000
short -32768...32767 6 0, -1, -32700, 45, 56,
0x45e, 0X3AA 0, -1, -32700, 45, 56
unsigned
long 0...(232-1) 10 0xFFFFFFFF 0, 1, 3400065,
95735
unsigned
short 0...65535 5 0, 1, 34000, 65,
65535, 0x3a, 0x00,
0xFFFF
0, 1, 34000, 65,
65535
Table 3-1: Communication Parameter Types
Note: Bytes are always represented in two-character hexadecimal notation.
Hexadecimal notation can use upper- or lower-case representation: 0..9 + [a
.. f | A .. F].
Characters sent within a string which do not fall within the ASCII character
range 0x20 to 0x7E (32 to 126 decimal) are sent using an adapted byte
notation - e.g. ”\x9A”, where \x (or \X) introduces a byte value in
hexadecimal notation.
Types of integer (short, unsigned short, long, unsigned long) can also be
represented in hexadecimal notation, introduced by 0x or 0X.
The following rules are for generating/interpreting values with a type different
from the base types and aggregated data types:
Numerical and string data type
The numerical data types correspond to the C-parameters in value, range
and precision as close as possible. If no identical data type is available then
the next best one will be taken. Character and string will be replaced by the
string data type.

GeoCOM Reference Manual Fundamentals of Programming GeoCOM
TPS1100 - Version 1.05 3-3
Enumerations
If the corresponding C-parameter is an enumeration data type, then the
enumeration value of the ASCII parameter is equal to the implicit value of
the declaration of the C-data type. For clarification, we will give always the
name and the associated value in the description of an enumeration data
type.
Structures
Structure data types will be converted into a comma separated list of
elements. One element’s representation conforms to the data type
representation of its base type. If an element itself is a structure then depth
first conversion will take place. If this rule does not apply then the types
and their ASCII parameters are described explicitly.
Arrays
An array will be converted into a comma-separated list of elements. One
element’s representation conforms to the data type representation of its
base type.
Example for Enumeration Data Types and Structures
The following example gives a typical data type declaration and the
corresponding procedure declaration used in this manual for
TMC_GetSimpleMea from the subsystem Theodolite Measurement and
Calculation:
Constants and Types
typedef long SYSTIME;
struct TMC_HZ_V_ANG
{double dHz;
double dV;
}
enum TMC_INCLINE_PRG
{TMC_MEA_INC, // encoded as 0
TMC_AUTO_INC, // 1
TMC_PLANE_INC // 2
}

GeoCOM Reference Manual Fundamentals of Programming GeoCOM
TPS1100 - Version 1.05 3-4
C-Declaration
TMC_GetSimpleMea(SYSTIME WaitTime,
TMC_HZ_V_ANG &OnlyAngle,
double &dSlopeDistance,
TMC_INCLINE_PRG Mode)
ASCII-Request
%R1Q,2108:WaitTime[long],Mode[long]
ASCII-Response
%R1P,0,0:RC,Hz[double],V[double],dSlopeDistance[double]
Please, notice that the RPC has two input and two output parameters.
Anytime a request must encode and send input and in/out parameters only
and a reply must encode and send in/out and output parameters only!
Note: Unnecessary parameters must not be sent.
Although the enclosed header file com_pub.hpp denotes default
values for certain function parameters they will not be supported.
Hence, they have to be sent.
The ASCII Request to call this RPC with the value for WaitTime = 1000
and the inclination measure mode TMC_AUTO_INC has the following form
(note that the value 1 is used for the Mode parameter because the counting
of enumeration data types start at 0):
%R1Q,2108:1000,1^m
A possible reply can be as follows:
%R1P,0,0:0,0.9973260431694,1.613443448007,1.3581^m
Where the second and third value after the colon corresponds to the dHz
and dV parts of the structure TMC_HZ_V_ANG and the fourth value
corresponds to the variable dSlopeDistance. (Note that the first value
after the ‘:’ is not a parameter but the return code value of the RPC).
3.1.2 ASCII Protocol Program Example
For getting a feeling of how requests and replies are build up and work see also
the provided geocom.trm file in the samples directory. Please refer to Appendix
C-1 Settings for Terminal Emulator for further information.

GeoCOM Reference Manual Fundamentals of Programming GeoCOM
TPS1100 - Version 1.05 3-5
3.1.3 Modes of Operation Concerning Communication
Section 3.5 - TPS1100 Instrument Modes of Operation - explains the different
modes of operation of GeoCOM concerning communication. Similar to that the
following is valid for the ASCII protocol.
Since the client has to remind which mode is active, no support can be given from
the TPS1100 instrument. The only way to distinguish between modes is to remind
the actions an application has initiated and their resulting replies. So far no other
possibility exists to determine the current mode.
To switch on the instrument a single character is sufficient. It is recommended to
ignore the subsequent reply (one or two lines). Please note, that if the autoexec
mechanism ([menu] CONF - [item] Autoexec-application) is enabled then the
instrument will not switch into Remote mode, but will start the autoexec
application instead.
When turning into local mode the TPS1100 instrument sends the “sign-on”
message:
“%N1,0,255,,0%T0,0,0,:%R1P,0,0:0”.
If the “sign-off” message is enabled (see COM_EnableSignOff) then the
following message will be sent if the instrument goes into sleep mode:
“%N1,0,255,,0%T0,0,0,:%R1P,1,0:0,1”,
and the following message will be sent if the instrument shuts down:
“%N1,0,255,,0%T0,0,0,:%R1P,1,0:0,0”.
Please notice that these two messages are different in the last character.
3.2 C/C++ - PROGRAMMING
Programming in C/C++ is based on the well-known DLL concept, defined by
Microsoft Corp. To compile a project successfully first you have to include the file
com_pub.hpp, which defines all necessary constants, data types and function
prototypes. Second gcom100.lib has to be included in the project, which enables
the linker to resolve the DLL exported functions. To operate successfully the
gcom100.dll file must be accessible for the operating system, hence it must be
located in a directory which the operating system looks up for the requested DLL
file.

GeoCOM Reference Manual Fundamentals of Programming GeoCOM
TPS1100 - Version 1.05 3-6
Project Options GCOM100.lib
Structure byte-alignment 4 bytes
Memory model N/A
Special #defines (if not using MFC) STRICT
3.2.1 Data Types in C/C++
Since the main programming language of implementation of TPS1100 instruments
Firmware is C/C++ all data types are initially defined in C/C++. Therefore, no
conversion of values or data types is necessary.
3.2.2 Basic GeoCOM Application Frame for C/C++
A C/C++ GeoCOM application consists at least of the following parts:
- Initialise GeoCOM
- Open a connection to the server
- One or more GeoCOM RPC’s
- Close the active connection to the server
- Finalise GeoCOM
A sample implementation of above points could be:
// include standard system headers
#include "com_pub.hpp"
// include application headers
#define RETRIES_1 1
RC_TYPE RetCode;
BOOLE bOpenAndRunning = FALSE;
// initialize GeoCOM
RetCode = COM_Init();
if (RetCode == RC_OK)
{// open a connection to the TPS1000 instrument
RetCode = COM_OpenConnection ( COM_1, COM_BAUD_19200,
RETRIES_1);
if (RetCode == RC_OK)
{

GeoCOM Reference Manual Fundamentals of Programming GeoCOM
TPS1100 - Version 1.05 3-7
bOpenAndRunning = TRUE;
}
}
// optionally set up other comm. parameters here
if (RetCode == RC_OK)
{// -- functionality of the application --
// here we just test if communication is up
RetCode = COM_NullProc();
if (RetCode != RC_OK)
{// handle error
}
}
// close channel
if (bOpenAndRunning)
{RetCode = COM_CloseConnection ();
if (RetCode != RC_OK)
{// handle error
}
}
// anytime finalize and reset GeoCOM
RetCode = COM_End();
if (RetCode != RC_OK)
{// handle error
}
3.2.3 C/C++ Development System Support
GeoCOM system files have been developed using Microsoft Visual C/C++ 5.0.
Although this development environment were the basis for the current GeoCOM
implementation, it has been emphasised that it is independent of it, hence other
development environments can be used too. But please notice that it has not been
tested thoroughly so far.