METHOD OF DETERMING REQUEST TRANSMISSION PRIORITY SUBJECT TO REQUEST SOURCE AND TRANSTTING REQUEST SUBJECT TO SUCH REQUEST TRANSMISSION PRIORITY IN APPLICATION OF FIELDBUS COMMUNICATION FRAMEWORK

• US 20080228976A1
• Filed: 03/18/2007
• Published: 09/18/2008
• Est. Priority Date: 03/18/2007
• Status: Active Grant

• Current Assignee: Moxa Inc.
• Original Assignee: MOXA Technologies Co. Ltd. (Moxa Inc.)
• Inventors: Wei, Bo-Er, Chen, You-Shih
• Granted Patent: US 7,913,016 B2
• Time in Patent Office: Days
• US Class Current: 710/110
• CPC Class Codes: H04L 12/4015 by scheduling the transmission of messages at the communication node
• CPC Class Codes: H04L 2012/4026 Bus for use in automation systems

Abstract

A method of determining request transmission priority subject to request source and transmitting request subject to such request transmission priority in application of Fieldbus communication framework in which the communication device determines whether the received requests have the priority subject to the respective source and also determines whether there is any logical operation condition established, and then the communication device transmits the received external requests to the connected slave device as an ordinary request or priority request, preventing the slave device from receiving an important external request sent by the main control end or manager at a late time.

Claims

1. A method of determining request transmission priority subject to request source and transmitting request subject to such request transmission priority in application of Fieldbus communication framework, comprising the steps of:

(a) external requests are transmitted from a remote control end to a communication device one after another;

(b) the communication device determines whether the source of each received request has the priority right;

(c) the communication device determines whether there is at least one logical operation condition established;

(d) the communication device couples the logical operation conditions subject to the user'"'"'s setting and priority condition of the source of each received external request;

(e) the communication device determines whether each received external request has the priority to transmit;

(f) the communication device transmits each external requests that does not have the priority to transmit as an ordinary requests; and

(g) the communication device transmits each external request that has the priority to transmit as a priority request.

2. The method as claimed in claim 1, wherein the priority request transmission procedure is to send the external request into the communication device into the queue having a higher priority.

3. The method as claimed in claim 1, wherein the priority request transmission procedure is to tag the priority request in the priority position on the original queue.

4. The method as claimed in claim 1, wherein said communication device categorizes the priority right into different levels or kinds.

5. The method as claimed in claim 1, wherein the logical operation condition to be coupled subject to the user'"'"'s setting is the numerical value of a counter/timer.

6. The method as claimed in claim 1, wherein the logical operation condition to be coupled subject to the user'"'"'s setting is the number of requests on the queue.

7. The method as claimed in claim 1, wherein said communication device is one of the electronic devices including communication gateway, master device, and repeater or device that are capable of receiving different external requests.

8. The method as claimed in claim 1, wherein the request source is one of an IP address and a Fieldbus serial port.

9. The method as claimed in claim 1, wherein when the external requests that are transmitted from said remote control end to said communication device are not in conformity with Fieldbus communication framework format, the external requests are processed through a format conversion procedure before sending out by said communication device.

10. The method as claimed in claim 1, wherein the Fieldbus communication framework is one of the framework of CAN, EtherCAT, DeviceNet, Modbus, PROFIBUS, CompuBus and SECS protocols for automated control application that has a master/slave architecture and communication mode of Request, Response or Exception.

11. A method of determining request transmission priority subject to request source and transmitting request subject to such request transmission priority in application of Fieldbus communication framework, comprising the steps of:

(a) external requests are transmitted from a remote control end to a communication device one after another;

(b) the communication device determines whether the source of each received external request has the priority right;

(c) the communication device determines whether the received external requests have the priority to transmit;

(d) the communication device transmits every received external request that does not have the priority to transmit as an ordinary request; and

(e) the communication device transmits every received external request that has the priority to transmit as a priority request.

12. The method as claimed in claim 11, wherein the priority request transmission procedure is to send the external request into the communication device into the queue having a higher priority.

13. The method as claimed in claim 11, wherein the priority request transmission procedure is to tag the priority request in the priority position on the original queue.

14. The method as claimed in claim 11, wherein said communication device categorizes the priority right into different levels or kinds.

15. The method as claimed in claim 11, wherein said communication device is one of the electronic devices including communication gateway, master device, and repeater or device that are capable of receiving different external requests.

16. The method as claimed in claim 11, wherein when the external requests that are transmitted from said remote control end to said communication device are not in conformity with Fieldbus communication framework format, the external requests are processed through a format conversion procedure before sending out by said communication device.

17. The method as claimed in claim 11, wherein the source of each received external request is one of an IP address and a Fieldbus serial port.

18. The method as claimed in claim 11, wherein the Fieldbus communication framework is one of the framework of CAN, EtherCAT, DeviceNet, Modbus, PROFIBUS, CompuBus and SECS protocols for automated control application that has a master/slave architecture and communication mode of Request, Response or Exception.