IP Library Granted Patent US 12,229,058
Granted Patent B2
US 12,229,058 · App. 18/091,596 · Granted Feb 18, 2025

Large packet daisy chain serial bus

Inventors: Morgan O. LaMoore (Minneapolis, MN); Pavel V. Tysyachuk (Bloomington, MN); Adriana F. Mickols (Fridley, MN); Nicholas T. Fritz (Minneapolis, MN)
Assignee: Graco Minnesota Inc.
G06F13/102G06F1/266G06F13/1668G06F13/4247G05B2219/1215
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,229,058
App. No.
18/091,596
Granted
Feb 18, 2025
Kind
B2
Abstract

A communication system for an industrial process includes multiple slave modules connected in series with a master controller. The master controller stores a communication schedule that defines an ordered sequence of messages and identifiers associated with each message. The master controller transmits messages downstream through the slave modules to a terminal one of the slave modules. The terminal slave module generates a return message that is transmitted upstream to the master controller. Each slave module receives each downstream message, identifies based on the message identifier whether the message is associated with response information from the slave module, and inserts the response information into corresponding upstream messages.

Claims (102)

1. A method for communicating in a communication system that includes a master controller and a plurality of slave modules connected in series with the master controller, the method comprising:

transmitting, by the master controller to each of the plurality of slave modules, a communication schedule defining an ordered sequence of messages;

transmitting, according to the communication schedule, downstream messages in a downstream direction from the master controller through an initial slave module to a terminal slave module, each of the downstream messages including header payload information with a schedule identifier that indicates an order number of the respective downstream message defined by the communication schedule;

identifying, by each of the plurality of slave modules based on the schedule identifiers included in the downstream messages, downstream messages that are associated with response information from the respective slave module;

generating, by the terminal slave module, upstream messages having schedule identifiers that correspond to the schedule identifiers included in the downstream messages;

transmitting the upstream messages from the terminal slave module in an upstream direction through the initial slave module to the master controller;

inserting, by the plurality of slave modules, the response information into upstream messages having schedule identifiers corresponding to the downstream messages identified as associated with response information from the respective slave module; and

receiving the upstream messages at the master controller.

2. The method of claim 1 ,

wherein transmitting the downstream messages in the downstream direction from the master controller through the initial slave module to the terminal slave module comprises transmitting the downstream messages from the master controller through the initial slave module and one or more intermediate slave modules connected between the initial slave module and the terminal slave module to the terminal slave module; and

wherein transmitting the upstream messages from the terminal slave module in the upstream direction through the initial slave module to the master controller comprises transmitting the upstream messages from the terminal slave module in the upstream direction through the one or more intermediate slave modules and the initial slave module to the master controller.

3. The method of claim 1 ,

wherein receiving and transmitting the downstream messages by each of the plurality of slave modules comprises receiving and transmitting the downstream messages using a first transceiver of a respective one of the plurality of slave modules; and

wherein receiving and transmitting the upstream messages by the plurality of slave modules comprises receiving and transmitting the upstream messages using a second transceiver of a respective one of the plurality of slave modules.

4. The method of claim 1 ,

wherein each of the plurality of slave modules stores the communication schedule in computer-readable memory; and

wherein identifying, by each of the plurality of slave modules, the downstream messages that are associated with response information from the respective slave module comprises identifying, by each of the plurality of slave modules, the downstream messages that are associated with response information from the respective slave module based on a comparison of the schedule identifiers with the communication schedule stored in the computer-readable memory of the respective slave module.

5. The method of claim 4 , wherein the communication schedule further defines, for each of the plurality of slave modules:

a local memory address for each of the downstream messages associated with the respective slave module;

a size of each of the downstream messages associated with the respective slave module;

a memory offset value within the downstream messages associated with the respective slave module at which information corresponding to the respective slave module is located within the downstream messages; and

a memory offset value within upstream messages at which the respective slave module is to insert response information into the upstream messages.

6. The method of claim 1 , further comprising:

determining the communication schedule by the master controller.

7. The method of claim 1 , further comprising:

identifying, by the master controller during an initialization phase of the communication system, a relative order of the plurality of slave modules in the series connection and identity of each of the plurality of slave modules.

8. The method of claim 7 ,

wherein each of the plurality of slave modules is pre-provisioned to store, within computer-readable memory of the respective slave module, a location identifier having a value defined as corresponding to an uninitialized slave module; and

wherein the identifying the relative order of the plurality of slave modules in the series connection and identity of each of the plurality of slave modules comprises iteratively:

transmitting, in a downstream direction, an identification class message that includes:

a location identifier having the value defined as corresponding to the uninitialized slave module; and

a commanded location identifier; and

identifying, as next in the relative order the plurality of slave modules in the series connection, a respective one of the plurality of slave modules corresponding to identity information received in an upstream identification class message.

9. The method of claim 1 ,

wherein the downstream messages further include message payload information corresponding to one or more of the plurality of slave modules.

10. A communications system for an industrial process, the communications system comprising:

a master controller; and

a plurality of slave modules connected in series with the master controller, the plurality of slave modules comprising:

an initial slave module; and

a terminal slave module;

wherein the master controller is configured to:

transmit, to each of the plurality of slave modules, a communication schedule that defines an ordered sequence of messages;

transmit downstream messages in a downstream direction through the initial slave module to the terminal slave module according to the communication schedule, each of the downstream messages including header payload information with a schedule identifier that indicates an order number of the respective downstream message defined by the communication schedule; and

receive return messages originating from the terminal slave module and transmitted by the terminal slave module in an upstream direction through the initial slave module to the master controller;

wherein the initial slave module is configured to:

identify, based on the schedule identifiers included in the header payload information of the downstream messages, downstream messages that are associated with response information from the initial slave module; and

insert the response information into upstream messages having schedule identifiers corresponding to the schedule identifiers in the downstream messages identified as associated with the response information from the initial slave module; and

wherein the terminal slave module is configured to:

generate the upstream messages having the schedule identifiers that correspond to the schedule identifiers included in the downstream messages; and

transmit the upstream messages in the upstream direction.

11. A communications system for an industrial process, the communications system comprising:

a master controller; and

a plurality of slave modules connected in series with the master controller, the plurality of slave modules comprising:

an initial slave module;

a terminal slave module; and

one or more intermediate slave modules connected between the initial slave module and the terminal slave module;

wherein the master controller is configured to:

transmit, to each of the plurality of slave modules, a communication schedule that defines an ordered sequence of messages;

transmit downstream messages in a downstream direction through the initial slave module and the one or more intermediate slave modules to the terminal slave module according to the communication schedule, each of the downstream messages including header payload information with a schedule identifier that indicates an order number of the respective downstream message defined by the communication schedule; and

receive return messages originating from the terminal slave module and transmitted by the terminal slave module in an upstream direction through the one or more intermediate slave modules and the initial slave module to the master controller;

wherein the initial slave module is configured to:

identify, based on the schedule identifiers included in the header payload information of the downstream messages, downstream messages that are associated with response information from the initial slave module; and

insert the response information into upstream messages having schedule identifiers corresponding to the schedule identifiers in the downstream messages identified as associated with the response information from the initial slave module;

wherein the terminal slave module is configured to:

generate the upstream messages having the schedule identifiers that correspond to the schedule identifiers included in the downstream messages; and

transmit the upstream messages in the upstream direction; and

wherein the one or more intermediate slave modules are configured to:

receive the downstream messages;

identify, based on the schedule identifiers included in the downstream messages, downstream messages that are associated with response information from the respective slave module; and

insert the response information into the upstream messages having schedule identifiers corresponding to the schedule identifiers that are associated with the response information from the respective slave module.

12. The communications system of claim 10 ,

wherein each of the plurality of slave modules comprises:

a first transceiver configured to receive and transmit the downstream messages; and

a second transceiver configured to receive and transmit the upstream messages.

13. The communications system of claim 10 ,

wherein the terminal slave module is further configured to:

identify, based on the schedule identifiers included in the header payload information of the downstream messages, whether the downstream messages are associated with response information from the terminal slave module; and

insert the response information into the upstream messages having the schedule identifiers that correspond to the downstream messages identified as being associated with response information from the terminal slave module.

14. The communications system of claim 10 ,

wherein each of the plurality of slave modules stores the communication schedule; and

wherein each of the plurality of slave modules is configured to identify whether the downstream messages are associated with response information from the respective slave module based on a comparison of the schedule identifiers with the communication schedule stored at the respective slave module.

15. The communications system of claim 14 ,

wherein the communication schedule further defines, for each of the plurality of slave modules:

a local memory address for each of the downstream messages associated with the respective slave module;

a size of each of the downstream messages associated with the respective slave module;

a memory offset value within the downstream messages associated with the respective slave module at which information corresponding to the respective slave module is located within the downstream messages; and

a memory offset value within upstream messages at which the respective slave module is to insert response information into the upstream messages.

16. The communications system of claim 10 ,

wherein the master controller is configured to determine the communication schedule.

17. The communications system of claim 10 ,

wherein the downstream messages further include message payload information corresponding to one or more of the plurality of slave modules.

18. The communications system of claim 10 ,

wherein the master controller is configured to identify a relative order of the plurality of slave modules in the series connection and identity of each of the slave modules during an initialization phase of the communications system.

19. The communications system of claim 17 ,

wherein each of the plurality of slave modules is pre-provisioned to store, within computer-readable memory of the respective slave module, a location identifier having a value defined as corresponding to an uninitialized slave module; and

wherein the master controller is configured to identify the relative order and the identity of each of the slave modules by iteratively:

transmitting, in a downstream direction, an identification class message that includes:

a location identifier having the value defined as corresponding to the uninitialized slave module; and

a commanded location identifier; and

identifying, as next in the relative order of the plurality of slave modules in the series connection, a respective one of the plurality of slave modules corresponding to identity information received in an upstream identification class message.

20. The communications system of claim 10 ,

wherein the terminal slave module is configured to insert the schedule identifiers that correspond to the schedule identifiers included in the downstream messages within header payload information included in the upstream messages.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 30, 2022
From: LAMOORE, MORGAN O.; TYSYACHUK, PAVEL V.; MICKOLS, ADRIANA F.; FRITZ, NICHOLAS T.
To: GRACO MINNESOTA INC.
Reel/Frame 062243/0990 →
Continuity (5)
Continuation 17721479 · Apr 15, 2022
Continuation 16715750 · Dec 16, 2019
Provisional Application 62851248 · May 22, 2019
Provisional Application 62780561 · Dec 17, 2018
Related Publication 20230139123A1 · May 4, 2023
References Cited (61)
US 5090012A · Kajiyama et al. · 1992 [cited by applicant]
US 6032208A · Nixon et al. · 2000 [cited by applicant]
US 6098116A · Nixon et al. · 2000 [cited by applicant]
US 6665742B2 · Owen et al. · 2003 [cited by applicant]
US 7433302B2 · Allen · 2008 [cited by applicant]
US RE40817E · Krivoshein et al. · 2009 [cited by applicant]
US 8428054B2 · Miller · 2013 [cited by applicant]
US 8625625B2 · Anderson et al. · 2014 [cited by applicant]
US 8650304B2 · Anderson et al. · 2014 [cited by applicant]
US 8651878B2 · Björklund · 2014 [cited by applicant]
US 8670457B2 · Anderson et al. · 2014 [cited by applicant]
US 8937966B2 · Kretschmann et al. · 2015 [cited by applicant]
US 9081742B2 · Sonnier et al. · 2015 [cited by applicant]
US 9535415B2 · Keller et al. · 2017 [cited by applicant]
US 9645572B2 · Telljohann et al. · 2017 [cited by applicant]
US 9723767B2 · Kojima et al. · 2017 [cited by applicant]
US 9768572B1 · Gelineau et al. · 2017 [cited by applicant]
US 9960997B2 · Balasubramanian et al. · 2018 [cited by applicant]
US 10139812B2 · Jones et al. · 2018 [cited by applicant]
US 10198871B1 · Hariton · 2019 [cited by applicant]
US 10484198B2 · Krumsiek · 2019 [cited by applicant]
US 10572162B2 · Rantanen et al. · 2020 [cited by applicant]
US 10678225B2 · Kidd et al. · 2020 [cited by applicant]
US 11546187B2 · Lamoore et al. · 2023 [cited by applicant]
US 11704257B1 · Tysyachuk · 2023 [cited by examiner]
US 20040088434A1 · Takabatake · 2004 [cited by applicant]
US 20060190112A1 · Buesgen et al. · 2006 [cited by applicant]
US 20080052417A1 · Aoyama et al. · 2008 [cited by applicant]
US 20100023657A1 · Fukuda et al. · 2010 [cited by applicant]
US 20120179849A1 · Mizutani · 2012 [cited by applicant]
US 20130301495A1 · Miller · 2013 [cited by applicant]
US 20140254431A1 · Yan et al. · 2014 [cited by applicant]
US 20140277597A1 · Le Sant et al. · 2014 [cited by applicant]
US 20160091903A1 · Patton et al. · 2016 [cited by applicant]
US 20160205066A1 · Attarwala et al. · 2016 [cited by applicant]
US 20170070564A1 · Sinistro et al. · 2017 [cited by applicant]
US 20170222829A1 · Kessler et al. · 2017 [cited by applicant]
US 20180004953A1 · Smith et al. · 2018 [cited by applicant]
US 20190018785A1 · Beard et al. · 2019 [cited by applicant]
US 20190278698A1 · Ahner et al. · 2019 [cited by applicant]
US 20200076713A1 · Meyer et al. · 2020 [cited by applicant]
US 20200192315A1 · Lamoore et al. · 2020 [cited by applicant]
US 20200218240A1 · Hkansson et al. · 2020 [cited by applicant]
US 20210089276A1 · Dunn et al. · 2021 [cited by applicant]
US 20210103690A1 · Stump et al. · 2021 [cited by applicant]
US 20210318889A1 · Waterman · 2021 [cited by applicant]
CN 101067804A · 2007 [cited by applicant]
CN 104285190A · 2015 [cited by applicant]
EP 1658535B1 · 2012 [cited by applicant]
EP 3166258A1 · 2017 [cited by applicant]
JP S63275237A · 1988 [cited by applicant]
JP H11136243A · 1999 [cited by applicant]
JP 2015149541A · 2015 [cited by applicant]
JP 2017192301A · 2017 [cited by applicant]
WO 2019054929A1 · 2019 [cited by applicant]
Extended European Search Report for European Patent Application No. 23167666.9, date Aug. 4, 2023, 8 pages. [cited by applicant]
Japanese Office Action for Japanese Patent Application No. 2021-534369, dated Jan. 17, 2024, four pages (including translation). [cited by applicant]
“Battery control circuit using non-isolation daisy-chain architecture for a 400V Li-ion battery system of a hybrid electric vehicle,” Akihiko Emori, et al., IEEE Vehicle Power and Propulsion Conference (VPPC), Sep. 3-5,… [cited by applicant]
“Design of Reatime System for a Fieldbus-based Embedded Motion Controller,” Lim Liming, et al., China Mechanical Engineering, Feb. 25, 2013. [cited by applicant]
First Chinese Office Action for CN Application No. 201980089450.3, dated Jun. 30, 2022, 28 pages. [cited by applicant]
International Search Report and Written Opinion for International Patent Application PCT/US2019/066574, dated Feb. 13, 2020, 13 pages. [cited by applicant]