Leica TPS1200全站仪GeoCOM接口操作手册：实现精准测量与控制

5星 · 超过95%的资源需积分: 46 199 浏览量更新于2024-07-26 2 收藏 1.42MB PDF 举报

本资源是一份关于徕卡全站仪（Leica TPS1200+、TS30/TM30）的GeoCOM接口操作手册，版本1.50，英文版。这份详细的文档涵盖了GeoCOM技术在Leica全站仪中的应用，特别是如何通过GeoCOM接口实现第三方设备对测量仪器的控制，从而达成测量目标。 1. **GeoCOM介绍**: - GeoCOM是Leica TPS系列全站仪的一种通信接口，它允许与外部设备（如计算机或其他测量设备）进行交互，通过ASCII协议或C/C++/VBA函数调用接口实现数据交换和命令发送。 - 操作原理包括系统软件的设置、命令和数据的传输方式，以及不同编程语言接口的使用方法。 2. **通用概念与编程基础**: - 用户指南介绍了GeoCOM的一般操作概念，包括接口的工作流程，如何编写和理解ASCII命令，以及C/C++和VBA两种编程语言的函数调用规则。 - 编程部分强调了单位转换、仪器操作模式的理解，以及可能遇到的通信错误处理。 3. **特定功能模块**: - 提供了两个实用功能模块：AltUser-AUS38和Automation-AUT43，分别针对不同的应用场景。 - AltUser-AUS38可能涉及高级用户自定义功能，包括常量和类型定义，以及一系列功能的实现。 - Automation-AUT43则聚焦于自动化操作，如任务取消和功能执行，同样提供了相应的常量、类型和函数列表。 4. **基本应用示例**: - BAP（Basic Applications）部分展示了如何将GeoCOM技术应用于实际测量工作中的基础场景，帮助用户理解和实践GeoCOM在测量作业中的实用性。 5. **通信设置与参数**: - 文档详细解释了如何配置通信参数，包括通用GeoCOM功能和客户端特定的设置，确保设备间的有效连接。这份手册是莱卡全站仪用户和开发人员的宝贵资源，它深入讲解了GeoCOM技术在Leica TPS系列仪器中的运用，为用户提供了一套完整的通信和编程指南，无论是基础操作还是高级应用都能从中获益。通过遵循其中的步骤和指导，用户可以高效地利用GeoCOM来提升测量工作的精确性和效率。

GeoCOM Reference Manual Fundamentals of Programming GeoCOM

Leica TPS1200 / TS30 / TM30 – Version 1.50 16

Dim s As String

' initialise string

s = Space(255)

Call VB_COM_GetErrorText(GRC_IVPARAM, s)

' trim string, justify string length

s = Trim$(s)

Note: Incorrectly handled string output parameters may lead to severe runtime problems.

3.5 UNITS OF VALUES

All parameters are based on the SI unit definition, if not explicitly indicated differently. The SI units, and their

derivatives, used are:

Abbreviation

Unit Description

M ( Meters ) for lengths, co-ordinates, ...

Rad ( Radians ) for angles

Sec ( Seconds ) for time

Hpa ( Hekto Pascal ) for pressure

C (Celsius ) for temperature

Table 3-2: SI Units

3.6 TPS1200 INSTRUMENT MODES OF OPERATION

In respect to communication, the TPS1200 instrument knows several states in which it reacts differently. The main state

for GeoCOM is online state or mode. There it is possible to use all RPC’s, which are described in this manual.

Especially we will describe the possibilities of changing the state by the built-in RPC’s. For the ASCII protocol refer to

section 3.2.3 - Modes of Operation Concerning Communication.

The possible states can be described as follows:

Off The instrument is switched off and can be switched on using

COM_OpenConnection. To switch on the

instrument a single character is sufficient.

GeoCOM The instrument accepts RPC’s. To switch into GeoCOM mode start the “Configuration” menu on the

instrument, open the submenu “Interfaces” and enable interface “GeoCOM Mode”.

RCS The instrument accepts Remote Control sequences.

3.7 COMMON COMMUNICATION ERRORS

GeoCOM is based on calling functions remotely. Because of the additional communication layer the set of return codes

increases with return codes based on communication errors. Since all of these codes may be returned by any RPC we

will explain them here and omit them in the descriptions of the RPC’s.

Return-Code Value Description

GRC_OK

0 Successful termination, implies also no communication error.

GRC_COM_CANT_ENCODE

3073 Can't encode arguments in client. Returned by the client to the

calling application directly, i.e. without anything being sent to

the transport layer and beyond.

GRC_COM_CANT_DECODE

3074 Can't decode results in client. Once an RPC has been sent to

the server and a reply has been sent back, this return code

states that the encoded reply could not be decoded in the

client. This is usually the result of using different versions of

GeoCOM on client and server.

GRC_COM_CANT_SEND

3075 Failure in sending calls. If the resources at the transmitting

port have been allocated previously, i.e. GeoCOM does not

have exclusive rights to the port, or if the exception or similar

routine has experienced a failure, this error code is returned.

GeoCOM Reference Manual Fundamentals of Programming GeoCOM

Leica TPS1200 / TS30 / TM30 – Version 1.50 17

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 / TS30 / TM30 – Version 1.50 19

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.

Leica TPS1200全站仪GeoCOM接口操作手册：实现精准测量与控制

莱卡全站仪TS30 / TM30 二次开发手册及软件详解

TPS1200系列测距仪接口手册：GeoCOM功能详解

TPS1200系列经纬仪GeoCOM接口中文指南

TPS1200_TS30_TM30_GeoCOM_Manual.rar_TM30通讯_TPS1200_TS30_TM30__ge

TPS1200_TS30_TM30_GEOCOM_MANUAL_GeoCom_莱卡通讯协议_

TPS1200、TS30、TM30_Simulation.zip

莱卡TS30 / TM30 二次开发手册

TS30/TM30测量机器人变形监测系统研究 (2014年)

TM30 GeoCOM说明书英文版v1.5

TS30测量机器人Geocom中文说明书.docx

最新资源