OSC on iOS 10

Ok. So trying to think of things which may have changed. You're still connected to the same WiFi access point?

Can you go into the shell on Eos and try pinging the IP address of your iOS device to check it can see it.

SO, I re-installed Touch OSC on my phone and tried again.  I actually can receive info from the console - when I press buttons, I see the commands on my phone's command line - but I cannot send info.  

So 10.101.100.201 looks like that must be the address of your iPhone. If your iPhone gets commands from Eos but not the other way round then it sounds like there's a mismatch between the OSC RX Port on Eos and the "Port (outgoing)" in TouchOSC.

That's what I'd thought too.  but when I tried swapping the "port (outgoing)" and "Port (incoming)" I got no response what-so-ever.  

These are the meeting when I can, at least RECEIVE data:

And just to check that 10.101.100.209 is your console? Otherwise everything seems ok with that setup.

Ah, so here's your problem.

It looks like both your iPhone and console have the same IP address. Your screenshot show 201 for the iPhone as well. You need to make sure they're unique.

Hi all,

Ok, I've cleared the String RX and TX port fields. I've made sure that the OSC TX IP Address and the IP of my phone are the same (10.101.100.201). I've opened the Diagnostic tab, and ONLY see OSC OUT packets, nothing incoming.

I still can only receive console data, not send it.

Do I need to do anything with the OSC Cue Send/Recv String fields? (those are new, right?)

What i don't really understand is that it was working perfectly before I upgraded to iOS10 and 2.4.  I haven't touched any of the settings in months up until now....

Thanks!

You don't need to change anything with the cue send/receive fields, they're just to override the default string send automatically when running/receiving cues.

If you could post screenshots of:

iOS Wifi settings

TouchOSC settings

Eos Show Control

Eos Network settings

We'll be able to get your sorted out with those. If communication is only working one way either you have duplicate IPs, port mismatch or the subnet masks is wrong.

Something must have changed. The fact you had the same IP at one point means you must have changed something as it could never have worked setup like that.

Cheers

Dan

Here you go.

I do have control through ETC's irfr app, but not OSC.

And thanks for all the help!!