JColvin

Administrators
  • Content Count

    4172
  • Joined

  • Last visited

  • Days Won

    165

Everything posted by JColvin

  1. 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.
  2. 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
  3. 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.
  4. 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
  5. 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
  6. 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
  7. 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
  8. 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.
  9. 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...
  10. 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
  11. 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.
  12. 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
  13. JColvin

    PmodALS

    Hello, I have moved your question to a more appropriate section of the Forum so that other users will be able to find your question more easily. The main issue you are running into is that the code example you are referencing is not for Vivado; it is for MPIDE, which is a programming environment similar to the Arduino IDE, neither of which will program the FPGA (which FPGA are you working with?). The code that you will instead need to use is available in the folder you presumably downloaded from our Github to get the PmodALS_v1_0 IP. The particular folder name style you are looking for is explained in step 12 of our Using Pmod IPs Tutorial. It has all of the appropriate library code for the PmodALS to run in the SDK. As for the ext_spi_clk pin on your block diagram, the Run Connection Automation does not connect that pin (since different Pmods require different clock speeds). I recall the Pmod ALS needing a pretty slow clock speed that Vivado had difficultly generating. I don't know which FPGA board you have, but you can add an additional output clock to the clocking wizard and configure it to output a 10 MHz clock. It's outside of the the 1 to 4 MHz spec listed in the datasheet for the Pmod ALS, but is within the maximum clock frequency limit (20 MHz) for that same datasheet. You can then connect that 10 MHz clock to the "ext_spi_clk" pin, and from what I've heard from my co-workers, this works for the Pmod ALS. This tutorial is for the Arty (again, I don't know what FPGA you have) but step 3.3 in it's MicroBlaze tutorial shows how you would add an additional clock for the clocking wizard. Let me know if you have any questions. Thanks, JColvin
  14. Hello, I have moved your question to the main portion of the Scopes and Instruments section of the Forum where the engineer best suited to help you will be able to see and respond to your question. Thanks, JColvin
  15. On a more personal note, I'm pretty excited about the project and have put some money where my mouth is and backed the project myself to show my support.
  16. Hello! I'm excited to announce that Digilent has our first Kickstarter project for the OpenScope! I won't be able to give the project proper justice in describing the OpenScope and WaveForms Live, so I encourage you to check out the Kickstarter to learn more about the mission of the project. With regards to this sub forum, Digilent would like this to be a place where backers of the Kickstarter are able to ask questions and provide feedback for both the OpenScope and the browser based WaveForms Live. As such, we kindly request that only backers of the project ask questions related to the OpenScope and WaveForms Live and provide feedback related to functionality, features, and the like. Those of us involved with the project at Digilent will do our best to respond back to those questions and feedback. However, if you just have some general encouragement or other positive feedback that doesn't fall into the described request in the above paragraph that you want to post here, I personally won't feel a need to stop you Thanks! The Digilent Team
  17. Thanks for sharing what you did! I think the reason the enclosure is such a tight fit to begin with is that the Analog Discovery (1) and other Digilent boards had some historical issues with the USB connector on the PCB physically coming off, which wasn't so easy to fix for most users, so it was made sure that wouldn't be a problem with this one. From what I've been told, it was found that you were far more likely to break the USB cable prior to the USB host connector coming off the PCB. I guess it's a little odd that you had issues with it disconnecting upon any sort of movement; I've picked up my whole assembly to move it from from one side of the monitor to the other, or rotated the whole assembly while debugging an accelerometer and haven't had any sort of disconnection issue. Glad to hear it's working the way it should now though.
  18. Hello, I have moved your question to our FPGA section of the Forum, so that way one of the Digilent engineers familiar with that particular demo of ours will be able to see and respond to your post. Thanks, JColvin
  19. Hi daveoprea, @[email protected] is correct in his guess that Digilent does not really support the Raspberry Pi directly; what we do have is the LabVIEW MakerHub LINX which can target the Raspberry Pi and has pre-existing VI's for a number of Digilent Pmods (although not all of them), so creating code to run directly on the Raspberry Pi is a bit out of the realm of what Digilent does. I'm not even certain myself how one would do it outside of LINX that's in a nice friendly fashion. The Pmod AD1 does technically have two rows of 6 pins each, but in terms of connecting it to the Raspberry Pi, you would only want to concern yourself with the male pins on the J1 header side of the module. You'll end up physically connecting the Raspberry Pi and the Pmod (whether the Pmod AD1 or any other Pmod) via a set of cables and individual gender changers (Digilent has some of these that come in rows of 6). Digilent doesn't have a single cable (whether for 6 wires or a single wire) that will directly connect the two pieces of hardware. Because of the way the Raspberry Pi is set up (and truthfully, the vast majority of microcontroller/microprocessor boards that exist) you will need to wire the Pmod to the board through individual pins since the Raspberry Pi does not have a "Pmod Host port". There isn't really any way to get around that for the Raspberry Pi that I am aware of. In terms of SPI, you'll find that a variety of development boards (such as the Raspberry Pi) have a number of prebuilt SPI ports, commonly labeled SPI0, SPI1, etc. For a Pmod that uses SPI (I2C and UART follow this same pattern), you would only need to connect to one such port, such as SPI0. You wouldn't have to worry about SPI1. In terms of the physical connection, it would be done much like it is shown in this tutorial that runs a SPI Pmod on a Digilent board through LabVIEW; the Raspberry Pi will not have the same connection pin numbers, but you would connect the Pmod to the SPI pins that do exist on the Raspberry Pi in a very similar manner. As Dan correctly points out, you would only need to connect the CS pin, the D0 pin, the CLK pin, the GND pin, and the VCC pin to get "half" of the Pmod AD1 working. In theory (as he mentions) you could also connect the D1 pin to a different SPI port (since SPI only consists of 4 pins: CS, MOSI, MISO, and SCLK; you can learn some more about SPI here), but that has a whole other set of problems that is beyond the scope of this thread (that and I don't know how it would be done on a Raspberry Pi directly). I suppose this begs the question of it's so difficult to make the Pmod AD1 work on a microcontroller why was it designed this way? The answer to that is that it was designed for FPGAs (and prior to Digilent getting its toe dipped in the microcontroller sector), and FPGAs can handle two data input lines simultaneously far more easily than a microcontroller and can easily account for pins being in different arrangements. I guess a final point might be that at Digilent we want to help teach people about electronics and want to help people learn about them. We'll definitely help you in the ways that we can to get you started, but we won't be able to promise that everything will be as straightforward as plugging a keyboard into your computer and having it work, cool as that would be for Pmods; there'll be a little more learning involved Let us know if you have any more questions. Thanks, JColvin
  20. Hi mishassio, We like to avoid putting personal emails on our Forum. Although we are moderators here on the Forum, we do not have access to the main Digilent website to see your information. As Christina is our coordinator for international academic orders (who also does not have access to our main US system), you will need to provide the information she requested to her via email. Thank you, JColvin
  21. Hello, Here's a page with the pinout on the Raspberry PI 3: https://developer.microsoft.com/en-us/windows/iot/docs/pinmappingsrpi which nicely lists the pins and protocols you're looking for. Let me know if you have any more questions. Thanks, JColvin
  22. Hello, The LabVIEW software is available for download here: https://www.labviewmakerhub.com/doku.php?id=libraries:labview:start. After clicking the link, click the Download Now button. You will be directed to another site to download the software. During the installation process, you will be prompted to enter the serial number that you received in the email from us. Once the install and activation process is complete, you will be ready to use the software. If you've already downloaded the evaluation version of LabVIEW and had the demo version run out, you can activate LabVIEW Home with the serial number received in the email from us. This serial can be used to activate the software online or it can be used to generate the 20 digit activation code manually. If the computer you're using is connected to the internet you can activate by performing the following steps: Launch NI License Manager from the Windows start menu. In the left column find LabVIEW Home Edition. Right click it and choose activate. Choose automatically activate through a secure internet connection. Enter your 9 digit serial number and complete the activation process. Repeat the steps for Applications Builder (under Modules) and any of the other LabVIEW Home Edition Modules you've installed (listed below). Let us know if you have any trouble activating the software and we can manually generate activation codes for you. As a side note, LabVIEW Home Edition includes: LabVIEW Full Development System LabVIEW Control Design and Simulation Module LabVIEW MathScript RT Module LabVIEW Application Builder LabVIEW Application builder enables you to build executables from your LabVIEW VIs that can run without the full development environment (they still require the LabVIEW runtime). It also enabled you to deploy LabVIEW VIs to BeagleBone Black and Raspberry Pi 2/3 using LINX. If you’re new to LabVIEW, you can get started quickly with the LabVIEW MakerHub’s LabVIEW Basics video tutorials (https://www.labviewmakerhub.com/doku.php?id=learn:tutorials:labview:basics). If you have any questions about your LabVIEW project feel free to join us in the LabVIEWMakerHub forums: https://www.labviewmakerhub.com/forums/. Please let us know if you have any other questions. Thanks, JColvin
  23. A customer on our website asked the following question: I purchased the LabVIEW Home Bundle from you and got the corresponding serial code for it, but I'm confused as to what I'm supposed to do next. The answer is below.
  24. @Ross Arnott, I asked around and it sounds like the update will be scheduled to release sometime next month. As for the reason why it seems so late in relation to this thread, perhaps there's something else that Digilent is planning to coincide with the update . Thanks, JColvin