• Date
    mcs
  • Date
  • Replies 2 replies
  • Subscribers 184 subscribers
  • Views 2200 views
  • Users 0 members are here

i/a RFR and partitions

Here's the control setup:

2-Rackmount Eos 4ks (primary/backup)
1-Ion (client)

Lots of cue lists/partitions for various control scenarios throughout the building (architectural installation).
Lots of programming to do, just one Ion to do it.

The bulk of the programming is a single architectural feature, which is partitioned out of the rest of the system.

So far, no one has been able to log onto the Eos with i/a RFR, we've only been able to log onto the client...

1) Is it possible to log onto the primary?  Seems odd that I can only log onto the client?

2) is a/i RFR limited to the same partition as the desk it is logged on through?

3) what happens if the primary is set to a different partition than the client? 

4) the key word "partition" does not currently exist in the macro editors command list... seems like should be there somewhere...

 

Thank you!

1.9.9

Parents

  • Hi there,

    Sorry for the delayed response.

    1. It sounds like there may be a different shell setting on the Eos console -- the Enable WiFi Remotes setting out in the shell (Exit -> Settings -> RFR) can be different from console to console, and isn't a system setting. Also double check that the console's name was typed correctly as the password, as this will also cause connection issues. This information can be seen in two places -- in the shell (Exit -> Settings -> General) or in About (Clear the command line -> About).  

    2. iRFR and aRFR do not use partitions at this time. Connection to a particular console in the system doesn't restrict the range of channels that can be selected or modified on a remote.

    3. Similar to #2 -- the Primary outputs for the entire rig, regardless of channels being in or outside the primary/master's partition. Partition restricts user control, not system control. 

    4. Partition should be a softkey in the Macro Editor -- I found it seven pages in, on the top row.  Also, it's possible to learn this as a macro, and then trim out the unnecessary keystrokes.  {Partition} x [Enter] should change the partition.

     

Reply

  • Hi there,

    Sorry for the delayed response.

    1. It sounds like there may be a different shell setting on the Eos console -- the Enable WiFi Remotes setting out in the shell (Exit -> Settings -> RFR) can be different from console to console, and isn't a system setting. Also double check that the console's name was typed correctly as the password, as this will also cause connection issues. This information can be seen in two places -- in the shell (Exit -> Settings -> General) or in About (Clear the command line -> About).  

    2. iRFR and aRFR do not use partitions at this time. Connection to a particular console in the system doesn't restrict the range of channels that can be selected or modified on a remote.

    3. Similar to #2 -- the Primary outputs for the entire rig, regardless of channels being in or outside the primary/master's partition. Partition restricts user control, not system control. 

    4. Partition should be a softkey in the Macro Editor -- I found it seven pages in, on the top row.  Also, it's possible to learn this as a macro, and then trim out the unnecessary keystrokes.  {Partition} x [Enter] should change the partition.

     

Children
Related

www.etcconnect.com