Etc rfr manual

The upper display line shows information about the selected channel s. The labels for the soft buttons are on the two lower rows of the display. Soft give direct access to basic channel functionality. The most common channel functions can be used to select channels and set levels At Mode Command Syntax is supported from Congo v5.

Use the wheel s to focus the item you want and click the wheel button to activate it. GROUP selects the item directly without showing the list. Two parameters at a time will be displayed in the middle of the display and controlled by the two wheels.

Press a wheel to toggle between coarse and fine for parameters. Next, Last and Select All functions are used to step within the current selection, Select All will return to the original selection. These will cycle thru the available parameter pages for the selected device s. Use the wheels to adjust parameter values. Fine mode is indicated with a "-" symbol before the parameter value.

The current color for the first selected channel is displayed by a small rotating indicator. Press anywhere on the color wheel to change the color, and the indicator will then move to the new color.

From the top down First you will find your selected channel s. Devices that connect to the access point are essentially on the same network as the wired devices. Connect the router's WAN port to a core switch in your system. If two switch ports are not available next to the console, ETC recommends installing a small unmanaged switch between the console, wall port, and router. The switch will provide access to the network while not placing the router in-line. Connect the access point to your core switch in the system.

If another switch port is not available in the location where you want to set up the router, ETC recommends installing a small unmanaged 5-port switch.

Note that access points will typically end up transmitting all multicast or broadcast information on the network. In larger installations, this can become problematic and affect WiFi remote connection, performance, and responsiveness. Newer consoles in the Eos and Cobalt Families have two network ports available for use. One application of the second network port is to allow for WiFi remote traffic to be separated from the rest of the lighting network.

In this case, be sure that the DHCP service is turned on for the second network port and connect the router's WAN port or access point to the console. Since the two network ports are on entirely separate networks, this setup works in scenarios where you have a single console in the system or only wish to use a WiFi remote with that console alone. Some systems do not transmit lighting levels over the network. In these cases, connecting the router's WAN port or access point directly after turning on the DHCP service on the console will be completely fine.

The IP address es will be listed at the top of the page. ETC has a set of standard network IP addresses, including appropriate defaults. One console in the system should be configured to hand out IP addresses to other devices in the system.

Net3 Conductor is preferred. If you have multiple consoles and no Net3 Conductor appliance, we recommend choosing the console assigned as Primary for Eos Family devices or Server for Congo and Cobalt Family devices. If you are running version 2. Ensure that WiFi Remotes is checked on the network port s where the wireless router or access point is connected. If you are using a personal computer and ETCnomad, this is managed separately — refer to your operating system documentation.

You may change this name to one that is easier to remember and type. In particular, when this functionality is enabled, functions and methods will return values of the following MoonGLMATH types: vec2 instead of vec , mat2x3 instead of mat , box2 instead of bb , and vec4 instead of color. Notice that for function arguments nothing changes, since the above MoonGLMATH types are compatible with the corresponding plain tables used by default, thus they can be used as function arguments in any case.

This submodule provides the tools that are used in examples and demos for rendering, input handling, and more. In addition to MoonChipmunk itself, the toolbox uses and thus requires the following libraries from the MoonLibs collection :.

MoonFreeType : bindings to FreeType, for loading fonts. MoonSndFile : bindings to libsndfile, for loading sound samples. Note that MoonChipmunk itself does not depend on the above libraries.

Only the toolbox does, and its use in an application is optional. The examples and demos, together with the comments in the toolbox script, should hopefully suffice to show how the tools are meant to be used. It is assumed that the reader is familiar with both Chipmunk2D and the Lua programming language. See also MoonChipmunk is part of MoonLibs , a collection of Lua libraries for graphics and audio programming. Introduction MoonChipmunk is an almost one-to-one Lua binding library to the Chipmunk2D physics engine.

Objects Listed below are the Lua object types in MoonChipmunk, together with the corresponding original types in Chipmunk2D:. Spaces Rfr: cpSpace. Rigid bodies Rfr: cpBody. Shapes Rfr: cpShape. Constructors and specialized methods are available for the following subtypes:. Constraints Rfr: cpConstraint. Collision handlers Rfr: cpCollisionHandler. Arbiters Rfr: cpArbiter. Miscellanea Float utilities Rfr: cp basic types. Vector utilities Rfr: cpVect.