Jump to content

Christie DHD800 - TPC Commands - URGENT


joeartist

Recommended Posts

I am working with WO 5 and trying to send TCP commands to 2 Christie DHD800 projectors, but getting no response from the projectors. 

 

 

Sending Command: C0D$0D & C0E$0D

on Port 3002

 

I also tried sending:

 

Commands:

SHUT1$0D & SHUT0$0D

 

SHU0$0D & SHU1$0D

 

Port 3001 and 10000

 

When I use telnet I have no problems sending the command C0D and C0E, (shutter mute and un-mute)

 

Any thoughts on why the projectors are not seeing the TCP command when sending through WO?

 

 

The network manual mentioned that the connection will be closed after 30 seconds. Do I need to send a command to open the port first and then send the shutter command?

 

Thanks!

Link to comment
Share on other sites

I have successfully been able to control the Christie DHD800 projector from WO.

 

Here is what I did:

 

Port 10000 TCP control

 

First String Command 0.300 from start of the aux timeline. Sending: Password and carriage return 

 

0000$0D

 

Second String Command 0.600 from start of aux timeline. Sending: Control command and carriage return

 

C0D$0D

 

Worked with no flaws. 

 

Here are the commands:

 

C0D - Close Shutter

C0E - Open Shutter

 

 

Hope this helps people. 

Link to comment
Share on other sites

  • 6 months later...
  • 2 weeks later...

I have successfully been able to control the Christie DHD800 projector from WO.

 

Here is what I did:

 

Port 10000 TCP control

 

First String Command 0.300 from start of the aux timeline. Sending: Password and carriage return 

 

0000$0D

 

Second String Command 0.600 from start of aux timeline. Sending: Control command and carriage return

 

C0D$0D

 

Worked with no flaws. 

 

Here are the commands:

 

C0D - Close Shutter

C0E - Open Shutter

 

 

Hope this helps people.

 

I also try this but still not respond

Link to comment
Share on other sites

  • Dataton Partner

When I get stuck with some control codes I always use a Telnet program, e.g. Hyperterminal, Putty,... to check the communication to the device. I do this from the production computer to see that the communication is not blocked somewhere in the system. Once the commands work from the Telnet program I use the same from WATCHOUT and usually I can make it work this way.

 

The benefit of using a Telnet program is that you can also see the responses sent from the device you're trying to control. This sometimes gives you valuable hints too. 

Link to comment
Share on other sites

  • Moderator

When I get stuck with some control codes I always use a Telnet program, e.g. Hyperterminal, Putty,... to check the communication to the device. I do this from the production computer to see that the communication is not blocked somewhere in the system. Once the commands work from the Telnet program I use the same from WATCHOUT and usually I can make it work this way.

 

The benefit of using a Telnet program is that you can also see the responses sent from the device you're trying to control. This sometimes gives you valuable hints too. 

 

x2 very sound advice thumbsup.gif

 

Just remember whenever you hit the key in Telent

you add $0D (hex value for carriage return) in the WATCHOUT string.

 

Using Telnet also makes it easier to communicate and solve issues

with the controlled device's  manufacturer's support.

They usually know little about WATCHOUT (nor should they)

but they all understand Telnet communication.

 

On Production Computer I use Windows 7 built-in command line Telnet.

Windows 7 standard command line Telnet is always on the comptuer,

but can be disabled - Windows default.

It can be re-enabled without any external media, no external connection via 

Control Panels - Programs & Features - [Turn Windows features on or off]

once the list populates, scroll down and

check [Telnet client]

 

At

Start - All Programs - Accessories - Command Prompt

type

telnet

there is a space between telnet and IP address

and a space between IP address and port number

and you should connect, allowing you to type commands to test.

 

Note, the Windows Telnet tool sends every key as its hit, i.e. there is no backspace.

So if you make an error in typing, hit enter to error and clear - start again.

Backspace will appear to work on screen,

but the device typically just sees the backspace as another keystroke

and does not backspace in its buffer. 

 

BTW My favorite Telnet test tool is MacOS built in Terminal application.

Type the MacOS Terminal command to start Telnet the exact same as the Windows Telnet example above.

The difference is, MacOS Terminal / Telnet does not send each keystroke as it is typed,

it buffers them and sends the entire line as a block when return is hit. i.e. you can backspace

you can also copy and paste ;)

Link to comment
Share on other sites

  • 2 weeks later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...