Technical data

SINAUT PG Routing
4.2 System requirements for PG routing
Software
440 System Manual, 07/2009, C79000-G8976-C222-07
Step 2:
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 b and TIM 3 a 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
$,
$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*
Figure 4-6 Step 2 of central SDB download in the sample configuration
Over the two routing-compliant modules TIM 4 b and TIM 3 a, the PG can now access all
locally connected CPU and TIM modules. All CPU and TIM modules connected to a routing-
compliant TIM over the backplane bus (with S7-300), over MPI, or over WAN are counted as
local.
In the example, the PG can now reach the following CPU and TIM modules:
● In the stations, the CPUs connected to TIM 3 a over the backplane bus.
● In the node station, the CPU and the TIM 4 c over MPI, the station TIM 3 b connected to
TIM 4 b over WAN c, but not the local CPU there.
The reachable CPU modules can now be remotely programmed. The PG can once again
perform all the diagnostics and service functions for the two newly reachable TIM modules
TIM 4 c and TIM 3 b. The PG can therefore also transfer SDBs to these TIM modules.