
fj604
Members-
Content Count
41 -
Joined
-
Last visited
-
Days Won
4
fj604 last won the day on May 4 2012
fj604 had the most liked content!
About fj604
-
Rank
Advanced Member
-
Yes it does - 23 Celcius is normal room temperature. I'll check with Maxim DS1624 though. Actually SLAU144 has the same formulas for MSP430x2xx - page 597 - 600. http://www.ti.com/lit/ug/slau144i/slau144i.pdf
-
More info on ADC calibration constants: SLAU144 - page 597 - 600. http://www.ti.com/lit/ug/slau144i/slau144i.pdf It shows these only for ADC12 - are they the same for ADC10?
-
More info regarding temperature sensor calibration in SLAU208, page 53: http://www.ti.com/lit/ug/slau208j/slau208j.pdf
-
Brilliant. Will try now. Thank you!! [edit] Your code works perfectly. Before calibration: 29C After calibration: 23C My (messy breadboard) talking clock now has a thermometer feature- thanks to you! P.S. "there is no dark side in the moon, really. As a matter of fact it's all dark"
-
This rudimentary debouncing code seems to work but the whole idea does not seem to be good - a loop inside ISR. Comments? #define DEBOUNCE_CYCLES 200 #define S2 BIT3 volatile uint8_t s2 = 0; #pragma vector=PORT1_VECTOR __interrupt void Port_1(void) { uint16_t s=0, t; if (P1IFG & S2) { if (!s2) { for (t=0; t if (! (P1IN & S2)) s++; if (s > DEBOUNCE_CYCLES / 2) s2 = 1; // set s2 flag } } P1IFG &= ~S2; // clear interrupt bit } _low_power_mode_off_on_exit(); }
-
MSP430G2452 datasheet http://www.ti.com/lit/ds/symlink/msp430g2452.pdf page 12 shows that ADC calibration constants should be in TLV, but their definitions such as CAL_ADC_15T30 are in neither .h nor .lnk files. None of the code examples uses ADC calibration. WTH?
-
slac467a has these formulas in msp430g2x32_adc10_10.c: // oF = ((A10/1024)*1500mV)-923mV)*1/1.97mV = A10*761/1024 - 468 temp = ADC10MEM; IntDegF = ((temp - 630) * 761) / 1024; // oC = ((A10/1024)*1500mV)-986mV)*1/3.55mV = A10*423/1024 - 278 temp = ADC10MEM; IntDegC = ((temp - 673) * 423) / 1024;
-
Would anyone be interested in a talking clock made with MSP430G2231? Also using AS1108 4-digit 7-segment LED driver and a ChipcCorder ISD1700 series for voice. What a mess Clock speaks in Russian
-
As long as you aren't using the crystal oscilator P2.6 and P2.7 are available as GPIO pins. (From memory I think you have to ensure BIT6 and BIT7 are cleared in P2SEL. Dan void sound_init(void) { P2SEL = 0; // Disable XIN/XOUT P2DIR = BUZZER_PIN; // XOUT pin = P2.7 }
-
This project uses all GPIO pins on P1 and also P2.7. The only one left unused is P2.6 - any ideas on a function to add?
-
I've never encased any of my projects before, but tempted to make a case for this one - and the next which I hope to finish soon and post here. I am mortally terrified of a thought of having to find a suitable case and have no idea how to mount a LED matrix into it. This article/video http://blog.makezine.com/2010/04/27/circuit-skills-electronics-enlosure/ explains the basics, but does not tell how to mount things like LED matrices, 7-segment displays, speakers etc. Any ideas or pointers please? Also, would annotations in the video be helpful, or is it pretty much self-explanatory?
-
The 2211 chip that came with the Launchpad is not useless! Here is what can be done with it: I decided to drive a LED matrix with the AS1106 chip from Austria Microsystems. It is a an equivalent of MAX7219 but can work with 3.3V that Launchpad supplies. Two buttons on a breadboard move the "catcher", and a single button on the Launchpad changes the game speed. Launchpad LEDs are used to indicate a catch (green) or a miss (red). A piezo buzzer can be added for (very annoying) sound effects beeps. I thought the whole thing has a certain 1970's touch to it #includ
-
This code uses input capture as well: http://www.43oh.com/forum/viewtopic.php?f=10&t=1053