• Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by JColvin

  1. JColvin


    Hi @tomas61, When the experiment is running, you can use the mouse scroll wheel to adjust the settings in the Arbitrary WaveForm Generator, though each setting will jump to the predefined settings that you can see in each of their dropdown arrows. Additionally, you can change form the Simple view to Basic view (image attached) to go the style of the original WaveForms. Let me know if you have any more questions about this. Thank you, JColvin
  2. Hello, Those of us here on the forum here will not be able accurately respond to your question. You will need to contact our sales team (sales at digilentinc dot com) to receive accurate information about the academic discounts. Thank you, JColvin
  3. Hi @amamitof7am, I do not think the Analog Discovery 2 will be visible on NIMAX. None of the Digilent staff have used the Analog Discovery 2 with LabVIEW 2019, as we have not worked on this since late 2016. What I have seen in this thread is that the Digilent WaveForms VI set is compatible with LabVIEW 2017 though the AD2 toolkit was not compatible with it. Beyond following the Instructables that demonstrates running it on LabVIEW 2016, I'm not sure if there is anything else that can be done to get it working correctly. I'm sorry I could not be of more help. Thank you, JColvin
  4. Hi @JamieJ, I don't know the full answer to your question (the engineer much familiar with this will be able to respond when they get back into the office after the weekend), but there is some information about the impedance of the Analog Discovery 2 on this thread here. Thanks, JColvin
  5. Hi @wimtormans, Digilent did make the LINX driver. However, no work has been done on it since late 2016 and there are not any plans to update the LINX 3.0 driver for Raspberry Pi 3.0 deployment for newer versions of LabVIEW, so that particular functionality is only compatible with LabVIEW Home 2014. Thanks, JColvin
  6. Hi @mossygreen, They let me know that they don't know why there are two device listings showing up for the OpenLogger; when they test on the Mac machine that they have only a single set of tty and cu devices. With that in mind, their only guess at this point to help with this would be to try updating the device drivers; they realize this isn't much help but it's their best understanding of the situation at this point. Thanks, JColvin
  7. Hi @mossygreen, It sounds to me like you're doing everything right; I've pinged our firmware guy again to see if they have some additional input. Though apparently I didn't send this message yesterday informing you of this like I thought I did. Thank you for your patience, JColvin
  8. Hi @edge30, I don't think any of us here at Digilent have attempted to use buildroot or other open source tools specifically with the Cora Z7, so the staff here will be of limited help in that regard. Perhaps some other community members have attempted this, though some basic searching online (which it sounds like you did) didn't seem to turn up anything particularly helpful. Thanks, JColvin
  9. Hi @mossygreen, I talked with our firmware engineer more familiar with the OpenLogger and they let me know that they have been unable to recreate the Access-Control-Allow-Origin errors or the broader issue that you are experiencing. Are you using the localhost version of WaveFormsLive (or how are you accessing WaveForms Live)? It looks like you are attempting to do this through Safari, but I'm not certain. Additionally, the original URL you posted has mixes of the OpenScope and the OpenLogger, which is in accurate so the when the you attempt to update the firmware the URL the app figures out is wrong (hence why the process is failing). Could you update the offline build (the zip file for it is here) and then try updating the firmware? There are some details on how to do this here. Additionally, to confirm based on what I am seeing, you are connecting the OpenLogger to your iPad? Or am I misinterpreting that entirely? Thanks, JColvin
  10. Hi @joniengr081, You should be able to attach files now as part of a reply to a thread; you were in a different member account type since you had created an account but had not posted anything within a month or so of creating that account (this is done as an attempt to help prevent any bots from just waiting until their account is "old enough" before attempting to spam). I apologize for the confusion. Thanks, JColvin
  11. Hi @Stefano Antoniazzi, Have you gotten to look through the Adept SDK download that is available on the right hand side of the Adept 2 Resource Center? It has a number of examples and documentation for it all contained in there. Let me know if you have any more questions. Thanks, JColvin
  12. Hi @Rob Young, Personally I would be more concerned about the data rate that the Pmod WiFi can achieve (with network traffic and software overhead) rather than the rate at which the hardware can provide data through a Pmod port, as the latter can almost always be orders of magnitude faster. In theory an IEEE 802.11g complaint chip (like the one on the Pmod WiFi) can achieve data rates up to 54 Mbps (equates to 6.75 MBps), though in practice this throughput will be less, for example Resource Center for the Pmod WiFi shows 1 or 2 Mbps for transferring data over 400 meters; by how much depends on network speeds/interference and how quickly you are collecting the data to send out over UDP. On the software side for the Pmod WiFi, it only communicates through SPI, so for our FPGAs we use Xilinx's soft core processor (Microblaze) to work with the WiFi software stack to communicate with the Pmod WiFi through AXI Quad SPI IP (Xilinx product guide on it here), and there is some limitation on how fast that soft core processor will be able to run the SPI protocol communicating with the Pmod WiFi, though I'm not certain what the exact impact is in this case. I'm a little confused about your second question. RMII is designed for a physical interface rather than a wireless one, so they don't tend to be directly compatible (they even have different IEEE standards), so unless you find a module that does both (maybe some ESP32 modules do this) it won't be readily feasible. Also, what do you mean by "would look (as closely as possible) like a wired connection"? Do you mean visually look like it, physically in terms of connectivity, or internally with the software? Out of curiosity, why are you looking to do wireless connectivity rather than wired? Thanks, JColvin
  13. Hi @GMA, As a clarification point though since you mentioned it, Digilent does not have any software material for using the USB OTG port, though I believe that Avnet and zedboard.org has some resources on this. Thanks, JColvin
  14. Hi @GMA, As long as they are not "charging only" cables, then yes they will be able to transfer data as well. Naturally, the cables do not facilitate the software side of the data transfer, but there are a number of existing materials to help get the software side of things working. Let me know if you have any other questions. Thanks, JColvin
  15. Hi @GMA, A microUSB Type B cable will be physically compatible with all three of those ports that you listed (PROG, UART, and USB OTG). Thanks, JColvin
  16. Hi @sgrobler, I guess it hasn't been updated for OpenLogger; I personally wasn't aware of an Android app for WFL in the first place. I'll ask about the plans for that, though I suspect since I don't recall hearing about it that there aren't any immediate plans to get it updated. I do agree about the phone browser not being ideal; even in landscape mode, it's difficult to see any relevant details. Thanks, JColvin
  17. JColvin

    Zybo hdmi

    Hi @adityasonavane7, Which particular Zybo board are you using? The original Zybo with both an HDMI port and a VGA port? Or a Zybo Z7-10 or a Zybo Z7-20? We have a demo for the HDMI out for each of the three boards available here and here, with the latter being the same demo example for both the Zybo Z7-10 and the Zybo Z7-20, though the existing projects are different for the two boards. They are all designed for Vivado 2016.4 though and so will not immediately work in 2018.2. As Jon mentions in this thread, upgrading these projects is not trivial. You can update these IPs though as described in this thread. Let me know if you have any questions about this. Thanks, JColvin Edit: looks like Jon beat me to the punch by about a minute. Oh well.
  18. Hi @mossygreen, Okay; to confirm, have you tested this again after your initial post this morning? I did hear (after I originally commented) that the downloads were again briefly down again this morning or at least a bit slow (we're looking into the root cause of this). Out of curiosity, where did you get that particular link you posted? It appears to have the version number that would be present at the end of the link stripped away so the url link is invalid. I believe the link you need for the latest firmware is here. Thanks, JColvin
  19. Hi @mossygreen, The links for the Digilent Agent and (I believe) the firmware were down over the weekend until yesterday morning, so that might be what you ran into in this instance. I just verified on the OpenLogger I have that through WaveFormsLive I can configure with different released firmwares. Are you still running into this issue today? Thanks, JColvin
  20. Hi @hjain, Are you specifically using Adept to connect to your FPGA board (is it a Digilent designed board or a custom board) or are you using the Vivado Hardware Manager to connect your board? I presume you are still using Linux with the newer Vivado versions like you mentioned in a previous thread? If you haven't already, it may be worth it to uninstall and then reinstall the Adept components (available here) if you are using Adept (both the Runtime and Utilities) to make sure it was installed correctly. Thanks, JColvin
  21. Hi @eriksan, I believe that is correct that you would not be able to dynamically store every pixel for the Pmod OLEDrgb within the uC32 to display it. However, if you have a pre-designed image (or set of images), those can be stored externally and accessed and displayed whenever you need them. The other thing to consider though is if you are changing every pixel on the display or only a small subset of pixels (or just storing premade images in the on-board flash). In the end though, @xc6lx45's suggestion/consideration of using a board that is more readily designed to accomplish the task of image display and double-buffering than doing a lot of up-front work yourself. Thanks, JColvin
  22. Hi @hongthiet1994, I think you are correct in that the HY3131 will not be able to read a 1 kHz signal, based on the datasheet of the HY3131 only claiming an output rate of 5 Hz (though it isn't the most clear on this point). I believe the important thing to remember with this module is that it is acting as a digital multi-meter, not an oscilloscope (which can operate at high speed). Does that answer your question, or did I misinterpret what you were asking? Thank you, JColvin
  23. Hi @GMA, The physical end of a Type-C connector will not work with the Zedboard as the pins and data lines inside of the cable are different between Type C and Type B. You can connect the micro-B cable to a USB 2.0 or 3.0 (or 3.1) port on a host computer though, but the data connection speed will be limited to 2.0 data rates (because that was all that existed at the time the Zedboard was designed). Let me know if you have any other questions. Thanks, JColvin
  24. Hi @eriksan, Could you let me know what you are hoping to accomplish with the double buffering? Additionally, when you are referring to a QVGA Pmod, are you referring to the Pmod MTDS? If you wanting to know if you can use it with Digilent boards, you can see the list of support Digilent boards (of which the uC32 is listed) in the library download. You would not want to use the SF3 to expand RAM; the SF3 (and other serial flash modules) are designed to store data in the long term and cannot be used as RAM in the way you are intending. You could store premade images on them, but realistically I would recommending having them on a microSD card and then insert that SD card into the slot that is present on the Pmod MTDS (or the MTDS Shield). Regardless, the both variants of the MTDS have their own embedded PIC32MZ processor that controls the display process, so you are only able to send commands and are not able to configure if double buffering is used by the display or not. As for the individual connections, you can individually wire the Pmod MTDS to the correct pins on a uC32, attach it to a Pmod Shield as you suggested, or just use the MTDS Shield directly on the uC32 (or a different supported board with Arduino headers). I don't believe any of the Digilent boards have graphical RAM that you are able to specifically utilize. They tend to instead have SRAM. With regards to the Pmod OLED or the Pmod OLEDrgb, I'm not certain what the purpose of double buffering would be since OLEDs do not refresh their displays like an LCD screen; you can simply manipulate the individual pixels to be on or off through the provided libraries. However, you certainly can have other images prepared and loaded into memory on the Pmod OLED before updating the display. Let me know if you have any questions about this. Thanks, JColvin
  25. Hi @sgrobler, The only time I encountered this error regarding your second question was when I powered on my OpenLogger (after the WiFi data had been stored on the OpenLogger) before I had turned on the hotspot on my phone; if I did that, I would get the connecting to device message and nothing would happen. If I powered on the hotspot first and then the OpenLogger second, the blue LED on the OpenLogger would turn solid (indicating WiFi was ready and connected), then it would connect without issue. Thanks, JColvin