|
Another possibility would be the FTDI Vinculum VDIP1. I have a couple on the bench and so far I like them. The only draw back I can see is the VDIP has to know EXACTLY how many bits are going to be written to it at a time.
I am planning to use the VDPI for a data logger from a gps module.
For the excel app, write the file as a CSV.
BrianT put together a nice how to, to get started with the VDPI.
http://www.picbasic.co.uk/forum/showthread.php?t=7700
Dave
Always wear safety glasses while programming.
|
To read a memory card directly on a PC, if needs to have a FAT file format as in the case of the DOSonChip. Note that the Microdrive, as mentioned in the second post does not have FAT so you cannot read the card directly on a PC.
The simplest solution is to use a PIC18 to write directly to SD/MicroSD or Compact Flash using FAT16/32. You can create CSV files for reading by Excel. I would recommend going with SD or MicroSD (instead of compact flash) as the physical interface to the PIC is simpler (uses much fewer lines) and the cards are smaller and less expensive.
|
In the past, I skipped the FAT16/32 step altogether. I save the data on the SD card (or CF card or whatever) according to the way I want it. When I need to retrieve the data, I just import it using the serial port on the PIC and Hyperterminal on a PC and save it to a file. Do some 'post-processing' on a PC with some VB instead of worrying about trying to reinvent the wheel and write a FAT16 filing system on a PIC.
|
Yes, that is definitely a viable solution if it fits the needs of the end user/customer.
|
True...Originally Posted by rmteo
I guess in my mind, FAT16/32 support is nice, but is it really worth the programming hassle, much less the code space, instruction cycles, etc. that might be a lot better off used elsewhere.
|
Sometimes it is a convenience issue - or the customer just wants a fool-proof system for the average user. See post #2 here:
http://www.picbasic.co.uk/forum/showthread.php?t=9619
|
Oh, I agree... If a guy is getting paid for it, then sure, use FAT and everything else, especially if you've already got the libraries and/or routines already written...
Biggest program I've got going is a full 18F4685 for that OBD2 reader...OBD2 interface, color gLCD, keypad, serial, SD card, and so on and so on...
Problem is, I'll probably never make any money off it!!!
Members who have read this thread : 0You do not have permission to view the list of names.
Posting Permissions
Bookmarks