Red tick on front panel of client VI unable to sort problem

Hi I am having a problem with a client\server application. I am running a Periodic I/O server and have created my shared variables. When I create my client VI I am getting a red tick instead of green, can anyone give me some ideas as to what I am doing wrong.

Hi Spar,
Thank you for contacting National Instruments. I wondered if you could give a little more details on your application so we can try and work out what is going on. You mentioned about your Red tick on the front panel, could you possibly attach a screenshot of what you are seeing and perhaps attach your project, if it is not too big.
Many thanks,
Andrew McLennan
Applications Engineer
National Instruments

Similar Messages

Satellite L500D - What is that annoying red light on front Panel?

Hello there,
On my L500D I have the normal five system indicator lights on the front panel of the computer base, where they are supposed to be. But then, to the left of these lights there is this annoying red light that is very distracting.
But what is even +more+ annoying that not one, +not one+ owners manuals that I have read makes any mention of it, +not even a hint+. The owners manual mentions the other lights in their diagrams, +but not this one+. :-(
Now, I'm assuming that it is something really simple, and I am publicly displaying just how blind or dumb (or both) i really am. :-) But for the love all things Holy, and before I loose all my hair, can somebody tell me just what that red light is? ?:|
And, while you're at it, maybe you can tell me how to turn it off!! That would be very novel experience at the moment. B-)
Don't get me wrong, I really love my new L500D, my best investment by far, and it goes like the clappers, and I would write a wacky advert jingle about it and broadcast it across the world... if not for that annoying red light. ;-)
Please Help! (i)

Thanks a lot, guys!
I told you I was dumb, or blind. I fixed the problem. The annoying red light is now gone. Woohoo! :D But just for the record, I checked Jeka's link and found it meantioned and shown just as he said. But then I checked my owners manual again, the one on my HDD, and I am afraid that it is not mentioned anywhere, and if by some quirk of fate that it truely is there, then it must be very well hidden. None of the diagrams show it at all. Just my luck... :-(
Anyway. Thanks again, guys, my problem is solved. :p
MSRankin

How can i access remote front panel in RT with LabVIEW run time engine in client PC

Hi to all,
I have developed the RT application with cRIO 9075 integrated chassis. And i have access its remote front panel in client PC. Now i want to access the remote panel in the client PC without having LabVIEW runtime engine. If i connect the remote panel with that client, it shows only the vi border. i doesn't downloads the front panel.
How Can i access its remote front panel without LabVIEW runtime engine in the client PC?

You cannot view a remote front panel without the LabVIEW runtime - the LabVIEW runtime is what makes the remote front panel possible. What you will want to do instead is likely create a Web Service that you can access from a remote PC without requiring the LabVIEW runtime. However, this will require you to develop a web-based HTML or similar UI to interact with the VIs running on your system - NI hasn't yet created a way to export a LabVIEW front panel as an HTML'ish page.
-Danny

Display fuzzy logic firering rule in front panel?

Hi all,
I only can display the firering rule no. (attached 1.gif red circule) in front panel.
How can I also display the firering rule no. detail infomation (attached 2.gif) in display panel?
Can I show the .fc file (generate in Fuzzy Logic Controller Design)detail infomation in display panel?
Thanks
Fung
Attachments:
1.GIF ‏61 KB
2.GIF ‏79 KB

Stephen M,
Attached .fc file. Please help!
Thanks
Fung
Attachments:
FuzzyDesign_v5_height.fc ‏3 KB

Storage VI blocking on front panel interaction

For some reason that I can't figure out, the "write data" storage vi (and perhaps others) will block during
front panel interactions. For instance clicking on a ring button will block until you select something.
The button doesn't have to be on the same VI either. Also editing a separate VI, when you right click
and start looking for the right function in block mode or widget (I forget the labview term) in the Front Panel,
will block the write.
The problem with this is that my main program is saving data from a ring buffer, so if someone takes
too long making a selection, I've lost data. I attached a VI that can demonstrate the bug
(at least on what I can try it on). I've gotten the attached VI to work with labview 8.0 and labview 8.0.1
Attachments:
Storage Vi Bug.vi ‏42 KB

Hello,
Thank you for posting this well written description and
great small example which reproduces the problem! This seems to be only occurring with the
write data like you mention. I’m not
exactly sure the cause, but I filed a bug-report on it (3ZNC2Q3A), so we can
investigate here. I’m betting it has
something to do with user interface interactions between the controls and the
write measurement file VI, as components from each could run in the UI thread
and block each other. Unfortunately, I
don’t see any immediate workaround without having to change a few things up
with your program structure. For example,
instead of a ring, you could just have one or two checkboxes for the options
and see which the user has pressed. Because
the write file VI is the only one that is blocked, you could conceivably separate
your data acquisition thread and your file IO thread (many times it’s a good
idea anyway). Using the Queue datatype,
you could add all the data to the queue in the non-writing loop, and write to
file in the separate file IO loop. If
the write to file blocks the data will continue to queue and no data will be
lost. This is known as a
producer/consumer VI design pattern.
Your consumer would be the file IO portion of your code. Check out the tutorial of this structure here.
Are these alternatives acceptable? Unfortunately, with the way the write VI
interacts with the user interface thread I don’t see any way to avoid this
problem. I apologize for any problems
that have occurred as a result of this behavior.
Travis M
LabVIEW R&D
National Instruments

VI locks up when front panel is displayed

Hi
Firstly, I apologise if I’ve sent this to the wrong forum – I’m not sure if this is a TestStand or Labview related issue or possibly both.
I have a test procedure developed using Labview 7.1 and TestStand 3.1. It’s run from TestStand’s Operator Interface VI (full version), and executes about a dozen TestStand sequences in turn which call lower level VIs that perform the actual tests.
The code was written on a Dell GX240 Pentium 4 PC, with Windows 2000 + SP4 installed and runs without a hitch. However, I also have a second PC, same model & spec, but running Windows XP + SP3 instead of Win2K. I’ve also installed the same versions of Labview & TestStand on it, and copied across all my TestStand sequences & VIs into the same working directory. However, when I run the program on this machine, again using the same Operator Interface, it executes until about half way through and then hangs up.
In several tests, I call up a graphical user interface VI which displays a picture and prompts the operator to click on either a ‘Pass’ or ‘Fail’ button – the actual text being passed as a parameter. When the lock up occurs, the front panel is displayed, but there’s no picture and the buttons are blank. Up to that point, previous calls to the VI have executed ok.
If I modify the step that causes the problem, to call another VI - for example, a sub VI that doesn’t display a front panel - the new VI executes and the program continues to run. If I then change this VI’s configuration so that it’s front panel is displayed at run time, the problem re-occurs - the front panel outline appears but everything then freezes.
Attempting to close the front panel window, results in either error code –18001 and the message ‘an error occurred accessing the Labview ActiveX automation server’ being displayed or the Windows prompt to close Labview as it’s not responding. Usually, clicking ‘End Program’ causes the PC to crash out & re-boot.
Skipping TestStand sequences, whether they execute the GUI VI or not, just moves the point where the lock up occurs further down the list of tests, to the next step where the GUI VI is called. It’s almost as if something isn’t being closed properly when the program runs, and eventually reaches some limit, but why this doesn’t appear to effect the Windows 2000 PC, I’m at a loss.
Very much appreciate anyone’s thoughts.
Thanks
Bruce

Hi Bruce,
I found a KnowledgeBase article relating to the error you are seeing.
It describes error 18001 "Error occurred accessing LV activeX automation server".
Let me know if this helps you out.
This problem may also be due to how you have configured the Distributed COM (DCOM) settings on your machine. You will need to ensure that your DCOM settings allows the LabVIEW ActiveX Server to be launched and accessed through ActiveX automation. Even Administrator accounts can be denied launch and access permissions. To modify these permissions follow the steps below for Windows XP:
Login to Windows using a UserID that has administrator privileges.
Select Start»Run and enter dcomcnfg.exe. This displays the Component Services dialog window.
Navigate to Component Services»Computers»My Computer and select DCOM Config. Ignore the warnings that may appear.
Right-click on LabVIEW Application, TestStandLVRTS or the name of your LabVIEW ActiveX Server and select Properties to open the LabVIEW Application Properties dialog window. Select the Security tab.
You must give permission to the appropriate users so that they can access the LabVIEW server. You should give everyone access permissions and appropriate users launch permission. Only users who have launch permission will be able to access the server. Add permissions by selecting Customize and Edit for each of the three permission settings and manually adding permissions for each user.
I doubled checked that LabVIEW 7.1 and 3.1 are compatible with windows XP and they are. Just to make sure, it is 32bit or 64bit you are using?
Let me know how you get on.
Kind Regards
Lewis Gear CLD
Check out my LabVIEW UAV

Error accessing Remote Front Panel on RT Target after upgrade to LV2011

I'm upgrading a real-time application (target is a desktop PC running the LabVIEW real-time) from LabVIEW 2009 to 2011. Under 2009, it was possible the view the main VI remotely by browsing to a static HTML page that embedded the front panel. After upgrading to LabVIEW 2011, instead of the front panel image I get an error saying "Server does not support Remote Panels." I have already gone through the list of possible causes from "Server Does Not Support Remote Panels" Error When Connecting to Remote Front Panel, and none of these resolved the problem. I am using the standard LabVIEW web server, there is a direct ethernet cable connecting my computer with the real-time system, and I have recreated the web page to reference the correct plug-in version. I reformatted the RT system and then did a clean install of the components from LabVIEW 2011 (using the Add/Remove Software feature in Measurement and Automation Explorer). I also created a new test project with a new simple VI; I was able to access that VI remotely on port 8000, but not on the default port 80 (which used to work under LabVIEW 2009). What changed in the web server between LabVIEW 2009 and 2011? Can I use the standard HTTP port 80 to serve a static page with an embedded VI, or does this now only work on other ports (and if so, why)? Will I need to recreate my entire project in LabVIEW 2011 in order to get this working at all?

Got it working, after much experimentation. Seems to require installing exactly the right combination of items on the RT target, as some items (web services? web configuration? the "application web server"?) apparently run a separate web server - or instance of the web server - on port 80, which prevents remote front panels from being served on that port.

Print front panel of a compiled VI

Dear All,
I am using a subVi that prints the front panel of
a certain VI. My problems comes when I compile
with the App Builder to create and exe file because
then it does not print anything. Anybody knows
any solution?
Cheers,
Ernest

Look here, mayby this is your answer.
Waldemar
Waldemar
Using 7.1.1, 8.5.1, 8.6.1, 2009 on XP and RT
Don't forget to give Kudos to good answers and/or questions

How can I display the front panel of the dinamically loaded VI on the cliente computer, the VI dinamically loaded contains files, I want to see the files that the server machine has, in the client machine

I can successfully view and control a VI remotly. However, the remote VI dinamically loads another VI, this VI loaded dinamically is a VI that allows open others VIs, I want to see the files that contains the server machine, in the client machine, but the front panel of the dinamic VI appears only on the server and not on the client, How can I display the fron panel with the files of the server machine of the dinamically loaded VI on the client computer?
Attachments:
micliente.llb ‏183 KB
miservidor.llb ‏186 KB
rdsubvis.llb ‏214 KB

I down loaded your files but could use some instructions on what needs run.
It seems that you are so close yet so far. You need to get the data on the server machine over to the client. I generally do this by doing a call by reference (on the client machine) of a VI that is served by the server. THe VI that executes on the server should pass the data you want to diplay via one of its output terminals. You can simply wire from this terminal (back on the client again) to an indicator of your choosing.
Now theorectically, I do not think that there is anything that prevents use from getting the control refnum of the actual indicator (on the server) of the indicator that has the data, and read its "Value" using a property node. I have never tried this idea but it seems t
hat all of the parts are there. You will need to know the name of the VI that holds the data as well as the indicator's name. You will also have to serve all VI's. This is not a good idea.
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Front Panel binding of shared variables very slow initialization / start

Hello @ all,
I am using a server running Windows2000 and LV 8 DSC RTS for datalogging. All shared variables are deployed on that server.
I am now facing the problem, that all front panels running on the clients using the network shared variables on the server take very long to sync on startup. First the flags on the controls bind to the shared variables turn red, after up to ten minutes they start to turn green. The panels use up to 40 controls bind to the shared variables.
All firewalls are turned off. I tried to connect the client to the same switch the server is connected to. Same problem. Does anybody have a clue?
Thx for your quick answers.
Carsten

While I can't offer any solution to your problem, I am having a similar issue running LV8.0 and shared variables on my block diagram (no DSC installed).
When using network published shared variables, it takes anywhere from 30 sec to 4 min from the vi start for any updates to be seen. Given enough time, they will all update normally, however this 4 minute time lag is somewhat troublesome.
I have confirmed the issue to be present when running the shared variable engine on windows and RT platforms, with exactly the same results.
In my case, the worst offenders are a couple of double precision arrays (4 elements each). They will normally exhibit similar "spurty" behavior on startup, and eventually work their way up to continuous and normal update rates. Interestingly enough there are no errors generated by the shared variables on the block diagram.

How to open front panel of a VI running in RT.

Hi,
I have an application to read the encoder position using the cRIO program. I have made an executable and this application runs as startup application whenever the controller reboots. Right now, i am accessing the VI of the startup exe through Remote Panel connection. This works fine but everytime i close the remote panel , i have to reboot the controller for the next view.
So is there any alterntaive to open the front panel of the VI.
I tried using VIServer but ran into errors. (i tried using front panel -open property node.did not work)
Also i do not have any VIs stored on the controller. Only the exe is stored on the ni-rt/startup folder on the RT controller.
Please let me know how to open this VI.
Thanks.

Hi Ben,
When i close the remote front panel the first time, i am terminating the RT VI which is running on startup.
So i had to reboot everytime to access the remote VI. I guess that the VI (exe) should be continuosly running when the RT is started up. The remote panel only should be opened and closed. After I close the remote panel , i want a windows VI to be opened up.
I have a Windows VI which programmatically opens connection to the RT server for opening the remote panel. The VI runs. When the user clicks Exit on this RT VI, the VI running is stopped and then another windows VI opens up. This works fine for first time. Since the RT VI is terminated, second time , if I run, it says, VI not in server memory.
Is there a method to close the remote panel programmatically in the RT VI itself. I have a Exit button in this RT VI, so if the user clicks, Exit, the program has to be running, but the remote panel has to close. There is a method called close connection to client , but this does not work in RT , as this requires VI path.. Right now , when the remote panel RT VI is launced, to close the remote panel, i click on the 'close' button on the VI title bar. Again when the remote panel is launched, there is no error. but is there a method to close the remote panel in the server(RT VI itself). i have attached the VI.
Thank you.
Attachments:
Dummytest.vi ‏39 KB

Front panel of my Audigy 2 won't w

My front panel on my Audigy 2 won't work. I recently had to replace my motherboard and it won't work since then. It worked fine before. The mixer panel won't even give me the option of Line 2 and Auxilliary in, and my headphone jack won't work either. I don't think they're even getting power, though I'm not sure. I took the optical plug out to see if there was a red light showing, and there wasn't. The inputs and outputs from the back are operational.
I've read other threads on this and none of the solutions there have worked. I've re-connected cables, uninstalled and reinstalled hardware, and software. Still nothing. Only inputs from the back work. I recently had to replace my motherboard. I've tried updating drivers - nothing.
My motherboard is a GIGABYTE GA-K8NSC-939 Socket 939 NVIDIA nForce3 250Gb ATX AMD Motherboard. My processor is AMD Athlon 64 3000+ Venice GHz FSB 52KB L2 Cache Socket 939 Processor. I run Windows XP with both service packs installed (same as with my old motherboard).
Is my card broken?

There should be a light from the optical output as long as there is power to the dri've. Perhaps switch the power cable on that dri've with the cable that goes to your floppy, to see if that helps (in case the cable is faulty). It's possible otherwise that the dri've itself is broken.
Cat

How do I programatically open a LabView Front panel?

I want to use a test stand variable (perhaps a sequence global) to control whether certain VIs open their front panels, and wait for subsequent operator interaction. Can I get there using the API and something like this: "Step_TSInfoProp.TSInfo_StepAdditions.LVStep_ModulePathProp" ?
I tried passing a boolean to the VI and then having it optionally open its own front panel using the VI Server, but I could not see it because it would always be behind the TestStand Window.

Sean, The reason for doing this is that the client wants a "debug level" control of some sort. If set below some value, the VIs just do their thing, take their measurements, report, or whatever and go on their way blindly as what we expect a good test sequence to do. However when this value is set above some level (the threshold may be different for various categories of tests) the VI becomes interactive. This would allow an operator to see a measured value, and possibly tinker with the instrument parameters or the UUT, before continuing on. This might be similar to a single step command, but not necessarily pausing at every step. Inside of the VI I can test the value of the variable (either passed in through the connector pane or via the sequence context) and thus decide whether to be interactive or silent. I can also use the VI server to open my front panel or not. But in doing so, even though I try to make the VI panel frontmost, it is hidden by Teststand. If the VI attribute is "dialog" then it does show up on top of everything else, but unfortunately does so even when I don't tell it to open at all.
PC

How can I close all open subVI front panels, without closing my top level VI front panel when all VIs are built into executables?

I'm using the code shown in the sample VI discussed here: http://digital.ni.com/public.nsf/allkb/353A696A3F393D9B86256E8B007A2912
to close all open VIs except my top level VI. My top level VI is actually a separate executable and the sub-VIs are their own executables. All reside under the same project. It works very well if I'm running in LabView but will not work when I build them. I added all the sub-VIs to the Always Include box in my top level VIs properties which did nothing. I also tried adding them to the Startup VIs box. This allowed me to close them all programmatically from the top level VI but it also open all the VIs at once (which was expected and not desired). I think the problem is the executables are not able to see outside their own memory space so the top-level VI never finds any other open front panels to close. Is this correct? Is there another way to go about doing this?
Thanks!

Where do I begin…..
I’m using a “server” to control 4 “client” PCs. My server opens references to 4 VIs on each client then executes them sequentially. So on a normal day, the server will run everything itself and I will have no contact with the clients. But on a several occasions, I’ve needed the ability to walk up to one of the clients and run just one of the 4 VIs.
We are updating from LabView 6.1 to 8.5 and we want to run executables rather than VIs for various reasons. I have a new VI running on the client PCs who’s only function is to initialize the shared variables and open/close the VIs. I initially thought of making the remaining 4 VIs sub-VIs but I will loose the ability to run them individually. I think I would also have to rewrite the VI running on the server since the 4 references it originally opened do not exist. I don’t think you can open a reference to a sub-VI on another PC. Can you???
As you can see, this is a huge mess. I’m still pretty new with LabView so any help you can provide would be great.

How can I close a remote front panel by closing only the browser window?

I control a remote front panel in a browser (from the client PC). If I don't use the 'close' - button in my program to end the remote front panel, but instead of this the 'x' of the browser window (in the right bottom corner), my program won't be close, it continues on the server. Do you know how to end a VI by closing only the browser windows?
Thanks for any help!
wolfe

I found the examples. Thanks.
But I could not find a solution yet. Now I know how to end a VI by clicking on the x of the VIwindow.
My problem is, to end a VI by clicking on the x of the BROWSER window after I loaded and controlled a remote panel VI in a browser (e.g. IE).
If you have any ideas ... I'd be happy.
Thanks for your help.

Red tick on front panel of client VI unable to sort problem

Similar Messages

Maybe you are looking for