• Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by JColvin

  1. Hi @rappysaha, We're not fully certain about the differences between those two licenses as those of us here on the Forum are not Xilinx employees. I believe that the two licenses that you are referring to are the same license (I didn't see a "voucher" on the second license that you linked to though), so you would need to contact Xilinx in order to get a full and accurate description between specific licenses. Thank you, JColvin
  2. Hello, I have confirmed that the speed grade is indeed -7 and have updated the Resource Center to reflect this. The full FPGA part wasn't listed on the Resource Center (I didn't update it since I couldn't figure out an easy way to make it visually look good without having to break that one section into three different lines), but it is XC2C256-7TQ144C. The "-7" indicates the speed grade, and the "C" at the end indicates that it is a commercial grade part. I'll work on getting the other FPGA pages updated as I notice them. Thanks for helping bring this to light. JColvin
  3. Hello, I talked with our senior engineer for our microcontroller boards and they do not know anything about the SEGGER J-Link, so no, we as Digilent will not have any information on how to debug chipKIT boards with that particular debugger, at least in the foreseeable future. I was informed that JP3 and JP4 are JTAG/Trace ports for Imagination Technologies, but we don't really have any information beyond that. It looks like Imagination Technologies has a document from January of last year that talks about using JP3 on the WiFire though. I'm sorry I couldn't be of more help. Thanks, JColvin
  4. Hello, We're in the process of getting the Resource Center updated; I'm confirming if the -7 rating is accurate. Thanks, JColvin
  5. Hi Henry, I'm not the most familiar with the original Analog Discovery, but from my understanding the factory settings should be good to go. You can go through a calibration yourself though on the initial WaveForms page in case some offset has occurred in your hardware. An engineer more experienced with the Analog Discovery commonly checks this sub section of the Forum and will be able to provide more advice/correct what I've said if needbe. Thanks, JColvin
  6. Hello Muhammad Tufail, I know the Basys 2 is currently in a limited supply (at least as per our website), I would recommend contacting the Digilent sales team by emailing sales @ digilentinc .com for the most accurate information in terms of price and timing. I know we have a distributor based in Pakistan (http://www.rastek.pk/index.php), but it doesn't look like they carry the Basys 2. Thanks, JColvin
  7. Hello @Simon, I have moved your question to a more appropriate location on this Forum so that the appropriate applications engineer will be able to see your question sooner. Thanks, JColvin
  8. Hi @[email protected], Thank you for the feedback; this is a slightly different take than what the various higher ups were thinking the purpose of the chat channel would be (to get a faster turn around time for responses). While this is similar, it has a distinctively different flavor(?) than just getting a faster turnaround time, since I think that is an expectation associated with chat channels. The other concern that was brought up was the fact that we as Digilent would not be able to guarantee that we always have somebody available to talk to in the chat, even just during the weekdays, so there's hesitation of representing a channel that we couldn't give proper support to. I wasn't aware of the recording portions; that'll be a nice thing to show that the thought process of working through a problem will still be available. I'll definitely bring up the idea of that the chat better supports faster communication for a project so customers aren't waiting multiple weeks, but I think at this point Digilent will still stick with the Forum since there are also a number of examples where communication goes quickly between Forum posts; to be sure it's not as fast as the chat, but if it takes both parties a half day or full day to respond to the other (due to having other daily life tasks or whatever might be the case), I suspect it won't be considered as a dire need. That being said, I don't think there will be any complaint if a community chat channel was created (not that we could do anything to stop it anyway). I'll continue to look into this though and do some data collection here on the Forum to get some numbers since that'll be a valuable metric in the end. Again, thank you for the feedback, JColvin
  9. As a side note, I think it would be good if we created some sort of chat channel, if only because IPS (the company that provides this forum software) will retire their chat feature on May 1 of 2017 (as per their update here). More googling showed that other people had promoted IRC chats on the IPS forums with the CEO of IPS present on that thread (link), but evidently that didn't come to anything. As for the Digilent side of things, there isn't really anything we can do to prevent them from removing the current chat that exists. I'll look into the other options to see if they have some of the things that various higher ups at Digilent would want, but the biggest thing is that right now it is wished that the Digilent Forum is our primary means of support since it is a feasible way of helping customers while keeping a growing "database" of existing solutions that people can find on their own, since having extensive documentation on our Wiki on how to approach every problem isn't feasible (yay engineering!). That and I imagine Digilent would want their own branded version considering that we are a company and all, as opposed to a group of people, although as the Forum is a group of people we'll see how that can change things. I'll bring it up in a meeting later this week to get some initial thoughts on this. Thanks, JColvin
  10. JColvin


    Hello usha_tiwari, Digilent does not sell the NI ELVIS, so we aren't able to offer proper support or guidance for using it. I would recommend posting your question in the National Instruments Forums instead. It looks like they have a forum specific to the ELVIS board here. I'm sorry I could not be of more help. Thanks, JColvin
  11. Hi Cristobal, I don't recall getting the Pmod AD5 working nicely; if I get the opportunity I'll try to take a look at it again, but I'm not certain when that will be. I think some of the changes I made were to the github code, but I don't recall at the moment. Thanks, JColvin
  12. Hello, This is just some friendly feedback on my part since I realize the software is still in beta, but I was taking a look at WFL again and noticed that I'm not seeing the labels for the Analyzer channel that Dharsan made reference to. Are those live or hopefully in a build that'll be pushed live soon? Also, (at least for me) it looks like the main viewing screen doesn't update with the waveform I've set from the waveform generator after hitting the "run" button. It doesn't update the screen until I hit the "stop" button while running (or by hitting the "single" button for just a lone acquisition). It also looks like that while running (presuming the waveforms are shown on the screen) I can have an analyzer line disappear from the screen, but not reappear. The waveforms (or at least the OSC1 and Waveform generator) also don't look like they disappear from the screen while the simulated OpenScope is set to run mode, even if I click their little power buttons. I'm not sure why the analyzers do that, but it seems like the others aren't updating maybe because once the run mode is activated it collects all of the current settings and sticks with it? It's a little weird since I'm not seeing the screen update until I hit the stop button (as I mentioned earlier). But I can make changes to the AWG while it's in run mode and see those changes when I hit stop, so that doesn't help my collect all of the current settings theory...hmmm. Mostly I figured I would mention this just in case a second pair of eyes was needed to help spot some of these things. Thanks, JColvin
  13. Sorry about that; Digilent is closed on the weekends so the appropriate people on the Kickstarter project (not me) probably didn't get the opportunity to collaborate in the midst of our other daily tasks. That and I think Digilent is in the awkward position of trying a Kickstarter for the very first time for our first open source scope, but having it be way more successful than we anticipated. I would like to think that a logical choice for a stretch goal would be to "upgrade" each backer level with something that is either the same across all of them or somehow appropriately tiered, but that isn't useless (which we all agree on in this thread), reasonably expected to come over time (software improvements), or drastically change shipping times (hardware changes). Perhaps the last one could be done if the change and timing "was right", but I don't have any idea what that might be. But those are all my random thoughts as somebody not in on the project, but interested in it and wanting to see it succeed. I'll see if I can come up with some fun (hopefully not too cheesy) things that could be done that make sense.
  14. Hi Tuan, I don't know the answers to most of your questions, but I do know that you can find the Base System Design for the Zybo on it's Resource Center on our Wiki; it's in the box on the right hand side underneath "Design Resources". Thanks, JColvin
  15. Yeah, I was a little bummed myself when I learned that is was decided to not release an intermediate solution to address this problem in the mean time. AFAIK, the mid-February timeframe should still be accurate though.
  16. Hi jmw, Very cool, thanks for sharing! Presuming you don't mind, I have put links to these projects and this thread on the Pmod OLED and Arty Resource Centers under Additional Resources and Example Projects, respectively. Thanks, JColvin
  17. Hi @HansV, I don't personally have the ability (or expertise) to implement the changes you suggested, but I do have a couple of questions simply because I'm curious. What do you mean by "have the relevant colors in the text that do disappear in the label option"? Do mean something like the 'black text on a black background' type of effect or something else entirely? And just to confirm your last point, you would like the images/labels to be layered so that when they are inserted, they go behind the existing trace? Or at least be able to place them on the screen and then re-run a data aquisition and have the new traces draw over the label/picture? Thanks, JColvin
  18. FWIW, it looks like both of the links are working now; I had also noticed that the Thingiverse link wasn't working yesterday. I'm not part of the OpenScope project here at Digilent, but I wouldn't be surprised if those files also found their way onto GitHub. There might be a delay in terms of pushing it to public view to help ensure that only the appropriate Kickstarter backers have early access, but again, I can't confirm or deny that. I think @LariSan will probably be able to get us a more formal answer early next week. Thanks, JColvin
  19. Hi Dharsan, Could you also increase the trace width (i.e. make it bold) when a particular waveform (analyzer or oscilloscope or otherwise) is selected? Thanks, JColvin
  20. I'm a little confused as to what you're wanting as well if a label isn't what you're looking for. As far as I can tell, you want some sort of highlighting effect around which analyzer pin you have selected to appear in the lower right hand corner (as indicated by my poorly drawn red box) and (what I would personally like) a label to appear when you click on the corresponding arrow with some information (shown by my poor hand writing in red). I took the screenshot from your video.
  21. Hello, I'm sorry to keep bothering you, but I'm not understanding some of your math. If I wanted a sampling frequency to fit 100 samples in a single division that was representing 1 ms, wouldn't that be 100 kHz (1 kHz is one sample per millisecond, so a 100 kHz is a hundred samples per millisecond)? I would think that 192 kHz gets you 192 data points per division (based on a 1 ms/div scale). So then, if I had a time base of 100 ms/div, I would need (working off of needing 192 points per division) a sampling frequency of 1920 Hz, theoretically requiring (with a buffer size of 3840) 2 seconds to get all of the data, plus some extra time to process it and display it on the screen. I'm not sure why I'm not seeing the all of the 100 ms/div sections filled with data though. I got some screen captures of the 100 ms/div running and then a zoomed in section of the stopped data that was being run at the 100 ms/div timebase. It looks like in the zoomed in version shows 200 total maxes and mins, implying a sampling rate of 2 kHz, which is fairly close to the expected 1.92 kHz (and probably would work out to be that if I could get the exact distances right, but I don't know how to nicely manipulate WFL into doing that). Going off of the 1920 samples per second and a buffer size of 3840 (since I have a 1920 by 1080 screen), I should expect to see 2 seconds worth of data plotted, correct? But I only see 0.7772 seconds of data plotted on the running screen (based on the largest magnitude of milliseconds I could get the tooltip to show) rather than 2 seconds worth of data and I can't seem to get the panning to show me any more data than what's shown on the screen...
  22. Hi Kristoff, Thanks for getting back to me. I guess I have one more clarification question about your first point on the timebase and sampling. If I had a time base of 100 ms/div or 200 ms/div, the device would then collect for 1 second and 2 seconds respectively, correct? It looks like it gets cut short from the amount of expected, but still maintains what appears to be a reasonable resolution considering the amount of data it has to collect. Is the software just hitting an internal limitation on how long it can sample for (since as you mentioned it's focused on fast acquisition as opposed to streaming or buffering)? As for the Math Menu, I guess what I was envisioning was if I was collecting some real data that was changing and had the WFL set to run (as opposed to single shot) I would like to be able to refresh the math as the incoming data is changing. Would the Math Menu do this automatically or would I need to close out the window and then reopen it to get updated data? If it wasn't dynamically updating as new data was being collected, I would like to be able to click the refresh button to update all of the values in the Math Menu without the Math Menu closing on that first click. I'm excited to see how everything develops! Thanks, JColvin
  23. This is just an idea, but maybe the backers who pledged for a case by itself or an OpenScope with a case can get it personalized in some way (or maybe have it say "proud Kickstater backer" or something similar), and everybody else gets generic cases instead? I'm not directly involved with this project so I don't know if there's a difference between the injection molding and 3D printing of the cases or how difficult it would be to personalize the cases and the time constraints that would be placed on such an endeavor. @WereCatf, what were you envisioning for the educational aspect? Learning materials or some physical components to play with? My concern with either of those is that it would mesh a lot with the Learning Edition backer level.
  24. Hello! I really like the look of WaveForms Live, and I don't doubt that one day most applications will be browser based rather than having a client version on your PC so I think it's a good think to start working on now, but I do have a few questions/feedback about it. @Kristoff, it looks like the buffer size (at least for the simulated device) appears to only collect about 3/4's of a second of data at a time. I imagine this is fine for a wide variety of debugging applications where you just need to see if the series of digital commands you sent/received are accurate, but in long term applications I imagine you would want to be able to stream/record data to your PC. Is it possible to stream data on WFL? It took me a long while, but I finally found the tutorial button in the lower right hand corner; it would be nice if there was a "Tutorial" watermark (at least on the initial screen) that helped draw attention to it. I'm glad that every time I take a new data sample set, it re-centers the acquisition to 0 seconds. However, when I'm scrolling in and out on the data set to view the data more closely and changing the time base, it seems to lose the centered position on 0 seconds. Is there a way to add a "re-center" button or have a way to nicely lock on to different segements of the time base (say every quarter or 8th or whatever is reasonable of whatever the timebase currently is) when you are panning across your data by dragging the associated bar at the top of the screen? Will WaveForms Live eventually be able to connect to existing Digilent instrumentation like the AD2 or the EE board? Could we get some more information/tutorial walkthrough on the Digital I/O? It's disconcerting when you first see it and attempt to click on it, but have nothing happen since I'm not in the correct settings yet. It looks like I can also get some green waveforms when I manage to switch them to "A" (for analyzer? not sure what that implies since I thought I could see "inputs" as well), but I don't know which green waveform corresponds to which analyzer that's enabled. They also seem to be on their own scale that I don't know how to adjust. I like the look of the Math Menu, but I wish that when I clicked the refresh math button it didn't close out the Math Menu popup, then have to click refresh again to convince myself that it worked, and then re-open the Math Menu. The Device Pinout button (which I'm super happy is there so I can easily reference which hardware pin my software is connecting to) next to the main viewing section seems to have big shorthand labels for everything but the last 5 SPI/UART pins on the lower right. Do those have names? What does the Console Log mean under Settings? Otherwise in terms of positive feedback, I think that looks very nice, I like being able to type in specific settings for voltages and frequency. I'm glad it's a dark background rather than the white, although I partially wish I could turn it to white some my laptop doesn't auto adjust the screen contrast everytime I switch tabs. It also looks very intuitive and easy to get things up and running. I also really like that I can zoom in nicely from a large timebase to a smaller timebase and not lose a ton of resolution. I'm super excited to see how WFL and OpenScope continues to develop! Thanks, JColvin