Go to the source code of this file.
Defines | |
#define | ROT_MODEL_DUMMY ROT_MAKE_MODEL(ROT_DUMMY, 1) |
A macro that returns the model number for the dummy backend. | |
#define | ROT_MODEL_RPC ROT_MAKE_MODEL(ROT_RPC, 1) |
A macro that returns the model number of the RPC Network pseudo-backend. | |
#define | ROT_MODEL_EASYCOMM1 ROT_MAKE_MODEL(ROT_EASYCOMM, 1) |
A macro that returns the model number of the EasyComm 1 backend. | |
#define | ROT_MODEL_EASYCOMM2 ROT_MAKE_MODEL(ROT_EASYCOMM, 2) |
A macro that returns the model number of the EasyComm 2 backend. | |
#define | ROT_MODEL_FODTRACK ROT_MAKE_MODEL(ROT_FODTRACK, 1) |
A macro that returns the model number of the Fodtrack backend. | |
#define | ROT_MODEL_ROTOREZ ROT_MAKE_MODEL(ROT_ROTOREZ, 1) |
A macro that returns the model number of the Rotor-EZ backend. | |
#define | ROT_MODEL_ROTORCARD ROT_MAKE_MODEL(ROT_ROTOREZ, 2) |
A macro that returns the model number of the Rotor Card backend. | |
#define | ROT_MODEL_DCU ROT_MAKE_MODEL(ROT_ROTOREZ, 3) |
A macro that returns the model number of the DCU backend. | |
#define | ROT_MODEL_SARTEK1 ROT_MAKE_MODEL(ROT_SARTEK, 1) |
A macro that returns the model number of the SARtek-1 backend. | |
#define | ROT_BACKEND_LIST |
Static list of rotator models. | |
Typedefs | |
typedef int | rot_model_t |
Convenience type definition for rotator model. |
This file contains rotator model definitions for the Hamlib rotator API. Each distinct rotator type has a unique model number (ID) and is used by hamlib to identify and distinguish between the different hardware drivers. The exact model numbers can be acquired using the macros in this file. To obtain a list of supported rotator branches, one can use the statically defined ROT_BACKEND_LIST macro. To obtain a full list of supported rotators (including each model in every branch), the foreach_opened_rot() API function can be used.
The model number, or ID, is used to tell hamlib, which rotator the client whishes to use. It is done with the rot_init() API call.
|
Value: { \
{ ROT_DUMMY, ROT_BACKEND_DUMMY }, \
{ ROT_RPC, ROT_BACKEND_RPC }, \
{ ROT_EASYCOMM, ROT_BACKEND_EASYCOMM }, \
{ ROT_FODTRACK, ROT_BACKEND_FODTRACK }, \
{ ROT_ROTOREZ, ROT_BACKEND_ROTOREZ }, \
{ ROT_SARTEK, ROT_BACKEND_SARTEK }, \
{ 0, NULL }, /* end */ \
}
This is a NULL terminated list of available rotator backends. Each entry in the list consists of two fields: The branch number, which is an integer, and the branch name, which is a character string. |
|
A macro that returns the model number of the DCU backend. The Rotor-EZ backend can be used with rotators that support the DCU command set by Hy-Gain (currently the DCU-1). |
|
A macro that returns the model number for the dummy backend. The dummy backend, as the name suggests, is a backend which performs no hardware operations and always behaves as one would expect. It can be thought of as a hardware simulator and is very usefull for testing client applications. |
|
A macro that returns the model number of the EasyComm 1 backend. The EasyComm 1 backend can be used with rotators that support the EASYCOMM I Standard. |
|
A macro that returns the model number of the EasyComm 2 backend. The EasyComm 2 backend can be used with rotators that support the EASYCOMM II Standard. |
|
A macro that returns the model number of the Fodtrack backend. The Fodtrack backend can be used with rotators that support the FODTRACK Standard. |
|
A macro that returns the model number of the Rotor Card backend. The Rotor-EZ backend can be used with Yaesu rotators that support the extended DCU command set by Idiom Press Rotor Card board. |
|
A macro that returns the model number of the Rotor-EZ backend. The Rotor-EZ backend can be used with Hy-Gain rotators that support the extended DCU command set by Idiom Press Rotor-EZ board. |
|
A macro that returns the model number of the RPC Network pseudo-backend.
The RPC backend can be used to connect and send commands to a rotator server, |
|
A macro that returns the model number of the SARtek-1 backend. The sartek backend can be used with rotators that support the SARtek protocol. |