LabVIEW
Error 1149 and Error 1000 occurred at Invode Node .vi
Solved!
I got error 1149 when,
Launch Main Menu then run >>Back Button
Launch Main Menu then run >> Default Data >> Back Button
Launch Main Menu then run >> Default Data >> 2 Bus System >>Back Button
Launch 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:
Launch Main Menu then run >>Back Button
I don't see any "back button" in your "Main Menu"…
Why do you think you need to call all VIs dynamically?
Why don't you use ordinary subVIs?
- Why are all frontpanels so huge?
- Why don't you cleanup the block diagrams?
- Why is there no project file to organize your project?
- There are missing VIs in your RAR file…
- Why do you use RAR instead of ZIP? ZIP files can be unpacked by any modern OS by default, while RAR requires additional (proprietary) software…
- Why do you hide terminal labels in the block diagram?
- Why do you even have frontpanel elements with an empty label???
- What exactly do you want to achieve with those "Back" buttons? The VI will not stop…
- Why are there 3 "T"s in the back button text?
- Why has the "FAULT ANALYSIS" button a label of "Fault Analysis Fault Analysis"?
- Why don't you read those latching buttons in their corresponding value change events???
I don't see any "back button" in your "Main Menu"…
I might have confused there, there is no back button in Main Menu and its my mistake. I should double check the next time i post something.
- Why are all frontpanels so huge?
- Why don't you cleanup the block diagrams?
- There is no reason as of why it is huge and messy.
I want to focus on the main functions of my project first since i am fairly new i.e Opening subvi's through the use of buttons.
- I thought putting them in the same folder is the same as organizing my vi's.
- There are missing VI's because those Vi's are empty so I excluded them.
- Will use ZIP files as of now thank you.
- For the terminal label, is my mistake and i should have shown them to make things easier.
- 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" - Thank you for pointing out the spelling mistake of "TTT"
- I am not sure why the label is "Fault Analysis Fault Analysis"
- Why don't you read those latching buttons in their corresponding value change events???
- Did you mean the button behaviour?
I just followed a youtube example that is why im calling them dynamically.
Why do you think you need to call all VIs dynamically?
Why don't you use ordinary subVIs?
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.
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?
I just followed a youtube example that is why im calling them dynamically.
Why do you think you need to call all VIs dynamically?
Why don't you use ordinary subVIs?
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!
I have changed it to use "Back" button to stop the loop but it gave me another Error 1026 and did not close the "Bus system Panel" front panel.
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?
Okay I did the ordinary subVI caller.
Sometimes the back button works by closing the vi and sometimes the front panel got stuck/frozen unable to close the vi.
Not sure why... Anyways it still works sometimes so its fine.
Another thing I want to implement, at "Fault Analysis Panel.vi" there is a "menu" button. I would like to reopen the "Main menu" panel by means of the "menu" button.
I tried adding SubVI for main menu but it seems I cannot.
Hi cute,
@Rusyaidi_arif_cute wrote:
Okay I did the ordinary subVI caller.
Sometimes the back button works by closing the vi and sometimes the front panel got stuck/frozen unable to close the vi.Not sure why... Anyways it still works sometimes so its fine.
You need to apply the very same settings in all your VIs:
- "Back" button as "latched when release" (default setting!)
- the button's terminal inside the event case
- the button value used to stop the loop
- the VI settings to close the frontpanel when finishing
@Rusyaidi_arif_cute wrote:
Another thing I want to implement, at "Fault Analysis Panel.vi" there is a "menu" button. I would like to reopen the "Main menu" panel by means of the "menu" button.
I tried adding SubVI for main menu but it seems I cannot.
You want to call your main VI from a 3-level deep subVI: this is called recursion!
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?
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:
