It's probably not a good idea to assume that everyone knows what a 'SID' is! I had to search for it, and finally found something audio related (I saw you had an LM386), that seemed to fit the bill.
SID = Sound Interface Device
First rule of good descriptive writing is to use commonly understood terminology, and where necessary to define the terminology that's not commonly understood.
I'm an avid R/C modeler, and I'm just finishing up my latest 'winter building' project, a 150" wingspan Douglas DC-3! http://http://en.wikipedia.org/wiki/Douglas_DC-3 I wanted to add a continuously flashing strobe light on the vertical stabilizer of the airplane, and remotely controlled Red (left) and Green (right) navigation lights on the wingtips. To satisfy this need, I decided to 'roll my own' R/C Aircraft Lighting Controller to finish off my DC-3 airplane!
[attachment=0]
This design is based on the PIC 12F629 microcontroller. The code for this project is written in 'C', using the CCS 'C' compiler. The schematic and board were done using Cadsoft Eagle software, and the PCB fabrication was done by OshPark!
The code is pretty simple. Timer0 in the PIC is used to generate the continuous 'Strobe' output signal of 2 seconds Off, 0.3 seconds On. Timer1 is used to measure the incoming pulse width of the R/C signal. This pulse width varies between approximately 1.0mS and 2.0mS, representing servo position and repeats at approximately 50Hz. My code switches the 'Nav' lights On at pulse width of approximately 1.5ms, with some hysteresis to prevent flickering about the trigger point. The code also will detect when the R/C input signal is (1) lost, or (2) intermittent, and will flash an error code using the Nav lights.
Which 'C' compiler are you using? If you happen to be using the CCS compiler then I can probably help! If not, I may be able to give you some general pointers anyway!
BTW, I did update my original GLCD clock, and I've had new boards here for a while, but I have not yet gotten around to playing with them! Too many projects, too little time :-)!
I'm looking for someone that can design an on-line membership application for a club I belong to. The application needs to be somewhat dynamic so that it 'populates' correctly depending on the type of application (New or Renewal - selected with a radio button). The application also must be 'aware' of the date as the dues amount is pro-rated based on the join date. Once an application is complete, PayPal will be used for billing.
I currently have a couple of static pages doing this membership function, but I'd like to clean it up and stream-line things a bit! I'm NOT looking for a freebie here, and am quite willing to discuss some sort of compensation if you are interested. Perhaps you'd like something from SEEED, Sparkfun, or Adafruit?
I'll send more details to anyone interested in taking a look at this project!
I'm looking for someone to code a single webpage for me that will be a member sign-up form for a model airplane club I'm involved in. I've already got a pretty functional page doing this using FrontPage, but it's clunky, and I'd like to add some dynamic content (example: membership dues change depending on sign-up date, etc.). Basically, I want something that is more functional, and looks more professional. If you are interested in this project, we can work out some mutually agreed upon payment, such as a credit at Sparkfun, Adafruit, or SeeedStudio, etc.
Contact me via PM, and then we can continue via email!
Here is the schematic for the GPS to Xbee Bridge. I'm posting it in .pdf format because I'm not sure if an Eagle.sch file is convenient for you or not? If you'd like the Eagle file as well, I can post that too!
Here is my latest project, a 'GPS to Xbee Bridge'. This project utilizes a USGlobalsat BR-355 GPS receiver, and an Xbee module to wirelessly transmit a GPS-derived time/date info packet to a variety of home-brew clocks around my home! These clocks consist of an odd mix of Nixie Tube clocks and GLCD clocks that I've design and built over the years! The design is based on a PIC 18F14K22 processor which receives and parses incoming NMEA data from the BR-355 GPS module, and an Xbee or Xbee Pro wireless module. These packets are transmitted every 15 seconds!
[attachment=0]
The prototype for this project looks pretty good, however, I made a pretty glaring mistake in the initial design by omitting an RS232-to-TTL converter IC between the GPS and the PIC! I hot-glued a MAX3232 IC to the back of the board deadbug style, and ran all my wires on the backside. Of course, the final PCB version will include this IC! The board itself is a 'Sick of Beige' size format, and will be mounted thus once complete!
Prototype boards were sourced through the awesome OSHPark service!!
For anyone that's interested, here is a picture of my Nixie Clock prototype! I had the hardwood base made out of Maple by a local cabinet shop for $30, and the Acrylic cover was sourced from a company that specializes in display cases for about $15. The clock is working extremely well, and really looks nice, especially in low light conditions!
[attachment=0]
Since the original concept, I've made a number of circuit changes based on the performance of the prototype. Most significantly, I've eliminated the USB interface, as the DS3231 RTC has such low drift that it wasn't worth the effort! The pushbutton time/date setting feature is not bad, and I plan to add an Xbee or Nordic receiver to the final design for periodic remote time updates via GPS.
There are a number of board issues with the current design (which thankfully cannot be seen!) that will require some modifications. It's minor stuff, and I plan to get to it as soon as I finish the 'GPS-to-Xbee' bridge project I'm wrapping up now that will allow automatic synchronization of the Nixie clock to GPS time. I'll post a description of this project shortly!
I need to keep moving on this project, as Christmas is fast approaching! Sigh! So many projects, so little time!!
Sorry for the late reply as I haven't visited in a while, and only did so recently to post another project!
The Nixie clock project was completed to the working prototype stage. There were a couple of issues with the original PCB's that need to be taken care of, and I need to wrap up the documentation. I'm planning a build of 5 clocks for Christmas presents, so I'm getting back to this project very soon!
I've been running Cadsoft Eagle v5.12 with a hobbyist license for the past year or so. I've resisted "upgrading" to Eagle v6 because the current version is basically doing everything I need. Lately, however, I've been encountering libraries and designs that I cannot open because they are in the v6 format. Aside from cost, are there any reasons not to "upgrade" to Eagle v6?
The 'protocol' is a clone of the RCS RS-21 network temperature sensor protocol. These sensors are no longer available, so I got a manual for one, and wrote my firmware to respond in an identical fashion. The 'Master' is an RCS StarGate system. PM me your email address, and I'll send you the RS-21 docs and the firmware.
I should mention that the code is written in 'C' for the CCS 'C' compiler, and is pretty straight-forward. That may not matter, however, if you don't code in C!
OK, your GLCD clock looks great!! I guess you had no trouble figuring out the programming menu?
I'm working on a new version of the firmware that adds a couple of useful features:
1. The ability to toggle between mm/dd/yy and dd/mm/yy formats 2. The ability to toggle between deg. C and deg. F 3. A temperature correction algorithm for the internal RTC temp sensor
I've also noticed that the temp. display tends to read high. I believe that this is due to internal heating in the RTC chip, and/or elevated local temp. due to heating from nearby components. I've collected a lot of data on this temp. "offset", and I think I've got a pretty good handle on this, and I'm testing it now!
