Sending TCP to Christie S+ 10k
-
I think you can use the hex PJ link commands which are close 25 31 41 56 4D 54 20 33 31 0D and open 25 31 41 56 4D 54 20 33 30 0D
-
Thanks! I have been trying all of these different iterations of the commands but am still not getting a response from the projector.Is there a way I can ping it to see if I am actually connected or not?I know the IP address, do I have to make sure that I set a manual IP address for my computer as well or something? -
One thing could be if you have set the IP manually for your network connection to the projector and use WLAN for the Internet there could be a problem because of the different IP ranges they are using. Try dissabling WLAN (if used for internet connection) and see if this helps.
Best Michel
-
You will want to make sure that the projector and your computer are in the same nework range like 192.168.0.xxx. You can always check your connection by putting the ip address of the projector in your web browser. If it works you'll get a Christy login window. You may need to disable your WiFi or change your network service order so ethernet is top of the list.
-
-
Update. Still not working, but:-
Set static IP manually on both the projector and the computer
-
Also made sure they were on the same subnet (192.168.0.xxx)
-
Turned wifi off
-
Ethernet 1 says "connected"
-
Saw that I am connected to the projector by typing the IP into the Firefox Address bar (I got the Christie login window)
-
Also confirmed by successfully pinging it via the terminal
-
Have made sure that I am connected to the projector via a network switch/router which I have verified as being functional, as per a suggestion I received elsewhere
-
Tried a number of formats for the TCP Commands (see attached photo)
-
I have seen a number of posts about other projectors saying you need to disable the password, but as far as I can tell, (after having gone through all of the menus), there is no way to set a password on this particular projector
-
I have contacted Christie Tech support. They said that the M Series of Christie projectors are not PJLink compliant. (Full email is attached as image).
-
They suggested connecting to the projectors via RS-232, but I'm trying to avoid physically touching the projectors at all costs because I really want to avoid having to do a whole show's worth of remapping for two projectors.
Questions:- Do I need to input something in the box for "Router" info in the Network preferences?
- Have been using the User Actor posted here by @cambrucedavis. It was created for PJLink, but looks like it should be able to do what I want in theory. (I think it does but, again I am brand-new to TCP.) Am I correct in thinking I can use this for my own purposes?
- Any thoughts on what I am missing?
Future Plans:- Currently I am branching out to investigate virtual machines to run Christie Powetool (their PC-only control software). (Another thing with which I am completely unfamiliar.)
- I have bootcamp on my laptop and feel that I can probably run Christie Powertool on my laptop and network it to my Mac Pro to trigger it through Isadora.
- I could also just network a windows laptop we have here with my Mac Pro and try that. (Though I am unsure of how to do this, and even if I did know, I am unsure of how to control Christie Powertool on another computer using Isadora.)
- Bang my head against a wall repeatedly.
- Commit seppuku with the projector remote.
Once I figure this out, I think it might not be a bad idea to create a Knowledge Base article on controlling projectors via TCP since it is SO crazy difficult to find information about this, not just with Isadora, but in general.(Seriously, googling "+projector +TCP" nets you a grand total of five hits. Five!)I will beat this thing, I swear it!Thanks everyone for the advice and help,Woland
-
-
Have you tried "(SHU1)" and "(SHU0)"
-
Looks like you have attacked this pretty well. I can't think of anything off hand to improve the setup. I will try to do the same with my Panasonic. . It won't be the same but perhaps I will find a related hurdle.
-
We finally got it working, but through QLab. I'm itching to try to do it through Isadora, but we simply do not have the time at the moment. To the best of my (limited) knowledge of networking, the issue was something to do with our ethernet switch, which did not have a DHCP server (or something). Our sound technician, who is very knowledgable about networking, plugged it into a spare router he had and got it up in running in about half an hour. I plan to post more details after the show is over and I have more time.
-
@WolandI
I am glad you found a solution in time for the show.It would be great if you could migrate the solution to Isadora and share it. As you pointed out there is very little information on these things availableIf the problem was hardware related, thats a tough one to pin down.
