Using RSLinx OPC with Labview 2009 SP1 and Getting Wierd Problem

I have a small test system with 4 analog inputs and 4 analog outputs. Oddly, I can use the Labview Distributed Systems Manager and read the input (level) changes and stroke the analog outputs (valves). However, when I go into a VI, I can get the level readings (only the first time I enter, after that not), but can never stroke the valves. Looking at the shared variable setup in both the project I am using and the Distributed Systems Manager, I have them both set up the same as a PSP with the same OPC reference, although formerly the project used project-attached shared variables.

Using the timed structure set at the same acquisition rate as the OPC interface corrected the problem.

Similar Messages

BSOD with labview 2009 sp1 on windows xp on dual core intel computer stop code F4

I have 14 test stations with the Labview runtime engine installed. These stations run 24 hours a day, or are supposed to, Every week, on average, one of the computers gets a blue screen of death, with a stop code of F4. It seems fairly random which computer it is.
Some other details:
Labview version 2009 sp1, and visa 5.02 installed
The computers are brand new Intel D510MO computers, with wester digital solid state hard drives. (Fanless)
XP service pack 3.
The computers aren't overheating, The ram is good, to power is stable and filtered.
The computers seem to run fine without ni software installed.
The only other thing installed is a serial port driver for a usb serial port converted.
We've caught one blue screen with no Labview executable running.
I've run a batch to turn off all non-essential Labview services, but it still seems to happen.
I've been working this problem for months. Any ideas?

John@ge wrote:
I have 14 test stations with the Labview runtime engine installed. These stations run 24 hours a day, or are supposed to, Every week, on average, one of the computers gets a blue screen of death, with a stop code of F4. It seems fairly random which computer it is.
Some other details:
We've caught one blue screen with no Labview executable running.
I've run a batch to turn off all non-essential Labview services, but it still seems to happen.
I've been working this problem for months. Any ideas?
If I am reading this correctly you have ruled out your LabVIEW program as the cause and you think it is one of the non-essential services. Which ones are still running?
Have you looked in the Windows error logs?
Edit: I forgot to add the link I was going to give you.
=====================
LabVIEW 2012

How to remove sub panel scrollbars with LabVIEW 2009-SP1?

I did a search and found this thread on the subject: http://forums.ni.com/t5/LabVIEW/subpanel-scollbars-in-labview-8-0/m-p/284503/highlight/false#M149983
I double checked that that the horizontal and vertical scrollbars were not selected in the Customize Window Appearance and they were not selected as shown in the image below. You can see the nasty scrollbars in the front panel in the image at the bottom. Of couse, since the code / sw cannot be shown, it has been painted over but you can still see the scrollbars along the frame of the sub-panel.
Customized Window Appearance settings:
Scrollbars are seen at the bottom & right of the sub panel frame
Solved!
Go to Solution.
Attachments:
WIndowAppearance.PNG ‏22 KB
scrollbars.PNG ‏33 KB

Just ran into this myself. (To complicate matters, forgot that one of my debug tools turns the scroll bars back on upon program exit.) "Off While Running" works, too. You can insert this code onto the diagram of any VI that will be called in a subpanel.
Thanks for the tip.
Certified LabVIEW Architect
Wait for Flag / Set Flag
Separate Views from Implementation for Strict Type Defs

Labview 2009 SP1 - Create exe option does not appear

Hello everyone,
I'm using Labview 2009 SP1 and I want to create a simple exe file (to run in the same computer that has labview or in any other computer with the appropiate labview run time engine).
I create a project with project explorer with the appropiate VI, everything OK for the moment, but when I right click on the menu "Build Specifications" of the project explorer I only have the options New and Help. If I click on New I only have "Source Distribution" and "Web Service (RESTful)" I would like to see the option Application and be able to create the EXE file.
Anyone knows how can i create simple EXE files or make the option "Application" to be visible?
Thanks for advance!
Much thanks for your time and dedication!

I guess you did not install the LabVIEW Application builder when you installed LabVIEW. When you do, it will allow you to create the exe and installer (You must be having a valid licence also).
The best solution is the one you find it by yourself

Can i build an application with Labview 2009 for Windows 7?

Hello
i use Labview 2009 SP1 and the application builder 2009 SP1. If i install the application on win7 this message is display:
Labview Run Time Engine depends on pruduct with upgrade code (...) version 9.0.301, language {} which is not in distribution.
Solved!
Go to Solution.

Is this an issue with Windows 7 having both installation folders for 32 bit (C:\Program Files (x86)) and 64 bit (C:\Program Files)?
I had an application built on an XP machine and installed on a Windows 7 machine which was looking for files in C:\Program Files when they were actually installed in C:\Program Files (x86) - because it was 32-bit application. After installation I had to move the files from 1 location to the other to make it work.

Error when trying to set up OPC I/O server with LabView 2009

Hi.I get an error when I try to set up OPC I/O server with LabView 2009 and the DSC module. If I open an empty project, right click ”My Computer”. Select new / I/O Server… and then OPC Client, the following error appears: Unable to browse OPC Server from the selected machine.Error -2147467262 occurred at GetOPCServerList.viPossible reason(s):LabVIEW: (Hex 0x80004002) No such interface supported. I have tried to repair LabView, but with no luck. Any idea what it could be?

The problems are not related to each otherOk then. Lets try getting this solved. Lemme dig......

I am using report generation toolkit 1.1 with Labview 7.0 and Office 2003 professional. The create new report VI opens Excel but throws error (-2147167262- from automation open VI) when I try to open MS word. please help...

I am using report generation toolkit 1.1 with Labview 7.0 and Office 2003 professional. The create new report VI opens Excel but throws error (-2147167262- from automation open VI) when I try to open MS word. please help...

Hi Leo22,
Does this error occur if you use any of the example programs that come shipped with LabVIEW? I would try opening one of the examples that write data to Word and see if those give you an error. Also, have you tried just putting down a New Report.VI and change the report type to Word? If this simple vi (that's all you need to open Word) breaks, I would check to see if there are any instances of Word still open. Check the task manager to see if any word processes are still open. There should not be a problem accessing Word 2003 from LabVIEW 7.0. If neither of these solutions work, please give some more detail about your application and we can research further. Thanks!
Jeremy L.
National Instruments
Jeremy L.
National Instruments

Windows 7 with labview 8.5 and NI-8451

Hello,
I am using LabVIEW 8.5 with NI-8451 device on Windows 7. I installed 1.1 driver for NI-8451, but I am unnable to access any subVI connected with NI-8451. Can you advise?
Thank you.

Hi miso2562,
The issue is most likely compatibility between the drivers, LabVIEW, and the OS. LabVIEW 8.5 is not supported on Windows 7 (only up to Vista), and NI-845X 1.1 is not supported on Windows 7 either (only up to XP). Also, NI-845X 1.1 does not support LabVIEW 8.5 either (only up to 8.2).
Ideally, if you use Windows 7 you should have LabVIEW 2009 SP1 or newer and NI-845X 2.1 or newer (1.1.4 could work as well). If you can move to XP, LabVIEW 8.5 and NI-845X 1.1.1 should work.
References for compatibility:
http://digital.ni.com/public.nsf/allkb/B972242574D4BB99862575A7007520CB
http://download.ni.com/support/softlib//i2c_spi/ni-845x/1.1/readme.htm
As for your main question "unable to access any subVI connected with NI-8451", do you mean they do not show on the function pallete?
- FCTesting

Simple Math VI crashes LabVIEW 2009 SP1

Hi,
We previously filed a related issue, (ref #: 7302858). The last problem was resolved by
Andy Hertzka from NI re-compiled the VI and send it back to us. That re-compilation solved the LabVIEW crashing.
However, the interesting crash happens again.
I attached a working VI before the change and a non working VI after the change and save. All the change I applied to the VI is
1. Add the "Word bits" as a connector on the diagram
2. Save it Then the VI begin to crash LabVIEW 2009 SP1.
Before the change, the VI was functioning all right.
Any idea why this might be happening? Can you try to recompile the non_working version and send it back to me for a try?
Thanks,
Tian
Attachments:
Non_working_AfterChange_RECOMPILED LRSample_U32in_U32output.vi ‏110 KB
Working_B4Change_RECOMPILED LRSample_U32in_U32output.vi ‏110 KB

Tian,
Like Andy I was unable to see why this code is unstable on your machine. I am able to run the code fine on my computer without any problems. Looking at the code on the block diagram I do not see any major "crash worthy" issues with it.
I have resaved the VIs like Andy had in order to fix your issue. By the way what OS are you using, windows 7? It might be helpful to save the log file for the LabVIEW crash. You should get this option when LabVIEW is restarted.
<Joel Khan | Applications Engineering | National Instruments | Rice University BSEE>
Attachments:
Non_working_AfterChange_RECOMPILED LRSample_U32in_U32output1.vi ‏108 KB
Working_B4Change_RECOMPILED LRSample_U32in_U32output1.vi ‏108 KB

NI Goop Wizard not working with LabVIEW 2009

I have added the NI Goop Wizard using VIPM (VI Package Manager) into my LabVIEW 2009 SP1 installation however it is not working. Whenever I select Create New Class from the drop down (same applies to menu selection) nothing happens and the drop down returns to it's default selection. I have tried this on 2 PC's both with 2009 SP1 installed, both exhibit the same unwanted behaviour. One of the PC's also has LabVIEW 8.2.1 installed also with NI GOOP Wizard and this installation works fine.
Anybody using GOOP Wizard with 2009 ?
Cheers
Chris
Don't forget to give Kudo's for a good answer !
LabVIEW Champion
Certified LabVIEW Architect
Certified TestStand Architect

Hi there Chris,
Off the top of my head it's my understanding that NI GOOP wizard is legacy software that was made redundant by the native GOOP tools in LabVIEW 8.2.0 and later.
In light of this it's a bit confusing that everything is working fine with 8.2.1 for you. Is there a version to the NI GOOP Wizard that you are using?
I had a search across the website but I'm afraid I haven't found any other examples or poeple using the GOOP Wizard in LabVIEW 2009 or 2010.
Kind Regards.
Rhys
Applications Engineer
National Instruments

Favor to ask : can you open this labview 2009 Vi and save it for me in a Labview 8.6 readable vi ?

Hi guys,
I have a favor to ask : May somebody would be nice enough to open this Labview 2009 VI and save it in a Labview 8.6 readable VI ? You'll probably have some missing blocks cause I use specials ones but I don't want to have to re-make all the VI.
Thanks you very much
G.
Solved!
Go to Solution.
Attachments:
Control3.vi ‏29 KB

notimperial wrote:
Probably not the right place to do this, but could someone onpen this in labview 2010 and save it in a format compatible with labview 2009?
Thank you in advance
You are right we have a thread for this here.
http://forums.ni.com/t5/LabVIEW/Downconvert-VI-Requests/m-p/1067229
Here is your vi please use the downconvert thread next time.
Tim
Johnson Controls
Holland Michigan
Attachments:
WFMreaderIII.vi ‏53 KB

Application builder for Lab View 8.6.1 , 2009 SP1 and 2010 SP1

All 3 Versions seem to have huge flaws. With 8.6.1 When trying to build and application I get a duplicate name error and the application won't work. With 2009 SP1 I get Error 1003 broken VI when I have no broken VI's. Again Application won't work! With 2010 SP1 After the application is built for some reason lab view can no longer find the Excel sub VI's no matter how I place them in the build. And again application doesn't work. With all 3 versions the Vi's and over all programs work perfectly in the development environment. The application builder seems extremely flawed.
I would currently like assistance with 2009 SP1 problem the Error 1003 broken VI. I have reinstalled and rebooted my machine several times , tried including as much as possible in the build and still get the error about a broken VI. That works perfectly in the development environment. Please HELP?
Thank You
Attachments:
Broken VI.gif ‏8 KB

Scott,
Good afternoon, I'm sorry to hear you are having problems working with the application builder, hopefully I can help you get to the root of this problem.
What steps have you taken to try and resolve the error? This error can be caused by a variety of things. The link below details 8 potential solutions that may help resolve your error.
http://digital.ni.com/public.nsf/allkb/705C2ECA081F3C7986256C0F00559B02?OpenDocument
I would recommend starting with these steps. Let me know if any of these solutions work for you.
-Nick-
Nick C | Staff LabVIEW Platform Product Support Engineer | National Instruments

LabVIEW 2009 SP1 - Incorrect icon in connector pane palette

In LabVIEW 2009 SP1 (I don't have 2010 yet to check it) there seems to be a minor bug in the connector pane palette.
One of the connector patters appears twice, but when you select the second one, it shows up as the missing pattern.
I'd post an image, but that function seems to be broken getting through my company's proxy server. So image attached (I hope).
In LabVIEW 2009 SP1 (I don't have 2010 yet to check it) there seems to be a minor bug in the connector pane palette.
One of the connector patterns appears twice, but when you select the second one, it shows up as the missing pattern.
Troy
CLDEach snowflake in an avalanche pleads not guilty. - Stanislaw J. Lec
I haven't failed, I've found 10,000 ways that don't work - Thomas Edison
Beware of the man who won't be bothered with details. - William Feather
The greatest of faults is to be conscious of none. - Thomas Carlyle
Solved!
Go to Solution.
Attachments:
Connector pane.PNG ‏4 KB

Troy K wrote:
I guess everyone else is using "proper" connector patterns instead of these crazy non-standard ones.
So you must be using crazy non-standard connector panes, or you would not have discovered this bug. Right? Actuall this is a good catch for it to go unnoticed for this long.
- tbob
Inventor of the WORM Global

LabVIEW 2009 SP1 Run-Time Engine (Minimum) (32-bit) for Windows - Supported Features

Hi,
Can some one please point out what features are supported by the LV RTE (Minimum ) [LabVIEW 2009 SP1 Run-Time Engine (Minimum) (32-bit) for Windows]
1) Is there a limit on the size of the exe which can be run on it?
2) Will this support additional modules like DAQ etc.,? Or do we have to chose the regular installer ( 170 Mb ) for that purpose?
3) If a list of what it does or does not support is available, it would be extremely helpful.
Thanks In advance.
Regards,
Vijay

Anand,
I did go through both the links that you had sent earlier before posting on the forum. For eaxample refer the following link where it says,
http://joule.ni.com/nidu/cds/view/p/lang/en/id/1599
It does not contain the full run-time engine, but will allow some executables to run.
1) What do they mean by 'some' executables. Is there a list of yay's and no's available?
2) Can someone from NI reply to this and shed more knowledge?
Regards,
Vijay

Bug report: on LabVIEW 2011 SP1 and Windows 8 'Open URL in default browser.vi'

Dear colleagues,
Here is a bug report.
Culprit: 'Open URL in default browser.vi'.
System: Windows 8, Professional. LabVIEW 2011 SP1.
Abnormal behaviour and steps to reproduce:
Above mentioned VI doesn't work when LabVIEW was started with administrator privilegies. And it works as expected when LabVIEW running in normal (non-administrator) mode.
Looking forward to see this fixed.
Best regards,
Igor Titov.
CLD.
=========================
Igor Titov, CLA
WebPager - put LabVIEW front panels into the web page
Labicom.net

Hi Igor,
Unfortunately LabVIEW 2011 SP1 does not support Windows 8. I tested this behavior with LabVIEW 2012 SP1 on Windows 8 and everything worked correctly.
Regards,
Jeff Peacock
Product Support Engineer | LabVIEW R&D | National Instruments

Using RSLinx OPC with Labview 2009 SP1 and Getting Wierd Problem

Similar Messages

Maybe you are looking for