ActiveX Tech Notes

Using the ConnectZBUS method always returns 0 for USB3 interface

Circuit fails when loaded using 64-bit Matlab or Python

ConnectPA5 method always fails (returns 0)

Writing console applications with ActiveX or OpenDeveloper controls

Using the GetStatus method with RX devices returns erroneous information

Converting WAV File Sampling Rates

Using LoadCOFsf to set arbitrary sampling rates yields erroneous results

Repeated use of the ActiveX Connect command causes the system to crash

GetStatus returns incorrect information for bit-0 on an RZ2

Buffering a long signal at a high sample rate causes a memory allocation error

RCO files created with RPvdsEx v50 or earlier might fail to load when using ActiveX v60 and greater

zBusSync always returns zero when using USB2, Gigabit, or Optibit interfaces

GetStatus returns zero or zBus error 'Failed locking device.'

Memory leaks occur in MATLAB when calling ActiveX functions with improper capitalization

HardwareReset always returns 0

GetStatus always returns a 0 for the RA16BA connection status (least significant bit)

Synchronizing devices using zBusSync

Invoking the ActiveX zTrigA or zTrigB calls always returns a zero

After upgrading the ActiveX controls, VC++, VB, and Delphi programs that used to work no longer work correctly

ZTrig does not work while using ActiveX with USB