I have a solid state relay that's rated for 220VAC and 25A, it'll be used to switch on/off a toaster oven's heating element. The toaster oven uses 1500 watts. Here is the relay: http://search.digikey.com/scripts/DkSea ... =CC1006-ND
Digikey has a few heatsinks listed on that page with various "thermal resistance" measured in degrees C per watt
Or I can fold up some aluminum sheets to make my own heatsink
I also have a small fan (about 1" in diameter) that I can add to my design.
My questions are: Do I need a heat sink? If I do, how do I calculate the required "thermal resistance" I need using my specifications? Do I need that small cooling fan?
To celebrate our 300th ThingSpeak channel, we are announcing, “The Easiest Contest Everâ€.
All you have to do is build a project using a ThingSpeak web service, take a photo (if it applies), and writeup a description / how-to on your blog, Instructables, or email us the details. We are giving away 20 gift certificates to SparkFun valued at $50 each.
I made a bunch of parts in a library, I named some pins VCC, VDD, VIO, GND, and those are all pins marked as "pwr". When I placed the part into my schematic and then my board, they become automatically connected. I don't want this to happen as some devices are 5V and some are 3.3V. I don't want to rename the pins because they are supposed to match what's printed on the part exactly.
How do I tell Eagle to not automatically create nets for pin names?
use avr-objdump to generate a .lst file which is the assembly code that your C code creates, then you can exactly predict the timing since you know the length of each instruction exactly, which is given in the datasheet for your microcontroller
Does anybody here use the mbed? I got one recently and it's really great for trying out ARM. The DRM on it is pretty bad though, and the online compiler isn't the greatest. However you can till build binaries using GNU offline if you really need to.
In the spirit of "I made this for myself but somebody else might want one"...
I'm slightly reluctant to share this GUI I made, it has many short comings, and I don't want to make the source code clean and neat and stuff. I also don't want to constantly look after it when people eventually find things wrong with it or want new features.
WIth that said, I'm uploading what it is at the moment. The binary and source are included.
The main focus of my GUI is to reduce repetitive actions by remembering the most recently used files, and to let people use Windows file open dialogs instead of typing file paths.
Only one instance of OpenOCD can be used at any given time, and Telnet will always use the localhost at port 4444 . Like I said, it's very customized to my own specific needs. The GUI essentially dumbs down OpenOCD to something like avrdude or pickit2, but probably with even less features.
There are some launch options, so you can call "OpenOCDHelperGUI.exe pathtobinaryfile.bin" from a makefile, which will auto-fill the path-to-flash-file textbox (but not immediantly begin the write operation). If the argument is a .cfg file, then the .cfg file is added to the list of .cfg files (it will not be considered a flash binary). Finally, if the argument is a .ini file, then the settings for the GUI will be loaded from the specified .ini file instead of the one that is stored in your AppData folder.
Oh, and OpenOCD must be in your PATH environmental variable
The "Show Info" button is supposed to display information about the flash memory of the microcontroller, it's kind of important to know what offset to write the binary image to.
Spent some time and wrote a custom C# WinForm GUI for OpenOCD purely designed for writing files, handles launching OpenOCD and initiating Telnet connection in the background, problem solved
