JColvin

Administrators
  • Content Count

    3933
  • Joined

  • Last visited

  • Days Won

    150

Everything posted by JColvin

  1. Hi radres, Unfortunately Digilent will not be able to help with this: the Nexys 4 and the Nexys 4 DDR are designed differently so you will not be able to as easily port code from one board to the other. MathWorks creates and maintains those files for Simulink, so they would need to add support for the Nexys 4 DDR. Thanks, JColvin
  2. Hi snohomish77, I'm sorry for taking awhile to get back to you; I have asked some of our applications engineers to take a look into this since the board files should all be up to date, but evidently that's not what you are experiencing. Thanks, JColvin
  3. Hi lafe, The PmodUSBUART will work in both directions, that is you can either have the ZedBoard receive data from the source on the USB side of the Pmod or have the ZedBoard send data over the UART side to whatever is on the other side. All of the data type conversions and headers and whatnot are handled internally by the FTDI chip that is present on the board. I don't know how it does it (the FTDI manufacturer keeps that information to itself), but the chip has " UART interface support for 7 or 8 data bits, 1 or 2 stop bits and odd / even / mark / space / no parity", as per the first page of it's datasheet. As far as I am aware, there is nothing fancy that you need to do or send to the Pmod to make it a host or a slave. Thanks, JColvin
  4. Hi tasnim, I have asked some of our applications engineers to take a look at this in case they are familiar with what you are trying to do, but in the meantime I will ask some clarification questions. Are you attempting to provide an audio signal to the Anvyl and then compare that audio signal to a known audio signal and then measure the difference? Or am I not understanding what you are wanting to do? In the meantime I would check out the projects for the Anvyl on it's Resource Center since the helloworld.c file would be difficult to expand upon. Thanks, JColvin
  5. Hi vwone, I'm sorry for not getting back to you earlier. Since you are using LabVIEW Home Edition and (presumably) LabVIEW MakerHub LINX to communicate to the WF32 I looked around on the MakerHub Forums to see what I could find. A common theme I ended up seeing was that LabVIEW MakerHub LINX was usually competing with a computer's USB connection to the WF32 so that could be a potential problem. Otherwise my thought was that perhaps voltage regulator on the board was overheating from the external power supply, but after looking through the datasheet I do not think this is the case; you would see the board turning on and off fairly quickly and not need to keep the board powered off. My last thought is that you are not getting a stable WiFi connection so the connection is patchy, but that's hard to debug (at least for me). Either way, I would recommend posting further questions on the LabVIEW MakerHub Forums under the LINX section. Let me know if you have any more questions. Thanks, JColvin
  6. Hi DavidMC, So I tried compiling the program for the WiFIRE with what I labeled as the the August 2015 edition of MPIDE on my computer (I presume it's the same version that it looks like you're using currently) and it was able to compile successfully once I told it to look in the appropriate location for the library files (by going to File, Preferences, and then choosing the right location) since it was looking in the wrong location for that version of MPIDE. I also found the deWebServer in the HTTPServer folder rather than the DEIPck library folder; I presume you did as well. Did you happen to get any other errors listed besides just the one we can see in your screen shot? Thanks, JColvin
  7. Hi btb4198, As per page 179 of the PIC32 Family Datasheet by Microchip, the absolute voltage range that the Analog to Digital Converter can accept is AVSS - 0.3V to AVDD + 0.3V, which correlates to -0.3V to 3.6V. With the setup you described, your 165 ohm resistor will only drop the incoming voltage (presuming we are providing 20 mA) by 3.3V, so you would be applying 21.7 V to the input of the Analog to Digital Converter. As Microchip notes on page 151 of the same document linked above: "Stresses above those listed under “Absolute Maximum Ratings” may cause permanent damage to the device. This is a stress rating only and functional operation of the device at those or any other conditions above those indicated in the operation listings of this specification is not implied. Exposure to maximum rating conditions for extended periods may affect device reliability." Likely, the pin you were using on the Analog to Digital Converter (or that whole section of the PIC32 chip) has been irreparably damaged. So you do not need to have the uC32 power the device sending the signal, but they do need to share the same ground (as you have done) and the device needs to send a signal within the 0V to 3.3V range. Let me know if you have any more questions. Thanks, JColvin
  8. Hi algae, Offhand without any experience with this (and looking at the reference manual) I don't believe they can handle the dual SPI modes; I'll ask some of our applications engineers for a more concrete answer though; they'll get back to you here on the forum. Thanks, JColvin
  9. Hi Steve, I have asked some of our applications engineers about this; they will get back to you here on the forum. Thanks, JColvin
  10. Hi ColoradoAnalog, Thanks for posting what you found! I'll make sure the demo project page gets updated appropriately. Thanks, JColvin
  11. Hi Thays, I have asked some of our applications engineers about this; they will get back to you here on the forum. Thanks, JColvin
  12. Hi Shruthi, I'm not the most experienced with Verilog so I can't guarantee this will be the most complete answer (or have correct syntax) but if you are wanting to store results to separate input parameters, you would need to do so in the for loop. Right now, it looks like you are just re-assigning x the MEASURED_AUX6 value four different times. It would probably be easier to store values in an array so you had x[ i ] = MEASURED_AUX6, so you have four stored values in the array called x. However, I don't know how to set up the rest pieces so that the array is initialized appropriately and to make sure that each x value gets a different part of the MEASURED_AUX6 parameter rather than having all four x's get the exact same value simultaneously. For that, I'll ask some of our applications engineers about (and to have them correct what I've said if necessary). Thanks, JColvin
  13. JColvin

    netFPGA 1G original flash

    Hi rfrm, Do you perhaps mean Virtex-II? NetFPGAs don't have a spartan chip on them as far as I am aware. If anybody would have the the files it would be the NetFPGA community. The two places I would look for the files would be both here and here. Thanks, JColvin
  14. Hi Randall, I personally don't know the answer to this, but I wanted to let you know that I've asked some of our applications engineers about this; they'll get back to you here on the forum. Thanks, JColvin
  15. Hi ledlighter, I looked up the internal part and found that it is 20 counts per full revolution for the shaft on the PmodENC. The part for the shaft can be found here. Thanks, JColvin
  16. Hi DavidMC, I personally don't have any experience with UDP, but doing a search through the files it seems like that error indicates that the IP is not set up, although again, I don't know what that indicates. I'll ask some of our applications engineers about this and they'll get back to you here on the forum. Thanks, JColvin
  17. Hi Hans, I have moved this question to a section of the forum where the engineer most qualified to answer your question can see it. From my understanding (from this thread) you are not able to connect the Analog Discovery 2 to both the Waveforms 2015 software and LabVIEW, but it sounds like you are able to do that with the older Waveforms runtime? Am I interpreting that correctly? Thanks, JColvin
  18. JColvin

    Genesys 2 FT2232H

    Hi Jensen, I have asked some of our applications engineers about this; they will get back to you here on the forum. Thanks, JColvin
  19. Hi Brandon, To my surprise, at this point in time there is not a way to order with the bracket with the lip. I'll ask to see if this angled bracket can be sold individually in the future. In the meantime, I would recommend either bending the metal yourself from the part you found (it's fairly soft for metal, so you can bend it with a good pair of pliers) or if you have access to a 3D printer, downloading and printing out the angled part here. Sorry that I can't be of more help. Thanks, JColvin
  20. Hi mospeada, After looking through the datasheet of the Allegro A4973 that is on the board, my guess is that the chip is getting overheated and entering thermal shutdown since it looks like this particular chip can only dissipate a little under 2 Watts at 25 degrees C. What voltage are you running the motors at since that will give a good indication of the power you're attempting to draw through the chip. Thanks, JColvin
  21. You can upload some more photos/screenshots to the Gallery if you need to.
  22. To directly answer your question, it doesn't matter where you save your SIM_MONITOR_FILE because within the document that Sam pointed out in the other thread, you are able to tell the program exactly where your file is located on your computer. Thanks, JColvin
  23. Hi Vardhan, I would recommend checking out the PmodTC1. This module comes with a K-type thermocouple and you can get data from the module by communicating with it through SPI. Thanks, JColvin
  24. JColvin

    basys 3 FPGA

    Hi Marco, What sort of errors are you getting? Is it complaining about temp_k? Also, you will need to set up your XDC file for the Basys 3. If you're not sure on how PWM works, I would definitely recommend reading through this forum thread here where one of our forum members walks through how PWM works. Let us know if you have any more questions. Thanks, JColvin
  25. Hi Steve, I have asked some of our applications engineers about this; they will get to you back on the forum. Thanks, JColvin