Our company, Industrial Data Xchange, shares its name with our software suite, IDX. IDX first came into being in 1995 as an industrial data communications suite at a time when there were few options when interconnecting real-time data systems between vendors. The original IDX concept is fairly straightforward – it provides a pool of tags (or Slots) to which various modules, akin to plugins, can commonly read and write real-time data using Actions. The trick is that the modules implement the custom code to interface with a specified system but also know how to share data into the IDX tag pool. Therefore, as long as one has the modules developed for the system one wants to share data between, IDX becomes a common real-time data hub. Over time, many PLC, DCS and protocol-specific modules were developed, but for us, the most frequently used are OPC DA, IDX TCP (our proprietary TCP protocol), @aGlance, Gensym G2 and MODBUS, in the various flavours.
Today, IDX 7 is largely still based on the original IDX concept, and has proved reliable while extensible over the years and is still in use as our primary data exchange product. However, early 2011 we released IDX 8 which, while carrying the same name as its predecessor, now has a much wider functionality footprint. Whereas IDX 7 addresses real-time data exchange only, IDX 8 introduces a common platform for all our industrial communications solutions. The goal is to tightly integrate our various products in a common, user friendly platform that can scale from simple, single machine installations to enterprise-wide deployments which can be managed from a single point.
Currently, IDX 8 provides Tag Management, Data Exchange, Alarms and Events and Historian functionality. These function modules are separately licensed items that provide specific, yet often overlapping functionality:
· Tag Management - synchronise tag configuration between systems
· Real-time Data Exchange – share real-time data between systems
· Alarms and Events (Emails/SMS) – generate human-readable events
· Historian – store real-time data history
In the next few blog posts, will be providing a general overview of the various modules in IDX 8, interesting features and new developments.
Popular posts from this blog
Last week IDX were called to site at a large commercial residence building in Pretoria, South Africa. Where our client was implementing an IoT solution for remote monitoring and control of various HVAC and power systems in the building. The control system the SI chose in this case was a Modbus enabled Industrial Micro PC called the Revolution PI. The client had Modbus sensors connected to boilers, air conditioning systems, ventilation systems and power meters. The Modbus communications between the controller and the sensors were intermittently failing due to various installation and implementation faults: 1. Earthing and Shielding Within any fieldbus communication installation, one of the requirements to ensure uninterrupted operation is to implement adequate grounding and shielding techniques. Effective grounding and Shielding help to prevent electrostatic and electromagnetic pickup, which can lead to failed communications. Some of the shielding and grounding req
Tag management of real-time data systems can prove challenging. As an industrial IT company we frequently come across the problem where tags need to be migrated from one system to another or where tags need to be synchronised and maintained between systems including historians. Generally, this ends up being a manual process, often involving Excel and much diligence and patience of the maintainer’s behalf. IDX Unifig was the first incarnation of a tool we designed with the aim to simplify the migration and management of tags between systems. The tool worked, but with as with most first editions of software tools, we could see the need for improvement and refinement of the approach used. Thus Tag Manager was born, and has become the key stone in the IDX 8 software suite. All other IDX 8 modules, such as Data Exchange, Alarms and Events and the Historian use Tag Manager to store and reference tags. The comparison result we like to see - no changes. Tag Manager employs a plug
Quick guide to get access to the P+F advanced diagnostic module via RS485 and COM converter. In order to do this, you need an RS485 converter which can convert RS485 to either ethernet or USB. I used a device from HMS (Anybus) called the Serial Server ( AB7701 ). This device connects to RS232, 422 or 485 and makes the data available over ethernet to your computer using a virtual com port. Connect the converter to the Diagnostic bus connection on the Pepperl & Fuchs fieldbus power hub 1. Once you have the com port available on your PC, Check the comport number via “manage my computer” Make sure that the FieldConnexd Diagnostic server (FDS) is running. Go to “Windows button”>“All programs” > “Pepperl+Fuchs” and start FDS control center In case the FDS is not running click onto “Start FDS” (in case it is running nothing is left to do here) click onto “Hide”. To avoid that this piece of software will be forgotten in future click onto settings and choose un