|
<< 点击显示目录 >> 主页 exOS使用助手 > exOS Automation Help > General information > Version Information > Version 2.0.0 - First pilot version |
•2.0.0 版对整个 exOS 环境进行了重大改造，进行了大量内部重构，并完成了以前版本的 "愿望清单 "和 "开放主题"。
•尽管大部分底层应用程序接口仍然兼容，但该版本与之前的 1.0.x BETA 版本不兼容。
•新的诊断功能块，使应用程序能够监控部署、执行和数据交换的状态，例如监控某个组件的执行状态或数据连接细节。这些功能块还使数据通信中的 "系统日志 "信息变得多余（只有在进行大量调试时才需要）。
•exos_api 中新增的同步事件和值可让 "在环路中 "的 Linux 应用程序全面了解 AR 和 Linux 之间的同步状态。
•为 exos-server 中的服务添加了工作目录，并对之前有关 "幽灵服务 "的 bug 进行了修正，使其在没有 root 账户（sudo 用户）的系统上也能正常运行。
•模块化：ExApi 和 ExTarget 库已被 ExData 和 ExDeploy 库取代，它们可以独立于 exOS 技术包（在其他项目中）运行。
•ExData：导出所有 exos_api 和 exos_log API 函数的库，以及两个新的 C-API 以 独立于 TP运行 消息路由器 ，即 exos_dmr 和 exos_lmr API。
•ExDeploy该库具有一个接口，可与 exOS 部署目标（exos-server）进行交互，而无需与 TP 进行任何连接。该库导出了 ExDeployApi。
•ExOS：构成 exOS TP 运行时侧的库，运行独立的 ExData 和 ExDeploy 库，通过功能块提供 ExData 和 ExDeploy 诊断。
•部署序列：允许更好的诊断（通过库中的 C-API 和 TP 中的功能块提供）
•部署序列：比较范围更广，现在还可进行 "在线更改"，即在其他组件仍在运行时交换/重启其他组件（带活动数据连接）。
•部署顺序：改进了对组件的监控，从而更容易发现运行时的错误。
•部署顺序：组件现在部署在各自的部署文件夹中，因此各组件的文件可以使用相同的名称。
•部署顺序：现在还能检测磁盘上文件大小的变化，如果目标上的文件发生变化，文件将被重新传输。
•部署顺序：部署的日志级别也与 exostarget 中设置的级别一致，这样在细节冗余的情况下（生产模式），部署序列就不会那么冗长。
•exoscomponent：允许更灵活的配置，例如通过更改 tar.gz 文件（包含解压文件的安装说明）来触发组件安装。
•exoscomponent：删除了对 .deb 文件的内置依赖，但仍允许安装 .deb 文件
•exoscomponent：在 .exospkg 文件和生成的 exoscomponent 之间创建了一种更简洁的关系，同时仍允许配置特定的附加组件。
•exoscomponent：为服务添加了可配置的工作目录，并更好地支持特殊命令（包括引号）
•exostarget：简化了配置，因此在 AS 中的配置中删除了任何可通过其他方式确定的值或具有单一 "最佳设置 "的值。
•exostarget：对于 TP 隐含需要但尚未在项目中配置的配置设置，TP 有了更好的 "辅助功能"。
•exospkg：GenerateHeader 已更改为 GenerateDatamodel，现在可生成两个文件（头文件和源文件）。当需要在对象中多次包含头文件时，这样做有很多好处。
•日志信息现在会如实显示在描述栏中，"输入单位 "也得到了简化，这样就可以更简单地筛选特定组件。
•编译输出也已简化，错误已按组归类，双击错误也会指向配置编辑器中的正确位置。
•外部 Linux-cross 编译器的输出格式化了，错误在 AS 输出中会被检测为错误，同时还提供了双击错误并进入 AS 源文件的功能。
•更好地检测 lxi 错误（如果发生）。以前，lxi 函数的返回代码被收集到一条错误信息中。现在额外的错误信息包括函数的返回代码。
•The version 2.0.0 constitutes a major rework of the entire exOS environment, with a lot of internal refactoring together with completing the "wish list" and "open topics" of previous versions.
•Even though most low-level APIs remain compatible, the version is incompatible with previous 1.0.x BETA versions.
•New Diagnostics function blocks to enable applications to monitor the status of deployment, execution and data-exchange, for example monitoring the execution status or data-connection details of a certain component. These function blocks have also made the "system log" information from the data-communication redundant (only needed in case of extensive debugging).
•Additional synchronization events and values in the exos_api enable Linux applications that are "in-the loop" have full overview of the synchronization status between AR and Linux.
•Added working directory for services in the exos-server and made a proper implementation of the previous bugfix concerning "ghost services", and it can also run perfectly fine on systems without root account (sudo users).
•Modularization: The ExApi and ExTarget libraries have been substituted with ExData and ExDeploy libraries that can operate independently of the exOS Technology package (in other projects).
•ExData: Library exporting all exos_api and exos_log API functions, as well as two new C-APIs to operate the Message Router independent of the TP, the exos_dmr and exos_lmr API.
•ExDeploy: Library with an interface able to interact with an exOS deployment target (exos-server) without any connections to the TP. This library exports the ExDeployApi.
•ExOS: Library that constitutes the runtime-side of the exOS TP, operating the independent ExData and ExDeploy libraries, offering ExData and ExDeploy diagnostics via function blocks.
•deployment sequence: Allowing for better diagnostics (available via C-APIs in the libraries and function blocks in the TP)
•deployment sequence: The comparison is more extensive and now also allows for "online changes" where components are exchanged / restarted while others are still running (with active data connection)
•deployment sequence: The monitoring of components has been improved so that runtime errors are easier to diganose.
•deployment sequence: Components are now deployed in their own deployment folder, so that files can have the same name across components.
•deployment sequence: Changes of file sizes on disk is now also detected, and if a file is changed on the target, the file will be retransferred.
•deployment sequence: The log level of the deployment also follows the level set in the exostarget so that the deployment sequence is less verbose, in situations where details are redundant (production mode).
•exoscomponent: Allowing for more flexible configurations, like triggering a component installation by changing a tar.gz fil (with the installation instruction to unpack the file).
•exoscomponent: Removed the built-in dependency on .deb files, while still allowing .deb files to be installed
•exoscomponent: Created a cleaner relation between .exospkg files and the resulting exoscomponent while still enabling configuration specific add-ons.
•exoscomponent: Added configurable working directory for services and better support for special commands (including quotes)
•exostarget: Configuration has been simplified, so that any values that could be determined by other means or had a single "best setting" have been removed from the configuration in AS.
•exostarget: The TP has better "helper functions" for configuration settings that are implicitly needed by the TP but not yet configured in the project.
•exospkg: the GenerateHeader has changed to GenerateDatamodel which now generates two files (header and source file). This has a lot of benefits when the headerfile needs to be included more than once in an object.
•Log messages now appear in the Description column as they should, and the "entered by" has been simplified so that its simpler to filter for a certain component, for example.
•Build output has been simplified, errors have been categorized in groups, and double clicking on errors will also lead to the correct position in the configuration editor.
•The output from the external Linux-cross compiler is formatted in a way that errors are detected as errors in the AS output, together with the functionailty to double click on an error and get to the source file in AS
•Better error detection for lxi errors, should they occur. Previously the return codes of the lxi functions were collected into a single error message. Now additional error messages include the return code of the functions.