Local WiFi mode loosing connection

[pingdynasty]

@holminid from #1

I tried different networks with different authentications, to no avail. IP Scanner occasionally sees the OSM for a second (and shows the IP address) but then it disappears. AP mode works as it should, but I need to extend the network. What to do?

[pingdynasty]

How can I best reproduce it?
What does the LED look like, does it stay solid yellow, blink, or go back to green?

[holminid]

My setup is like this: An Airport router extends the available internet connection, the authentication is WPA2. I guess an ad-hoc connection can be used for testing. Gyrosc is running on an iPhone 6 and the OSM receives /gyrosc/comp and /gyrosc/alt on the CV ports.

The LED blinks for a while and stays solid yellow when I press it for 5 seconds. I also tried the reconnect option from the web interface.

[pingdynasty]

If it stays solid yellow it should still be connected to the network.

Did you try installing the liblo utilities?
http://pingdynasty.github.io/OpenSoundModule/Troubleshooting/
It can really help to troubleshoot OSC issues on the network.

With oscdump running on the same WiFi network you should see the broadcast message from OSM that is sent when you press (briefly) the WiFi button.

[holminid]

I installed liblo but didn’t see a message when pressing the button.

On 10 Jun 2016, at 23:01, Martin Klang notifications@github.com wrote:

If it stays solid yellow it should still be connected to the network.

Did you try installing the liblo utilities?
http://pingdynasty.github.io/OpenSoundModule/Troubleshooting/ http://pingdynasty.github.io/OpenSoundModule/Troubleshooting/
It can really help to troubleshoot OSC issues on the network.

With oscdump running on the same WiFi network you should see the broadcast message from OSM that is sent when you press (briefly) the WiFi button.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub #3 (comment), or mute the thread https://github.com/notifications/unsubscribe/ABwO54xE1fb7FdCnLUtU63LtuOmomEObks5qKdC7gaJpZM4IzPy0.

[holminid]

The module seems unresponsive to liblo. It also turns off the LED entirely or resets to AP mode. Sometimes pressing it momentarily causes a green flash, other times it flashes yellow a couple of times and turns off.

[pingdynasty]

Have you got oscdump working as expected in AP mode?

When OSM flashes yellow it is because it has lost (or is regaining) the WiFi connection. It is likely that your local WiFi is resetting the connection for some reason. I'll try to get hold of an Airport router to test with, what is the model name and version of yours?

[holminid]

No, I didn’t get it to work with oscdump in AP mode either.

It’s an old Airport Express, 802.11n, 1st generation.

On 12 Jun 2016, at 19:24, Martin Klang notifications@github.com wrote:

Have you got oscdump working as expected in AP mode?

When OSM flashes yellow it is because it has lost (or is regaining) the WiFi connection. It is likely that your local WiFi is resetting the connection for some reason. I'll try to get hold of an Airport router to test with, what is the model name and version of yours?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub #3 (comment), or mute the thread https://github.com/notifications/unsubscribe/ABwO5zZ-KtnWWM8W72-74qG8GZL6cI8Fks5qLEDRgaJpZM4IzPy0.

[pingdynasty]

Okay so please try to get liblo working in AP mode, it's worth it if you want to see what's happening on the OSC network. Follow the instructions on the Troubleshooting page linked above.

Once you can send and receive messages in AP mode, you can do the same thing in local WiFi mode and use it both to get the right IP address of the device and to check that it is still on the network.

Just make sure the laptop you are running liblo on is on the same WiFi network as the OSM.

[holminid]

liblo works in AP mode, it shows the IP and port, but nothing is shown in local WiFI mode. The yellow light doesn’t flash or anything either.

On 13 Jun 2016, at 11:22, Martin Klang notifications@github.com wrote:

Okay so please try to get liblo working in AP mode, it's worth it if you want to see what's happening on the OSC network. Follow the instructions on the Troubleshooting page linked above.

Once you can send and receive messages in AP mode, you can do the same thing in local WiFi mode and use it both to get the right IP address of the device and to check that it is still on the network.

Just make sure the laptop you are running liblo on is on the same WiFi network as the OSM.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub #3 (comment), or mute the thread https://github.com/notifications/unsubscribe/ABwO575my-1Z9Ihh2bNmAg5mLL6msT7Qks5qLSFCgaJpZM4IzPy0.

[holminid]

I managed to connect to it with liblo in local WiFi mode, this time using the "reconnect as client" option.

[holminid]

The issue remains unresolved. I don't currently receive status reports in Liblo using oscdump, either in local mode or AP mode. Sending for example oscsend osc.udp://192.168.2.102:8000 /osm/a/cv f 274.339020 does not work either. The status was working earlier, although power cycling was required for the status to appear again, after some hours. I noticed that using "reconnect as client" switched to blank LED, which turned to yellow after a while, then green, flashing yellow again and finally green. The AP appeared in the available networks after this. The strange thing is that controls from Chrome do work and transmit CV.

[pingdynasty]

It sounds like your WiFi hub is kicking the OSM off the network for some reason. I'm still trying to get hold of a similar Airport device to diagnose it.

Meanwhile I suggest you debug the system in AP mode, and get it all set up the way you want it, before switching to local WiFi mode.

By default, on startup the OSM logs in to any available WiFi network that it has stored credentials for. To prevent this and remain in AP mode, you can clear the stored credentials from the Status page in the web interface.

[holminid]

The credentials aren't cleared from the OSM despite many attempts. However, it defaults to AP mode now. I removed the cable from the Airport Express connected to the main router just in case.

Update: oscdump now works, as does oscsend. The problem with oscdump was a human error (wrong port) but it does not explain why oscsend didn't work previously.

[pingdynasty]

oscsend will quietly fail if the IP address is wrong. This can happen if the OSM has been kicked of the local WiFi network and assigned a new IP address. In AP mode, the IP is always 192.168.0.1.

I'm curious to know what makes you say the credentials aren't cleared? If it defaults to AP mode, then either the network is not available, the credentials have been cleared, or both.