Re: gEDA-user: home made hot plate
On Mar 2, 2007, at 12:57 PM, Ryan Seal wrote: Dave N6NZ wrote: Seeing DJ's hot plate photo brought to mind a link I once saw, where a guy built a home-brew SMT hot plate. I can't find the link, but as I recall, he used a few low-ohm high-watt power resistors epoxied to a piece of aluminum sheet. He drove it with a 0-30V bench supply and controlled the temperature manually by varying the voltage. Seems to me that one should be able to build a pretty good hot plate that way for not a lot of money. Although I would think that copper might give more uniform heat spreading than aluminum (at much greater expense, however, unless you get lucky). And a thermostatic temperature control shouldn't be hard. -dave Why not heating wire? How would you attach it to the hot plate? -a ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
RE: gEDA-user: home made hot plate
Hi all, Why not use a http://esmonde-white.com/toasteroven.html Kind regrds, Bert Timmerman. -Oorspronkelijk bericht- Van: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Namens Andy Peters Verzonden: vrijdag 2 maart 2007 21:16 Aan: gEDA user mailing list Onderwerp: Re: gEDA-user: home made hot plate On Mar 2, 2007, at 12:57 PM, Ryan Seal wrote: Dave N6NZ wrote: Seeing DJ's hot plate photo brought to mind a link I once saw, where a guy built a home-brew SMT hot plate. I can't find the link, but as I recall, he used a few low-ohm high-watt power resistors epoxied to a piece of aluminum sheet. He drove it with a 0-30V bench supply and controlled the temperature manually by varying the voltage. Seems to me that one should be able to build a pretty good hot plate that way for not a lot of money. Although I would think that copper might give more uniform heat spreading than aluminum (at much greater expense, however, unless you get lucky). And a thermostatic temperature control shouldn't be hard. -dave Why not heating wire? How would you attach it to the hot plate? -a ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: home made hot plate
On Fri, 2 Mar 2007 22:03:49 +0100 Bert Timmerman [EMAIL PROTECTED] wrote: Hi all, Why not use a http://esmonde-white.com/toasteroven.html Kind regrds, Bert Timmerman. #199 Circuit Cellar[1] Feb 2007 Has an interesting article about makeing a reflow oven controller based on a ATMega32 with Keypad and Graphic LCD. The authors Ihara,K. and Javed,D. are from Cornell University and needed a reliable way to reflow $200 worth of parts without the great expense of commercial reflow. Interesting article. [1] www.circuitcellar.com The article is not available online without buying it. Sorry :| -Marc pgp0q91lPOKFo.pgp Description: PGP signature ___ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
gEDA-user: C question
Look at the following:1) int bob[5] = {0x1, 0x2];2) int const bob[2] = {0x1,
0x2};3) static int const bob[2] = {0x1, 0x2};1 creates an initialized array in
ram.2 creates a read-only array - presumably in ROMWhat does 3 do? I think 3
compiles to a read-only area of ram. Am I correct?gene
___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: C question
On Sat, Mar 03, 2007 at 03:23:22AM +, [EMAIL PROTECTED] wrote:
Look at the following:1) int bob[5] = {0x1, 0x2];2) int const bob[2] = {0x1,
0x2};3) static int const bob[2] = {0x1, 0x2};1 creates an initialized array
in ram.2 creates a read-only array - presumably in ROMWhat does 3 do? I
think 3 compiles to a read-only area of ram. Am I correct?gene
static vs nothing (non-static, default) has to do with linking. A static
variable is not global and cannot be accessed from other modules (files,
basically) when compiling. It's basically hiding data and avoiding
namespace polution.
const vs nothing (non-const, default) determines whether you can modify
the data. The compiler may put the data somewhere different than it
would put other initialized data, or it may not. Where you put const
matters, because in one declaration different things might be protected.
For example,
const char *p; /* p points to 'const chars', an immutable string */
char const *p; /* the pointer p can't change, but the chars can */
const char const *p; /* neither p nor the chars it points at change */
So without looking it up, I'm not sure what your 'int const bob[]' means,
but you probably mean 'const int bob[]', the ints in bob don't change.
--
Ben Jackson AD7GD
[EMAIL PROTECTED]
http://www.ben.com/
___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
Re: gEDA-user: C question
On Sat, 03 Mar 2007 03:23:22 + (GMT)
[EMAIL PROTECTED] wrote:
Look at the following:1) int bob[5] = {0x1, 0x2];2) int const bob[2] =
{0x1, 0x2};3) static int const bob[2] = {0x1, 0x2};1 creates an
initialized array in ram.2 creates a read-only array - presumably in
ROMWhat does 3 do? I think 3 compiles to a read-only area of ram. Am
I correct?gene
Though I can't image the reason to put this question on this forum,
here's what I think:
'Static' is normally reserved to specify the data should never be
destroyed by the compiler if the compiler thinks it's not necessary any
more (eg. to make data 'static', i.e. available between function calls to
the same function).
'const' means the program shouldn't be able to change it. Like you said,
make it read-only.
John
___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
