JColvin

Administrators
  • Content Count

    4172
  • Joined

  • Last visited

  • Days Won

    165

Everything posted by JColvin

  1. Hello, We don't have a lot of information available on the Arty with the Spartan-7 chip available as of yet; you can learn a little bit more about it in this thread on our Forum. I'm pretty excited to see what it has as well since I don't really know anything more than what is mentioned in that thread. Thanks, JColvin
  2. JColvin

    Zybo board

    Hello, Unfortunately, Digilent does not maintain or create the Vivado software by Xilinx. After taking a look at this Xilinx Forum thread which it looked you had already posted on, it appears that there isn't anything that Xilinx can do to change this due to U.S. export regulations. You should be able to issue an RMA request with whomever you purchased the Zybo from (either Digilent or a distributor). From my understanding, to start an RMA with Digilent, you will need to email the Digilent sales department at sales @ digilentinc.com and provide them your name, your order number, when you purchased it, and a description of why you are returning it (in this case, because the Xilinx software is not available in your country). I'm sorry I could not be of more help. Thanks, JColvin
  3. Hi @[email protected], Thanks for the feedback! Sadly, it doesn't look like the software will let me something like that (despite how simple it sounds in principle), but I'll keep looking. I do agree that some sort of post count would need to be reached before such a rating were implemented though to help avoid any one-hit-wonders. That might not be a fair rating for any senior engineers at Digilent that happen to post an answer on the Forum when it's not their job to do so and never get above 10 posts, but at the same time I suppose at the same time they might be bothered by that anyway. Who knows. I'll look to see what sort of plugins exist for this sort of rating, either by likes or something else, or I may just do something like changing the tag labels given to people based on the number of posts (otherwise by that regard I'd be labeled as the most competent person on the Forum which is a long ways from the truth and just a byproduct of having joined the Forum back in September of 2014). Thanks, JColvin
  4. Hi @[email protected], I would probably recommend listing their adviser if they are a grad student. In other situations (say you are a lab instructor/tech or a purchasing department), I believe you would be able to use the primary instructor/professor that requires the materials. But as a disclaimer, the Digilent Sales team will have the final word on what counts; this recommendation was just my educated guess as to what a good choice would be. Thanks, JColvin
  5. I think I got everybody now, including elodg (which I imagine prompted your comment on the staff labels to begin with). I also tried to change some of the former employees (mainly interns who no longer are here) status' from technical forum moderator to just staff to better indicate that they are no longer active on the Forum, but at the same time show that the responses they made are from Digilent. Still don't have a nice solution on indicating competency level from a system point of view, but I'll keep looking to see if I can find a non-cheesy and effective solution (if it exists). Thanks, JColvin
  6. Now that is something I can definitely do. I'll get working on that.
  7. Hello, I'm not part of the sales team, but from my understanding, ideally you should put the name of the person who will be teaching the class that you are taking which uses the board with the academic pricing; that way we will be better able to confirm that you are qualified for the academic pricing. You do not need to inform them that you are putting their name down in the academic verification process. However, this is a manual process on Digilent's end to perform the academic verification and Digilent is closed on the weekends (despite what it may look like from my response here; I'm just making up hours from the workweek) so you probably won't hear back until Monday. If you have any further questions, I recommending our sales team at sales @ digilentinc.com Thanks, JColvin
  8. Hi @zygot, I agree that the current rating system is definitely misleading; some of the senior engineers at Digilent have a newbie status simply because they have only posted once or twice on the Forum (since it isn't their job to do so). The main problem at the moment is the software running the Forum (IPS) does not seem to have a way to sort the "Rank" (newbie, advanced member, etc), as they call it, differently than by number of posts, at least as far as I can tell from my admin page that I was recently granted access to. I don't immediately see a way to disable it, but I'll keep looking and see if there's a way to change the way rankings are calculated differently. At the very least, I can change the labels that are provided by the software to labels that don't have any indication of skill level. I only have the number of posts that I do since I've responded a lot to users stating that I don't know the answer and have asked another one of our engineers for input. :/ Alternatively, there is an option of reputation. Right now it is solely based on the number of "likes" the user has received on posts. I can change this to be more of a reddit style where you are able to upvote/downvote answers, but I don't think the Reddit model is appropriate for this Forum, but please let me know (and anybody else reading this thread) if you think that wouldn't be an issue. Right now all I have is a sample size of 1 with regards to that opinion, so not statistically sound at the very least. The reputation can be set to positive and negative options, only positive, or only negative. My concern with the negative portions of those is that some poor soul who asks what appears to be a silly question may get downvoted into oblivion and immediately become discouraged from attempting to learn anything in this field; I'd like to think that wouldn't happen on this style of Forum but who knows? I'm curious to know your thoughts on this. That's what I have at the moment. I'll keep looking into what sort of configuration options are available for the Forum. Thank you very much your feedback! Thanks, JColvin
  9. Hi @BeamPower, It looks like you ran the cd command for the GPIO demo rather than the OOB demo; as I mentioned on your other thread, I'm not certain why the GPIO demo is occurring so I've asked the creator of that project for some feedback on it. The "User" project is the Out of the Box project, but it is mislabeled in the tutorial (I think it used to be called the user project while it was still being developed); I will make sure that name gets fixed. I went through the out of the box demo on Vivado 2016.4 and was able to successfully generate the bitstream without any issues (although it did take significantly longer since the project is using MicroBlaze and it was my first time generating the bitstream for that project). I don't have a CmodA7 available to me at the moment though so I am not able to confirm that the project works as expected at the moment. Let me know if you run into any problems. Thanks, JColvin
  10. Hello @BeamPower, From my understanding you would be able to either work from the existing Vivado environment (it would ask you if you want to close out the existing project) or work from a fresh GUI without issues. But, I ran through the tutorial (for the Cmod A7 35t version) on my own Vivado 2016.4 and received the same errors that you did, so I have contacted the creator of this project and have asked them to help explain the proper way to go through this tutorial/correct it. I do not know if they are in the office today though and Digilent is closed on the weekends, but I'm hoping for an easy solution (as I imagine you are as well). I'll let you know if I get any updates. Thanks, JColvin
  11. Hi @InterestedTom, I don't have an IDC connector on me to confirm this, but I'm thinking the nubs on the sides (presuming we're thinking about the same standard connector) will not let it fit nicely; the Analog Discovery pins are pretty tight fitting with regards to the 100 mill spacing. @attila may have a better informed opinion on this though. Thanks, JColvin
  12. JColvin

    Arty-S7?

    Oh, and for others reading this thread, here is the video that asmi is referring to: https://www.youtube.com/watch?v=nzQYLflFfmo
  13. JColvin

    Arty-S7?

    Hi @asmi, I talked with my supervisor and learned that the Arty S7 is still in development at this point, so we don't know what ports and peripherals will be available on the board as of yet. Hopefully we all get to learn what it has soon! Thanks, JColvin
  14. JColvin

    LUT utilization tips

    Hello, I have upped the message count limit for PMs using some super secret methods (*looks at profile icon label*) ...or maybe not so secret methods. Please let me know if this ever becomes a problem again in the future. Thanks, JColvin
  15. Hello @a_basys3_user, I unhid your post; do you mind sharing what you found the problem to be and how you solved it? That way other people who run into the same issue you did would be able to search and find out the answer without having to go through the same troubleshooting process. Thanks! JColvin
  16. Hello, I have moved your question to a more appropriate thread where the engineer best suited to help you will be able to see and respond to your question. Unfortunately, I don't know the answer to your question, so I won't be of much help in this case Thanks, JColvin
  17. Depending on how your code is set up, you could also create what is known as a custom command in LINX. There is a Forum thread that walks through how to make one here as well as some documentation from LabVIEW MakerHub on it here. The idea behind a custom command is that LabVIEW (LINX) would send out a single command (realistically this will still be 5 bytes or so thanks to the packet checking), but then all of the operations will be done on the system board (WF32, Raspberry Pi, etc) based on a function that runs through the procedure once it receives the command packet from LabVIEW. This helps prevent LabVIEW needing to send out multiple commands of read this pin, process this, send out this, process again, etc, and can just have the microcontroller do all of the processing at it's own faster pace and then send the result back to LabVIEW when it is finished. If you have a lot of back and forth between LabVIEW and the MCU, this can definitely speed up the loop rate by merit of simply not communicating as often. The drawback with this is you'll have to do error testing and debugging on the microcontroller side rather than being able to do everything within a single environment, but you do get to potentially (again, depends on your application setup) speed up your loop rate. I guess as a side note, you are not able to port your LabVIEW VI to the chipKIT boards like you are with the BBB and RPi's at this point in time (as you noted) so there isn't a nice way to get those sort of speeds as far as I know. Hopefully that will be able to be done in the future, but I'm not privy towards those sort of developments. Thanks, JColvin
  18. Hello, You can check out the change logs on our Wiki for WaveForms here: https://reference.digilentinc.com/reference/software/waveforms/waveforms-3/previous-versions, but I'm not seeing any new updates yet nor have I heard anything new as of yet... Thanks, JColvin
  19. Hello, I've updated the reference manual for the Pmod IOXP to reflect the pin headers: https://reference.digilentinc.com/reference/pmod/pmodioxp/reference-manual. I would like to update the manual further with some more details on how to configure and work with the ADP5589, but I want to update the manual cleanly in one go rather than having it be in flux for a time where everybody besides me is confused about the state of the reference manual. I'm hoping that'll be done later this week. Thanks, JColvin
  20. JColvin

    Connector components

    Hi @Jon Frey, That looks like it would fit nicely. My only concern is that it also looks like it is just the housing without any built-in wires/pins, but I'm not sure if that was intentional on your part or not. I did a little bit of research and came up with a Mouser list of the header versions of these that do have built-in pins in case that was actually what you were looking for (link to Mouser search). Thanks, JColvin
  21. JColvin

    LabView Home Version

    Hi @Jon Frey, Signal Express is not included with LabVIEW Home Edition; the features that do come with LabVIEW Home (as per this page) are the LabVIEW Full Development System, the LabVIEW Control Design and Simulation Module, the LabVIEW MathScript RT Module, and the LabVIEW Application Builder Module. The LabVIEW Database Connectivity Toolkit and the Report Generation Toolkit for Microsoft Office are also not part of LabVIEW Home, even though they are included in the download for it (though I have no idea why they are in the download), which is why the serial number didn't work for some of the elements in the download. LabVIEW does have a ton of examples in the LabVIEW Example Finder (available under Help>Find Examples, in case you weren't already aware of it), so you wouldn't have to start completely from scratch. Thanks, JColvin
  22. JColvin

    HS2 HS3 Slew rates

    Hello @wrb123, I have asked one of our senior engineers about this; I hope to have a response back to you in the next day or so. Thanks, JColvin
  23. Hi @Mqasimag, Looking at the demo, it looks like the demo only uses the top six pins on the Pmod GYRO, so I would recommend getting a six-pin cable and 6 gender changer so you can connect your GYRO to the Basys 2 without having the lower set of pins being stopped/blocked by the PCB. It'll end up looking similar to this image: Please let me know if I misunderstood your question. Thanks, JColvin
  24. Hi @jonathanar1701, I have moved your question to the FPGA section of the forum where it is more likely to be seen by an engineer better suited to help you. That being said, I believe (as per this thread) that the Basys 3 uses the General IO demo, which is labeled as "GPIO" on our GitHub. From what I can tell, it only uses VHDL code (available on Github or in zipfile on our Wiki) and no IP cores. Let us know if you have any more questions. Thanks, JColvin
  25. Hi @coloradosensors, I am not certain what the issue is; I am hoping to be able to look into it very shortly. Thank you for your patience, JColvin