Leica TPS1200 Series Reference Manual page 17

GeoCOM Reference Manual
Return-Code
GRC_COM_CANT_RECV
GRC_COM_TIMEDOUT
GRC_COM_WRONG_FORMAT
GRC_COM_VER_MISMATCH
GRC_COM_CANT_DECODE_REQ
GRC_COM_PROC_UNAVAIL
GRC_COM_CANT_ENCODE_REP
GRC_COM_SYSTEM_ERR
GRC_COM_FAILED
GRC_COM_NO_BINARY
GRC_COM_INTR
GRC_COM_REQUIRES_8DBITS
GRC_COM_TR_ID_MISMATCH
GRC_COM_NOT_GEOCOM
GRC_COM_UNKNOWN_PORT
Leica TPS1200 / TS30 / TM30 – Version 1.50
Value Description
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..
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).
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.
3079 RPC protocol mismatch error. An RPC protocol has been
requested which does not exist. This error will indicate
incompatible client and server protocols.
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.
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.
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.
3083 Communication hardware error
3085 Mess into communication itself. Should be OK once the node
has been recycled, i.e. powered-down and -up again.
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.
3087 Call interrupted. Something has happened outside of the scope
of GeoCOM, which has forced the current RPC to abort itself.
3090 This error indicates desired protocol requires 8 data bits
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.
3094 Parse failed; data package not recognised as GeoCOM
communication package
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.
Fundamentals of Programming GeoCOM
17