Arrangements, storage mediums and methods for associating an extensible stylesheet language device description file with a non- proprietary language device description file

• US 20040230899A1
• Filed: 05/13/2003
• Published: 11/18/2004
• Est. Priority Date: 05/13/2003
• Status: Abandoned Application

• Current Assignee: Smar Research Corp.
• Original Assignee: Smar Research Corp.
• Inventors: Pagnano, Marco Aurelio de Oliveira, Pantoni, Rodrigo Palucci
• Application Number:
  US10/436,956
• Publication Number:
  US 20040230899A1
• Time in Patent Office: Days
• US Class Current: 715/513
• CPC Class Codes: G05B 2219/31121 Fielddevice, field controller, interface connected to fieldbus
• CPC Class Codes: G05B 2219/32142 Define device, module description using xml format file
• CPC Class Codes: G06F 16/88 Mark-up to mark-up conversion conversion for visualization in web browsing G06F16/9577

Abstract

An arrangement, storage medium and method are provided to associate an Extensible Stylesheet Language (“XSL”) Device Description file with a non-proprietary language Device Description file. Each of the non-proprietary language Device Description file and the XSL Device Description file is associated with a particular type of a field device, and the XSL Device Description file includes a script-type language source code. For example, the non-proprietary language Device Description file can be an Extensible Markup Language Device Description file, and the script-type language source code can include a code associated with a method of implementing the field device and/or a function performed by the field device. Moreover, the non-proprietary language Device Description file and the XSL Device Description file can be converted into a platform-independent page having the script-type language source code embedded therein.

Claims

1. An arrangement, comprising:

a processing system operable to associate a particular Extensible Stylesheet Language (“

XSL”

) Device Description (“

DD”

) file with a particular non-proprietary language DD file, wherein each of the particular non-proprietary language DD file and the particular XSL DD file is associated with a particular type of a field device, and wherein the particular XSL DD file comprises a particular script-type language source code.

2. The arrangement of claim 1, wherein the particular script-type language source code is one of a Javascript®

language source code and a Visual Basic®

language source code.

3. The arrangement of claim 1, wherein the non-proprietary language DD file is an Extensible Markup Language (“

XML”

) DD file, and wherein the particular script-type language source code comprises code associated with at least one procedure for implementing the particular type of the field device.

4. The arrangement of claim 1, wherein the particular type of the field device is one of a pressure sensor, a temperature sensor, a flow-rate sensor, a valve and a switch.

5. The arrangement of claim 1, wherein the processing system is further operable to convert at least one of a particular proprietary language DD file and a particular Device Description Language (“

DDL”

) source code associated with the particular type of the field device into the particular non-proprietary language DD file.

6. The arrangement of claim 5, wherein the processing system is further operable to convert the particular non-proprietary language DD file and the particular XSL DD file into a platform-independent file which does not comprise the script-type language source code embedded therein, and to transmit the platform-independent file to a further processing arrangement.

7. The arrangement of claim 6, wherein the processing system is further operable to transmit the particular non-proprietary language DD file and the particular XSL DD file to a further processing system, and wherein the further processing system is operable to convert the particular non-proprietary language DD file and the particular XSL DD file into a platform-independent file having the script-type language source code embedded therein.

8. The arrangement of claim 7, wherein the platform-independent file is a Hypertext Markup Language (“

HTML”

) file.

9. The arrangement of claim 8, wherein the HTML file comprises at least one link associated with at least one method for implementing the particular type of the field device.

10. The arrangement of claim 9, wherein the non-proprietary language DD file is a non-binary Device Description file.

11. The arrangement of claim 10, wherein the non-binary DD file is an Extensible Markup Language (“

XML”

) DD file.

12. The arrangement of claim 10, wherein the further processing system is further operable to execute the script-type language source code, and to invoke and execute an operation of a particular component of the processing system through a remote procedure call (“

RPC”

).

13. The arrangement of claim 12, wherein the particular component is an Object Linked Embedded For Process Control component, and wherein the RPC is a Web Service.

14. The arrangement of claim 13, wherein the particular component is operable to establish a communication with the particular type of the field device.

15. The arrangement of claim 13, wherein the particular script-type language source code comprises a code associated with at least one procedure for implementing the particular type of the field device, and wherein the particular component is operable to directly or indirectly execute the at least one procedure for implementing the particular type of the field device.

17. The arrangement of claim 1, wherein the processing system is further operable to associate a further XSL DD file with a further non-proprietary language DD file, wherein the further non-proprietary language DD file is associated with a further type of a field device, wherein the further XSL DD file comprises a further script-type language source code, and wherein the further non-proprietary language DD file is different than the particular non-proprietary language Device Description file.

34. The arrangement of claim 1, wherein the field device includes a sensing device.

16. The arrangement of claim 4613, wherein the particular component is further operable to directly or indirectly configure the particular type of the field device, obtain data from the particular type of the field device, and transmit the data to the further processing system.

18. A logic arrangement, which, when executed by a processing system, configures the processing system to perform the steps comprising of:

converting at least one of a proprietary language Device Description (“

DD”

) file and a Device Description Language source code associated with a particular type of a field device into a non-proprietary language DD file; and

associating an Extensible Stylesheet Language (“

XSL”

) DD file with the non-proprietary language DD file, wherein the XSL DD file is associated with the particular type of the field device, and wherein the XSL DD file comprises a script-type language source code.

35. The logic arrangement of claim 18, wherein the field device includes a sensing device.

19. A storage medium including executable instructions thereon, wherein, when the executable instructions are executed by a processing system, the executable instructions configure the processing system to perform the steps comprising of:

converting at least one of a proprietary language Device Description (“

DD”

) file and a Device Description Language (“

DDL”

) source code associated with a particular type of a field device into a non-proprietary language DD file; and

associating an Extensible Stylesheet Language (“

XSL”

) DD file with the non-proprietary language DD file, wherein the XSL DD file is associated with the particular type of the field device, and wherein the XSL DD file comprises a script-type language source code.

36. The storage medium of claim 19, wherein the field device includes a sensing device.

20. A software arrangement, which is operable to be executed by a processing system to perform the steps comprising of:

converting at least one of a proprietary language Device Description (“

DD”

) file and a Device Description Language source code associated with a particular type of a field device into a non-proprietary language DD file; and

associating an Extensible Stylesheet Language (“

XSL”

) DD file with the non-proprietary language DD file, wherein the XSL DD file is associated with the particular type of the field device, and wherein the XSL DD file comprises a script-type language source code.

33. The method of claim 20, further comprising the steps of:

converting at least one of a further proprietary language DD file and a further DDL source code associated with a further type of a field device into a further non-proprietary language DD file; and

associating a further Extensible Stylesheet Language (“

XSL”

) DD file with the further non-proprietary language DD file, wherein the further XSL Device Description file is associated with the further type of the field device, wherein the further XSL DD file comprises a further script-type language source code, and wherein the further non-proprietary language DD file is different than the particular non-proprietary language DD file.

37. The software arrangement of claim 20, wherein the field device includes a sensing device.

21. A method, comprising the steps of:

converting at least one of a particular proprietary language DD (“

DD”

) file and a particular Device Description Language (“

DD”

) source code associated with a particular type of a field device into a particular non-proprietary language DD file; and

associating a particular Extensible Stylesheet Language (“

XSL”

) Device Description file with the particular non-proprietary language DD file, wherein the particular XSL DD file is associated with the particular type of the field device, and wherein the particular XSL Device Description file comprises a particular script-type language source code.

22. The method of claim 21, wherein the particular script-type language source code is one of a Javascript®

language source code and a Visual Basic®

language source code.

23. The method of claim 21, wherein the non-proprietary language DD file is an Extensible Markup Language (“

XML”

) DD file.

24. The method of claim 21, wherein the particular type of the field device is one of a pressure sensor, a temperature sensor, a flow-rate sensor, a valve and a switch.

25. The method of claim 21, wherein the particular script-type language source code comprises a code associated with at least one method for implementing the particular type of the field device.

26. The method of claim 21, further comprising the step of transmitting the particular non-proprietary language DD file and the particular XSL DD file to a remote processing system.

27. The method of claim 26, further comprising the step of converting the particular non-proprietary language DD file and the particular XSL DD file into a platform-independent file having the script-type language source code embedded therein.

28. The method of claim 27, wherein the platform-independent file is a Hypertext Markup Language (“

HTML”

) file.

29. The method of claim 28, wherein the HTML file comprises at least one link associated with at least one method for implementing the particular type of the field device.

30. The method of claim 29, wherein the non-proprietary language DD file is a non-binary DD file.

31. The method of claim 30, wherein the non-binary DD file is an Extensible Markup Language (“

XML”

) DD file.

32. The method of claim 30, further comprising the step of executing the script-type language source code.

38. The method of claim 21, wherein the field device includes a sensing device.