You might want to consider changing to a class 1 bluetooth network arrangement. That network will consist of a class 1 bluetooth USB dongle for the PC and a class 1 BlueSM1rf from sparkfun.com I've never experienced a connection failure even when the PC is 50 feet away from the EZ-B.

Robot-Doc,

Thanks! That's good info to know. It would be wonderful to have a reliable connection.

I would appreciate an answer to the following questions:

1. Were you experiencing serious connection problems at short (<10 feet) range before upgrading?

2. DJ says he's had problems with third party dongles. Which one is working for you?

3. Are you using the gold or silver spark.fun module?

4. How did you configure the 6 pins for EZ-B plug-in? I assume soldering is required.

5. Is the connection procedure the same as DJ's simple procedure?

6. Is connecting totally trouble-free now? (I believe you, but the info is so marvelous that I just have to ask!)

DJ,

Please add your two cents worth! Think more power is the cure for all the connection problems?

1. I did not have luck trying to flash the EZ-B when I first got it because the EZ-B was in the shop and the PC was in another room.

2. I got the class 1 USB bluetooth from Amazon.com (Targus)

3. Gold (class 1)

4. I used a 6 pin header and soldered it to the BlueSM1rf module. The pinout is identical to the original class 2 bluetooth modules. Only the 4 center pins are used. The outer pin on each end is not connected.

5. Standard connection procedure using bluetooth association.

6. Yes

Contact me via email ( 1 have a few extra BlueSM1rfs) we'll negotiate a price.

[email protected]

Update:

I've still been struggling to solve my connection problem. Based on your experience I finally bought the SparkFun class 1 dongle and Gold modem, but no luck. I am getting completely random results in initially connecting and then maintaining connection. The worst part is the dropped connections, making it impossible to enjoy my robot. So now I have bought a FTDI USB-TTL serial cable to eliminate Bluetooth and see what that tells me. Unfortunately, I now have another connection problem: I can't connect and I get the error message saying I have the EZ-B V8.5 firmware and need to upgrade to V16 (which I already have). I'm going to write a new post on this problem if you want to follow my trials and tribulations.

I want to thank you for your above response and offer. Much appreciated.

Sorry, I've never said there is an issue with third party dongles. In many cases, third party dongles have a higher distance than embedded antennas. Please re-read what I had written regarding the third party item that does not work. Specifically, the third party item that does not work is "Bluetooth Stack" or "Bluetooth Software".

The MS Windows Bluetooth Stack is the only supported software for EZ-Robot. This is because it is the only software known to work properly. We don't have access to the source code of any Bluetooth stack (Microsoft or third party) , so we have no idea why they are different. The only thing we know is they are different

As for your connection issues with the FTDI reporting V8.5. There can be a few causes with this. Either the module has ECHO enabled. Or, the RX/TX are connected backward. Or, they TX and RX have been shorted and the chip is damaged.

There is no reason to start a new thread on the same topic.

Perhaps post your ARC Project file in this thread. Maybe there is something strange in the project file that is causing the disconnect? You can post a project file by using the "ATTACH FILE" option to the right. Brose for your file, and press UPLOAD.

Also, we cannot diagnose any issues with an EZ-B if there are peripherals connected. This means, the only way to truly test is to disconnect all peripherals from the EZ-B. No servos. No LEDs. No Motor Controllers. Nothing. There can be nothing connected to the EZ-B.

If you can, i'd like to see a photo of the bottom of your EZ-B. On occasion, with so many boards being hand built - there is the odd one with a missing solder joint. Funny thing, it's usually pin #1 on the chip too. We've had a 2 or 3 with pin #1 not soldered.

We'll figure it out for you

1. Dongle/Stack. I let Windows 7 install the driver automatically, so should be the right stack.

2. Echo. I don't see any way to check Echo enable using Device Manager. Otherwise: 9600 baud, 8 data bits, 1 stop bit, no parity, and no flow control.

3. Tx/Rx connections. Cable Tx to EZ-B Rx and Cable Rx to EZ-B Tx. No shorts on Cable header connector and the EZ-B Rx,Tx,5V, Gnd pins are visually well isolated (except for the 5V bridge). (The 5V and 3.3V pads are uncomfortably close but an ohm-meter shows no connection.) Can't speak for chip damage.

4. New thread. Sorry, already started one in Hardware thread. I thought an isolated discussion of this problem would be easily found by others. (Take a look at the site. Do the replies seem useful to follow?)

5. Project file. I was doing my testing with only the Connection Control pulled up.

6. Peripherals. I disconnected everything (two servos, one ultrasonic ranger, and one camera). Still have the problem.

EZ-B Photo (Looks good to me!):

I had the same problem until i update the firmware in the firmware tutorial.

Then i check it at 100 feet away and still work perfect.

I did use a better bluetooth dongle that came with EZB ,that be part of the reason i have a long range

But only check 1 of my 20 EZB'S i bought ,most likely will need to update the firmware in the rest of them.

Also best way to test for bad connections,since some are on top ,it with a 40 pin ic clip and a meter.

Only connections need on the board to get communication is v+,gnd,mclr,2 clock (crystal ) and tx and rx ,

I dont have the data sheet of the microprocessor used in EZB here where i am at,to tell you the pin #.

=