Slashdot Mirror


Obtaining a USB Vendor/Product ID?

Qeygh asks: "I am interested in developing some hardware devices for my own use and, since RS-232 is dying, would like to use USB to communicate with them. If they work out well I may offer kits for sale. To do this right I should get a USB Vendor ID so that the devices can be uniquely identified by the host; but, being cheap, I don't want to drop the $1500 that USB.org charges for one. Does anyone know of any alternatives -- perhaps someone who bought a Vendor ID and re-sells small blocks of Product IDs? If no-one out there is doing this yet, is it a service that anyone else would use?"

8 of 37 comments (clear)

  1. If you're going to sell kits... by torpor · · Score: 4, Informative

    ... then, make an investment for the 'business' you will make from this, and pay the $1500 to get your own Vendor ID.

    Shirking out of paying a vendor ID when you want to sell product based on USB is just stupid. USB requires a unique vendor ID, that database of vendor ID's needs to be maintained and administered, and the cost for that is $1500. Fair enough, welcome to business.

    Pay the fee, if you're going to sell kits. It is the only thing that makes sense. You want to use USB, well ... there is a door fee, and that door fee is $1500.

    If you're not going to sell kits, you don't need your own Vendor ID. Just use nulls for everything, or make one up for your own lab purposes.

    --
    ; -- the corruption of government starts with its secrets. a truly free people keep no secrets. --
    1. Re:If you're going to sell kits... by thecampbeln · · Score: 2, Interesting
      Backup just a little bit... the guy is trying to something on the cheap while also trying doing it right! There's nothing wrong with that! *IF* his shit goes to plan, then he may do kits, but until then it's not a business.

      Your last bit of advice is the best... If you're not going to sell kits, you don't need your own Vendor ID. Just use nulls for everything, or make one up for your own lab purposes.... As long as this'll work for testing purposes, this should do him just fine.

      On another note, I agree with $1500 being inexpensive for a block, I thought it was a typo at first as for a business, that's less then a drop in the bucket! I agree with everything you said, just watch admonishing a guy who's doing the right thing, is all =)

      --
      "1984" was ment to be a warning, not a guidebook. You hear that Kim Jong-il!? BushCo?!
    2. Re:If you're going to sell kits... by Blkdeath · · Score: 3, Interesting
      the guy is trying to something on the cheap while also trying doing it right! There's nothing wrong with that!

      By the sounds of the article, it sounds as if he's going to sell a few kits to recoup some cash, and/or because others are interested and he wants to share. It doesn't sound to me as if he wants to become the next Rockafeller out of the deal.

      Your last bit of advice is the best... If you're not going to sell kits, you don't need your own Vendor ID. Just use nulls for everything, or make one up for your own lab purposes.... As long as this'll work for testing purposes, this should do him just fine.

      People used to say the same thing about IPv4 space. "Just use whatever block you want; it's only a lab!" Suddenly companies small and large alike are finding people announcing routes for their IP space halfway across the Internet. In other words, if you're going to "make up" your vendor ID, try to find a reserved/testing block or ensure that these devices will never get into the wild.

      On another note, I agree with $1500 being inexpensive for a block, I thought it was a typo at first as for a business, that's less then a drop in the bucket!

      Sounds like you've never run a small / SOHO business my friend. :)

      --
      BD Phone Home!

      Shameless plug. Like you weren't expecting it.

    3. Re:If you're going to sell kits... by wik · · Score: 2, Funny

      Don't worry, they're safe once you snap their cables. Just be careful of the ones crowded around a hub. They have been observed ganging up and strangling lesser PS/2 mice and other small vermin.

      If you're ever caught in a room with one, remember the A-type connector is benign, but the B-type cable can deliver a serious sticker shock.

      --
      / \
      \ / ASCII ribbon campaign for peace
      x
      / \
  2. Your Google-Fu is no good! by Anonymous Coward · · Score: 5, Informative
    You must master Jeet-Comb-Do.

    "- USB Product Id's or PID are supplied using our Vendor ID for each licensed product if your company doesn't already have a USB Vendor ID and doesn't want to pay the yearly fee for a Vendor ID from www.usb.org." -- Andrew Pargeter & Associates . Sales : 888-806-1053


    This seems to be your best bet. Doesn't look like it would be much of a problem to set up a program and sell or give PID's away though. But, what's to stop random developers from "barrowing" them and causing a difficult to diagnose problem down the line, should you pursue it?

    1. Re:Your Google-Fu is no good! by GreenKiwi · · Score: 2, Informative

      I can speak from experience that the driver and service provided by this company are excellent.

      kiwi

  3. Check with the chipset vendor by morcheeba · · Score: 4, Informative

    A lot of times, the manufacturer of the USB chipset you're using will sublet their product ID's for free or nominal cost. (example: Answer 3, part 2). They're happy to sell parts, and it costs them only 1.1 cents a year per PID (they've got a block of 64k; that's a lot of numbers)

    Also, correction to Qeygh's original question: it's not just $1500, it's $1500 every two years, for just the numbers Or you can join the USB org for $2500/year and get the numbers for free!

  4. Buy a chip, get PIDs for free by nmnilsson · · Score: 3, Informative

    I'd recommend buying a USB-RS232 chip.
    USB is USB - just a lot of specs to follow and nothing innovative.
    It gives you time to concentrate on 'your own' hardware, which after all is what you want.
    You get to use the vendors device drivers and VID, and get a couple of PIDs for your own use.

    My company has worked quite a bit with FTDI.
    They make reliable chips (AFAIKT), and give excellent support.

    --
    No sig to see here. Move along.