Systems, devices, and methods for acceptance testing a fieldbus component configuration program

• US 6,963,814 B2
• Filed: 12/11/2003
• Issued: 11/08/2005
• Est. Priority Date: 12/23/2002
• Status: Expired due to Fees

• Current Assignee: Siemens Industry Incorporated (Siemens AG)
• Original Assignee: Siemens Energy & Automation Incorporated (Siemens AG)
• Inventors: Jones, John David, Hausman, Steven Michael
• Primary Examiner(s): Assouad, Patrick J.
• Application Number:
  US10/734,010
• Publication Number:
  US 20040193396A1
• Time in Patent Office: 698 Days
• Field of Search: 709/201, 709/208, 709/223, 709/230, 700/2, 700/9, 700/19, 700/20, 702/123, 702/122, 702/188, 702/119, 710/8, 710/15, 713/1, 703/13, 703/21, 703/22
• US Class Current: 702/119
• CPC Class Codes: G06F 11/221 to test buses, lines or interfaces, e.g. stuck-at or open line faults
• CPC Class Codes: G06F 11/261 by simulating additional hardware, e.g. fault simulation

Abstract

Certain exemplary embodiments comprise a method for acceptance testing a fieldbus component configuration program. The method can comprise providing simulated input information to the fieldbus component configuration program. The method can further comprise comparing outputs from the fieldbus component configuration program to predetermined outputs. In certain exemplary embodiments, the method can comprise determining if the fieldbus component configuration program output is faulty.

Claims

1. A method for acceptance testing a fieldbus component configuration program comprising:

providing a plurality of simulated inputs to a fieldbus component configuration program; and

comparing an output from the fieldbus component configuration program to a predetermined output.

2. The method of claim 1, further comprising:

generating the plurality of simulated inputs.

3. The method of claim 1, wherein the fieldbus component configuration program relates to an actuator-sensor interface network.

4. The method of claim 1, further comprising:

determining if the fieldbus component configuration program output is faulty.

5. The method of claim 1, further comprising:

logging a faulty fieldbus component configuration program output.

6. The method of claim 1, further comprising:

logging information obtained from the fieldbus component configuration program.

7. The method of claim 1, further comprising:

providing to a user a log comprising a faulty fieldbus component configuration program output.

8. The method of claim 1, wherein at least one of the simulated inputs is associated with at least one master.

9. The method of claim 1, wherein at least one of the simulated inputs is associated with at least one master comprising an out of range version number.

10. The method of claim 1, wherein at least one of the simulated inputs is associated with a control line between a PLC and at least one master.

11. The method of claim 1, wherein at least one of the simulated inputs is associated with at least one slave.

12. The method of claim 1, wherein the plurality of simulated inputs comprises inputs associated with a plurality of slaves.

13. The method of claim 1, wherein the plurality of simulated inputs comprises inputs associated with a plurality of possible of slave profiles.

14. The method of claim 1, wherein the plurality of simulated inputs comprises inputs associated with a plurality of possible types of slave.

15. The method of claim 1, wherein at least one of the simulated inputs is associated with an unknown type of slave.

16. The method of claim 1, wherein the plurality of simulated inputs comprises inputs associated with a plurality of possible slave failures.

17. The method of claim 1, wherein the plurality of simulated inputs comprises inputs associated with a movement of slaves among various available addresses on a network.

18. The method of claim 1, wherein at least one of the simulated inputs is associated with a PLC process control program communicable with masters and slaves.

19. The method of claim 1, wherein at least one of the simulated inputs is associated with at least one user input to said configuration program.

20. An acceptance tester adaptable to test a fieldbus component configuration program, said tester comprising:

a simulator adapted to provide a plurality of simulated inputs to a fieldbus component configuration program; and

a comparator adapted to compare an output from the fieldbus component configuration program to a predetermined output.

21. A system comprising:

a configuration program adapted to configure fieldbus components; and

an acceptance tester adapted to evaluate an output of said configuration program relatable to at least one simulated input to said configuration program.

22. A machine-readable medium storing instructions for activities comprising:

providing a plurality of simulated inputs to a fieldbus component configuration program; and

comparing an output from the fieldbus component configuration program to a predetermined output.

23. A system adaptable to test a fieldbus component configuration program, comprising:

means for providing a plurality of simulated inputs to a fieldbus component configuration program; and

means for comparing an output from the fieldbus component configuration program to a predetermined output.