Comments on: LED Cylinder http://www.nycresistor.com/2008/07/26/led-cylinder/ We learn, share, and make things Tue, 07 Feb 2012 19:00:00 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Dominic http://www.nycresistor.com/2008/07/26/led-cylinder/comment-page-1/#comment-7198 Dominic Mon, 04 Apr 2011 08:55:00 +0000 http://www.nycresistor.com/?p=346#comment-7198 can someone please tell me the pin connections if im using a Arduino Duemilanove as the botton board.. can someone please tell me the pin connections if im using a Arduino Duemilanove as the botton board..

]]> By: Fede Sideralis http://www.nycresistor.com/2008/07/26/led-cylinder/comment-page-1/#comment-6932 Fede Sideralis Tue, 02 Nov 2010 19:01:54 +0000 http://www.nycresistor.com/?p=346#comment-6932 Ufortunatly Steve is right. You have to change your leds! Fede Ufortunatly Steve is right. You have to change your leds! Fede

]]> By: Steve- http://www.nycresistor.com/2008/07/26/led-cylinder/comment-page-1/#comment-6930 Steve- Tue, 02 Nov 2010 10:39:53 +0000 http://www.nycresistor.com/?p=346#comment-6930 Big mistake. You'll have to change all the LEDS. It's a hardware problem, not programming Big mistake. You'll have to change all the LEDS. It's a hardware problem, not programming

]]> By: TheSharpieOne http://www.nycresistor.com/2008/07/26/led-cylinder/comment-page-1/#comment-6901 TheSharpieOne Sun, 24 Oct 2010 12:03:19 +0000 http://www.nycresistor.com/?p=346#comment-6901 I haven't had time to do anything in a while, I just started soldering all the LEDs to the music wire... a pain. I just now noticed that I had gotten common-anode and not common-cathode. How screwed am I? Is is possible to changing some things in the programming, or would have I to re-do something on the board, or order common-cathode LEDs..... I haven't had time to do anything in a while, I just started soldering all the LEDs to the music wire… a pain. I just now noticed that I had gotten common-anode and not common-cathode. How screwed am I? Is is possible to changing some things in the programming, or would have I to re-do something on the board, or order common-cathode LEDs…..

]]> By: joeblowm http://www.nycresistor.com/2008/07/26/led-cylinder/comment-page-1/#comment-6371 joeblowm Wed, 31 Mar 2010 22:06:32 +0000 http://www.nycresistor.com/?p=346#comment-6371 Very cool use of the 5940 and Arduino. I'm working on a project that is similar and hopefully you can give me some direction. I want to use the 5940 to control an array of 10x10 RGB leds. How much of your design could I use for this? Very cool use of the 5940 and Arduino. I'm working on a project that is similar and hopefully you can give me some direction. I want to use the 5940 to control an array of 10×10 RGB leds. How much of your design could I use for this?

]]> By: TheSharpieOne http://www.nycresistor.com/2008/07/26/led-cylinder/comment-page-1/#comment-6156 TheSharpieOne Mon, 01 Feb 2010 11:12:23 +0000 http://www.nycresistor.com/?p=346#comment-6156 What I have so far is:<br>The PCB<br>4X TLC5940NT (led-drivers)<br>5X IRLU3715 (mosfets)<br>3X TC4427A (mosfets drivers)<br>1X ATMEGA328<br>and the LEDs<br>.015 OD music wire. (in shipping.... hope i for the right diameter)<br><br>Were you able to find your buy list? What I have so far is:
The PCB
4X TLC5940NT (led-drivers)
5X IRLU3715 (mosfets)
3X TC4427A (mosfets drivers)
1X ATMEGA328
and the LEDs
.015 OD music wire. (in shipping…. hope i for the right diameter)

Were you able to find your buy list?

]]> By: daveclausen http://www.nycresistor.com/2008/07/26/led-cylinder/comment-page-1/#comment-6102 daveclausen Sat, 16 Jan 2010 22:37:43 +0000 http://www.nycresistor.com/?p=346#comment-6102 PD5 is the name of a pin on the AVR microcontroller. Forget about the Arduino numbering system for a moment. This system is totally different. AVR microcontrollers have output pins grouped into things they call "ports". You get PORTA, PORTB, PORTC, PORTD, and so on. Each port has 8 pins in it, named PX0, PX1, PX2 through PX7 (replace X with the letter of the port). In C code, the ports map to 8-bit variables. So you can say PORTC = 0xFF. That drives all eight C pins of the microcontroller high. PORTC= 0 drives all of the C pins low. When you want to set the value for just one pin, say PC3, you do something like this: PORTC |= 0x08. That sets the fourth bit in PORTC to one, driving it high, leaving all the other pins unchanged. To someone looking at the code, the 0x08 in that statement looks like a magic number. So to make the programmers intentions more clear, the library maintainers created constants like PB3 and macros like _BV. _BV(PB3) is equivalent to (1 << 3), which is equal to 0x08. So PORTC = _BV(PB3) has the same effect as saying PORTC = 0x08. The difference is that it is more clear to a human reader.<br><br>For some reason, when using the mega32, some of these constants seem to be missing. It's probably just a bug that will be fixed in a future relase. To work around it, I think you can always replace PAX, PBX, PCX, and PDX with just X. I.e. PA3 with 3, PB7 with 7, PC0 with 0, and so on. PD5 is the name of a pin on the AVR microcontroller. Forget about the Arduino numbering system for a moment. This system is totally different. AVR microcontrollers have output pins grouped into things they call “ports”. You get PORTA, PORTB, PORTC, PORTD, and so on. Each port has 8 pins in it, named PX0, PX1, PX2 through PX7 (replace X with the letter of the port). In C code, the ports map to 8-bit variables. So you can say PORTC = 0xFF. That drives all eight C pins of the microcontroller high. PORTC= 0 drives all of the C pins low. When you want to set the value for just one pin, say PC3, you do something like this: PORTC |= 0×08. That sets the fourth bit in PORTC to one, driving it high, leaving all the other pins unchanged. To someone looking at the code, the 0×08 in that statement looks like a magic number. So to make the programmers intentions more clear, the library maintainers created constants like PB3 and macros like _BV. _BV(PB3) is equivalent to (1 << 3), which is equal to 0×08. So PORTC = _BV(PB3) has the same effect as saying PORTC = 0×08. The difference is that it is more clear to a human reader.

For some reason, when using the mega32, some of these constants seem to be missing. It's probably just a bug that will be fixed in a future relase. To work around it, I think you can always replace PAX, PBX, PCX, and PDX with just X. I.e. PA3 with 3, PB7 with 7, PC0 with 0, and so on.

]]> By: Federico http://www.nycresistor.com/2008/07/26/led-cylinder/comment-page-1/#comment-6101 Federico Sat, 16 Jan 2010 15:29:08 +0000 http://www.nycresistor.com/?p=346#comment-6101 PD5 should be Arduino digital pin 5 PWM (pin 11 on the atmega) and PB2 should be Arduino digital pin 10 PWM (pin 16 on the atmega). Digital 9 is PB1, because the first one is PB0. You have to read the datashet of the atmega to understand these values!<br>Fede PD5 should be Arduino digital pin 5 PWM (pin 11 on the atmega) and PB2 should be Arduino digital pin 10 PWM (pin 16 on the atmega). Digital 9 is PB1, because the first one is PB0. You have to read the datashet of the atmega to understand these values!
Fede

]]> By: TheSharpieOne http://www.nycresistor.com/2008/07/26/led-cylinder/comment-page-1/#comment-6099 TheSharpieOne Thu, 14 Jan 2010 23:09:30 +0000 http://www.nycresistor.com/?p=346#comment-6099 I just got an Arduino with mega328 and was trying to see if I could burn the sketch of the c file that you gave in the zip file. I get an error mentioned above. I changed the PD5 to just 5 and I get another error dealing with a similar thing (this time its the PB2)... not sure why it is doing this. I know nothing about this stuff so I did some research.<br>I found on this page: <a href="http://www.arduino.cc/en/Reference/PortManipulation" rel="nofollow">http://www.arduino.cc/en/Reference/PortManipula...</a> it explains what all the the PD and PB are, PORTD digital pins 0-7, PORTB digital pins 8-13.<br>Anyways... my question is... PD5 means pin 5 (yes?) but PB2 doesn't mean pin 2, but the 2nd pin in the PB range (pin 9?)... Basically.. what do I have to set these to as to not have a constant but the literal value? I just got an Arduino with mega328 and was trying to see if I could burn the sketch of the c file that you gave in the zip file. I get an error mentioned above. I changed the PD5 to just 5 and I get another error dealing with a similar thing (this time its the PB2)… not sure why it is doing this. I know nothing about this stuff so I did some research.
I found on this page: http://www.arduino.cc/en/Reference/PortManipula… it explains what all the the PD and PB are, PORTD digital pins 0-7, PORTB digital pins 8-13.
Anyways… my question is… PD5 means pin 5 (yes?) but PB2 doesn't mean pin 2, but the 2nd pin in the PB range (pin 9?)… Basically.. what do I have to set these to as to not have a constant but the literal value?

]]> By: Federico http://www.nycresistor.com/2008/07/26/led-cylinder/comment-page-1/#comment-6079 Federico Sat, 09 Jan 2010 20:07:34 +0000 http://www.nycresistor.com/?p=346#comment-6079 It should be easy to have it working on the 328, but I have not tryed yet. I am using a 168 that I had here doing nothing. I have to search to see if I still have my digikey buy list, or at least I could tell you the names of the hardware you need. If its not too much different it should be ok. <br><br>BTW, tomorrow I have spare time to try again to do my lower board... I hope to complete it !! Fede It should be easy to have it working on the 328, but I have not tryed yet. I am using a 168 that I had here doing nothing. I have to search to see if I still have my digikey buy list, or at least I could tell you the names of the hardware you need. If its not too much different it should be ok.

BTW, tomorrow I have spare time to try again to do my lower board… I hope to complete it !! Fede

]]>