OpenServo.com

[Bundy]

Hello @ all
I got an OSv3 board and an OSIF and I'm trying to get it to live using Win7. I installed driver OSIF_V2.1\drivers\V2\ and run openservointerface.exe. The naked OS board is connected and has it's 7V supply. The first Bus Scan says:
Welcome to OpenServo test application v0.61
OSIF initiased! Now run a bus scan...
scanbus: found adapter

scanbus: found 0 adapters

Found adapter OSIF_1
Selected Adapter OSIF_1
Starting scan

The scan returned 0 devices

Found 0 OpenServo devices

Scanning first adapter

A second bus scan says:
scanbus: found adapter

scanbus: found -1 adapters

No adapters found, but got this far regardless. Something went horribly wrong.

So I tried XP. Same result

What went horribly wrong?

[jharvey]

Sounds like a soft supply to me. I typically run mine with a 5 amp current limit. Can you bump up the currents supply?

[Bundy]

are you kidding or where do your 5 amps go?

there is an additional message in the terminal: wUSB error: error sending control message: win error
does it help anyone?

[jharvey]

Nope not kidding. It doesn't use a continous 5A, it simply draws short little spikes of current, and my supply won't properly provide them unless I crank up the current. Failure to provide enough energy for those short spikes causes brown out issues.

Batteries typically have no problem producing those short spikes, can you connect it to a 7.2v pack?

[Bundy]

no sorry, it doesn't work with a battery pack either
5V are available on the board, I just measured
anything else I could check?

[jharvey]

libusb is often a bit finicky with windows. I know the process appears like it needs to happen in a specific sequence, or it will get buggered. I believe the issue is something to do with root permissions. I know that in linux you are required to be root when using libusb, unless you do some special configuration stuff. I should have written down the sequence that seemed to work for me on a WinXP box. I seem to recall that from a fresh boot,
I would plug in the OSIF with the OSV3 attached,
then connect power to the OSV3 header,
then wait at least 3 seconds,
then open the software and click the scan button.

Once it would scan successfully typically coming up as 0x10, basically every thing else would work. I think people often get buggered with the 3 second thing.

When it would get buggered such that it couldn't find the OSIF, I would reboot the PC and it would come out of it.

Try that sequence, and keep any significant notes as you go from step to step. Then if it doesn't work, post your log. Also I should ask, this is an OSIF and OSV3 from Robotfuzz, correct? Basically, your OSV3 has been pre-loaded with the firmware right? I know Robotfuzz sells them pre-programmed.

I've been using them on Linux for some time now, so I'm a bit fuzzy on the windows side of it.

[Bundy]

I just tried as you suggested
[img]hmmm[/img] couldn't link the screenshot but the text is like in the first post
after the next bus scan even the OSIF disappeared

Starting the openservotestinterface.exe (v0.61) again leads to "No adapters found, but got this far regardless. Something went horribly wrong."

Plugin in the USB again it behaves like the first start. Looks to me a bit like trouble in the driver?

The hardware is from robotfuzz OSv3 and OSIF

[jharvey]

Sounds like the OSIF isn't being detected. USBsnoop may offer some insight into the USB enumeration steps and might help show things like Vendor ID's and where it's connected in the USB structure.

Barry will probably be along before to long. He may have more insight, I don't have a win7 platform to work with.

I just plugged in my OSIF that works on my Linux box, into my XP machine which it used to work on. I get a USB error noting that it's not recognized, and the program tells me it can't find the device. Hmmm, I wonder, could a windows update break the libusd stuff. USBsnoop shows 4 devices that are listed as UNKNOWN. USBsnoop shows OSIFbl with a VID of 0403, and PID of 6666. So it appears it enumerated. Perhaps the libusb driver isn't functioning properly. That would explain why the software isn't able to connect to it. I'm not sure how to verify that libusb is working. I can verify that it's not working on this XP machine, and it used to work on this machine. I should also try this after a reboot, to ensure everything has fired off cleanly.

I plug in the OSIF and get a green LED. Then I open the software and get this in the log window.

Welcome to OpenServo test application v0.61
OSIF initiased! Now run a bus scan...
scanbus: found adapter

scanbus: found -1 adapters

No adapters found, but got this far regardless. Something went horribly wrong.

[ginge]

[lvmarcoux]

I had the same kind of problems and found that:
-As long as your servo is powered for more than a few seconds,your scan will succeed and detect the device;
-If the servo is powered off (either B+ or Gnd disconnect) but still on the bus, the scan will hang;
-if the OSIF is alone on the twi net (servo disconnected), the scan will get thru.
-If you send a reset to the servo and try to rescan right after, the scan will hang

This is using usblib0 on XP sp3, OSIF is powered thru USB, servo by a 7.2V pack.

A servo unpowered or in a reset sequence will break the twi network, locking the OSIF for any attempted communicaiton. Resetting the OSIF will bring everything back in working order.

This problem makes the flash through OSIF nearly useless. I rewrote the flash program in Python to be able to control the scanning and the timing of the flash.

Any idea what an unpowered servo is to the TWI lines?

[ginge]

an unpowered TWI device will hold the lines of TWI low, causing a bus lockup.

Shouldn't lock the OSIF though. Will look into that, maybe a bug has crept in on a newer firmware.
_________________
http://www.headfuzz.co.uk/
http://www.robotfuzz.co.uk/