Lumantek WEIVER 2.0 - Page 96

WEIVER 2.0 Manual
Weiver 2.0
/ Operations Manual
96
The contents in the below are the structure of API packets (ref.:WvPlayerRemoteAPI.h).
#dene WEIVER_PLAYER_ID 0x057b50b7
#dene WEIVER_PLAYER_API_RX_PORT 50504
#dene REMOTE_STRING_SUCCESS _T("Received")
#dene REMOTE_STRING_INVALIDE_PARAM _T("Invalid Param")
typedef enum _WvPlayerRemoteCMD_e
{
WV_PLAYER_REMOTE_CMD_SET_STRING,
WV_PLAYER_REMOTE_CMD_MAX
}WvPlayerRemoteCMD_t;
typedef struct _WvPlayerRemotePacket_t
{
unsigned int u4_ID;// WEIVER_PLAYER_ID
unsigned int u4_Reserved;//WV_PLAYER_REMOTE_CMD_SET_STRING
unsigned int u4_DataSize;
unsigned char u1a_Data[1000];
}WvPlayerRemotePacket_t, *WvPlayerRemotePacket_tp;
For controlling the WEIVER via API, an UDP Port (50504) has been opened. Hence, if data is added to
‘WvPlayerRemotePacket’ structure, the WEIVER program is running with these packet data.
These open sources are for Windows but can be applied to other OSs.
Before explaining the command list, we have ve conditions of the program (WEIVERRemoteAPI.exe).
1. IP address of the WEIVER is 192.168.100.1.
2. An opened port number for API control is 50504 (xed).
3. After sending packet to the WEIVER 1.0, a receiving port nuber is 50000 (variable).
4. One letter accounts for 2 byte respectively.
5. After sending the packet, ‘Time out’ occurs if there is no response.