METHOD OF DETERMINING REQUEST TRANSMISSION PRIORITY SUBJECT TO REQUEST CONTENT AND TRANSMITTING REQUEST SUBJECT TO SUCH REQUEST TRANSMISSION PRIORITY IN APPLICATION OF FIELDBUS COMMUNICATION FRAMEWORK

• US 20100205340A1
• Filed: 04/23/2010
• Published: 08/12/2010
• Est. Priority Date: 03/18/2007
• Status: Active Grant

• Current Assignee: Moxa Inc.
• Original Assignee: Moxa Inc.
• Inventors: WEI, Bo-Er, CHEN, You-Shih
• Granted Patent: US 8,065,460 B2
• Time in Patent Office: Days
• US Class Current: 710/110
• CPC Class Codes: H04L 12/413 with random access, e.g. carrier-sense multiple-access with collision detection [CSMA-CD]
• CPC Class Codes: H04L 67/61 taking into account QoS or priority requirements

Abstract

A method of determining request transmission priority subject to request content 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 content, 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 content 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 content 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 content 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;

wherein the logical operation condition includes an on/off switch function can be triggered by user.

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 a 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 an original queue of the communication device.

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 a determination column of said priority right can include the type of request, address of the slave device to receive, address of the register to read/write.

6. The method as claimed in claim 1, wherein said communication device can be a communication gate, a master device or a repeater capable of receiving external requests.

7. The method as claimed in claim 1, wherein if said external request is different from said Fieldbus communication frame, said external request can be converted before transit.

8. 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.

9. A method of determining request transmission priority subject to request content 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 in orderly;

(b) the communication device determines whether the content of each received external request has the priority right, wherein said content of each received external request comprises a specific type of request and an address of a specific register to read/write

(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.

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

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

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

13. The method as claimed in claim 9, wherein said communication device can be a communication gate, a master device or a repeater capable of receiving external requests.

14. The method as claimed in claim 9, 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.

15. The method as claimed in claim 9, 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.