Search the Community

Showing results for tags 'chipkit'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • News
    • New Users Introduction
    • Announcements
  • Digilent Technical Forums
    • FPGA
    • Test and Measurement
    • Measurement Computing (MCC)
    • Add-on Boards
    • Digilent Microcontroller Boards
    • Non-Digilent Microcontrollers
    • LabVIEW
    • FRC
    • Other
  • General Discussion
    • Project Vault
    • Learn
    • Suggestions & Feedback
    • Buy, Sell, Trade
    • Sales Questions
    • Off Topic
    • Educators
    • Technical Based Off-Topic Discussions
    • Archived

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 5 results

  1. I am having a ChipKit pro mx7 board (PIC32MX795F512L), when i try to connect with mplab x ide with the on-board debugger (license debugger) i get the error : "Failed to get device ID". I also try the mplab ipe, it able to detect the board but each time i get the same error message. Note: I tried with jumper JP11 removed and J3 connected to Debug and Usb connected to J15 and with same setting but JP11 plugged . (Still the issue remains). All the connection are checked and tightly connected . And last thing do i need to attach a external hardware(debugger) to program it and also programming tutorial?
  2. I'm pretty confident I am following instructions to the letter but it's possible I am doing something wrong. But any assistance here would be great. MPLab X (5.20), XC32 (2.10), Arduino 1.8.10, Chipkit Library 2.10, Importer 1.0.6 (All the latest), Target Board is Pro MX 7. The latest importer states these versions should be acceptable because of the whole "or later" caveat. I've added photos showing I'm my directories (pretty sure they're all pointing to the correct location I'm trying to upload the Chipkit Wire - Master Reader .ino file. I select the Pro MX 7 in Arduino IDE, open the sketch, and save it to a different folder. Is that possibly the wrong step? Just spit balling. Is there some grand secret to making this work that I don't know and the internet refuses to tell us? Here's what that last photo says: java.lang.RuntimeException: java.lang.NullPointerException at com.microchip.mplab.nbide.embedded.chipkit.importer.ArduinoBuilderRunner.preprocess( at com.microchip.mplab.nbide.embedded.chipkit.importer.ArduinoBuilderRunner.preprocess( at com.microchip.mplab.nbide.embedded.chipkit.importer.ChipKitProjectImporter.preprocessSourceProject( at com.microchip.mplab.nbide.embedded.chipkit.importer.ChipKitProjectImporter.execute( at com.microchip.mplab.nbide.embedded.chipkit.wizard.ImportWorker.importChipKitProjectFiles( at com.microchip.mplab.nbide.embedded.chipkit.wizard.ImportWorker.createProjectFromChipKit( at com.microchip.mplab.nbide.embedded.chipkit.wizard.ImportWorker.invokeImporterTasks( at com.microchip.mplab.nbide.embedded.chipkit.wizard.ImportWorker.doInBackground( at com.microchip.mplab.nbide.embedded.chipkit.wizard.ImportWorker.doInBackground( at javax.swing.SwingWorker$ at at at java.util.concurrent.ThreadPoolExecutor.runWorker( at java.util.concurrent.ThreadPoolExecutor$ at Caused by: java.lang.NullPointerException at com.microchip.mplab.nbide.embedded.chipkit.importer.ArduinoBuilderRunner.lambda$findMainLibraryPaths$0( at java.lang.Iterable.forEach( at java.util.Collections$UnmodifiableCollection.forEach( at com.microchip.mplab.nbide.embedded.chipkit.importer.ArduinoBuilderRunner.findMainLibraryPaths( at com.microchip.mplab.nbide.embedded.chipkit.importer.ArduinoBuilderRunner.preprocess( ... 14 more
  3. Hey Guys, Tommy and I are starting a chipKit project that uses piezo sensors to sense a hit on a drum and then light the drum up with LEDs. This creates a pretty cool effect to watch in the dark. Our endgame with this project is to approach a drum line and hook them all up to some WS2812s to create a cool music/light show. Below is our proof of concept video using a single snare drum. We think we can use this technique for most percussion instruments. Cymbals seem to be the only thing we cant use this on so far. Our next step is to dress up our drum a little more to make a little more appealing video to present to a drum line. Let us know if you guys like our project or want to know anything about it. We will also attach the MPIDE sketch. We will be posting to this stream as we progress with our project. /************************************************************************/ /* Drum Lights Proof of Concept */ /* */ /* Authors: Thomas Kappenman and Samuel Lowe */ /* */ /* This is a simple sketch that lights up a snare drum whenever */ /* it is struck. */ /* */ /* tested supported boards: */ /* - Digilent UNO32 */ /* */ /* This library is protected under the GNU GPL v3.0 license */ /* */ /************************************************************************/ #include <PICxel.h> //our strip had 43 lights #define number_of_LEDs 43 #define LED_pin 5 #define millisecond_delay 5 //Adjust these values to obtain better results for each drum #define sense 25 //Sensitivity of each drum #define debounce 300 //Debounce to get rid of idle values. PICxel strip(number_of_LEDs, LED_pin, GRB); struct drum{ int r; int b; int g; int zero; }; int red; int green; int blue; int i; int triggerval; int lastval; int in1; int prevTime = 0; drum drum1; void setup(){ strip.begin(); strip.setBrightness(100); Serial.begin(9600); drum1 = {0, 255, 0}; //snare } void loop(){ int a; if(millis()-prevTime > millisecond_delay){ a=analogRead(A0); Serial.println(a); if (lastval-a>100)in1=1; lastval=a; colorLogic(); in1=0; if(red>= 15 ) red -= 15; else red = 0; if(green>15) green-=15; else green = 0; if(blue>15) blue-=15; else blue = 0; for(int i= 0; i<number_of_LEDs; i++){ strip.GRBsetLEDColor(i, green, red, blue); } strip.refreshLEDs(); prevTime = millis(); } } void colorLogic(){ if(in1){ green += drum1.g; red += drum1.r; blue += drum1.b; } if(red >255) red = 255; if(green >255) green = 255; if(blue >255) blue = 255; }
  4. From the album: Marshall's pics

    Compile errors indicate the wrong hardware is selected. double-check the correct board with this drop-down menu.