LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Core Palettes Missing


@RkTrey wrote:

Another observation: logging in as a different licensed user on the same affected machine, I do get the palettes back. 



That's really strange -- sounds like something in your Profile is messing up LabVIEW.  My inclination would be to caal NI with a Service Request (to avoid the hassle of deleting, then rebuilding, my Profile).

 

Bob Schor

0 Kudos
Message 11 of 17
(1,085 Views)

Hey @SpaceTrey,

 

I have a few questions, if you try and quick drop one of these functions (CTRL+Space) on the block diagram does it come up in the search? 

 

Also, if you go to the following location do you find the functions you are looking for there?

 

C:\Program Files (x86)\National Instruments\LabVIEW 20XX\vi.lib. This is where the function palette is pulling what is available.

 

Gerald M.
Applications Engineer
NI
0 Kudos
Message 12 of 17
(1,066 Views)

I'll use UDP Multicast Open.vi as an example here. 

I cannot find this using Quick Drop. Navigating to vi.lib\Utility\tcp.llb, I do see that vi on disk. 

 

0 Kudos
Message 13 of 17
(1,057 Views)

"

One simple thing you could try would be to delete the LabVIEW.ini file located in your national instruments folder for the version of LabVIEW that you have. It should be where your LabVIEW.exe file is located.

 

Make a backup of this file before you try this so you can out it back if it does not help.

"

I would have thought that would fix it IF...

 

LV was closed before deleting the ini file.

 

IN my ini I have the line

 

menuSetup="default"

 

Under the ...\menus folder I have a file named "default.txt"

 

Inside of that I have the word "Advanced".

 

Not much more I can offer.

 

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 14 of 17
(1,053 Views)

Strangely this does nothing to my palettes. What's more, that the palettes reappear using a different licensed user with the same LabVIEW.ini as I have in my... injured?... user profile is pretty perplexing. This may be the right direction though as I've done a bit of work on my palettes. I notice now that my palettes after reinstalling are the same as prior to uninstallation/ manual deletion of .\Program Files (x86)\... LabVIEW files. I'd like to persist the palettes I have and attempt to "Restore to Default" to see if that fixes the issue but I don't know where the palette definition files are stored on disk. Any ideas where those might be?

0 Kudos
Message 15 of 17
(1,039 Views)

Core palettes are in [LabVIEW 20xx]\menus.

 

Any edits you've done to the palettes are stored in [User Documents]\LabVIEW Data\[version]\Palettes\menus.

 

This is probably why another user account doesn't exhibit the issues...your edits are specific to the logged-in user.

 

If you don't mind managing your own edits to files in the LV install folder, you can add this token to your INI file, which will save palette edits to the LV install folder, which will make the palettes the same no matter which user is logged in:

 

InternalPaletteEdit=True

 

Note that using this INI token isn't officially supported by NI.

0 Kudos
Message 16 of 17
(1,035 Views)

Thanks Darren. On "Restore to Default", I get a "Restoring palettes to default failed!" dialog now but the palettes are in fact restored. ¯\_(ツ)_/¯

This gets me going without needing to use a remote session or maintain dual local sessions. I'll rebuild the palettes as needed.

0 Kudos
Message 17 of 17
(1,028 Views)