We are having strange problem, where there are no data is being sent to some devices. For example, we can have a tablet sitting next to the Edison, with strong WiFi signal and no interference, and video being streamed without any problems, and then we connect another tablet to it and it will stop data for about 20-30 seconds, and then small amount would get through and then that drop off repeats. So essentially our frame rate drops from 10 fps to 2 per minute.
It could also happen with single device - it would be connected to Edison with strong WiFi but only send data through every 20-30 sec.
Edison, running netcat to transfer tcp data. We run Edison as hotspot using stock hostapd (2.1).
Here are the steps:
- Load stock Edison image (problem appears with both image in edison-image-ww25.5-15.zip and iot-devkit-prof-dev-image-edison-20160606.zip)
- Configure wifi access point:
- Login over serial console and enable wifi access point with commands:
- Boot computer to Ubuntu 14 using live usb stick (install on harddisk not needed)
- Connect to Edison wifi.
- Start two terminals
- In terminal 1: enter command: "ping 192.168.42.1"
- In terminal 2: enter command: "nc -v -l -n -p 2222 > /dev/null" (netcat listens at port 2222 and discards received data)
- You can also start "system monitor" to monitor wifi data
You now have two computers pinging the Edison without problems.
- Start sending data to computer A (assuming computer A has ip 192.168.42.20) with command: "cat /dev/zero|nc 192.168.42.20 2222"
- The problem is that somehow computer A wifi locks up the Edison wifi completely for some time, also for other devices connected.
- If a wifi "hiccup" does occur, it can be resolved by trying to associate any other device to the Edison wifi access point. No matter if the password is correct or not.
- Different hostapd version does not resolve problem (I tried both 2.1 and 2.5)
- When using another OS on computer A the problem might not necessarily occur as well.
- When using another wifi adapter on computer A (same OS), like Atheros AR9271 the problem does not occur ( and data throughput is ~3x higher!)
We would like to run the steps exactly as you're doing it right now, however, we are not very clear with the first steps you mention.
Could you please share the steps you're using to configure and enable the wifi access point in the Edison?
Also, at the end of the first list of steps you mention that "you now have two computers pinging the Edison without problems", so you booted up two different computers with the same Ubuntu 14 USB stick, right?
Any other detail about your process or configuration will be more than appreciated.
My apologies, I am not the end customer but a disti AE trying to get answers, let me try to clarify.
They have one Edison kit running a stock image acting as a Wi-Fi access point. They have two separate computers, A and B, running Ubuntu 14. The computers could boot from Live USB stick or a standard boot, we have seen this issue in both instances.
For each computer, we are running two terminals; one to ping the Edison board and one to listen on port 2222 and discard received data.
In the Edison board we start sending to either computer using something like: cat /dev/zero|nc 192.168.42.20 2222, just to send packets.
We see that the pings from computer B stop getting answered. It seem like the process of sending data to Computer A, in this case, from the Edison board locks up the Wi-Fi for some time.
If this is not clear please let me know.
We would like to let you know that we are aware of this issue and that it has been communicated to the engineering team. We will get back to you as soon as we have updates on this.
Have you had any success with resolving this? We are experiencing similar issue, and it randomly turns our product from amazing thing into a piece of garbage that everyone hate.
If you have some ideas as to what it might be, or any workaround, please let me know. We can try things out on our own and would welcome any direction from Intel on resolving this.
We understand your frustration about this issue and the current state of your product. This issue is still being investigated by the Engineering team. I'm afraid we don't have a workaround to offer at this time, but as soon as an update or any information is shared with us that can lead to a solution we will let you know. Hopefully, that will happen soon.
We apologize for the delay in our response. We've been informed that this issue is in consideration for a future release of Edison software. Hopefully it will be released soon, nevertheless, there is no ETA for it.