I have looked over everything on the ftdi website. the examples are, as to be expected, incomplete and not very useful. the example for visual basic communication, I couldn't get to work on it's own. I had to dig up some older code that I've worked with before to modify the example to make it work. on my 3rd day of messing with it and not getting any successful communication, I finally realized, I've used this api before with the uChameleon device!
yes, I believe you're right. you can get slightly faster transfer rates/better performance by using the direct interface driver, as apposed to the virtual com port. I was surprised more people didn't use it, then I remembered, most arduino projects are only temporary hobby projects, not something that would have thousands of hours put into the code.
Can you explain why you need to communicate with an Arduino but not using a serial port? Hardware-wise, how would this be accomplished?
I suspect most arduino users are unaware that it does come with both a virtual com port driver and a direct interface driver on windows. nothing at all needs to be changed on the arduino side of things, but you do need to know the right api's and how to use them properly in the computer program.
maybe this is actually something I can contribute to the community, a usable d2xx class/api wrapper. anyone care to help me write up a quick tutorial after a class is put together?