Jonboy

Members
  • Content Count

    9
  • Joined

  • Last visited

About Jonboy

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi @attila Thank you very much. You have great products and awesome support which is greatly appreciated!
  2. Hi @attila Thank you! After adding a small wait() inside loop, I now see the DIO pin changing state quickly. Out of curiosity and generally speaking, is there a minimum amount of wait time required, or recommended for the UI? I assume this might be somewhat arbitrary. And what is the minimum time the wait() will accept or what is the resolution of this parameter? I can play with this value but I would like to run with as little time delay as possible but I am curious what is achievable. Thanks again.
  3. I am trying create a test bed to send UART data across a cable using two RS485 Half Duplex transceivers. These transceivers have control pins that will enable/disable the Driver and Receiver for the desired mode of operation. In order to control the enable pins of the transceiver, I was trying to use a JavaScript to set a DIO pin high when the UART will send data, and then change it back to low so that is can receive data sent to it. My setup uses two AD2 devices connected together and when I send UART data from one device, the other device will receive this data, look for the Line Feed cha
  4. Is there an API or Software interface to the Waveforms 2015 software? I would like to use Waveforms 2015 as the interface to an Analog Discovery 2 for making various measurements but pass that data to another piece of software such as LabView, TestStand, or Python, etc. as part of a larger automated test sequence. Basically I would like to incorporate Waveforms 2015 into a larger test environment that may contain additional test equipment. I am aware of the SDK that allows for LabView and Python to control the Analog Discovery 2 directly. However, this prevents Waveforms 2015 from being
  5. Hi @attila Thank you for your support and explanations. Concatenating the sub-adress and data fields works and I am now able to read and write specific register at will. I had been approaching this from the thought that the Script tool was controlling the features of the Protocol tool. Other parameters such as the Frequency, Read Bytes, etc. were updated through the script code when executed. Since I have to set the sub-address field in the Protocol window when manually reading/writing bytes, I assumed that the sub-address must be treated as it's own parameter in the Script tool.
  6. Hi @attila Thank you for bug fix in the beta version and the additional information. This helps a lot and I am able to read data through my script which is a big improvement. I only have one additional point of confusion on how to write data to a subaddress. There does not appear to be a parameter in the write function for the subaddress like there was in the read function. How do I write data to a particular subaddress through the script tool? For example let's say I want to write a little script to work with a temp sensor (PN: TMP102) that has a device address set to 0x48 and fo
  7. I have been having difficulty getting a simple script setup in the Script Tool to read and write a sequence of registers to a device through I2C on my Analog Discovery 2. Most of the I2C configuration commands that correlate to the manual controls on the Protocol I2C window such as SCL, SDA pins assignments, Frequency, Address, ReadBytes, and WriteBytes are working properly. However, the SubAddress does not seem to be functioning properly and does not update from the script like the other parameters. Perhaps there is a different function call or parameter to set instead of what I am tr
  8. Hi Attila, Thank you for the information, it answered my question and I actually prefer to use the Script Tool instead of the custom scripts feature from within the protocol tool. I had thought I tried the Protocol.SPI.value command and I am not sure why I didn't figure this out on my own with my Analog Discovery 2 module. What I think was somewhat confusing me was that I had switched over to my Digital Discovery module because it has a higher sample rate and allowed me to achieve faster SPI clock data rates. In your example, the Protocol.Select.value = 10; corresponds to DIO 10 pin wh
  9. I am fairly new user of Waveforms 2015 and I have both an Analog Discovery 2 and a Digital Discovery that I am trying to use for some for some tests with custom scripts. I am having difficulty finding the documentation or some example code that instructs me how to assign the pins I want to use for the Select, Clock, DQ0 (write), and DQ1 (read) functions. I have two different devices I need to communicate with through SPI but there is only one "select" line. I have two transceiver/MCU nodes connected together in a system and I need to communicate with the SPI port of one node to have it