B&R Automation Studio 6 Features

Ask Questions
3

In the upcoming weeks, we will update this page in the Online Automation Help to include this infromation, but here is the feature & changes related information that you requested, deprications are already explained in the thread above.

General - Feature Highlights

Enabling Shorter time to Market

Enhanced Software Lifecycle - Automation Software 6 delivers transparent product schedules, ensuring that expectations for solution delivery are clearly set and met with improved accuracy. By providing a unified platform that synchronizes activities among product users, R&D, partners, suppliers, and order processing, we bridge the gap between teams. This integrated approach enhances the efficiency of the supply chain and stakeholder collaboration.

Programming efficiency Improvements - After migrating projects to Automation Studio 6, our Selective Versioning ensures that projects can be updated to the latest Automation Studio versions without the need for conversion, maintaining compatibility across different future releases. This enhancement simplifies the development and maintenance of multiple projects, improving efficiency and reducing the potential for errors. With Automation Studio 6.0, project versions are distinct from the software version, facilitating ongoing project maintenance. This feature allows for uninterrupted work on projects even as new versions of Automation Studio are released, ensuring that compatibility is maintained.

Flexible Upgrade Paths - Customization is key when using multiple mapp technologies in a machine. We are removing interlocking between Automation Studio, Automation Runtime, and individual mapp Technology packages, so users now have the discretion to select specific versions that meet their project requirements. This a la-carte upgrade approach allows for targeted updates, providing access to the latest features and bug fixes without the need for comprehensive software upgrades.

Faster development

Compiler and Operating System Enhancements - The new release upgrades to the GNU Compiler Collection - GCC 11+, offering enhanced performance and reliability. Alongside this, we have upgraded the base Real-time Operating System to bolster stability and security. These upgrades are pivotal in improving software quality and simplifying the porting of open-source software, aligned with the latest C/C++ language standards.

Innovations in Ladder Logic Programming - The ladder diagram editor in Automation Studio 6.0 has been reimagined with an updated user interface and revised editing rules, maintaining compatibility with existing programs. This editor improves usability with variable width contacts/coils, function blocks, and connections to power rails. These changes aim to simplify programming alignment, optimize the programming interface for various devices, and enhance program readability.

Future Proof software development

Advanced Security Measures - Automation Studio 6.0 has been engineered with a focus on security, incorporating enhanced secure OPC UA communications and conforming to IEC 62443-4-1 certified development processes for Automation Runtime 6.0. This rigorous approach ensures that client systems are protected against current and future security vulnerabilities.

Product Specific

Automation Studio

Features and changes

  • Selective Versioning
    • Automation Studio 6.0 serves as the foundational version for seamless project compatibility within a major release of Automation Studio.
    • With Automation Studio 6.0, projects created using any version within the range of AS 6. can be seamlessly processed within any version labeled AS 6.<x+n>, where “n” represents a subsequent release.
    • This compatibility extends to both the source files of your projects and the binary data generated during the project compilation process.
    • As a result, your work in side project remains consistent and uninterrupted as you transition to newer versions of Automation Software 6., enabling you to take full advantage of the latest features and enhancements without the need for extensive project adjustments.
  • Global Installation of Automation Studio
    • If a user already has AS 6.0 installed with certain Technology Packages (TP) and Hardware (HW) configurations, etc. and subsequently installs AS 6.2 or any later version, there is no need to reinstall the previously installed TP or HW versions. This streamlined approach saves users time and effort during upgrades or new installations.
    • Starting with version 6.0 of Automation Studio (AS), we have implemented a significant change in how relevant sub-system configuration files are managed. These configuration files are now stored globally throughout the entire major version of Automation Studio. In practical terms, this means the following benifits for our users:
      • Streamlined Upgrades: Hardware and Technology Packages (TPs) no longer require reinstallation for each new minor version of Automation Studio. This simplifies the upgrade process, allowing users to seamlessly transition to newer versions without the need to redo their configurations.
      • Persistent Automation Help: Automation Help remains intact across minor version updates, eliminating the need for repeated installations. Users can access help resources consistently without any additional steps.
      • Time Efficiency: The new approach significantly reduces the time required for installing hardware and software upgrades, including TPs. Users can swiftly integrate the latest features and enhancements, optimizing their workflow.
      • Space Conservation: By eliminating redundant installations, users save hard disk space. This efficient use of storage resources ensures a more sustainable and clutter-free environment.
      • Efficient Bug Fixes: When installing the latest minor version, the system automatically integrates bug fixes for older minor versions. This proactive approach ensures that users benefit from a more stable and reliable software experience.
    • Please note that if a user decides to uninstall AS 6.x, they will need to reinstall the previously installed Technology Packages and Hardware configurations when they reinstall the software. This ensures that the system retains the necessary configurations for optimal functionality.
  • New GCC 11 Toolchain Integration
    • Automation Studio now supports a new toolchain based on GCC 11. This enhancement brings a host of benefits and improvements to your development experience, ensuring increased compatibility, performance, and advanced capabilities. We believe that these enhancements will elevate your development experience within Automation Studio, enabling you to create more powerful and reliable applications.
      • Expanded Language Support: With the new toolchain, Automation Studio now offers support for C++17, C++20 experimental, and C17, empowering you to leverage the latest language features for your projects.
      • Enhanced Performance and Scalability: GCC is now an x64 executable, significantly enhancing its ability to handle and build large projects efficiently. This improvement ensures smoother compilation and linking processes for even the most complex applications.
      • Advanced Static Code Analysis: Unlock the potential of advanced static code analysis with the inclusion of advanced build options. These options enable you to achieve higher code quality and robustness in your software development projects.
      • GDB 12.1 Integration: We’ve updated the GNU Debugger (GDB) to version 12.1. For a comprehensive list of changes and improvements, please refer to the GDB 12.1 release notes.
      • ARM-ABI Transition to EABI: To seamlessly align with the new Automation Runtime 6, which is based on VxWorks 7, the ARM-ABI support has transitioned to EABI. This transition ensures compatibility and optimal performance within this updated runtime environment.
      • Improved C Standard Library (libc) Support: We have bolstered the support for the C standard library (libc), ensuring a more robust and reliable foundation for your software projects.
    • For a comprehensive list of changes specific to GCC 11, please refer to the GCC 11 release notes.
  • New Ladder Editor

    • The new Ladder Diagram editor offers a modern and user-friendly design.

      • Automatic Positioning (Default Mode): In default mode, network elements are intelligently and automatically positioned, streamlining the diagram creation process.
        • Flexible Positioning (Legacy Mode): For those who prefer more control, legacy mode allows for free positioning of network elements, accommodating diverse workflow preferences.
      • Insertion Guidance: Visual cues display possible insertion positions when adding network elements, reducing errors and enhancing efficiency.
      • Mini Toolbar: A compact, context-sensitive toolbar provides quick access to essential functionalities, ensuring an intuitive editing experience.
      • Drag & Drop Connectivity: Drawing connections between elements is now as simple as dragging and dropping, simplifying the wiring process.
      • Execution Order Visualization: Gain a clear understanding of execution order with visual cues, improving overall diagram comprehension.
      • Dynamic Width for Visibility: Network element width dynamically adjusts to display text, enhancing text visibility and making your diagrams more informative.
      • Network Collapsibility: Streamline complex diagrams by collapsing networks, allowing for a more organized and focused view.
      • Bookmark Functionality: Harness the power of bookmarks to mark and navigate key points within your ladder diagrams, enhancing productivity.

    • Ladder diagram source files now adhere to the IEC 61131-10 standard. When opening an Automation Studio 4.12 project, any ladder diagram files within it are automatically converted to the new file format.

    • Seamless compatibility: Ladder diagrams from older Automation Studio versions can be opened and edited in the new editor.

      • The new ladder diagram editor supports two distinct working modes: “Default” and “Legacy.”
      • For newly created ladder diagrams, the editor operates in the “Default” mode, enabling the creation of networks according to the IEC 61131-3 standard.
      • When opening a ladder diagram from an older Automation Studio version, the editor switches to “Legacy” mode. In “Legacy” mode, users have access to the same wiring options as in the ladder diagram editor of older Automation Studio versions.

    • In monitor mode and for diagnostics, communication with the target system is established through OPC UA, ensuring secure, robust and efficient data exchange.

      • When incorporating a ladder diagram into your Automation Studio project, you now have the option to configure the OPC UA system conveniently through a dedicated dialog, enhancing system compatibility and ease of use.
  • Enhanced OPC UA
    • Upgrade of OPC 30000 v1.01 to v1.02: The IEC 61131-3 based PLC model has been upgraded to v1.02.
    • Upgrade of OPC 30001 v1.01 to v1.02: The IEC 61131-3 OPC UA client function blocks (library AsOpcUac) have been upgraded to v1.02.
    • Introduction of Standard-Compliant Permissions
      • In pursuit of standardization and enhanced compatibility, we are introducing standard-compliant permissions for B&R permissions on OPC UA Nodes within all OPC UA information models. These updates are reflected in the DefaultView configuration within Automation Studio and the OPC UA Server on Automation Runtime.
      • The following permissions have been affected:
        • Visible: Removed
        • HistoryWrite: Removed
        • Subscribe: Removed
        • Execute: Replaced by “Call”
        • HistoryRead: Replaced by “ReadHistory”
        • AttrWrite: Replaced by “WriteAttribute”
        • ReadRolePermissions: New
        • WriteRolePermissions: New
      • For in-depth information on standard-compliant permissions, please consult the OPC Foundation documentation.

Automation Runtime

Features and changes

  • Selective Versioning between Automation Runtime and Automation Studio
    • The version dependency between Automation Runtime and Automation Studio has been revised for enhanced flexibility. Now, each version of Automation Runtime within a specific major version line is designed to be compatible with any Automation Studio version from the same major line. This improvement signifies that integrating a new feature version of Automation Runtime within a major version line does not compulsorily require an upgrade to the latest Automation Studio version. However, to utilize new features present in an updated Automation Runtime version, an upgrade to Automation Studio may be necessary mainly to enable access to the relevant configuration options.
  • OpenSSL 3.0.8 in Automation Runtime Version 6
    • Automation Runtime version 6 is now equipped with the updated OpenSSL version 3.0.8, enhancing security and performance.
    • The secure FTP server (FTPS) is hardened and fulfills TLS1.3 as a minimum standard.
  • Unified versioning for BR Modules
    • BR modules in Automation Runtime now adopt a standardized versioning system, using the Major.Minor.Patch.Build format. This alignment brings consistency in versioning across Automation Runtime and its BR modules.
  • Changes in ARsim for greater file system compatibility with realtime targets
    • In Automation Runtime 6, the ARsim drive mappings for C: through F: have been altered. These drive letters no longer correspond to the Windows system drives C: through F:. Instead, they now resolve to the system folder within Automation Runtime, specifically pointing to the Temp\Simulation directory.
  • Partition Naming Conventions in Automation Runtime 6

mapp Motion

Features and changes

  • General

    • The version dependency, which required all mapp packages to use the same Major.Minor version, has been removed.
    • Motion realated Automation Help 6 has been restructured. Documentation for mapp Axis, mapp Robotics, and mapp Trak is now available in individual section within the mapp Motion documentation.
    • The datatype for the “Parameter” input of the MC_BR_GetCoordSystemIdent function block has been modified. The “AxesGroup” element has been replaced with a “Component” element.
    • Due to changes in the OPC-UA interfaces, Automatic scene generation for mapp Robotics and mapp Trak now requires Scene Viewer 4.3 for the AS6.0 Engineering Sample.
    • The AS6 release (scheduled for June 2024) will require Scene Viewer 6.0 or higher.

  • ACOPOS Firmware (McAcpSys)

    • Encoder Interface: An error message will now be reported (error 7100) if the parameters ENCODx_OUTPUT_STAGE and ENCODx_OUTPUT_FREQUENCY are not connected (i.e., if the encoder type is not set).
    • Encoder Interface: We have unified the supply error bit in the status (ENCOD_STATUS):
      • For ABR (incremental), BiSS, EnDat, SinCos SSI, T-Format, the encoder status bit 13 has been changed to bit 28.
      • For HIPERFACE, the encoder status bit 26 has been changed to bit 28.
      • For HIPERFACE DSL, the encoder status bit 16 has been changed to bit 28.

  • mapp Axis

    • The term “Standby” replaces “StandBy” in outputs or elements of the following function blocks and data types: MC_BR_CamAutomatCommand, MC_BR_CamIn, MpAxisCamSequencer, and MpAxisCamInfoType.
    • “DataAddress” is now correctly spelled in the McCamDefineType data type.
    • The “DataSize” element has been removed from McCamDefineType, as it is no longer necessary.
    • For the module 80SD100XD.C011-01, “Reference station address” replaces “Reference station adress” in the Encoder / Encoder X6{A,B} / Interface type / Hiperface interface configuration.
    • The order of elements within several data types is reorganized for improved clarity.
    • “AutoTuneDone” has been moved from the “Info” output to a direct output at the function block interface.
    • The elements “MechDeviationCompState”, “AutoTuneState”, “CommunicationState”, “StartupCount”, “DigitalInputStatus”, and “PLCopenState” are now integrated into the “AxisAdditionalInfo” element of the “Info” structure.
    • “ActualOffsetShift” and “OffsetValid” from MpAxisCouplingInfoType and MpAxisCamSequencerInfoType are grouped into the new “Offset” element of the MpAxisShiftInfoType structure, which includes “ActualShift” and “Valid” elements.
    • Similarly, “ActualPhaseShift” and “PhasingValid” are now part of the new “Phasing” element in the MpAxisShiftInfoType structure.
    • The data types “MpAxisCouplingRecoveryParType” and “MpAxisSequencerRecoveryParType” are merged into “MpAxisRecoveryParType,” as both structures shared identical elements.
    • The negative edge at the “GetCamPosition” input of MpAxisCoupling during an active movement with mcAXIS_MOVE_CAM_POSITION_SLAVE mode now results in a Halt, aligning with other movement commands.
    • The “CamList” of MpAxisCoupling can now be automatically updated with the “Cam” command when “UpdateCamListOnStart” is set.
    • The “Shift” parameter in the “Offset” and “Phasing” commands of MpAxisCoupling and MpAxisCamSequencer can no longer be changed with the “Update” command.
    • For MpAxisCoupling and MpAxisCamSequencer, the outputs “Info.Offset.Valid” and “Info.Phasing.Valid” will only be set when “CmdIndependentActivation” is activated with the “Update” command and the axis state is SynchronizedMotion. These outputs will reset when the SynchronizedMotion axis state is exited.
    • The default value of “Base type” within the axis configuration has changed from “Linear bounded” to “Rotary periodic,” with adjusted default movement limit values.
    • Configuration for “Cam automat common” and “Cam automat ACOPOS,” as well as the data types “McCamAutParType” and “McAcpAxCamAutParType,” are unified for easier reuse across ACOPOS axes and axes using the ProfGen-Feature. Notable adjustments include:
      • “MasterCamLeadIn” is now under “Advanced parameters” of a state, rather than in the compensation modes’ “Advanced parameters.”
      • The “StartStateParam” structure is moved from “Common / Advanced parameters” directly into the “Common” structure.
      • For “StartState” > 0, selection between starting into “Cam” or “Compensation” is now available.
    • Unified behavior across all axis features in case of an invalid configuration is now implemented. Previously, behavior varied depending on the axis feature type.
    • The internal “Reset” command will only be activated if the “Errorstop” state of the axis is specifically due to invalid parameters. Previously, upon successful execution, the MC_BR_ProcessParam command invariably triggered an internal “Reset” command. This could result in the axis inadvertently exiting the “Errorstop” state, even when not prompted by an invalid configuration. We’ve now updated this functionality.
    • Significant improvement in the functionality and versatility of virtual ACOPOS axes are introduced with accommodation limit value parameters in virtual axes. With the current enhancement, these axes now fully utilize and evaluate limit values.

  • mapp Robotics/CNC

    • The default mode for stopping, such as during a power-off event or when a specific mode isn’t designated, has been changed to quickstop. This update reflects a shift towards prioritizing rapid response in stop scenarios for enhanced system safety and reliability.
    • Configuration settings related to the automatic scene generation for Mechanical Systems are modified to offer greater flexibility to accommodate diverse application requirements.
    • Specific robotic models, such as open Robotics Comau mechanics, are no longer bundled with the mapp Motion package. Instead, these will now be available through dedicated installers. This change is intended to streamline the distribution process and ensure more focused support.

  • mapp Trak

    • The assembly function blocks MC_BR_Asm{GetShuttle, GetSegment, DeleteShuttle, Reset, CommandError, ReadInfo}_AcpTrak have been enhanced with additional parameters to support the future inclusion of the “SegmentGroup” parameter.
    • Additional parameter “StopMode” has been introduced to the function blocks MC_BR_AsmPowerOff_AcpTrak and MC_BR_SegPowerOff_AcpTrak, allowing users to stop shuttles in specific assembly sections before powering off with jerk limitation.
    • The function block MC_BR_ShReadFrame_AcpTrak now includes advanced parameters for future selection of the tool center point in reference to the output frame.
    • The count outputs in the function block MC_BR_AsmReadInfo_AcpTrak have been consolidated into ‘McAcpTrakShuttleCountType’ and ‘McAcpTrakSegmentCountType’ to improve clarity.
    • The count outputs for shuttles in the function block MC_BR_SecReadInfo_AcpTrak have been consolidated into ‘McAcpTrakShuttleCountType’ to improve clarity.
    • “Elongation compensation” and “Segment transition compensation” have been grouped under a common “Compensation” category in the assembly configuration.
    • “Elongation compensation” and “Asymmetric current compensation” are now grouped under a single “Compensation” category in the segment configuration.
    • The function block MC_BR_ShSetUserId has been renamed to MC_BR_ShSetUserID, aligning the function block name with the parameter name “UserID”.
    • The error stop reason "mcACPTRAK_{ASM, SEG}NOGRIPPER" has been removed from MC_BR {Asm,Seg}ReadErrorInfo_AcpTrak as it was never set.
    • The “ShuttleTrace” feature was renamed to “SectorTrace” to avoid misinterpretation and to allow for a future shuttle trace feature to trace a specific shuttle.
    • The function block MC_BR_TrgPointGetInfo_AcpTrak was renamed to MC_BR_TrgPointReadInfo_AcpTrak as the function block provides information that change between cycles. This improves consistency in the naming of the function blocks.
    • Process points were factored out from the “ProcessPointList” configuration for consistency with other components and to enable full support of MC_BR_ProcessParam.
    • The size of the McAcpTrakShuttle{Mon, Vis}Data structure was increased from 150 to 250 to support the visualization of assemblies with a high number of shuttles.
    • The assembly configuration for excluding virtual shuttles from collision avoidance was clarified.
    • A PowerOn is now aborted if a movement is detected after the initial position identification routine has been started. This ensures that shuttles are created on the positions they are identified.
    • The segment speed filter is now activated per default with a filter time of 800 µs, as this boosts the control performance of a shuttle.
    • The maximum deceleration specified in the shuttle stereotype is now required not to exceed the emergency stop limit of 200 m/s².
    • “Standby” is used instead of “StandBy” at elements of the McAcpTrakShCamAutCmdInfoType data type.

mapp Services

Features and changes

  • mapp Services

    • The version dependency for mapp packages has been removed, except for mapp View. mapp View and mapp Services must still operate on the same Minor version.
    • Components are no longer based solely on function blocks but become active components upon configuration within the system, offering several benefits:
      • mapp Services components can now operate independently of any application, enabling initial interactions without the need for programming. Interactions at the application level remain facilitated through function blocks and functions.
      • An additional interface is now provided for interaction with mapp Services components via mapp Cockpit, encompassing Commands, Parameters, Watchables, and Logger.
      • There’s an enhanced performance of function blocks.
      • Download handling has been simplified; for instance, disabling function blocks in the ‘Exit’ routine is no longer necessary.
    • File name definitions have been moved to the application level to increase flexibility, responding to feedback for greater file naming versatility.
    • Language and Measurement System handling have been made more user-friendly through separation at the application level.
    • Memory configuration has been standardized acorss different mapp Services components.
    • The usage of text system, unit handling, and snippets in mapp Services has been unified and simplified.
    • Configuration function blocks have been eliminated in favor of a central solution for runtime configuration changes. This improvement, similar to mapp Motion, allows for parameter adjustments before data is saved, enhancing flexibility and performance.
      • The initial release’s central solution includes MpAlarmX and MpBackup, with other components to follow in subsequent versions.
    • Modifications to the limits and behaviors of certain UI function blocks have been implemented, addressing changes previously hindered by compatibility constraints.
    • Localization efforts have prompted a shift from STRING to WSTRING where applicable (e.g., the “Backtrace” parameter of MpAlarmXListUI).
    • All passwords within configurations are now encrypted.
    • Time configuration has been streamlined.
    • From version 6 onward, system restarts will consistently be required for version changes, library modifications, and component start/stop actions.
      • Starting and stopping components refers to a new feature that fully activates or deactivates components, not merely enabling or disabling function blocks, optimizing the operation for specific machine setups.

  • mapp AlarmX

    • The mapp AlarmX configuration and IEC interface have been streamlined for better modularization of alarms.
    • A “Confirm” feature has been introduced to align with OPC UA part 9 standards. Concurrently, the “Required after active” option for alarm acknowledgment, which was incompatible with OPC UA part 9, has been removed.
      • Note: This sets the stage for future OPC UA part 9 support, which is not curretly included in version 6.0.

  • mapp Audit

    • The process for enabling/disabling auditing in other components has been standardized.
    • The mapp Audit configuration and IEC interface have been simplified.
    • Text linking and the separation of audit events have been improved, allowing users to select which events to display.
    • A plugin for configuring auditable events has been added.

  • mapp UserX

    • The mapp UserX configuration and IEC interface have been simplified.
    • Certain status information has been generalized for enhanced security.
    • New audit events have been introduced.

  • Other components

    • Minor adjustments to configuration and IEC interfaces have been made, especially where compatibility issues previously prevented changes.

Features and Changes

  • HMI templates
    • A new mapp View HMI can be created by selecting templates.
  • Automatic Synchronization:
    • Mapp View elements are now automatically synchronized with their respective file or package names upon creation or renaming.
    • When the ID of a mapp view file or package (e.g., page package) is modified, the file/package name will be automatically updated to match.
    • Corresponding IDs within the visualization (.vis) files are also automatically adjusted to reflect these changes.
  • Refactoring of Mapp View Elements:
    • Renaming mapp view elements (such as widget names) will now automatically update all referenced elements, including widget IDs in bindings or event bindings.
    • Deletions of widgets/contents will trigger an automatic update of bindings and event bindings.
    • References to StylesSet and KeywordSet within a theme are now automatically updated.
    • Styles references within a StylesSet will also receive automatic updates.
  • Type Editors:
    • Added type editor for the ColorCollection data type.
    • Introduced type editor for the ImagePath data type.
    • New type editor for the ImageList data type.
  • New Screenshot Functionality:
    • It is now possible to create screenshots of a running mapp View HMI and save the images either on the PLC or the client side.
  • Compound Widget Enhancements:
    • Within a compound widget, it’s now possible to bind structure elements to local properties, such as the enable, visible, or a specific local property within the compound widget.

mapp Cockpit

Features and Changes

  • General
    • The version dependency that required all mapp packages to use the same Major.Minor version has been removed. It is now possible to use i.e. mapp Cockpit 6.0 and mapp Motion 6.1 and vice versa in the same Automation Studio project.
    • Starting with mapp Cockpit 6.0 a WebServer configuration is available where the user can define the used ports and also if HTTPS and/or HTTP is used. In case of HTTPS the user can define an SSL configuration in the same area.
    • mapp Cockpit HMI application can run on a user-defined port.
    • The jitter of timestamp during trace has been improved by recording the timestamp on the controller at the beginning of the execution of the task class.
    • Trace analysis functionality has been expanded with additional zero lag filters:
      • Moving average filter
      • Finite impulse response (FIR) filters for low pass, high pass, band pass and band stop.

mapp Vision

Changes & Additions

  • The Table Editor is no longer necessary, as all configurations can now be completed in the Property Window.

OPC UA FX

Features and changes

  • Real-time traffic handling performance has significantly improved because OPC UA FX real-time traffic now operates independently from network schedules and other background traffic.
  • Port-based TSN configuration for the B&R TSN switch (0ACST052.1) is now available. This enhancement enables the implementation of new use cases that require network partitioning into subdomains.
    • TSN switch parameters, such as real-time windows and VLAN configurations, are now configurable per port. This approach allows for tailored configurations rather than applying identical settings to all TSN-capable ports.
    • For scenarios requiring uniform parameters across multiple ports, it is possible to create references to the configurations of other ports.
    • By default, all ports inherit the configuration from the first port.
  • A new configuration option has been introduced for setting the Priority Code Point (PCP) in VLAN-enabled PubSub communications.
    • The default PCP setting is ‘automatic’, aligning with industry-standard recommendations.
    • Alternatively, the ‘manual’ setting allows users to select the PCP values explicitly.
  • To streamline real-time communication setup, VLAN configuration visibility in the OPC UA FX PubSub editor has been enhanced to ensure these parameters are consistently displayed.
  • The DataSetReader configuration in the OPC UA FX PubSub editor no longer includes a message receive timeout.
    • The publishing interval now serves as the mechanism for detecting lost network messages.
  • Enhanced plausibility checks for parameter inputs in OPC UA FX editors have been implemented. For example, TSN switch hostname validation now conforms to SSH protocol character restrictions, including alphanumeric and approved special characters.

Please note that detailed information regarding mapp Technologies mapp 6D, mapp Control and mapp Safety are not necessary for this context.

15 Likes