LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Error after 29 hrs

I'm running LabView 2017 64-bit which calls a TestStand 2016 64-bit sequence

After running for approximately 29hrs the Operating System shows an Event Failure

- EventData

LabVIEW.exe 17.0.0.4011

59947661

NiViSv64.dll

17.5.0.49152

59ef657f

c0000005

0000000000003123

2330

C:\Program Files\National Instruments\LabView 2017\LabVIEW.exe

C:\WINDOWS\SYSTEM32\NiViSv64.dll

34b6980f-d189-4ca4-aef3-08bfe5d36509

0 Kudos
Message 1 of 10
(2,612 Views)

Check your power saving settings for any comm port you may be using.

 

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 2 of 10
(2,604 Views)

I've double-checked the Power Settings.

The only thing I believe I missed was a default setting on the USB port, which I've now disabled.

 

I'm about 6-hrs away from determining whether this is the answer or not.

Still looking for additional suggestions.

Any theories on the DLL ?

 

Keith

0 Kudos
Message 3 of 10
(2,590 Views)

@DylanEngKeith wrote:

...

Any theories on the DLL ?

 

Keith


With the scares info you provided, the wild guess about VISA failing if the power saving options are active is the only idea that I can offer.

 

Now if you provide more information... maybe someone can say more.

 

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 4 of 10
(2,573 Views)

Additional Information:

Main Application is LabView 

This App uses the example 

C:\Users\Public\Documents\National Instruments\TestStand 2017 (32-bit)\Examples\Modifying User Interfaces\Creating a Basic User Interface\LabVIEW

It calls a TestStand Sequence which contains a combination of LabView routines as well as .NET calls

The Main LabView application uses Messages to pass data between the UI and the Sequence to update FileGlobals, as well as Indicators.

I understand this is fairly cryptic. If more details are required then I will provide as much as I can with security concerns

 

KM

0 Kudos
Message 5 of 10
(2,521 Views)

See here for a KB article that may help.

 

It speaks of an access violation "c0000005 "

 

Clearly winging it...

 

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 6 of 10
(2,502 Views)

In addition, this occurs in

NiViSv64.dll

I was hoping that someone would have a bit more information on this dll

 

 

KM

0 Kudos
Message 7 of 10
(2,482 Views)

@DylanEngKeith wrote:

In addition, this occurs in

NiViSv64.dll

I was hoping that someone would have a bit more information on this dll


What kind of information are you looking for?

 

There's this.

0 Kudos
Message 8 of 10
(2,457 Views)

@DylanEngKeith wrote:

In addition, this occurs in

NiViSv64.dll

I was hoping that someone would have a bit more information on this dll

 

 

KM


If you check the properties of this file it says that it is the NI-VISA Library Service, so most likely a collection of library routines used by the NI-VISA software.

 

So it would seem that something goes wrong when doing VISA communication, which leads us back to USB power saving troubles as a possible culprit.

Rolf Kalbermatter
My Blog
0 Kudos
Message 9 of 10
(2,445 Views)

@Ben wrote:

Check your power saving settings for any comm port you may be using.

 

Ben


Sometimes the (internal) USB hubs have power saving settings too. Those might need tweaking as well.

0 Kudos
Message 10 of 10
(2,440 Views)