US 12,229,058 B2
Large packet daisy chain serial bus
Morgan O. LaMoore, Minneapolis, MN (US); Pavel V. Tysyachuk, Bloomington, MN (US); Adriana F. Mickols, Fridley, MN (US); and Nicholas T. Fritz, Minneapolis, MN (US)
Assigned to Graco Minnesota Inc., Minneapolis, MN (US)
Filed by Graco Minnesota Inc., Minneapolis, MN (US)
Filed on Dec. 30, 2022, as Appl. No. 18/091,596.
Application 18/091,596 is a continuation of application No. 17/721,479, filed on Apr. 15, 2022, granted, now 11,704,257.
Application 18/091,596 is a continuation of application No. 16/715,750, filed on Dec. 16, 2019, granted, now 11,546,187.
Claims priority of provisional application 62/851,248, filed on May 22, 2019.
Claims priority of provisional application 62/780,561, filed on Dec. 17, 2018.
Prior Publication US 2023/0139123 A1, May 4, 2023
This patent is subject to a terminal disclaimer.
Int. Cl. G06F 13/10 (2006.01); G06F 1/26 (2006.01); G06F 13/16 (2006.01); G06F 13/42 (2006.01)
CPC G06F 13/102 (2013.01) [G06F 1/266 (2013.01); G06F 13/1668 (2013.01); G06F 13/4247 (2013.01); G05B 2219/1215 (2013.01)] 20 Claims
OG exemplary drawing
 
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.