Yokogawa RotaMASS 3-Series - Manual (Page 172)

APPENdIX 7. LINK MASTEr FUNCTIONS
a-72 IM 01R04B05-00E-E 3rd edition July 30, 2010 -00 all Rights Reserved. Copyright © 2005, Rota Yokogawa
(14) dlmeScheduledescriptor
this parameter exists for the same number as
the total number of domains, and each describes
the LaS schedule downloaded to the correspond-
ing domain. For the domain to which a schedule
has not yet been downloaded, the values in this
parameter are all zeros.
Element Description
Sub-
index
Size
[bytes]
2
4
2
Indicates the version number of
the LaS schedule downloaded
to the corresponding domain.
Indicates the macro cycle of the
LaS schedule downloaded to
the corresponding domain.
Indicates the time resolution
that is required to execute the
LaS schedule downloaded to
the corresponding domain.
Version
Macrocycle
Duration
timeResolution
1
2
3
ta0614.EPS
(15) domain
Read/write: impossible; get-oD: possible
Carrying out the GenericDomainDownload com-
mand from a host writes an LaS schedule to the
domain.
A7.6 FAQs
Q1. When the LAS stops, a rOTAMASS does
not back it up by becoming the LAS.
Why?
a1-1. Is that RotaMaSS running as an LM?
Check that the value of BootoperatFunc-
tionalClass (index 367) is 2 (indicating that
it is an LM).
a1-2. Check the values of V(St) and V(tn) in all
LMs on the segment and confirm that the
following condition is met:
RotaMaSS other LMs
V(St)  V(tn) < V(St)  V(tn)
Q2. How can I make a rOTAMASS become
the LAS?
a2-1. Check that the version numbers of the ac-
tive schedules in the current LaS and the
RotaMaSS are the same by reading:
LinkScheduleListChar-
acteristicsRecord
(index 374 for a RotaMaSS)
- activeScheduleVersion (subindex 3)
a2-2. Make the RotaMaSS declare itself as and
become the LaS by writing:
• 0x00 (false) to PrimaryLinkMaster-
FlagVariable in the current LaS; and
• 0xFF (true) to PrimaryLinkMasterFlagVari-
able (index 364) in the RotaMaSS.
Q3. On a segment where a rOTAMASS
works as the LAS, another device cannot
be connected. Why?
a3-1. Check the following bus parameters that in-
dicate the bus parameter as being the LaS
for the RotaMaSS and the capabilities of
being the LaS for the device that cannot be
connected:
• V(St), V(MID), and V(MRD) of
RotaMaSS: ConfiguredLinkSettingsRe-
cord (index 369)
• V(St), V(MID), and V(MRD) of problem-
atic device: DlmeBasicInfo
then, confirm that the following conditions
are met:
RotaMaSS Problematic Device
V(St) > V(St)
V(MID) > V(MID)
V(MRD) > V(MRD)
a3-2. Check that the node address of the prob-
lematic device does not lie within either
0x00 to 0x10 or the range of unused
(unpolled) node addresses determined by
the RotaMaSS LM parameter settings,
which is 0x00 to 0x10 or V(Fun) to V(Fun)
+ V(nuM). (Refer to Section 5.2, “network
Definition.”)
Q4. The LCd keeps showing “— — —”. It is
presumed that an LAS does not exist on
the bus or the rOTAMASS cannot estab-
lish communication with the LAS. What
should be done?
a4-1. Check that an LaS is connected on the
bus. (When using the RotaMaSS as the
LaS [which requires an option], perform
steps (1) to (3) in Section a6-3.)
a4-2. Make the parameters in the current LaS
match the capabilities parameter in the