Generic Command Responses

Cascade Driver for Hilscher Fieldbus CIF Cards: Version 4.1
Prev | Chapter 6. Configuration File and Command Specifications | Next

# 6.2. Generic Command Responses

The generic responses from a command are `OK` on success, and either `(error)` or `(error `cmd` `status` `status_desc`)` on failure. However, many commands will generate responses that are specific to the command, including error messages that are specific to the command and error.

More complex error responses have the following syntax:

        (error cmd_name error_code (time) error_text")

where:

`cmd_name`

  The name of the command generating the error.

`error_code`

  A signed integer value (see header files for the mapping from the error definitions to the actual error code returned).

`time`

  The time of the error, expressed as `yymmdd@hh:mm:ss`.

`error_text`

  The detailed description of the error, often including the field particular to the occurrence.

The command interpreter itself will also generate error messages if the command could not be successfully invoked. These include:

        (error "cmd_name ST_CMD_SYNTAX_ERROR (time) Command not found")
        (error "cmd_name ST_CMD_SYNTAX_ERROR (time) Bad parameter count: cmd_description")
        (error "cmd_name ST_CMD_SYNTAX_ERROR (time) Bad parameter count")

Prev | Home | Next
Configuration File and Command Specifications | Up | Summary of Reported Errors

Copyright 1995-2002 by Cogent Real-Time Systems, Inc.