Morning, folks!

Thanks to you both for your replies, too!

@jstarne: It's one of those frustrating issues, because sometimes (Close range) everything works, and I'm all like, woo 'n stuff. Then it moves a few metres away and it all goes to pot.

@Rich: Yeah, I'm leaning toward the bluetooth dongle at this stage. The camera had (Note, past tense) worked without issue, although I've now got the dreaded blue-light-wont-go-off-and-all-I-get-is-a-black-screen Eternal-Blue-Light problem. I notice you post a solution in that thread, Rich, but do you know of one that doesn't restrict the camera to working only when the EZB is on?

Additionally, thanks for the offer of a new dongle! I've got to head to a Maplin in the next few days for some unrelated supplies, though, so I'll see if I can't snag one up while I'm there. For reference, though, I'm not far from Northampton.

Thanks again! Let's see if a new dongle will make all my gremlins go away!

I believe the camera has issues when the battery is not charged but when charged it's fine, so I would suggest keeping the battery attached, giving it a good charge and then trying it. I also read that using PWM control on the camera signal can get it working but I forget the percentage that does it.

Thanks, Rich. I've left it plugged in charging while I'm at work, so I'll see what happens this evening!

I have the exact same problem. 100%. However, the configuration is different. I am using my macbook with parallels with Win8. Built-in bluetooth. I know EZ-Robot clearly states no support for ARC running in virtual machine. So, I am going to try few options of powering the camera USB with the powered USB hub and/or with an external blueetooth dongle.

Update:

Well, this is an odd update. As mentioned before, I ended up with a Blue-light-of-death problem. Even when fully charged (Left for 24 hours) the light wouldn't go out. I was considering getting a new camera - it's something I had considered following previous problems. Before that, though, decided to try one more thing. I popped the case open, located the + and - pins that connect the battery to the board and shorted them briefly. (I do like to live risky!). My assumption was that this would interrupt the power completely, perhaps resetting the device. It did indeed work, the light went out. A few seconds later, I powered it back up and it worked correctly.

More curiously, and I cannot fathom this one for the life of me, my interference problem was also resolved. No ports were changed, no drivers re-installed. Just this one act and I no longer suffer connection drops with the camera on. I have absolutely no idea why, but for me, this seems to have done the job.

Any takers on explaining this?

Disclaimer: I do not recommend trying this! Shorting a battery could have consequences, so don't come blaming me (Or EzB) if you let out the magic smoke!

A safer way would be to disconnect the battery and reconnect it... but shorting it sounds like it works for those thrill seekers amongst us

Not a clue why it fixed it. I will put it down to the old "turn it off and back on again" fix that works on pretty much everything.

I considered the safe option, but there was solder, wires, chickens and a giraffe called Simon, so I figured quick 'n easy was the way to go

In my configuration (Macbook, Parallels, Win 8 and Built-in bluetooth), I could make it run w/o disconnecting by reducing the resolution of the camera (I chose the lowest resolution in the pull-down menu).