Search the Community

Showing results for tags 'protocol'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • News
    • New Users Introduction
    • Announcements
  • Digilent Technical Forums
    • FPGA
    • Digilent Microcontroller Boards
    • Non-Digilent Microcontrollers
    • Add-on Boards
    • Scopes & Instruments
    • LabVIEW
    • Other
  • General Discussion
    • Project Vault
    • Learn
    • Suggestions & Feedback
    • Buy, Sell, Trade
    • Sales Questions
    • Off Topic
    • Educators
    • Technical Based Off-Topic Discussions


  • Community Calendar

Found 8 results

  1. Can someone please point me to a manual for the Protocol section of the Waveforms software? I would like to send an I2C command over a bus but I am getting an I2C bus error. Verify the signal pull-ups error. I do have the appropriate pullup resistor however. Also, it's not clear how the interface works. A manual would be useful. Thanks, Dave
  2. Hello, I am attempting to communicate to a Pmod RF2: IEEE 802.15 RF Transceiver with a Basys3 board using the SPI protocol in VHDL. The microchip on the pmod is the MRF24J40. How do I identify the address of the MRF24J40? To my understanding, if I want to write/read a memory location on the MRF24J40, I need to send the address followed by the address of the specific memory location on the MRF24J40. Is it written on the microchip itself? The master and slave SPI modules that I am attempting to use are linked to this post. The documentation for the master and slave links are below. The specification sheets for the pmod and MRF24J40 are included as well. Master: Slave: Pmod: Interface_Specification.pdf MRF24J40: Thank you. spi_slave.vhd spi_master.vhd
  3. Emulate I2C slave

    Would it be possible to emulate a I2C slave using the digital discovery (using scripting)? If not, is this something that could potentially be added in the future, or are there any HW limitations that make this infeasible?
  4. Protocol

    Hi, In the Protocol tool, the UART tab The ´Receive to File´ and ´Save´ button generate a windows error by me. Thanks in advance, Hans
  5. Hello, I think the latest waveforms software is fantastic. However, I still have a problem with triggering, specifically protocol triggering. In the enclosed screenshot, I have a UART and OneWire and a SPI protocol decoder. If I choose Simple triggering, everything is ok, but if I choose Protocol-UART-TX-GPIO1 (UART decoder form the Protocol selection button pull down menu) then the OneWire and SPI decoders trigger-selection-arrows switch too! What I would like is that I can only choose the UART OR only the OneWire OR only the SPI decoder as suggested by te Protocol selection button pull-down menu. So I can see where I am triggering on. Am I right? or is what I ask impossible? Thanks in advance, Hans.
  6. Hi all tagging some experts @jpeyron @attila Thank you for all the help in previous questions! From what I have gathered up till now is that I cannot access the protocol analyzers since they are at the application level and are not exposed to the SDK. However in my application I need a protocol analyzer along with the analog read of the AD2 simultaneously. (attaching previous post) So my only hope is to make a custom protocol analyzer to get the logic bitstream from the digital pins along with the raw waveform data. I tried to do the same in the code snippet attached. However the program hangs at line #79 at FDwfAnalogInStatusData. And also the logic bits i have read at this point do not reflect the right logic levels. Is there something I am missing? What is the right way to get both analog and digital data from the oscilloscope? EDIT: When it is not hanging at that line the digital values i have read from the digital pins are not the right value i am supposed to see (dont see the logic stream of the signal just half 1s and the other half 0s). How does it have to be setup to ready a signal with 500K - 1MHz signal levels? Thanks in advance! Shabbir main.cxx
  7. I'm working with a sensor that uses clock stretching to tell the master when data is ready. When using the AD2 as an I2C master, the analyzer insists there's a NACK after an address somewhere, but I can't see where. The first attached picture shows a write to 0x40, ACK, 0xF1, restart, read from 0x40, ACK, then slave holds both SCL and SDA low. About 68ms later (seen in the second attached picture), the slave releases the bus indicating the data is ready. The protocol analyzer shows the correct sequence from its point of view, then shows "NACK after address" even though all bytes were clearly ACK'd. From what I can tell, I'm using everything correctly. Does WaveForms 2015 actually support I2C clock stretching when acting as an I2C master? As a matter of curiosity, you might be wondering why I chose to use an analog analyzer to view the I2C lines. That's because I can't seem to coerce the logic analyzer to behave while I was also using the protocol analyzer. Is that a software limitation, a bug, or am I just using it wrong?
  8. Hi, Is it possible to write a MDIO (Clause 45 and 22) protocol decoder plugin for the Waveforms software (preferably under Linux but Windows would also be OK). I want to capture the data using Analog Discovery and decode it. Thanks, Methlal