Total Time Spent Posted Wednesday, May 5, 2004 by Jeff
Week Total: 5.0
Semester Total: 203.0 Hours

Stunning, simply stunning.

05.05.2004 - [1 Hour] Archived Group Account Posted Wednesday, May 5, 2004 by Jeff
And we're finally done. Beautiful.

05.04.2004 - [4 Hours] Final Report Posted Wednesday, May 5, 2004 by Jeff
Worked on final report, finished up my parts, wrote the summary/conclusion. Will archive account to CD tomorrow morning once Bill is done editing things.

04.27.2004 - [6 Hours] Final presentation prep Posted Friday, April 30, 2004 by Jeff
Met with group to finish up final presentation and record footage for our final video. Then returned to my place with group, ran through presentation, and after they left worked on editing the video. I added a title, some "cool" transitions, and of course, excellent background music.

04.26.2004 - [1 Hour] Presentation work Posted Friday, April 30, 2004 by Jeff
Made my slides for the presentation, looked over what else people had thrown together.

04.25.2004 - [5 Hours] Package construction! Posted Friday, April 30, 2004 by Jeff
Built our package, helped out with the drill and such. It was quite entertaining. Hot glue is unquestionably everyone's friend. Anyway, the project actually looks sorta neat now. And it works :) That aside, we discovered that IR signals do, thankfully, travel through plexiglass. We're almost free!

04.24.2004 - [8 Hours] Complete success Posted Friday, April 30, 2004 by Jeff
Came in early after GABS stuff today and tried to figure out why the board wasn't working. Phil showed up a little later, and we discovered the clock had come loose for the Epson. Once that was fixed everything worked beautifully. We tried out Phil's code to send the image, and got an image to display on the monitor. The image was initially tiled in a weird fashion, but that was because I forgot to explain to Phil that the Epson only deals with word-aligned addresses/data. Also, the RGB values were incorrectly ordered/padded. As expected the bottom portion of the screen is a little whacked. Anyway, Bill and Ego are going to get materials for the packaging today and we're going to throw it all together tomorrow theoretically. Loading the picture is also hillariously slow. Also spent a large amount of time video taping this and then digitally encoding the video in the event that our board bursts into flames.

04.22.2004 - [1 Hour] Die, rabbits, die! Posted Friday, April 30, 2004 by Jeff
Apparently another rabbit is dead. I'm not sure why. Wandered into lab briefly to look at it, no luck.

04.20.2004 - [3 Hours] DRAM is evil! Posted Friday, April 30, 2004 by Jeff
Actually, it turns out that the main problem with getting pixels to map linearly to the screen was the fact that the DRAM module wasn't soldered down all the way. At this point we should be ready to actually load up a pixel, assuming Phil's software is set to go. The only issue appears to be the bottom portion of the screen, which doesn't look quite right.

04.19.2004 - [8 Hours] Success Posted Tuesday, April 20, 2004 by Jeff
Unbelievable. I actually got the Epson to output useful stuff to a monitor. I can set the screen to any color out of 65,000ish. However, as expected, since the DRAM chip is 4MB and the Epson is expecting 2MB, it's a little whacky. It's easy to set the screen to one single color, but loading a picture isn't going to look exactly right. Hopefully you should be able to recognize portions of it. I had it working around 2:30pm, and then it stopped this evening. It appeared as though the problem was related to the VGA connector, but it turned out the DRAM was loose and not soldered on all the way. Once that was fixed everything worked great. We also borrowed a video camera and taped everything functioning in case the board decides to spite us and burst into flames or something. Hopefully sometime soon Phil and Ego will finish software to send image data to the rabbit (I really don't understand they weren't done with that weeks ago, although right now they're working a mini-webserver to better demonstrate the image data via ethernet outcome). If I get a chance, and they're not done, I'll try to write my own later this week. Oh yes, and the reason the Epson didn't work was because the 2n2222 transistor's pinouts were incorrect. Once it was fly-wired correctly, it worked perfectly.

04.17.2004 - [11 Hours] Posted Sunday, April 18, 2004 by Jeff
Ahhh 3:30am. Today has been filled with some success as well as failure. I am now actually able to read and write to the Epson's registers. It returns the expected values and does all sorts of wonderous things in that respect. However, still no video output. Additionally, I question whether the DRAM chip is actually doing something productive. That aside, there was an unfortunate incident involving and LDO frying internally, thus placing 9V on all of the digital circuitry. This in turn killed a Rabbit and the DRAM chip, which were both replaced. I'm not sure why the LDO fried...I did briefly touch 9V power and ground when plugging in the board, which could have done it. I've taken many, many pictures of our setup as well as some of the prototyping boards that we came up with on a breadboard. I'll post them and add appropriate references in my journal at some point in the future.
Another issue that was run into is the fact that the current reference circuit doesn't really appear to be doing anything productive (it's supposed to provide a reference of 4.something mA). This may be why the VGA output isn't working. Although, when you hook one of the RGB pins (or especially the HSYNC/VSYNC pins) up to the oscilloscope, you get really interesting stuff...the HSYNC and VSYNC pins look right, but the RGB pins only run about 80mV peak-top-peak. I'm pretty sure it's supposed to be a bit higher than that for a monitor to actually interpret it. Something to ask the TA's on Monday I suppose.
Regardless, I probably won't be working on this at all tomorrow (today) as I have other homework, and I've allowed 477 to consume a considerable chunk of my life.

04.16.2004 - [15 Hours] ... Posted Sunday, April 18, 2004 by Jeff
Indeed, 15 hours. Ugh. I finished the last PLD and got that onto the board. Bill soldered on the DRAM chip, and we had Chuck solder on the Epson. Thus the board is now entirely propagated. After writing a test program to initialize the Epson and draw a red rectangle on the screen, I wasn't surprised when it failed. At that point an extended period of time was spent actually soldering on the debugging headers and then hooking up the respective address and data lines to the digital logic analyzer. Surprisingly, all of the PLD's function perfectly. Thus, from a Rabbit perspective, we're good to interface with the Epson. However, the Epson doesn't seem to want to respond. As 4:30am rolled around, I went home and went to sleep.

04.15.2004 - [2.5 Hours] Wheee Posted Thursday, April 15, 2004 by Jeff
Updated lab notebook a little, also worked on programming final PLD. Here's a pretty diagram for you!

MODE	RD/WR#	WE1#	WE0#	RD#	BS#	RESET#	M/R#	CS#
Reset - 000	1	1	1	1	1	0	1	0
CSOff - 001	1	1	1	1	1	1	1	1
ReadReg - 010	0	1	1	0	1	1	0	0
WriteReg - 011	1	0	0	1	1	1	0	0
Read - 100	0	1	1	0	1	1	1	0
Write - 101	1	0	0	1	1	1	1	0

04.14.2004 - [10 Hours] Kill me Posted Thursday, April 15, 2004 by Jeff
Taught myself CUPL in a day, programmed 3 out of the four pld's and soldered them onto the board (with ample amounts of flywiring). One of them ended up being deadbugged. Interestingly, I should note that the JEDEC files produced by Atmel's CUPL compiler have invalid checksums, so the Dataman programmer refuses to load them. However, if you edit the files and change the checksum to what the programmer expects, it works. Frightening, I know. Regardless, the address "latches" are now all in place (21-bits output, 2-bits mode select, 11-bits input). The only thing that remains at this point is to program the last PLD (which generates the control signals for the Epson), solder on the clock, and finally the DRAM. Oh yes, that isn't a typo up on the title. I spent 10 hours today (until 4:30am) working on this. Ughhh.

04.13.2004 - [1 Hour] Monkeys Posted Thursday, April 15, 2004 by Jeff
Fiddled with PLD's for a while, started looking up CUPL examples (Atmel has a JEDEC compiler for CUPL, but not ABEL).

04.12.2004 - [3 Hours] Lies Posted Monday, April 12, 2004 by Jeff
PLD's did come in today, I got them around 5pm. Spent 3 hours trying to figure out how to get a useful JEDEC file to program them with, no success. Atmel's development environment is whacked. I'm going to try to talk to one of the TA's on Wednesday. I should probably also note that I chose the ATF22LV10CQZ-30PC because it was the only 22v10 operating at 3.3V in a PDIP package that I could find. All of the other ones (especially the GAL's from Lattice) were PLCC packages.

04.12.2004 - [3 Hours] Soldering! Posted Monday, April 12, 2004 by Jeff
Yes, even more. I now have pretty much the entire board propagated (minus the Epson, DRAM, PLD's, pushbuttons, and VGA port...all of which shouldn't be too bad [excluding the Epson]). I think it's important for documentation purposes to point out that, one capacitor (I think it was a capacitor, it may have been something else) aside, I've soldered everything onto the board at this point without assistance from anyone else. PLD's didn't arive today either. Hopefully they'll show up tomorrow and by the middle/end of this week we (I) can start some serious testing with the Epson. On the plus side, the microcontroller is on the board and working (I can get it to flash LED's), and I think the IR circuit works, although I really have no idea, since that's about the only thing Bill is responsible for.

04.08.2004 - [4 Hours] Soldering! Posted Monday, April 12, 2004 by Jeff
I just couldn't stay away. I stayed up until 2am soldering. Pretty much all bypass caps are on, as well as the rabbit headers and some of the resistors. IR subsystem is next along with LED's, the rest of the resistors, and probably the analog part of the Epson area. Waiting for PLD's to come in so I can program those and then work on the Epson.

04.07.2004 - [2 Hours] Soldering and Ordering Posted Wednesday, April 7, 2004 by Jeff
Power subsystem on new board is mostly done (just have to add the 5V LDO). Preparing to throw rabbit on there and test it as well. Ordered the 3.3V PLD's today. 3-Day UPS, should hopefully be here next Monday, at which point we can start doing crazy Epson stuff.

04.05.2004 - [2 Hours] PLD / VGA Madness Posted Tuesday, April 6, 2004 by Jeff
Started ripping the VGA connector off of an old ISA video card of mine (we couldn't find any place to order them online). Also talked to John, the PLD solution I came up with seems to be the most viable. Forgot to check the programmer today, will do it in the next day or two and order the PLD's. Still waiting for our board to come in :-/.

04.03.2004 - [1 Hour] More PLD Madness Posted Tuesday, April 6, 2004 by Jeff
I found some 3.3V PLD's and will be ordering those as soon as I ensure that the programmer in lab can deal with them. There aren't any 26V12 versions of the 3.3V, only 22V10. Thus, there will be some fly wiring. It shouldn't be too bad though, since the footprints (less 4 pins) do line up for the most part. I still plan on talking to the TA on Monday.

04.02.2004 - [3 Hours] PLD Madness Posted Tuesday, April 6, 2004 by Jeff
After spending an extended period of time trying to figure out why the PLD's worked at 5V and not 3.3V, I re-read the spec sheets. Apparently the PLD's "don't blow up" between -1.3ish volts and 5.5ish volts. That doesn't mean they work. They only work between 4.25 and 5.5V. Joy. I'll be speaking with one of the TA's Monday to see what they think. Meanwhile I'll be thinking of alternative solutions as well.

03.31.2004 - [4 Hours] Discussion, PLD work Posted Friday, April 2, 2004 by Jeff
Met with team. Had at-length discussion about use of costatements, etc with Phil. I'm convinced that simplicity is a better way to approach things (and from what I've heard, costatements/functions can be flakey at times), but I've given up on the argument. I have sample code that works and can be gotten to a state which creates a usable demonstration in a short period of time, so I'm letting them do what they want. If it works, they win; if it doesn't, we have something to fall back on. I also started programming the PLD's and discovered that they aren't capable of having an 11-bit counter (not enough macrocells). As such I've devised an even more interesting solution. The rabbit will track the address internally and the PLD's can deal with a 9-bit counter. Once the 9-bit counter rolls over, the Rabbit will do a load to change the upper 10th/11th-bits each time. It should be a little slower, but it'll still work (and be faster than doing a load after each byte of data). Fun.

03.30.2004 - [2 Hours] Software, software Posted Friday, April 2, 2004 by Jeff
Looked at what Phil/Ego had done so far, was somewhat disturbed by how little was accomplished. Wrote a small test program which establishes a connection to PC, receives arbitrary data, outputs data to Ports F/G (Epson data/address lines), then polls for input on Port E (IR input lines). Tested it on the Rabbit with great success.

03.26.2004 - [4 Hours] Yuck Posted Friday, April 2, 2004 by Jeff
Revised board layout, submitted it back to the boardhouse. If we're lucky it'll be in a week from Monday. Going to concentrate on software and prototyping as much as possible this coming week.

03.25.2004 - [3 Hours] Good news, bad news Posted Friday, April 2, 2004 by Jeff
Well, I finished soldering the power-related components and the entire power "network" seems to work perfectly. Unfortunatley, the rabbit headers are wrong and the Epson's footprint is frighteningly close to being too "wide." Considered fly wiring some stuff, but there are a *lot* of wires. Going to talk to TA's tomorrow. Also started updating PCB layout in the (likely) event that we order a new PCB.

03.24.2004 - [4 Hours] Got board back, soldered some Posted Friday, April 2, 2004 by Jeff
Got PCB back, started soldering on power supply-related chips. Experimented on "junk" board for a while first.

03.11.2004 - [7 Hours] Finished layout Posted Thursday, March 11, 2004 by Jeff
Submitted to FreeDFM.com repeatedly, and fixed the minor errors they found (one with spacing of the pins on the custom rabbit headers, the other with a few traces that were too closely spaced, which was weird because the DRC in Orcad thought it was fine). Layout Plus is evil too, as it dies randomly and corrupts your last saved layout on occasion. Ugh. Regardless, layout is finally done. Now working on updating notebook and writing the remaining part of the layout homework.

03.10.2004 - [17 Hours] ... Posted Thursday, March 11, 2004 by Jeff
Layout. Repeatedly. Started out one way, spoke to Gilbert, changed strategy. Got key components around Epson routed. Gilbert realized that our board is evil, taught me how to use autorouter. Autorouted large portion of board. Spent too many hours resolving the last 3 or 4 traces which were pretty much impossible, but somehow got it. ugh.

03.09.2004 - [2 Hours] Layout Posted Thursday, March 11, 2004 by Jeff
Little more layout work. Started routing components where trace size isn't too important. Also made sure rabbit headers were spaced correctly and not mirrored.

03.08.2004 - [1 Hour] More layout Posted Thursday, March 11, 2004 by Jeff
Fiddled with layout a little. GABS (women's basketball pep band) has the Big 10 tournament final round today, so didn't have much time). Still waiting to get questions on trace sizes and spacing answered.

03.06.2004 - [10 Hours] Layout hell Posted Thursday, March 11, 2004 by Jeff
Started layout. Took an obscene amount of time to create custom footprints for some of the chips. Realized that I was doing a few things wrong (ie, once the chip was placed I couldn't draw traces to/from any of the pins). Fixed that. Started routing briefly, then stopped. Have to find out if it's okay to use 6mil traces, since the Epson pins are only ~6.5mils. If not, we're pretty much screwed.

03.02.2004 - [1.5 Hours] Posted Thursday, March 11, 2004 by Jeff
Design review. Spoke with Dr. Meyer about my timing hack for the epson, he seemed to think that there should be a cleaner way to do it (ie, running the rabbit clock to the Epson). After looking into it, that would require some weird fly wiring. Talked to him again later, decided just to go with the timing hack.

03.01.2004 - [6 Hours] Powerpoint! Posted Thursday, March 11, 2004 by Jeff
Yes, more powerpoint. Also finished ensuring schematic accuracy. At that point I went to the Math building and realized how messed up their transparency system is. Stayed for a couple of hours (accounted for in above time) waiting for something magical to happen, asked the lab assistant if he'd tell me where the printer was actually located so I could make sure it actually was being printed. Lab assistant indicated that "that's not possible." Right...because the printer is in some alternate dimension (or doesn't exist at all). Regardless, finally went home and slept. Luckily the transparency spit out the next day.

02.29.2004 - [6 Hours] Another meeting... Posted Thursday, March 11, 2004 by Jeff
Worked on presentation a lot more, Bill prototyped the IR controller. Played with the rabbit some as well - briefly dealing with clock generation. We realized that this is difficult without access to Port F (which we really can't give up due to pin requirements). Thus, we're going to go with the little timing "hack" instead of trying to generate a clock from the rabbit for BUSCLK on the Epson. Essentially we ensure that the enable signal for the Epson is asserted for at least two clock cycles, avoiding any timing issues with crossing clock domains. In a worse case scenario this results in data being latched and written twice into the DRAM, although realistically since the Epson as a wait signal, I'm guessing it takes a few cycles to write and thus we won't experience any delay issues.

02.26.2004 - [5 minutes] How the PLD's work Posted Sunday, February 29, 2004 by Jeff
People keep asking how the PLD's work. They basically sit on the Epson's data bus (PF[0:7], PG[0:7]) and latch data bits for a given mode. The mode is determined by two bits (PD[4,5]). There are four modes: Mode 0, do nothing; Mode 1, increment; Mode 2, latch first 11 bits of address (all in the lower PLD); Mode 3, latch last 10 bits (ADDR 11 on PLD1 - from PF0 and ADDR[12:20] on PLD2 - from PF1-PF7,PG0-PG1). Hurray. I never really accounted for the time that it took me to hack together this solution, so I'm doing that now. That's right. 5 minutes baby. Can we say "dirty hack"?

02.24.2004 - [4 Hours] You've got RAM! Posted Sunday, February 29, 2004 by Jeff
Ordered 4MB RAM modules for Epson. Excellent. Spec sheets will be uploaded at some point. I have them randomly scattered all over. Configuring the Epson to interface with this RAM should be "fun". Yes that's it, "fun". You have no idea how hard it was to find compatible RAM either. Or the number of companies that I talked to that basically said "screw you!" One of them wanted me to spend $100 to get 100 RAM chips. Riiiight. Apparently they don't understand "sample."

02.22.2004 - [6.5 Hours] Whee Posted Sunday, February 29, 2004 by Jeff
Met at 9pm to work on schematic, stayed up until ~ 2:30am. Fun. Schematic mostly done now. Found out some interesting things about the Epson. For instance, it has a whacky way of loading in configuration settings on reset (it basically reads them from the memory databus, but the memory isn't generating them...a dip switch connected to pullup resistors is. *shudder*) After checking with many other people (I tried calling Epson, but gave up) it seems as though is actually common practice.

02.21.2004 - [2 Hours] Meeting Posted Saturday, February 21, 2004 by Jeff
Met at 11:30am for two hours or so to work on website, discuss project, and find memory. Found some good places to try to order DRAM from (Micron, alsc.com, oki semiconductors). Going to call them on Monday and try to get RAM. [Actually, I had already asked to sample some old DRAM from a guy that I called, but he never got back to me, so we're looking elsewhere]. Also setup newspro so we can be lazy with respect to our journals.

02.18.2004 - [1 Hour] Proposal Posted Saturday, February 21, 2004 by Jeff
Updated proposal to reflect new design objectives. Phil wasn't able to find a JPEG decoder, so we're going to send raw image data to the Rabbit. Instead of JPEG decoding, we're going to add an on-screen display overlay of text for a menu kind of thing.

02.10.2004 - [1 minute] Order Shipped Posted Saturday, February 21, 2004 by Jeff
The Epson is on its way!

02.09.2004 - [2 Hours] Ordered a Part! Posted Saturday, February 21, 2004 by Jeff
Ordered Epson S1D13505 from Arrow Electronics. This one doesn't have built in memory, so will have to find a DRAM chip. Total cost (for two) was $38.24. Shutup. It didn't take two hours to *order* the part. It took two hours to *find* and *then* order the part. Yes. That's right, these things are difficult to find.

02.09.2004 - [1 Hour] Wheee Posted Saturday, February 21, 2004 by Jeff
Contacted Chris Robinson, Epson's Area Sales Manager. He indicated that the 13806 is being EOL'd but sent me a chart of other controllers. Recommended checking out Digikey to try and sample them. Note that this was after bouncing around Epson's phone system for an ungodly amount of time.

02.08.2004 - [2 Hours] Component Selection Posted Saturday, February 21, 2004 by Jeff
Started looking for places to sample components (Phil needs a list of ones that we're planning on using soon for homework).

02.03.2004 - [2 Hours] Final Project Proposal Posted Saturday, February 21, 2004 by Jeff
Worked on it. Bill will post it on the website once complete.

02.03.2004 - [0.5 Hours] IR vs. RF Posted Saturday, February 21, 2004 by Jeff
Bill is trying to decide between IR and RF. IR looks cheaper, but RF has more abilities/larger range. I think IR is the way to go (the user should have line-of-sight to the device anyway to see what picture is being displayed).

02.02.2004 - [1 Hour] Team Meeting Posted Saturday, February 21, 2004 by Jeff
Met again this evening, discussed project more. Have decided to go ahead with just interfacing with a VGA device (ie, CRT monitor/analog LCD). Will be receiving image data via ethernet and probably using the Epson S1D13806 to display image data. It has built in RAM (2MB) so we don't have to deal with memory interfacing.

02.02.2004 - [3 Hours] Bleh Posted Saturday, February 21, 2004 by Jeff
Did more research on USB, not looking good. The USB interfacing doesn't seem to be a huge deal (they have chips for that). However, if we're interfacing to a USB storage device we'll have to deal with a file system. Writing filesystem drivers would probably be incredibly painful.

01.29.2004 - [0.5 Hours] All Hail, Our Own Purdue! Posted Saturday, February 21, 2004 by Jeff
Overall project view at this time: A microcontroller interfacing
with a video chip (probably an S1D13806, which allows us to plug in any standard VGA device...LCD, CRT, etc) as well as a USB controller (I've found a few, but not sure which is best). It would also continue to interface with the IR controller, since instead of using an LCD screen we would have arbitrarily sized displays which could be placed in inaccessible locations.

01.28.2004 - [2 Hours] Of the Days We've Spent with You Posted Saturday, February 21, 2004 by Jeff
Morning meeting with 477 staff. Discussed initial project idea, seemed to be feasible. Also checked out some websites. Bill is looking at ritek.com for parts. Phil found an LCD controller...http://www.cirrus.com/en/pubs/proBulletin/7500-003.pdf Appears to be massive overkill for what we want to do.
I also found an epson controller...http://suncrusher.turkeyland.net/~jeff/stuff/477/S1D13806_MF1430-01.pdf This looks usable and something that we could interface with a microprocessor. It does have a large number of pins, though.
We're probably going to be using the rabbit microprocessor, since ethernet will be the easiest/best way to obtain image data. Also discussed using compactflash or usb storage devices.
Met at 4pm in senior design lab to finish layout.

01.27.2004 - [1 Hour] Thus We Raise Our Song Anew! Posted Saturday, February 21, 2004 by Jeff
Briefly met with group, explained progress to this point. Will finish board layout on Wednesday. Also started messing with shay account and making sure things work.

01.26.2004 - [7 Hours] Ever Greatful, Ever True! Posted Saturday, February 21, 2004 by Jeff
Spent ~7 hours working on orcad homework, finished schematic, netlist, and footprinting. Meeting with group tomorrow @ 9pm to discuss progress, start layout.

01.21.2004 - [1 Hour] Our Friendship May She Never Lack! Posted Saturday, February 21, 2004 by Jeff
Met with faculty advisors, decided we were going to go ahead with the digital picture frame idea. Started looking for LCD displays.

01.20.2004 - [2.5 Hours] Hail, Hail to Old Purdue! Posted Saturday, February 21, 2004 by Jeff
Met with group to once again discuss project ideas and begin working on preliminary project proposal. Eliminated Phil's idea for the knightrider thing. Basically down to digital picture frame and medicine dispenser.

01.19.2004 - [0.5 Hours] All Hail to Our Old Gold and Black! Posted Saturday, February 21, 2004 by Jeff
Group meeting this evening in ENAD. ENAD was closed, met in MSEE. Decided to do sheet music digital display with LCD. Writing up intitial project proposal later this week. Also decided to make the project a little more general, so instead of a sheet music display device, it's a digital picture frame.

01.15.2004 - [1.0 Hours] Hail, hail to old Purdue! Posted Saturday, February 21, 2004 by Jeff
Group numbers assigned. Initially group 1, bumped to group 12. Briefly discussed project ideas again after class. Still try to pick one of the 3 mentioned in the last entry and possibly come up with new ones.

01.13.2004 - [0.5 Hours] Watch out for the gnomes...they'll get you in your sleep Posted Saturday, February 21, 2004 by Jeff
Team members selected, briefly discussed project ideas.
Team members are:
Jeff Turkstra
Bill Kreider
Phil Boone
Ego Jegede
Project ideas discussed:
1) Pill dispensing/scheduling/warning system for elderly. Microcontroller would control LCD display as well as locking mechanism on pill dispenser. Potential wrist unit to alert individual that it's time to take pills. Unsure on whether or not good enough use of microcontroller. Also, creating such a small wrist unit may have issues as well.
2) Night Rider-like car interface. Would provide voice recognition to control things such as windshield wipers, lights, etc. Overall project idea seams mostly impractical. None of us have vehicles with onboard computers that can be interfaced with.
3) Electronic Music "Flip Folder". An LCD display that would allow one to a view a page of music and easily move to the next one by pushing a button. Would involve interfacing with some kind of centralized storage area containing the music as well as the display. Music could be stored as a JPEG image or in some other format. Problems with project include it being too simple potentially and finding a large enough LCD.

This is a test Posted Saturday, February 21, 2004 by Jeff
Boiler Up!