JColvin

Administrators
  • Content count

    1,740
  • Joined

  • Last visited

  • Days Won

    49

JColvin last won the day on March 11

JColvin had the most liked content!

About JColvin

  • Rank
    Forum Moderator
  • Birthday April 22

Profile Information

  • Gender
    Male
  • Location
    Pullman, WA

Recent Profile Visitors

4,510 profile views
  1. Lab

    Hello, Unfortunately, we do not have a set of solutions for the labs in Real Analog - Circuits 1. The reason for this is the creator of the labs (who no longer works at Digilent) felt that there was never going to be a 'correct' answer, primarily because a number of the questions from the lab worksheets ask for the schematic that the student used in their particular project which will inevitably vary from student to student and yet can all still be correct. Additionally, some of the questions ask for lab data from the students which is even more difficult to grade since one cannot fully know how a circuit setup behaved in its environment, so there isn't really a solution key that could be accurately provided for lab data. I'm sorry I could not be of more help. Thanks, JColvin P.S. I also moved this question to Scopes and Instruments as that was a more appropriate section for this particular question than NI's LabVIEW.
  2. Hi @Tony Mauro, The reference manual has been updated as appropriate and is available here: https://reference.digilentinc.com/_media/reference/programmable-logic/cmod-s6/cmods6_rm.pdf (different link that what Michael originally gave). Let us know if you have any questions. Thank you, JColvin
  3. The title has been edited as appropriate. Unfortunately, I'm not familiar enough with the FMC to give any useful feedback though. And quoting @RisinT96, where did you add the line of code that you were originally attempting to add (even though it apparently didn't solve what you were seeing)? Also what does the display show when you run the project? Thanks, JColvin
  4. Hi @mehdiru, I know a number of people that would be interested in such a conversion! I personally think it would be great if we incorporated your work on our GitHub, but unfortunately I don't have control over such things. I did let our content manager for our GitHub know what you have done though and that you would like to share your work, so hopefully that all goes smoothly. Thanks, JColvin
  5. Hello, From my understanding at this point in time, none of the Digilent FPGA boards are compatible with LabVIEW. LabVIEW is able to interact with our microcontroller boards and our instrumentation line and we have VIs to go with them, but not for our FPGAs at this point in time. Let us know if you have any more questions. Thanks, JColvin
  6. Hello, Here's the response I got back from the designer of the cases: The most popular FDM 3D print materials are PLA and ABS. In our office, we have been printing with PLA. That being said, I would recommend to print with PLA since this material is easier to work with and there are plenty of slicer profiles for any user to setup and adjust their printer to get them started. But don’t let this be the limitation, feel free to print away with other materials that have different mechanical properties, and keep us updated. As far as units, the STL files have been exported in millimeters, so be sure to check this in your slicer when your importing it. For more information, refer to the Thingiverse or Repables page for updated instructions. Thanks, JColvin
  7. @BigGuy1000, I'm sorry for not getting back to you sooner; I have asked the appropriate person at Digilent what the answer to your questions are and will reply back with the answer. Thanks, JColvin
  8. This was a response to jpeyron by the original poster, but it got placed as a report on the post rather than a reply. Here is the post of what I presume was intended to be posted: Hi jpeyron, thank you very much for your kind cooperation and for the information regarding my issue . you have mentioned apost in matlab community is posted by me and i have tried over jtag same error persist. I am unable to debug the cause that is the main issue. But anyway once again thank you for your kind support to me. with regards, Morla Lakshmi Sai kumar
  9. Hello @buddin buddin, I don't have Mutlisim Blue (or the Student edition of Multisim from Digilent) on my computer, but my initial thought is that the two sets of Mutisim did not get installed in the same location so they are unaware that the other installation (and the corresponding parts library) exists on your machine. What you would likely want to do is merge the two databases of parts together by following this guide from NI; however, as per the guide, this only works if the two versions of Multisim are the same and I don't know if the Multisim Blue is version 14 or not, so you may need to follow the conversion guide from NI. Alternatively, it looks like this guide from Mouser shows that you can specify which versions of Multisim user the Mouser database. Let me know if you have any questions. Thanks, JColvin
  10. Hello, Would you be able to provide some pictures of your setup? Based on the datasheet for that chip (is this the correct chip?) I'm getting a little confused as to which pins you are referring to when you mention the other pin numbers. I know one thing you will want to make sure you do is to enable the positive power supply for the Analog Discovery 2 inside of WaveForms; you are able to click "on" the positive supply, but you also need to set the master enable to be on as well. For the Static IO, make sure that your outputs going to the two inputs of each AND gate are set to be switches and the single output line to be an LED for easy viewing and manipulation. I don't have the exact chip that you do so I'm not able to replicate this nicely, but I found a different IC with the same number of pins and wired up the Analog Discovery 2 wires to it as if it were that same chip for a visual comparison (not powering the chip of course to make sure I don't damage the IC). The way I have it set up is IO pin 0 (the pink wire) is going to 1A as an input to the AND gate, IO pin 1 (the green wire) is going to 1B as the second input on that AND gate, and IO pin 8 (the pink and white wire) going to 1Y as the output of the AND gate, along with some wires for the power and ground (again, without any actual power flowing through them) pins. I have an image of my setup available on the Forum here. Let me know if you have any questions, Thanks, JColvin
  11. From the album Forum photos

    A setup with the Analog Discovery 2 for a SN74LS08N using static IO.
  12. @zygot, I looked at what I envisioned it would be (on the Scopes and Instruments section with the Analog Discovery troubleshooting as what I had in mind) and it became apparent that I misunderstood what the comment pinning would look like for myself, since the thread I was going to reference has the entire thread pinned and not the comment. :/ I suppose I was imagining having a particular comment always be visible on the very first page of the thread, but the only one that is guaranteed to be there (since I tend to sort comments by date rather than by rating so an upvoted comment doesn't confuse the flow for me) is the original comment/question. So, I guess what I would suggest would be to edit the original post (I believe you have access to do that, or at least my 3rd party account with no special privileges seems to be able to do that; please let me know if this is not the case) to add in new links/files to updated code. If you have updated the code and want to be able to redirect readers who are only looking at the most recent comment in the thread, you can get a direct url link to the comment/question/whatever-vernacular-is-appropriate-in-this-situation by clicking on the bubbled branch thing that looks like a "<" in the upper right hand corner in the comment of interest, which you can then use as a redirect to appropriately update viewers who happen to only be reading the latest comment in the thread. With this situation/setup since there is no comment pinning as I imagined it, you would not need any moderator help to get anything pinned; you should be able to update your own post as you see fit. I apologize for the confusion that I caused earlier. Thanks, JColvin
  13. Hello @zygot, @D@n, and @jpeyron, Turns out I was able to respond slightly sooner than next week. The best (well, easiest) way that I can think to approach this would be to pin a comment in a thread so that it stays as the very first topic. The original creator of that thread would be able to edit their own comment (ideally the one that is the pinned) to add new versions of a code while keeping the old ones available. The slightly tricky bit that I'll have to work out (or work with the other Digilent people who do the back-end maintenance of the Forum) is the pinning portion. Currently, only moderators are able to pin posts on a Forum thread, since that can potentially get a little crazy if anybody was allowed to pin any comment. Ideally, I would like to set it so that only comments in the Project Vault threads could be pinned, but I'm not seeing that level of precision available to me. What I can also do (and have now done since I don't know why it was never done before) is add a "spoiler" button so that way long bits of code can be hidden at the users discretion and it makes for a slightly easier way of presenting multiple revisions of a project where you could have a "old version" spoiler and a "newest version" spoiler so that there is minimal confusion. Regardless, at this point in time since I do not have any formal solution, if anybody has a comment that they would like pinned in a thread so that it stays upfront and center for any reason, feel free to send one of the moderators a PM (or "@" them) and we'll make sure it get's taken care of. @zygot, would you like that done for your initial post on the differential Pmod challenge post? Thanks, JColvin
  14. The wiki has been updated.
  15. Hello @Andrei Kh., Thank you for pointing that mistake out; I am personally working on getting this correct, although I am admittedly baffled as to why this was never brought up by anybody before. It seems unlikely that everybody would have only looked at the PDF. Regardless, it will be fixed today. Thank you, JColvin