Imbedded interrupt

• US 20030065855A1
• Filed: 08/12/2002
• Published: 04/03/2003
• Est. Priority Date: 07/12/2001
• Status: Abandoned Application

• Current Assignee: Schneider Automation Incorporated (Schneider Electric SE)
• Original Assignee: Schneider Automation Incorporated (Schneider Electric SE)
• Inventors: Webster, Steve R.
• Application Number:
  US10/217,155
• Publication Number:
  US 20030065855A1
• Time in Patent Office: Days
• US Class Current: 710/260
• CPC Class Codes: G05B 19/0423 Input/output
• CPC Class Codes: G05B 19/054 Input/output

Abstract

A system and method for triggering interrupt service routines is disclosed. The system can be implemented in a computer readable medium that includes logic for receiving first and second signals. The first signal triggers a first interrupt that triggers a first interrupt service routine that is designed to process a first task. The second signal trigger is designed to cause the processing of a second task. The medium also includes logic for determining if the second task is a high priority task, and logic for creating a second interrupt if the second task is a high priority task. The medium further includes logic for completing the first interrupt service routine before processing a second interrupt service routine. The second interrupt service routine is triggered by the second interrupt. The second interrupt service routine is designed to complete the high priority task. And, the medium includes logic for returning to a main loop after completing the second interrupt service routine.

Claims

1. A computer readable medium for processing interrupts, the medium comprising:

logic for receiving a first interrupt signal, the first interrupt signal triggering a first interrupt, the first interrupt signal being in a protocol format, the first interrupt triggering a first interrupt service routine, the first interrupt service routine designed to process a first task;

logic for receiving a second interrupt signal, the second interrupt signal designed to cause the processing of a second task;

logic for determining if the second task is a high priority task;

logic for creating a second interrupt if the second task is a high priority task;

logic for completing the first interrupt service routine before processing a second interrupt service routine, the second interrupt service routine being triggered by the second interrupt, the second interrupt service routine being designed to complete the high priority task; and

logic for returning to a main loop after completing the second interrupt service routine.

2. The computer readable medium of claim 1, where the protocol of the first interrupt signal is Controller Area Network (CAN) protocol.

3. The computer readable medium of claim 1, where the protocol is one of a group of protocols, where the group consists of Controller Area Network (CAN), Profibus, Interbus, Devicenet and Ethernet.

4. The computer readable medium of claim 1, where the first interrupt signal is a CANOpen interrupt signal.

5. The computer readable medium of claim 1, where the first task is a CANOpen message.

6. The computer readable medium of claim 1, where the high priority task is a reflex operation.

7. The computer readable medium of claim 1, where the second interrupt service routine is a reflex interrupt service routine.

8. The computer readable medium of claim 1, where the second interrupt is a reflex interrupt.

9. The computer readable medium of claim 1, where the second interrupt occurs immediately after the completion of the first interrupt service routine.

10. The computer readable medium of claim 1, where the second interrupt service routine is completed prior to returning to the main loop.

11. The computer readable medium of claim 1, where the first interrupt signal is representative of a first condition of a device, and the second task includes the generation of a first state signal.

12. The computer readable medium of claim 1, where the computer readable medium resides in an input module.

13. The computer readable medium of claim 1, where the computer readable medium resides in an output module.

14. The computer readable medium of claim 1, where the computer readable medium resides in a controller.

15. The computer readable medium of claim 1, where the computer readable medium resides in a control system, and the control system does not include a controller.

16. The computer readable medium of claim 1, where the first interrupt is triggered by receipt of the first interrupt signal at an interrupt pin.

17. The computer readable medium of claim 1, where the first interrupt includes the following instructions:

18. The computer readable medium of claim 1, where the medium determines whether the second task is a high priority task based on whether the second task should be completed prior to returning to the main loop.

19. The computer readable medium of claim 1, where the first and second interrupt signals are received at the same pin.

20. The computer readable medium of claim 1, where the second request for service is enabled with the instruction,

PBOR=0x10;

// enable interrupt on port B pin 4

22. The method of claim 1, where the protocol of the first interrupt signal is Controller Area Network (CAN) protocol.

23. The method of claim 1, where the protocol is one of a group of protocols, where the group consists of Controller Area Network (CAN), Profibus, Interbus, Devicenet and Ethernet.

24. The method of claim 1, where the first interrupt signal is a CANOpen interrupt signal.

25. The method of claim 1, where the first task is a CANOpen message.

26. The method of claim 1, where the high priority task is a reflex operation.

27. The method of claim 1, where the second interrupt service routine is a reflex interrupt service routine.

28. The method of claim 1, where the second interrupt is a reflex interrupt.

29. The method of claim 1, where the second interrupt occurs immediately after the completion of the first interrupt service routine.

30. The method of claim 1, where the second interrupt service routine is completed prior to returning to the main loop.

31. The method of claim 1, where the first interrupt signal is representative of a first condition of a device, and the second task includes the generation of a first state signal.

32. The method of claim 1, where the method is practiced using an input module.

33. The method of claim 1, where the method is practiced using an output module.

34. The method of claim 1, where the method is practiced using a controller.

35. The method of claim 1, where the method is practiced in a control system, and the control system does not include a controller.

36. The method of claim 1, where the first interrupt is triggered by receipt of the first interrupt signal at an interrupt pin.

37. The method of claim 1, where the first interrupt includes the following instructions:

38. The method of claim 1, where the step of determining if the second task is a high priority task is based on whether the second task should be completed prior to returning to the main loop.

39. The method of claim 1, where the first and second interrupt signals are received at the same pin.

40. The method of claim 1, where the second request for service is enabled with the instruction,

PBOR=0x10;

// enable interrupt on port B pin 4

42. The system of claim 1, where the protocol of the first interrupt signal is Controller Area Network (CAN) protocol.

43. The system of claim 1, where the protocol is one of a group of protocols, where the group consists of Controller Area Network (CAN), Profibus, Interbus, Devicenet and Ethernet.

44. The system of claim 1, where the first interrupt signal is a CANOpen interrupt signal.

45. The system of claim 1, where the first task is a CANOpen message.

46. The system of claim 1, where the high priority task is a reflex operation.

47. The system of claim 1, where the second interrupt service routine is a reflex interrupt service routine.

48. The system of claim 1, where the second interrupt is a reflex interrupt.

49. The system of claim 1, where the second interrupt occurs immediately after the completion of the first interrupt service routine.

50. The system of claim 1, where the second interrupt service routine is completed prior to returning to the main loop.

51. The system of claim 1, where the first interrupt signal is representative of a first condition of a device, and the second task includes the generation of a first state signal.

52. The system of claim 1, where the system resides in an input module.

53. The system of claim 1, where the system resides in an output module.

54. The system of claim 1, where the system resides in a controller.

55. The system of claim 1, where the system resides in a control system, and the control system does not include a controller.

56. The system of claim 1, where the first interrupt is triggered by receipt of the first interrupt signal at an interrupt pin.

57. The system of claim 1, where the first interrupt includes the following instructions:

58. The system of claim 1, where the means for determining if the second task is a high priority task is based on whether the second task should be completed prior to returning to the main loop.

59. The system of claim 1, where the first and second interrupt signals are received at the same pin.

60. The system of claim 1, where the second request for service is enabled with the instruction,

PBOR=0x10;

// enable interrupt on port B pin 4

21. A method for processing interrupts, the method comprising the steps of:

receiving a first interrupt signal, the first interrupt signal triggering a first interrupt, the first interrupt signal being in a protocol format, the first interrupt triggering a first interrupt service routine, the first interrupt service routine designed to process a first task;

receiving a second interrupt signal, the second interrupt signal designed to cause the processing of a second task;

determining if the second task is a high priority task;

creating a second interrupt if the second task is a high priority task;

completing the first interrupt service routine before processing a second interrupt service routine, the second interrupt service routine being triggered by the second interrupt, the second interrupt service routine being designed to complete the high priority task; and

returning to a main loop after completing the second interrupt service routine.

41. A system for processing interrupts, the system comprising:

means for receiving a first interrupt signal, the first interrupt signal triggering a first interrupt, the first interrupt signal being in a protocol format, the first interrupt triggering a first interrupt service routine, the first interrupt service routine designed to process a first task;

means for receiving a second interrupt signal, the second interrupt signal designed to cause the processing of a second task;

means for determining if the second task is a high priority task;

means for creating a second interrupt if the second task is a high priority task;

means for completing the first interrupt service routine before processing a second interrupt service routine, the second interrupt service routine being triggered by the second interrupt, the second interrupt service routine being designed to complete the high priority task; and

means for returning to a main loop after completing the second interrupt service routine.