USB 16Servo driver 4 mobile

Support Servo controllers and servos
1

Is there Pololu USB 16servo controller driver for MS Mobile 6.0?

2

Hello,

We don’t really know anything about drivers or development for Windows Mobile. The 16 servo controller uses the CP2102 USB-to-serial bridge, so we don’t have much control of the drivers, too. You could do a more general search by seeing if anyone has used that chip with your platform. Alternatively, if you know of any USB-to-serial adapter that works, you could use that with a simple serial version of the servo controller.

- Jan

3

I have followed the Silicon Lab instructions in below but still failed. Simply no response from my mobile and not lights from Servo controller.

WinCE 6.0 USBXpress Driver 1.3.1
Copyright © 2008 Silicon Laboratories, Inc.

Hardware Support

  • CP210x
  • C8051F32x/F34x

Platform Support

  • ARMV4I
  • MIPSII
  • MIPSII_FP
  • MIPSIV
  • MIPSIV_FP
  • SH4
  • x86

Files Included

  • SIUSBXP.DLL (Driver DLL)

  • SIUSBXP.REG (Registry Entry for SIUSBXP Driver)

  • SIUSBXP_LIB.DLL (API Interface DLL)

  • SIUSBXP_LIB.LIB (LIB file for API Interface DLL)

  • SIUSBXP_LIB.EXP (EXP file for API Interface DLL)

  • SIUSBXP_LIB.H (Header for the functions available in the API Interface DLL)

  • CP210xWinCETest.exe (Test app - Loopback)

  • CP210xWinCETest Source Code

  • CP210xWinCEtoWindowsHTTest.exe (Test App - Loopback/Null Modem to HyperTerminal)

  • CP210xWinCEtoWindowsHTTest Source Code

Release Dates

USBXpress for WinCE 1.3.1 - August 7, 2008

Installation Instructions

  1. Copy the SIUSBXP.DLL and SIUSBXP.REG files the the \Windows directory on
    the CE device.

  2. Plug in the CP210x Device with VID 10C4 and PID EA61. If your cP210x still contains the
    default VID and PID (10C4, EA60) use the CP210xSetIDs.exe application in located
    in Application Note to change the PID to EA61. AN144 and its software package (AN144SW) are
    available here:

    silabs.com/tgwWebApp/public/ … pnotes.htm

  3. When the dialog pops up saying “Unidentified USB Device” enter SIUSBXP for
    the driver name. The dialog should close when OK is pressed, and the LED on
    the CP210x development board should be lit. (If the dialog doesn’t pop up, but
    the LED on the CP210x development board is on, then it automatically found the
    device)

  4. The two included test applications can now be run (CP210xWinCETest.exe and
    CP210xWinCEtoWindowsHTTest.exe) using the CP210x in loopback mode. To put the
    device in a loopback state, disconnect the two jumpers for TXD and RXD, and reconnect
    one jumper joining the TXD and RXD pins closest to the USB port - see Figure 1. Under
    Normal Operation, running CP210xWinCEtoWindowsHTTest.exe will write to HyperTerminal
    when hooked up via a Null Modem Cable.

     	  Figure 1:

  Serial			     Serial

    T R D D D C R T R D D D C R
    X X T R C S T T X X T R C S T T
    D D R I D R S S D D R I D R S S
    . . . . . . . . .. . . . . . .
    J2 | | | | | | | | J2 | | | | | |
    . . . . . . . . .    . . . . . . .

       USB			      USB

    Normal Operation Loopback Mode

(Use w/WinCEtoWindowsHTTest.exe) (Use w/WinCETest.exe)

Release History

Release 1.3.1

  • Modified the SIUSBXP driver to work properly with ARM devices

Release 1.3

  • Added SI_SetBreak function for CP210x devices
  • Modified to allow proper access of devices using SI_GetNumDevices with SI_Open/Close

Release 1.2

  • Added SI_GetProductString function

Release 1.0

- Initial Release

4

Did you change the VID and PID? The servo controller ships with the PID set to a number Silicon Labs allocated for us, so you’ll first need to install the device with the driver we provide; you should then be able to use their set IDs application to set the IDs appropriately.

- Jan

5

I have tested the USB 16Servo with my C# apps on my XP and it was O.K.

After I changed the PID to EA61, Mobile still had no dialog pop up after the device had been plugged in.

Even the XP apps failed to run after that.

6

Once you change the PID, you have to reinstall the device with drivers from Silicon Labs; did you do that?

- Jan