PTZ-camera control. Protocol Pelco-P

Pelco, Pelco-P, PTZ, протокол

In the previous article I was considered an option to work with Pelco-D protocol, and now look to work with Pelco-P protocol - a modified variation of the previous PTZ-camera control protocol, which is also developed by the same name by Pelco. Also used over the RS482 / 485 interface for communicating with cameras equipped with servo drives.

Pelco-P protocol also has a set of standard commands, as well as advanced instruction set. Let us consider how we can work with standard commands. Protocol Pelco-P Let us examine the example of the abstract and the abstract command source SDK, which receives the message for onward transmission to its RS485 interface.

Therefore there is a protocol by which data is transmitted, and further understand the data transmitted to the SDK, which sends a message already in the RS485 transmission path. Below is a picture in which there is a yellow square. It is in this function and will form the necessary us the message you want to convey in the SDK.

Message Structure

The checksum is the sum for the exclusive OR, ie XOR, byte from the 1 st to 7 th. As you can see in this protocol using 8 bytes to transmit the message, instead of 7, as in Pelco-D.

It should be noted that the protocol Pelco-P addressing starts with 1 and 0. That is, the first address will be transmitted as #00, but the most interesting is that the PTZ camera settings, the address will be listed as 01, it is necessary to consider this point when developing layer for a given protocol.

PAN and TILT commands

Examples of commands

Rotation to left: A0 00 00 04 20 00 AF 2B
Rotation to right: A0 00 00 02 20 00 AF 2D
Tilt up: A0 00 00 08 00 20 AF 27
Tilt down: A0 00 00 10 00 20 AF 3F
Stop all activities: A0 00 00 00 00 00 AF 0F

Sample code

In this abstract code was created in a vacuum, such a situation that the function of these values fall:

• address;
• PanSpeed - rotation speed with the direction, from - 100 to +100;
• TiltSpeed - Tilt speed with the direction, from -100 to +100;
• ZoomSpeed - Zoom speed with direction, from -100 to +100. Why so submitted data for Zuma - is a question for me, given that Pelco is no speed setting, but that is what it is.

But SDK has already formed a team takes a pointer to an array of data, and an indication of the length of the array. The result is the following code.

void ptzCmd(int addressPTZ, int panSpeed, int tiltSpeed, int zoomSpeed)
{
    unsigned char *dataPelco;
    unsigned char address, data1, data2, data3, data4, checkSum;
    address = data1 = data2 = data3 = data4 = checkSum = 0x00;

    dataPelco = (unsigned char*) malloc(8);
    memset(dataPelco,0,8);

    address = (unsigned char)addressPTZ;
    --address;
    if(pan < 0) {
        data2 |= 0x04;
        pan *= (-1);
    } else if(pan > 0) {
        data2 |= 0x02;
    }
    data3 = pan*63/100;

    if(tilt < 0) {
        data2 |= 0x10;
        tilt *= (-1);
    } else if(tilt > 0) {
        data2 |= 0x08;
    }
    data4 = tilt*63/100;

    if(zoom < 0) {
        data2 |= 0x40;
    } else if(zoom > 0) {
        data2 |= 0x20;
    }

    checkSum ^= 0xA0;
    checkSum ^= address;
    checkSum ^= data1;
    checkSum ^= data2;
    checkSum ^= data3;
    checkSum ^= data4;
    checkSum ^= 0xAF;

    dataPelco[0] = 0xA0;
    dataPelco[1] = address;
    dataPelco[2] = data1;
    dataPelco[3] = data2;
    dataPelco[4] = data3;
    dataPelco[5] = data4;
    dataPelco[6] = 0xAF;
    dataPelco[7] = checkSum;

    sdk_write_pelco_cmd(8, dataPelco); // 8 - length of message
    free(dataPelco);
}