You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
**Issue - Internal bug 1720960
No data read when using the Instrument Addon Custom Device with a USB VISA device with wait type as Wait Second. Does not matter if casting to data type or formatting to a String for output to VeriStand screen indicator. No data will be read or displayed to a screen indicator.
Versions Noted
Confirmed in VeriStand 2019 R3 and VeriStand 2020 R5 with the 20.4 Instrument Addon Custom Device release from Github.
Replicating Steps
Create new VeriStand default project and save to a desired test location
Open System Definition file using the Configure button
Add a new Instrument Addon by right clicking on Custom Devices, then selecting National Instruments>>Instrument Addon
Select VISA as protocol
Select the applicable VISA resource (tested with Tektronix 2001C USBTMC Oscilloscope)
Now create a message group by right clicking the new device from the tree view and selecting Add Group
Right click the message group and select Add Message
Expand the message group and individual message and configure the message and response
For example, for the Tektronix instrument, a "MEASU:MEAS:VAL?" command was used after verifying in a VISA test panel in NI-MAX
Configure the response by assigning a variable such as [myMeasurement]
Right click on the response and create the data for the response
Connect the data to the variable under the Linkage section of the Response entry item from the tree view
Navigate to the screen (UI manager)
Add an indicator and connect it to the response data
Ensure the Wait Type is Wait Second (This is the problem setting while Byte Count works great)
Deploy the system definition to Windows LocalHost
No data is seen updating in the indicator
Work Around
Current work around is to use Byte Count and give big enough buffer so that the VISA Read.vi function will complete successfully.
Root Cause
The Instrument Addon Custom Device uses an incorrect VISA attribute called Number of Bytes at Serial Port when on the Wait Second wait type. This attribute is not applicable to USB or USBTMC devices.
Using source code, navigate to Instrument Addon Engine.llb>>Protocol Engine.vi See screenshot below of Protocol Engine.viProtocol Engine Code.png
Double click on Read function (icon with glasses) to view the different Class definitions for reading different instrumentsProtocol Engine Class VISA class Read.png
**Issue - Internal bug 1720960
No data read when using the Instrument Addon Custom Device with a USB VISA device with wait type as Wait Second. Does not matter if casting to data type or formatting to a String for output to VeriStand screen indicator. No data will be read or displayed to a screen indicator.
Versions Noted
Confirmed in VeriStand 2019 R3 and VeriStand 2020 R5 with the 20.4 Instrument Addon Custom Device release from Github.
Replicating Steps
Work Around
Current work around is to use Byte Count and give big enough buffer so that the VISA Read.vi function will complete successfully.
Root Cause
The Instrument Addon Custom Device uses an incorrect VISA attribute called Number of Bytes at Serial Port when on the Wait Second wait type. This attribute is not applicable to USB or USBTMC devices.
The text was updated successfully, but these errors were encountered: