It looks like you have registered but you have not yet posted and
messages. Our requirements are that you must post at least two
messages, to allow the moderators to review your registration, before
you will be allowed access to the full range of forum areas.

Please make a couple of posts, until then you may see a notice that
says you are banned from certain forum areas.

Thanks, I`ve got a copy of this now. There is an error on the Vdrive2 sheet I have also found. The link for SPI/UART is incorrect on both the overlay and the example with a micro. The 0v and 3V3 are transposed, in the example for microcontroller the link is in the position for SPI and not UART mode which is being used.

Vdrive2 logger

I have built a logger using the Vdrive2 and wrote a blog on it. At the blog I posted schematics and code for both a 8 bit and 10 bit version. The logger uses a DS1307 for a time stamp and saves data at 1 per second using a 16F688 pic and Pic Pro Basic.

Re: Vinculum Vdrive2

WE are using VDRIVE2 with Firmware Ver 03.66VDAPF.We are interfacing it with our USB device which is a fingerprint sensor Morphosmart MSO CBM.Details of the Slave Device (fingerprint sensor): - Communication Class Device in accordance with USB Device Class Specifications version 2.0- The Device use full speed transfer rate of 12Mbits/s- Compatible with USB 1.1 and USB 2.0 hosts and hubsWE tested our sensor with a GET DESCRIPTOR string using the command mode. We are getting desired response when we send the 'DRD' command. But, on our application we don't want the command interface. We want to send/receive data transparently (i.e. w/o using any commands).The GET DESCRIPTOR string is a data that we send to the sensor , after which the sensor replies:SYNCÔˇžName: CBMMobi5 Serial Number: 0944

This is our GET DESCRIPTOR string (18 Bytes):$53$59$4E$43$04$00$00$00$FB$FF$FF$FF$05$01$00$2F$4 5$4EIn the above string $53 is a hex value, so we are sending 18 bytes written above in HEX format. We send these values using a Windows XP PC serial PORT. On the PC we are using Terminal v1.9b software (Bray++) and we send hex data using the transmit macros field in Terminal software.Now while testing, we used the device in command mode initially. Selected the device SC 1 and then pulled the DATAREQ line (pin 36 of VNC1L) low (0V), after that the DATAACK line also became low. So now vdrive2 is in DATA MODE. But, now if we send the GET DESCRIPTOR string then we DON'T get the desired response. Rather we don't get any response from the device. Thus, we fail to interface the sensor in data mode.

But the same can be done successfully using command mode only and the following is the device log:Command mode successful trial log:Commands:ipaqp2qd 0qd 1sc 1dsd 18%%%%%%%% Comment: send the GET DESCRIPTOR string (18 Bytes) using the transmit macros field in Terminal software. %%%%%%%%%%%%drd

Our objective is to interface without using any commands after we select the device (i.e. after sc 1). We want to send our data (for eg. the GET DESCRIPTOR string ) directly to the sensor and get the response from the sensor without using any commands. P.S.:We have also tried the VCDC firmware and failed in a similar manner i.e. we didn't get any reply from the sensor.

Re: Vinculum Vdrive2

I got inconsistent responses with different usb flash drives so I gave up using the Vinculum for use as a data logger. I will be looking into using a SD card or a Datakey from Datakey Electronics. http://www.datakeyelectronics.com/ With the Datakey, the interface is made to go with the key. With USB sticks, you don't know what your getting.