JColvin

Administrators
  • Content Count

    3017
  • Joined

  • Last visited

  • Days Won

    93

Everything posted by JColvin

  1. Hi @srv565, I'm not certain what the error actually is; the LabVIEW forum thread you linked with the comment that the firmware code restricting the code to only work on WF32 and Arduino Mega boards would be the most likely reason though I don't know how to readily change. I made a simple LabVIEW code setup to use the Max32 with the WS2812 VIs and stepped into and out of the VIs until I found the VI that generated the source of the error (Wait for Packet VI) though I don't know what's going wrong; it seems like one of the checksums isn't returning a proper value, but I'm not certain how that could be fixed. I have asked another engineer more familiar with LINX and the associated firmware to see if they have a recommendation on what can be done. Thanks, JColvin
  2. Hi @stunix, If both the Cmod A7 and the Raspberry Pi are being powered through an external power supply from the general source (i.e. a power strip) that should be fine. Any differences that would exist in that case should be mitigated by connecting the grounds like you described. How are you monitoring the packets being sent to and from the Cmod A7 and the Raspberry Pi? In general, I would expect that it would be a timing error based on what you described, but I'm not certain. Thanks, JColvin
  3. Hi @StuE, You can set the acquisition mode to be in a different mode than the single acquisition mode (FDwfAnalogInAcquisitionModeSet) which I believe is the default mode and will only fill up a single buffer that then needs to be read and then refilled. There are other modes such as ScanShift, ScanScreen, and Record mode (detailed more on page 22 on the WaveForms SDK Reference Manual) that would do what you are wanting. Specifically the ScanScreen mode does write to the buffer in a circular fashion, though I personally don't know the limitiations associated with reading from and writing to a buffer at the same time. Otherwise what you may want to do Record mode since that runs up to 1 MHz from my understanding ( @attila would be better able to confirm specs on this). I'm also not certain how tight your timing requirements are, but since changing the buffer size and some of the other functions aren't so easily changed, it may be worth it to just have LabVIEW call python scripts (or c based scripts, both available with samples in WaveForms SDK folder with Analog Input examples. Again, I'm not certain on your timing constraints so that may not be of help to you. Thanks, JColvin
  4. Hi @stef, I believe @attila was just showing an example of how to read from I2C since we don't know how your specific sensor is set up so we went with a more general example. Thanks, JColvin
  5. Hi @StuE, I'm not certain what what might be able to be done differently in your setup since you've stripped down the process for what you need done. What you are needing is WaveForms SDK function (which is what the LabVIEW functions call) to adjust the buffer size used by the analog inputs, though I'm not certain what the maximum buffer size is, nor do I believe this function is implemented within LabForms. The function names you would be looking for in WaveForms SDK (available as part of the WaveForms download available on it's Resource Center here), are FDwfAnalogInBufferSizeInfo, FDwfAnalogInBufferSizeSet, and FDwfAnalogInBufferSizeGet. Let me know if you have any questions about this. Thanks, JColvin
  6. JColvin

    AD2 synced with picoscope

    Hi @PEF, I don't know which threads you've looked at already, but I would recommend this thread and some of the links that are in that thread as well, so yes you can sync two or more AD2s to get more than 2 Analog inputs through the use of triggering. Correspondingly, you can probably also sync acquisitions with a picoscope as well, though as each device will have their own independent oscillators, so you'll probably need to periodically resync the two devices to help account for any phase shift that would occur. I'll have to defer to @attila on your last question about the analog and digital signals time synchronization. Thanks, JColvin
  7. JColvin

    3D Model

    Hi @aaronBe, I don't believe we have a 3D model that includes both the case and the PCB, but the case is now available for download in at the bottom of the Resource Center under Additional Resources: https://reference.digilentinc.com/reference/instrumentation/analog-discovery-2/start. Thanks, JColvin
  8. Hi @inselcontroller, That is accurate that DB0-7 is U-PD0 through U-PD7 on the Coolrunner II. Did you configure the Coolrunner II with a DEPP compatible design? This is described more in the DEPP Programmer's Reference Manual and the Digilent Asynchronous Parallel Interface (DEPP) documents that are part of Adept SDK, available for download on the right-hand-side on the Adept Resource Center. Within there, there is also a sample VHDL file for the DEPP that can be used to configure the CPLD so that it properly communicates with Adept on your computer. I also found what seems to be a complete .ucf file for the Coolrunner II on this users GitHub here which more directly answers your question about the pin assignments under the section called "Parallel Data Bus from microcontroller - Port "C" ", starting around line 297. Specifically, it looks like the pins you need are as follows: Wait is on P42, Write is on P41, Data Strobe (DSTB) is on P40, and Address Strobe (ASTB) is on P35. The .ucf and the VHDL file don't have matching names though, so you'll need to fix those as needed so they match. Let me know if you have any questions about this. Thanks, JColvin
  9. Hi @Mary Becker, Unfortunately, we do not have any further details about the conducting paths that describe the resistance and capacitance of each of them, nor a user's manual. Please let us know if we are misunderstanding what you looking for. Thank you, JColvin
  10. Hi @jasons, When you said "I haven't messed with any of the bitstream or device properties" does that mean your project has not changed or that your project has been changed an updated, but the creation process hasn't changed? In general, you may need to adding an initial delay in the beginning of the SDK code can sometimes help if the application is trying to run before all of the power rails are fully up. This can be an issue when the verbose is commented out. Could you post a screen shot of your Block design, the wrapper file and the SDK code? Thanks, JColvin
  11. Hi @pmjobin, Yes, we can make a note to the Cmod page (and other pages as appropriate) to be wary of charging only cables. Thank you for the feedback. Thanks, JColvin
  12. Hi @Yacov Cohen, Unfortunately you have the latest files that I do as I have not had the opportunity to work on this further. Hopefully I will get a bit of time to work on it a bit more this week, but I will let you know when I have made some progress on it, though I cannot guarantee that I will have the time to do so. Thanks, JColvin
  13. Hi @TestDeveloper, That is accurate in that you are not able to do the simultaneous sampling with the two channels configured as is; I asked another one of our engineers about this and they let me know that from what they recall it was originally intended to use auxiliary inputs 4 and 12, but was (evidently) changed during the development cycle. Thanks, JColvin
  14. Hi @chrisdoe, I have tagged the engineer ( @attila )who is much more familiar with the Digital Discovery hardware for this question, though since we are not in the same office, I do not know when they will get the opportunity to respond. Thanks, JColvin
  15. Hi @pmjobin, You can find a list of manufacturers that have certified Micro-B connectivity on the USB.org site here, however you'll note that the vast majority of the cables listed are type C to micro B, rather than type A to micro B, so be aware that your options will be somewhat limited (and if it matters to you) not necessarily readily available in whatever country you may be in. After some searching, I was able to find this certified USB 2.0 A to micro B cable from a Swedish based company (link), but none of us here at Digilent have tried this specific cable. I wasn't able to readily locate an Evernew USB cable that was available for purchase. Otherwise, these two other cables from Amazon (link1, link2) may work, but note that they are not USB-IF certified (nor have those of us at Digilent tried these specific cables. Thanks, JColvin
  16. Hi @hugo.gomez@ufl.edu, The engineer who normally answers these questions is on a different time zone so they may not get an opportunity to respond until tomorrow. Otherwise this thread may be of help to you since there was a driver issue with MacOS 10.9.5 which I believe you are currently using. Thanks, JColvin
  17. Hi @DCSoutherner, What version of WaveForms do you have? Most recent versions should have a Protocol tool that we have a tutorial for here: https://reference.digilentinc.com/learn/instrumentation/tutorials/ad2-protocol-analyzer/start. Let me know if you have any questions about this. Thanks, JColvin
  18. Hi @Joysondsouza253@gmail.com, I heard back from the other engineer; they let me know that the LEDs are not actually displaying a fault condition, but an undefined state which they've only seen with faulty hardware. I've sent you a PM with some more details. Thanks, JColvin
  19. Hi @Illia, I apologize for the delay. I have tagged the engineer most familiar with WaveForms SDK ( @attila )to see what they recommend. Thanks, JColvin
  20. Hi @Joysondsouza253@gmail.com, I apologize for the delay. I have asked another engineer with more experience with the DMC60 for their input. Thank you, JColvin
  21. Hi @Ilkka, I found a knowledge article form NI that recommended to decline support for the device drivers when initially installing LabVIEW and the install the drivers later. Maybe that will help you. Thanks, JColvin
  22. Hi @Ilkka, I don't have any DAQ hardware to test this, but I downloaded the NI-DAQmx 17.0 package from the NI website here (as opposed to attempting to install it from my LabVIEW 2014) but I was able to select the 32-bit LabVIEW 2014 support and it seemed to install on my Windows 10 machine without any complaints. I'm not certain what you mean by the last line of "If I use the LV2014 home bundle installation package the setup program cannot find the driver installation folder"; do you mean the LabVIEW Home Bundle can't find the installation folder or the NI DAQmx can't find an installation folder? Either way, the folks over at NI would probably be better able to answer any installation questions for their software. Let me know if you have any questions about this. Thanks, JColvin
  23. Hi @jn74, The channel 2 is probably damaged then. I have sent you a PM with some details on the next steps. Thanks, JColvin
  24. Hi @jn74, As a bit of additional information, it may be worth it to first load the factory calibration first and leave the scope inputs open/short them to ground before stating the oscilloscope or scope meter as mentioned in this thread here. Thanks, JColvin
  25. Hi @Yacov Cohen, The way you would do this would be to change the ReadRegisterValue and SetRegisterValue functions so that the final parameter in each of those functions (a manipulate CS parameter) be set to 0 rather than 1. This would force you to manually toggle the CS pin yourself which you then have more control over. What I would probably do instead is change the begin function to then accept a parameter that ends up dictating what pin the CS pin is; you'll then be able to keep all of the other functions that use the Read / Set RegisterValue functions as is since it would automatically toggle the CS pin for you. Generically the adjusted begin function would look like this: bool AD7193::begin(int newCsPin) { SPI.begin(); SPI.setDataMode(SPI_MODE3); SPI.setClockDivider(SPI_CLOCK_DIV16); AD7193_CS_PIN = newCsPin; pinMode(AD7193_CS_PIN, OUTPUT); delay(100); Reset(); } Naturally you'll also need to change the begin function in the .h file to reflect this new parameter. Thanks, JColvin