User Manual

SGD-SB2025NT-TUM, Part 2
Jan 12 Page 82 TROUBLESHOOTING & MAINT
11.1.3.1 Delay from NI to each TM
The Solar network settings are held in the Primary TM and passed, in their entirety, to the
Secondary TM, i.e. there is no provision to “customise” the Secondary TM in any way. Depending
upon the network “distance” between the two TMs, it is quite reasonable to expect that some NIs
will be ‘closer’ to the Primary than the Secondary and vice-versa.
If buffer settings are used that are simply taken from the results obtained from the Primary TM,
albeit that this is the best way to get the system operating at the initial commissioning stage, when
TM changeover occurs, it may be found that system performance degrades. Therefore, it would be
very easy to conclude that there is some sort of malfunction with the Secondary TM when in fact
the real reason is more subtle.
Therefore, when it comes to optimising the Solar buffer times on a duplicated configuration, the
packet delivery times must be examined when each TM is operating and the “worst case” values
used. If a duplicated configuration is used together with network re-routing, the permutations of
configurations will probably become considerable. However, unless the network architecture is
very complex, it should prove relatively easy to identify what is likely to be the worst case situation
and study that in detail in order to arrive at the optimum buffer settings.
11.1.3.2 Network Fault causing TM Changeover
Similar to the situation with a network re-route, a network failure could result in loss of
communications between the Primary and Secondary TM while both units are working normally.
This will result in the Secondary TM sending data packets to every NI while the Primary TM is still
active. Since we are assuming a fault condition that is preventing inter-TM traffic flow, it would not
be possible for any single NI to “see” both the Primary TM and the Secondary TM at the same
time, i.e. the NI would only receive packets from one TM. This would cause a “split” of the NIs
between the two TM.
The network design and the location of the fault determine which NI would be associated to which
TM. This could range from the Central NI for the channel being on one TM and all the Station NIs
being on the other TM to just one Station NI being “lost” to the Secondary. In the first scenario, the
setting ‘TM triggered Talk Thru’ ‘On Central NI Fail’ (see Section 5.4.2.4 ) would be recommended
so that the channel could still provide a fallback service when running on the Secondary TM. This
setting would of course have to be applied at the Primary TM even though the facility may not
seem appropriate when operating in that mode.
The results of network problems when using a duplicated TM configuration may be very varied but
should be entirely predictable if each fault scenario is carefully considered, even though there may
be little or nothing that can be done about the resultant effects.
11.2 F IRMWARE U P -I SSUES
11.2.1 Availability
The latest Firmware version is posted on the Team Simoco web site; users who are on a list of
interested parties will be notified when a new version becomes available.
11.2.2 Loader – General
To up-issue the TM Firmware and NI PIC Firmware requires the use of the ET or ‘Loader’ software
applications. The Loader software is available from the Team Simoco website and, like the ET, is
an executable file, which uses the front panel USB port – it is possible to change firmware remotely
with the ET, however, the Loader application needs a direct USB connection.