H1 ITK Version 6
| ITK 6.5.0 - January 2023 |
| ||||||||||||||||||||||||||
| ITK 6.4.0 - February 2020 |
|
| ITK 6.3.1 - November 2018 |
|
| ITK 6.3.0 - December 2017 |
Known Issue:
|
ITK 6.2.0 – July 2016 |
|
ITK 6.1.2 - November 2014 |
|
ITK 6.1.1 - November 2013
|
|
ITK 6.1.0 - January 2013 |
|
ITK 6.0.1 - October 2011
|
|
ITK 6.0.0 - September 2010 |
|
H1 ITK Version 5
| ITK 5.2.0 - September 2009 | Updates included Positioner Transducer Block test cases to support the FOUNDATION fieldbus Positioner Transducer Block Final Specification (FF-906), which is key resource supporting the organization and integration of advanced device diagnostics within fieldbus systems. This specification provides standard definitions for positioner transducer blocks, including an analog positioner for basic and complex device access, a discrete positioner for basic and complex device access, and a combination analog/discrete positioner for basic and complex device access. It also includes parameter structure definitions for better data organization with fieldbus devices, including partial/full stroke test (PST/FST) of valves. The document conveniently groups parameters in function-based categories and offers a variety of helpful diagrams.
|
| ITK 5.1.0 - December 2008 | Updates supported Temperature Transducer Blocks, Device Description (DD) 5.1 functionality, and Field Diagnostics Profiles enhancing organization and integration of device diagnostics within FOUNDATION fieldbus systems. Specific enhancements included: Cross-block Device Description, National Instruments (NI) Communication Driver 3.2.2, and updated DD Viewer. Other updates included support for the FF-904 Temperature Transducer Block Specification (single and dualsensor), FF-912 Field Diagnostics Profile Specification, and Resource Block parameter set to implement the Field Diagnostics Profile.
|
| ITK 5.0.0 - September 2006 | Updates allowed testing of devices with DD 5.0 files, which provided new features focused on device data organization, graphical visualization consistency, and support for persistent data storage. Specific enhancements included: multi-bit alarm testing for both single and multi-bit alarms, which provides for more thorough testing; block instantiation as specified in the Capabilities File (CF), ensuring interoperability on a FOUNDATION fieldbus network when a block is instantiated; and testing for valid/invalid behavior during common software download, ensuring interoperability when downloading software/firmware to a device via a FOUNDATION fieldbus network.
|
H1 ITK Version 4
| ITK 4.6.1 - May 2006 |
|
| ITK 4.6.0 - July 2004 | IMPORTANT REGISTERED PRODUCT CATALOG REQUIREMENT: In 2004, the Fieldbus Foundation Board of Directors mandated all DD/CF files must be re-registered against ITK 4.6.0 and made available on the Fieldbus Foundation’s website. In 2005, an extension was offered to the original deadline to September 2005. On August 30, 2007 the Fieldbus Foundation’s Registered Product Catalog was updated to list only those devices whose DD/CF files are registered to ITK 4.6 or above. The web catalog maintains a list of registered devices to the current standards as set forth by the Fieldbus Foundation. The de-listing of a device from the registered catalog does not invalidate the device’s original registration certificate. The manufacturer can return a device to the web catalog completing a new DD/CF test for the existing device, or the manufacturer can resubmit an updated device revision for a full device test and subsequent registration (if it passes the ITK). In both scenarios, both current and prior registered devices will be listed in the web catalog. To inquire about the status of a specific registration, send us a support ticket.
|
| ITK 4.5.1 - January 2003 | 95 test cases were added to the ITK to allow the testing of new function blocks. The following blocks were approved for registration once two independent member companies implement the block successfully and pass all associated test cases in the ITK:
Other Updates:
|
| ITK 4.0.1 - February 2001 |
|
| ITK 4.0.0 - April 2000 | IMPORTANT REGISTERED PRODUCT CATALOG REQUIREMENT: From the release notes: At the October 19, 1999 Fieldbus Foundation Board of Director's meeting, the Board decided that all the registered devices must be retested and registered using the ITK 4.0 version of the ITK. All devices that test and register using ITK 4.0 must comply with the specifications, tech-notes, and app-notes associated with ITK 4.0, as outlined in the readme.txt file of the test system. The enclosed version 4.0 of the Interoperability Test System (ITS) contains modified test cases to bring the system into compliance with Fieldbus Foundation Specification Revision 1.4. Specification changes required modification and creation of a new testcase for AlarmSummary (I0603_06). The inclusion of ITK version number in the Resource Block required testcase modifications. The new Status Option required the creation of a new testcase for devices that have the option (I0501_12). The clarification of the PV Tracking when coming out of Bypass required the modification of testcases as well. ITK version 4.0 also includes Device Description Test Case modifications for Multiple View 3 and 4 implementations that make the test cases in line with the Application Note 2 on Multiple Views. A new test for the Common File Format Capabilities file(FF-103-1.5) is also included with this version(testcase I9100_00). Other modifications were made based on Action Requests that were resolved since the release of specification 1.4 This version of the ITK is approved for use in development, but not registration at this time. The test cases are testing AI, AO, DI, DO, and PID Function Blocks. After two independent implementations of a block are tested, the tester will be reviewed and released for registration of that block. (This minimum requirement of ITK 4.0 must be met in order to have the registered product published in the online product catalog on our website.)
|
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article