User manual

Operating Manual - FR-8/16 Remote Level Controller

1. Network requirements

Ethernet communication with this device is made by wiring

it with standard Cat-5 cable terminated with an RJ-45 connector

through an Ethernet network router, switch, hub, or patch panel

to a PC running Protea NE Software v5.10 or higher. Maximum

cable distance is 100 meters (328 ft) from the nearest router, hub,

or switch. Ashly networked devices will auto detect their Eth-

ernet network connection, and adapt to either a straight through pin to pin, or crossover Ethernet cable.

Note that the push release tab on the back panel connector (as shown) is meant only for XLR type RJ-45

connectors. Non-XLR type RJ-45 connectors have their own release tab built in.

IP Address -

There is no need to assign an IP address to FR-8/16 used with a network router. The

router or Link Local Addressing will assign IP addresses to each product automatically. When a router

is not available, most current NE products and remotes have the capability to assign their own IP address

based on Link Local Addressing. This allows the device to operate without the need to set up static IP

address. If the only option is to use an Ethernet switch instead of a router, and communications problems

remain which cannot be solved with the use of the link local standard, each device must have a static IP

address assigned from within Protea NE software. This is done by selecting “Manual Conﬁ guration” in

the Network Properties tab of each device, where the system/network administrator must assign each

product its’ own unique static IP address, each with the appropriate sub net if applicable.

Firewalls - If Protea NE software does not detect the FR-8/16, the ﬁ rewall in the host PC

should be turned off, as ﬁ rewalls may block the device response to the controlling PC when network

communication is attempted. The current PC ﬁ rewall status is found by clicking on the Windows

Start button, then Control Panel, then double clicking on the security shield where the ﬁ rewall can

then be disabled. Once communications with the device is established, the ﬁ rewall can be enabled

again, but if there continues to be communications problems then disable the ﬁ rewall.

Wi-Fi and LAN – For the initial device auto-conﬁ guration process, any secondary Wi-Fi con-

nection should also be disabled, and the LAN (Local Area Network) connection must be enabled on

the PC. Secondary network connections may confuse the auto device discovery process. Go to the

Windows Control Panel, then Network Connections, to disable any secondary network connections.

Once communications with the device is established, secondary network connections can be enabled

again, unless a communications problem remains with the FR-8/16, in which case the secondary

network connections should remain disabled.

Connecting Device(s) - Connect an Ethernet cable with PoE (Power over Ethernet) to the FR-

8/16 unit. If a successful Ethernet connection has been made, a solid green LED (Link) lights up

near the device Ethernet port. If there is no green LED showing, there is either a problem with the

cable or the network source, which must be addressed before proceeding further. All RJ-45 Ethernet

ports ﬂ ash green when active, so backtrack through any other cables, routers, or switches to ﬁ nd the

problem. The ﬂ ashing yellow LED (Data) indicates that data is ﬂ owing to or from the device.

Power over Ethernet - FR-8/16 remote controllers must be phantom powered using a IEEE

802.3af Power over Ethernet (PoE) switch, hub, or in-line PoE injector. Power consumption is two

watts maximum.

PRELIMINARY