Jump to content

LabVIEW Crashing with Silver button on new hardware


Recommended Posts

Guys,

I would like to ask for a favour from other engineers.

We have a problem that is causing LabVIEW to crash. After a lot of effort, we found the exact functions causing the crash and have prepared some simple test VI's (attached).

I would like to ask other LabVIEW developers to test these VI's according to the procedure below.

1. Close LabVIEW – this is important!!

2. Open LabVIEW and open ‘test_8.2.1.vi’. You do not need to run it – opening it is enough.

3. Open and Run ‘test_2011.vi’.

4. Click the silver button (called ‘Boolean’).

5. On our newest industrial PC's, this crashes immediately. On older models there is no problem.

The crash only occurs with the silver button.

Interestingly, if you open and run test_2011.vi first and click the button. you can then load the other VI and start and stop the VI's in any order and the crash does not occur. That is until you stop LabVIEW and start the process above again.

The response from NI is that the problem must be with our industrial PC's and "Don't use the Silver Controls". Not using the silver controls is no problem of course, but I am interested how common this problem is.

Link to comment

Thanks asbo.

I should have perhaps mentioned these VI's are saved using LV2011SP1.

I think our problem is hardware related and not linked to operating system. However, it is good to know the operating system is OK.

We have essentially identical PC's running windows XP. The crash only occurs on PC's with the latest motherboard revision (although of course the bios could also have been updated).

Link to comment
The response from NI is that the problem must be with our industrial PC's and "Don't use the Silver Controls". Not using the silver controls is no problem of course, but I am interested how common this problem is.

That's a valid statement for a workaround, but do you know if they've escalated it into a CAR to be further investigated? My gut tells me that there are a few people in LabVIEW R&D that would be interested in this issue.

The crash does not repro in LV2011 on Win7 x64.

I don't have any issues on my PC - although it's the same model as asbo's (Lenovo T510), with Win7 64 and LabVIEW 2011 32bit SP1 installed.

Link to comment

That's a valid statement for a workaround, but do you know if they've escalated it into a CAR to be further investigated? My gut tells me that there are a few people in LabVIEW R&D that would be interested in this issue.

I have no information that they have escalated the issue. In this case I assume nothing has been done. I will contact them and ask the question.

I can live without the silver controls, but is this highlighting a bigger issue behind???? I have no idea.

It is a valid statement that maybe this issue is with the industrial PC. I am in discussions with the PC manufacturer regarding this problem, however, this occurs only if a specific function in LabVIEW is used!! I am not sure how much luck I will have convincing them!

Link to comment

I would hazard a guess that do a repair or uninstall/reinstall on LabVIEW will remedy the issue. How many machines does it present on?

Hey Asbo, not this time. ;-)

We have 16 - 20 PC'S of one specification and this crash does not occur. Thex have been working reliably for many months.

We had 1 PC that started crashing. We uninstalled and then reinstalled LabVIEW but the crash still occurred.

We then restaged the PC back to its 'as supplied' status and reinstalled LabVIEW. Again LabVIEW crashed.

Finally we noticed the different mainboard number. So we took a couple of PC's from stock with this new mainboard and installed LabVIEW. The same trial was performed and LabVIEW crashed on them all.

Take away the silver control and all work well.

Link to comment

Hey Asbo, not this time. ;-)

We have 16 - 20 PC'S of one specification and this crash does not occur. Thex have been working reliably for many months.

We had 1 PC that started crashing. We uninstalled and then reinstalled LabVIEW but the crash still occurred.

We then restaged the PC back to its 'as supplied' status and reinstalled LabVIEW. Again LabVIEW crashed.

Finally we noticed the different mainboard number. So we took a couple of PC's from stock with this new mainboard and installed LabVIEW. The same trial was performed and LabVIEW crashed on them all.

Take away the silver control and all work well.

Haven't checked out how they did the silver controls, but being graphics and all I have a suspicion that it is either a Video Driver or maybe even specifically a GPU issue. Can you see if the different revision motherboards use some kind of different chipset, or at least revision thereof. What about the video driver?

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.