User manual

Phoenix
32
User Manual www.RealmCtrl.com
114
14. Appendix A: Control Logic Descriptions
This appendix describes the behavior of the source Control Logics that govern families of
devices. An important distinction to make when it comes to Control Logics is that there are
two general categories of Control Logics: those geared towards a “device family” and those
geared towards specific makes and models. By device family, we simply mean a grouping of
devices that follow the same constraints in their behavior. An example would be the means
by which an IR controlled VCR conducts a Search Forward. Some models require that the
infrared stream be sent continuously for the duration of the search; when the stream stops,
the search stops. Others require a command to start the search and they remain in search
mode until they receive a command to stop. Even in that, there is another family of logic
required: does the return to Play from Search require a Play command or a Search
command, or does it accept both? These are the kinds of questions that the Control Logics
handle. Since the advent of RealmCtrl, it has been our goal to get away from the Control
Logic families and instead create Control Logics geared towards specific devices, which will
be named accordingly in the Control Logic drop list (see section 4.2). This helps eliminate
some confusion and guesswork. However, if the device that you need to support is not
available in the list of Control Logics, you may use one of the general control versions
instead. As mentioned previously, any Control Logic that is prefixed with an ‘x’ has been
authored by RealmCtrl whereas any other Control Logic replicates the behavior of the Control
Logic that existed within the predecessor to Phoenix, which was Synergy.
Unlike Synergy, Control Logics that are not available within the control system code will not
be available from the Server interface. I.e., if you are searching for a Control Logic that
existed in Synergy but is not selectable in Phoenix then it indicates that the Control Logic has
not been brought across to Phoenix. In this event, contact RealmCtrl to request that the
Control Logic be developed, or for information regarding a comparable Control Logic that is
included within the application.
Another important item to mention for our former Synergy users is that Phoenix does not
require that the button be depressed for the duration of a Search. In Synergy, the button had
to be held for the entire duration of the Search, then the device would return to its former
state when the button was released. In Phoenix, once you issue a Search command, the
device will remain in Search mode until you toggle out of it, either by pressing the search
button again, or any other transport command.
Following are the Control Logic descriptions:
CAM01
Synergy counterpart: CAM1
Control: N/A
Available Function Description Button Action Logic Slot
Undeveloped
CAM02
Synergy counterpart: CAM1
Control: N/A
Available Function Description Button Action Logic Slot
Undeveloped
CAS01
Synergy counterpart: CAS1
Control: IR
Available Function Description Button Action Logic Slot
Play
PLAY PUSH
PULSE
Play
1
Stop
STOP PUSH
PULSE
Stop
2
Pause
PAUSE PUSH
PULSE
Pause
3
Fast Forward
FFWD PUSH
PULSE
Fast Forward
4
Rewind
RWD PUSH
PULSE
Rewind
5
Record
Toggle Navigation Mode
[Internal] N/A
PULSE
Record
8