I got error 1149 when, Launch Main Menu then run >>Back Button Launch Main Menu then run >> Default Data >> Back ButtonLaunch Main Menu then run >> Default Data >> 2 Bus System >>Back ButtonLaunch Main Menu then run >> Default Data >> 2 Bus System >> Fault Analysis >> Back Button Error 1000 when,Launch Main Menu then run >> Default Data >> 2 Bus System >> Fault Analysis >> Menu Button

Hi cute, @Rusyaidi_arif_cute wrote: I did make it work through recursion. But it opens multiple "Main Menu" vi panels with 'clone' instead of the previous 'main menu.vi' front panel. How do i stop it from making more front panels and go back to the first level of subvi? Using recursion and clones isn't the way you should go with your task, instead you should implement a proper architecture to your code! You should not try to call the mainVI from a several layer deep subVI, instead you end all the subVIs to get back to your mainVI! To do so is quite easy in your current approach: spend a boolean output in each subVI to signal the caller it should also end its loop. Use the connector pane of your subVIs! When a subVI outputs a TRUE then the caller also should end the loop: you just need to connect to the stop condition of the caller… Example:

Hi cute, @Rusyaidi_arif_cute wrote: I have changed it to use "Back" button to stop the loop but it … did not close the "Bus system Panel" front panel. Because the button is initially in TRUE state and you switch it to FALSE. This will not end the loop and so not close/quit the subVI! You should set the button to initially FALSE and change the switching mode to (default) "latch when released"! @Rusyaidi_arif_cute wrote: it gave me another Error 1026 Where does the error exactly occur? Do you call the VI already as ordinary subVI in the caller?

Hi cute, @Rusyaidi_arif_cute wrote:There is no reason as of why it is huge and messy. I thought putting them in the same folder is the same as organizing my vi's. What I am trying to achieve with "back buttons" is by closing current Vi's and go back to previous VI e.g (Main Menu>> Default Data >> Back Button), I want to close "Bus System Panel.vi" and reappear the "Main Menu.vi" There's no reason to create huge frontpanels when you "just" want to test functionality… A project file does more than just putting some VIs in the same folder… When you "just" want to go back to the calling VI then you should use the "BACK" button to stop the loop inside your subVI. As you set the (default) behaviour of closing the frontpanel when finishing you don't need to fiddle with that property node at all! Example: @Rusyaidi_arif_cute wrote: Why don't you read those latching buttons in their corresponding value change events??? Did you mean the button behaviour? Why do you think you need to call all VIs dynamically? Why don't you use ordinary subVIs? I just followed a youtube example that is why im calling them dynamically. If you have any suggestions on how to improve the way I call subVIs, please do let me know.Also i did all of these in a hurry as my project deadline is coming. Yes, I'm talking about the switching behaviour! Any latching buttons should have their terminal inside the value change event case! Using Youtube often gives bad results. There are learning resources collected at the top of the LabVIEW board!

LabVIEW

Error 1149 and Error 1000 occurred at Invode Node .vi

Solved!

Author

I get it now!.😀 Thank you for your insights sir!

Message 11 of 11

(37 Views)

LabVIEW

Error 1149 and Error 1000 occurred at Invode Node .vi

Re: Error 1149 and Error 1000 occurred at Invode Node .vi