A short introduction of how to use the VeriStand project is given in this video: Link


Max explained in German how he used the LabVIEW and VeriStand project for his thesis: Link

If you want to add/create functionalities for the control model, please check this option.


Step by step guide:

1. Make sure that the connection to your targets is possible

Before deploying make sure that:

  • the targets are switched on
  • the targets are idling / not used by other users
  • the PC is in the same network as the targets - try pinging them, a list of all ips can be found here.

2. VeriStand

Start the project you want to use:

  • Experiments: VeriStand\CoSES_Smart_Grid.nivsproj
  • Software in the Loop: VeriStand\CoSES_SiL.nivsproj

  1. When running experiments, open the System Definition File and activate the targets you want to use.
    Right click on the targets and "Enable" or "Disable" them.

    Use only the targets you require:
    • IC (Industrial Controller) for the heat system
      SFx - different houses
      DH - district heating system
    • PXI for the electric system
    • HostPC for models that run on the PC/laptop, e.g. PHIL models
  2. Use the user interfaces to interact with the models once deployed:
    • The UI manager (nivsprj) has a GUI to monitor the current status of the experiment.
    • The Workspace (nivsscreen) can be used to manually set inputs.
  3. Ignore this button! If you deploy from VeriStand, all input signals will be ignored for safety reasons!

Check if the controllers are switched on and not used by anyone else if you can't deploy.

3. LabVIEW / VeriStand Interface Settings

Open the VeriStand Interface (VeriStand Interface\VeriStandInterface.lvproj).

  1. Select the Project path "Experiment", "Software-in-the-Loop" or "Individual Project File Path".
    When choosing "Individual Project File Path" you have to define the Project File Path, otherwise this input will be ignored.
  2. Select the targets you want to use, all other targets will not be activated. You have to choose at least 1 target.
  3. Click "run" to deploy the project.
  4. When deployed, you can choose if you want to use the implemented standard control for some of the components or activate external communication. If you choose nothing, you can define the "fromLogic" values of the Control&Safety yourself.
  5. Once VeriStand is deployed, the LED shows it and the "Experiment Time" runs.
  6. If you need electrical measurements from the PXIs, always make sure that the reflective memory network (RMN) is connected!

Pathlist

The list shows all inport and outport signals and their paths. This might be useful, if you need the name of a specific path for your control algorithm.

Data Logging

In this tab you can define the logging specifics. If you require high speed datalogging (>10 Hz), please use the data logging of the VeriStand UI Manager.

  1. Set the sample rate, logging time, path file and result name file
  2. Select the signals you want to store
    1. Signals can be chosen by a file, where all paths are defined or by the buttons
    2. If "Use Channel Buttons" is selected, the Modules and Signal types can be selected. The logging VI will then automatically make a list of all signals and paths to be stored
    3. If additional signals are required, they can be defined in this array. Don't delete the first row and always make sure, that the paths name is correct (no space or enter at the end, no empty row!)
  3. Start / Stop the data logging. Changes in the signal selection will be ignored during active logging!
  4. The LED should glow when data logging is active.

Parameters

  1. Filter the target and the parameter set you want to work with (not required, but otherwise all available parameters are shown in 2).
  2. Select the parameters you want to change. If you want to delete all selections, you can click "Reinitialize Parameter List".
  3. Click "Get Parameter Values" to show the current values of the parameters.
  4. Click "Apply New Parameter Values" to set new parameter values.

PHIL and SiL

  1. Select all models that should run with PHIL setpoints (if you don't choose them, you have to define the PHIL Control&Safety inputs yourself).
  2. Select the simulation model you want to change, set the Typeday and the InitializationTime.
  3. Change parameters of the simulation model similar to the section above
  4. You can control the (PHIL) experiment execution with these buttons
  5. These output elements show in which state the experiment is currently.

Error Codes

If something unexpected happens, please check the error codes. It is also suggested to check the error codes prior to any data logging to make sure, everything works as planned.

  1. Standard LabVIEW error handler. If some error is shown, check where it comes from by using the "Probe".
  2. VeriStand error handler: If some values are overwritten in the Control&Safety due to any safety violations, they are given by an error code. The error code is translated in this screen into its text.

Programming Individual Control Code

The Control code template can help to program or adapt the control code for different modules by directly controlling the actuator via the VeriStand Interface.

It is available for the following modules:

4. VeriStand UI Manager

The UI Manager is set up as a GUI showing all input and output signals to/from the testbed or Software in the Loop.

To get signals, you have to connect (Ctrl + F5) it.

5. Workspace

The workspace can be used to manually define the "fromLogic" signals, if they are defined by the VeriStand Interface.

Additional blocks can be added by changing to the edit mode (ctrl + M). In edit mode, the values of the blocks cannot be changed, deactivate the edit mode first.

6. Undeploy

If you want to stop the experiment, click "undeploy" in the VeriStand Interface, this will set the testbed into a safe state before undeploying the project.

  • Keine Stichwörter