Sammy
Resolved by DJ Sures!
Hello all,
I have an issue with a frequently intermittent disconnect of my EZ-B from ARC. I am constantly forced to reset the EZ-B or my bluetooth connection or both. Sometime, I am able to operate for a good 20 minutes (+/-) before I am forced to reset, and other times I have to reset every minute or so (especially after issuing servo commands)
Some background:
This is a Wall-E project. I am inserting the EZ-B and the battery pack into Wall-e's "gut". However, they are not firmly attached and may move around slightly as Wall-E moves. Can this be a problem? Should the board be firmly attached? (I will eventually make sure everything is firmly attached and connected but I haven't finalized the Wall-e hardware configuration yet and wanted to do a few trial runs before)
I should also point out I am running Windows using Parallels on my Mac. I suspect this virtual os problem may be the main suspect. However, I am hopeful it is not the case, and someone else has experienced a similar problem and found an alternate solution for it.
Many Thanks for any feedback,
Sam
P.S. I am considering installing Windows directly using BootCamp (instead of virtual environments). This way I can start my mac using Windows as my operating system. It's just a pain doing so, as I would have to shutdown and restart every time I wish to alternate between OS'es
@ robot-doc ... I never understood why I need a bluetooth dongle if my laptop is already equipped with one (my macbook has bluetooth) ... is it possible to simply use that?
If you can check to see what class your internal BT is on your laptop. To get the proper connection and coverage you should match up your classes. Chances are you only have a Class 2 on the laptop. Class 2 seems to be very common. Also I noticed I got a steadier connection with a Dongle then the internal laptop Bluetooth. Just make sure your using the Microsoft BT stack.
As dschulpius mentioned, your computer probably only has a Class 2 bluetooth since most accessories that are made to work via bluetooth and PCs are units like keyboards and speakers with a need for a very short operational distance <= 33 feet.
I realize I'm jumping in to help late but yes I suspect that virtually running windows can cause some problems with a native windows app. So i would do like you suggested and do a full native install with correct drivers and default blue tooth stack. That's your best bet for reliable connection. Also a side note the V4 comes with WIFI built in and longer range. Upgrading to a wifi enabled board will also improve overall signal strength.
What is the error message when it disconnects? You can press the copy button on the debug window at the bottom of the screed. That will help me know what's up
Happy New Year Everyone !
@DJ Sures
When I first start up everything. Connection is made. I ask Wall-E to wake up ... and back to sleep ... then wake up again ... (that makes him move his head up with arms when he wakes up and then head down with arms down when he sleeps)
However, when I ask him to "Wall-e Go" (which makes him move forward, while moving hands up and down and moving head sideways left and right - all simultaneously) he moves forward and then I get a comm fault. EZ-B disconnects.
I ran the debug window the entire time and made a copy. Here it is:
Attempting connection to COM3 EZ-B reports EZ-B Firmware V16 Connected Comm Err: The operation has timed out. BbytesToExpect: 1
Received: Disconnected Disconnected Comm Err: Not Connected BbytesToExpect: 0
Received: Disconnected Comm Err: Not Connected BbytesToExpect: 1
Received: Disconnected Disconnected Comm Err: Not Connected BbytesToExpect: 1
Received: Disconnected Disconnected Comm Err: Not Connected BbytesToExpect: 0
Received: Disconnected Comm Err: Not Connected BbytesToExpect: 1
Received: Disconnected Disconnected Comm Err: Not Connected BbytesToExpect: 0
Received: Disconnected Comm Err: Not Connected BbytesToExpect: 1
Received: Disconnected Disconnected Comm Err: Not Connected BbytesToExpect: 0
Received: Disconnected Comm Err: Not Connected BbytesToExpect: 1
Received: Disconnected Disconnected Comm Err: Not Connected BbytesToExpect: 1
Received: Disconnected Disconnected Comm Err: Not Connected BbytesToExpect: 1
Received: Disconnected Disconnected Comm Err: Not Connected BbytesToExpect: 0
Received: Disconnected Comm Err: Not Connected BbytesToExpect: 0
Received: Disconnected Comm Err: Not Connected BbytesToExpect: 0
Received: Disconnected
AND THEN WHEN I ATTEMPT TO RECONNECT WITHOUT RESETING EZ-B, I GET THE FOLLOWING:
Attempting connection to COM3 Comm Err: The operation has timed out. BbytesToExpect: 1
Received: Disconnected Connection Failed: System.Exception: Controller Not Responding at EZ_B.EZB.Connect(String hostname, String tcpPassword) Disconnected
At this stage all I could do is reset the EZ-B and start over. I am also sometimes forced to reconnect my bluetooth dongle by physically removing it and inserting again.
I have not yet installed Windows natively. Still running Parallels.
Will attempt to install Windows natively very soon and report back my results.
In the meantime, if that debug message tells you anything that may be of help, please let me know.
Thanks
Sam
Sounds like the batteries cannot provide enough voltage. Soon as the robot moves it uses more power. How many batteries does your walle have? Are they rechargeable?
@DJ Sures
That was it! Your suspicions proved correct. I replaced the batteries and problem resolved. I will monitor a bit longer and see if it comes back. I should've picked up on it as it was happening a little too much the last couple of days.
I am using 5 x 1.5 Duracell batteries. No rechargeables.
Do you have recommendations for a better source of power? lasts longer with enough amperage.
Thank you DJ Sures !
Sam