Herbert Graf wrote:

> > And why do I have to add a separate and distinct 'device driver'
> > for EVERY new device, unlike RS232 or firewire, where the
> > application talks to ONE STANDARDIZED API?
>
>         You don't. For example many storage devices use the "mass storage" driver,
> most modern OS's have the driver and therefore you don't need to install
> anything. Devices can also be "HID" which also don't require new drivers.

But I still have to load a -driver- for each and EVERY device.
With Firewire there is ONE driver and each app ties to it
as needed (and as expected).

And every MP3 player I've tried in the last month requires
that it's OWN driver be loaded. None seem to support the generic
'storage' device type (e.g. Yepp, IRiver, WaveX, Rio...).
It's been a royal PITA, especially since the Yepp install
nuked my USB connectivity and it took many many hours to purge the
registry after the uninstall royally messed up.
It will be a cold day in hades before Samsung gets another
dollar out of me.

> > And if one has used a few dozen different devices over time,
> > one is stuck with ALL those drivers being loaded by Winblows,
> > even if the device is now in the dumpster.
>
>         Any device worse a dollar has drivers with an uninstall feature, you get
> what you pay for.

The Yepp wasn't cheap, and it came from a supposedly reputable
company. It went back untested.

> > And of course USB works every time, and is EASY to implement
> > on embedded processors like the PIC (NOT!).
>
>         And firewire is? I don't think there is a PIC with firewire, there is a PIC
> with USB.

I don't know of many PIC applications that need the 400mbs pipe
firewire gives, but it looks to be LOT easier to code for.

Unfortunately I am about to be -forced- to implement USB on one of our
medical devices. I am not looking forward to the task.

> USB-serial devices out there it's just a matter of time before working with
> USB is easier then with the legacy ports.

PLEASE point me in the right direction. I have just been told
(this afternoon) that a research device which works just fine with
optically isolated RS232, must now do USB so that
it can tie to wireless 802.11 USB dongles for laptops. ARGGHH!!!

> > P&P stands for Plug and PRAY, remember?

Or is than now "Plug and PAY!".

>         I used to be like you, I think you should give USB a try again, today's
> devices and drivers are approaching flawless. TTYL

It looks like I'm not going to have a choice. By amazing coincidence
my boss has ordered that we "MUST HAVE" USB on our stimulator
for the clinical trials phase. I now get to dig through the
archives to find Novembers "PIC USB" thread and try to 'make it go'...

Any idea where to get those 'micro USB' PCB connectors,
suitable drivers/chips, PIC code and my life back?

I'd like to use some USB-Serial blobs,
but that has been explicitly ruled out since they (collaborative
design team) wants 802.11 without actually understanding what that really involves.

Maybe if I hadn't slammed USB I wouldn't be forced to use it now :{
Da pain... da pain.

Thanks for the collective ear and direction.

Robert

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.