Custom Devices folder

Within the documentation, it says, "The Select Objects dialog box opens with the Devices folder as the root folder. By default, the Servers and Workstations folders are displayed along with any custom folders that you have created in the Devices folder. How does one create a custom folder?
All our workstations get registered in the Workstations folder. However, we now have a population of managed devices that we want to exclude from Bundle/Policy associations to the Workstations folder. I have a Workstations/Excluded from Management folder, but am now reading that devices moved into this folder still inherit the associations?!?! So ideally, I'd like to create a custom root folder to place my unique managed devices in so I don't have to go through all my bundles and change associates to accommodate these new devices.

Originally Posted by bkeadle
Within the documentation, it says, "The Select Objects dialog box opens with the Devices folder as the root folder. By default, the Servers and Workstations folders are displayed along with any custom folders that you have created in the Devices folder. How does one create a custom folder?
All our workstations get registered in the Workstations folder. However, we now have a population of managed devices that we want to exclude from Bundle/Policy associations to the Workstations folder. I have a Workstations/Excluded from Management folder, but am now reading that devices moved into this folder still inherit the associations?!?! So ideally, I'd like to create a custom root folder to place my unique managed devices in so I don't have to go through all my bundles and change associates to accommodate these new devices.
I don't have my ZCC in front of me right now, but the docs imply that you can create a new root folder, but I've never done it.
However, what *I* would do:
Create a new subfolder underneath Workstations and then set the blocking/parameters there. Just click the Worsktations folder and then the bluish menu bar should have a New -> Folder option or something.
So you're regular workstations will be in:
\Devices\Workstations
your special ones will be like:
\Devices\Workstations\Special
For example, we have like 25 sub-folders underneath Workstations (for our geographical locations).
You can then either manually place the workstations in there, or use registration keys to auto-place the special devices there.
--Kevin

Similar Messages

Calling Main and Extra Pages of Custom Device(s) from LabVIEW

Hi,
I am currently evaluating VeriStand (VeriStand 2011) and its control from LabVIEW using .NET APIs.
I am trying to use LabVIEW to add and configure custom devices for a given system definition file.
For that I am using a subpanel, the same way it is done in the System Explorer.
It is almost working.
I only get errors from VIs that are dynamically called from the Custom Devices API. These VI's are part of an lvlib which is called "Custom Devices Storage.lvlib".
I can't find this lvlib on my Computer. So, I guess, this error is normal. The only way to get rid of this error would be to load this lvlib in memory, but how ?
An example of a dynamically loaded VI from the Custom Device API :
If I can't configure a Custom Device inside my own Human Man Interface, there is no way I use VeriStand in the future. I don't wan't an operator or an administrator to open the System Explorer and change anything else than Custom Devices that may change in several of our test benches.
Is there a way to do that or should I throw VeriStand to the trashcan ?
Thanks in advance for your answer(s).
Regards,

Hi DaHelmut,
First of all, I apologize for the lack of applicable replies. What you're attempting isn't something we usually encounter so our team didn't quite understand.
I'll restate what you want to make sure its clear: You want to make your own version of system explorer fir your team to edit system definitions with. You also want it to support configuring custom devices. Therefore, you need custom devices to work inside your system explorer just like they do inside the shipping system explorer.
This is technically possible, and I will help you accomplish this with some advice, however I have never seen this done before so it might take us a while to figure out all the issues. Typically people developing a custom GUI for a test bench just use the system definition API directly instead of using custom device's as-is... which is more difficult, and I agree your approach is better if it works. However, most test benches have a known set of custom devices (maybe just XCP/CCP and scan engine) so they only need to use the system definition API for maybe a few custom devices... not any device.
First things I should mention:
Editing a system definition, either through your custom gui and therefore through the system definition API, or through the system explorer... always requires a PC or Full development license. An operator licenses will never be able to edit system definitions no matter what.
There is a set of VIs provided by the ECUMC toolkit to add/remove/edit system definitions with the XCP/CCP custom device. You would have to put your own GUI on top, but the VIs are installed here: <\LabVIEW>\vi.lib\ECUMC\NIVS
I have an unreleased set of VIs that do the same thing for the scan engine and ethercat custom device I can provide
If you still want to create your own system explorer thats capable of loading and configuring any custom device, here are some suggestions:
Custom devices are built into LLBs that include all of their dependencies, so they can be loaded by the LabVIEW run time engine. If you create a VI that loads custom device's, you should be careful to avoid cross linking corrupting your development system or your custom device's. For example your system explorer might use "Get File Extension.vi" from vi.lib, but the custom device you're loading might also use this VI and therefore its linked to a copy inside its LLB. You will know when cross linking happens when the LabVIEW load warning dialog appears saying "vi X loaded vi Y from Z instead of A". If that happens, do not save. To avoid this entirely, it might be easiest to test your system explorer only as a compiled exe.
As you saw, some custom device API VIs used by custom device developers make dynamic VI calls to an in-memory library named "Custom Device Storage.lvlib". Since this library is part of the shipping system explorer.exe source, these dynamic calls will error when not run inside the shipping system explorer.exe. There are two types that must be handled separately.
Some custom device APIs like "NI VeriStand - Signal When Ready for Shutdown.vi" just make this dynamic call, and will simply return an error. These are mostly system explorer GUI specific custom device APIs. To avoid this error, you must create and bring this VI into memory yourself. So create that library and the stub VIs you need, then place static VI references to those stub VIs on your custom system explorer's block diagram. That will bring them into memory so when the custom device VIs try to dynamically call them, it will not error.
Most custom device APIs like "NI VeriStand - Get Item Description.vi" make the dynamic call and instead of simply erroring, they will instead catch the error and switch to using a .NET implementation of the API call. I advise looking at the block diagram of this VI and then the corresponding offline API VIs to better understand this redirect system. Unfortunately, this redirection gets the offline API VI path relative to vi.lib which doesn't exist for exe's. So when you build your custom system explorer into an exe, you will need to place the "NI VeriStand\Custom Device Offline API" folder adjacent to the exe with these VIs for them to be found because the "vi library" primitive returns the exe's directory when inside an exe
Let me know if that helps or if you have questions.

"media" and "watchers" default device folder is missing after install

Hi everyone,
I begin an installation of Final cut server and i meet an issue. At the end of the installation, Final cut server don’t create three default devices folders « library », « watchers », and « media ». Final cut server only create the « library » folder. Furthermore, Final cut server don’t create « default permission sets » during the install. I just have « admin » permission set.
I’m working on an Xserve 2 X 2,66 Ghz Quad-core intel Xeon, 12 Go 1066 Mhz RAM, with OSX server v 10.6.4 :
- First I install Final cut server v1.0. During this install, I choose « Video production » customer profile selection. Then, I set my « proxy media location » and my « Production media location » in a SAN device’s folder (Active RAID using Metasan). I choose the internal hard drive to install Final cut server software. Everything means Ok, Install succeeded
- I update to Final cut server v1.1, and I start my « Final cut server »
- Then, I upgrade to Final cut server v 1.5, Install succeeded.
- At the end, I update to Final cut server 1.5.2
Final cut server is working fine but there are something wrong compare to « setup and admin guide » :
- My « proxy media location » and my « Production media location » are in my internal hard drive, not in my SAN device’s folder like my settings during the first install.
- « watchers » and « media » default devices haven’t been created. I only have the « library » folder. Instead, if I set up manually all my « device folder », is it OK ? Is there any potential issue ?
- Final cut server don’t create « default permission sets » during the install. I just have « admin » permission set
If, someone could explain me what’s wrong in my install…. Thanks a lot
Best regards
Elka
Message was edited by: Elka75

Since you haven't added any content or customizations yet, I would just do a clean reinstall.
First uninstall everything. See "Best Practices for uninstalling Final Cut Server" at <http://support.apple.com/kb/ht1764>.
Then, install Final Cut Server 1.5 and update that to 1.5.2.
(Don't install 1.0, update to 1.1, and update to 1.5--there is no reason to if you have an empty database. If your 1.5 license is an upgrade license that's OK, it will install without any previous installations--it just asks you for the 1.0 license key to authenticate.)

Custom device / I am trying to use a vehicle controller model developed in LabVIEW with compactRIO (cRIO-9024)

Now I have developed a vehile controller model with LabVIEW so as to run on VxWorks operating system. ( compactRIO cRIO-9024)
And I converted a controller model of labview into *.lvmodel in order to use it as I did with simulink models.
However, converted *.lvmodel was not supported for VxWorks operating system. so after searching for this, I found out that I have to use a custom device.
I am now studying the custom device, but it looks diffcult because I dont have much experience in real-time system.
Here are my questions.
1. Simulation model in VeriStand
Should I convert a labview controller model into *.lvmodel even if I use the custom device in order to run on VxWorks operating system?
If not, what should I do after building a controller model with labview?
2. Operating system
It is silly question. anyway, as long as I run a controller model on compactRIO cRIO-9024, the operating system always has to be set to VxWorks. Is it right?
3. Custom device
This is the most difficult thing. I dont know even what to do. What functions should be inside a custom device template tool? The controller model send output signals to a vehicle model, and receive input signals from a vehicle model.
Thank you in advance.
Hognjun

Hi,
You should post this on the Veristand Forum.
http://forums.ni.com/t5/NI-VeriStand/bd-p/440
Ravi

Using Set Cursor Busy in Veristand Custom Device Page

I am writing a Custom Device in Veristand and tried using the Set Busy vi to disable the cursor while I am doing some tasks on a System Explorer page. It seems like the Set and Unset Busy vi do not work inside of the System Explorer environment. I see that NI provides a way to release the cursor with the Veristand API but I do not see a way to set it busy with in the API.
Am I correct in saying these cursor VIs don't work the way they would in a normal application? Or is there a work around here that I am missing?
Thanks.
Rob
Solved!
Go to Solution.

Hello,
The idea is good, it works for me if you open a reference to System Explorer.lvlibystem Explorer.vi (VeriStand 2012) :
Best regards,
.mrLeft{float:left} .mrInfo{border-left:solid 1px #989898;font-size:x-small;color:#989898}
Mathieu R.
  CTD - Certified TestStand Developer / Développeur TestStand Certifié
  CLAD - Certified LabVIEW Associate Developer

Shuffle no longer syncs the playlists correctly and I cannot "see" the shuffle at all. There is no "device" folder in the left column. This may have occured after an Apple I-Tunes software update, but I am not sure. Software or hardware??

Shuffle no longer syncs the playlists correctly and I cannot "see" the shuffle at all. There is no "device" folder in the left column. This may have occured after an I-Tunes software update, but I am not sure. Is this likely a software issue or is the shuffle not working correctly?

Shuffle no longer syncs the playlists correctly and I cannot "see" the shuffle at all. There is no "device" folder in the left column. This may have occured after an I-Tunes software update, but I am not sure. Is this likely a software issue or is the shuffle not working correctly?

How can I use Easy Custom Device Tool to do the same thing LabVIEW the Basic Averaged DC-RMS VI does

I am using a cRio 9024 and am reading PWM with a 9205 analog input card. It was suggested that I use the Basic Averaged DC-RMS VI to convert the PWM signal voltage into an analog signal (RMS value) for use in my system. The issue is that the 9024 cannot use LabVIEW models (it is VxWorks). I am working through the Easy Custom Device Tool, and wonder if someone can guide me in the right direction.
Solved!
Go to Solution.

Hello,
Can you give more details about your VeriStand configuration ? Are you using the Scan Interface (and thus the Scan Engine Custom Device) or are you using the FPGA of your cRIO chassis to access the I/O ?
If you are programming the FPGA and using a FPGA Personalty in VeriStand you can probably add the calculations such as RMS to the FPGA code directly.
If you are using the Scan Engine, you will need a custom device. The Easy Custom Device Tool is just a tool, you will need to know more about what a custom device is and how to develop one:
- http://www.ni.com/white-paper/12712/en/
Regards
Eric M. - Application Engineering Specialist
Certified LabVIEW Architect
Certified LabWindows™/CVI Developer

Deploy modbus I/O server as part of custom device build

Hello,
We are attempting to get Modbus up and running as a custom device. From Labview we have managed to get modbus communication working by using Modbus IO servers.
When I package this with the custom device build we get the following error code when reading the bound variable:
(0x8BBB0005)
General Description:
LabVIEW: Unable to locate variable in the Shared Variable Engine. Deployment of this variable may have failed.
I am starting to worry if it is even possible to deploy the Modbus IO server together with the custom device? Any suggestions for other approaches?
Best regards,
Jørgen

Thanks for your replies.
The Network Variable Engine is activated on the RT target.
I now tried to create programmatically the modbus IO server by using the Express VI. This, however, will not allow me to deploy the system definition file, as it reports that it is missing a .vi.
I have then tried to convert it to a regular .vi and bundle it with both the configuration and engine build specs, but the same message appears.
Am I misunderstanding how the .vi dependencies are managed by the build specifications? Or do I have to use something else than the express .vi to create the modbus IO.
Best Regards,
Jørgen
EDIT: Added the error message:
The VeriStand Gateway encountered an error while deploying the System Definition file.
Details:
Error 1003 occurred at Project Window.lvlibroject Window.vi >> Project Window.lvlib:Command Loop.vi >> NI_VS Workspace ExecutionAPI.lvlib:NI VeriStand - Connect to System.vi
Possible reason(s):
LabVIEW: The VI is not executable. This error may occur because the VI is either broken or contains a subVI that LabVIEW cannot locate. Select File>>Open to open the VI and verify that you can run it.
As soon as I remove the usage of the express.vi, it deploys just fine.

More questions on asynchronous custom device

I am trying to create an asynchronous custom device for VeriStand and have the following questions:
a) At what rate is input channel being scanned and data pushed into the input FIFO of the custom device? Is the scan rate affected by whether the input channel is mapped to a Workspace control object or whether it is mapped to a simulation model (.dll file) output?
b) At what rate is the asynchronous custome device real-time VI being executed? Is it at the same rate as the primary control loop rate? Can I change the execution rate of a custom device and how?
c) I have a quad-core PXI real-time platform. How can I assign the custom device to a specific processor, like what you do with a simulation model (.dll file) in the system definition file?
Thank you in advance.
Solved!
Go to Solution.

Data FIFO
The rate at which data is pumped to your Custom Device is static, and has nothing to do with whether the Workspace is connected, or whether a model is mapped to any of your channels. By default, data is pushed into your Custom Device's input FIFO every iteration of the Primary Control Loop. If the FIFO is full, the oldest data packet will be overwritten. Also, by default your outputs FIFO is checked ever iteration of the Primary Control Loop. You can, however, use the function NI VeriStand - Set Custom Device Decimation to tag a property on your custom device that will indicate to the system its expected decimation. If you set a decimation of 10, for example, the Primary Control Loop will only send new data every 10 iterations and only check for new data from your outputs FIFO every 10 iterations. This can help reduce the CPU load of your system if you don't need updates that often.
Similarly, you can use the function NI VeriStand - Set FIFO Depth to control the FIFO depths of your inputs and outputs FIFO respectively. By default both have depth 1.
Execution Rate
The rate at which your Custom Device executes depends entirely on how you set it up. You can, for instance, have your asynchronous Custom Device use its own timing and run at a completely independent rate from the system. Your VI could have a regular while loop with a 10ms timer in it, for instance, or it could be based off some hardware device timing.
You can also choose to tightly synchronize yourself with the Primary Control Loop. You do this by registering using a property that your Custom Device has a Timed Loop that will use the Device Clock. The Device Clock is a timing source that is ticked every iteration of the Primary Control Loop after Custom Device FIFOs have been updated. You register for this simply by calling the property NI VeriStand - Set Loop Type and specifying Timed Loop for loop type and Use Device Clock to be True. Then, as the template VI does, just wire the Device Clock into your timing source input for the Timed Loop. If you have specified a decimation factor, as mentioned above, you should probably also use this factor as your dt. This means if you have a decimation of 10, you should only execute your Timed Loop every 10 ticks of the Device Clock timing source.
Another easy way to synchronize yourself tightly with the Primary Control Loop with little hassle is to simply base your timing off the availability of new data in your Inputs or Outputs FIFO. To do this, you could just use a regular while loop, and then just wire -1 to the FIFO timeouts. Then your Custom Device will run as fast as data is being produced and consumed by the system.
Specifying a Processor
There is no built-in property for processor assignment, but it will be very easy for you to implement this yourself. You can specify the Processor to execute on in System Explorer by creating a custom property using NI VeriStand - Set Item Property. For instance, you could set an I32 property called "Processor", with -2 meaning auto-assign, and any non-negative value indicating a specific processor index. Set this property in one of your Custom Device configuration pages in System Explorer and then read the property in the Driver VI in the engine using NI VeriStand - Get Item Property. Then just wire the property value to the processor affinity input on your Timed Loop. You should, however, always check that that processor exists on the target. Otherwise the Timed Loop will report an error and abort. This is exactly what we do for models internally.
Jarrod S.
National Instruments

PXI-6624 custom device

Hello,
Sorry for my bad english.
I start with the custom device.
I want use two PXI-6624 with Veristand for counter I/O.
So I try to creat two easy custom device, one for each card.
The program is ok in Labview, the Configuraton/Engine build too. I can interget it, in Veristand without problems.
The target deployment is well but I don't see anything in output with an osciloscop.
I think it's because of the connection beetween the PXI and the device.
You can find, in attached files, the program for one of the two card.
It's the more simple of the two device, just two input and two ouput.
Thank for your advice

Hello HervéM,
Unfortunately there is no attachment.
Could you spot below the files you wanted to attach ?
Regards,
Valentin
Certified TestStand Architect
Certified LabVIEW Developer
National Instruments France
#adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
Travaux Pratiques d'initiation à LabVIEW et à la mesure
Du 2 au 23 octobre, partout en France

Running unit tests on inline hardware custom device

How to do unit tests for Inline Hardware Custom Devices?
I get this error after creating a unit test.
Possible reason(s):
Cannot connect to the target. Please ensure that the VI Server setting is enabled and deployed to the target. Also, make sure that the port number is correct and that this machine is allowed to connect through VI Server.

wegunterjrASI,
I have a few follow up questions for you to gain a better understanding of your application:
1). What are you using to do the unit test (NI’s unit test framework or VI tester from JKI)?
2). What are you conducting the unit test on (RT Driver or something on the host machine)?
3). Are the unit test VIs under the target in the LabVIEW project?
4). Are you able to run a simple unit test?
Screenshots are always appreciated.
Regards,

Flash Builder custom code folding

I've just donwloaded the new CC versions and will possibly be buying the subscription at the end of this month. I was previously using CS4 versions.
One thing I noticed though, is that the custom code folding options in the Flash CC actionscript editor are gone, you can now only collapse entire functions. This remains true for flash builder as well.
So is there any way to collapse custom regions in flash builder instead of just entire functions? I'm working on a flash MMO and I've got over 10,000+ lines of code. Being able to collapse only functions simply doesn't cut it. It really hinders my development time as I have to scroll through masses of code in order to get to what I need. It's also much much more confusing looking at thousands of lines of code that I don't need to see at the moment. Visual studio has a way of defining regions by typing "#region" and "#endregion" in the area you wish to collapse. Is there anything I can do about this? This is a very very important feature (at least for me) that I'm not sure why it was left out, or I am unable to find it.
Thanks.

I've just donwloaded the new CC versions and will possibly be buying the subscription at the end of this month. I was previously using CS4 versions.
One thing I noticed though, is that the custom code folding options in the Flash CC actionscript editor are gone, you can now only collapse entire functions. This remains true for flash builder as well.
So is there any way to collapse custom regions in flash builder instead of just entire functions? I'm working on a flash MMO and I've got over 10,000+ lines of code. Being able to collapse only functions simply doesn't cut it. It really hinders my development time as I have to scroll through masses of code in order to get to what I need. It's also much much more confusing looking at thousands of lines of code that I don't need to see at the moment. Visual studio has a way of defining regions by typing "#region" and "#endregion" in the area you wish to collapse. Is there anything I can do about this? This is a very very important feature (at least for me) that I'm not sure why it was left out, or I am unable to find it.
Thanks.

Execution of RT driver VIs in custom device

Hi All
I am building a custom device wherein I am expecting some user input.( user provides input on the main page of the custom device).
Once the input is provided , based on it i am reading specific data from file and creating channels and section.
Previously creation of channels and section i was doing in initailiazation code. But now As i am expecting user input i cannot create those channels in initialization(reason is before getting input channels will be created which i dont want. My channel creation depends on the user input ).
So this channel creation logic I am now writing in RT driver VI along with my main logic of reading and writing of channels. For this I just want to know when does exactly RT driver VI starts its execution ?
If the RT driver Vi starts execution after adding custom deivce in veristand and after giving the user input then my purpose will be solved.
I hope i have explained my question correctly.
Solved!
Go to Solution.

The driver starts after the system definition is deployed. I don't think you can add channels in the driver VI. Nor do I think you want to, because you won't have an interface to them in the system definition. Without an interface to the channels, i.e. mapping, how will you get data into and out of them? I think your plan to create channels based on user input and config data is fine. I suggest you implement in the main page or in custom pages under the main page.
-Steve K

Pulling list of machines under the Customized device Collection

Hi Guys,
I have created a customized Device collection - "All Laptops" there are some 300+ laptop machines listed, i can see those machines when i do Right Click --> Show Members
I need to submit the list of machine to my manager, How can get the list of machines in a Report format or an excel format
Please assist.
Cheers,

Also in the console open up the collection so you see all the computers..
Hit CTRL+A to select all of them
Hit CTRL+C to copy
Open up excel, select cell A1, CTRL+V will put them in Excel.

How Create Custom Device in CS4 DC?

I need to create a new device for a phone in development. Any
one know how to create a custom device profile? I've tried
duplicating a current device and editing the XML but it doesn't
show up in the Local Device Library.
Thanks,
Sonny

>I need to create a new device for a phone in development.
Any one know how
>to
> create a custom device profile? I've tried duplicating a
current device
> and
> editing the XML but it doesn't show up in the Local
Device Library.
See if this helps
http://www.adobe.com/devnet/devices/articles/custom_profiles.html
http://twitter.com/Stevehoward999
Adobe Community Expert: eLearning, Mobile and Devices
European eLearning Summit - EeLS
Adobe-sponsored eLearning conference.
http://www.elearningsummit.eu

Custom Devices folder

Similar Messages

Maybe you are looking for