From: Dietmar Bruckner <Dietmar.Bruckner@br-automation.com>
Sent: Monday, August 29, 2022 7:22 AM
To: Steindl, Guenter (DI FA TIP SAT); Kenneth Lee (Schneider
Electric); René Hummen; Alen Mehmedagic; Satou, Atsushi (A.Satou@yokogawa.com);
Alexander Gogolev; Alexander Ockert; Ziegler, Alexander (DI PA CI TI); AllenTL
Huang (黃子倫); Mrosowski,
Anja; Bastian Otto; Bob Lattimer; Brian Batke; Mangin, Christophe; DAVID CHO;
McCall, David; Paul Didier; Georg Stöger; George Ditzel (Schneider Electric);
glessmann@phoenixcontact.com; Jack CY Lin (林俊余); Woods, Jordon; Josef Dorr; Karl Wachswender;
Lars Ellegaard - M31680; Li Ming; Ludwig Leurs; Lukas Wuesteney; Maik Seewald;
Marius-Petru Stanica; Mittelberger, Martin (DI PA DCP TI); Nithin Babu; Patrick
Loschmidt; Paul Brooks; Peter Lutz; Priyadharshini Prabhakaran; Rafael Selent;
Shahaji B; Stephan Kehrer; Thomas Enzinger; Tom Ko (柯岳明); Vincent
Lacroix
Subject: AW: UAFX
Networking WG - minimum cycle time
Dear all,
Thanks Ken and Günter for the research and recollection.
It looks like we need to further specify on these figures, since we need on the one hand minimal values, on the other hand the minimum to be supported ordinal values.
Proposal:
instead
of:
|
Infrastructure |
UAFX EthernetBridgeQuantities
Scheduled Traffic minCT |
Support
minimum admin cycle time of 200 µs or smaller for scheduled traffic for
ports operating on 100 Mb/s. Support
minimum admin cycle time of 20 µs or smaller for scheduled traffic for
ports operating on 1 Gb/s. |
new:
|
Infrastructure |
UAFX EthernetBridgeQuantities
Scheduled Traffic minCT |
Support minimum admin cycle time of 250 µs or smaller for
scheduled traffic for ports operating on 100 Mb/s. Support minimum admin cycle time of 25 µs or smaller for
scheduled traffic for ports operating on 1 Gb/s. |
|
Infrastructure |
UAFX EthernetBridgeQuantities
Scheduled Traffic supportedCTs |
Support at least admin cycle times of multiples of 250µs and multiples
of 200µs for scheduled traffic for ports operating on 100 Mb/s. Support at least admin cycle times of multiples of 25µs and multiples of 31,25µs for scheduled
traffic for ports operating on 1 Gb/s. |
Regards
Dietmar
Von: Steindl, Guenter <guenter.steindl@siemens.com>
Gesendet: Montag, 29. August 2022 12:46
An: Kenneth Lee <kenneth.lee@se.com>;
René Hummen <Rene.Hummen@belden.com>;
Alen Mehmedagic <alen.mehmedagic@se.com>;
Alex Sato <a.satou@yokogawa.com>;
Alexander Gogolev <alexander.gogolev@huawei.com>;
Alexander Ockert <aockert@hilscher.com>;
Ziegler, Alexander <alexander.ziegler@siemens.com>;
Allen Huang <AllenTL.Huang@moxa.com>;
Anja Mrosowski <Anja.Mrosowski@meg.mee.com>;
Bastian Otto <Botto@hilscher.com>;
Bob Lattimer <bob.lattimer@opcfoundation.org>;
Brian Batke <babatke@ra.rockwell.com>;
Christophe Mangin <c.mangin@fr.merce.mee.com>;
David Cho <cho@idata-inc.jp>; David
McCall <david.mccall@intel.com>;
Didier Paul (padidier@cisco.com) <padidier@cisco.com>; Dietmar Bruckner
<Dietmar.Bruckner@br-automation.com>;
Georg Stöger <georg.stoeger@tttech-industrial.com>;
George Ditzel <george.ditzel@se.com>;
Gunnar Lessmann <glessmann@phoenixcontact.com>;
Jack CY Lin <Jack.Lin@moxa.com>; Woods,
Jordon <jordon.woods@analog.com>;
Dorr, Josef <josef.dorr@siemens.com>;
Karl Wachswender <Karl.Wachswender@latticesemi.com>;
Lars Ellegaard <lars.ellegaard@microchip.com>;
Li Ming <li.ming@huawei.com>;
Ludwig Leurs <Ludwig.Leurs@boschrexroth.de>;
Lukas Wuesteney <Lukas.Wuesteney@belden.com>;
Maik Seewald <maseewal@cisco.com>;
Marius-Petru Stanica <marius-petru.stanica@de.abb.com>;
Mittelberger, Martin <martin.mittelberger@siemens.com>;
Nithin Babu <nithin.babu@in.abb.com>;
Patrick Loschmidt <patrick.loschmidt@tttech-industrial.com>;
Paul Brooks <pbrooks@ra.rockwell.com>;
Peter Lutz <peter.lutz@opcfoundation.org>;
Priyadharshini Prabhakaran <priyadharshini.p@kalycito.com>;
Rafael Selent <rafael.selent@de.abb.com>;
Shahaji B <shahaji.b@in.abb.com>;
Stephan Kehrer <Stephan.Kehrer@belden.com>;
thomas.enzinger@inchstone.com;
Tom Ko <Tom.Ko@moxa.com>; Vincent
Lacroix <lacroix@systerel.fr>
Betreff: AW: UAFX Networking WG - minimum cycle time
|
BeSecure! |
This email comes from outside of ABB. Make sure you verify
the sender before clicking any links or downloading/opening attachments. |
Hello Ken,
thanks for pointing this out.
According to my memory:
Two basic scales were identified – the n*25µs and the n*31,25µs – as needed.
Out of these numerical series some values may be mandatory, some may be optional.
n*31,25µs (historically dividing 1kHz by 2)
- Includes the n*125µs
numerical series
n*25µs (10…100…1000 series)
- Includes the n*125µs
numerical series
125µs will be se common denominator…
Thus, 20µs and 200µs doesn’t fit into the above mentioned numerical series!
Regards
Günter
Von: Kenneth Lee <kenneth.lee@se.com>
Gesendet: Freitag, 26. August 2022 22:33
An: René Hummen <Rene.Hummen@belden.com>; Alen Mehmedagic <alen.mehmedagic@se.com>; Alex Sato <a.satou@yokogawa.com>; Alexander Gogolev <alexander.gogolev@huawei.com>; Alexander Ockert <aockert@hilscher.com>; Ziegler, Alexander (DI PA DCP TI)
<alexander.ziegler@siemens.com>; Allen Huang <AllenTL.Huang@moxa.com>; Anja Mrosowski <Anja.Mrosowski@meg.mee.com>; Bastian Otto <BOtto@hilscher.com>; Bob Lattimer <bob.lattimer@opcfoundation.org>; Brian Batke <babatke@ra.rockwell.com>; Christophe Mangin <c.mangin@fr.merce.mee.com>; David Cho <cho@idata-inc.jp>; David McCall <david.mccall@intel.com>; Didier Paul (padidier@cisco.com) <padidier@cisco.com>; Dietmar Bruckner <dietmar.bruckner@br-automation.com>;
Georg Stöger <georg.stoeger@tttech-industrial.com>;
George Ditzel <george.ditzel@se.com>; Gunnar Lessmann <glessmann@phoenixcontact.com>; Steindl, Günter (DI
FA TI ART EA) <guenter.steindl@siemens.com>; Jack CY Lin <Jack.Lin@moxa.com>;
Jordon Woods <jordon.woods@analog.com>; Dorr, Josef (DI PA DCP
TI) <josef.dorr@siemens.com>; Karl Wachswender <Karl.Wachswender@latticesemi.com>;
Lars Ellegaard <lars.ellegaard@microchip.com>; Li Ming <li.ming@huawei.com>;
Ludwig Leurs <Ludwig.Leurs@boschrexroth.de>; Lukas Wuesteney <Lukas.Wuesteney@belden.com>; Maik Seewald <maseewal@cisco.com>;
Marius-Petru Stanica <marius-petru.stanica@de.abb.com>;
Mittelberger, Martin (DI PA DCP TI) <martin.mittelberger@siemens.com>;
Nithin Babu <nithin.babu@in.abb.com>; Patrick Loschmidt <patrick.loschmidt@tttech-industrial.com>;
Paul Brooks <pbrooks@ra.rockwell.com>; Peter Lutz <peter.lutz@opcfoundation.org>; Priyadharshini
Prabhakaran <priyadharshini.p@kalycito.com>; Rafael Selent <rafael.selent@de.abb.com>; Shahaji B <shahaji.b@in.abb.com>;
Stephan Kehrer <Stephan.Kehrer@belden.com>; Thomas Enzinger <thomas.enzinger@inchstone.com>; Tom Ko <Tom.Ko@moxa.com>;
Vincent Lacroix <lacroix@systerel.fr>
Betreff: UAFX Networking WG - minimum cycle time
Hello all,
Regarding OPC Part 84 Table 9 – UAFX Ethernet networking quantities, UAFX EthernetBridgeQuantities Scheduled Traffic minCT
In Mantis, we have:
|
MR 5177: The network may have a cycle time of 31.25us (0005177: The network may have a cycle time of 31.25us - MantisBT (opcfoundation.org)) From MVS ppt: Cycle times of down to 32kHz shall be possible And constrained by network capability not specification |
|
MR 4922: Communication cycle times down to 31,25 usec Communication cycle times down to 31,25 usec |
There is another requirement that seems related (not specifically on network cycle but likely related):
|
MR 5943: Cycle time groups: 2ms and below (0005943: Cycle time groups: 2ms and below - MantisBT (opcfoundation.org)) At 2ms and below, the communication rates shall belong to the binary group or the non-binary group or may belong to both groups: Binary cycle timing group: 2ms, 1ms, 500µs, 250µs, 125µs, 62.5µs, 31.25µs, and lower Non-binary cycle timing group: 2ms, 1.6ms, 1.2ms, 800µs, 400µs, 200µs, 100µs, 50µs, 25µs, and lower It is acceptable that an FLC automation component operates using only one cycle timing group, (either binary or non-binary). |
In addition, there are MR 6437, 6436, 6435, 6434 that mention specific network cycles of 50, 100, 500, and 100 µs, respectively.
|
MR 6437: FLC motion shall support operation of 6 motion functional entities with a 50 µsec network cycle period. FLC motion shall support operation of 6 motion functional entities with a 50 µsec network cycle period. |
The smallest number specifically mentioned seems to be 25 µs.
|
Best regards, Ken Kenneth Lee |
D 978-975-9032 |
800
Federal Street |
|
|
|
*Please consider the
environment before printing this e-mail |
|
