Remote Client Help

[biffklg]

Can someone make up a quick how-to on how-to set up the remote client in Vixen 2.0 beta, or is it not fully implemented yet? I have been trying to figure it out on my own, but I am just spinning my wheels. I already have my 2 computers networked and they are seeing each other and I am able to transfer files back and forth, so that part is good.
Thanks for any help.

Ken

[KC]

I'll try to come up with something. The 2.0 version is different enough from the 1.1 version that it needs significant testing, but it should be complete.

What would you like to be doing with it?

[biffklg]

What I would like to do is be running Vixen and a light sequence on computer#1 and have that one linked to computer#2 running vixen for the ledtriks board. That way I could have the #1 computer tell the #2 computer to run "sequence#1" at a certain time during the light show and "sequence#2" at a certain time during the show ect. Is that the way it was intended to work or way it intended for internet based triggering?

[KC]

Somehow, this post got buried. Sorry, Ken.

I did get the HOWTO written up. It's funny that you ask what it's intended for because that's actually the first statement in it. The original intention of it was to coordinate remote execution of one or more Vixen clients. In other words, if you and your neighbors wanted to be part of the same show and you had no wireless options, it would help you coordinate that.

Joey's use last year with his Halloween site expanded it a bit to allow execution and channel control over the internet.

It looks as if it wouldn't serve your needs at this point, however.

[Dan Ross]

Where by chance is this How to located?

[jdamon]

I too am looking for the How To. I am very interested in making two computers talk Vixen to each other. As of yet, I haven't gotten very far.

[cmoneyster]

Has anybody been able to locate the HOWTO file yet? Thanks!

[KC]

Here is the quick-and-dirty I came up with back then, I believe it's still accurate. Documentation is not a skill of mine, so if it doesn't make sense I'll be happy to change it so that it does with some input.

[cmoneyster]

Thanks so much!! I'll look over it as soon as possible. Thanks again!

[Dan Ross]

Thanks KC. I'll try to play with it this weekend, but probably won't get to it till next week.

[FireGod]

I have been playing with the Reomte Client plugin and I guess I am doing something wrong. Can someone help me?

When I setup a deault profile with one serial port plugin of any kind, then set up the Preferences to use that profile for Remote Execution of Sequence Executions and Channel Control, then click the Remote Client Add-in menu selection to turn it on, I get two error messages back to back stating:
Access to port 'COM8' is denied

COM8 is the plugin port on my default profile.

If I start a sequence using ANY method, I get the message. If I turn off the Remote Client option, execution is normal. This error causes the sequence to not start until you click the OK buttons then the sequence start normally.

Has anyone else had this problem? Did I do something wrong?

[FireGod]

I messed around some more. I am unable to set any Remote Execution profiles, it will only use the default selection. I detached the profile from the sequence. I made a profile called Default and set it as the default profile. Somehow I got it to work but I am unable to reliably recreate the error.

I now need to discover how to run the remote client from a cold PC boot on both the server and clients then run a scheduled program. If I am on a business trip and we have a power failure, I need this stuff to work on its own.

[joeberg]

This sounds like the problem I reported earlier about not being able to set a specific profile for remote execution. I could tell it to use the profile in an open sequence and it worked fine. I believe KC has resolved this problem and it should be available in the next update.

The remote client starts up and connects automatically for me. Just make sure the Remote Client is Checked under the Addins menu. The problem though is that the server doesn't appear to start automatically when started. It would be nice if you could set an option (or use a CLI switch) to start it automatically.

Joe


I messed around some more. I am unable to set any Remote Execution profiles, it will only use the default selection. I detached the profile from the sequence. I made a profile called Default and set it as the default profile. Somehow I got it to work but I am unable to reliably recreate the error.

I now need to discover how to run the remote client from a cold PC boot on both the server and clients then run a scheduled program. If I am on a business trip and we have a power failure, I need this stuff to work on its own.

[GS]

Ok, so I''ve managed to connect both my systems, but how do I proceed? The howto is a bit vague on this. I assume this feature will allow me to hit 'Play' on one system and have both systems stay synced up, correct?

I just can't get any of my PCs to show under the 'Client control' menu. Help!