>> Well, I was figuring on emulating the FT245, to save driver
>> development. I do not know (and so far haven't got the time
...
>
>Don't think that Labview is able to understad the DLL,
>since the calls has to be compiled in.
>
>As far as I understand it, the DLL is for new projects where
>you build the SW to communicate with the FDTI-device and don't
>need Com-port emulation (it is not neccesary), the com-port
>driver is there to emulate the SW which normaly do com through
>either serial or LPT. Not knowing how labiew I supposed to work,
>but I imagine it is supposed to connect through LPT, then
>you have to emulate it with a virtual driver.

Umm, there is a Labview unit supplied in the zip file of this particular
USB-GPIB project. So my thinking was to make the PIC hardware as compatible
to the project as possible to minimise playing with the drivers. It sounds
like this may all be a non-problem, from what others have said about the
FTDI chip.

I must admit that I had only skim read the article, and not digested it
deeply. I think I am going to have to dig deeper and get some sample chips.

Anyone know of an alternative to the 75160/75161 GPIB Bus Driver chips? They
do seem to chew a heap of current. They also seem to be on notice as going
out of production with "last buy" notices at TI and I think I found "not
available" at National Semiconductor.

-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist