This article works as a guide to establish and summarize the best practices for developing\u00a0 Elipse E3<\/a> applications. Based on the software modules, we will list a few articles and useful tips for developing applications with this platform.<\/p>\n <\/p>\n There is a set of guidelines for developing high-performance applications; one of these guidelines is the use of Libraries. Due to their complexity and extension, some projects can be developed a lot faster when using object-oriented resources and Elipse E3 libraries, which help create simple, objective projects that require considerably less maintenance.<\/p>\n The following list features some of the articles about this subject in our Knowledgebase:<\/p>\n Elipse E3 can establish native connection with Access, Oracle, SQL Server, PostgreSQL and MySQL. Each model has its pros and cons<\/a>, and choosing between them will depend on the project’s purposes.<\/p>\n Historics <\/b>are the modules responsible for storing the application data in a Database for future analyses. They can contain primary keys<\/strong> and indexes<\/strong>. Indexes are fields (or sets of fields) previously sorted out by the database in order to improve the performance of the queries using these indexes.<\/p>\n As for Queries<\/strong>, depending on the volume of data returned or the number of objects with associated queries, the excessive build up of data can cause slowness in the system. In this case, it’s important to add a filter<\/strong> with a short time span in the variables that are responsible for filters by date.<\/p>\n You should notice that when using a Historic, or when using the Query’s Execute<\/strong> method with ImmediateExecute<\/strong> parameter as False<\/strong>, the data will pass through the database’s operation queues\u00a0 (.e3i and .e3o files) asynchronously, which improves the application’s performance. We don’t recommend activating the ImmediateExecute(True)<\/strong> method because it can potentially cause the application to crash due to database disconnection.<\/p>\n The following list features some of the articles about this subject in our Knowledgebase:<\/p>\n Although most VBScript rules apply to programming with scripts in Elipse E3, some peculiarities must be addressed here about implementing object-orientation in the system.<\/p>\n Avoid using cyclical scripts; if you can’t use associations to achieve the desired results, we recommend creating a user event that will only execute when meeting a certain condition.<\/p>\n The following tutorial illustrates how to use VBScript in Elipse E3 via practical examples and exercises; it should help the user establish their own best practices for scripts development.<\/p>\n To ensure the application’s good communication performance, we must take a series of factors into account, such as: equipment type, communication interface type, baud rate, errors rate, etc. Additionally, for better performance, you can configure some of the options directly in the I\/O driver.<\/p>\n This property establishes how writes are sent to the IOServer (synchronous or asynchronous mode). When the application’s communication underperforms, you can edit the property to unconfirmed asynchronous mode (2 – wsmAsyncUnconfirmed<\/strong>). With unconfirmed asynchronous write, E3Run sends the information to the I\/O Server and doesn’t await response; in this case, the system assumes the write has worked. Then, the application is immediately released to follow its natural course.<\/p>\n This property allows controlling feedback from writes in I\/O Tags. It only applies to readable I\/O Tags, that it, tags whose AllowRead<\/strong> property is set as True. Therefore, when the application underperforms, you can edit this property as 0 – wfWaitNextRead<\/strong>; in this case, the I\/O Tag will be read normally in the next scan.<\/p>\n This property allows read optimization or automatic grouping in I\/O Tags. It can’t be edited when the driver is running, and the default value is True. Read optimization will only take place if the I\/O driver supports this resource.<\/p>\n However, you should notice that grouping (EnableReadGrouping<\/strong>) in Elipse E3 requires a device that supports the established limits. But some equipment will only support inferior limits. In order to group tags successfully in these cases, there are drivers (such as Modicon Modbus Master ASC\/RTU\/TCP driver<\/em>) that allow customizing higher limits of supported data bytes, depending on the type of communication.<\/p>\n With Modbus driver<\/strong>, you can set this up at Customize Max. PDU Size<\/em><\/strong>; <\/em>with BACnet driver<\/strong>, choose the option Maximum number of properties per ReadPropertyMultiple request<\/strong>;<\/em> finally, when using Allen Bradley DF1 driver<\/strong>, access Max Message Bytes. <\/strong><\/em>Therefore, always check for this setting’s availability in your driver.<\/p>\n In applications with hundreds of drivers, the amount of resources required to execute the IOServer processes in each driver can exhaust the operating system’s capacity. In these cases, you may need to enable the IOServer process pool<\/strong>; to do so, go the the Domain’s settings and check the option on Properties<\/strong> tab.<\/p>\n The following list features some of the articles about this subject in our Knowledgebase:<\/p>\n It’s not unusual for visual interfaces to be designed by engineers or technicians working in the plant, and not by professional designers. However, not all engineers and technicians are well versed in design studies, which encompass notions of psychology and cognitive sciences that guide the development of modern interfaces.<\/p>\n The HighPerformance Template<\/strong> library for Elipse E3 or Elipse Power is a template for the application that summarizes the state of the art of modern design trends and applies them to the development of industrial interfaces.<\/p>\nLibraries<\/strong><\/h2>\n
\n
<\/h2>\n
Databases<\/h2>\n
Note<\/h3>\n
\n
<\/h2>\n
Scripts<\/h2>\n
\n
<\/h2>\n
Communication<\/h2>\n
Driver’s WriteSyncMode<\/strong><\/em> property<\/h3>\n
Driver’s WriteFeedBackMode<\/strong><\/em> property<\/h3>\n
Driver’s EnableReadGrouping<\/strong><\/em> property<\/h3>\n
<\/h3>\n
IOServer process pool<\/strong><\/h3>\n
\n
<\/h2>\n
Visual interface design<\/h2>\n