Frontend Plugins for the Battery Test System Web UI

Frontend plugins for the Battery Test System Web UI define the visual layout, presentation, and interactive behavior of the Web UI.

There are two general types of frontend plugins:

  • Page plugin—Plugin that implements a navigable page within the UI; a page has its own URL, can appear in the left-side navigation bar of the UI or as an action to a button click on another page, and can contain components. The following page plugins are available in the Web UI:
    • Home page: A landing page that provides an overall view of the test system.
    • Custom navigation bar page: Additional navigation pages to address other system or user needs. For instance, a test request page or a schedular page could be added as pages to the navigation bar.
  • Component plugin—Plugin that implements a modular component—an interactive element within a page of the Web UI. The following component plugins are available in the Web UI:
    • Bar code scanner: A dialog that can be used to input a bar-coded serial number and/or to validate that the serial number for the DUT is correct.
    • Test monitor: A component plugin used to monitor live data while a test is running.
    • DUT debugging: A component plugin that validates that the DUT is connected and functioning properly in the system.
    • DUT help: A component plugin that provides help on how to connect a DUT to the test system. It can include images, graphs, and checklists.
    • Test station validation: A component plugin that validates that the system can communicate with all of its instruments (chiller, cycler, and so on).
  • There are two general ways you can implement frontend page and component plugins:

  • Blazor-based—Uses Blazor development to create modules and incorporate them into your UI.

    Use Blazor-based plugins to access the Web UI SystemService directly, achieve a consistent look and feel by using the built-in FluentUI components, and easily transfer data between your plugin and the container page or component.

  • Web page host—Serves any HTML page through an HTML <iframe>.

    In addition to your own HTML assets, you can use web page host plugins to serve web applications you develop with G Web Development Software.

    Use web page host plugins to easily add existing HTML assets and web applications to the Web UI without the need for .NET programming.