PROVEtechTA Logo


current version    select version    show all

Version 2021 SE (2021-May-31)

Module Type Description
General Feature The "parallel PROVEtech:RE/UI:TestAId" model configuration allows adding several instances. This is mainly for sharing several video sources with UI:TestAId for image recognition. Additionally, the configuration of UI:TestAId within PROVEtech:TA changed: In older versions UI:TestAId expected several command line parameters. Now it just expects the path to an INI file. Thus, you only specify this single path in PROVEtech:TA now and do not have to care anymore about quotation marks around a path with space characters. Furthermore, you now specify optionally, which video source to share with a UI:TestAId instance.
The XCP master in ModelCom supports EV_CMD_PENDING sent by the slave to restart the command timeout detection.
The XCP master in ModelCom supports the t1 timeout value from the .a2l file for the command timeout detection. The t1 value is the 2nd value in the optional "/begin PROTOCOL_LAYER" block of the .a2l file. Attention: This also affects the time between CONNECT command retries. To have the old behavior simply set that value to 1000 in the .a2l file (timeout of 1 second).
ModelCom on dSPACE SCALEXIO has the additional parameter "Ethernet monitoring buffer size" to change the buffer size for monitoring Ethernet channels. The buffer must be large enough to hold the maximum amount of Ethernet data collected between two model steps for a channel. Use 0 to disable the Ethernet monitoring. Please be aware that if you update ModelCom for an existing model, ConfigurationDesk will set it to 0 instead of the default value, which is 1536 KB.
Possibility to disable the data acquisition start synchronization across model nodes via "DisableAcquisitionSynchronization=1" in [General] of the according model setting .cfg file.
The .ldf file parser supports format extensions which were not part of the standard originally.
The settings dialog displays the current value (in the RAM) of each replacement variable in an additional column beside the current value in the CFG.ini file if you select the currently loaded configuration.
Changing the configuration reloads the CFG.ini file to take changes into account.
MatlabPatch additionally supports MATLAB R2021a.
TOI Library V2.16 which uses more digits to transfer the mask parameter values to the underlying Simulink blocks. Furthermore, it does not use the default value 0 anymore for "evalin" calls. This means, missing workspace variables now lead to error messages. This can break the compatibility in some cases where an empty string was used instead of 0, e.g. in auto-generated TOI block insertion. In such a case you must fix your code/model as this change prevents unwanted wrong model code generation.
Info No support for ETAS LabCar prior to version 5.0 anymore.
Bugfix Using the dSPACE MicroAutoBox was not possible with dSPACE releases using "RecentHardware.xml" instead of "dSPACE.ini".
Floating license information dialog: Minor bugfix and additional percentage value for total licenses in use.
Using custom UDP links for the RTAE possibly crashed the model on dSPACE SCALEXIO when executing AL.Init.
Workpage Feature Support for multi-rate data acquisition files. This means, data acquisition files can have multiple groups of signals that were acquired using different sample rates. Additionally, each group can have an own time offset within the data acquisition. This has an impact on the supported data acquisition formats:
  • PROVEtech:TA format (.hdr): In case of several signal groups, the header itself (.hdr file) uses an XML format now. Each group has an own .bin/.eva/.xtr file where all groups beside the 1st one have an additional group index for the file extension: .bin1/.eva1/.xtr1/.bin2/.eva2/.xtr2, etc.. Old PROVEtech:TA versions cannot read the new format. However, PROVEtech:TA 2021 SE generates the old format if not using several signal groups. Furthermore, the free PROVEtech:TA DAQViewer 2021 SE can read and display the new format.
  • ASCII text table format (.txt): Each group has an own text file where all groups beside the 1st one have an additional group index for the file extension: .txt1/.txt2/.txt3, etc.. A new optional export option (UTF-8=1) allows the export in UTF-8 text format with BOM (byte order mark). Old PROVEtech:TA versions can only read the text files separately when the extension is .txt.
  • MATLAB .mat format: The structure has an additional level for the groups. Old PROVEtech:TA versions cannot read the generated files, but PROVEtech:TA 2021 SE can read the old files.
  • .tdm, .tdms, .mdf and .mf4 formats: They always supported multiple signal groups with different sample rates.
  • .pcapng and .asc are not affected as they store messages.
  • The offline mode does not support the time base "samples" anymore as one sample might have a different time span for each signal group. The offline mode additionally supports microseconds as time base though. Internally, it calculates everything based on nanoseconds now.
  • Please be aware that PROVEtech:TA 2021 SE does not create data acquisitions with several rates in the online mode. It still uses oversampling if necessary. This feature is mainly a requirement for upcoming versions.
The PROVEtech:TA data acquisition format (.hdr) supports storing codepage information of text signal arrays for the offline mode.
The PROVEtech:TA data acquisition format (.hdr) supports 64-bit integer signals. Please be aware that these get converted to 64-bit floating point values internally in the offline mode for displaying them. This conversion might remove the least significant bits.
The data acquisition conversion supports the conversion to the .hdr.7z format.
Import of .mf4 data acquisition files (only for signals over time, not for messages). It only supports a subset of the standard. In case of not equidistant timed signal data there is an equidistant sampling.
When manually saving a data acquisition the file dialog remembers the target format for the next time per user.
The offline mode can now use either T1 or T2 for the time to display in non-strip-chart controls. Previous versions always used T2. Click on T1 or T2 to switch the time to use. A bold and underlined font for T1 or T2 marks which one is currently active.
3D surface graph to view and manipulate matrices.
The bitmap control supports entering ranges with "inf" and "-inf" (also on the custom control).
Support for scrolling while creating a rectangle selection box with the mouse.
The offline mode uses our own video frame output now instead of the Windows Enhanced Video Renderer for better performance.
The text signal array on the custom control now also works in the offline mode if the data acquisition only contains the first part of the array.
Bugfix In rare cases a deadlock occurred while updating the message window while starting a data acquisition via the test language as an example.
Test Manager Feature You can set URIs (links) as values, descriptions or user-defined data of test parameters. Clicking on such URIs while holding Ctrl executes them according to the application specified in Windows Registry.
If a user has the "arManage" access right to the database object (root object), additional operations are now enabled, such as emptying the entire trash folder, database purge, top-level sorting or modifying special database settings. Thus, this user does not necessarily need to know the PROVEtech:TA "admin" password for these operations. However, resetting passwords is still only possible for the PROVEtech:TA "admin".
If a test result has the validation status "Invalid", the icon on the left column of the "Result" tab is also set to "Invalid", regardless of whether the test result is "Pass" or "Fail".
Extended timeout dialog in the "Execute" tab.
Result tab: In the list of displayed test results, the icon in the first column can now be hidden via toolbar. If you want, you can use an emoji in the test result name instead.
Info Initially the test parameters are no longer expanded in the window.
The Basic handler "Preprocess the next test object for execution" is now also called before executing single elementary test objects, if configured in the Test Manager tab of the settings dialog.
The Basic handler "Preprocess the next test object for execution" is now also called in remote sequencer mode, if configured in the Test Manager tab of the settings dialog.
The "Overview" tab does not display the child objects of user libraries anymore. This is consistent with the execution list in the "Execute" tab.
Names and file extensions of test documents and attachments can contain space characters now. Space characters at the beginning or the end of names or file extensions are still not allowed.
If there is an error after a test execution when saving the protocols, the test result value changes to "Runtime error".
Database Feature PROVEtech:TA uses a more secure encryption method for storing newly entered database and user passwords. As a consequence, with PROVEtech:TA 2019 SE and older for these new passwords the password check fails. If you are not using older PROVEtech:TA versions, we recommend to re-enter and save your passwords to use the enhanced encryption.
Database consistency checks: Extended configuration options in the settings dialog.
Info No support anymore for Microsoft SQL Server 2008 or older.
Microsoft SQL Server ODBC driver V17.7.2
Oracle ODBC driver V19.10
PostgreSQL ODBC driver V13.01.0000
The installation package contains PostgreSQL server V13.3 in the 64-bit variant.
Basic Editor Feature There is an additional variant for script code encryption now based on a password instead of the PROVEtech:TA license. You can add encryption packages via the combo box in the Basic Editor toolbar. The execution of encrypted scripts is possible without the password, but not viewing them. However, you are responsible for your passwords. AKKA cannot recover lost passwords.
WinWrap Basic V10.50.043. It highlights simple syntax errors like missing keywords. It supports .NET version 5 via the '#Language "WWB.NET/5" special comment. The old '#Language "WWB.NET" special comment still targets .NET 4.x and stays compatible. While the .NET 5 libraries look similar to .NET 4.x, they use a completely different binary installation and are not 100% compatible. Please be aware that Microsoft does not provide long term support for .NET 5. According to Microsoft's homepage the .NET version 6 released in November 2021 shall have long term support. We do not know the relationship and compatibility between .NET 5 and 6 yet. Microsoft will support .NET 4.8 (the last 4.x version) much longer than .NET 5.
Test Language Feature Evaluation.SampleCount has the additional optional parameter "vSignalOrGroup".
Evaluation.SamplingRate has the additional optional parameter "vSignalOrGroup".
Evaluation.StartTime added.
TestParameter.Type and TestParameter.ChoiceType added.
Info In case "CAN-FRAME-TX-BEHAVIOR" is missing for a CAN triggering in the AR-XML file of the channel (= "VFrameFormat" in .dbc files), setting CanMsg.Id(True) or CanMsg.Name(True) uses the channel type to set the frame transmission type ("FD with BRS" for CAN FD channel, "Normal" for normal CAN channel).
GUI.ShowMeasure does not support the value "sam" for the parameter "strTimeBase" anymore (samples). It maps that value to "seconds". It additionally supports the value "µs" for microseconds.
Automation Library/RTAE Feature The Enum parameter "ProtType" of the command "AL.Init" has two new possible values: "ptHTMLWithSourceLinks" and "ptXMLWithSourceLinks". They add the information to the test protocol, which WinWrap Basic source code line created the according protocol entry for some of the structuring blocks like processes, concurrencies, "While" loops, etc.. For HTML it creates <a href="TestAutomation:..." links and for XML it creates the attributes "Caller" and "Line". Old PROVEtech:TA versions switch to normal HTML protocols when passing one of the new Enum values. You need to import the new "AutomationLibrary.dbi.7z" in your database to use this feature.
RT.CANChannelNameToPortNumber added to map a CAN channel name to the port number used by "RT.CANMsgMux" and "RT.CANMsgDemux".
MCD-3 D Diagnostics Feature Extended interface (D-PDU API) handling. Now it is possible to use several CAN channels. You can configure which interface and resource to use for each ECU. This means, different ECUs can be connected to different buses at the same time.