Search the Community

Showing results for tags 'LED'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • News
    • New Users Introduction
    • Announcements
  • Digilent Technical Forums
    • FPGA
    • Digilent Microcontroller Boards
    • Non-Digilent Microcontrollers
    • Add-on Boards
    • Scopes & Instruments
    • LabVIEW
    • Other
  • General Discussion
    • Project Vault
    • Learn
    • Suggestions & Feedback
    • Buy, Sell, Trade
    • Sales Questions
    • Off Topic
    • Educators
    • Technical Based Off-Topic Discussions

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 15 results

  1. I'm designing an application using the Audio CODEC of the Zybo Z7. I'm configuring the CODEC by I2C properly and could see data coming from the I2S. Then I realized that each time I programmed the FPGA, the Led 5 of the board was turning ON... even this LED is not at all part of my design!! Never mentioned in my constraints and never mentioned in the verilog wrapper. Then proceeding by elimination when analyzing the constraints, I realized that this LED was turned ON as soon as the I2S clock went enabled... with below constraints: NO LED TURNED ON ##I2S Audio Codec ##set_property -dict { PACKAGE_PIN R19 IOSTANDARD LVCMOS33 } [get_ports BCLK_0]; #IO_L12N_T1_MRCC_35 Sch=AC_BCLK ##set_property -dict { PACKAGE_PIN R17 IOSTANDARD LVCMOS33 } [get_ports FCLK_CLK1_0]; #IO_25_34 Sch=AC_MCLK ##set_property -dict { PACKAGE_PIN R16 IOSTANDARD LVCMOS33 } [get_ports RECDAT_0]; #IO_L12P_T1_MRCC_35 Sch=AC_RECDAT set_property -dict { PACKAGE_PIN Y18 IOSTANDARD LVCMOS33 } [get_ports RECLRCLK_0]; #IO_L8N_T1_AD10N_35 Sch=AC_RECLRC ##Audio Codec/external EEPROM IIC bus set_property -dict { PACKAGE_PIN N18 IOSTANDARD LVCMOS33 } [get_ports IIC_0_0_scl_io]; #IO_L13P_T2_MRCC_34 Sch=AC_SCL set_property -dict { PACKAGE_PIN N17 IOSTANDARD LVCMOS33 } [get_ports IIC_0_0_sda_io]; #IO_L23P_T3_34 Sch=AC_SDA But with below constraints enabling the CLOCK... I get the LED turning on in Red, Green or Blue depending... ##I2S Audio Codec set_property -dict { PACKAGE_PIN R19 IOSTANDARD LVCMOS33 } [get_ports BCLK_0]; #IO_L12N_T1_MRCC_35 Sch=AC_BCLK set_property -dict { PACKAGE_PIN R17 IOSTANDARD LVCMOS33 } [get_ports FCLK_CLK1_0]; #IO_25_34 Sch=AC_MCLK set_property -dict { PACKAGE_PIN R16 IOSTANDARD LVCMOS33 } [get_ports RECDAT_0]; #IO_L12P_T1_MRCC_35 Sch=AC_RECDAT set_property -dict { PACKAGE_PIN Y18 IOSTANDARD LVCMOS33 } [get_ports RECLRCLK_0]; #IO_L8N_T1_AD10N_35 Sch=AC_RECLRC ##Audio Codec/external EEPROM IIC bus set_property -dict { PACKAGE_PIN N18 IOSTANDARD LVCMOS33 } [get_ports IIC_0_0_scl_io]; #IO_L13P_T2_MRCC_34 Sch=AC_SCL set_property -dict { PACKAGE_PIN N17 IOSTANDARD LVCMOS33 } [get_ports IIC_0_0_sda_io]; #IO_L23P_T3_34 Sch=AC_SDA I'm respecting the pin allocation proposed in the Zybo Z7 manual... therefore I do not understand what is going on... Let me know if someone already faced this situation or have any idea of the phenomena. I"m using Zybo_Audio_Ctrl IP for the I2S below a copy of my design...
  2. Most of the individual pixel strips are the dc5v low voltage strip,but dc5v will not be so convenient installation in some cases, for most led device are just dc12v,so the new dc12v GS8208 individual pixel led strip can easily use in these equipment devices or led projects. Also for the same wattage strips, the current of dc12v strip will be much lower than the dc5v led strips,as the sk6812,ws2813,apa102,so it is not so higher temperature and more safety. The GS8208 is a type of featured IC for our dc12v individual pixel led products,it is not only dc12v but also feature-rich with dual-signal break-point function (one bad led,the signal still transfer),built-in program effects,it can work without controller when power on it, but also can run as your own DIY programs with your controller system. Videos about the DC12V GS8208 LED Strips https://youtu.be/WBZKLZtxlJM
  3. Alex

    Documentation For Ws2812 Led Strip

    I have a question from the customer. Can anyone help on this? I purchased the WS2812 LED Strip but can not find the documentation covering the protocol to control it onyour site. Can you please provide a link to a .pdf or a website?
  4. Ben

    Arty: Display UART data on LEDs

    Hi all I have a very simply UART TX/RX pair I have built in Verilog, and have been struggling to get them to function on the Arty Board. I can connect the two together to form a simple "echo" function, where any received RX data is immediately sent out on the TX module, but beyond that I can't correctly see the values I send to the Arty. I tried simply piping the received byte to the LEDs on the Arty board, but the values lit up do not correspond at all to the ones I expect. Sending the character string "AaA" does not make the ascii encodings for "A" and "a" appear on the LEDs. However, I do get the right characters echoed back to my PuTTY terminal. My code for the project can be found here: https://github.com/ben-marshall/uart You'll need: rtl/uart_rx.v , rtl/uart_tx.v, rtl/impl_top.v and constraints/default.xdc to re-create the project. I'm using Vivado 2016.4 on Ubuntu 16.04. Thanks, Ben
  5. megaxoplasma

    Default bit file

    Hello, I am new here, I was just wondering about two questions How would I use VHDL code as well as ucf to change the LED light intensity?? I know the up voltage is 3.3V and I cant seem to give it any other voltage aside from 3.3 using LVCMOS33 on the nexys 4 DDR. However I noticed that the built in default bit file in the board was able to make the light seem deemer, so I am also wondering,where do I download that default bit file so I can look at the code??? or how would I extract it back out from the board? Thank You
  6. I am at my wits end and hope someone more literate than I will help. In short I had a MPLABX cx32 v1.0 project to target an uno32 board to operate a radioshack tricolor LED p/n 2760249 and it worked PERFECTLY using core timer for precision timing. However, even after manually installed Microchip's peripheral library on top of xc32 x1.34 and genning the SystemConfig function to complile. the core timer counts are producing erratic results...no matter what I put in blocking whiles for CP0 counts I cant make the pattern....waiting X counts while high is different than while low. This LED strip works on 24 bits... a LOGIC one needs to be ~1.5us HIGH followed by .78us LOW a LOGIC zero needs to be .78us HIGH followed by 1.5us LOW in the code below i an sending 0xFF00FF....so 8 ones followed by 8 zeros followed by 8 ones with timing above. To do that I was using core timer counts...for now I just want something that simple w/o interrupts. Used to be a core timer counts was 25ns like clockwork. That was several years ago and now that I have installed the new versions of the toolchain something is a amiss. I am including my complete code and a screen shot of a scope plot or 2 showing weird timing. #include <xc.h> #include <cp0defs.h> #include <sys/attribs.h> #include <p32xxxx.h> #include <plib.h> #pragma config FPLLIDIV = DIV_2 // PLL Input Divider (2x Divider) #pragma config FPLLMUL = MUL_20 // PLL Multiplier (20x Multiplier) #pragma config FPLLODIV = DIV_1 // System PLL Output Clock Divider (PLL Divide by 1) #pragma config FNOSC = PRIPLL // Oscillator Selection Bits (Primary Osc w/PLL (XT+,HS+,EC+PLL)) #pragma config FSOSCEN = OFF // Secondary Oscillator Enable (Enabled) #pragma config IESO = ON // Internal/External Switch Over (Enabled) #pragma config POSCMOD = XT // Primary Oscillator Configuration (XT osc mode) #pragma config FWDTEN = OFF // Watchdog Timer Enable (WDT Enabled) #define SYS_CLOCK (80000000L) #define SYS_FREQ (80000000L) UINT64 start=0; UINT64 stop=0; const unsigned long pattern_test_rainbow[10][10]={ {0xff0000,0xff7f00,0xffff00,0x00ff00,0x0000ff,0x6f00ff,0x8f00ff,0x000000,0x000000,0x000000}, {0x000000,0xff0000,0xff7f00,0xffff00,0x00ff00,0x0000ff,0x6f00ff,0x8f00ff,0x000000,0x000000}, {0x000000,0x000000,0xff0000,0xff7f00,0xffff00,0x00ff00,0x0000ff,0x6f00ff,0x8f00ff,0x000000}, {0x000000,0x000000,0x000000,0xff0000,0xff7f00,0xffff00,0x00ff00,0x0000ff,0x6f00ff,0x8f00ff}, {0x8f00ff,0x000000,0x000000,0x000000,0xff0000,0xff7f00,0xffff00,0x00ff00,0x0000ff,0x6f00ff}, {0x6f00ff,0x8f00ff,0x000000,0x000000,0x000000,0xff0000,0xff7f00,0xffff00,0x00ff00,0x0000ff}, {0x0000ff,0x6f00ff,0x8f00ff,0x000000,0x000000,0x000000,0xff0000,0xff7f00,0xffff00,0x00ff00}, {0x00ff00,0x0000ff,0x6f00ff,0x8f00ff,0x000000,0x000000,0x000000,0xff0000,0xff7f00,0xffff00}, {0xffff00,0x00ff00,0x0000ff,0x6f00ff,0x8f00ff,0x000000,0x000000,0x000000,0xff0000,0xff7f00}, {0xff7f00,0xffff00,0x00ff00,0x0000ff,0x6f00ff,0x8f00ff,0x000000,0x000000,0x000000,0xff0000}, }; int main(int argc, char** argv) { SYSTEMConfigPerformance(80000000); //SYSTEMConfig(SYS_FREQ, SYS_CFG_WAIT_STATES | SYS_CFG_PCACHE); TRISF = 0x0000; PORTF = 0x0000; send_strip(0xff00ff); while(1) { } return (EXIT_SUCCESS); } void send_strip(unsigned int data) { int i; unsigned long long j=0x800000; for (i=0;i<24;i++) { if (data & j) { PORTFbits.RF1=1; start=_CP0_GET_COUNT() ; while(_CP0_GET_COUNT()<=(start+36)); //40MHz=> period is 25ns...neded this to be 1.55us PORTFbits.RF1=0; start=_CP0_GET_COUNT() ; while(_CP0_GET_COUNT()<=(start)); } else { PORTFbits.RF1=1; start=_CP0_GET_COUNT() ; while(_CP0_GET_COUNT()<=(start)); PORTFbits.RF1=0; start=_CP0_GET_COUNT() ; while(_CP0_GET_COUNT()<=(start+36)); } j>>=1; } } void set_white() { // INTDisableInterrupts(); int i; for (i=0;i<10;i++) { send_strip(0x00ffff); } // INTEnableInterrupts(); PORTFbits.RF1=0; start=_CP0_GET_COUNT() ; while(_CP0_GET_COUNT()<=(start+1000)); } void send_1M_pattern(const unsigned long data[][10], int pattern_no, int frame_rate) { int i=0; int j=0; UINT32 temp_data; INTDisableInterrupts(); for (i=0;i<pattern_no;i++) { for (j=0;j<10;j++) { temp_data=&data[j]; send_strip(temp_data); } INTEnableInterrupts(); start=_CP0_GET_COUNT() ; while(_CP0_GET_COUNT()<=(start+frame_rate*20000000)); } } ScopePlots.docx
  7. candylion

    LED vs UV lamp

    Hi, there are two types of lamps in the nail salon for drying the nails: LED lamp and UV lamp. I wonder which one is better?
  8. Hello! Many of you have seen many larger LED cubes, but connecting the 512 LED's present in an 8x8x8 LED cube can be rather daunting, but from this Instructable you can take a step back and check out how we would put together (and operate) a 3x3x3 LED cube.
  9. I am working with the MAX32 board and want to control LD5. The schematic shows that the control for this LED is connected to RC1. However, the Reference guide (and the Excel pinout table show this as not assigned to a chipKIT pin number. If I were working with XC32 and the MPLAB X IDE, I would simply write TRISCCLR = 0x01; and then use LATCSET and LATCCLR to turn the LED on or off. What are my options if I want to stay in the Arduino IDE format? .
  10. candylion

    led bulb

    Hi, i want to buy some led bulbs for home decoration. Is philips 60 watt A19 LED light bulb good? Alternatively are there any other good brands? Thanks.
  11. candylion

    choose proper led bulbs

    Hi, I'm trying to buy some brands for the bulbs for my chandelier in the living room, after searching our whether filament bulb is good for chandelier: https://www.earthled.com/blogs/light-2-0-the-ear...r-vintage-led-bulbs#.VMNMaYGwrqB i'm thinking to buy the following bulbs: 1. https://www.earthled.com/collections/led-lightin...qual-e12-base?variant=1011456188 and 2. http://www.fortilighting.com/index.php/products...t-led-4w-watt-b11-e12-bulb.html. Could anyone suggest which one is better? Many thanks!
  12. Okay, I need someone to please point out the key piece of information I'm missing. I have years of microcontroller programming experience but am new to Digilient products. I have a chipKIT Max32 with "REV D" printed on the back in silkscreen. I look at the Rev D schematic on the Digilent website, and on sheet 5 of 5 there is a LED with reference designator "LD5" that is controlled by net "T2CK/RC1" (see snapshot below/attached). On schematic sheet 3 of 5 I see where the net "T2CK/RC1" is connected to reference designator "IC2PC" "Port C" on pin 6 (see snapshot below/attached). I program the most basic blink-LED example in MPIDE and... LD5 does not blink. I Google the situation and find someone else having the same problem but is given the only partially helpful tip of "... LD5 isn't on pin 6, LD5 is on pin 86." (see link). I change my MPIDE sketch to "int ledPin = 86;" and sure enough it works! Looking through the schematic, pin 86 is a VDD pin on sheet 2 (see snapshot below/attached). What is going on? Can someone please point out my error in thinking?
  13. Hi, I have a question about LEDs on the basys3 board. I'm using Verilog, and in my code I have a top level module which has other sub-modules within it. Like this: module top (); sub_module m1 (some_inputs, some_outputs); endmoduleIf I want to have the sub-module with an LED output, how would I go about doing it? I already tried having "output [15:0] led" in the definition of the top level module and also having it as an output of the sub level module, but that did not work. I also tried to simply declare led as a register within the sub_module, but that also didn't work.
  14. Hi, When I try to use the delay function (__delay_ms() in a simple code for turning LEDs on and off, the project does not build. I have defined _XTAL_FREQ as indicated in MPLABX help. When I include 'delays.h' as indicated in the help, I get a parse error. When I try to build without including delays.h I get the error below. Are the delay functions not available foe PIC32MZ devices? I am using Flow Cloud Skeleton App, and the device is PIC32MZ2048ECG100 ChipKit WiFire. Below is the error and the code. ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Error: c:/microchip/harmony/current/apps/flow/flow_skeletonapp/src/main.c:35: undefined reference to `__delay_us' ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Code: #include <stddef.h> // Defines NULL #include <stdbool.h> // Defines true #include <stdlib.h> // Defines EXIT_FAILURE #include <system/debug/sys_debug.h> #include <tcpip/src/system/system_debug.h> #include <app_core.h> #include "app.h" #include "command_handlers.h" #define _XTAL_FREQ=200000000; //App information given to libappbase. static APP_info info = { .appName = "Flow PIC32MZ WiFire Skeleton App", .appVersion = "1.0.0", .appVersionDate = "23 Mar 2015", .AppTask = SYS_AppTask, .CommandSet = CommandSet, .CommandShow = CommandShow, .AppCLI_ResetHandler = CommandHandlers_ResetHandler }; //char message [200]; int main ( void ) { //libappbase inits and then runs our task. TRISE=0; //set all pins as outputs ANSELE=0; //set all 8 pins as digital while(1){ PORTE=0x00ff; //set all 8 pins to HIGH __delay_ms(100); PORTE=0x0000; //set all pins to LOW __delay_ms(100); } return APPCORE_init(&info); }
  15. Squirrel

    New Zybo, Microsd/led Failures

    I’m not entirely sure where to put this RMA, but I think the ZYBO board I just received may have a faulty LED (LD3) and a faulty microSD card from the accessories kit. One thing at a time… first, the LED. I have been having trouble getting u-boot (and subsequently the Digilent Linux distro) to work on the board. In order to make sure that at least the PL portion was being programmed correctly, I made a basic project in Vivado 2014.1 for the xc7z010clg400-1 SoC target. The LEDs are hooked to a constant IP block [3:0] with a constant value “1111”: But the ZYBO response does not have all the LEDs lit as expected: I'll happily post the synthesis report, although there doesn’t appear to be a ‘smoking gun’ in there. Back to the SD card; using the same format (FAT32) and files on three different cards (SanDisk, ADATA, and the unbranded one from the accessory kit), only the first two worked.... and they have lower speed grades than the broken one (4 and 6 vs. 10, respectively). Not sure what other evidence I can provide...