Use of variables in a number of automation systems

Abstract

There is described a method and system for using at least one variable of a first automation system in a second automation system, with the variable being made available by the first automation system. An object is to allow a user to program access to a local and remote variable in an identical manner, without having to program special access functions, set up connections and apply a local variable to take up the variable value or to create additional assignment tables and similarly apply the local variable. This object is achieved with a method and system of the type mentioned above, in that an identification feature is used for the unique identification of the variable in the at least second automation system, said identification feature being hierarchically structured and having a system-specific path name and a name for the variable.

Description

BRIEF DESCRIPTION OF THE DRAWING

The invention is described in more detail below with reference to the exemplary embodiment shown in the sole FIGURE, in which:

FIG. 1 shows a schematic diagram of two automation systems, using the same variable.

Claims

1.-26. (canceled)

27. A method for using a variable of a first automation system in a second automation system, comprising: making the variable available by the first automation system to the second automation system; andusing an hierarchically structured identification feature having a system-specific path name and a variable name in order to a uniquely identify the variable within the second automation system.

28. The method as claimed in claim 27, wherein the identification feature has individual components which are separated from each other by a separating feature.

29. The method as claimed in claim 28, wherein a user selects the variable in a program editor from a list of variables and the program editor automatically creates the identification feature.

30. The method as claimed in claim 29, wherein the identification feature of the variable is inputted into a program editor by a user and the user is always offered an up to date selection of the identification features, the identification feature is corresponding to the identification feature input to date.

31. The method as claimed in claim 27, wherein a proxy variable is applied in the second automation system, the proxy variable having the same data type and having the same value as the variable of the first automation system identified by the identification feature.

32. The method as claimed in claim 31, wherein the proxy variable is cyclically updated.

33. The method as claimed in claim 32, wherein an configured initial value of the proxy variable is used, if an error occurs during a first access by the second automation system to the first automation system.

34. The method as claimed in claim 32, wherein the last value of the proxy variable is retained as the current value, if an error occurs during a further access than the first access by the second automation system to the first automation system.

35. The method as claimed in claim 31, wherein an error event in the second automation system is initiated, if an error occurs during access by the second automation system to the first automation system, wherein a specific algorithms for a response to the access error is executed in a user program.

36. The method as claimed in claim 35, wherein the first automation system makes all variables available to the second automation system having a characteristic specified by a user.

37. The method as claimed in claim 28, wherein the variable of the first automation system is accessible from the second automation system only by a request made by the second automation system.

38. The method as claimed in claim 37, wherein the quantity of variables made available in the first automation system is limited by a user.

39. An automation system, comprising: a first automation systems having a variable;a second automation system that uses the variable of the first automation system; andan hierarchical structured identification feature for a unique identification of the variable in the second automation system, wherein a system-specific path name and a variable name is used as individual components for the hierarchical structure.

40. The automation system as claimed in claim 39, wherein a separating feature separates the individual components from each other.

41. The automation system as claimed in claim 40, wherein the second automation system has a program editor to select the variable by a user from a list of variables.

42. The automation system as claimed in claim 41, wherein the second automation system has a program editor to input the identification feature of the variable by a user, wherein the program editor offers a selection and an actual display of identification features, which correspond to the identification feature input made by the user.

43. The automation system as claimed in claim 41, wherein the variable has a data type and a value and the second automation system has the variable of the same data type and with the same value as the variable of the first automation systems identified by the identification feature, wherein the proxy variable is cyclical updated.

44. The automation system as claimed in claim 43, wherein a configurable initial value of the proxy variable is provided, if an error occurs during a first access by the second automation systems to the first automation system, wherein the last value of the proxy variable is used as a current value, if an error occurs during a further access than the first access by the second automation system to the first automation system.

45. The automation system as claimed in claim 44, wherein an error event is initiated in a user program of the second automation system, causing an execution of specific algorithms in a user program to respond to the error, if an error occurs during access by the second automation system to the first automation system.