Twitter "jsnover" - “Microsoft Distinguished Engineer/ Lead Architect for Windows Server and System Center Datacenter/ PowerShell Architect / Science fan / Really bad speller”.
Thorsten Butz "CIMLingen 2015" - “Ich sprach auf der CIMLingen 2015 über die finale Version der “Windows PowerShell Desired State Configuration for Linux” (WPSDSCLinux)”.
“FDI host. SIMATIC PDM is ready for the future. As an FDI host, SIMATIC PDM can now also process field devices that are described in the new standardized FDI integration technology (Field Device Integration). In SIMATIC PDM, the integration, processing and display of field devices described via FDI device description packages take place similarly to the integration technologies used to date”.
SIEMENS "Delivery release: SIMATIC PDM V9.1", 2017-12-17 - “This new SIMATIC PDM V9.1 version introduces support for the new FDI technology for device integration. The standardized FDI technology is an open integration technology for field devices in parameter assignment and diagnostic tools. The Device Integration Manager (DIM) of SIMATIC PDM enables the integration of FDI device description packages created on the basis of the FDI specification V1.2.”.
FDI / FDT should bring “intelligence” and the option for dynamic configuration into device management, without the need for an expensive DCS. So local device management without the overhead of an expensive DCS is needed and wanted by customers with little budgets and little number of devices.
Just for the process industry, FDI shall reunite both FDI and EDDL.
Experts told me that:
FDI is technically obselete and just a political compromise to include those ( big ) companies which favoured EDDL over FDI in the past.
Technically FDT is sufficient for all purposes. As there are now a free FDI plugins for FDT frames, you may operate both FDT 1.2, FDT 2.0 and FDI from a single FDT 2.0 frame application.
As of 2016-02, FDI is limited to the fieldbus standards HART, Fieldbus Foundation and ”PROFIBUS PA”. According to experts, there are currently no further plans to offer support of all the fieldbus protocols supported by FDT.
iDTM-FDI by CodeWrights GmbH, a free FDI plugin for FDT frame applications - “iDTM-FDI is the FDI adapter for every FDT Host. Try it out right now, with the Tech Preview”.
ifak system GmbH "FDI Package" - “An FDI package can contain programmed user interfaces, so called UIPs – User Interface Plugins that implement complex device commissioning and diagnostic functions”.
M&M "dtmMANAGER development suite" - The license limits the development of DTMs for in-house purposes of the customer. I.e. you can´t provide self-developed DTMs to third parties as your own customers.
M&M "dtmINSPECTOR" - “The official certificate issued by the FDT Group gives your DTM the seal of approval. It confirms a DTM’s conformity to the FDT specification and therefore plays an important role in assuring your DTM’s quality... dtmINSPECTOR is the one and only DTM test and certification tool officially approved by the FDT Group”.
ABB "DAT200 Asset Vision Basic und DTM Download" - “Eine FDT-Rahmenanwendung mit moderner und anwenderfreundlicher grafischen Benutzeroberfläche. Sie stellt die Grundfunktionalitäten zur Konfiguration, Diagnose und Wartung ihrer intelligenten Feldgeräte bereit”.
Currently, FieldCare is a free frame software for Windows with .NET. Experts told me that it just supports FDT 1.2.
DeviceCare is a free frame software for Windows with .NET 3.5. Experts told me that it supports FDT 1.2 and FDT 2.0.
Endress+Hauser Messtechnik GmbH+Co. KG "FieldCare SFE500 - Universelle Gerätekonfiguration" - “FieldCare ist Endress+Hausers universelles Tool für die Feldgeräte-Konfiguration mit vielen Funktionalitäten, von der Geräteparametrisierung bis hin zu Lösungen für die Zustandsüberwachung. Am schnellsten lassen sich Feldgeräte von Endress+Hauser mit dem dedizierten Tool DeviceCare konfigurieren”.
ABB "800xA PROFIBUS Device Integration" - “With Fieldbus Builder PROFIBUS the user has the capability to configure and diagnose PROFIBUS field devices supporting data access via DP-V1 from each System 800xA client using FDT/DTM technology”.
FTD 2.0 is based on Microsoft .NET 2.0, 3.5, 4.0...
A DTM is not a static, but consists both of ( 80×86 or .NET ) code. By this, - e.g. in opposite to a static XML file like with <AutomationML> - it can dynamically change data: If you change the unit of a device parameter, e.g. metric system to US inch / feet / miles system.
There are 2 kinds of DTMs:
Communication or Gateway-DTMs”, e.g. for USB-to-PROFIBUS devices.
Device DTMs, e.g. for PROFIBUS devices connected to a PROFIBUS.
The “FDT Common Components” make it easier to develop DTMs.
I was told by experts, that “M&M” is able to generate a DTM from ProfibusDP device description, by a software generator. I was told by the same experts, that CodeWrights GmbH is able to do fast DTM development by the help of a software interpreter. So the generation of DTMs is not an easy working business modell. Anyhow, there are a few freelancers who may be hired to generate a DTM for a device.
DTMs are loaded and executed in the frame software on a Windows computer.
How to get DTMs?
In the case of Windows interface devices ( PEAK-System USB to CANBus device, Softing USB to PROFIBUS device,... ), the DTM is provided by the software developer of the windows device driver.
If the device is connected to a bus ( e.g. a CANBus or PROFIBUS device ), you need both the DTM for the Windows interface device plus the DTM for the device itself.
It might be a good market entry strategy, to start with the development of a DTM for an affordable budget-price sensor device ( by Turck, Pepperl+Fuchs, SIG, IFM... ), connected to a serial bus ( CANBus, PROFIBUS, not PROFINET ! ). The device is connected to the Windows computer by a with a Windows interface device ( USB to CANBus device, USB to PROFIBUS device,... ) shipped with a DTM by the interface device manufacturer.
DIMA "Module Type Package (MTP)" - “Zur Projektierung der gesamten Anlage benötigt der Anlagenprogrammierer die Informationen der möglichen Dienste für die Prozedur und Visualisierung vom Modulhersteller. Diese Informationen speichert der Modulhersteller bei der Programmierung seines Moduls in einer 'digitalen Visitenkarte', dem 'Modul Type Package' (MTP)”.
MTP is an adoption of the FDI / FDT concepts for module hardware, which is equipped with a user interface.
The electronics of FDI/ FDT devices is so “small”, that such devices don´t have a user interface or just a very limited user interface. Thats why FDI / FDT provide a user interface by the DTM module running in an FDI / FDT frame, on a computer used for configuration & maintainance.
Module hardware is usually so “big” that it is shipped with a full-blown user interface, which is generated by the developer using the usual PLC IDE. The idea of MTP is to export this existing data from the developer IDE, as base for a FDI / FDT user interface in a frame application on computer used for configuation & maintainance.
NAMUR "Die NE 148 ist neu erschienen" - “NE 148 “Anforderungen an die Automatisierungstechnik durch die Modularisierung verfahrenstechnischer Anlagen” (Version 22.10.2013)”.
Experts told me in 2015-06, that the forthcoming standard might be based on:
Internal modules with I/O only → FDI based interface.
External modules with a PLC → OPC/UA based interface.
GSD files contain information about the basic capabilities of a device. All devices are shipped with a GSD file, or a file can be downloaded from this web site or the vendor's own web site. With a GSD file, system integrators can determine basic data such as the communications options and the available diagnostics”.
“PROFINET GSDML Files”:
“GSDML are GSD files written in XML format. They describe the features of the PROFINET device model. GSDML editing can be accomplished with standard XML editors and should comply with ISO 15745, the base for device descriptions. The aim is to allow better integration of devices into an engineering tool”.
“It is not an objective of the GSDML format to describe technological functions or the graphical user interface of a device. For this purpose concepts such as TCI, FDT, EDD should be used”.
“Tool Calling Interface. TCI – 2006 aufgrund der Anforderungen in der Fertigungsautomatisierung durch die PNO spezifiziert – ist eine einfache Aufrufschnittstelle, um komplexe DT vom ES aufzurufen. Ziel von TCI ist es, die proprietären DT der verschiedenen Hersteller von Feldgeräten möglichst einfach an das ES anzubinden. Von einer wirklichen Integration in das ES wie bei EDD (Electronic Device Description) und FDT kann jedoch keine Rede sein”.
“Ein TCI-fähiges ES ist der Simatic-Manager von Siemens”.
“Anders als bei einer integrierten FDT-Rahmenapplikation handelt es sich bei TCI um eine Aufrufschnittstelle eines externen Tools und nicht um eine Integration der Geräteapplikation in das ES wie bei FDT. Ein Datenaustausch ist nur in Richtung vom ES zum Gerätetool definiert, nicht jedoch in Gegenrichtung”.
Programmable Logic Controllers (PLC ) and Distributed Control Systems ( DSC ) do cyclic data collection, in case of PROFIBUS DP the GSD ( “Geräte-Stamm-Datei” ) defines devices.
Acyclic data acquistion:
Asset management by EDD / DD of SIEMENS, DTM of FDT.
EDDL is intended to become the successor of both EDD and DTM/FDT.
EN.Wikipedia "OSGi", DE.Wikipedia "OSGi" - “Die Spezifikation der OSGi Service Platform definiert eine Java-basierte Laufzeitumgebung oberhalb der JVM und deren Basisdienste. Ein bedeutendes Merkmal der Service-Plattform ist die Möglichkeit, dynamisch und kontrolliert Service-Anwendungen (sogenannte Bundles) zur Laufzeit einzuspielen und – vor allem – auch zu aktualisieren und wieder zu entfernen”.
EN.Wikipedia "Equinox (OSGi)", DE.Wikipedia "Equinox (OSGi-Framework)" - “Entstanden ist das Projekt 2003, als Eclipse auf eine Plug-in-basierte Struktur umgestellt werden sollte. Um das zu ermöglichen entschied man sich, die OSGi-Plattform zu verwenden. 2004 wurde mit Eclipse 3.0 die erste auf Equinox basierende Version veröffentlicht”.
Critical feedback: Afterall, Vorto just describes the language interface by a list of functions with its parameters and return values . This is known as class diagramm... or C/C++ header file.
The ThingWorx server may parse Vorto description files.
Apple "Corporate-owned deployments made simple" - “The Device Enrollment Program provides a fast, streamlined way to deploy your corporate-owned Mac, Apple TV or iOS devices, whether purchased directly from Apple or through participating Apple Authorized Resellers”
LinkedIn "FDT/DTM" - “For professional with FDT/DTM background or experience. Automation engineers with fieldbus experience and FDT /DTM Technlogy know how to connect to each other and share ideas”.