Dumping efficiency measurements from Yokogawa WT1600 power analyzer - Page 1
Forum section: electronics / testgear

author: w00t
author_rank: Newbie
timestamp: May 28, 2025, 01:43:59 am
content: I'm working on an electric motor dynamometer system and trying to get efficiency measurements for our inverter and motor by measuring DC power, AC power, and mechanical power. Currently trying to get a Yokogawa WT1600 to dump logs over WTViewer (note: NOT WTViewerE) so that I can post-process the measurements. The WT1600 is an old instrument and WTViewer supported up to Windows 7, so I'm dealing with some software headaches.Problem: WTViewer crashes whenever I try to start logging data.I started writing a bit of Python to do the GPIB interfacing myself and it works but it's a bit of a pain, and it would be ideal if WTViewer just worked instead.Hardware:- WT1600, GPIB option- NI GPIB-USB-HSSoftware versions:- WT1600: firmware version 3.23 (2.01+ required for WTViewer)- WTViewer: 8.24- Running as administratorTried two separate computers running the same setup:- Windows 11 Pro- Visual C++ Redistributable: installed 2005, 2008, and 2015 x86- NI 488.2 GPIB drivers: 22.8 (2022 Q4)- Note: WT1600 manual calls out for version 2.8.1, which isn't supported on Windows 11- Running WTViewer in compatibility mode (Windows 7)Also tried a VM setup:- Windows 7 Home Basic- Visual C++ Redistributable: installed 2005 and 2008 x86- NI 488.2 GPIB drivers: 2.8.1GPIB setup:- NI MAX: GPIB interface ID set to 0- WT1600 communication: "GP-IB"- WT1600 GP-IB Address: 1- WTViewer address: 1Crashing behavior, consistent across all 3 computer setups:1. Enter "On-Line" mode, GPIB address 12. We are able to connect via GPIB to the WT1600 in multiple modes, enabling the "REMOTE" light3. I'm able to successfully launch all the modes: "Normal", "Integration", etc.4. I can successfully set settings over GPIB from WTViewer5. Pressing "Start" to start logging still crashes the programI dumped an error log from WTViewer crashing in Windows Event Viewer:> Faulting application name: WtViewer.exe, version: 8.2.4.0, time stamp: 0x57c78d3c> Faulting module name: tmctl.dll, version: 2.1.6.0, time stamp: 0x4cad4916> Exception code: 0xc0000409> Fault offset: 0x0001451b> Faulting process id: 0xD4C> Faulting application start time: 0x1DBCE65B79ED72C> Faulting application path: C:\Program Files (x86)\YOKOGAWA\WTViewer\WtViewer.exe> Faulting module path: C:\Program Files (x86)\YOKOGAWA\WTViewer\tmctl.dll> Report Id: 3cff716f-c36b-439d-8a61-ea7fefddf178> Faulting package full name:> Faulting package-relative application ID:From some digging, this appears to indicate a stack buffer overrun error in the Test & Measurement Control Library (tmctl.dll). I've been in touch with the Yokogawa application engineering team and they unfortunately don't have experience with the instrument/software since it's so old. Currently pending a DLL investigation by their product team.Also note: I suspect that our GPIB adapter is a knockoff, but I can still send and read data over GPIB through Python and set settings in WTViewer. It only crashes on the WTViewer DLL after I start logging.WT1600 manual:https://cdn.tmi.yokogawa.com/IM760101-01E.pdfWTViewer manual:https://archive.org/details/manualzilla-id-5796074/page/n97/mode/2upWould appreciate any debugging insights, thanks!

author: KungFuJosh
author_rank: Super Contributor
timestamp: May 28, 2025, 02:22:15 am
content: Can you adjust the GPIB data rate? This is just a blind guess, but maybe the logging is too fast?