DISE Screen Control

Note: This article is about the application "DISE Screen Control". For information about screen control in DISE Enterprise, please see Screen control#DISE Enterprise.

Overview

DISE Screen Control will communicate with a screen at a set interval. It has as its main tasks:

Checking if a screen is on or off.
Turning a screen on or off
Getting screen temperature.
Getting specified screen parameters.

While the application is called Screen Control, in fact control of a lot more than screens is possible:

Projectors
LEDs
Back projection setups.
Other devices that can be controlled in the same way as a normal LCD or Plasma screen.

DISE Screen Control may be used as a standalone application.

It is possible to communicate with the screen using these connections:

RS232

Note: It's important to determine the type of cable needed to connect the screen. Please consult your screen manual for information. If the connector on the screen is male you may need a null modem cable.

Read more: RS-232 - Wikipedia

TCP
UDP

Settings

General tab

Start Screen Control when Windows starts

Start the Screen Control application on Windows startup.

Start communication on program start

If enabled then the application will automatically start communication to the screen at program startup.

Minimize at program start

Application will start minimized in the system tray.

Connect to the screen interval

Number of seconds between connections to the screen.

It is only when connecting to the screen any status information, temperature values and on/off control will be processed.

DISE Complete status interval

Number of seconds between DISE Complete status updates.

The status, temperature or other properties of the screen will only be sent to the DISE Complete database at this interval.

Remote Control tab

Settings that will be used to receive multicast or UDP / TCP Remote Control messages on the network.

DISE Complete Settings

Setup the DISE Complete connection parameters.

Read more: DISE Complete integration

Communication Settings

Specify how the Screen Control application should communicate with the Screen.

Screen Setup

Screen Model

The model of the screen connected.

Name and Description

Will be visible in DISE Complete.

Library name and Description

Read only, will be available in DISE Complete.

Timeout

Number of seconds to wait before disconnecting or aborting connection.

Show debug information

Will show what is sent to the screen and what is being responded by the screen, to be used for debugging.

Control tab

Here you can control the connected screen's power state. If Screen state is set to Auto (schedule) you may define a power schedule for the screen. For example, you might want to turn the screen off at night between 10 PM and 6 AM.

Functions tab

Here you can select the functions that you want to run.

Advanced tab

Some screens have advanced options, for example to select what display id that should receive the communication in a daisy chain setup.

Supported screens

Model	Select ID	Control Power	Control Input	Read Status (Power)	Read Input	Read Signal Supplied	Read FW Version	Read Temperature	Additional
Hantarex	Yes	Yes	No	Yes	Yes	Yes	Yes	No	Read Model
JVC	No	Yes	No	Yes	Yes	No	No	No
KiSmart	Yes	Yes	No	Yes	Yes	No	No	Yes
LG	Yes	Yes	No	Yes	Yes	No	No	No
Mitsubishi	No	Yes	No	Yes	Yes	No	No	Yes
Mitsubishi Cube	No	Yes	No	Yes	Yes	Yes	Yes	Yes	TCP Support
Mitsubishi Projectors	No	Yes	No	Yes	Yes	Yes	Yes	No
NEC	Yes	Yes	No	Yes	No	Yes	No	Yes
NEC (API)	No	Yes	No	Yes	Yes	Yes	No	Yes	TCP Support
Panasonic	No	Yes	Yes	Yes	Yes	No	No	Yes
Pioneer	Yes	Yes	No	Yes	Yes	No	No	Yes
Projectiondesign	No	Yes	No	Yes	Yes	Yes	Yes	Yes	Read Scaling, Read Lamp 1/2 Status, Read Lamp 1/2 Estimated Remaining Time, Read Fan Speed, Read Serial Number
Samsung	Yes	Yes	No	Yes	Yes	No	No	Yes	Read Sensor States, Read Aspect, Read Brightness, Read Contrast, Read Color, Read Serial Number, Read Volume, Read Sound Mute, Read Sharpness, Control Volume
Sanyo	No	Yes	No	No	No	No	No	No
Sharp	No	Yes	No	Yes	No	No	No	Yes
Sony	No	Yes	No	Yes	Yes	Yes	No	No	TCP Support
ViewPia	Yes	Yes	No	Yes	Yes	No	No	No	Read Aspect

Screens that communicate using the same protocols as the ones above are of course supported.

Note: If you want to use an as-yet unsupported screen, please send us the RS232 or network communication spec for the screen/projector/LED and we can look at adding support for it.

Troubleshooting

If you are receiving Communication timeout messages then the problem probably lies with the cable connection or communication settings. Please refer to the screen manual for more information about what cable and settings you should have. Also please verify that no other application (or other instance of Screen Control) is not accessing the serial port at the same time.
If you receive Incorrect command reference message then you either have communication problems that are scrambling the data transmitted, or we do not support the whole or a part of the protocol.
If you only get above messages for some of the screen functions then it could be that said screen do not support these messages, or that there is a difference in protocol for these functions.
To gain more information about sent and received data please go into the screen settings and enable the "Show debug information" function. Then start the communication. Take a screenshot and send to us and we can give you more information.
It is important to make sure that the screen will accept any ID or Identifier that you configure in Advanced settings. If the screen is set to only receive messages directed to a certain ID then it may reject any messages not sent with this ID and you may get a timeout communication with the screen.