Technical Forum Moderator
  • Content count

  • Joined

  • Last visited

  • Days Won


sudharsan.sukumar last won the day on February 11

sudharsan.sukumar had the most liked content!

About sudharsan.sukumar

  • Rank

Profile Information

  • Gender
    Not Telling
  1. 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
  2. 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.
  3. Yep most of these things are fixed. I haven't pushed a new build to 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.
  4. 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
  5. 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
  6. 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
  7. 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
  8. 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.
  9. 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 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.
  10. 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.
  11. That is the correct website. Is it working now for you or are you still having issues? -Dharsan
  12. Hi Jake, What version of the Arduino IDE are you using? I know there were some issues with Arduino 1.6.8 so that could be a problem. From the error message it sounds like one of the files is missing so I would try and install chipKIT core again (uninstall it first if you can). Have you tried auto installing via URL from within the Arduino IDE? It's super easy and I wrote a blog post on how to do it. -Dharsan
  13. Hi Graether, Glad you got it working! If you have any more LabVIEW or LINX specific questions a great resource is the LabVIEW MakerHub forums! They also have some great video guides over there as well. -Dharsan
  14. Hi Graether, It sounds to me like you might not actually have the newest version of LINX. This can happen because of an outdated VIPM so make sure that VIPM is updated and then you should see the correct LINX version. To check your current LINX version, open VI Package Manager and scroll to MakerHub LINX and make sure the version is or newer. Also you should be using the 32 bit version of LabVIEW not the 64 bit just in case that is the issue. Thanks, Dharsan
  15. Unfortunately I'm not sure when the myDAQ will be available, but you can add it to your wishlist and there will be an announcement on our website when it is released! -Dharsan