• Date
    tdrga
  • Date
  • Replies 10 replies
  • Subscribers 185 subscribers
  • Views 11086 views
  • Users 0 members are here

iRFR is slow and drops connections

So I just got a new iPod touch 8gb- version 3.1.1.  Got the iRFR app v.1.0.30 and want to use it with my EOS.

Here's the setup: EOS console (backup), RPU (master), RVI - all v1.7.  10 Sensor Racks and about 10 Net2 nodes on the network.  Linksys WAP54g access point.

I followed the instructions on the iRFR Wiki pages and got the iPod to connect to the console (green check mark next to console ip address).  The password field contains the RPU name.

When I go to the Welcome screen and click Connect- sometimes it shows a checkmark but no console info, other times, it does show console info.  When I start the virtual RFR, it is slooow- like 10-15 seconds between button click and response on the RPU screen.  The iRFR display never catches up with what I'm doing and eventually stops responding altogether.

Sometimes when I start the iRFR app, as it tries to connect the iPod loses wi-fi connection.(no bars)  I thought it might be the security settings on the access point, so I disabled all security, but it still drops out.

Not being too familliar with the iPod yet, I'm not sure how to fix this to make the iRFR usable.  I can't find enough information on the iPod to diagnose any wi-fi connection problem- it just shows signal strength and no other statistics (packet count, dropped packets, etc.)

I can't figure out if this is an app compatibility issue with iPod v. 3.1.1 or a network issue or an EOS config issue.  The enable iPod RFR option is checked in the RFR shell tabs on both the RPU and the console.

The iPod works fine when I connect to my wi-fi network at home (no drop-outs), so I think the iPod wi-fi is okay.

I assume that others are using the iRFR succesfully, any ideas on how I can get mine to work?

Thanks-

-Todd

 

Parents

  • Hello Todd

        I had the exact same problem.  I followed the instructions concerning IP address and the 2 second delay.  The problem was how my I touch was getting its IP address thru the network.

         Someone here who knows much more than me"stacked the IP address"  So the touch was not going thru all the switches.  It fixed the problem and the Itough is almost if not as fact has the RFR.  But it does so much more.

         On the show we are doing we have some gobo rotators and when I showed the desighner how I could control each one he was very imprressed

         If you are still having problem let me know and I will get the exact IP address for you.

         JeffMBike@aol.com

         Electrician Fords Theatre

     

     

     

     

     

  • in reply to jeffmbike

    I doubt I'm the only one who'd be grateful to know how you fixed the lag, so could it be posted on here?

    When it works the iRFR is so much more useful than the standard RFR, but we are still having to carry both round in case the lag is bad making the iphones unusable.

  • in reply to harryt

    Here is my 2 cents.  Change the WAP Channel to one that has less interference.  Move WAP Closer to area where you are using the IRFR.  This is a wireless device that is subject to interference.  Please read the following post.  http://community.etcconnect.com/forums/t/4181.aspx  It may help with some of the issues you are seeing.  I doubt highly it is your new IPod. 

    P-

Reply Children
Related

www.etcconnect.com