• Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by JColvin

  1. Hi @Mahdi, I get 3.75V from the 1.25V * Vbat calculation, but the issue you found remains regardless. From what I am able to tell, your deduction is correct that you are not able to use both primary power (in this case 3.3V) and a backup battery at the same time on the Pynq board or other system boards that use 3.3V logic. I believe you are using the "normal precision" Grove RTC, but the normal precision value one seems to currently have support for Arduino and Raspberry PI, which I believe both use 5V logic (the high precision one doesn't have any supported platforms listed and doesn't seem to support battery powered based on the chip IC despite having a battery holder). So what you would need to do is boost the VCC voltage through external circuitry (such as a buck converter) to above 3.75 V (or 4V to be safe) in order for it to work correctly; naturally, this is not very convenient, but I am not sure if there is another alternative Let me know if you have any questions about this. Thanks, JColvin
  2. Hi @mgooding9, I have moved your question to a more appropriate section of the Forum. We (Digilent) do not have a phase noise graph specific to our boards within our own documentation, but you can find details for the 100 MHz oscillator that we use on page 3 of it's datasheet here. If you are looking for the output jitter and duty cycle of the clocks and PLLs within the Artix 7 chip, I would recommend looking at the Artix-7 DC and AC Switching Characteristics datasheet from Xilinx. Let me know if you have any further questions. Thanks, JColvin
  3. Hi @KevinM, I entirely forgot about this, but we have actually designed an acrylic case for the OpenScope MZ (https://store.digilentinc.com/openscope-mz-acrylic-case/) if that accomplishes what you are looking for since you could just use longer screws with it. Thanks, JColvin
  4. Hi @KevinM, The recommendation remains that you should not attempt this. Safely leaving 0.05 mm (just shy of 2 thousandths of an inch) on each side of the hole will be incredibly difficult if not nearly impossible as a common small size for a PCB trace width is 5 or 6 mils. If you are willing to void the warranty on your board (by intentionally drilling a hole into it) and have equipment available to achieve this level of precision and then are able to check that no shorts have occurred via a microscope, then this is theoretically possible to do without ill effect. Good luck, JColvin
  5. Hi @KevinM, I talked with out layout engineer and they let me know that this is definitely not a good idea as the internal planes can short. The aperture in the copper planes/polygons around the 1.5mm mounting holes is 2.5mm in diameter, so you would need to keep within that area (and ensure that the drilling process does not cause any of the external area around it to become crushed/shorted together). Thanks, JColvin
  6. Hi @callum413, Depending on how long you are sampling, this may be possible to do within the WaveForms GUI itself as per this thread. Otherwise I believe this feature has been requested for the SPY mode (rather than just master mode) based on this thread, though I do not know what the current status is on this. @attila, do you happen to have an update on that second half? Thanks, JColvin
  7. Hi @Mighael Walker, I will say that you are the first person on our Forums (as far as I know) to mention that the AD2 is fragile, though based on the documents you linked, it seems like it's more of the flywire cables and their associated connectors that you are not happy with rather than the AD2 assembly itself? Otherwise, I don't think there will necessarily be any change to the calibration process itself since you are essentially changing the trace lengths that are being used, but the calibration process can already be done with or without an adapter (such as the BNC adapter); correspondingly to your second question I don't think the BNC connections will need special termination added as our own BNC adapter doesn't use any special termination (though it does have a jumper for AC/DC coupling). Thanks, JColvin
  8. Hi @KevinM, I think most of the corners will be okay; I'm finding out for sure though since there's one corner (top left when viewing the top side) that I'm less certain of. I'll let you know what I find out. Thanks, JColvin
  9. Hi @Divvi, Unfortunately, we do not have the silkscreen details readily available in a useful format and they do not have the bandwidth to be able to create and provide them at this point in time. I'm sorry we could not be of more help. Thank you, JColvin
  10. JColvin

    Arty A7 vs Nexys A7

    Hi @Phil, Let's see if I can explain the differences for you: There are a couple of variants between the boards. The Arty A7 has two chip size options, a -35T Artix 7 chip and a -100T Artix 7 chip. The Nexys A7 also has two size options in the -50T Artix 7 chip and the -100T Artix 7 chip. While the labels are slightly different (I'll find out which one is accurate and correct the other one, though I'm worried I'll find evidence for both), both of the -100T versions of Arty A7 and the Nexys A7 are the same chip. With regards to the Nexys variants, the Nexys A7 is a re-branding of the Nexys 4 DDR, which in turn is a partial re-design of the Nexys 4 (which had received an EOL for one of it's memory chips that it used, which you can read a bit more about on this page). Time line wise, I believe the original Nexys 4 came out in 2013, the Nexys 4 DDR redesisn in 2014, and finally the rebranded Nexys A7 in 2018. As for the Arty A7, it originally started out in 2015 as just the "Arty" that used an -35T Artix 7 chip. The product line has then expanded further over time to include a much wider variety, covered nicely in one of our blog posts here. I believe the Arty A7 also was rebranded back in 2018. The biggest difference you'll find between the Arty A7-100T boards and the Nexys A7-100T boards will be the peripherals that are present on the boards (and correspondingly the demos based on those peripherals) With regards to the Xilinx datasheet, you'll actually want to use this datasheet rather than the one you referenced which is exclusive to the automotive versions of the chips. Let me know if you have any questions about this. Thanks, JColvin
  11. Hi @savmil, I may be wrong about this, but it looks like your intended command of 05h may not be transmitting correctly; the datasheet for the S25FL128S says that data is clocked in to the part on each rising edge of the serial clock and the clock cycles are measured starting on the first falling edge of the SCK after the falling edge of ~CS. Presuming I am interpreting this correctly, since the CS line goes high on the 8th falling edge of SCK (which is required otherwise the command will fail), it appears you are actually transmitting a command of 82h rather than 05h, which as far as I can tell from the list of commands does not correspond to anything. Thanks, JColvin
  12. Hi @stever, Yes, this is possible to do; this is described a bit more in this thread where the oscilloscope, patterns, and waveform generator are synchronized with each other. Let me know if you have any questions about this. Thanks, JColvin
  13. Hi @DonT, Do you receive an error or pop-up stating that the calibration has failed? The LED pattern you describe for the OpenScope MZ is what you would normally experience for calibration (solid red during calibration and then flashing blue for when the device is booted and ready to use by WiFi is not connected), so I am a little confused at what you are experiencing. I presume you were following this calibration procedure: https://reference.digilentinc.com/learn/instrumentation/tutorials/openscope-mz/calibration? Thanks, JColvin
  14. Hi @kmesne, Given the two options, I'd definitely prefer using the HC-05; it is bluetooth compatible (so you could always pair it with your phone if needbe) whereas the HC-12 is a long range wireless transmitter that is not bluetooth based. Plus I do not think you will need to be able to communicate with your remote controlled vehicle from 1.8 kilometers away. To be fair, they both appear to be straightforward modules to use, so both will work, but the HC-05 will offer a little more flexibility in what all can be used with the project. Thanks, JColvin
  15. Hi @kmesne, Let me see if I see if I can help clarify a few things. The good news is that there is not a wrong way to do your project, provided it meets all of the given requirements. However, there are certainly harder and easier ways to accomplish this project. As a general policy of the staff on the Digilent forum (which has been unofficially adopted by a number of our kind and helpful forum members that offer advice on their own free time) is that we don't actively complete homework assignments or semester projects for people because we believe that approach isn't truly helpful for anybody trying to learn (and it could be construed as cheating). I believe the folks over at reddit feel the same way based on what I saw. Naturally, this does not prevent you from looking to see if there are similar projects already existing online that you could use as a guideline for your own project, but realize there is no guarantee that what you find will work for your system; you will likely have to do a bit of work changing it to fit your requirements/needs. Based on what you have described both here and in other places, I would like to believe that there are some resources available at your institution that can help guide you in making the needed steps and design choices for your project, but you will know that answer best. On the other hand, if you have specific questions on how particular part of design might work and have done some due diligence on accomplishing this for yourself, we can likely give you some advice. Let me know if you have any questions. Thank you, JColvin
  16. Hi @suraj.mallik, Unfortunately, we have not used that particular library that you linked to so I do not have any immediate advice for that. What I can recommend is that you look at this thread for some additional information using the Pmod IA. Let me know if you have any questions about this. Thanks, JColvin
  17. Hi @joe3, If you have your notification settings (available by clicking your icon in the top right of the web page -> account settings -> notification settings (on the right hand side of account settings) to receive a "notification when new content is posted" then yes, you will receive a message in some way. Let us know if you have any questions about this. Thank you, JColvin
  18. Hi @dry, I'm not intending to take over this thread, but I'm hoping you could clarify which OS you were using. My confusion comes from this two statements: Which of those statements is accurate? Thanks, JColvin
  19. Hi @rzsmi, Could you clarify which getting started guide led you to believe that you could readily use MicroBlaze on a Zybo-Z7? We would like to be able to correct that language if it is on one of our tutorials; the IPI tutorial you linked to (from what I can tell) separates between the Zynq and Microblaze processes. Thank you, JColvin
  20. Hi @Kostas, Unfortunately, those of us here at Digilent do not have experience with the AD2 support package for the MATLAB Data Acquisition Toolbox as it is my understanding that MathWorks developed this independently. I would recommend contacting MathWorks for some additional information on this. Thank you, JColvin
  21. Hi @Denci, I don't have the same setup as you so I do not have a nice graph to show, but I was able to set up a Pmod MIC3 to have data collected to a host board, send the serialized data to a digital-to-analog converter (also 12bits just like the PmodMIC3) which then provides the analog output directly to an audio output module (such as a PmodAMP2). The host board I was using (a microcontroller) had limited storage capabilities so I was only able to store a limited amount of sound to memory before sending it to the audio output at various sampling rates (ranging from 13 kHz to 45 kHz, corresponding to delays between each sample of about 75 microseconds to 22 microseconds, respectively). Each sampling and output rate sounded noisy to me, but I am inclined to think my setup involving lots of jumper wires and cheap headphones on a breadboard didn't help very much. I don't know if the Pmod MIC3 microphone is limited to a 15 kHz frequency as much as the sensitivity goes up; since it continually produces an audio signal there is no real limitation on how often it is sampled. Regardless, I was able to reliably get a "click" response from snapping my fingers though (presuming I snapped while it was sampling rather than playing out audio data), though I do not know how the response looks on an oscilloscope. Let me know if you have any questions. Thanks, JColvin
  22. JColvin

    Scope in labview

    Hello @Dejvid, I don't believe the LabForms VI's implemented any of the FFT capabilities of the WaveForms software. Depending on how the data is collected, you may be able to use a VI from National Instruments to then perform an FFT on the data, but I haven't looked into this. Otherwise, if you happen to already have the Analog Discovery 2, I would recommend using the WaveForms software and the Spectrum Analyzer tool (link to more details) if that is an option to you. Thanks, JColvin
  23. Hi @zygot (and anybody else who is wondering), We didn't provide the circuitry details; we instead provided them the name of the appropriate Digilent contact to discuss licensing options of this circuitry. We'll try to be more transparent about this sort of thing in the future. Thank you, JColvin
  24. Hi @tfcb, I apologize for the delay; this is the material that I used for the Pmod ISNS20 with Digilent's uC32 and the Arduino IDE. I commented out the debugging material, so I would not consider this a formal release as of yet. Let me know if you have any questions. Thanks, JColvin
  25. As a member of the self-taught group, I will agree that it is possible to learn how to use a Zynq or any other board. However, you will absolutely run into the fact that that zygot put nicely where you will need: You can readily get an understanding of the basics, but you will also need (to loosely quote Dan) "an understanding of the formal methods" to both create and verify work. Otherwise you will run into the mentioned "I ran the demo, but tried to change one thing and now nothing works"; it's hard to know what you're doing if you don't know how it works. So is it possible to learn? Yes, but if you're wanting to do complex designs (which you only learn which ones are complex by trying to build them yourself) you'll need to dedicate more than just spare time on the weekends to learning. The phrase "reap what you sow" is applicable here I think.