• Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by JColvin

  1. Hi @yoom@misoccer.us, The OpenLogger does not have any way to measure protocol information, so it would not be appropriate for a sensor that converts the K type thermocouple Analog Data into digital data (at least on the interpretation side of things). Similarlly, while it could work for just analog data, the OpenLogger does not support the needed resolution (41.276 uV/deg C) to correctly analyze the data. If you are using a sensor, such as the Pmod TC1, I would recommend using a microcontroller or microprocessor to receive the data from a thermocouple. Let me know if you have any questions about this. Thank you, JColvin
  2. Hi @RaBe, Are you using a level shifter with the Arduino Nano V3 and the Pmod ISNS20? Even if you connect the Pmod ISNS20 to 3.3V power, that doesn't change the 5V logic that comes out of the Arduino Nano itself. Thanks, JColvin
  3. Hi @tfcb, I am taking a look into this; I connected a level shifter of my own (Digilent's Pmod LVLSHFT rather than the Sparkfun one you linked to) to connect an Arduino Uno and Pmod ISNS20, but I too am getting strange values (no initial offset for example), so I'm debugging some more. Thanks, JColvin
  4. JColvin

    basys 3 WiFi usage

    Hi @Dom_123, Would you be able to upload your zipped project to either dropbox or google drive or something similar? The fact that you are now getting 0's for the temperature and humidity indicates that your Pmod HYGRO might be damaged, though this will help verify this for certain. Additionally, did you put the source and header files in the wrapper rather than just the application like it shows in your screenshot? Thanks, JColvin
  5. JColvin

    Sample mode

    Hi @Dejdys, Unfortunately, I'm personally not aware of a way to change the sampling mode in either the AD2 set of VIs or WaveForms set of VIs. Thank you, JColvin
  6. JColvin

    basys 3 WiFi usage

    Hi @Dom_123, I would probably recommend dropbox or something similar since the people who manage the server side of things over at Digilent don't want to increase the file size options for uploading to the forum. I do have another thing that we can do to test the HYGRO functionality; mostly I added a function to the demo code that reads the device ID of the embedded chip in the Pmod HYGRO since that will be a constant value and should (ideally) help point towards where the issue might be. I have attached the 3 relevant files so if you could replace the main.c in the application project (under it's respective source file) and PmodHYGRO.c and .h files in wrapper_hw_platform (drivers -> PmodHYGRO_v1_0 -> src) with the their respective files (or at least the contents), save the changes, and then relaunch the application on the hardware (after programming the FPGA with the bitstream). What you should see in the serial terminal is: "DevID: 0x1050 is devID" followed by the temperature and humidity data on each line. Thank you, JColvin PmodHYGRO.c PmodHYGRO.h main.c
  7. Hi @Jaraqui Peixe, Unfortunately, Digilent does not have the ability to obtain these licenses for you with regards to Xilinx negotiations. I do not doubt that the Spartan 3E Starter Boards you have are as good as new and work as such, but the reality is that last variant of ISE 14.7 that could support the FPGA chips on the Basys 2 and the Spartan 3E (both over 10 years old), was released by Xilinx back in 2013, so active support on these boards is limited as the required software will not install on newer OS's (at least the Windows variants anyway). As @xc6lx45, it is possible to make it work though. What I would probably recommend is looking into the newer 7 series boards, such as the Basys 3 (the most similar to the Basys 2) or if you would want access to more memory than is provided in BRAM, both the Arty A7 and the Nexys A7 have on-board DDR memory. All of these boards work with Microblaze and are supported by the free Vivado WebPACK from Xilinx (which is license-free if that is a factor for you and includes Microblaze). Naturally, there is no guarantee that the Vivado software that supports these Artix 7 FPGA chips will become end-of-life'd, but I can at least say from Digilent's end that I have not heard of this happening in the near future. Thanks, JColvin
  8. Hi @James783, What formatting does your 64GB SD card use? From my understanding the SD library (which is provided by the Arduino IDE) only supports the FAT16 and FAT32 formats, which if I recall correctly isn't the format used on most 64GB cards. Thanks, JColvin
  9. Hi @aeon20, As zygot surmised, the design is not driving UART; I looked through the tutorial you were going through and evidently we forgot to explicitly add the step in the Microblaze subsection to add in the AXI Uartlite IP block; it is referenced a few other times later in the tutorial (and clearly expects you to have it). I'll make sure this gets added in to the tutorial today. What you would need to do to correct this is to add the USB UART block to your design from the board tab of your block design (same location as where you got the system clock in section 4.3). To ensure everything gets connected correctly, I would recommend starting fresh since Vivado doesn't necessarily "fix" connections between blocks. You can add the UART block before or after you add the Microblaze IP (though before running "Block automation") Let me know if you have any questions about this. Thanks, JColvin
  10. JColvin

    basys 3 WiFi usage

    Hi @Dom_123, I created my own separate project using the Basys 3 and Pmod HYGRO and was able to successfully receive accurate data. We are looking further into your situation to see what could be different, since the data pulls from a register that the read function sends to. Thanks, JColvin
  11. Hi @Jaye, I believe attila responded to your other thread, but based on the supported operating systems for WaveForms (link), I do not believe you will be able to successfully use the Analog Discovery 2 with a Windows 2000 computer. Perhaps it is possible to get it working, but we do not have the hardware to test this for ourselves and I do not believe there are any plans to make it work. I'm sorry I could not be of more help. Thanks, JColvin
  12. JColvin

    basys 3 WiFi usage

    Hi @Dom_123, If you understand the block design errors, does this mean that you have started a fresh project and resolved the path errors to the Vivado Library folder? Thanks, JColvin
  13. Hi @zygot, Thanks for the suggestion for the aforementioned HowTo section; we have a number of resources on our Wiki (reference.digilentinc.com for those who don't know the url) but we can create another section on the forum that helps direct users to those materials. Thanks, JColvin
  14. Hi @Kimlorentz, With regards to your first question, are you just trying to run WaveForms on a tablet? What sort of tablet are you attempting to use? Neither of the VI sets for WaveForms (the AD2 set and the WaveForms set) can do everything that WaveForms and WaveForms SDK can do as the LabVIEW VIs only implmented a subset of the features. Between the two of them, I would recommend using the WaveForms set which is done with LabForms, which has a nice Instructable on it here. Thank you, JColvin
  15. 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
  16. 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
  17. 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
  18. 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
  19. 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
  20. 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
  21. 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
  22. 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
  23. 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
  24. 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
  25. 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