4DSystems' uoled-96 uSD question
rjo_
Posts: 1,825
Help!!!
UPS finally got through the Christmas blitz and delivered my long awaited uoled-96. None of the documents I can find discuss writing to and reading from the uSD card... and the democode I have from 4D doesn't have prototype functions or document the Prop pins corresponding to the schematic of the SD card interface found on page 8 in v. 1.1 of the User Manual.
is there any -96 specific uSD code around? Anyone have the Prop pin assignments?
Happy New Year!
Rich
UPS finally got through the Christmas blitz and delivered my long awaited uoled-96. None of the documents I can find discuss writing to and reading from the uSD card... and the democode I have from 4D doesn't have prototype functions or document the Prop pins corresponding to the schematic of the SD card interface found on page 8 in v. 1.1 of the User Manual.
is there any -96 specific uSD code around? Anyone have the Prop pin assignments?
Happy New Year!
Rich
Comments
Goto the www.parallax.com website and find that part.
All manuals are there..
It is a little odd that nothing comes with the display..
Anyway all should be there..
cheers Ron
I've been there... must be my tired eyes.
Mike,
I have the FemtoBasic version for the 96, which is one of the reasons I'm so exited about this little display. That makes this the smallest "basic" computer in history[noparse]:)[/noparse] Everything is in there... including the uSD stuff. It is the first place I looked. (BUT I didn't want to have a brainfart trying to understand it today[noparse]:)[/noparse]
Long term, the FemtoBasic is more important to me than this little project, but I've been waiting so long to hook up the 96 to my GPS module, I started playing with that... and of course, I'm having unexpected problems... so I've changed my hardware setup back to what I know works... and of course it doesn't work either... lah dee dah dee dah...
I'm going to bed before I break something.
Thanks guys,
Rich
BUT I still don't see any demo code which shows writing to and reading from the uSD card on the 96... as there is for the 128 (which I tortured to death);
AND it looks like we need a one wire keyboard to go with Femto Basic... I've seen some discussion about this. We are one step away from a postage stamp sized Basic Computer... come on guys!!!
By the way, I just say the thread: "uOLED-96-Prop - Propeller Clock Speed Limitations." What a hoot!!!
For us slow learners, it doesn't hurt to hear... "cut yourself back to pll8x."
(over, over and over again[noparse]:)[/noparse]
If anyone has some working code... writing to the uSD of the 96, I'd appreciate it. I'm going to give it a shot... but there are some things I don't know and I'm not entirely sure what they are[noparse]:)[/noparse]
Thanks again,
Rich
pin assignment in the mount command, and it should work just fine.
If you can't make it work easily from what's written there, let me know and I'll
give additional details.
Thanks,
Rich
I modified Rokicki's sdrw_test.spin for the oled-96 and of course the·display routines are a little different...· Everything works fine: I can read and write to the directory, create files and write to them... but when it comes time to read from them, I'm running into what I think is an ascii·type issue.· The display shows one character and even that one isn't· right.
The files open and show almost correctly in WordPad.
I suspect that I need something like a character to string conversion... if so, where do I buy one?
here is the offending code...
·· r := sdfat.popen(string("newfiley.txt"), "r")
·· oled.cls
·· ii:=0
·· jj:=1
·· count:=0
·· repeat
····· r := sdfat.pgetc
····· if r < 0
········ quit
····· count:=count+1
····· oled.Putchar (r,ii,jj,0, 255,255,255)
····· ii++
····· if ii >= 10
······ ii:=0········
······ jj++
··
The full project is included with correct pinouts.
Thanks,
Rich
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Timothy D. Swieter
tdswieter.com
One little spark of imagination is all it takes for an idea to explode
My project (completely public domain) is to hook up a GPS and uoled and write locations, times and velocities to the uSD. The uSD is then read into a Mac and the data is turned into a tour using Applescript to drive Google Earth... I've tested all of the parts and they work. Which is why this is a little frustrating... I had it working a month ago... then destroyed some hardware, etc. etc. etc.
The uSD is working fine, but I don't have a version that isn't broke in some other way right now.
I'll get the prototype functions working correctly and post the whole project even if I don't have everything implemented correctly. Right now, I have a new problem reading time and date from the GPS. which makes no sense to me, since I have other code with exactly the same calls and it works fine.
Rich
Graham
Not sure if I'm picking up steam or not...most of the time I feel like I'm venting.· I'm starting to know what I· don't· know, which is encouraging[noparse]:)[/noparse]
My next step is to get myself sued for copyright infringement[noparse]:)[/noparse]
Tim... I found it... praise Jesus!· See attached.
Rich