benl

Members
  • Content Count

    7
  • Joined

  • Last visited

  • Days Won

    1
  1. Oh, absolutely agree / understand that some form of decimation and interpolation is required to display the waveform (though my DSP is getting pretty rusty). The current implementation is clearly inadequate to the point of not being useful: the waveform displayed when zoomed out is a very inaccurate representation of the signal. You should at least be able to get a somewhat accurate view of the signal's envelope. The same goes for the buffer view at the top; at present it's not useful to inform on much beyond the relative position of the display within the buffer - ideally you'd be able to use it to pick out envelope changes and transients (the latter would certainly benefit from a peak-detection mechanism). In a nutshell, it'd be useful if WFL presented the signal in a similar fashion as the same data on a deep-memory oscilloscope. Ta, Ben
  2. What does the host Agent application do? I've discovered it's not needed to run Waveforms Live when connecting to an OpenLogger via wifi; I presume it's only needed when using USB connectivity? (i.e. it doesn't presently serve any useful purpose on macOS/Linux) for the OpenLogger.
  3. G'Day Andrew, Uh, so there's no way to view the recorded data? Oops. (<flashback to the Seinfeld "most important part" scene> :-) Obviously it'd be great to load / replay the recorded data back into WFL, the interface is pretty neat and I'm a fan of the browser-as-an-app-platform. In the meantime, yes, can you please provide the header? (btw, when's all this going up on github?) Ta, Ben
  4. There is some pretty messy aliasing happening in Waveforms Live's buffer view and also the main chart. For example, below is the AWG connected to channel 1, zoomed out. It looks fine on the main chart when zoomed in (though the buffer view remains full of alias artefacts). It would be great if the signal envelope was represented properly in both the buffer view and the chart, regardless of zoom.
  5. So I've successfully logged some data to SD card on the OpenLogger MZ (0.1807.0); I can download the .log file and though I've yet to try it I see the dlog utility can be used to spit out a CSV file. How can you use WFL to view the logged data?
  6. Thanks JColvin; I was able to reduce / eliminate the "fall behind" errors by reducing the sampling rate (should have tried this earlier!); I found that up to 100kS/s seems to work reliably in terms of streaming data; however interacting with the AWG at anything over about 20kS/s causes ""Could not set AWG parameters" errors. Hmm, I just noticed the official specs / FAQ states streaming over wifi at 10kS/s. So I guess this is working as expected. Also I found the firmware version info is reported in the 'Settings' page you referred to; as is the Waveforms Live version. Re. logging: setting the log to the console logs a boatload of debug level logs, not errors. Indeed, I can't actually find the errors reported via the 'toast' notifications logged to console at all in the logs when enabled.
  7. Have just started playing with the OpenLogger that just arrived. Did a firmware update and calibration via a Windows 10 VM on a macOS machine, and connected the OpenLogger to wifi, all went fine. Is wifi meant to be working? If so, consider the following as a bug report. If not, then what's the ETA looking like? OL firmware version: whatever the latest is (how can I determine this from a running device? the UI should have some method of viewing the connected device's firmware version (e.g. in device manager?)) env: Chrome Version 73.0.3683.103 (Official Build) (64-bit); macOS 10.14.4 (18E226) However when connected to the OpenLogger via wifi I see frequent errors, including - "Error Occurred Starting Or Running Acquisition" when interacting with the timebase and amplitude (i.e. mouse zooming/scrolling) - "Could not set AWG parameters" when interacting with the AWG controls, changing modes There doesn't seem to be anything in the browser dev tools console when these occur. (the console does show a bunch of warnings re. 't' plugin and a CORS policy error just on loading the waveformslive.com page, but there's nothing additional when the acquisition error occurs). Repro: 0. OpenLogger connected to wifi 1. go to http://waveformslive.com/ 2. start streaming 3. interact with the UI - scroll back and forth, zoom in/out 4. in very short order one of the above error messages pops up; at this point the UI becomes unresponsive and a page reload / device reconnect is required Occasionally the device will get itself so confused it won't connect at all (WFL reports "No response received"), and a OL board reset is required. PS: there needs to be some sort of error log mechanism, it's a real pain to try and capture the errors via toasts....