Technical data

SINAUT PG Routing
4.2 System requirements for PG routing
Software
System Manual, 07/2009, C79000-G8976-C222-07
441
Step 3:
Download the newly compiled SDBs to the TIM modules TIM 4 b and TIM 3 a and then
activate the SDBs by running a restart on the two TIM modules. TIM 4 c and TIM 3 b are
now routing-compliant.

1RGH
VWDWLRQ
0DVWHUVWDWLRQ
6WDWLRQ
6'%
6'%
6'%
03,
03,
03,
:$1
:$1
:$1D :$1E
:$1F :$1G :$1H
:$1
7,0D
03, 03,
',
'2
$,
$,
',
'2
$,
$2
&38

&38

&38

&38

03,
:$1 :$1 :$1 :$1
7,0E
7,0
D
:$1
',
'2
$,
$2
7,0
E
:$1
',
'2
$,
$2
7,0
F
7,0F
3*
6'%
6'%
Figure 4-7 Step 3 of central SDB download in the sample configuration
Over the two routing-compliant modules TIM 4 c and TIM 3 b, the PG can now access all
locally connected CPU and TIM modules. In the example, the PG can now reach the
following CPU and TIM modules:
● In the stations, the CPUs connected to TIM 3 b over the backplane bus.
● The station TIM 3 c, connected over WAN d to the TIM 4 c in the node station, but the
CPU connected locally to TIM 3 c in the station not yet.
The reachable CPU module can now be remotely programmed.
The PG can once again perform all the diagnostics and service functions for the newly
reachable TIM module. The PG can therefore also transfer SDBs to this TIM module.