Jump to content

bryan78

Members
  • Posts

    42
  • Joined

  • Last visited

Posts posted by bryan78

  1. When I am using the various protocols like UART under Logic, I can not get it to trigger correctly when using the line 1 in device options.  If I change it to use line 2 then the device triggers as expected.   I am not exactly sure what the difference in functionality between the 2 memory setting but the first just doesn't seem to work correctly and that is the one it defaults to when starting a new workspaceimage.thumb.png.ad7a5f15ec215351bd7c36f944e29eca.png

  2. 13 hours ago, attila said:

    Hi @bryan78

    ADP5 is VirtualBench for which I cannot change the firmware.

    Is there a way to use digital input of the digital discovery?  Thanks

    Never mind,the counter already works in the digital discovery under the Logic analyzer.  Just wasn't in your list of supported devices.

  3. Is there a way to have the sweep go to and from a start and stop frequency instead of wrap around?  I have tried accomplishing it in a script but I am relying on setting the frequency time and using wait() to switch start and stop frequency.  This leads to un-smooth transfers or the possibility the timing is a bit off and it wraps around before stopping. 

  4. On 3/18/2022 at 3:59 PM, attila said:

    Hi @bryan78

    You could use the Script tool to print or log measurements to file.

    DMM.run();
    while(wait(2.0)){ // every 2 seconds
      print(DMM.Measure.value)
      //FileAppendLine("~/Desktop/log.txt", DMM.Measure.value)
    }

    image.png.c9459c185b2b51b22a8944fa988235e4.png

    I came back to this one once again.  Is there any chance in the future of adding an export or log to file option in the gui?

  5. 10 minutes ago, attila said:

    Hi @bryan78

    In newer versions the SPI transfers can automatically control the CS, so there is no need to use start/stop.
    My intention was to make it backward compatible... start/stop will be fixed in the next version.

    image.png

    One other question about the scripting.  How do I switch back and forth between protocol reception and logic analyzer inside the script?

  6. Just now, attila said:

    Hi @bryan78

    In newer versions the SPI transfers can automatically control the CS, so there is no need to use start/stop.
    My intention was to make it backward compatible... start/stop will be fixed in the next version.

    image.png

    Ill try removing them all.   I spent a day on it until I figured out I could get it to work by setting active state opposite and somewhat works.  Glad I am not loosing my mind.   thanks

  7. in the Discovery2 when I run the example SPI script, it doesn't look. the Stop() is releasing the chip select.  Also to accomplish this I have to make the protocol setting opposite of what I am expecting.  I think the Stop and Start function are reversed???

    image.thumb.png.1d5d54a1a6c8022bfb2ba048c60e6aa2.pngimage.thumb.png.0091d62d8f05b84f14205899b8750ead.pngimage.thumb.png.81585833f136895ca37719e4ea679b4e.png

  8. Thanks for the latest feature.  May not be possible and also preference, but may be better if it latches the state until next check.  So it is a tone instead of constantly beeping.  Really like that it was also added to the voltages also, thanks.

  9. It would be nice to have a feature to output a differential signal to replicate rs485.  I find myself often having to generate a pattern on one pin and then the inverse on another to drive a differential signal.   It would also be nice if this was available under protocols.

  10. 7 hours ago, attila said:

    Hi @bryan78

    There is no such option yet, but we can add it.

    image.png

    That would be great.  Keep me from having to look up.  If you are able to add that can you also add the inverse, break detection.  So beep either for good continuity or set to beep when open based on adjustable values. Thanks

  11. didn't want to flood the forum, just wanted to say thanks for jumping through some hoops to get SPI and I2C going for this.  Confused myself when testing because it took a second to realize you had to use the static IO lines for driving the signals. It looks like only single and dual spi are available, couldn't select the other data lines for quad.   Any other features you can add to the adp5250 with some creativity is greatly appreciated.  Could it be possible to replicate a sensor or custom script for it also ?  Just that next step would fill the gap in what its missing.  Wish we could just use patterns on it :)

  12. On 6/23/2022 at 11:31 AM, attila said:

    Hi @bryan78

    The 'Repetition' channel/signal option is not available for Digital Discovery. Without this the pattern is repeated while the Pattern Generator is running.
    The disabling of this option will be solved in the next version.
    The next version won't list disconnected ADP5250. With the current sw version uncheck the Filter/Remote option.

    is repetition setting option possible on the analog discovery2?  I hate when using the feature on the DD or 3450 and then breaks if I go to the ADiscovery 2,  thanks 

  13. 7 hours ago, attila said:

    Hi @bryan78

    In Custom, Script and API the Select is software controlled so the timing is around 1ms.
    With Sensor a custom pattern is built including the select signal with such timing:

    image.png

    Here is what I am gettingimage.thumb.png.c75a839eb54ecd6359275e79459c10c8.png

    I think I got it,  the delay goes away when moving the functions to loop instead of initialize.  Is there a reason for this or documentation explaining it?  thanks

  14. When writing scripts for the SPI protocol, there is a long delay of over 1.5mS from chip select "Start()" to the clocking out of data.  is there a way to drastically reduce this?  It breaks the way an FPGA is expecting the data

×
×
  • Create New...