Bruce Boyes

  • Content Count

  • Joined

  • Last visited

  1. Can do. We just received another AD2, so we could test on a whole other PC with different cable and different AD2. This PC is using the cable which came with the AD2. We have a full electronics shop with stereo microscopes etc so can give it a good look. And just to be clear, this PC with the 0xA error (what does that mean exactly?) is a completely different PC from the Ubuntu system with the 0x2 error. Thanks for the reply. We'd like to get this tracked down. We were hoping to use two AD2s as our main remote logging devices. Linux is highly preferred because of all the junk in Wind
  2. Just now there is a new Comm error: 0xA, this is on a ThinkPad Yoga 11e with Win 10 Pro, one instance of Waveforms 3.8.2 is the only application open. AD2 is in option 2, only the Scope is open. Just viewing, not logging. What is error 0xA? This is a deal killer if this happens while the system is unattended since all operation ceases and there is no recovery without a visit to the field site. FYI I have Windows auto update turned off, so it will not download or install without my permission, so that is not the issue here. I have sleep turned off, and just now in addition turned
  3. Thanks! I understand your explanation. It does sound like some FIFO control error. That would be great if you could fix this. Leaving a headless Linux system for remote logging is a lot more practical than Windows... in all other experience with USB on a small variety of Linux PC and desktops, I find Linux does a much better/faster job with USB devices, especially development systems where I am downloading new code maybe dozens of times a day or loading test code into 250 new systems. So I am really surprised that in this case, on mainstream Intel hardware on Asus motherboard, USB is worse und
  4. Agreed timeout would not seem to be the issue here... AD2 also has some USB data loss issue with Linux on Raspberry Pi... any connection? When this connection error occurs, what does it really mean (handshake lost, data CRC failed, etc) and what does the software do? Should I expect any better result under Windows 10? Is there any hardware data I can provide to help? Any logging of detailed error information? Every time this ERC 0x2 communication timeout error happens, I can always reconnect by clicking in Waveforms, so apparently the hardware is OK at some level... so why can't WF a
  5. Here I'll keep a running total of what I have tried and what worked or didn't. I have to find a stable solution or quickly switch to other hardware. We are scheduled to log in the field well before the Christmas holiday, as soon as we can be ready. In our real application, trigger events are expected to be very infrequent (perhaps not even one per day) but obviously if USB connection to the AD2 fails, and WF just halts, we have failed the whole acquisition attempt. AD2, Ubuntu 18.04, Asus UN62, Intel Core i5, test signal asserts every 100 msec, holdoff 0, (OpenScope MZ also running
  6. Did that. No better. It is saving each triggered acquisition and it fails after 500 to 2500 events, even with holdoff of 1 second (so not much data transfer per second). I had it in Option 2 (16K Samples) but had time set for only 8K, it still failed.
  7. Hi, trying to get new OpenScope MZ (from the original KS, just now getting around to this!) working on Ubuntu 18.04 desktop system. The OpenScope MZ getting started instructions did not work for me. Here's what did thanks in part to @wyojustin Installed digilent-agent but it does not show up in task bar Try to execute digilent-agent from command line. That worked. Plugging in OpenScope MZ to USB has no effect http://localhost:42135 gives a 404 error Try putting in chrome address bar. That works. Now I can start the firmware update, etc
  8. How to crash Waveforms at least under Linux. Have not tried Windows yet open a new workspace Select Scope View Logging In the filename dialog, enter "[ddhh]-[" ahead of the existing "acq####.csv" text. An underscore also is OK. It's the 2nd '[' that seems to be the problem Crash! and application closes screenshot shows just about to enter the '[', I couldn't capture after that because of the crash. My intent was to enter something like [ddhh]-[mmss]. I managed to do this by entering first a [ddhhmmss] then inserting other chars in the middle. Ultim
  9. Perfect! Thanks. The Scope trigger output located in Waveforms - Options was not obvious. It's not mentioned or linked in the Help Oscilloscope - 2.Control - Source.
  10. Hi, and thanks for the support so far. After a lot of experimenting and reading the help, I'd like to understand the "envelope" of possible triggered, repeated, logged acquisitions, which can run unattended for days or weeks. We need to leave a system in an inaccessible location and log at least 4 analog channels with at least 100 KHz sample rate, for a time of at least 100 usec after the trigger occurs for each triggered event. We believe these events have a time frame of 5 or so 60 Hz cycles, so that's 85 msec post-trigger and we'd like a cycle or two (16 or 32 msec) of pre-trigger. These ev
  11. It ran all night with the mode of 8192 samples, and with system keyboard and screen locked, so any autosuspend issues didn't surface, but I'll look into that. I think I only saw the problem in 16384 sample mode: is that information helpful?
  12. It's a pure Ubuntu install on a desktop machine, Asus UN62 box. Different hardware entirely. Just got another such error on a different USB port.
  13. Hi, is there more info somewhere on AD2 trigger out? I found this topic: AD2 trigger out pulse length and posted a question (then realized it might not be seen since that is an old topic, and I couldn't see how to delete or move the post) there but I can't figure how to get to the screens shown in that thread. I looked in the online help and manual... thanks.
  14. Aha the Device Manager has to be set to a mode which supports "patterns". I had the AD2 set to the only option with 16K scope sample depth, since that is important to us... I would like to trigger a 2nd AD2 module when the first one triggers, and also trigger an external device (Dataq 718) when the first AD2 triggers. This probably belongs in a new thread:
  15. Today WF has thrown two of these Errors. I am using the USB cable which came with AD2, WF version as shown, Ubuntu 18.04. Just started using AD2 on this Ubuntu machine. I'm switching USB ports. Have not seen this on Windows10 notebook with same device and same USB cable. Any ideas? Forum search didn't find this error mentioned. Maybe something peculiar to Linux? Happy to send any further details or logs if you tell me where to find them.