• Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by JColvin

  1. 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
  2. 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
  3. 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
  4. 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
  5. 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
  6. 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
  7. 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
  8. 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
  9. 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
  10. 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
  11. 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
  12. 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
  13. 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
  14. 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
  15. 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
  16. 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
  17. 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
  18. 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
  19. 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.
  20. Hi @John Evans, I'm personally not able to find the actual part number individually, but there are some details about the microUSB connector on this thread here: Is the connector broken off entirely, or are there some instances where the cable was plugged in upside down so that the tab inside of the connector was simply bent downward slightly? If the latter is the case, you can push the tab back up with a small flathead screwdriver or something similarly sized. Thank you, JColvin
  21. Hi @VishnuChittan, Yes, that is the main drawback with the embedded AD5933 within the Pmod IA. The catch with the Pmod IA is that you already need to have some sort of idea of what impedance (or at least a general range of impedance) in order to receive and interpret accurate data. If you know (or can make an educated guess) what the approximate impedance will be, the next step would be to calculate if the output voltage range through the unknown impedance will saturate the ADC sampling this data, which as per the schematic is limited to a range between 0V and 3.0V. The equation used to figure out the gain applied (and what voltage would be presented to the ADC inputs) is as follows (as illustrated on page 18 of the AD5933 datasheet) : Gain = Output Excitation Voltage * PGA Gain * Gain Setting Resistor Impedance / Z unknown Where: Gain (measured in volts) represents the peak to peak range applied to the ADC Output Excitation Voltage is a register that is set in the AD5933 and can have a value of 0.2 volts, 0.4 volts, 1.0 volts, or 2.0 volts peak to peak. However, note that these values (listed on page 23) may actually be different as described on page 13, depending on what supply voltage you are using. PGA Gain is register that is set in the AD5933 and can have a value of 1 or 5 Gain Setting Resistor Impedance is the selected resistor value via the header J2 (sel); if left alone (sel pulled logic high), this resistor value is 20 Ohms. If pulled to a logic low state, this resistor value is 100k ohms. Note that with resistors your actual resistance may vary depending on the resistor variance (I believe 1% or better resistors were used). Z unknown (or predicted in this example) is the unknown impedance that is applied between the two SMA terminals (J3 and J4) If the calculation yields a Gain value greater than 3V (or close to it), this means that any frequency sweep applied will saturate the input to the internal ADC and provide unhelpful and incorrect results. At the same time, you do not want too small of a result in volts because the 12-bit ADC will not be able to effectively measure any changes as each difference may or may not produce a change in the LSB. If either of these things occur, either theoretically or in practice, you would likely want to change one of the settings (Output Excitation Voltage, PGA Gain, Gain Setting Resistor Impedance) to see what gain you would receive through the system. Let me know if you have any more questions. Thanks, JColvin
  22. Hi @kmesne, The Pmod COLOR does sense the color of objects; it even uses the same chip as the Adafruit part that you listed. The restriction (and perhaps I am misunderstanding your application) is that the color you are wanting to detect needs to be very close to the sensor. This is illustrated on the Adafruit page where they place an orange/apple directly on top of the sensor (link) in order to have it correctly detect the intended orange/green. Let me know if you have any more questions. Thanks, JColvin
  23. Hi @kmesne, We responded to your other question here with some detail, but I will try to elaborate a little bit more here. The Pmod COLOR is not intended to detect colors from any sort of distance, so you would need it next to the red/green light indicator and then have it transmit data to the main controller for the car as opposed to be mounted on the car (unless the red/green indicator was on the car itself). I believe the Pmod COLOR could detect the green in a green cube, but it would need to be fairly well lit up due to the limitations of the sensor itself. As a bit of perspective, this will be a large and non-trivial state machine (especially for first semester project) with a lot of conditions to be covered; is light red or green to control the enable bit on 2+ H-bridge drivers running the motor, which needs to be checked frequently in order to obey traffic laws, as well as the enable bit being toggled as appropriate when changing input directions if the vehicle can go in reverse to avoid burning out the h-bridges, pwm control over the enable pin to allow the vehicle to turn; all done over (presumably) 3 remote systems communicating with each other; the controller with the direction buttons, the color sensor detecting the light change, and the RC vehicle itself. Which system/input will have priority in the state machine and how often will you need to check each input to provide a "smooth driving experience" will all be things that you need to consider. Some good resources for VHDL basics can be found at asic-world.com and fpga4fun.com, as well as this page that discusses state machine construction in VHDL. Thanks, JColvin
  24. Hi @Bhushan021, We don't have an Arduino Due to directly test this ourselves, but I believe the ModbusMaster.h should generally be compatible with the Pmod RS485 since from what I can tell in the material available on the associated github account (link) it just uses a serial port and flow control bits which are required for the Pmod RS485 to work correctly. My understanding with the Arduino Due is that it subject to the caveat listed in the readme where you will need to disconnect the module from RX while uploading the sketch before being able to reconnect and properly use it. I am uncertain of how the other two pieces of hardware listed in the Github hardware states differ from the Pmod RS485 though. Thanks, JColvin
  25. Hi @RussGlover Ah, sorry about that; it's on ACBUS5. Let me know if you have any more questions. Thanks, JColvin