Baker Steve

(Sorry about inadvertently rude typo: it was a genuine slip of the fingers!)

Ok - I now have an actual Analog 2, so here's more feedback. Despite the above advice, I had some fun (?) getting Waveforms to recognize the device with the Mavericks build you cited on Feb 11. Sometimes I got the message 'No device detected', while at other times (not sure of the circumstances) I got a message telling me to delete the driver, and the relevant window opens in the Finder. I deleted and reinstalled the driver shat was included with the Mavericks release several times. One possible complication is that I have Parallels Desktop running. When a new USB device is connected, Parallels pops up a window asking whether you want to connect it to the host OS or a virtual machine (I am of course selecting the host OS). However, trying Waveforms with Parallels not running made no difference. I then went back to the last version of Waveforms that was stable on OS X 10.9, v 3.5.4. Starting that popped up a dialog telling me that no FTDI driver was installed, and asking me if I wanted to install one. When I ok'd that it installed the driver, but this made no difference: Waveforms v 3.5.4 still gave the 'No device detected' message on launch. Rebooting as in your item 2 above did, finally, allow v 3.5.4 to recognize the device (hooray!). After that the Mavericks build detected the Analog 2 and also works. I'm passing this back as feedback, as this experience suggests that maybe with the Mavericks build (for which, by the way, many thanks) it is necessary to install an older version of Waveforms first and then upgrade, as my efforts to get the Mavericks build to work 'cold' were unsuccessful, rather going round in FTDI driver-induced circles. I'm really excited at having got this to work. If it performs as well as I suspect it will, it makes possible projects that I would never have been able to afford with discrete instrumentation.

This does appear to be stable in OS X 10.9 - thanks for the heads-up. For the driver, does 'restart having the device disconnected' mean 'restart *with* the device disconnected? Steve

I too have experienced instability with Waveforms on an older version of OS X – everything beyond 3.6 crashes here in launch. I see that the new Waveforms 3.9.1 comes with an optional driver ''For OS X 10.13 or earlier version'. Is this intended to fix the instabilities discussed in this thread, or is it for some other purpose? (I'm still on OS X 10.9 for a variety of reasons that have nothing to do with Waveforms.)

I understand. At least WF 3.6.8 works here. At some point soon I will actually get a physical Analog Discovery 2 (the relevant project's been on the back-burner for 18 months), which will allow me to test whether this is anything to do with running WF in demo mode. At present though it's looking as if more recent versions of WF aren't compatible with OS X 10.9 ('Mavericks'). (I'm stuck with Mavericks for reasons of not rocking the boat with more mission-critical stuff, like all my costly Adobe software that runs under an OS X 10.6 virtual machine in Parallels, plus FrameMaker under Windows 7, ditto.)

Ah, right - sorry.

Sorry, don't understand what you mean by 'insight'.

I'm sorry it's taken me a long time to get back to this. WF 3.7.19 also exhibits the same crash on launch behavior here. I've appended the initial section of the crash dump below. It's maybe important to note that I'm only running WF in demo mode. The highest revision that is stable here is 3.6.8. Waveforms 3.7.19 crash dump.rtf

The Digilent website states that Waveforms v 3.7.5 works with OS X 10.9. However, it always crashes on launch here. v 3.6.8 works just fine. Here is the first section of the crash trace... ath: /Applications/WaveForms.app/Contents/MacOS/WaveForms Identifier: com.Digilent.WaveForms Version: ??? Code Type: X86-64 (Native) Parent Process: launchd [202] Responsible: WaveForms [8930] User ID: 501 Date/Time: 2018-05-03 15:33:38.800 +0100 OS Version: Mac OS X 10.9.5 (13F1911) Report Version: 11 Anonymous UUID: 7BFA442D-B897-118F-12D8-40163310AEDA Crashed Thread: 12 Exception Type: EXC_BREAKPOINT (SIGTRAP) Exception Codes: 0x0000000000000002, 0x0000000000000000 Dyld Error Message: Symbol not found: _OSAtomicIncrement32Barrier Referenced from: /Applications/WaveForms.app/Contents/MacOS/../Frameworks/dwf.framework/Frameworks/../Frameworks/libdabs.dylib Expected in: /usr/lib/libSystem.B.dylib Thread 0:: Dispatch queue: com.apple.main-thread 0 libsystem_kernel.dylib 0x00007fff88360a3a __semwait_signal + 10 1 libsystem_c.dylib 0x00007fff8a4e2dcc nanosleep + 200 2 libdabs.dylib 0x000000010864c95b OSXUTIL::SleepMs(unsigned int) + 107 3 libdpcomm.dylib 0x00000001083e608f ENMMG::FDoEnumEx(int*, unsigned int, unsigned int, unsigned int, void*) + 143 4 libdpcomm.dylib 0x00000001083dab30 DpcEnumDevicesEx + 80 5 libdmgr.dylib 0x0000000106bf391f DmgrEnumDevicesEx + 47 6 com.Digilent.WaveForms 0x00000001068eb5a3 FCommEnum(int) + 51 7 com.Digilent.WaveForms 0x00000001068eb835 FDwfEnum + 133 8 com.Digilent.WaveForms 0x00000001067a3dc7 0x1064a5000 + 3141063 9 com.Digilent.WaveForms 0x00000001067a2fcd 0x1064a5000 + 3137485 10 com.Digilent.WaveForms 0x00000001065ae362 0x1064a5000 + 1086306 11 org.qt-project.QtCore 0x00000001070c4d5c QObject::event(QEvent*) + 156 12 org.qt-project.QtWidgets 0x0000000107acef6e QWidget::event(QEvent*) + 4254 13 org.qt-project.QtWidgets 0x0000000107bde44c QMainWindow::event(QEvent*) + 1660 14 org.qt-project.QtWidgets 0x0000000107a8d086 QApplicationPrivate::notify_helper(QObject*, QEvent*) + 294 15 org.qt-project.QtWidgets 0x0000000107a8fb45 QApplication::notify(QObject*, QEvent*) + 5941 16 org.qt-project.QtCore 0x00000001070989c4 QCoreApplication::notifyInternal2(QObject*, QEvent*) + 164 17 org.qt-project.QtCore 0x00000001070995e4 QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) + 596 18 libqcocoa.dylib 0x000000010af58dfe 0x10af36000 + 142846 19 com.apple.CoreFoundation 0x00007fff907dfd67 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23 20 com.apple.CoreFoundation 0x00007fff907dfcd7 __CFRunLoopDoObservers + 391 21 com.apple.CoreFoundation 0x00007fff907d0e59 CFRunLoopRunSpecific + 281 22 com.apple.HIToolbox 0x00007fff8f254a0d RunCurrentEventLoopInMode + 226 23 com.apple.HIToolbox 0x00007fff8f254685 ReceiveNextEventCommon + 173 24 com.apple.HIToolbox 0x00007fff8f2545bc _BlockUntilNextEventMatchingListInModeWithFilter + 65 25 com.apple.AppKit 0x00007fff892d624e _DPSNextEvent + 1434 26 com.apple.AppKit 0x00007fff892d589b -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 122 27 com.apple.AppKit 0x00007fff892c999c -[NSApplication run] + 553 28 libqcocoa.dylib 0x000000010af5856f 0x10af36000 + 140655 29 org.qt-project.QtCore 0x0000000107094d91 QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 401 30 org.qt-project.QtCore 0x0000000107099035 QCoreApplication::exec() + 341 31 com.Digilent.WaveForms 0x00000001064adc43 main + 6067 32 com.Digilent.WaveForms 0x00000001064abb84 start + 52 Thread 1: 0 libsystem_kernel.dylib 0x00007fff88360e6a __workq_kernreturn + 10 1 libsystem_pthread.dylib 0x00007fff94290f08 _pthread_wqthread + 330 2 libsystem_pthread.dylib 0x00007fff94293fb9 start_wqthread + 13 Thread 2:: Dispatch queue: com.apple.libdispatch-manager 0 libsystem_kernel.dylib 0x00007fff88361662 kevent64 + 10 1 libdispatch.dylib 0x00007fff88d81421 _dispatch_mgr_invoke + 239 2 libdispatch.dylib 0x00007fff88d81136 _dispatch_mgr_thread + 52 Thread 3: 0 libsystem_kernel.dylib 0x00007fff88360e6a __workq_kernreturn + 10 1 libsystem_pthread.dylib 0x00007fff94290f08 _pthread_wqthread + 330 2 libsystem_pthread.dylib 0x00007fff94293fb9 start_wqthread + 13 Thread 4: 0 libsystem_kernel.dylib 0x00007fff88360e6a __workq_kernreturn + 10 1 libsystem_pthread.dylib 0x00007fff94290f08 _pthread_wqthread + 330 2 libsystem_pthread.dylib 0x00007fff94293fb9 start_wqthread + 13 Thread 5: 0 libsystem_kernel.dylib 0x00007fff88360e6a __workq_kernreturn + 10 1 libsystem_pthread.dylib 0x00007fff94290f08 _pthread_wqthread + 330 2 libsystem_pthread.dylib 0x00007fff94293fb9 start_wqthread + 13 Thread 6: 0 libsystem_kernel.dylib 0x00007fff88360e6a __workq_kernreturn + 10 1 libsystem_pthread.dylib 0x00007fff94290f08 _pthread_wqthread + 330 2 libsystem_pthread.dylib 0x00007fff94293fb9 start_wqthread + 13 Thread 7:: Qt bearer thread 0 libsystem_kernel.dylib 0x00007fff883609aa __select + 10 1 libsystem_c.dylib 0x00007fff8a4e2bec pselect$1050 + 183 2 org.qt-project.QtCore 0x00000001070ece37 qt_safe_select(int, fd_set*, fd_set*, fd_set*, timespec const*) + 103 3 org.qt-project.QtCore 0x00000001070edf05 QEventDispatcherUNIXPrivate::doSelect(QFlags<QEventLoop::ProcessEventsFlag>, timespec*) + 693 4 org.qt-project.QtCore 0x00000001070ef0a7 QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 231 5 org.qt-project.QtCore 0x0000000107094d91 QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 401 6 org.qt-project.QtCore 0x0000000106ed8e4e QThread::exec() + 110 7 org.qt-project.QtCore 0x0000000106edc8ba 0x106eb3000 + 170170 8 libsystem_pthread.dylib 0x00007fff9428f899 _pthread_body + 138 9 libsystem_pthread.dylib 0x00007fff9428f72a _pthread_start + 137 10 libsystem_pthread.dylib 0x00007fff94293fc9 thread_start + 13 Thread 8:: QScanThread 0 libsystem_kernel.dylib 0x00007fff883609aa __select + 10 1 com.apple.framework.CoreWLAN 0x00007fff8d22f91a _waitForScanComplete + 336 2 com.apple.framework.CoreWLAN 0x00007fff8d22ed65 Apple80211Scan + 889 3 com.apple.framework.CoreWLAN 0x00007fff8d209f34 -[CWInterface(Private) scanForNetworksWithChannels:ssid:bssid:restTime:dwellTime:ssidList:error:] + 1613 4 com.apple.framework.CoreWLAN 0x00007fff8d205e77 -[CWInterface scanForNetworksWithSSID:error:] + 171 5 libqcorewlanbearer.dylib 0x000000010e98cdd2 0x10e986000 + 28114 6 org.qt-project.QtCore 0x0000000106edc8ba 0x106eb3000 + 170170 7 libsystem_pthread.dylib 0x00007fff9428f899 _pthread_body + 138 8 libsystem_pthread.dylib 0x00007fff9428f72a _pthread_start + 137 9 libsystem_pthread.dylib 0x00007fff94293fc9 thread_start + 13 Thread 9: 0 libsystem_kernel.dylib 0x00007fff88360e6a __workq_kernreturn + 10 1 libsystem_pthread.dylib 0x00007fff94290f08 _pthread_wqthread + 330 2 libsystem_pthread.dylib 0x00007fff94293fb9 start_wqthread + 13 Thread 10: 0 libsystem_kernel.dylib 0x00007fff88360e6a __workq_kernreturn + 10 1 libsystem_pthread.dylib 0x00007fff94290f08 _pthread_wqthread + 330 2 libsystem_pthread.dylib 0x00007fff94293fb9 start_wqthread + 13 Thread 11: 0 libsystem_kernel.dylib 0x00007fff88360e6a __workq_kernreturn + 10 1 libsystem_pthread.dylib 0x00007fff94290f08 _pthread_wqthread + 330 2 libsystem_pthread.dylib 0x00007fff94293fb9 start_wqthread + 13 Thread 12 Crashed: 0 dyld 0x00007fff6c4fe09d dyld_fatal_error + 1 1 dyld 0x00007fff6c500df6 dyld::fastBindLazySymbol(ImageLoader**, unsigned long) + 171 2 libdyld.dylib 0x00007fff8fab02dd dyld_stub_binder_ + 13 3 ??? 0x0000000108660050 0 + 4435869776 4 libdabs.dylib 0x000000010864f7ce libusb_init + 542 5 libdabs.dylib 0x0000000108647853 OSXUSB::InitLibusb() + 67 6 libdabs.dylib 0x000000010864777e OSXUSB::Init() + 62 7 libdpcomm.dylib 0x00000001083f8275 USBC::FEnum(int, int, unsigned int, void*, DVCMG*) + 917 8 libdpcomm.dylib 0x00000001083e5914 ENMMG::DoEnumThread() + 404 9 libdpcomm.dylib 0x00000001083e576d EnumThread(void*) + 29 10 libsystem_pthread.dylib 0x00007fff9428f899 _pthread_body + 138 11 libsystem_pthread.dylib 0x00007fff9428f72a _pthread_start + 137 12 libsystem_pthread.dylib 0x00007fff94293fc9 thread_start + 13 Thread 12 crashed with X86 Thread State (64-bit): rax: 0x00007fff6c532db0 rbx: 0x00007fc9db9c9290 rcx: 0x0000000000000000 rdx: 0x0000000000000000 rdi: 0x00007fff6c532f20 rsi: 0x0000000000000000 rbp: 0x000000010f44a2e0 rsp: 0x000000010f44a2c8 r8: 0x00007fff6c51db8c r9: 0x0000000000000000 r10: 0x00007fff6c520d26 r11: 0x00007fff6c532f20 r12: 0x00007fc9d9d94090 r13: 0x00007fc9d9d94140 r14: 0x00007fff6c532f20 r15: 0x00007fc9d9d94080 rip: 0x00007fff6c4fe09d rfl: 0x0000000000000246 cr2: 0x000000010f465000 Logical CPU: 2 Error Code: 0x00000000 Trap Number: 3

Thanks!

I've got more info. I think at least part of the problem occurs at save-on-quit: when a cmd-Q or File->Quit command is issued, at least one instrument window closes before the context save. That instrument is therefore not saved, and so not re-displayed on open. Steve

If I spot any causative factor that makes the issue repeatable I will let you know. Steve

I ought to add that this problem is intermittent, so not necessarily repeatable. I've not found a set of circumstances that precipitates it. Steve

Is this issue being addressed? I am definitely seeing lost instruments on a context save/restore, and I need to make a purchase decision. It might be specific to my setup: 2013 MacPro/Mavericks (OS X 10.9.5) with a simulated Analog Discovery 2 in Waveforms 2015 v 3.2.6. I appreciate that you are working on Waveforms 2016, but if there is a bug, I don't expect you want to carry it over into the new version. I'm entirely happy to run tests and/or diagnostics here if that would help: I'm excited about the Discovery 2 and am happy to help. I spent half my working life on electronics of one sort or another, so generally know what I'm doing. Thanks. Steve (BSc MBCS MISTC CITP)

Ignore the screenshot, which was done with 3.1 - I am now definitely using 3.2.6. I tried to attach a screenshot of the 'About' box to prove this, but I get a message saying I'm only allowed to upload 30 kB. The missing instruments aren't opening outside the screen area, as they don't show up in the Window menu either. Steve