[Live Data] – In some rare cases where a device in the eLynx Application sourced data from two different types of field hardware, the Demand Scan action could result in data being returned for only one of the field devices. Our team researched this issue and resolved the problem.
[Liquid Production] – We found an issue with Liquid Production calculations that could cause the prior day production value to be inaccurate when a specific start date was passed in. The team performed testing to detail the behavior of this bug and corrected it.
[Scheduled Reports] – Some scheduled reports began to fail after our previous code deployment on July 6th. The team rolled back some of the code that was deployed around Reporting and Exports to investigate and isolate the source of the problem. Rolling back the deployed code fixed the issue with scheduled reports.
[Graph Tools] – All of the Graph tools in the application previously had a max limit for y-axes. This limit was included several versions back to prevent users from creating a Graph that had so many axes, no data would be displayed. As screens have increased in size, this limit no longer seems practical. Rather than raising the limit, the team decided to just remove it all together. Users can now configure as many y-axes as they like.
[String Data Support] – We have added support for bringing string data into the eLynx system. We can now process and store groups of letters, words, phrases, and other non-numeric data. We can gather this data directly from field equipment eLynx is polling, and also through data we import from other SCADA systems. String data can be used in common tools such as Summary Listing, Reporting, and Device Details. We have also added support for alarming on string values. Please contact our Support teamfor more information on our string data support.
[Search] – The search feature has been updated to return Tank Batteries in the results. Just like Devices and Wells, you will see a dedicated section for any Tank Batteries that match your search criteria.
[Device & Well Details] – The display for Tags in alarm at the Device and Well level has been updated to match the behavior of Summary Listing. The cell will now be shaded with the background color defined in the alarm settings. Previously, the cell remained white, and the text changed color. This change should make it easier to read Tag values when the alarm is using non-standard colors.
[Historical Data] – We have flipped the sort order on the Historical Data view based on timestamp. It now displays the most recent values at the top, making it easier to look back over the dataset.
[Historical Data] – The Historical Data view will now query 7 days back in an effort to provide more data when you load the page. For wells that have recently had communication issues, this should display more data without the need to adjust the timeframe.
[Comm Management] – The Comm Management tool now supports adding new Comm Objects from scratch. This allows users to define a new Comm Object and link it to any existing Devices. Users with access to the Comm Management tool can now change and update their field hardware without contacting eLynx Support.
[Rules Engine] – We have added support for Alarm Schemes to our Rules Engine. Alarm Schemes allow you to build tiered escalations with options for delays and repeats to ensure your team is aware of all field issues. The Rules Engine can be used to create multi-conditional alarms that record transactional Events. Contact our Support Team to learn more.
Please sign in to leave a comment.