LabVIEW ARM break after update Front Panel during debug

I try to debug the vi by Ulink, the vi just show the LED blinking for 500ms on/off with while infinity loop, after click run button the loop continue working about 5 second and then break button actived with front panel update. Is this normal working?
Thank you

After I click Run button on the toolbar the vi start ranning, the LED blinking show on the hardware but not update to the vi front panel, around 3 second the vi stop (like a we click on Pause button on toolbar) and update the status LED to front panel.
I used ULINK1 for this example, I don't know this cause of the problem or not.
Thank you.
Attachments:
vi_stop.JPG ‏25 KB

Similar Messages

[General Question] redrawing and updating front panel objects

Hello,
I have several questions on this topic.
1) Is there a difference between redrawing and updating the front panel? (I assume so, but when a control is updated it will be redrawn at the same time, right?)
2) Is redrawing = rendering? In the case of decorations I think they need only to be rendered once (if fix/static) and stay in memory so that it is available for the gfx-card...
3) Are decorations redrawn or updated by LabView with every loop?
4) Is there a way to prevent LabView from redrawing and/or updating front panel objects (like controls, indicators and decorations)?
    When I put indicators into case-structures they are only updated when the case in which they are placed is executed but they will be obviously still redrawn.
    In another case when I disable visibility of those indicators they will not be redrawn anymore but be updated in the background.
    So when I put these indicators into a case-structure and combine it with toggling the visibility I could stop LabView from updating and redrawing them.
    Is this correct?
    Is there another way to prevent LabView from redrawing single objects? (at best leave them somehow visible)
Many thanks in advance!

Nocturn wrote:
Hello,
I have several questions on this topic.
1) Is there a difference between redrawing and updating the front panel? (I assume so, but when a control is updated it will be redrawn at the same time, right?)
2) Is redrawing = rendering? In the case of decorations I think they need only to be rendered once (if fix/static) and stay in memory so that it is available for the gfx-card...
3) Are decorations redrawn or updated by LabView with every loop?
4) Is there a way to prevent LabView from redrawing and/or updating front panel objects (like controls, indicators and decorations)?
    When I put indicators into case-structures they are only updated when the case in which they are placed is executed but they will be obviously still redrawn.
    In another case when I disable visibility of those indicators they will not be redrawn anymore but be updated in the background.
    So when I put these indicators into a case-structure and combine it with toggling the visibility I could stop LabView from updating and redrawing them.
    Is this correct?
    Is there another way to prevent LabView from redrawing single objects? (at best leave them somehow visible)
Many thanks in advance!
redraw vs update
Yes threr is a difference. A control is redrawn when LV decides to update the GUI. Look into "syncronous" setting for controls that forces update when value changed. These tags and thesse tags may help out abit.
Q2
Not sure about equality but decoartion may need redrawn if there is overlap of chanable objects.
Q3
i have observed decorations that failed to update on occation so I suspect they are only update when required.
Q4
LV will update the value for a hidden control but will not update its image. Same if the object is ona hidden tab page.
No wawy that I know of to prevent an update of a single object with out going to extremes. The Front pnale property "DeferFPupdate" will inhibit FP updates while true and allow then when set false. I use this when doing a lot fast GUI updates so allow the changes to accumulate and be apllied only once.
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

How to get Labview RT to Display a Front Panel on the Graphics port

I suspect that this post belongs on the feature request board but I'll ask anyway.
Most of my systems require a seperate PC for a SCADA/HMI/User interface linked to the RT controller using Network Published Shared Variables.
I understand that Remote Panels and Web Interfaces are also an option, bu still requires a PC to Access them.
I use high end RT controllers such as PXI, CRIO, and of 3 hours ago Desktop PC's.
Each has a DVI or VGA port connected to a graphics processor.
What I would like to be able to do is display my main VI front Panel to a connected monitor.
A possible solution is to use a windows OS but it is no good for a precision realtime system.
Any thoughts?
iTm - Senior Systems Engineer
uses: LABVIEW 2012 SP1 x86 on Windows 7 x64. cFP, cRIO, PXI-RT

Dan,
As above, Web interface still requires additional hardware of some sort.
Apple is a closed system so loads of prlems with 1/2 the market,
I am warming up to the hypervisor, I just don't like the idea of it taking out an entire core (on a dual core system). And needing a windows licence to go with it as well.
A quad Core PXI puts a gaping hole in my budget, makes a second PC not seem so expensive.
Would be great if I could get it on a Desktop, quad cores are pretty cheap now.
iTm - Senior Systems Engineer
uses: LABVIEW 2012 SP1 x86 on Windows 7 x64. cFP, cRIO, PXI-RT

How to update front panel immediately with any control change in LabVIEW7.0?

I have a lot of controls on the front panel. I want my 3D plot to be updated with any of them changed. Currently only one control's change can result in the update even if I do have done changes on other controls .. that's to say, only one specific control's change can activate the front panel updating ... That's not what I want. So how to make the front panel updated immediately like VC?
Many thanks!

I solve this problem by combining the event structure with a classical state machine. The classical state machine is a case inside a loop with either an enum or string shift register defining the actual state. In the idle case of that structure is the actual event structure which handles the UI.
Whenever I need to trigger a specific action which could happen from multiple locations I actually place the handling code in a specific case in the outside state machine and just wire from the actual event case the according state out to the shift register.
This architecture allows for a very flexible and extende state machine programming with the event structure doing all the UI event handling and the state machine doing the more involved actions or series of actions
Rolf K
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Unable to play any music after updating FRONT ROW TO 1.2.2

Please help, my Front Row refuse to play any music, after updating to 1.2.2 a day ago.
it shows all the folders in the iTune and the playlists but none of the songs in the folder, you keep pressing play and pause button and it TAKE YOU TO A shufle and the n ext one massage says "A PROBLEM HAS OCCURED".
It play the music videos and movies fron Front Row.
Please anyone enlighten me with your wisdom.
L. Namgyal
iMac inTel Mac OS X (10.4.7)

Hi
I have the excact same problem, however the problem is in my case not the upgrade in Frontrow, as the trouble was present before aswell. Everything works fine for me ONCE, but if i return to my desktop after having activated frontrow, and then reactivate it, i get the same error as you. I can solve the problem by Quiting FR and then relaunching it again, but this is not acceptable.

LabVIEW Real-Time and Remote Front Panel MemoryManager.cpp line 437 error

Hi all,
I'm using a smartcamera (NI 1742) with LabVIEW Real-Time 8.6.
When I look at the Front Panel with the web browser and I close the browser or I Stop the executable, I always get this error: MemoryManager.cpp line 437. I've checked if someone else had this error, but I guess I'm the only person who got this error. I saw someone who had the MemoryManager.cpp line 406, but mine isn't on this line.
The application works well, but when I got the error, I need to reboot the smartcam to get it works. In my application, I use the Modbus library and I read/write binary file in the hard disk of the smartcam....
Anyone knows the solution?
Thank you very much
Stephanie

Hi again,
Still didn't find the problem on my side. Here's a picture of my code. If I put the code surrended in red at place (1), I don't get the error, but if I put the code at place (2), I get the error. Why oh why....?
I get the error when I close the browser or click Back button of the browser or Stop the application with the red dot or stop the application with the Quit button on my front panel.
This morning I found a post on this forum about getting an error using Property node and Remote panel (http://forums.ni.com/ni/board/message?board.id=170&message.id=252705). I did what they suggest: wire the property output to an indicator and it works (disable "Enable automatic error handling dialod" didn't work... I don't know why)... until I put extra code in my VI.
I really need help please!
Thank you
Stephanie
Attachments:
MemoryManager line 437 error.JPG ‏228 KB

Lync 2013 updating databases after updating Front End servers

We have a front-end server pool consisting of 3 Lync 2013 servers and a back end of 2 SQL servers using SQL mirroring. All servers are Windows 2008 R2.
Following the instructions in
http://support2.microsoft.com/kb/2809243 , I verified that the servers were all ready for updates, then I ran the
Stop-CsWindowsService -Graceful cmdlet to stop the Lync services on the first FE server, then I ran LyncServerUpdateInstaller.exe to install the updates. After the updates were installed, I restarted the server, waited for Lync services
to all start, then repeated the process on the next 2 servers in turn. This was all successful.
I am now looking at step 2 in this document, applying the back-end database updates, and I have a problem and some questions. The problem is that all the databases had the principal copy on the mirrored SQL server. I ran the recommended Invoke-CsDatabaseFailover
-NewPrincipal Primary cmdlet repeatedly, using all the database types I could find, but I still have two databases (database names
xds and lis) on the mirrored server. Since the cmdlet requires a database type, what type of databases are the xds and the lis databases?
Once I get that done, I an still unsure of exactly what to run to update the databases. The KB article states to run Install-CsDatabase -ConfiguredDatabases -SqlServerFqdn FEBE.FQDN -Verbose .  Do I type this in exactly
as stated, or is FEBE.FQDN a variable for our SQL server or some other entity in our environment? If I do use the actual SQL Server name in that, do I run it twice, using the name of the mirrored SQL server the second time?
Thank you very much for your help.

Hi Logan Burt,
Central Management store database files
Data file or log purpose
                Xds.ldf
Transaction log file for the Central Management store
                Xds.mdf
Maintains the configuration of the current Lync Server 2013 topology, as defined and published by Topology Builder
                Lis.mdf
Location Information service data file
                Lis.ldf
Transaction log for the Location Information service data file
And you could verify if Lync Server 2013 database updates have completed successfully.
How to Verify if Lync Server 2013 Database Updates Completed Successfully
http://blogs.technet.com/b/dodeitte/archive/2013/07/02/how-to-verify-if-lync-server-2013-database-updates-completed-successfully.aspx
Best regards,
Eric

Bug: Labview doesnt start after Update to LV 7.1.1

Hello,
someone here with solution for this problem?
You can reproduce it by doing these steps:
1.) Install Labview 7.1
2.) Install an executable Labview-program compiled/created with LV 7.1.1
3.) Install the LV-Update 7.1.1
4.) Try to start Labview.exe
Here I get an pop-up with the text:
Executable version (LV7.1.1) doesn´t match resource file (LV7.1)
[OK]
The only thing i can do is to uninstall Labview 7.1.1 and the Runtime 7.1.1 and the reinstall Labview 7.1.
But there is no way to install the update on a normal way.
I think the problem is, that the executable programm already installs the Runtime 7.1.1 and makes some registry-things. So when installing the update after that, then the registry is already 1/2 updated and something goes wrong.
Perhaps i only need one more registry-entry to get rid of the pop-up.#
Thanks for your help

Edit:
Executable version (7.1.1) doesn´t match resource file (7.1).
Check your configuration.
[OK]
This is the full message-popup.
The problem has to be somewhere else. On another computer i tried the steps i described above but there i had no problems to update.
So the main-question is: What can i do against this popup?

How can I show and hide an image or a decoration on the front panel during execution of the vi?

Hello,
I've made a user interface with a little grafic description.
That description should change depending on user actions, e.g. if the user switches a button, some lines should disappear and some other lines should appear.
I thought some decorations could be shown and hidden via something like a property node, but that is not possible. Images can also not be hidden during execution of the program.
Is there any posibility to change a grafic user interface?
Johannes
LV 7.1
Greetings Johannes
Using LabVIEW 7.1 and 2009 recently
Attachments:
LV_Grafic.JPG ‏21 KB

Thanks to Tim for drawing what I suggested as option while I had some real work to do.
There is a trick of overcoming the index problem that was presented/devloped in the forum in the last month's:
You can place the decoration inside a cluster, so you can use the lable of the cluster to adress the decoration you want. The data type of the cluster doesn't mather for this, so you will hide the control/indicator. And you colour the cluster transparent (hint: right click with the coloring tool and use space to toggle).
Felix
www.aescusoft.de
My latest community nugget on producer/consumer design
My current blog: A journey through uml

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.

How does one empty an array during runtime with a front panel switch

I can 'empty array' from the front panel during runtime but I want to empty all arrays (20) from my vi with a front panel switch (see screenshot). I have used replace array subset and reshape array with no success. Any help would be appreciated
Attachments:
TempScan_screenshot.JPG ‏26 KB

Hmm... You can empty an array by reshaping it or by assigning a constant empty array - using local variables or properies of the original control (see attached example... hmmm... not the best one ). May be you can attach a part of your code to see what is better to do in the given case.
Attachments:
reset_table.vi ‏20 KB

Publishing VI's on the Internet without open front panels

I'm using LabVIEW 6.02 and are publishing VI's on the Internet. I'm wondering if it is possible to publish VI's without having the front panels open when you are running the program?Or do they have to be open to be in memory and to be able to get updated front panels?
(I use the .snap command so it is possible to refresh and get updated VI panels.)
I also wondering if the only difference between .snap and .monitor command is that you can use the refresh command with monitor so the labVIEW display will automatic updated itself. This is not possible with the .snap command?
Thanksregards Anne

I've never tried to exactly what you are talking about but a similar issue comes up when printing. A front panel normally won't update unless it's open. The way to insure that it does is to have at least one property node on the routine's block diagram. When LV sees the property node, it goes ahead and updates the front panel even when it's closed.
Hope this helps...
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

Background color of front panel when printing

My vi has a control named "print" which allows the user to print the front panel during execution. The background color of the front panel is white, to avoid filling the printed page with any color. In labview 7.1 (and also 6.0), this worked perfectly. I recently updated to labview 8 and now the background color of the print is gray. Does anybody have any idea how to avoid this?
I am using the "print panel.vi" found in the "vi.lib\utility\printvi.llb". I also tried with the "Easy Print VI Panel or Documentation.vi", with the same result. The same problem also occurs when exporting the front panel to a ".png" file.
Best regards

I tried with different colors, without any success.
I think that this is a bug ! Good catch !
Chilly Charly (aka CC)
E-List Master - Kudos glutton - Press the yellow button on the left...
Attachments:
Background color bug.vi ‏11 KB

How to place event callback components and "main-VI" components in the same Front Panel?

What I'm trying to accomplish:
Place a .NET component, which generates events, and other standard LabVIEW components in the same Front Panel. The standard LabVIEW components should be updated when events are being generated in the .NET component.
How I tried to solve it:
Problem:
The event callback code must reside in a separate event callback VI. In order to "pass the event up" to the main VI I tried to use a global variable. The interrupt does occur:
but I was hoping that the string indicator would be updated when the event occurred, but it wasn't.
Questions:
What's the best way to solve what I try to accomplish? If I want to solve the problem on the picture above, how would I do it (it may not be the best solution, but I'm still curious what's wrong)? Please feel free to be over-explicit when replying as I am novice LabVIEW programmer. Thanks in advance for any help.

There are two bundle functions for creating clusters. The function simply called Bundle operates almost exactly like the Build Array function I showed. The type of the output cluster depends on whatever you wire in as inputs. You don't have to supply a specific type parameter.
The function called Bundle by Name takes in a specific type of cluster in the top input and allows you to fill in the values of that specific type of cluster. To create the specific type of cluster you want, you need to create a cluster of string references. Here's how to do that:
Go to the Front panel and drop down an empty cluster shell.
Go to the Refnum palette and drop down a Generic Control Refnum. Now here's a cool trick to turn that generic refnum into a string-specific refnum (a so-called strictly-typed refnum). Grab a string from the controls palette and drag it into the Generic Control Refnum. Once you drop it, you'll see the refnum change its icon to display a string picture.
Make copies of this string refnum (as many as you need) and add it to the cluster shell.
Now, if you're making specific types of clusters to work with, now is the absolute best time to learn about typedefs if you haven't already. It will save you hours and hours (if not days) of development time in the future. Trust me!
Jarrod S.
National Instruments

How can you "enable front panel datalogging?"

In the Labview User Manual, it says that "You can create and read datalog files by enabling front panel datalogging." How do you go about "enabling front panel datalogging?"
Any help would be greatly appreciated.

From a LabVIEW only perspective, you can enable control (front panel) datalogging through the menu Operate>Data Logging->. If you bind a log file to the VIs front panel it will generate a binary file with the state of the controls in it, when you execute Operate>Data Logging>Log... (I could not find a way to execute this Log... by VI server programmatically - Maybe someone else?)
From a LabVIEW DSC perspective you can generate a Logos Remote connection to a tag (e.g. with the HMI Wizard). And when you have enabled that this tag has to be logged, the LabVIEW DSC Engine will store/log the value into the Citadel database.
Hope this helps
Roland
PS:
Not updated however maybe helpful:
80E?OpenDocument>Using Enable Database Access to Retrieve Data from a LabVIEW VI's Log File
Front Panel Data Logging and Retrieval (old Example)

LabVIEW ARM break after update Front Panel during debug

Similar Messages

Maybe you are looking for