Leica TPS1200 GeoCOM 参考手册 - CSDN文库

5星 · 超过95%的资源需积分: 9 157 浏览量更新于2024-07-23 收藏 1.02MB PDF 举报

"TPS1200_GeoCom_Manual 是一份关于Leica TPS1200系列全站仪的GeoCOM参考手册，主要针对GeoCOM的开发和使用进行详细阐述，适用于版本1.10。该手册涵盖GeoCOM的基础操作原理、通用概念、编程基础、通信设置以及不同应用模块的使用方法。" 正文: 这份GeoCOM参考手册详细介绍了Leica TPS1200全站仪与GeoCOM系统软件的集成和操作。GeoCOM是一个通讯平台，允许用户通过C/C++或VBA编程语言与仪器进行交互，实现自动化测量和数据处理任务。 1. GeoCOM的基本介绍在1.1章节中，手册介绍了GeoCOM的主要功能和目标，它是TPS1200系统软件的重要组成部分。1.2章节则详细讲解了TPS1200系统软件的特性，1.3章节概述了GeoCOM的操作原理，帮助用户理解其工作流程。 2. 通用GeoCOM使用概念这部分（2.1-2.5章节）提供了GeoCOM的基础使用指导，包括一般操作概念、ASCII协议、C/C++和VBA的功能调用协议。这些内容对开发者理解如何与仪器进行数据交换至关重要。 3. GeoCOM编程基础 3.1-3.7章节深入讨论了GeoCOM的编程技术，包括ASCII协议编程、C/C++编程语言的应用、VBA编程以及各种单位值的使用、仪器的操作模式和常见通信错误的识别与处理。 4. 描述的结构和注意事项 4.1章节解释了手册的描述结构，为读者提供阅读指南。4.2章节提醒用户在使用GeoCOM时应遵循的注意事项。 5. 通信设置 5.1-5.4章节详细描述了GeoCOM的通信配置，包括使用方法、常量和类型、通用GeoCOM函数以及客户端特定的GeoCOM函数。 6-8章节分别介绍了三个不同的应用模块：ALTUSER-AUS、AUTOMATION-AUT和BASIC APPLICATIONS-BAP，每个模块都包含其用途、常量和类型以及一系列可用的函数。 6. ALTUSER-AUS模块这个模块可能涉及用户自定义功能的实现，提供对仪器操作的扩展支持。 7. AUTOMATION-AUT模块该模块是自动化应用的核心，允许用户创建自动化测量程序，提高测量效率。 8. BASIC APPLICATIONS-BAP模块基础应用程序模块提供了基本的测量和数据处理功能，适合初级或标准的测量应用场景。总而言之，TPS1200_GeoCom_Manual是一个全面的参考资料，对于那些希望利用GeoCOM开发定制化解决方案或者提升TPS1200全站仪自动化能力的IT专业人士来说，它提供了必要的工具和信息。

GeoCOM Reference Manual Fundamentals of Programming GeoCOM

Leica TPS1200 – Version 1.10 16

Return-Code Value Description

GRC_COM_CANT_RECV

3076 Failure in receiving result. A failure has occurred during

reception of a packet at the data link layer. This could be due

to incorrect parameter settings or noise on the line, etc..

GRC_COM_TIMEDOUT

3077 Call timed out. The client has sent an RPC to the server but it

has not replied within the current time-out period as set for the

current transaction. This could be because: the server has not

received the request; the server has taken too long to execute

the request; the client has not received the reply; the

communication line (physical layer is no longer there; or, the

time-out is too short (especially true when communicating

over noisy or radio links at low baud rates).

GRC_COM_WRONG_FORMAT

3078 The request and receive formats are different. Something got

mixed up along the way or the application tried to send using a

format, which has not been implemented on both client and

server.

GRC_COM_VER_MISMATCH

3079 RPC protocol mismatch error. An RPC protocol has been

requested which does not exist. This error will indicate

incompatible client and server protocols.

GRC_COM_CANT_DECODE_REQ

3080 Can't decode request in server. If the client sends the server an

RPC but one, which cannot be decoded in the server, the

server replies with this error. It could be that the GeoCOM

versions running on the client and server are different or the

packet was not correctly sent over a noisy or unreliable line.

GRC_COM_PROC_UNAVAIL

3081 The requested procedure is unavailable in the server. An

attempt has been made to call an RPC, which does not exist.

This is usually caused when calling RPC’s, which have been

inserted, appended, deleted, or altered between the differing

versions of GeoCOM on client and server. To be on the safe

side, always use the same GeoCOM version whenever

possible on both sides.

GRC_COM_CANT_ENCODE_REP

3082 Can't encode reply in server. The server has attempted to

encode the reply but has failed. This can be caused by the

calling procedure trying to pass too much data back to the

client and in so doing has exceeded the maximum packet

length.

GRC_COM_SYSTEM_ERR

3083 Communication hardware error

GRC_COM_FAILED

3085 Mess into communication itself. Should be OK once the node

has been recycled, i.e. powered-down and -up again.

GRC_COM_NO_BINARY

3086 Unknown protocol. An unknown (or not yet supported)

Transport or Network protocol has been used. Could appear

when using differing GeoCOM versions on client and server.

GRC_COM_INTR

3087 Call interrupted. Something has happened outside of the scope

of GeoCOM, which has forced the current RPC to abort itself.

GRC_COM_REQUIRES_8DBITS

3090 This error indicates desired protocol requires 8 data bits

GRC_COM_TR_ID_MISMATCH

3093 Request and reply transaction ids do not match. Somewhere

along the line a packet (usually a reply) has been lost or

delayed. GeoCOM tries to bring everything back to order but

if this error continues during the session it may be wise to

inspect the line and, at least, to restart the session. The

immediately following RPC may be lost.

GRC_COM_NOT_GEOCOM

3094 Parse failed; data package not recognised as GeoCOM

communication package

GRC_COM_UNKNOWN_PORT

3095 Tried to access an unknown hardware port. The application

has not taken the physical resources of the machine on which

it is running into account.

GeoCOM Reference Manual Remarks on the Description

Leica TPS1200 – Version 1.10 18

4 REMARKS ON THE DESCRIPTION

This chapter contains some remarks on the description of RPC’s and on the structure of the descriptions.

4.1 STRUCTURE OF DESCRIPTIONS

The whole reference part is subdivided into sections. Each section contains descriptions of a set of functions, which

build up a subsystem. A subsystem gathers all functions, which are related to a specific functionality of a TPS1200

instrument, e.g. MOT describes all functions, which relate to motorization. Each subsystem is subdivided into the

descriptions of RPC’s.

4.1.1 Structure of a Subsystem

A subsystem consists of the following parts:

1. Usage

This part gives some hints about the usage of the subsystem and general information of its functionality.

2. Constants and Types

All subsystem specific constants and data types are listed here. Also their meanings are described if they are not

obvious.

3. Functions

All RPC’s of these subsystems are listed here and described in detail.

Note: To reduce redundancy the VB declarations of data types and constants have been omitted. Please refer to chapter

3.3 to get more information about this subject.

4.1.2 Structure of a RPC Description

One RPC description contains the following parts:

Title

Contains the name of the RPC and a short description of the function.

C-Declaration

Contains the C declaration of the function (excluding the return type).

VB-Declaration

Declares the function in VB (excluding the return type).

ASCII-Request

Describes the request including the input parameters and their data types listed in [ ].

ASCII-Reply

Describes the reply including the output parameters and their data types listed in [ ].

Remarks

Gives additional information on the usage and possible side effects of the function.

Parameters In/Out

Explains the parameters, their data types and their meaning. Parameters and their ASCII equivalent are explained

at the beginning of each chapter.

Return-Codes

Lists the most common RC to this request, in RC name and RC value.

See Also

Cross-references shows other RPC’s which relate to this one.

Example

Gives an example of how this RPC could be used.

剩余184页未读，继续阅读

skywalkermel

粉丝: 1
资源: 1

最新资源