{"id":2881,"date":"2019-03-25T17:41:40","date_gmt":"2019-03-25T20:41:40","guid":{"rendered":"http:\/\/xexeu.elipse.com.br\/pt\/developing-applications-with-optimum-performances\/"},"modified":"2019-10-18T10:53:13","modified_gmt":"2019-10-18T13:53:13","slug":"developing-applications-with-optimum-performances","status":"publish","type":"post","link":"https:\/\/kb.elipse.com.br\/en\/developing-applications-with-optimum-performances\/","title":{"rendered":"Developing applications with optimum performances."},"content":{"rendered":"<p>&nbsp;<\/p>\n<div style=\"text-align: justify;\">\n<p><span style=\"font-weight: bold;\">Using Elipse SCADA&#8217;s 32-bit version<\/span><\/p>\n<p>With Elipse SCADA&#8217;s 32-bit version, each I\/O driver can work separately, which will enhance the application&#8217;s performance greatly. This can be noticed especially when working with slow modems or I\/O drivers (1200, 9600, or 19200 bps, for example). To put I\/O drivers in background, click <span style=\"font-weight: bold;\">Advanced <\/span>button on the driver&#8217;s settings page (inside Organizer), uncheck <span style=\"font-weight: bold;\">Keep behavior 16-bits<\/span> option, and decide whether the driver will write in background. Please notice that some I\/O drivers cannot be put in background.<\/p>\n<p><span style=\"font-weight: bold;\">Using tag blocks<\/span><\/p>\n<p>Creating as many block tags as possible instead of PLC tags is highly encouraged. Block tags are sets of PLC tags that transfer more information (tags) in less time. They are used especially to monitor alarms and tags recorded in historics (which are always communicating) or screens loaded with data, thus streamlining the communication process. Block tags are usually memory (or input\/output) sequences where the block&#8217;s initial and final addresses are indicated. Unused block elements can be deleted in the Organizer. Use <span style=\"font-weight: bold;\">Cross-Reference<\/span> page to check which elements had been used.<\/p>\n<p><br style=\"font-weight: bold;\" \/><span style=\"font-weight: bold;\">Scan time<\/span><br style=\"font-weight: bold;\" \/><br \/>\nThe application&#8217;s scan time for block and PLC tags require careful planning. For each block or PLC tag in the system, ask yourself, <span style=\"font-style: italic;\">&#8220;What is the ideal update time for this tag?&#8221;<\/span>. This question will usually lead to other questions, such as <span style=\"font-style: italic;\">&#8220;What is the system&#8217;s\/PLC&#8217;s update time?&#8221;<\/span>, or <span style=\"font-style: italic;\">&#8220;Does this variable really need to be updated every 1 second? Could it be updated every 5 seconds instead without compromising the system?&#8221;<\/span>. The answer to these questions will lead high-priority variables to be read more frequently than the others, which will make Elipse SCADA work smoothly. Another point worth making is that write-only variables do not need to have their <span style=\"font-weight: bold;\">Enable scan reading<\/span> or <span style=\"font-weight: bold;\">Enable automatic reading<\/span> options checked, thus keeping them from being read unnecessarily.<\/p>\n<p><br style=\"font-weight: bold;\" \/><span style=\"font-weight: bold;\">Communication speed<\/span><br style=\"font-weight: bold;\" \/><br \/>\nCommunication speed must be set up, whenever possible, for the maximum value allowed by the device, thus enhancing the performance in the system being monitored. If several communication errors are found (occasional errors can be suppressed with 1 or 2 communication retries), you must first try to set up the communication time-out (usually between 20 and 50 ms) and, if necessary, decrease speed gradually until the ideal condition is reached. Distances and installation conditions are decisive factors for data communication between the computer and the data acquisition device.<\/p>\n<p><span style=\"font-weight: bold;\">Tags&#8217; &#8220;advise&#8221;<\/span><\/p>\n<p>Elipse SCADA does not communicate periodically with all tags in the system at the same time; this would mean chaos in terms of performance. Its communication is managed and prioritized then on what we call the &#8220;advise&#8221; mode. If a certain tag is said to be on &#8220;advise&#8221; (tag property), it means it is ready to be periodically updated by Elipse SCADA, and to have its value informed to the objects linked to it. For example, when a screen is activated, Elipse SCADA shows all objects on this screen and starts the &#8220;advise&#8221; mode of all the tags linked to those objects. In other words, each tag referenced on that screen will be read automatically, in the frequency informed in the tag&#8217;s scan. Other objects that can force the tags&#8217; &#8220;advise&#8221; mode are activated historics and alarms enabled for the object. This is how Elipse SCADA manages tags communication, thus avoiding communication with unnecessary variables under certain circumstances.<\/p>\n<p><span style=\"font-weight: bold;\"><span style=\"font-style: italic;\">OnCommError <\/span>script<\/span><\/p>\n<p>Whenever a communication error occurs, Elipse SCADA will automatically call an <span style=\"font-style: italic;\">OnCommError <\/span>script to perform specific, user-defined tasks. A communication error will only be generated after the number of retries set up in the driver&#8217;s communication parameters is reached. Examples of this script&#8217;s user-defined tasks can be deactivating the driver, or deactivating reading\/writing the tag that caused the communication error, in case a certain device in the system breaks down. To do so, you must filter the desired tags via the I\/O driver&#8217;s <span style=\"font-style: italic;\">AddFilter()<\/span> function.<\/p>\n<p><span style=\"font-weight: bold;\">Windowed screens<\/span><\/p>\n<p>Please notice that windowed screens have a distinct behavior: tags belonging to an open screen in the system have their communication activated according to the scan defined for each tag, so whenever windowed screens overlap, more communication &#8220;windows&#8221; are opened, and communication with the active variables on the hidden screens is still sustained. This will needlessly degrade the whole system&#8217;s performance, not only regarding communication, but also because of the amount of memory required in this situation.\u00a0 To fix this, you must close the overlapping windows (<span style=\"font-style: italic;\">Hide <\/span>function) with the same command that opens the other windows. Another option is using full screens instead of windowed screens, because these are deactivated automatically whenever a new full screen is open.<\/p>\n<p><span style=\"font-weight: bold;\">Active screens<\/span><\/p>\n<p>The initial screens of an application are all of those whose <span style=\"font-style: italic;\">Visible <\/span>property is on. Therefore, they are all going to be loaded alongside the application, thus slowing down this process, and using up unnecessary resources. Also, those screens will overlap, which clutters the system&#8217;s appearance. That is why it is recommended that you activate only the screen to be displayed at the beginning of the application while keeping all other screens closed. The same must be done when setting the application, because once an application is saved and closed, all screens that were open at that moment will open again the next time the application is opened by the configurator. Then, close all windows (or keep only one open) before saving your application. Following these procedures, loading your application will surely be easier the next time.<\/p>\n<p><span style=\"font-weight: bold;\"><span style=\"font-style: italic;\">WhileRunning <\/span>scripts<\/span><\/p>\n<p>These scripts run constantly whenever the application is executed or a screen is opened, and they usually spend more processing time than other scripts. With <span style=\"font-style: italic;\">ScriptWindow() <\/span>function, you can check, at runtime, how long will each script take to be executed. The better this time is estimated, the better the system&#8217;s performance is.<\/p>\n<p><br style=\"font-weight: bold;\" \/><span style=\"font-weight: bold;\"><span style=\"font-style: italic;\">Compile Script<\/span>, <span style=\"font-style: italic;\">Build Scripts<\/span>, and <span style=\"font-style: italic;\">Rebuild All Scripts<\/span> buttons<\/span><\/p>\n<p>Before executing an application in Elipse SCADA, you must check it for scripts errors. This task is really important, since scripts with syntax errors will not be executed. To check them easily, use <span style=\"font-weight: bold;\">Compile Script<\/span>, <span style=\"font-weight: bold;\">Build Scripts<\/span>, and <span style=\"font-weight: bold;\">Rebuild All Scripts<\/span> buttons, located on the lower half of the Organizer. <span style=\"font-weight: bold;\">Compile Script<\/span> button checks for errors in the script being currently edited; however, you must notice that this button does not check for errors in the other scripts in the application. <span style=\"font-weight: bold;\">Build Scripts<\/span> button verifies only unchecked scripts. <span style=\"font-weight: bold;\">Rebuild All Scripts<\/span> button checks all scripts in the application, whether they have been already edited or not. Though the operation generated by <span style=\"font-weight: bold;\">Rebuild All Scripts<\/span> button takes considerably more time than the one generated by <span style=\"font-weight: bold;\">Build Scripts<\/span> button, especially in larger applications, this extra time is very useful for preventing errors in script execution.<\/p>\n<p><span style=\"font-weight: bold;\">Historics<\/span><\/p>\n<p>The recording time for Historics must be set up according to the application&#8217;s real needs, and taking the tags&#8217; scan time into consideration: it is no use recording the Historic every 1 second if tags&#8217; scan is every 5 seconds. Since the Historic accesses the disk, you must avoid smaller scan times whenever possible. An option in such cases is having event-activated Historics, that is, Historics that are activated whenever <span style=\"font-style: italic;\">WriteRecord()<\/span> function is activated in a script, which avoid scan times (you must uncheck <span style=\"font-weight: bold;\">Use the Write Time to Save Records<\/span> option).<\/p>\n<div align=\"justify\">When you wish to record several records in a historic file that is set to record data per events (<b>Enable historic per scan <\/b>option disabled), such as by copying data from a file to another or by reading the PLC&#8217;s events buffer, you will get a significantly enhanced performance if you open the historic just once with <i>Open(<\/i>) function, write all necessary records via <i>WriteRecord()<\/i> function, and then close them all via <i>Close()<\/i> function. This keeps the historic from having to be opened and closed every write operation.<\/div>\n<p>Please remember that all tags belonging to an active Historic update constantly, communicating at every scan period.<\/p>\n<p><span style=\"font-weight: bold;\">Animation<\/span><\/p>\n<p>Animation objects, such as large, colorful (high or true color) bitmaps, slow down system execution. Animation bitmaps must be developed with the exact size they will be used and with as few colors as possible for better performance.<\/p>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>&nbsp; Using Elipse SCADA&#8217;s 32-bit version With Elipse SCADA&#8217;s 32-bit version, each I\/O driver can work separately, which will enhance the application&#8217;s performance greatly. This can be noticed especially when&hellip;<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_exactmetrics_skip_tracking":false,"_exactmetrics_sitenote_active":false,"_exactmetrics_sitenote_note":"","_exactmetrics_sitenote_category":0},"categories":[770,783],"tags":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v19.8 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Developing applications with optimum performances. - Elipse Knowledgebase<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/kb.elipse.com.br\/en\/developing-applications-with-optimum-performances\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Developing applications with optimum performances.\" \/>\n<meta property=\"og:description\" content=\"&nbsp; Using Elipse SCADA&#8217;s 32-bit version With Elipse SCADA&#8217;s 32-bit version, each I\/O driver can work separately, which will enhance the application&#8217;s performance greatly. This can be noticed especially when&hellip;\" \/>\n<meta property=\"og:url\" content=\"https:\/\/kb.elipse.com.br\/en\/developing-applications-with-optimum-performances\/\" \/>\n<meta property=\"og:site_name\" content=\"Elipse Knowledgebase\" \/>\n<meta property=\"article:publisher\" content=\"http:\/\/www.facebook.com\/elipsesoftware\" \/>\n<meta property=\"article:published_time\" content=\"2019-03-25T20:41:40+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2019-10-18T13:53:13+00:00\" \/>\n<meta name=\"author\" content=\"Elipse Software\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Elipse Software\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/kb.elipse.com.br\/en\/developing-applications-with-optimum-performances\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/kb.elipse.com.br\/en\/developing-applications-with-optimum-performances\/\"},\"author\":{\"name\":\"Elipse Software\",\"@id\":\"https:\/\/kb.elipse.com.br\/#\/schema\/person\/def69ea453ea60b250497b89225a9f87\"},\"headline\":\"Developing applications with optimum performances.\",\"datePublished\":\"2019-03-25T20:41:40+00:00\",\"dateModified\":\"2019-10-18T13:53:13+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/kb.elipse.com.br\/en\/developing-applications-with-optimum-performances\/\"},\"wordCount\":1358,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/kb.elipse.com.br\/#organization\"},\"articleSection\":[\"Elipse Scada\",\"Performance\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/kb.elipse.com.br\/en\/developing-applications-with-optimum-performances\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/kb.elipse.com.br\/en\/developing-applications-with-optimum-performances\/\",\"url\":\"https:\/\/kb.elipse.com.br\/en\/developing-applications-with-optimum-performances\/\",\"name\":\"[:pt]Developing applications with optimum performances.[:en]Developing applications with optimum performances.[:] - Elipse Knowledgebase\",\"isPartOf\":{\"@id\":\"https:\/\/kb.elipse.com.br\/#website\"},\"datePublished\":\"2019-03-25T20:41:40+00:00\",\"dateModified\":\"2019-10-18T13:53:13+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/kb.elipse.com.br\/en\/developing-applications-with-optimum-performances\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/kb.elipse.com.br\/en\/developing-applications-with-optimum-performances\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/kb.elipse.com.br\/en\/developing-applications-with-optimum-performances\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"In\u00edcio\",\"item\":\"https:\/\/kb.elipse.com.br\/en\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Developing applications with optimum performances.\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/kb.elipse.com.br\/#website\",\"url\":\"https:\/\/kb.elipse.com.br\/\",\"name\":\"Elipse Knowledgebase\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/kb.elipse.com.br\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/kb.elipse.com.br\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/kb.elipse.com.br\/#organization\",\"name\":\"Elipse Software\",\"url\":\"https:\/\/kb.elipse.com.br\/\",\"sameAs\":[\"http:\/\/www.facebook.com\/elipsesoftware\"],\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/kb.elipse.com.br\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/kb.elipse.com.br\/wp-content\/uploads\/2019\/05\/schererelipse-com-br\/logoElipse.png\",\"contentUrl\":\"https:\/\/kb.elipse.com.br\/wp-content\/uploads\/2019\/05\/schererelipse-com-br\/logoElipse.png\",\"width\":161,\"height\":58,\"caption\":\"Elipse Software\"},\"image\":{\"@id\":\"https:\/\/kb.elipse.com.br\/#\/schema\/logo\/image\/\"}},{\"@type\":\"Person\",\"@id\":\"https:\/\/kb.elipse.com.br\/#\/schema\/person\/def69ea453ea60b250497b89225a9f87\",\"name\":\"Elipse Software\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/kb.elipse.com.br\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/ff1f7ec38f4687b06f6851d97b3cd2d0?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/ff1f7ec38f4687b06f6851d97b3cd2d0?s=96&d=mm&r=g\",\"caption\":\"Elipse Software\"},\"url\":\"https:\/\/kb.elipse.com.br\/en\/author\/webmasterelipse-com-br\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Developing applications with optimum performances. - Elipse Knowledgebase","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/kb.elipse.com.br\/en\/developing-applications-with-optimum-performances\/","og_locale":"en_US","og_type":"article","og_title":"[:pt]Developing applications with optimum performances.[:en]Developing applications with optimum performances.[:] - Elipse Knowledgebase","og_description":"&nbsp; Using Elipse SCADA&#8217;s 32-bit version With Elipse SCADA&#8217;s 32-bit version, each I\/O driver can work separately, which will enhance the application&#8217;s performance greatly. This can be noticed especially when&hellip;","og_url":"https:\/\/kb.elipse.com.br\/en\/developing-applications-with-optimum-performances\/","og_site_name":"Elipse Knowledgebase","article_publisher":"http:\/\/www.facebook.com\/elipsesoftware","article_published_time":"2019-03-25T20:41:40+00:00","article_modified_time":"2019-10-18T13:53:13+00:00","author":"Elipse Software","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Elipse Software","Est. reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/kb.elipse.com.br\/en\/developing-applications-with-optimum-performances\/#article","isPartOf":{"@id":"https:\/\/kb.elipse.com.br\/en\/developing-applications-with-optimum-performances\/"},"author":{"name":"Elipse Software","@id":"https:\/\/kb.elipse.com.br\/#\/schema\/person\/def69ea453ea60b250497b89225a9f87"},"headline":"Developing applications with optimum performances.","datePublished":"2019-03-25T20:41:40+00:00","dateModified":"2019-10-18T13:53:13+00:00","mainEntityOfPage":{"@id":"https:\/\/kb.elipse.com.br\/en\/developing-applications-with-optimum-performances\/"},"wordCount":1358,"commentCount":0,"publisher":{"@id":"https:\/\/kb.elipse.com.br\/#organization"},"articleSection":["Elipse Scada","Performance"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/kb.elipse.com.br\/en\/developing-applications-with-optimum-performances\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/kb.elipse.com.br\/en\/developing-applications-with-optimum-performances\/","url":"https:\/\/kb.elipse.com.br\/en\/developing-applications-with-optimum-performances\/","name":"[:pt]Developing applications with optimum performances.[:en]Developing applications with optimum performances.[:] - Elipse Knowledgebase","isPartOf":{"@id":"https:\/\/kb.elipse.com.br\/#website"},"datePublished":"2019-03-25T20:41:40+00:00","dateModified":"2019-10-18T13:53:13+00:00","breadcrumb":{"@id":"https:\/\/kb.elipse.com.br\/en\/developing-applications-with-optimum-performances\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/kb.elipse.com.br\/en\/developing-applications-with-optimum-performances\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/kb.elipse.com.br\/en\/developing-applications-with-optimum-performances\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"In\u00edcio","item":"https:\/\/kb.elipse.com.br\/en\/"},{"@type":"ListItem","position":2,"name":"Developing applications with optimum performances."}]},{"@type":"WebSite","@id":"https:\/\/kb.elipse.com.br\/#website","url":"https:\/\/kb.elipse.com.br\/","name":"Elipse Knowledgebase","description":"","publisher":{"@id":"https:\/\/kb.elipse.com.br\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/kb.elipse.com.br\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/kb.elipse.com.br\/#organization","name":"Elipse Software","url":"https:\/\/kb.elipse.com.br\/","sameAs":["http:\/\/www.facebook.com\/elipsesoftware"],"logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/kb.elipse.com.br\/#\/schema\/logo\/image\/","url":"https:\/\/kb.elipse.com.br\/wp-content\/uploads\/2019\/05\/schererelipse-com-br\/logoElipse.png","contentUrl":"https:\/\/kb.elipse.com.br\/wp-content\/uploads\/2019\/05\/schererelipse-com-br\/logoElipse.png","width":161,"height":58,"caption":"Elipse Software"},"image":{"@id":"https:\/\/kb.elipse.com.br\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/kb.elipse.com.br\/#\/schema\/person\/def69ea453ea60b250497b89225a9f87","name":"Elipse Software","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/kb.elipse.com.br\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/ff1f7ec38f4687b06f6851d97b3cd2d0?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/ff1f7ec38f4687b06f6851d97b3cd2d0?s=96&d=mm&r=g","caption":"Elipse Software"},"url":"https:\/\/kb.elipse.com.br\/en\/author\/webmasterelipse-com-br\/"}]}},"_links":{"self":[{"href":"https:\/\/kb.elipse.com.br\/en\/wp-json\/wp\/v2\/posts\/2881"}],"collection":[{"href":"https:\/\/kb.elipse.com.br\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/kb.elipse.com.br\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/kb.elipse.com.br\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/kb.elipse.com.br\/en\/wp-json\/wp\/v2\/comments?post=2881"}],"version-history":[{"count":2,"href":"https:\/\/kb.elipse.com.br\/en\/wp-json\/wp\/v2\/posts\/2881\/revisions"}],"predecessor-version":[{"id":9197,"href":"https:\/\/kb.elipse.com.br\/en\/wp-json\/wp\/v2\/posts\/2881\/revisions\/9197"}],"wp:attachment":[{"href":"https:\/\/kb.elipse.com.br\/en\/wp-json\/wp\/v2\/media?parent=2881"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/kb.elipse.com.br\/en\/wp-json\/wp\/v2\/categories?post=2881"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/kb.elipse.com.br\/en\/wp-json\/wp\/v2\/tags?post=2881"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}