RFR, Ions, VPN and VRFs

were talking RFR and not the app, right? i don't think that the RFR uses wifi-protocols to communicate (it does indeed use the same frequencies though), so i'm not sure if you can make it work with a VPN (which requires networking protocols methinks)

I you have a NET3 RFR then you could place the base station on the network with a VLAN. But I doubt you can install anything on the console...

If you are talking about the app and regular wifi, I suggest getting a second/third/fourth access point to act as a repeater/extender. Put it in the catwalks, pit or backstage somewhere. Much easier than messing with VLANs and building networks.

Andrew,

First of all never ever install anything, that does not come from ETC on your console. Second of all, never ever turn over control of your physical network to some IT Guru who works 9-5 and won't be there if things go wrong five minutes before the show goes up.
If you have cat 5 you can put the RFR receiver on your network anywhere, the same as any other AP. If you use the App just stick a few more AP in your building and if you are concerned about security power them via a relay that you switch on and of if and when needed....

Just my 2p 

Hello Andrew,

You should never install any windows updates or 3rd party software on your console - "This would be a bad thing"© 

Your console is running Windows XP Embedded, this is a striped down version of Windows.

As I believe you are talking mainly about the RFR* (as a pose to the ARFR/IRFR), you have a couple of options.

1) Move the RFR base station, connected via Ethernet, on to stage

2) Purchase another RFR base station.

Multiple stations can be used on the system. These can be located around the venue, connected via Ethernet, to supply full coverage of your working environment.

3) You may also have interference (dispute full signal), on the selected RFR frequency. It looks like you know how to change freq, but just incase: details on how to change the frequency can be found on page 413 of the EOS manual ( http://www.etcconnect.com/WorkArea/DownloadAsset.aspx?id=10737461407

With regards the ARFR and IRFR running on a phone or tablet, if you want to integrate this to your building WiFi - I would recommend that this is done via a separate VLAN and WiFi SSID. 

If you need more help/details with any of the above, we can be contacted directly via the details here: http://www.etcconnect.com/Templates/ContactUsRedirectPage.aspx

Regards,

Marcus

* FYI this uses a form of RF called 802.15.4 (ZigBee)

Yep, I've got the Net3 RFR. I'm trying to solve the drop outs by going to an iApp or aApp on a "new" device by using the building (university) wifi system.

Richard: so move the ETC base station out of the booth, and connect it to the network via Ethernet elsewhere in the venue, and connect the console to the network as well. But I think that would still require the Service Pack 3 upgrade and installing Cisco, so the console can work with the building network.

Your second idea: I buy a phone and my own personal wifi emitter for the booth, and a second wifi emitter for somewhere else in the venue. That will bounce/boost the signal into the booth. I take it that doesn't actually require interfacing with the building network. (wifi newbie question: how do I get the 2nd emitter to link with the first, and not the building system?)

Interesting. Thanks.

Hi Florian.
that's why I'm asking ETC about this first. I had hoped the solution to my drop outs wouldn't go that far.

What do you mean by "AP?" Access point?
There is only 1 ethernet network in the building: and that's the building system. It seems you're suggesting the same as Richard: If I move the ETC emitter (access point) to somewhere else, and patch into an ethernet port, I still need to have the console and ETC emitter find each other in the building network.

and that's where I involve the gurus, since that's out of my area and control. I don't want to piggyback on the building infrustructure, but that's where this seems to be heading.

Andrew

One other option for getting additional WiFi or RFR coverage is to use some unused or spare building infrastructure (network wiring) but install separate switch(es) and access points (AP's) that are exclusively for the lighting network. This avoids the VLAN issue and would only involve the University's IT folks on the initial install (to physically patch the installed cable runs into your equipment).

This way, you are in control of your own equipment (which typically requires little ongoing configuration once it is up and running) and the lighting network is completely separate from the building network.

-Todd

Hi Marcus
Yes I'm talking about the ETC Net3 RFR. My inital hope/solution was to go to an iApp or aApp, and get more functionality. If the net3 remote is dropping out based on the physical building, would an android/apple product phone and local wifi (keep typing wife instead of wifi) have the same issues? I'm trying to sort that out before committing and spending $ on a wifi access point.

I get it that i can move the Net3 AP, and never considered the ethernet jack on the back of the emitter. However, I can't just run an ethernet cable into the catwalk for it: i would need to connect it the building system, which of course is networked up the yahzoo. (and then I'm still into VLAN and VRF stuff, am I not? please correct me if that's not the case.)

However, I do have an ethernet line run to the sound pit for the designer's RPU client.... I could move the Net3 emitter Remote there and run that back to the console. Maybe I'll try this first. See if that offers any improvement.

Thanks
Andrew

"Your second idea: I buy a phone and my own personal wifi emitter for the booth, and a second wifi emitter for somewhere else in the venue. That will bounce/boost the signal into the booth. I take it that doesn't actually require interfacing with the building network. (wifi newbie question: how do I get the 2nd emitter to link with the first, and not the building system?)"

Yes you can skip the building network completely by using just wireless access points.The one by the console plugs into the network port but all the others just need power. (Thus the relay suggestion above. Some devices have a wireless disable button, or you unplug the one by the console at show time.)

Many full routers can become access points with a menu setting, and they are so cheap that it's often done. Or you can buy one for the purpose. This one is cheap $20! http://www.bestbuy.com/site/tp-link-wireless-n300-wi-fi-range-extender-with-ethernet-port-white/2080012.p?id=1219528556820&skuId=2080012

Each device will have it's own settings procedure, but generally you would connect a computer to it to and make any changes. Set the two the same except for their own IP. You will need to select a "SSID" (name) and password for the network, just like every WiFi network you've logged into. Instructions in the box should be enough or the IT guys can take an hour to do a 15 min job. [:)]

A variation on the 'move the emitter' option: Ask the network guys if they can patch two jacks to each other - skipping the switch. Back in the IT closet they would use a jumper to join the two wires. At least most major set ups can do that, but no guarantees! Now you have a really long cat5 between two jacks and no building network issues.

I hope that helps!

Lots of threads in this conversation, so I'm replying to this one:

I moved the USB RFR base station from the console into the house, and plugged an ethernet line into the jack. Into the console I plugged a 10/100 Workgroup switch, and then the ethernet line also went into the switch. (normally the switch lives with my RPU for the designer's remote. I just moved the switch to the booth end of the ethernet cable.)
No joy. The switch sees the console, but there is no power to the base station. Is Power over Ethernet required for the basestation? what does it take to achieve that?

thoughts anyone?

Power is from POE or USB.

A USB power source is pretty easy get these days, much more so than a POE injector. I'd go for one with a detachable cord so you use whatever cord is needed at the time. (I think the RFR uses a printer type connector.)

The base station needs power from either USB or POE. I believe this is what the USB should look like: