sudharsan.sukumar

Technical Forum Moderator
  • Content count

    35
  • Joined

  • Last visited

  • Days Won

    1

sudharsan.sukumar last won the day on February 11

sudharsan.sukumar had the most liked content!

About sudharsan.sukumar

  • Rank
    Advanced User

Profile Information

  • Gender
    Not Telling
  1. OK so what's happening is the OpenScope is losing power while trying to calibrate and then automatically restarts. This is why there are connectivity problems and also why sometimes WFL can read the storage locations and sometimes it can't. While the OpenScope is starting up, it will not be able to respond to the commands. When the OpenScope (OS) starts up, LD5/LD6 flash because the firmware is printing out the OS info. This also explains why WFL is complaining about the calibration falling back since when the OS restarts, the calibration is reset if it wasn't saved. Further proof this is the issue is that when the OS restarts, the Digilent Agent is no longer able to talk to the device and you'd have to release it or restart WFL to talk to the device over the Agent again. I would try a different USB cable and maybe a different power supply (I use the one I have to charge my phone). If you still can't get it to calibrate, it sounds like you might have received a faulty OS and we'll send you a new one It sounds like you're connecting the wires correctly, but as a sanity check here's a picture of my set up. Thanks for your patience debugging this! Very helpful write-ups made it easy to figure out what was happening. -Dharsan
  2. Hey I got to look at the logs. Definitely looks like there's something going on when the OpenScope is calibrating. I talked to Keith who wrote the calibration and he said this: "Look at the LEDs while calibrating. It takes about 30 sec to calibrate, for about 28 seconds the RED LED should be solid ON. If the RED LED goes off after about 10 seconds or so, calibration is failing. This would happen if DC is not tied to OSC properly; OR IF some other circuit type PCB error on the feedback circuit; which might slip through our manufacturing test." Edit: More info: "The blue LED should be solid ON while WiFi is up and running, or blinking if not connected to a network, but should be OFF during calibration. When he does the save, is the Blue LED blinking or solid ON? if not, the MZ probably either crashed (LEDs stuck in position they were when crash happened), or asserted (All LEDs ON). This could happen if I get a math error (divide by zero) which could happen if one of the feedback circuits are not working and ALL values are the same when reading the ADCs, I'll probably get a divide by zero fault and crash the MZ." WIll you try that out and let us know? If that's not it, I have a couple of things we can try to figure out what is going on. -Dharsan
  3. This sounds like the device is not responding to the commands WFL is sending to list storage locations and save the calibration. What browser and OS are you using? I just uploaded 1.4.0 and calibration seems to work. Like Sam said, I'd update the Agent and then remove and re-add the device to WFL and make sure the firmware version displayed on the device configuration page is 1.4.0. If you're still seeing issues after that, go to the main page (Device Manager Page) and then open the side menu and click settings. Open the advanced menu and click change console log and select "Local Storage". This saves debug logs to your local storage. Now, try and calibrate the device until you see the error. Once you run into the error, get back to the settings page and under advanced click "Export Log". This should download a .txt file that contains some of the debug information we collected and should give us some info on what is actually happening. Also, the local storage debugging will only run during the session you enabled it. If you refresh WFL and still want to store the debug info, you'll have to go back to the settings page and set it to local storage again. Thanks, Dharsan
  4. That is the correct current behavior. We're looking into changing this if we get more feedback like yours! -Dharsan
  5. For the LEDs, it sounds like you're probably just on old firmware! As or WaveForms Live (WFL), what OS and browser are you using? We recommend Chrome, but it should work with Safari, and Firefox. Follow the instructions to add an agent to WFL and then upload the latest firmware. Here's a link to the getting started. If you're still having issues with WaveForms Live, I'll be happy to troubleshoot it with you. -Dharsan.
  6. Waveforms Live was updated. I recommend removing your existing device and adding a new device because there have been a couple of device specific changes. -Dharsan
  7. We aren't exactly sure what the sample rate range would be possible yet since we're still working on some finishing touches before tackling the improved datalogger.
  8. Yep most of these things are fixed. I haven't pushed a new build to waveformslive.com in a while. I'll let you know when a new build is pushed. The weird stuff you're talking about with run and the analyzer channels has been fixed. Try to see if you can replicate it when I post a new build.
  9. Here we go. Now when a channel is selected the series anchor is highlighted. Analyzer channels now have a channel label on them. As a side note, when there is a new build the min frequency for the simulated device will be 6Hz since that is the min frequency for the OpenScope and the simulated device is a simulated OpenScope. Once we have more devices that follow the OpenScope Protocol, we can have more simulated devices. -Dharsan
  10. I could do that. The only problem might be that it looks too massive on phones. Right now what I'm going to do is make it so that the series anchor gets a white outline if it is the active channel. I'm also going to add a label for the analyzer channels so you know which is which. -Dharsan
  11. The UI indicates which Osc channel is selected by changing the y-axis label. You'll notice this if you toggle between Osc 1 and Osc 2. What I was saying earlier is that the analyzer channels don't update the label because it doesn't really make sense to show the units on something you know toggles between 0 and 1. So what I thought you were saying is that there needs to be a better way to tell which analyzer channel is selected (if any) and I agree with that because it is confusing. As far as shift + lmb is concerned, you're right that you can't tell when an analyzer channel is selected so some options I thought of are: 1) Remove the ability to use shift + lmb to move analyzer channels 2) Come up with a way to display which trace corresponds to which channel (which is what I mentioned in my comment above and also what James is suggesting). Further, if you can use shift + lmb to move the analyzer channels you need to know which one is currently selected. 3) Update the axis label to show which analyzer channel is selected and show the units for the channel (which like I said above may be a waste since you know the value is 0 or 1). Hope that makes sense, Dharsan
  12. I think I see what you're saying. There needs to be a better way to determine which logic analyzer channel is which (whether that is updating the axis label or some other method). Thanks for the feedback! -Dharsan
  13. You can see the selected channel based on the axis label on the left side of the chart. You can click in the control box (or any of the buttons inside of it) for either Osc 1 or Osc and that channel will be set as the active channel. When you grab the arrow (we call it a series anchor) that also sets the corresponding channel as the active channel. The analyzer channels aren't set as the active series when moved since they are only ever 1 or 0 and thus seeing the labels isn't as useful as it is for the Osc channels. You can still grab the series anchor to move the analyzer channel where you would like it.
  14. Yes I misspoke about the 100 samples per division. The samples per division is the pixel width / 10 like in the 1920px example. Your counting peaks method is a little bit off because there is some aliasing when displaying the data due to the fact that we're limiting the sampling frequency depending on your time base. This is the reason you're getting the interesting looking waveform in your second picture. The minimum sampling frequency for the simulated device is 3052Hz (which I think I got from the OpenScope in the very early days but that value has changed since then). I've just updated the minimum frequency to 1Hz so that should give you more room to work with (this change is still not live on waveformslive.com). The minimum frequency is also the reason you were getting buffers shorter than you were expecting (and also why the incoming buffer was not 2x the window width). Tips and tricks for WFL that should help you manipulate the buffers you get: 1) When you use the mousewheel to zoom, it zooms on your mouse position (like Google Maps). This is useful if you want to zoom in on a specific point of the buffer, you can hover your mouse over it and zoom. 2) You can also press the middle mouse button down and drag to highlight an area. When the middle mouse button is released, the chart fits to the selected area. The end result is that you can highlight what part of the buffer you want to view. 3) You can hold shift and left click and drag to pan the buffer up and down. 4) If you want to pan quickly, you can use the timeline view at the top to pan. You can also click on a specific part of the buffer to center the view at that point in the buffer.
  15. 1) I'm going to use 1 ms/div for the example. The buffer size is set to two multiplied by the chart width in pixels. Two times because we want a full window and then half a window on either size of the current window so users can pan. The sampling frequency is calculated by determining the sampling frequency that would cause 100 samples to fit into one division. For instance, if your window resolution is 1920px then each div will need 192 data points. If your time base is 1ms/div then that means you need 192 samples / ms. Thus the sampling frequency would be set to 192000Hz. The expected time in seconds to complete is then (bufferSize / sampleFreq) which in the example would be 20ms. The actual time it takes to get a buffer back is actually longer for a couple of reasons. 2) If you click a specific measurement (like frequency) it will pop it out to the chart next to the refresh button. You can select up to 4 measurements to pop down to the chart. You can then click the refresh button and that value will be updated without having to open the Math Menu again. If you want to remove a measurement from the chart, just open the math menu and click the measurement you want to remove.