BARIX Instreamer Manuel d'utilisateur télécharger pdf (Page 7)

Technical Documentation “Instreamer “ - V4.03 - 24th October 2013

2.4 Principles of the CGI WEB interface

• The browser should support frames.

• Use GET method in forms.

• Respect the common character set for URL's.

• Example for CGI WEB commands: http://x.x.x.x/rc.cgi?c=84 (command for RESETTALK on Instreamer x.x.x.x)

2.5 Principles of the SERIAL interface

• Default settings of the serial control interface: 9600 baud, 8 data bits, 1 stop bit, no parity

• Each command must be terminated with an ASCII code less than a space 0x20 (like carriage return or/and line feed).

• If the command is correct and could be executed the answer OK is sent back with attached carriage return (ASCII 0x0D) and line feed (ASCII 0x0A).

• ERROR with attached carriage return (ASCII 0x0D) and line feed (ASCII 0x0A) is sent back when:

- a byte is lost

- an invalid syntax is used

- the time between two characters exceeds 10 seconds

- the command is unknown or can’t be executed

• There is no time to wait between two commands or characters.

• The serial connector pin out is described in chapter Error: Reference source not found Serial Port It's the same as on a standard PC 9pol. DSub.

• If IR once is used, the serial command interface can't be used anymore.

• If the serial gateway functionality is used, the serial command interface can't be used anymore.

2.6 Principles of the UDP command interface

• The standard UDP interface port for control commands is 12301.

• Each UDP packet must be terminated with a ASCII 0x00, ASCII 0x0D (carriage return) or ASCII 0x0A (line feed). If it is not terminated, the last

character will be discarded.

• If the command queue is full, busy.ack will be returned. This could happen if too many other commands are being executed at the same time.

7 Software Application Interface Software Application Interface 7

1 2 3 4 5 6 7 8 9 10 11 12 ... 38 39

Pas de commentaire

BARIX Instreamer Manuel d'utilisateur Page 7