Hi all,
I don't know if the issue I'm having now is with iOS 10 or EOS 2.4 but I can no longer connect with TouchOSC. Is anyone else having this problem? Is there a work-around?
Thanks
Hi all,
I don't know if the issue I'm having now is with iOS 10 or EOS 2.4 but I can no longer connect with TouchOSC. Is anyone else having this problem? Is there a work-around?
Thanks
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 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.
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
In the pics above you have the wrong ip address set in touchosc for the host. The host in touchosc is the console. The console is .101 but you have touchosc pointed to .209
A suggestion. Please take/read a basic computer networking class or book. The problems we are trying to help you solve are not "lighting" problems but rather networking problems. We are in an increasingly tech heavy industry and everyone needs to have a basic understanding of computer networking.
If you are having problems with IP addresses, Subnet Masks, default gateways and DHCP servers you should increase your knowledge base to gain an understanding of them.
We will always help here but each and every one of us needs to also try to expand our understanding of the underlying technologies we are using.
www.etcconnect.com