Technical Forum Moderator
  • Content Count

  • Joined

  • Last visited


About AndrewHolzer

  • Rank
    Prolific Poster

Profile Information

  • Gender

Recent Profile Visitors

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

  1. For those coming to this thread at a later date, looking for a solution to the "busy" Trigger state: In short the "busy" state is a catchall for any Trigger state that isn't Idle, Stopped, Triggered, Running or Armed. In the case of the Trigger, it is usually busy due to being in a Waiting state but can be other states as defined in the OPEN_SCOPE_STATES enumeration in OpenScope.h of the firmware source (starting at line 476). The solution here is to wait for the Trigger to leave that "busy" state by continuing to send the Trigger getCurrentState commands. I suggest that an easement algor
  2. Hi @Raghunathan, I took a look into the WPA/WPA2 issue you've been having. In short, the WINC1500 driver doesn't distinguish between WPA & WPA2 from the perspective of the software, in happens internally on the chip. The OpenLogger reports back to WaveForms Live what the WINC1500 is telling it during a WiFi AP scan, which is that a WPA/WPA2 network is just a WPA network. I'm glad to hear that switching to WPA got you to the saving stage, but I urge you to go back to WPA2 instead. You are increasing the vulnerability of your local network. Instead, can you please send a capture of
  3. Hi @orquesea, There are a few things going on that I will try to explain to you, that I hope will help you get things working properly and perhaps impart some info on how WaveForms Live is working. WaveForms-Live calculates the expected acquisition time based off the buffer size and the sampling frequency. After clicking Start, WaveForms-Live waits for this period of time to pass before querying the OpenScope for available data. WaveForms-Live also calculates the sampling frequency from the time per division value in order to fit the entire acquired signal on the chart by default. If we
  4. Hi @Raghunathan, Is it possible for you to send a capture of the browser console log when you are trying to log to the SD card and get the "Error Starting or Running" message? There should be some more technical information in there that should help in debugging your issues.
  5. You will have to redo the calibration every time you program the OpenScope with the Arduino tools. It isn't preserved through the process. You can possibly re-implement the firmware upgrade flow in WFL, which will allow you to preserve the calibration settings that have been saved in flash. Otherwise you can save to an SD card as well. We intended that user calibration exist on the SD card and manufacturing calibration be kept in flash, but both can be overwritten by the user, anyways.
  6. Hi @Ravi Kumar, Thank you for supplying these log outputs as they've proved helpful in finding a solution that should work for you. I took a look through the source code and found that the OpenScope will attempt to save the calibration configuration to the SD card when using the terminal UI, which fails if you don't supply an SD card . I confirmed that I received the save error as you have demonstrated and after a small change that I'll describe to you I saw the error disappear. If you look at line 811 inside IO.cpp, you will see a call being made to CFGSaveCalibration . You can configu
  7. Hi @Ravi Kumar, I am going to need some more information from you. What version of the Digilent Agent are you running? Can you connect from your PC to the OpenScope using a terminal application (puTTY, TeraTerm, etc.) and see what the output is booting your compiled firmware, and share the results? How recent was the last time that you synced your copy of the firmware source with the Digilent repo (in case you've had it a while)? Can you enable the console logs, and see the output in your browser's developer tools when you try to calibrate your device? I am curious to see what error code yo
  8. Hi @Ravi Kumar, I am going to need more information from you in order to proceed with this issue. I haven't been able to replicate your issue unfortunately; I've made a few additions to the OpenScope source, built and flashed the device and can trigger the scope instrument. Can you tell me what Arduino version you are running? Have you made any changes to the OpenScope source code? After uploading your custom firmware, have you calibrated your OpenScope? Your answers to these questions should form a foundation from which we can build an understanding of the issue you are experiencing.
  9. Hi @frokostfredag, That's some odd behavior that you're describing there. There is one thing I'd like you to try to debug this, and that's to enable the console output in WaveForms Live before trying to connect to the device. I'm hoping that this lets us see what command is causing the OpenScope to choke. You can do this by going into the Settings page, opening the Advanced section and clicking on Change Console Log. Set this to Console, then open the developer tools for your browser. For Chrome and Firefox this is Ctrl+Shft+i. The commands and their responses, plus some other additional in
  10. Hi @ravikumargrk, Glad you were able to find your solution! If you need any further help, do not hesitate to reach out. We'd be more than happy to help out! Regards, AndrewHolzer
  11. Hi @ravikumargrk, Can you describe what else you have done to configure the OpenScope, such as trigger conditions, and anything else you are doing? Typically this error is thrown while the instrument being read hasn't idled yet. You'll need to issue another read command in that case until the status code comes back 0, with data, or a terminal error. Let me know the answers the above questions, and we'll get to the bottom of this. Regards, Andrew
  12. Hi @herg, I apologize for the long delay, and want to say that I appreciate your patience. I took a look into the source code to reaffirm my knowledge and found that things are a bit easier than I have previously described to you. I had erroneously assumed that the oscilloscope data is sent to WaveForms Live with the samples interlaced into a binary blob. In short, each channel's databuffer is a contiguous portion of the binary data, whose lengths and positions are known from the JSON portion of the response. The read response is still sent in a chunked-transfer format, and I have included
  13. Hi @alockcal, Thank you for your patience. Can you take a look at the Task Manager and see if the Digilent Agent is still running, or if there's any Digilent-associated process running? You may need to kill them here if you still run into the error when uninstalling. You may also want to give your computer a reboot if the process-killing didn't work. Do you happen to have any other Digilent devices plugged into your computer? Any other software? Regards, AndrewHolzer
  14. Hi @herg! Good to hear from you again. I am happy to hear that you found my response helpful. I want to let you know that I'm working on a description of the de-interlace process and data-point extraction. I'm going to need some time to work on that, but you can be sure that it is in the pipeline. I do want to answer the questions in your second paragraph, however. To start, there isn't currently any functionality the way you've described. The firmware would need some modification to allow the dynamic functionality you describe, or to wire that behavior into the system directly. Now, I c
  15. You can follow along with how WaveForms Live sends the commands to the OpenScope, using the browser tools to inspect the HTTP requests, since the commands are either sent to the agent if using serial communication, or directly to the OpenScope using these requests. For Chrome and Firefox, press Ctrl+Shft+i then navigate to the network tab to see these commands and the responses received to them. You can also get an idea as to what commands to send and in what order by looking at the WaveForms Live GitHub source, however, I am not expecting you to take a dive into that just to figure this out.