From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

VirtualBench

cancel
Showing results for 
Search instead for 
Did you mean: 

VB-8012: device error: Index was outside the bounds of the array.

My VB-8012 was running firmware version 1.0 up to this morning (I have not used it much these past few months). Earlier today I saw a firmware update was available. I accepted it and the device upgraded to FW version 1.1. After rebooting, a new FW update was proposed (15.1). I accepted it, the device rebooted again.

But now when I want to use the application, the following error box appears: "Device error: Index was outside the bounds of the array"

My PC is running 64-bit Windows 7. I always start the application from the virtual CD-ROM drive, I never installed it on my PC.

 

I have tried the following actions:

  • reboot my PC
  • power cycle the Virtualbench
  • delete the AppData\Local\National Instruments\NI-VirtualBench directory
  • press the VB reset button

None of them solved the issue. Any idea?

 

0 Kudos
Message 1 of 3
(4,386 Views)

heel78 wrote:

 

I have tried the following actions:

  • reboot my PC
  • power cycle the Virtualbench
  • delete the AppData\Local\National Instruments\NI-VirtualBench directory
  • press the VB reset button

I would expect the last two, when done together, would reset the application.

 

With the application closed, would you try again?

  1. Close VirtualBench.exe
  2. Delete AppData\Local\National Instruments\NI-VirtualBench
  3. Press the reset button on the VirtualBench until it reboots itself
Joe Friedchicken
NI Configuration Based Software
Get with your fellow OS users
[ Linux ] [ macOS ]
Principal Software Engineer :: Configuration Based Software
Senior Software Engineer :: Multifunction Instruments Applications Group (until May 2018)
Software Engineer :: Measurements RLP Group (until Mar 2014)
Applications Engineer :: High Speed Product Group (until Sep 2008)
Message 2 of 3
(4,378 Views)

Thanks for your reply.

I did restart the application every time.

The problem went away when I pressed the reset button. I think I didn't press it for long enough before.

0 Kudos
Message 3 of 3
(4,375 Views)