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 Windows 10 which cannot be shut off. You'd think this instrumentation would be easy for us to put together but it is not proving to be the case.
  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 off even checking for updates for 35 days (the most allowed). FYI in the Windows Defender history I can see it did to a scan and installed a threat definition update this morning. I don't see how to turn checking for those off. But that alone I would hope would not cause USB comm errors. I just forced a scan now: no comm errors. I'm starting a more rigorous full scan now to see if it causes comm errors: so far, not but it has 3 hours to go. Previous scans have not found any threats.
  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 under Linux. On this particular system I have done exactly those tasks with never a problem. I hope you can find this and get it fixed. I will be interested to hear what the problem and solution are. Sincerely...
  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 automatically do this? Halting on an error means if this happens in the field, our whole data mission is lost.
  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 in Chrome, sampling trigger output from AD2). At 100 KHz: 16 msec/div, at 50 KHz: 32 msec/div Option 1 (8K Samples), Time 8192 Samples, 50 KHz, 3999 logged acquisitions success: 4, fails: 0. Option 2 (16K Samples), Time 16384 Samples, 50 KHz, 3999 logged acquisitions success: 0, fails: 2 [email protected] 3226, 3434 acquisitions Option 2 (16 K Samples), Time 16384 Samples, 100 KHz, 3999 logged acquisitions success: 1, fails: 3 @ 366, 1 after max index reached Option 2 (16K Samples), Time 8192 Samples, 50 KHz, 3999 logged acquisitions success: 0, fails: 2 Communication fails while just monitoring the scope, as you would in the lab. No logging happening, but Execute was set to "Each Triggered Acquisition" but Export said "Not saving. Maximum index reached". I changed Execute to "Manual" to see if that made any difference: no. There seems to be correlation with the Device Manager setting for number of samples: 8K has never failed and 16K always fails. Oddly it doesn';t seem to be the number of samples sent over USB but the number being contemplated by the AD2. Setting for 16K but only sending 8K (via the time base) still fails. Sample rate doesn't seem to be the issue. Also, OpenScope MZ continued to run flawlessly on the Linux system, monitoring trigger out from the AD2. AD2, Windows 10 Pro, Thinkpad Yoga S1 notebook - this is my main daily use notebook. I notice startup is much slower on Windows, so is deleting the temp log files, by like 100X: Windows deletes 80 files per second, so for 3999 files this takes a while. Anyway, after two tests I turned unchecked "noise" per Atilla's suggestion. Option 2 (16K Samples), Time 16384 Samples, 100 KHz, 3999 logged acquisitions success: 8, fails: 0. In addition, no comm error while just viewing waveform on screen. AD2, Windows 10 Pro, Thinkpad x11e notebook - this is the notebook we can leave on site for extended logging Option 2 (16K Samples) can run for days no error... then suddenly there is a popup with Comm error 0xA. This was while just viewing on screen, not logging.
  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. That update went smoothly. Calibration completes but the web page still says it is uncalibrated. Did it again. No change. Ignore and continue. Now I can make a sample measurement with scope 1 (orange) connected to wavegen (yellow) Randomly the PC speaker outputs a thump, seems to be caused by WaveformsLive. What's up with that? digilent-agent terminal frequently spews out binary data (?) Should I worry? What exactly is the need to go to a web site at to use this scope? That seems an awfully circuitous way to get a local display. Is all the scope data getting sent to AWS and then back in the display? Or AWS is serving the display and data gets merged in locally somehow? And what if I don't have a fast Internet connection everywhere I want to use this tool? Would like to trigger this MZ from a AD2 to get two more analog channels to log. Now to read documentation and try to get useful results. Also will try under Windows 10 Pro Thanks to @wyojustin and this helpful forum post.
  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. Ultimately I arrived at this: acq_####_[ddhh]_[mmss].csv which makes more sense for our files.
  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 events are rare and not on a predictable timetable. So we are rather searching for a needle in a haystack and we hope to find evidence it exists. Here I am talking about Scope function (Logger's sample rate of 100 msec is too slow for this case) and there are still many details I don't claim to understand. But since I need to make a report of what is possible with AD2, here goes. Record mode can capture much longer numbers of samples Device manager determines what is possible (e.g. Patterns) but some things seem ignored (e.g. Scope samples) Sample rate, number of samples, and pre-trigger samples are set with the "Config" button with the green diode-like symbol. This is intuitive with a % of total acquisition setting for trigger location. Zooming and scrolling in the display window does not change what you set with the Config button so subsequent captures use the same config. Actual sample rate and length is limited by USB connection speed to the host PC. On a 1.7 GHz dual core Linux with 16 GB RAM and SSD, it seems to be limited to 200 KHz sample rate. At 100 KHz we can capture up to 10 M samples, for a 100 second acquisition Acquisition in "record" mode can only be started with a button click and cannot be triggered by normal scope triggers even though those settings are still present on the GUI. Pressing Record is the only way to start capture and that immediately captures one acquisition. It can't wait for trigger conditions to be met. An acquisition can be saved using the logging settings if set for "each triggered acquisition", even though it really wasn't 'triggered'. Also "each acquisition" works. In record mode, if Device Manager is set to allow it, Patterns can work to use Scope Detector to make an external trigger output on a DIO pin, and this will trigger on the stated conditions but only *after* the Scope Record button is clicked. And I also have to remember to separately click the Pattern Run button or its output won't generate This can only record a single event and you have to click on the Scope Record button to start the acquisition. So Record mode won't work for us. In "repeated" mode, the scope will use the trigger settings Device Manager determines how many samples can be captured: 8K or 16K are the highest options of the 6 available and those seem to be the only ones possible. so it can wait until trigger conditions occur, then capture each time the trigger conditions are met. Sample length is a max of 16384 samples Settings - Options can make one of the trigger pins "Scope" which generates a single rising edge trigger per acquisition, to trigger other AD2s or other logging devices Sample rate and pre-trigger are confusing in repeated mode. It appears they can be set in the Time dialogs, also number of samples, pre-trigger (the "position" setting), but this interacts with the scope display screen: zooming and panning changes your intended settings. There seems to be no way to lock them like on a traditional desktop DSO. It's nothing like Config in Record mode. The display has 10 divisions so if I want to trigger at 2 divisions I'm better off to drag the white triangle on the top of the scope display to 2 divisions from the left. In repeated mode, Trigger takes place at time 0 and pretrigger time is negative. So for 16K samples at 100 KHz, that is about 16 msec/div. Trigger two divisions from left makes the leftmost time -32 msec and Time "Position" 48 msec, which doesn't make any sense to me. Time Base is 16 msec/div as expected. Don't dare zoom in the scope display or the time settings will also change, changing the next triggered acquisition! If you do this by accident its a tedious, multi-click process to get back to the settings you intended. At 100 KHz 16384 samples is 168 msec, long enough for us, we hope. At 8K samples we'd have to drop to 50 KHz samples Clicking Run button means scope will wait for trigger satisfied, then log both channels to PC memory, auto-incrementing the file name File name can include day hour min sec which is handy. Be careful entering this information or Waveforms will crash. I'll post a bug elsewhere. Full timestamp and setting values are included in the .csv log file You specify how many acquisitions to save, at which point logging halts. 1,000,000 is the largest number I could set. Saving workspace sometimes causes a ghost progress window which can be cleared with another save. So Repeated mode will work for us, with the limits of 16K @ 100 KHz samples Each 2-channel 16K log file is about 984 KBytes. As each 16K sample file is a bit under 1 MByte, you get 1000 log files per GB. Summary: For unattended, auto trigger and acquisition of multiple events, and logging to a computer file, "repeated" mode is the only option. We can log two analog channels per AD2, plus digital inputs if we wish. External trigger output: one rising edge per triggered acquisition. Trigger goes low at end of acquisition. Trigger other AD2s or external equipment. Samples per acquisition are 16K or 8K Logging can occur up to the maximum value you set (up to 1 M acquisitions), or the PC runs out of disk space, at about 1 MByte per 16K acquisition.
  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.