# US 10,481,920 B2 · Method of extending the device description file of field devices and field device having an extensible device description file > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,481,920 B2 - Document ID: US10481920B2 - Status: Granted - Kind: B2 - Application number: 15/336,860 - Filed: 2016-10-28 - Published: 2017-05-04 - Granted: 2019-11-19 - Earliest claimed: 2015-10-30 - Assignees: Buerkert Werke GmbH - Applicants: Buerkert Werke GmbH - Inventors: Ralf Schmoetzer - Web page: https://patentgrep.com/patent/US10481920B2 ## CPC - G06F 9/44505: {Configuring for program initiating, e.g. using registry, configuration files} - G05B 19/0426: {Programming the control sequence} - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - G05B: CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS (systems for controlling or regulating non-electric variables G05D; systems for regulating electric or magnetic variables G05F; control devices or systems insofar as characterised by mechanical features only G05G) ## Abstract A method and system of the subject invention provides for the extension of a device description file of a field device. The device description file is loaded on a field device, the field device is put into operation with the device description file in a fieldbus system, and an extension file is loaded on the field device during the operation of the field device. The extension file contains only concrete objects. ## Claims ### Claim 1 A method for the extension of a device description file of a field device comprising: loading a device description file on a field device, putting the field device with the device description file into operation in a fieldbus system, and loading an extension file on the field device during operation of the field device, the extension file including only concrete objects, and wherein the concrete objects each comprise at least one specified parameter name, one specified data type, and one specified access type, and wherein the device description file is managed in an object dictionary of the field device, and wherein, using the extension file, the object dictionary is dynamically extended by the concrete objects at runtime. ### Claim 2 (depends on 1) The method according to claim 1, wherein the device description file and the extension file use the same syntax. ### Claim 3 (depends on 1) The method according to claim 1, wherein the device description file is an EDS (Electronic Data Sheet) device description file for the CANopen standard, the extension file is an EDS extension for the CANopen standard, and the field device is configured for a fieldbus system according to the CANopen standard. ### Claim 4 (depends on 1) The method according to claim 1, comprising: parsing the extension file and using the concrete objects after a reinitializing or a restart of the field device. ### Claim 5 (depends on 1) The method according to claim 1, wherein the at least one field device is a gateway or controller. ### Claim 6 (depends on 1) The method according to claim 1, wherein the extension file is realized with the concrete objects which are available in the fieldbus system or in a network but initially are not yet known to the at least one field device, and wherein the system permits an addition of the concrete objects on the at least one field device at runtime without having to adapt firmware of the at least one field device. ### Claim 7 (depends on 1) The method according to claim 1, wherein the device description file comprises a static part which is already present on the at least one field device and the extension file comprises a dynamic part that is loaded on the at least one field device at runtime, and wherein as soon as the extension file is present on the at least one field device, all newly added concrete objects are addressable and can be retrieved externally and be processed. ### Claim 8 (depends on 1) The method according to claim 1, wherein the extension file dynamically extends the object dictionary of the at least one field device at runtime such that the concrete objects can then be used by functions of the at least one field device during operation of the at least one field device. ### Claim 9 (depends on 8) The method according to claim 8, wherein the at least one field device includes at least one sensor that is adapted to measure and evaluate at least one value, and wherein once the extension file is loaded on the field device, the field device can determine at least one additional value not previously capable of being determined by the field device prior to the extension file being loaded. ### Claim 10 (depends on 9) The method according to claim 9, wherein field device comprises a flowmeter and where the at least one sensor measures flow, and wherein the concrete object comprises pH value that is determinable once the extension file has been loaded on the field device. ### Claim 11 (depends on 1) The method according to claim 1, including extending the object dictionary via the extension file wherein the extension is performed such that the object dictionary is extended only by concrete objects. ### Claim 12 A system comprising: a fieldbus system having at least one field device; and the system being configured to load a device description file on the field device, to put the field device with the device description file into operation in the fieldbus system, and to load an extension file on the field device during operation of the field device, and wherein the extension file only includes concrete objects, and wherein the concrete objects each comprise at least one specified parameter name, one specified data type, and one specified access type, and wherein the device description file is managed in an object dictionary of the field device, and wherein, using the extension file, the object dictionary is dynamically extended by the concrete objects at runtime. ### Claim 13 (depends on 12) The system according to claim 12, wherein the device description file is an EDS (Electronic Data Sheet) device description file for the CANopen standard, the extension file is an EDS extension for the CANopen standard, and the field device is configured for a fieldbus system according to the CANopen standard. ### Claim 14 (depends on 12) The system according to claim 12, wherein the at least one field device is a gateway or controller. ### Claim 15 (depends on 12) The system according to claim 12, wherein the extension file is realized with the concrete objects which are available in the fieldbus system or in a network but initially are not yet known to the at least one field device, and wherein the system permits an addition of the concrete objects on the at least one field device at runtime without having to adapt firmware of the at least one field device. ### Claim 16 (depends on 12) The system according to claim 12, wherein the device description file comprises a static part which is already present on the at least one field device and the extension file comprises a dynamic part that is loaded on the at least one field device at runtime, and wherein as soon as the extension file is present on the at least one field device, all newly added concrete objects are addressable and can be retrieved externally and be processed. ### Claim 17 (depends on 12) The system according to claim 12, wherein the extension file dynamically extends the object dictionary of the at least one field device at runtime such that the concrete objects can then be used by functions of the at least one field device during operation of the at least one field device. ### Claim 18 (depends on 17) The system according to claim 17, wherein the at least one field device includes at least one sensor that is adapted to measure and evaluate at least one value, and wherein once the extension file is loaded on the field device, the field device can determine at least one additional value not previously capable of being determined by the field device prior to the extension file being loaded. ### Claim 19 (depends on 18) The system according to claim 18, wherein field device comprises a flowmeter and where the at least one sensor measures flow, and wherein the concrete object comprises pH value that is determinable once the extension file has been loaded on the field device. ### Claim 20 (depends on 12) The system according to claim 12, wherein the object dictionary is extended via the extension file, and wherein the extension is performed such that the object dictionary is extended only by concrete objects.