JColvin

Administrators
  • Content Count

    3933
  • Joined

  • Last visited

  • Days Won

    150

Everything posted by JColvin

  1. Hi @aparna, It's difficult to say on the accuracy. The main source of error will be from the module itself. The datasheet for the MMC34160PJ magnetometer claims header accuracy within 1% (if you use their proprietary software/algorithim as clarified on the second page of the datasheet), though with the Set/Reset functions to help eliminate the 1 degree in alignment error, the 2% in transverse sensitivity, and 3% error associated with temperature drift, you should be able to get reasonably close (though magnetic fields in your environment will definitely affect the heading. In terms of the math itself, the atan2f is from the standard c library that is included (math.h). You can see what standard C libraries Xilinx uses in their Xilinx Standalone Library Documentation. Pi is rounded/estimated to 5 decimal places but that is a common practice to help make the calculations go faster. Thanks, JColvin
  2. Hi @Cameron Tacklind, What range of pulse width are you using for the DMC60C? I believe the CAN mode has it's own command that it needs to start, but I have reached out to another engineer to get their thoughts on this. Thanks, JColvin
  3. Hi @J995, It sounds like some of the ICs were probably damaged if you're not getting any voltage across the on/off switch when it is switched on. If the board is still be detected by the host computer but not Adept or Vivado, then EEPROM was probably erased or corrupted though fixing that won't matter much of the rest of the board does not turn on. I presume when you say testing the switches that control the on-board LEDs you are referring to the Out-of-box demo for the which is loaded in the QSPI flash and have the mode jumper set to QSPI? Depending on when you got the board it could still be under warranty. Otherwise, perhaps it was just the fuse that was damaged which you can test with a multimeter; you can find some more details about this in this thread: .https://forum.digilentinc.com/topic/4788-protection-diode-and-fuse-damage/. Let me know if you have any questions. Thanks, JColvin
  4. In terms of priority, that'll depend on how LabVIEW processes it since it runs things simultaneously somewhat? I'm not sure how it works on those finer details. The main catch is that while the stop VI will complete, I imagine that when the now processed stop condition flows through the yellow error wire (presuming that is where it is stored), LabVIEW will not further process that data until DWF MSO Read.vi is completed, so unless there was a way to interrupt that flow, it may not work.
  5. Hi @Ravi Kumar, My understanding is that Serial1 will need to be run at 1250000 baud rather than 115200 baud because 1.25 MBaud is what the OpenScope MZ has been setup to run at in order to correctly receive characters. I believe it is possible run it at slower baud rate though the OpenScope material would need to be adjusted accordingly. Thanks, JColvin
  6. Hi @dave123, The .xpr file is the 2018.2 .zip releases for those projects; the specific links to their releases are available here: https://github.com/Digilent/Cora-Z7-10-Basic-IO/releases and https://github.com/Digilent/Cora-Z7-10-XADC/releases. Let me know if you have any questions. Thanks, JColvin
  7. HI @welchs101, Yes, the WaveForms software which controls the Analog Discovery 2 is compatible with Windows 7. You can see the supported operating systems on the right-hand side of it's Resource Center here: https://reference.digilentinc.com/reference/software/waveforms/waveforms-3/start. Thanks, JColvin
  8. Hi @robert.d.lau, I apologize for not being more clear. Once you are in the developer tools for your browser, could you also click on the "Console" tab so we can see what is being logged to it? Right now you are on the "Elements" tab. I'm not sure on the name change portion, but I will ask about that. Thanks, JColvin
  9. Hi @[email protected], I am inclined to agree with you; I am not sure how you would readily provide this functionality either without changing the existing VI to accept an additional input. @attila do you happen to know how this might be done for the Digilent WaveForms VI set? Thanks, JColvin
  10. JColvin

    Analog Discovery 2

    Hi @fresh147, I haven't gotten to see if and how the Analog Discovery 2 works with LabVIEW 2020 Community Edition (I know that there are a couple of other VI sets that work with some older versions of LabVIEW). The other required software will be the WaveForms software, https://reference.digilentinc.com/reference/software/waveforms/waveforms-3/start, which LabVIEW communicates with to control the Analog Discovery 2. The communication speed with LabVIEW is harder to quantify; the main limitation is that communication with the Analog Discovery 2 occurs over USB 2.0 so loading new configurations to the device can take a few milliseconds, though it is my understanding that LabVIEW will receive all of the measured samples as intended with accurate time stamps. Again, I'm not certain how long it will take for LabVIEW to process the received data and display it (and note that the Analog Discovery 2 is not a "live data" instrument) though. Let me know if you have any questions. Thanks, JColvin
  11. Hi @[email protected], Normally, this would be done by pressing the "Stop" button once the acquisition is going. I'm not sure on the getting the two VIs to play nicely with each other, but it may be possible to add in the existing DWF MSO Stop.vi (which from the description is the equivalent of this button on the WaveForms application) that you can find in the source files for the VI (in the case of LabVIEW 2020, this is located for me in "LabVIEW 2020->vi.lib->DigilentWF->DWF MSO Stop). It should be on the function panel in Measurement I/O->Digilent WF VIs->MSO->Utility. Thanks, JColvin
  12. Hi @[email protected], I'm not a LabVIEW expert, but should your Scope Start input on your block diagram be connected to something? I'm not sure what options are available in the VI, but there usually is a manual trigger option. That's normally done via a button within WaveForms itself, but maybe there is a way to connect it to the Trigger Source. Thanks, JColvin
  13. For future readers of this thread, this was resolved during the work day on Monday April 20th, 2020.
  14. Hi @JoeJosh, That particular error is usually indicative of a drop in power on the voltage supply line as per this Xilinx thread: https://forums.xilinx.com/t5/FPGA-Configuration/Error-Labtools-27-3165-End-of-startup-status-LOW/td-p/737029. I do have some additional questions for you though. - Have you tried using a different USB cable with the JTAG HS3? I imagine this might be the case since you mentioned testing multiple JTAG HS3's, but I figured I would check. - Do you still encounter this issue if you use a different bitstream? And did the hardware design used change at all when this problem started occurring? - Are you connected to a FPGA or a Zynq? - Could you provide the output of the Config_Status registers from the Vivado Hardware Manager this can be done by running the following tcl script: report_property [current_hw_device] -regexp REGISTER.CONFIG_STATUS.* Thanks, JColvin
  15. Hi @robert.d.lau, I asked another engineer more experienced with WaveForms Live and the OpenScope MZ about this and they said that one thing to try would be to enable the console output in WaveForms Live before trying to connect to the device. Hopefully this will let us see what command is causing the OpenScope to choke. You can do this by going into the Settings page, opening the Advanced section and clicking on Change Console Log. Set this to Console, then open the developer tools for your browser. For Chrome and Firefox this is Ctrl+Shft+i. The commands and their responses, plus some other additional information will be printed in the console here as you use WaveForms Live to configure the OpenScope. Let us know what you find out. Thanks, JColvin
  16. JColvin

    CMOD S6 JTAG

    Hi @[email protected], As @Cristian.Fatu mentioned in their post on this thread, it is a header to implement the USB-JTAG solution. As for why it does not support JTAG like other similar looking headers on different Digilent boards, I do not know; it was the result of a design choice made back in 2013. Thanks, JColvin
  17. Hi @MsDh, Xilinx maintains both that page and those links on the page, but those links both work for me; here are their respective URLs: https://www.xilinx.com/support/documentation/sw_manuals/xilinx11/ism_c_mixed_lang_simulation.htm and https://www.xilinx.com/support/documentation/sw_manuals/xilinx11/ism_p_instantiating_verilog_module_mixedlang.htm. Thanks, JColvin
  18. JColvin

    Waveforms Licensing

    Hi @NathanK, Yes, you may install the WaveForms SDK on two different machines for development and deployment. Naturally, you can also do both development and deployment on a single machine, but I understand the need for developing on a more powerful machine. If you have any questions about the development or deployment process, feel free to ask them in the Scopes and Instruments section of the Forum, https://forum.digilentinc.com/forum/8-scopes-instruments-and-the-waveforms-software/, where one of the primary developers of the WaveForms software will be able to see and respond to your question. Thanks, JColvin
  19. Hi @etienne68, The cable set in link1 actually comes with two cables. One cable is a 2x6 (single 12 pin connection) to a 2x6 (single 12 pin connection. The other cable does split a 2x6 (single 12 pin connection) into two 1x6 connections. So yes, that second cable that does the splitting will allow you to use a single Pmod port for a single 2-digit 7-seg Pmod. Or alternatively, two different 6-pin Pmods on a single Pmod port. Let me know if you have any questions about this. Thanks, JColvin
  20. Hi @Steven Cornett, I apologize for the long delay since I evidently never hit the submit reply button. I think there is some confusion between a hardware platform and a board file. The board files are available on Digilent's GitHub here, https://github.com/Digilent/vivado-boards, and provide Vivado with context about what materials exist on the board and provide configurations for some parts, such as the Zynq chip. The hardware platform which Vitis uses will need to be generated and exported from Vivado. From my understanding, Digilent has not made any pre-built .xsa files for the Genesys ZU to use. This Getting Started with Vivado IPI for 2019.2 that we have will walk you through the process of creating and exporting such a file. Thanks, JColvin
  21. Ok, I have sent you a direct message with the contact information.
  22. Hi @ZzyzxOhZzyzxOh, The original @ZzyzxOh account can still access the Forums and has no restrictions placed against them; all of the forum accounts are separate from the store accounts though. Please let me know if you are still unable to access your account and I can work with you to restore access. I personally have never seen any alternate locations to download the Digilent WaveForms software that are not Digilent hosted websites, but if you know of one, please let us know so I can pass that on to the product manager/legal team as appropriate. For what it's worth, you are the first person that I am aware to request MD5 verification for the WaveForms software (or any Digilent made software) but I will pass your request on to the appropriate people at Digilent. Thanks, JColvin
  23. Hi @WojtekSkulski, We do not share this exact configuration, though if you wish I can put you in contact with the appropriate representative at Digilent with regards to licensing our FTDI solution. Thanks, JColvin
  24. Hi @sramelyk, My understanding is that while the Analog Discovery 2 can work as a vector network analyzer (sending a signal and measuring it both before and after the device under test) as that is the typical usage for it as per the documentation (available here with a default Windows installation location): file:///C:/Program%20Files%20(x86)/Digilent/WaveForms3/doc/index.html. However, the Analog Discovery 2 is not set up on it's own to measure wireless systems, nor is able to analyze a 2.4 GHz system. I will defer to @attila who is much more familiar with the WaveForms software provide any additional details or corrections that they might have. Thanks, JColvin
  25. Hi @RTC, I have moved your thread to a more appropriate section of the forum where the engineer much more experienced with the WaveForms software will be able to see and respond to your question. Thanks, JColvin