GE FVP110, Руководство по обслуживанию

Страница: 245 / 292

229
FAQs
Link Master Functions
FAQs
Q1. When the LAS stops, a FVP does not back it up by becoming the LAS. Why?
A1-1. Is that FVP running as an LM? Check that the value of
BootOperatFunctionalClass (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:
Q2. How can I make a FVP become the LAS?
A2-1. Check that the version numbers of the active schedules in the current LAS and
the FVP are the same by reading:
LinkScheduleListCharacteristicsRecord (index 374 for a FVP)
- ActiveScheduleVersion (subindex 3)
A2-2. Make the FVP declare itself as and become the LAS by writing:
❑
0x00 (false) to PrimaryLinkMasterFlagVariable in the current LAS; and
❑
0xFF (true) to PrimaryLinkMasterFlagVariable (index 364) in the FVP.
Q3. On a segment where a FVP works as the LAS, another device cannot be
connected. How come?
A3-1. Check the following bus parameters that indicate the bus parameter as being the
LAS for the FVP and the capabilities of being the LAS for the device that cannot be
connected:
❑
V(ST), V(MID), V(MRD) of FVP: ConfiguredLinkSettingsRecord (index 369)
❑
V(ST), V(MID), V(MRD) of problematic device: DlmeBasicInfo
Then, confirm that the following conditions are met:
A3-2. Check the node address of the problematic device is not included in the
V(FUN)+V(NUN) of the FVP.
FVP Other LMs
V(ST) X V(TN) < V(ST) V(TN)
FVP Problematic Device
V(ST) > V(ST)
V(MID) > V(MID)
V(MRD) > V(MRD)