|
<< 点击显示目录 >> 主页 exOS使用助手 > exOS Automation Help > General information > Workflow > Approaches |
在某些情况下， 开发任务 由几个人或几个团队分担。这些人或团队也可能属于不同的公司。例如，一家机械制造公司可能会与外部合作伙伴签约，由其开发基于 Linux 的特定软件。
一方面，Linux 开发团队负责提供特定功能。这个团队很可能在事件驱动编程方面拥有良好的专业知识，并熟悉 IT / 物联网概念。另一方面，机器应用团队负责创建 PLC 应用程序。该团队通常掌握 IEC 语言、运动和 I/O 处理以及循环编程方面的专业知识。
在这种情况下，需要考虑以下因素：
•Linux 程序员对 AS 软件不了解或了解有限
•Linux 程序员希望使用自己的开发环境
•exOS 软件包将以二进制形式提供给 PLC 程序员
在其他情况下，开发角色由一个团队或个人承担。这样，这一个人或团队就掌握了 Linux 开发和 PLC 编程的诀窍。
这种方法非常适合敏捷开发的情况，因为在这种情况下，Linux 和 PLC 应用程序方面都会经常发生变化。大多数情况下，Linux 和 PLC 应用程序之间也没有固定的接口，这意味着在开发过程中，接口可能会经常发生变化。
在这种情况下，需要考虑以下因素：
•由 Linux 和 PLC 软件组成的整个源代码应在一个项目中管理
•应用程序的每次构建都应涉及 Linux 和 PLC 软件
•Linux 软件的构建可以在开发 PC 上完成（交叉编译、二进制传输），也可以在目标机上完成（本地编译、源代码传输）
•可在开发 PC 上对整个应用软件进行模拟和调试
In some cases, the development roles are split between several persons or teams. Those persons or teams may also belong to different companies. For example, a machine building company may contract an external partner to create specific Linux-based software.
On one hand there is a Linux development team that is responsible for providing a specific functionality. This team has most likely good know-how in event-driven programming and is familiar with IT / IoT concepts. On the other hand, there is the machine application team that is responsible for creating the PLC application. This team typically has got know-how in IEC languages, motion and I/O handling and cyclic programming.
In such situation, the following considerations apply:
•The Linux programmers have no/limited know-how of Automation Studio
•The Linux programmers want to use their own development environment
•The exOS Package will be provided to the PLC programmers in binary form
In other cases, the development roles are combined in a single team or person. So, this single person or team has got know-how of Linux development and PLC programming.
This approach is ideal in case of a very agile development, where changes are frequently made on both, the Linux and the PLC application side. Mostly, there is also no fixed interface between the Linux and the PLC application, meaning that this interface may change frequently during development.
In such situation, the following considerations apply:
•The whole source code consisting of Linux and PLC software shall be managed in a single project
•Each build of the application shall involve both Linux and PLC software
•The build of the Linux software may be done on the development PC (cross-compile, binary transfer) or on the target (native compile, source transfer)
•Simulation and debugging of the whole application software shall be possible on the development PC