• State Not Answered
  • Date
    jolsson
  • Date
  • Replies 4 replies
  • Subscribers 57 subscribers
  • Views 3401 views
  • Users 0 members are here

Client Laptop not updating.

Hello!

I have a Client dongle (256 output) that I wanted to use with my CongoJR with Cobalt 7.3.1

So I plugged the dongle in my laptop, connected to my light-WiFi (where I run my iRFR) and got alot of trubble. 

The docks didn't work well. The direct select didn't show the direct selects, Some was just yellow and when I finally got the direct select dock to show the content (after pressing the 1 2 3 4 5 page boxes a few times) it didn't update. example: I moved lights for a focus pallet, and when I wanted to update the pallet I pressed "Record" in the direct select window and they did NOT turn red, but when I pressed the pallet I got the "Record pallet" window. if I pressed Record many times they did turn red, but it didn't mean it was set to record. do big delays.

 

It felt like the communication back to the Client from the master didn't work as intended. My commands from the client got to the master (like 5 [channel] 30 @level) but my screens didn't update so I didn't know where I was.

Any suggestions how to fix this?

Parents
  • 0
    WiFi is not recommended and is not currently supported at all for Client or Backup, as it has quite long and often highly variable latency.

    Sometimes it will be fine, however you will often get long delays.

    WiFi was never designed for this, it's intended for general web surfing which means high throughput in only one direction, and it really doesn't matter if a request has to wait half a second to get through.

    iRFR/aRFR is fine because very little information is being sent back and forth, and of course an occasional half-second delay is rarely a real problem when focusing!
  • 0 in reply to Richard
    In addition I would like to add in my experience wifi connections can cause the primary to slow down as well. I would avoid at all costs.

    I have been able to get it to work in a network with no DMX protocols (no SACN or ARTNet) gumming up the lines and a powerful router in close line of sight, but I don't really recommend it. Even in a perfect situation you will have annoying latency popping up from time to time.

    For Clients and backups always run a wire. If you need access untethered look towards the RFRs and the OSC applications.
Reply
  • 0 in reply to Richard
    In addition I would like to add in my experience wifi connections can cause the primary to slow down as well. I would avoid at all costs.

    I have been able to get it to work in a network with no DMX protocols (no SACN or ARTNet) gumming up the lines and a powerful router in close line of sight, but I don't really recommend it. Even in a perfect situation you will have annoying latency popping up from time to time.

    For Clients and backups always run a wire. If you need access untethered look towards the RFRs and the OSC applications.
Children
No Data
Related

www.etcconnect.com