• Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by JColvin

  1. Hi Jo, The clock frequency of SPI will (most likely) be limited and determined by the on-board ATmega48 that is embedded into the PmodCLS. Looking at the datasheet, it appears that the chip has a default clock frequency of 1MHz. But since the SPI clock will need to driven a little slower to ensure that the Atmel chip is able to perform all of the necessary processing on the incoming information, it seems that the maximum SPI clock speed is 625 kHz, as per the example code that is available for the PmodCLS. Naturally, you can also drive the clock slower if you so desire. The power requirements for the Pmod will be dependent on both the ATmega48 and the LCD screen. The screen appears that it has a typical power draw of 16 mW (based on the typical supply voltage and current). The ATmega48 according to its Electrical Characteristics section will draw up to 3.5 mA of current at 3V, so about 12 mW, for a total power draw between the two of less than 30 mW. Let me know if you have any more questions. Thanks, JColvin
  2. Great, I'm glad it worked out for you.
  3. Hi rbharvs, It might be enough of a difference between boards to have that issue; the page for this demo looks very similar to the one for the Nexys 4 DDR, but maybe it's different enough. Let me know how it goes. Thanks, JColvin
  4. Yes, I think the file was accidentally stored in a location that was inaccessible to the public. I re-uploaded it in a different location though, so you should be able to download it now. Let me know if you have any more questions. Thanks, JColvin
  5. Hi c64, It was recommended to me that you try downloading one of the newer MPIDEs from 2015-01-30 or newer. These apparently have the MRF libraries incorporated into them. Let me know if you have any more questions. Thanks, JColvin
  6. Hi Hamid, I think I found the potential issue that you're running into, which for some reason is not mentioned at all inside the provided manual. The PmodLS1 has the small orange/yellow knob that is the gain factor for that Pmod and controls the sensitivity of the sensors. If it is rotated too far to one side or the other the sensors will be either too sensitive so that they are always on or too insensitive so that they are always off. I would try rotating the knob until those four LEDs on the PmodLS1 turn on again, indicating that they are sensing the infrared being reflected off the white(ish) floor. This should hopefully make your robots turn on since the code only lets the robots turn on when the button is pressed or if some of the light sensors are sensing something. Everything else about your design seems to be done perfectly. Let me know how it goes. Thanks, JColvin
  7. Hi Team21, As zygot mentions, the current draw will be dependent on whatever peripherals you are running with the ZYBO board. As a reference though, in the ZYBO reference manual it recommends that if you are using a 5V "wall wart" power supply that it is able to provide at least 2.5A of current. You could use a more powerful 5V supply that allows for higher current draws if needbe. If you are concerned about running too much current/power through your ZYBO power rails to power all of your peripherals that you have going on without running into overheating issues, I would recommend trying to power any external applications with their own separate power supply. If everything you are doing is already built into the ZYBO board, then I believe a 5V 4A wall wart power supply will be plenty for your needs, but a 5V 2.5 power supply might also work. Again, it depends on how much current your design requires. Let me know if you have any more questions. Thanks, JColvin
  8. The link was gone like you said when I started writing this reply, but it appears to be back up now... hopefully it stays there. But PID control can quickly become a very involved topic, especially if you're not super familiar with some of the math and theory involved behind it, and unfortunately there doesn't seem to be a lot of material out there that explains PID from the ground up. This project goes beyond the scope of what Digilent does as a company, and it's been awhile since I took a process control class, so I will be of limited help. However, I would recommend checking out these three links that get progressively more in depth on PID here, here, and here. There is also an (apparently) semi-famous article on PID for people with PhD's here that does a decent job on explaining the purpose of the three main parts of PID (proportional, integral, and derivative). Thanks, JColvin
  9. Hi, When you say it is not running, what do you mean? Are the motors turning on but the wheels aren't turning? The robot doesn't turn on at all? Did you program the chipKIT MX3 board through MPIDE? If you can post a photo of your setup, that would be great. Thanks, JColvin
  10. Hi Fazeel, I haven't gotten the opportunity to learn much about the PmodBT2 yet, but there is a small demo that has been done that uses the PmodBt2 and the Nexys 3 available here on our wiki. Thanks, JColvin
  11. Hi neryggc, Check out these two other posts from our forum here and here. They're for other boards besides the Nexys 3, but the principle should be the same (as far as I know). Let me know if you have any more questions. Thanks, JColvin
  12. Hi rbharvs, I'm personally not very familiar with FGPAs, but I can at least get you started. We've created a demo that uses the ADC on the Nexys 4 board which you can get here. Let me know if you have any more questions. Thanks, JColvin
  13. Hi c64, That website does describe the correct way to get any downloaded libraries accessible for MPIDE, and I presume that you included all 5 libraries that came in the deIPck zip file. Did you make sure to close out and restart MPIDE so that it can find the newly placed files? Thanks, JColvin
  14. Hi Alex, I apologize for not getting to you sooner. I'm not the most familiar with MPLAB X, but it seems your jumpers are all in the right location. After taking a look at the MX7 reference manual in Section 1.1 for programming, do you have the #pragma config ICESEL = ICS_PGx1 line in your code? That (apparently) is necessary for using the debugging/programming circuit on the chipKIT Pro MX7. Let me know if you have any more questions. Thanks, JColvin
  15. Hi Ferenc, Digilent personally offers the Box Monster as a K-12 project where people are able to build their first robotics/electronics project as a Box Monster that opens and closes its mouth. I'm personally not familiar with other maker options out there, although I have no doubt that there probably are some out there. Thanks, JColvin
  16. Here's a slightly more direct link to the material zygot is referring to: http://brettbeauregard.com/blog/2011/04/improving-the-beginners-pid-introduction/ I'll echo zygot in the fact that the material is a great place to start for PID control.
  17. Hi anil, The short answer is yes, you could potentially use the Analog Discovery as an ECG, although this project goes beyond the scope of what Digilent does as a company. However, there will likely be quite a bit of circuit building since you would need to get some sort of capacitive component (or whatever they use for the electrodes) and set up Waveforms to appropriately decode the incoming information. And if you're non-medical savvy like me, all the ECG would show is your heart rate which you can find just measuring your pulse. What I would recommend as a unofficial, unsanctioned bit of advice is to make sure you eat sometime before getting on the treadmill to make sure that your blood sugar is high enough, lest your muscles use up all of the immediately available energy stores, causing you to feel faint. Thanks, JColvin
  18. Hi bchatree, Please contact Digilent support at support_at_digilentinc_dot_com to find out that sort of information.
  19. JColvin

    Cmod S6

    Hi rmrosnik, Is it all of the Cmod S6's that you have that are encountering this issue or just one of them? Thanks, JColvin
  20. Hi pinnocfa32, The forum is the right place to go to get answers for Digilent products. As for the Vref+ pin, it is on pin 42 as you mentioned. Looking at the silk screen on your microcontroller, this will be labeled as "A" and is next to digital pin 41. These are both on header J5 as described in the A/D Converter Reference section of the reference manual for the uC32 (pg 10). Note that the maximum voltage that can be applied to this pin is 3.3V, as limited by the ADC that is built into the PIC32 processor. You can check out a photo of where this is located on the uC32 from our image galleries https://forum.digilentinc.com/gallery/image/20-uc32-analog-ref/ That pin is located in the same location on the Basic IO Shield as well. Let me know if you have any more questions. Thanks, JColvin
  21. JColvin

    uC32 Analog Ref

    From the album: Forum photos

    Location of Analog Vref+ voltage pin, pin 42
  22. Yep, that's exactly what will happen in this circuit.
  23. I'll put in a request to get it available on the website, so hopefully it will become more widely available soon. Thanks, JColvin