
dodgerrrr

I am having problems with JD losing wifi connection after several minutes of connection time. I am not in an over saturated wifi area and it happens every time after a few commands are executed successfully on the iPhone 6. Everything is updated. The only way to get connection is to power JD down and reconnect. When I operate JD from my laptop everything is fine. Also I notice JD will not load my servo profiles from the iPhone. That is a problem too. What can I do about connections to the iPhone to make them last as normal as it does on my laptop ?
1) Does the red LED stay on the EZ-B when the connection is dropped?
2) What iphone version do you have? 6, 6 plus? 6s? 6s plug? or just the 6. I have a 6 plus, and alan has a 6 - neither have issues. hmmm
3) Does the iphone have a case on it? They are prone to wifi issues for lengthy periods without cases and if held incorrectly due to the location of the antenna in the top corner (which is on the side when using ARC)
4) Have you tried changing the wifi channels on the ez-b?
5) are you connecting in client mode or ap mode? (ie direct to robot or through network)
I have an iphone, so does everyone else at ez-robot. We haven't experienced any issues or had anything similar brought to our attention in over 10,000 units - so the tough part is to identify what could be causing this on your side.
Connection stays on with my windows laptop. Only happens on iPhone
Simply take the back of the head and refit the rgb eye connector. Do the same for the connector to the ezb.
Good news, it's not wifi related. Have fun!
Or, easily make a profile on the mobile. I find it easier to make a profile on the mobile rather than go through the effort of saving and syncing.
Do what ever process you find easiest
Or this: http://www.ez-robot.com/Tutorials/FAQ.aspx#9
My EZB sometimes freezes, shuts down the WIFI and the red LED on it turns on. However I'm not using a i2c port. What causes this on my setup is when I try to send a command through a UART port without it being initiated or a command that is not structured right. I have to power cycle the EZB, reconnect and make sure the Uart port is initiated or the command is written properly.
I thought maybe you were trying to send a corrupt command through the i2c port. My other guess would be a bad cable or connection. *confused*
You will see this most often with communication hardware - because communication "waits" for something to happen. The same would apply if I told you to wait for ever to read these 5 words: Apple, orange, chicken, Sky,