JColvin

Administrators
  • Content Count

    3019
  • Joined

  • Last visited

  • Days Won

    93

Posts posted by JColvin


  1. Hi @catphish,

    I took a look at the possible build list for the Arty S7 and it seems that the Piecemaker board is a build option for the two versions of the Arty S7, which I was surprised to learn. The datasheet that I am looking at the for the Piecemaker DDR chip (link to datasheet) seems to say in some places that it will work with either voltage (such as in the description on page 4 and page 11) but the list of the parts list on page 5 seems to say only one particular part works on 1.35V.

    However, we have one of these Arty S7 boards with that same PMF511816EBR-KADN chip and we verified that it works correctly and measured the capacitors that it runs at 1.35V. I have reached out to our design engineer for this board to confirm this though.

    Thank you,
    JColvin


  2. @zygot no problem, I'm glad I could help out.

    For others reference (just in case there are other situations where the pdf displays differently than the two situations mentioned on this thread), this is what I see on page 3 of the schematic in my Firefox browser on my Windows 10 machine:

    Thanks,
    JColvin

    Cmod A7 pg 3.png


  3. Hi @zygot,

    So I can ensure the correct schematics are available, which current schematic are you referring to that doesn't have these details? The current version that I am aware of (Rev B on it's Resource Center) shows all of these details on the 3rd page. Or am I misinterpreting what you are saying?

    @eric_holtzclaw, to confirm, yes changing out the clock chip will cause the USB interface to break. There is a location where you can provide an external oscillator on IC4 (intended to be 100 MHz), though you would need to remove R80 so that it and the USB clock aren't interfering. Otherwise you can always using the clocking wizard to create a PLL to create your 32 MHz signal if you don't strictly need an external source.

    Thanks,
    JColvin


  4. Hi @mossygreen,

    My understanding (I don't have a Mac to confirm this) is that you should be able to click on the Apple icon on your screen and then select the Software Update option. Otherwise, I would get the FTDI drivers (what the OpenLogger uses to communicate) directly from the FTDI website here; you might need to uninstall the existing drivers first to help facilitate this.

    Let me know if you have any questions about this.

    Thanks,
    JColvin


  5. Hi @tomas61,

    When the experiment is running, you can use the mouse scroll wheel to adjust the settings in the Arbitrary WaveForm Generator, though each setting will jump to the predefined settings that you can see in each of their dropdown arrows. Additionally, you can change form the Simple view to Basic view (image attached) to go the style of the original WaveForms.

    Let me know if you have any more questions about this.

    Thank you,
    JColvin

    WaveForms Basic view.png


  6. Hi @amamitof7am,

    I do not think the Analog Discovery 2 will be visible on NIMAX. None of the Digilent staff have used the Analog Discovery 2 with LabVIEW 2019, as we have not worked on this since late 2016. What I have seen in this thread is that the Digilent WaveForms VI set is compatible with LabVIEW 2017 though the AD2 toolkit was not compatible with it. Beyond following the Instructables that demonstrates running it on LabVIEW 2016, I'm not sure if there is anything else that can be done to get it working correctly.

    I'm sorry I could not be of more help.

    Thank you,
    JColvin


  7. Hi @wimtormans,

    Digilent did make the LINX driver. However, no work has been done on it since late 2016 and there are not any plans to update the LINX 3.0 driver for Raspberry Pi 3.0 deployment for newer versions of LabVIEW, so that particular functionality is only compatible with LabVIEW Home 2014.

    Thanks,
    JColvin


  8. Hi @mossygreen,

    They let me know that they don't know why there are two device listings showing up for the OpenLogger; when they test on the Mac machine that they have only a single set of tty and cu devices. With that in mind, their only guess at this point to help with this would be to try updating the device drivers; they realize this isn't much help but it's their best understanding of the situation at this point.

    Thanks,
    JColvin


  9. Hi @mossygreen,

    I talked with our firmware engineer more familiar with the OpenLogger and they let me know that they have been unable to recreate the Access-Control-Allow-Origin errors or the broader issue that you are experiencing.

    Are you using the localhost version of WaveFormsLive (or how are you accessing WaveForms Live)? It looks like you are attempting to do this through Safari, but I'm not certain. Additionally, the original URL you posted has mixes of the OpenScope and the OpenLogger, which is in accurate so the when the you attempt to update the firmware the URL the app figures out is wrong (hence why the process is failing). Could you update the offline build (the zip file for it is here) and then try updating the firmware? There are some details on how to do this here.

    Additionally, to confirm based on what I am seeing, you are connecting the OpenLogger to your iPad? Or am I misinterpreting that entirely?

    Thanks,
    JColvin

     

     


  10. Hi @joniengr081,

    You should be able to attach files now as part of a reply to a thread; you were in a different member account type since you had created an account but had not posted anything within a month or so of creating that account (this is done as an attempt to help prevent any bots from just waiting until their account is "old enough" before attempting to spam).

    I apologize for the confusion.

    Thanks,
    JColvin