• Content Count

  • Joined

  • Last visited

  1. Good Afternoon @AndrewHolzer, Your last response has been very helpful. I was able to view the messages and data being sent through WaveformsLive on Google Chrome browser. Just to clarify something in your last post, the only way to tell when the data buffer is full and ready to be read (for the osc instrument) I have to keep requesting a "read" and then check the response message and interpret the status? Would there be any way to assign one of the I/O pins to go high or low when the buffer is full and ready to be read? Also, if you can explain to me how to de-interlace it (was not familiar with this term, but found it originates from TV signal processing) and extract the data points (time vs. voltage) that would be great, as that is very important for me. Thanks again for all of your help. Best Regards, herg
  2. Hey @AndrewHolzer, Thanks for the information. I will try what you have suggested above and get back to you. Regards, herg
  3. Hey @AndrewHolzer, Thank you for your help, I am very impressed with you and your company's speed and quality of responses thus far, and I completely understand. I look forward to your response and being able to move farther ahead with my project. Best Regards, herg
  4. Hi @AndrewHolzer, Thank you for your reply. I have successfully established serial communication with the OpenScopeMZ using PuTTy, and have been able to send commands for parameter changes and then read the parameters that I changed back. As a side note and for others trying to access the OpenScope in a similar way, I was able to find this file: https://forum.digilentinc.com/applications/core/interface/file/attachment.php?id=7554 Please note, when you click on this link it downloads an .htm file that contains a list of Statuscodes, some of which I came across when communicating with the OpenScope via JSON. As for what I would like to use in the OpenScope instrumentation: -setup the 2 oscilloscope channels -setup the trigger and arm it for single or continuous run (depending) -then read data back Questions that I have: -How is the oscilloscope data transmitted when I request to read it? Is there a trigger pin that is involved indicating the data is ready to be read? I understand that the OpenScope only has so many samples it can store, and I was hoping to be able to pull that data out, then let the OpenScope continue sampling (free run). If this is possible, would there be any lapse in the data between the 2 "chunks" of that the on-board memory is capable of holding? StatusCodes I have encountered so far: 2684354592 - InstrumentNotConfigured 2684354589 - InstrumentNotArmed 2147483673 - TRGUnableToSetTrigger I am having trouble setting the trigger and reading data back. When I send the command to "read" oscilloscope data back i get the "TRGUnableToSetTrigger" error code. Any documentation or help you can provide will be very much appreciated. Thank you.
  5. I am working on a project with the hopes of interfacing with the OpenScopeMZ via serial communication, to send parameters to the oscilloscope function and read the data back. With the end goal being direct serial communication with the OpenScopeMZ (bypassing the FTDI serial-usb converter). It's been difficult finding documentation on how I might be able to do this. I have read through the OpenScope Protocol https://reference.digilentinc.com/reference/software/openscope/communication-protocol and see that it uses JSON to communicate, which I am not previously familiar with but have been doing my best to read up on it. Currently I have been able to connect to the OpenScopeMZ via USB and Putty, and I accidentally managed to bring up the following dialogue: The "Unsupported option, please try again" came up after I tried to paste the command to put the OpenScopeMZ into JSON Command mode into Putty with the following code Then I just pressed the '1' key and the following response came up: I have the OpenScopeMZ working with WaveForms Live and am using a baudrate of 1250000 to communicate via Putty. How can I send the JSON commands documented in https://reference.digilentinc.com/reference/software/openscope/communication-protocol to the OpenScopeMZ? Also, any information that might help me to utilize the oscilloscope functions (set parameters, trigger, and read data) would be greatly appreciated.