Wn - Error correction messages control. Schneider Electric PL7 Micro/Junior/Pro - Communication applications, volume 2
Реклама
Реклама
Appendices
Wn - Error correction messages control
Introduction
Parameters
This command controls the format of CONNECT messages. The parameter value, if valid, is written in bits 2 and 3 of S31 (also see description of S95).
The parameters are:
Code
W0
W1
W2
Description
On connection, the modem only indicates the baud rate of the DTE (e.g.
CONNECT 9600). Subsequent responses are deactivated (default value).
On connection, the modem indicates the line baud rate, the error correction protocol and the baud rate of the DTE respectively. Subsequent responses are deactivated.
On connection, the modem indicates the baud rate of the DCE (e.g. CONNECT
2400). Subsequent responses are deactivated.
Result codes The following table lists the possible command responses.
Code
OK
ERROR
Description n = 0 to 2.
If n is not in the range 0 to 2.
152
TLX DS COM PL7 xxE
Appendices
Xn - Extended result codes
Introduction This command selects the set of messages that the modem will use to inform the
DTE of the command results. The table indicates the messages which are activated for each value of X.
If the modem is in fax mode (+FCLASS=1 or 2), the only message sent to indicate that a connection has been made is CONNECT without any indication of baud rate.
Parameters
Code
X0
X1
X2
X3
X4
The parameters are:
Description
Deactivates detection of engaged tones except if this is imposed by the national requirements; only sends the result codes OK , CONNECT , RING , NO CARRIER , ERROR and NO ANSWER .The blind dialing mode is activated/deactivated by the national parameters. If detection of the engaged tone is in use and if such a tone is detected, it is the response NO CARRIER which is sent back instead of BUSY .If dial tone detection is in use or selected and if no such tone is detected, it is the response NO CARRIER which is sent back instead of NO DIAL TONE .The binary value 000 is written in bits 6, 5 and 4 of S22 respectively.
Deactivates detection of engaged tones except if this is imposed by the national requirments; only sends the result codes OK , CONNECT , RING , NO CARRIER , ERROR , NO ANSWER and CONNECT XXXX
(XXXX = baud rate). Blind dialing mode is activated/deactivated by the national parameters. If detection of the engaged tone is in use and if such a tone is detected, it is the response NO CARRIER which is sent back instead of BUSY .If dial tone detection is in use or selected and if no such tone is detected, it is the response NO CARRIER which is sent back instead of NO DIAL TONE .The binary value 100 is written in bits 6, 5 and 4 of S22 respectively.
Deactivates detection of engaged tones except if this is imposed by national requirements; only sends the result codes OK , CONNECT , RING , NO CARRIER , ERROR , NO DIAL TONE , NO ANSWER and
CONNECT XXXX .If detection of the engaged tone is in use and if such a tone is detected, it is the response NO CARRIER which is sent back instead of BUSY .If dial tone detection is in use or selected and if no such tone is detected, it is the response NO CARRIER which is sent back instead of NO DIAL
TONE .The binary value 101 is written in bits 6, 5 and 4 of S22 respectively.
Activates detection of engaged tones; only sends the result codes OK , CONNECT , RING , NO CARRIER ,
ERROR , NO DIAL TONE , NO ANSWER et CONNECT XXXX .Blind dialing mode is activated/deactivated by the national parameters.If dial tone detection is in use and if no such tone is detected, it is the reply
NO CARRIER which is sent instead of NO DIAL TONE .The binary value 110 is written in bits 6, 5 and
4 of S22 respectively.
Activates detection of engaged tones; sends all messages. The binary value 111 is written in bits 6,
5 and 4 of S22 (default value) respectively.
TLX DS COM PL7 xxE
153
Appendices
Result codes The following table lists the possible command responses.
Code
OK
ERROR
Description n = 0 to 4.
If n is not in the range 0 to 4.
Table of result codes
The n value
18
19
20
22
14
15
16
17
23
24
32
33
10
11
12
13
8
9
6
7
4
5
2
3
0
1
Abbreviated Complete form form
OK
CONNECT
RING
NO CARRIER
ERROR
CONNECT 1200
NO DIAL TONE
BUSY
NO ANSWER
CONNECT 0600
CONNECT 2400
CONNECT 4800
CONNECT 9600
CONNECT 7200 n = 0
CONNECT 12000
CONNECT 14400
CONNECT 19200
CONNECT 38400
CONNECT 57600
CONNECT 115200
CONNECT 230400 X
CONNECT 75RTX / 1200RX 1
CONNECT 1200TX / 75RX
DELAYED
1
4
BLACKLISTED
FAX
4
X
1
1
1
1
1
1
1
1
1
1
X
1
3
3
X
1
X
X
X
X n = 1
X
X
X
X
X
X
X
X
3
3
X
X
X
X
X
X
X
4
X
X
4
X
X
X
X
X n = 2 n = 3
X
X
X
X
X
X
X
X
X
3
X
X
X
X
X
X
X
4
X
X
4
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
4
X
X
4
X
X
X
X
X n = 4
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
Note
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Note 4
-
154
TLX DS COM PL7 xxE
Appendices
77
78
79
80
66
67
69
70
81
84
91
150
61
62
63
64
56
57
58
59
52
53
54
55
48
49
50
51
44
45
46
47
Abbreviated form
Complete form
35
40
DATA
CARRIER 300
CARRIER 1200 / 75
CARRIER 75 / 1200
CARRIER 1200
CARRIER 2400
CARRIER 4800
CARRIER 7200
CARRIER 9600
CARRIER 12000
CARRIER 14400
CARRIER 16800
CARRIER 19200
CARRIER 21600
CARRIER 24000
CARRIER 26400
CARRIER 28800
CONNECT 16800
CONNECT 21600
CONNECT 24000
CONNECT 26400
CONNECT 28800
COMPRESSION: CLASS 5
COMPRESSION: V.24 bis n = 0
COMPRESSION: NONE
PROTOCOL: NONE
PROTOCOL: LAPM
CARRIER 31200
CARRIER 33600
PROTOCOL: ALT
PROTOCOL: ALT-CELLULAR X
CONNECT 33600 1
X
X
CONNECT 31200
CARRIER 32000
1
X
X
X
X
X
X
X
1
1
1
1
X
1
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
TLX DS COM PL7 xxE n = 1 n = 2
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X n = 3
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
Note
-
-
-
Note 3
Note 3
-
-
Note 3
Note 3
Note 4
Note 2
Note 2
Note 2
Note 2
-
-
Note 2
Note 2
-
-
-
Note 2
Note 2
Note 2
Note 2
Note 2
-
-
-
-
-
-
-
n = 4
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
155
Appendices
171
172
173
174
167
168
169
170
175
176
177
+ F4
161
162
165
166
157
158
159
160
153
154
155
156
Abbreviated Complete form form
151
152
CARRIER 34000
CARRIER 36000
CARRIER 38000
CARRIER 40000
CARRIER 42000
CARRIER 44000
CARRIER 46000
CARRIER 48000
CARRIER 50000
CARRIER 52000
CARRIER 54000
CARRIER 56000
CONNECT 32000
CONNECT 34000
CONNECT 36000
CONNECT 38000
CONNECT 40000
CONNECT 42000
CONNECT 44000
CONNECT 46000
CONNECT 48000
CONNECT 50000
CONNECT 52000
CONNECT 54000
CONNECT 56000
+FCERROR n = 0 n = 1
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X n = 2 n = 3
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X n = 4
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
Note
Note 4
Note 4
Note 4
Note 4
Note 4
Note 4
Note 4
Note 4
Note 4
Note 4
Note 4
Note 4
Note 4
Note 4
Note 4
Note 4
Note 4
Note 4
Note 4
Note 4
Note 4
Note 4
Note 4
Note 4
Note 4
-
156
TLX DS COM PL7 xxE
Appendices
Abbreviated form
Complete form n = 0 n = 1 n = 2 n = 3 n = 4 Note
2
3
4
Observatio ns
1 An ‘X’ in the column means that the message in question (in its text form or only numerical) is generated when the corresponding value ‘n’ (indicated at the top of column) has been selected with the ATXn command. If the column is blank, no message is generated for this table slot. A number sends back a less explicit message (in complete or abbreviated form) which will be sent to the table slot in question.
RC288 modems and higher.
RC336 modems and higher.
RC56 modems.
TLX DS COM PL7 xxE
157
Appendices
Yn - Disconnection after prolonged inactivity
Introduction
Parameters
This command activates/deactivates generation and response to a disconnection after prolonged inactivity. The parameter value, if valid, is written in bit 7 of S21.
The parameters are:
Code
Y0
Y1
Description
Deactivates disconnection after prolonged inactivity.
Activates disconnection after prolonged inactivity. In error correction mode, the modem sends an inactivity signal of four seconds before hanging up. In the same mode, the modem responds to the receipt of a prolonged inactivity signal
(for example a 'break' signal of more than 1.6 seconds) by hanging up.
Result codes The following table lists the possible command responses.
Code
OK
ERROR
Description n = 0 to 1.
If n is not in the range 0 to 1.
158
TLX DS COM PL7 xxE
Appendices
Zn - Software reset of modem and restoration of profile
Introduction
Parameters
The modem executes a software reset and reestablishes the configuration profile defined by the parameter.
In the absence of a parameter, zero is assumed.
The parameters are:
Code
Z0
Z1
Description
Software reset of modem and reestablishment of stored profile 0.
Software reset of modem and reestablishment of stored profile 1.
Result codes The following table lists the possible command responses.
Code
OK
ERROR
Description n = 0 to 1.
If n is not in the range 0 to 1.
TLX DS COM PL7 xxE
159
Appendices
&Cn - RLSD Option (detection of DCD carrier)
Introduction
Parameters
The modem monitors the carrier detection output according to the parameter entered. The parameter value, if valid, is written in bit 5 of S21.
The parameters are:
Code
&C0
&C1
Description
Carrier detection is active all the time (default value).
Carrier detection depends on the carrier status.
Result codes The following table lists the possible command responses.
Code
OK
ERROR
Description n = 0 to 1.
If n is not in the range 0 to 1.
160
TLX DS COM PL7 xxE
Appendices
&Dn - DTR Option (Data Terminal Ready)
Introduction
Parameters
This command interprets loss of the DTR signal sent by the DTE, according to the parameter entered. The parameter value, if valid, is written in bits 3 and 4 of S21.
The parameters are:
Code
&D0
&D1
&D2
&D3
Description
Loss of the DTR signal is interpreted as follows according to the &Q value in progress (default value): l &Q0,&Q5, &Q6: ignores the DTR signal (assumed activated) and enables operation with DTEs which do not support DTR signals.
l &Q1, &Q4: loss of the DTR signal causes the modem to hang up. There is no repercussion on automatic answer.
l &Q2, &Q3: loss of the DTR signal causes the modem to hang up. Automatic answer is inhibited.
Loss of the DTR signal is interpreted as follows according to the &Q value in progress: l &Q0, &Q1, &Q4, &Q5, &Q6: loss of the DTR signal is interpreted by the modem as though the synchronous escape sequence had been entered.
The modem returns to asynchronous command mode without l disconnection.
&Q2, &Q3: loss of the DTR signal causes the modem to hang up. Automatic answer is inhibited.
Loss of the DTR signal is interpreted as follows according to the &Q value in progress: l &Q0 to &Q6: loss of the DTR signal causes the modem to hang up.
Automatic answer is inhibited.
Loss of the DTR signal is interpreted as follows according to the &Q value in progress: l &Q0, &Q1, &Q4, &Q5, &Q6: loss of the DTR signal causes the modem to reset the software as though it had received the Z command. The value of
&Y defines the profile which is loaded.
l &Q2, &Q3: loss of the DTR signal causes the modem to hang up. Automatic answer is inhibited.
Note: If &Q5, &Q6, +FCLASS=1 is in use, the result is identical to the &Q0 command.
TLX DS COM PL7 xxE
161
Appendices
&Fn - Restoration of the factory configuration (profile)
Introduction
Parameters
The modem loads the defined factory default configuration according to the parameter entered. The default Rockwell values corresponding to the 0 (&F0) profile are used for each command and in the S register descriptions. Two profiles are available. A configuration profile is made up of a sub-set of S registers.
The parameters are:
Code
&F0
&F1
Description
Reestablishes the factory profile 0 (default value).
Reestablishes the factory profile 1.
162
TLX DS COM PL7 xxE
Appendices
&Gn - Selection of guard tone
Introduction
Parameters
The modem generates the guard tone selected by this command according to the parameter entered (differential phase shift modulation modes only). The parameter value, if valid, is written in bits 6 and 7 of S23.
The parameters are:
Code
&G0
&G1
&G2
Description
Deactivates the guard tone (default value for US models).
Deactivates the guard tone.
Selects a guard tone of 1800 Hz (default value for W-class models).
Result codes
Note: In certain countries, this command may not be authorized.
The following table lists the possible command responses.
Code
OK
ERROR
Description n = 0 to 2.
If n is not in the range 0 to 2.
TLX DS COM PL7 xxE
163
Appendices
&Kn – Flow control
Introduction
Parameters
This command defines the DTE/DCE (terminal/modem) flow control mechanism.
The parameter value, if valid, is written in bits 0, 1 and 2 of S39.
The parameters are:
Code
&K0
&K3
&K4
&K5
&K6
Description
Deactivates flow control.
Activates RTS/CTS flow control - hardware flow control (default value for data modem modes).
Activates XON/XOFF flow control – software flow control.
Activates transparent XON/XOFF flow control.
Activates RTS/CTS flow control and XON/XOFF flow control at the same time
(default value for fax-modem modes).
Result codes The following table lists the possible command responses.
Code
OK
ERROR
Description n = 0, 3 to 6.
If n is not equal to 0 or 3 to 6.
164
TLX DS COM PL7 xxE
Appendices
&Pn - Selection of pulse dialing close/open report
Introduction
Parameters
This command determines the close/open report used during pulse dialing. It only has an effect if the appropriate bit activating this command is set by the program
ConfigurACE.
If the command is activated, it has priority over the close/open reports defined by the
OEM parameters in ConfigurACE. The default value depends on the country. The parameter value, if valid, is written in bits 3 and 4 of S28.
The parameters are:
Code
&P0
&P1
&P2
&P3
Description
Selection of 39%-61% as close/open report at 10 pulses per second (default value).
Selection of 33%-67% as close/open report at 10 pulses per second.
Selection of 39%-61% as close/open report at 20 pulses per second.
Selection of 33%-67% as close/open report at 20 pulses per second.
Result codes The following table lists the possible command responses.
Code
OK
ERROR
Description n = 0 to 3.
If n is not in the range 0 to 3.
TLX DS COM PL7 xxE
165
Appendices
&Qn - Synchronous/asynchronous mode
Introduction
Parameters
This command monitors the authorized connection modes. It is used in association with S36 and S48 (see also command \N).
The parameters are:
Code
&Q0
&Q1
&Q2
&Q4
&Q5
&Q6
Description
Selects direct asynchronous mode.
Selects
Selects
Selects automatic synchronous mode. The binary value 100 is written in bits 3,
1 and 0 of S27 respectively.
The modem attempts to establish a link with error correction. The mode can be configured with S36 to determine if, in case of failure, the modem hangs up or if it falls back to an asynchronous connection. The binary value 101 is written in bits 3, 1 and 0 of S27 (default value) respectively.
Selects normal asynchronous mode (with baud rate buffer). The binary value
110 is written in bits 3, 1 and 0 of S27 respectively.
Result codes The following table lists the possible command responses.
Code
OK
ERROR
Description n = 0, 1, 2, ,4, 5, 6.
If n is not equal to 0, 1, 2, 4, 5, or 6.
166
TLX DS COM PL7 xxE
Appendices
&Rn - RTS/CTS option
Introduction
Parameters
This command selects the mode for monitoring of the ready to send signal (Clear to
Send - CTS) by the modem. The operation of the CTS signal is modified if hardware flow control is selected (see command &K).
The parameters are:
Code
&R0
&R1
Description
In synchronous mode, the CTS signal follows the RTS status (request to send); the RTS-CTS delay is defined by S26. In asynchronous mode, CTS operates according to V.25 handshaking.
In synchronous mode, CTS is always active (the RTS transitions are ignored).
In asynchronous mode, CTS does not become inactive unless it is imposed by flow control (default value).
Result codes The following table lists the possible command responses.
Code
OK
ERROR
Description n = 0 to 1.
If n is not in the range 0 to 1.
TLX DS COM PL7 xxE
167
Appendices
&Sn - DSR Monitoring (Data Station Ready)
Introduction
Parameters
This command selects the way in which the modem monitors the DSR signal (Data
Station Ready). The parameter value, if valid, is written in bit 6 of S21.
The parameters are:
Code
&S0
&S1
Description
The DSR signal is always active (default value).
The DSR signal becomes active after the detection of an answer tone and inactive after the loss of the carrier.
Result codes The following table lists the possible command responses.
Code
OK
ERROR
Description n = 0 to 1.
If n is not in the range 0 to 1.
168
TLX DS COM PL7 xxE
Appendices
&V - Display of current configuration and stored profiles
Introduction
Result codes
This command gives the current configuration (active), the profiles (defined by the user) and the first four stored telephone numbers.
The profiles and the stored telephone numbers are not displayed if the NVRAM memory is not installed or if it is detected as being non operational by the NVRAM test during the reset process.
The following table lists the possible command responses.
Code
OK
Description
-
Example The example
AT&V
ACTIVE PROFILE :
B0 E1 L1 M1 N1 QO T V1 W0 X4 Y0 &C0 &D0 &G2 &J0 &K3 &Q5 &R1
&S0 &T4 &X0 &Y0
S00:002 S01:000 S02:043 S03:013 S04:010 S05:008 S06:002
S07:030 S08:002 S09:006S10:014 S11:255 S12:050 S18:000 S25:005
S26:001 S36:007 S37:000 S38:020 S46:138
S48:007 S95:000
PROFILE 0 STORED :
B0 E1 L1 M1 N1 QO T V1 W0 X4 Y0 &C0 &D0 &G2 &J0 &K3 &Q5 &R1
&S0 &T4 &X0
S00:002 S02:043 S06:002 S07:030 S08:002 S09:006 S10:014
S11:095 S12:050 S18:000
S36:007 S37:000 S40:105 S41:003 S46:138 S95:000
PROFILE 1 STORED :
B0 E1 L1 M1 N1 QO T V1 W0 X4 Y0 &C0 &D0 &G2 &J0 &K3 &Q5 &R1
&S0 &T4 &X0
S00:002 S02:043 S06:002 S07:030 S08:002 S09:006 S10:014
S11:095 S12:050 S18:000
S36:007 S37:000 S40:105 S41:003 S46:138 S95:000
TELEPHONE NUMBERS :
0 = 1 =
2 = 3 =
OK
TLX DS COM PL7 xxE
169
Appendices
&Wn – Storage of the current configuration
Introduction
Parameters
Saves the current configuration (active profile), including the S registers, in one of the two user profiles in NVRAM memory, according to the value of the parameter.
This command will result in an ERROR response if the NVRAM memory is not installed or if it is detected as being non operational by the test.
The current configuration is made up of a list of storable parameters, as illustrated by the &V command. These values are reassigned to the active configuration on receipt of a Zn command or on power-up (see &Yn command).
The parameters are:
Code
&W0
&W1
Description
Stores the active configuration as profile 0.
Stores the active configuration as profile 1.
Result codes The following table lists the possible command responses.
Code
OK
ERROR
Description n = 0 to 1.
If n is not in the range 0 to 1.
170
TLX DS COM PL7 xxE
&Yn - Designation of a default profile on reset
Introduction
Parameters
Selects the user profile to be loaded after a hardware reset.
The parameters are:
Code
&Y0
&Y1
Description
The modem uses profile 0.
The modem uses profile 1.
Result codes The following table lists the possible command responses.
Code
OK
ERROR
Description n = 0 to 1.
If n is not in the range 0 to 1.
Appendices
TLX DS COM PL7 xxE
171
Appendices
&Zn – Storage of telephone numbers
Introduction
Parameters
The modem can store a maximum of 20 telephone numbers. Each telephone number can be up to 45 digits.
The parameters are:
Code Description
&Zn = x n = 0 to 19 (W-class) and x = number string (needs 2048 bytes of NVRAM).
Result codes The following table lists the possible command responses.
Code
OK
ERROR
Description n = 0 to 19 and x less than or equal to 45 digits.
If n is greater than 19 or x greater than 45 digits.
172
TLX DS COM PL7 xxE
Appendices
%Cn - Activation / deactivation of data compression
Introduction
Parameters
Activates / deactivates data compression The parameter value, if valid, is written in bits 0 and 1 of S41.
The parameters are:
Code
%C0
%C1
%E2
%E3
Description
Deactivates data compression.
Activates MNP 5 data compression.
Activates V.42 bis data compression.
Activates V.42 bis and MNP 5 data compression.
Result codes The following table lists the possible command responses.
Code
OK
ERROR
Description n = 0 to 3.
If n is not in the range 0 to 3.
TLX DS COM PL7 xxE
173
Appendices
%En - Activation/deactivation of line quality monitoring or automatic resynchronization or fallback/increase of transfer rate
Introduction
Parameters
Determines whether or not the modem automatically monitors the line quality and requests resynchronization (%E1) or a fallback when the line quality is insufficient or an increase in the transfer rate when the line quality is sufficient (%E2). This only applies to switched lines. The parameter value, if valid, is written in bits 2 and 6 of
S41.
The resynchronization attempt, if it is activated, lasts a maximum of 30 seconds.
The parameters are:
Code
%E0
%E1
%E2
Description
Deactivates line quality monitoring and automatic resynchronization attempt
(default value).
Activates line quality monitoring and automatic resynchronization attempt.
Activates line quality monitoring and transfer rate fallback/increase.
Result codes The following table lists the possible command responses.
Code
OK
ERROR
Description n = 0 to 2.
If n is not in the range 0 to 2.
174
TLX DS COM PL7 xxE
Appendices
%L - Level of line signal
Introduction
Result codes
Sends back a value which indicates the level of signal received. The returned value is a direct indication of the level of reception at the modem data pumping device, and not at the telephone line connector.
For example, 009 = -9 dBm, 043 = -43 dBm, and so on.
The following table lists the possible command responses.
Code
OK
Description n = 0 to 1.
TLX DS COM PL7 xxE
175
Appendices
%Q - Quality of line signal
Introduction
Result codes
Indicates the line quality (DAA function, network access connector). Sends back most significant byte of EQM value. Depending on the EQM value, there can be a resynchronization attempt or a fallback/increase of transfer rate, triggered by &E1 or
%E23.
The following table lists the possible command responses.
Code
OK
ERROR
Description
If connected.
If not connected or connected at 300 b/s, in V.23 or in fax mode.
Example AT&Q
015
176
TLX DS COM PL7 xxE
Appendices
\Kn - BREAK control
Introduction
Parameters of case 1
According to the parameter entered, controls the modem response to a break signal received from the DTE, from the remote modem or from the \B command. The value of the parameter, if valid, is written in bits 3, 4 and 5 of S40. The response is different according to the case.
Code
\K0
\K1
\K2
\K3
\K4
\K5
The first case is that of the modem which receives a break from the DTE when it is in data transfer mode:
Description
Switches to on-line command mode, no break sent to the remote modem.
Empties the data buffers and sends a break to the remote modem.
As \K0.
Immediately sends a break to the remote modem.
As \K0.
Sends a break to the remote modem in sequence with the transmitted data
(default value).
Parameters of case 2
Code
\K0
\K1
\K2
\K3
\K4
\K5
The second case is that of the modem which is in on-line command mode (awaiting
AT commands) during a connection, and which receives a \B command for it to send a break to the remote modem:
Description
Empties the data buffers and sends a break to the remote modem.
Empties the data buffers and sends a break to the remote modem.
Immediately sends a break to the remote modem.
Immediately sends a break to the remote modem.
Sends a break to the remote modem in sequence with the data.
Sends a break to the remote modem in sequence with the data.
TLX DS COM PL7 xxE
177
Appendices
Parameters of case 3
Code
\K0
\K1
\K2
\K3
\K4
\K5
The third case is that of the modem which receives a break from the remote modem during a connection without error correction:
Description
Empties the data buffers and sends a break to the DTE.
Empties the data buffers and sends a break to the DTE.
Immediately sends a break to the DTE.
Immediately sends a break to the DTE.
Sends a break to the DTE in sequence with the received data.
Sends a break to the DTE in sequence with the received data (default value).
Result codes The following table lists the possible command responses.
Code
OK
ERROR
Description n = 0 to 5.
If n is not in the range 0 to 5.
178
TLX DS COM PL7 xxE
Appendices
\Nn - Operating mode
Introduction
Parameters
This command defines the preferred error correction mode to negotiate during a subsequent connection. It is assigned by the configuration of the OEM firmware.
The parameters are:
Code
\N0
\N1
\N2
\N3
\N4
\N5
Description
Selects normal mode with baud rate buffer (without error correction mode)
(equivalent to &Q6).
Serial interface selected – selects direct mode and is equivalent to the operating mode (equivalent to &Q0). Parallel interface selected – as \N0.
Select reliable mode (with error correction). The modem attempts first to establish an LAPM correction then an MNP connection. If it fails, the modem hangs up (equivalent to &Q5, S36=4 and S48=7).
Selects automatic reliable mode. This mode is identical to \N2 mode apart from the fact that if the modem does not manage to establish a reliable connection, it falls back to normal mode (equivalent to &Q5, S36=7 and S48=7).
Selects LAPM error correction mode. If it fails, the modem hangs up
(equivalent to &Q5, and S48=0).
Selects MNP error correction mode. If it fails, the modem hangs up (equivalent to &Q5, S36=4 et S48=128).
Result codes The following table lists the possible command responses.
Code
OK
ERROR
Description n = 0 to 5.
If n is not in the range 0 to 5.
TLX DS COM PL7 xxE
179
Appendices
Values of the registers of the TSX MDM 10 card in a PLC
Introduction
Registers
The default values of the TSX MDM 10 card are stored in ROM memory and loaded during power-up or by the ATZn command.
S18
S25
S26
S36
S09
S10
S11
S12
S37
S38
S46
S48
S95
The default values are shown in the following table:
S03
S04
S05
S06
Register
S00
S01
S02
S07
S08
Function
Rings to auto-answer
Ring counter
Escape character
Carriage Return character
Line Feed Character
Backspace character
Wait time for dial tone
Wait time for carrier
Pause time for dial delay modifier
Carrier detect response time 006
Carrier loss disconnect time 014
DTMF tone duration
Escape code guard time
070
050
Test timer
Delay to DTR off
RTS to CTS delay
LAPM failure control
000
005
000
007
Line connection speed 000
Delay before forced hangup 020
Data compression control
V.42 negotiation control
Result code messages control
136
007
000
013
010
008
005
Values
000
000
043
050
002
180
TLX DS COM PL7 xxE
Communication via Modbus Plus
III
Introduction
Aim of this part
What's in this part?
This part introduces the principles of configuring and communicating with Modbus
Plus via PL7 software.
This Part contains the following Chapters:
Chapter
12
13
14
15
16
17
Chaptername
General
Peer Cop service
Configuring Modbus Plus communication
Programming Modbus Plus communication
Debugging Modbus Plus communication
Language objects associated with Modbus Plus communication
Page
181
TLX DS COM PL7 xxE
Communication via Modbus Plus
182
TLX DS COM PL7 xxE
General
12
Introduction
Aim of this
Chapter
What's in this
Chapter?
This Chapter introduces Modbus Plus communication and its services.
This Chapter contains the following Maps:
Topic
Introduction
Compatibility
Integration into an X-WAY architecture
Integration into a Modbus Plus architecture
Page
TLX DS COM PL7 xxE
183
Modus Plus communication: General
Introduction
Introduction Modbus Plus communication is used to exchange data between all devices connected by the bus.
The Modbus Plus protocol is based on the principle of a logical token bus (Logical
Token passing). Each station of one network is identified by an address between 1 and 64 and each station accesses the network after reception of a token. Duplicated addresses are not valid.
Network example
Modbus Plus
2 12
Premium Quantum
Token bus (logic ring)
Associated manuals
A Modbus Plus communication channel comprises three main functions: l point to point data exchanges via the messaging service, using the Modbus protocol, l broadcast exchanges of global data between all the stations participating in this exchange, l multidrop exchanges of specific data via the Peer Cop services.
If you require further information you should consult the following manuals:
Title
Modbus Plus Network - Installation and planning manual
TSX Micro PLCs - Installation manual
Premium TSX PLCs - Installation manual
Description
Detailed description of the set-up procedure for the Modbus Plus network
Hardware installation
Hardware installation
184
TLX DS COM PL7 xxE
Modus Plus communication: General
Compatibility
Hardware
Software
This type of communication is available for PLCs of at least version V3.0: l l
TSX Premium via the intermediary of the TSX MBP100 PCMCIA card,
TSX Micro accepting the PCMCIA card described below.
Note: This type of communication is not available with TSX SCY 21601 modules.
TSX Premium and Micro PLCs do not support redundancy with the TSX MBP 100 card.
The PCMCIA TSX MBP 100 card can process 4 communication functions at the same time.
The maximum size of the number of objects per communication function is 125 useful data words (maximum frame of 256 bytes).
In the event of communication of a TSX Premium and Micro PLC with a TSX
Quantum PLC, it is necessary to shift addressing. To access a Quantum object with address n, the communication function on the Premium side must have the address n-1.
The Peer Cop service is only supported by TSX Premium PLCs.
During configuration of inputs and outputs for the Peer Cop service, it is possible to allocate up to 32 internal words to each connection point in the local bus. The total number of words must not exceed 500 internal words.
TLX DS COM PL7 xxE
185
Modus Plus communication: General
Integration into an X-WAY architecture
Introduction A Modbus Plus segment can be integrated into an X-WAY network architecture.
Communications between stations on the different networks are possible under certain conditions of use.
Communication to a Modbus Plus network
A client application connected to a FIPWAY or ETHERNET TCP/IP network can communicate with a Modbus Plus station via the Modbus protocol.
In this case, you must indicate the X-WAY network address of the TSX Premium
PLC which is connected on the Modbus Plus segment as well as on the FIPWAY network, and the number of the destination Modbus Plus station.
The syntax is as follows:
{network number, station number} 0.1. Modbus Plus station number
Example In this example, the FIPWAY station {5.3} has a Modbus Plus connection and therefore, any remote FIPWAY station which wishes to communicate with a Modbus
Plus station (for example station 5) must use this address.
READ_VAR(ADR#{5.3}0.1.5, '%MW', 100, 10,%MW200:10, %MW300:4)
Configuration example
READ_VAR(ADR#{5.3}0.1.5, '%MW', 100,
10,%MW200:10, %MW300:4)
Premium
3
FIPWAY #5
Quantum
8
Modbus Plus
Quantum
5
Note: Routing between FIPWAY and Modbus Plus is carried out by the automatic system. In a network architecture, it is not necessary to declare a bridge station.
186
TLX DS COM PL7 xxE
Modus Plus communication: General
Communication from a Modbus
Plus network
If a Modbus Plus segment is integrated into an X-WAY architecture, a Quantum station cannot communicate with stations connected to another network in this architecture (for example FIPWAY or ETHERNET TCP/IP). Communication is only possible with the local Premium.
Example The Quantum PLC sends a write request to modify 5 words in the PL7 application
(%MW10, .etc.), but it does not have access to the other stations on Fipway.
Premium
3
FIPWAY #5
Quantum
5 Modbus Plus
MBP-MSTR write
5
10
RP=5.0.0.0.0
TLX DS COM PL7 xxE
187
Modus Plus communication: General
Integration into a Modbus Plus architecture
Introduction
Premium to
Quantum
Quantum to
Premium
In a Modbus Plus architecture, a TSX Quantum PLC application can communicate with a TSX Premium PLC and vice versa.
Communication from a TSX Premium PLC to a remote station is described in the exchange service on remote networks.
Communication from a TSX Quantum PLC to a TSX Premium PLC is available via
MSTR blocks.
In this case, the TSX Premium or Micro are servers; therefore, all Modbus Plus stations connected to a network architecture, up to a maximum of 5 levels, can communicate with them.
Example
1
Premium
2
Quantum
3 Modbus Plus
Bridge Plus
Modbus Plus
5
8
Bridge Plus
Modbus Plus
Quantum
4
Quantum
MSTR read
The Quantum station sends a read request to the Premium station using an address path: 8.5.1.0.0 (routing path).
188
TLX DS COM PL7 xxE
Modus Plus communication: General
The MSTR function block is used to read or write internal words of a Premium or
Micro station. The parameter of the slave register of the MSTR function block directly indicates the address of the internal word %MW of the PL7 application. This function block is also used to read or reset the statistics counters of a Premium or
Micro station. This request is executed directly by the PCMCIA card which responds directly.
TLX DS COM PL7 xxE
189
Modus Plus communication: General
190
TLX DS COM PL7 xxE
Peer Cop service
13
Peer Cop service
Introduction
Specific inputs and outputs
Report
The Peer Cop service is an automatic exchange mechanism between stations connected to the same local Modbus Plus segment.
This service is used to maintain constant control over inputs / outputs which have been remoted by implicit exchanges.
l l
The TSX Premium PLCs support two types of Peer Cop transfer.
specific inputs, specific outputs.
The specific inputs and outputs are point to point services which use the multicast protocol (multistations). Each message contains one or several destination addresses for sending the data. This function is used to exchange data to several stations without repetition.
l l
Three types of report are associated with the specific inputs and outputs: activity bit: provides information on the availability and validity of the status bits, status bits (to the number of one bit per station): l ensure coherence between the number of specific inputs configured and the l l number of specific inputs received, indicate if the specific inputs have been received during the Timeout, presence bits (to the number of one bit per station): indicate if the specific inputs have been refreshed.
Note: The presence bits are only valid for the specific inputs.
191
TLX DS COM PL7 xxE
Communication Modbus Plus: Peer Cop service
Example for the inputs
The data blocks are copied in full from the PCMCIA card to the internal word space, reserved during configuration.
Max. 500 characters
In the following example, the address of the first internal word is %MW10:
Internal words PCMCIA card Modbus Plus network
%MW10
3 words from station 1
%MW13
32 words from station 5
%MW45
20 words from station 6
%MW65
12 words from station 8
%MW77
32 words from station 9 copy
Peer Cop data specific inputs
Station 1
Station 5
Station 6
Station 62
%MW150
3 words from station 62
Activity bit
%IW0.1.6
%IW0.1.7
...
%IW0.1.14
copy
Status bits
Presence bits
192
TLX DS COM PL7 xxE
Communication Modbus Plus: Peer Cop service
Example for the outputs
The data blocks are copied in full from the internal word space, reserved during configuration, to the PCMCIA card. The reports are copied from the PCMCIA card to the language objects.
In the following example, the address of the first internal word is %MW10:
Max. 500 characters
Internal words
%MW10
3 words from station 1
%MW13
32 words of station 5
%MW45
20 words of station 6
%MW65
12 words from station 8
%MW77
32 words from station 9 copy
PCMCIA card
Specific outputs
Peer Cop data
Modbus Plus network
Station 1
Station 5
Station 6
Station 62
%MW150
3 words from station 62
%IW0.1.6
%IW0.1.7
...
%IW0.1.14
copy
Activity bit
Status bits
Station 1
Station 5
Station 6
Station 62
TLX DS COM PL7 xxE
193
Communication Modbus Plus: Peer Cop service
194
TLX DS COM PL7 xxE
Configuring Modbus Plus communication
14
Introduction
Aim of this
Chapter
What's in this
Chapter?
This Chapter describes the Configuration process during set-up of Modbus Plus communication.
This Chapter contains the following Maps:
Topic
How to access the Modbus Plus PCMCIA card parameters
Modbus Plus configuration screen
Functions accessible from Modbus Plus
Modbus Plus configuration parameters
Configuring the specific inputs and outputs
Page
195
TLX DS COM PL7 xxE
Modbus Plus configuration
How to access the Modbus Plus PCMCIA card parameters
Introduction
How to access the link
This operation describes how to access the configuration parameters of the Modbus
Plus link via the intermediary of the PCMCIA cards for TSX Premium PLCs.
The following table shows the procedure for accessing the Modbus Plus link:
Step
1
2
Action
Access the communication channel configuration screen.
Select the communication channel from the drop-down menu CHANNEL 1
Example
CHANNEL 1:
CHANNEL 1 (No PCMCIA submodule)
(Link not configured)
CHANNEL 1
MAST
3 Select the PCMCIA card from the drop-down menu TSX MBP 100 MODBUS+
PCMCIA CARD :
Example
CHANNEL 1
CHANNEL 1 (No PCMCIA submodule)
(Link not configured) MAST
TSX FPP 200 FIPWAY PCMCIA CARD
TSX FPP 10 FIPIO PCMCIA CARD
TSX FPP 100 MODBUS+ PCMCIA CARD
TSX MDM 10 MODEM PCMCIA CARD
FCS SCP 111 RS232 OPEN PCMCIA CARD
FCS SCP 114 RS485 OPEN PCMCIA CARD
196
TLX DS COM PL7 xxE
Modbus Plus configuration
Modbus Plus configuration screen
Introduction
Illustration
This screen, split into two zones, is used to declare the communication channel and to configure the parameters necessary for a Modbus Plus link.
The screen dedicated to Modbus Plus communication looks like this:
TSX 57302 [RACK 0 POSITION 0]
Configuration
Designation: PROCESSOR TSX P 57302
1
CHANNEL 1:
CHANNEL 1
MODBUS+
TSX MBP 100 MODBUS+ PCMCIA CARD
MAST
2
Station number: : 1
Peer Cop
Value of Timeout:
Input fallback mode
Maintain
Reset to 0
500 (ms)
Specific Inputs
Specific outputs
Elements and functions
This table describes the different zones that make up the configuration screen:
Address Zone
1 common
2 specific
Function
(See : PL7 Micro/Junior/Pro ; Communication applications ;
Volume 1) is used to select or complete the parameters of a Modbus Plus link.
It is split into two types of information: l l station addressing, the parameters concerning the Peer Cop service.
TLX DS COM PL7 xxE
197
Modbus Plus configuration
Functions accessible from Modbus Plus
Introduction
Accessible functions
Depending on the chosen communication supports, some parameters cannot be modified. They appear grayed out.
The summary table below shows the various choices possible:
Functions
Station number
Peer Cop
Input fallback mode
Specific inputs
Specific outputs
TSX MPB 100
For processors of at least version V3.0
For processors of at least version V3.3
Accessible if the Peer Cop box is checked
Accessible if the Peer Cop box is checked
Accessible if the Peer Cop box is checked
198
TLX DS COM PL7 xxE
Modbus Plus configuration
Modbus Plus configuration parameters
Introduction
Addressing parameter
Peer Cop parameters
Once the communication channel has been configured, complete the parameters dedicated to the Modbus Plus link.
They are split into two windows: l l the Station number window, the Peer Cop window,
The window looks like this:
Station number: : 1
This parameter is used to define the address (or connection point) of the station on the Modbus Plus network.
The window is only accessible by checking the box Peer Cop:
Peer Cop
Value of Timeout:
Input fallback mode
Maintain
Reset to 0
500 (ms)
Specific Inputs
Specific outputs
It can be used to: l complete the Timeout value: Input refresh time in milliseconds. It is used to specify the maximum time during which the inputs from remote stations must be l l updated in the PCMCIA card. In the event that data is not refreshed within the time allowed, an error is detected.
l l the default value is 20 ms, the values range from 20 ms to 2 s, l the increment is 20 ms.
define the Input Fallback mode: l maintained, l cleared.
access the values of the specific inputs and specific outputs. Peer Cop
TLX DS COM PL7 xxE
199
Modbus Plus configuration
Configuring the specific inputs and outputs
Introduction
Configuration rules
Specific inputs
If you have checked the box Peer Cop, you must specify the start address and the size of the data to be exchanged.
These data are stored in the internal words of the application. Peer Cop service,
The input words zone cannot be superimposed on the output words zone.
The internal words corresponding to the specific inputs or outputs are stored continuously.
The maximum size of the specific data must not exceed 1000 words (max. 500 words for the inputs and max. 500 words for the outputs).
After selection of the button Specific inputs, the following window will appear:
Peer Cop input
Station
8
9
6
7
10
3
4
1
2
5
Ref.
Length (0..32)
%MW10
%MW15
%MW24
%MW56
%MW84
%MW88
%MW104
%MW117
%MW149
5
9
32
28
4
16
13
32
19
Validate
Cancel
Address of 1st %MW
%MW 10
For each connection point of the local bus segment, the user must define: l l the start address in the table of internal words (%MW),
The size of the exchanges from 0 to 32 words per station on the local bus segment.
200
TLX DS COM PL7 xxE
Modbus Plus configuration
Specific outputs After selection of the button Specific outputs, the following window will appear:
Peer Cop outputs
Station
8
9
6
7
10
3
4
1
2
5
Ref.
%MW100
%MW105
%MW111
%MW126
%MW158
%MW184
%MW187
%MW199
%MW220
Length (0..32)
5
6
15
32
26
3
12
21
1
Validate
Cancel
Address of 1st %MW
%MW 100 l l
For each connection point of the local bus segment, the user must define: the start address in the table of internal words (%MW),
The size of the exchanges from 0 to 32 words per station on the local bus segment.
TLX DS COM PL7 xxE
201
Modbus Plus configuration
202
TLX DS COM PL7 xxE
Programming Modbus Plus communication
15
Introduction
Aim of this
Chapter
What's in this
Chapter?
This Chapter describes the Programming process during set-up of Modbus Plus communication.
This Chapter contains the following Maps:
Topic
Read and write service on local segment
Exchange service on remote Modbus Plus networks
Examples of Exchanges on Offset Networks
Diagnostic service
Global data exchange service
Page
203
TLX DS COM PL7 xxE
Modbus Plus programming
Read and write service on local segment
Introduction A TSX Micro or Premium PLC can exchange data with stations connected to the local Modbus Plus network.
Data exchanges The functions READ_VAR and WRITE_VAR are used to access remote stations on the same local segment, bits, internal words or input and output words in read / write mode.
These exchanges are explicit exchanges managed by the application.
The addressing from a TSX Premium station will be for example: l in read mode l
READ_VAR (ADR#0.1.10, '%MW', 10, 20, %MW10:20, %MW100:4) in write mode
WRITE_VAR (ADR#0.1.10, '%MW', 10, 20, %MW10:20, %MW100:4)
The following table describes the different parameters of the function:
Parameter
ADR#0.1.10
'%MW'
10
20
%MW10:20
%MW100:4
Description
Address of destination device for the message: l l l processor slot: 0 or 1
PCMCIA channel: 1 destination station number: 10
Type of object to be read or written, for example: internal words
Address of first word to be read or written
Number of words to be read or written
For reading: content of response
For writing: value of words to be written
Activity bit, exchange report, length
204
TLX DS COM PL7 xxE
Modbus Plus programming
Correspondence of object type
The tables describe the correspondence of object types between the TSX Premium and TSX Quantum PLCs.
The TSX Premium PLC is the sender of the request and the TSX Quantum PLC replies:
Type of PL7 object Responding Quantum object READ_VAR or WRITE_VAR function
'%MW'
'%M'
'%IW'
'%I' internal words internal bits input words input bits
4x... memory area
0x... memory area
3x... memory area
1x... memory area
The TSX Quantum PLC is the sender via an MSTR function block and the TSX
Premium PLC replies:
MSTR function block
READ
WRITE
Responding Premium object
%MW
%MW
Example
1
The TSX Premium PLC application writes 10 internal words in the TSX Quantum
PLC at address 2 and reads 5 input words in the TSX Quantum PLC at address 5:
2 5
Quantum
WRITE_VAR(ADR#0.1.2, ‘%MW’, 10, 5, %MW100:5, %MW200:4)
READ_VAR(ADR#0.1.5, ‘%IW’, 5, 8, %MW100:5, %MW200:4)
The internal words to be written in station 2 are at address 10.
The internal words to be read in station 5 are at address 5.
Quantum
TLX DS COM PL7 xxE
205
Modbus Plus programming
Exchange service on remote Modbus Plus networks
Introduction A TSX Micro or Premium PLC can exchange data with stations connected to other
Modbus Plus segments via BP85 Bridge Plus bridges.
Access to a remote station.
To access a station connected to another network segment, it is necessary to indicate the full address path (routing path) in the information sent.
Beforehand, indicate, in the request, the address of the first destination connection point on the local bus.
Next, clarify, in the data to be sent, each address of the devices which will allow the passage of the exchanges to the destination station.
Data exchanges This type of exchange is accessible via the function SEND_REQ . To differentiate the reading and writing of data from a remote station, a request code is associated to the function SEND_REQ . These exchanges are explicit exchanges managed by the application.
The addressing from a TSX Premium station will be for example: l in read mode
SEND_REQ (ADR#0.1.61, 16#36, %MW300:50, %MW450:150, l
%MW600:4) in write mode
SEND_REQ (ADR#0.1.61, 16#37, %MW300:50, %MW450:150,
%MW600:4)
The following table describes the different parameters of the function:
Parameters
ADR#0.1.61
16#36
16#37
%MW300:50
%MW450:150
%MW600:4
Description
Address of destination device for the message: l l l processor slot: 0 or 1
PCMCIA channel: 1 number of the destination connection point on the local bus:
61
Request code for reading objects
Request code for writing objects
Address path, length, data to be sent
Address, length of data to be received
Activity bit, exchange report, length
206
TLX DS COM PL7 xxE
Data coding
Modbus Plus programming
The data of read / write requests are encoded in internal words, to be sent in the following way:
%MW300
Third address
Second address
Fifth address
%MW301
Fourth address
Type
%MW302
Segment
%MW303 %MW304
Address of first word
%MW306 to
%MW349
Size of data Data
TLX DS COM PL7 xxE
207
Modbus Plus programming
Examples of Exchanges on Offset Networks
At a Glance
22
The following illustration shows the two types, which are processed subsequently:
Modbus Plus
Premium
13
Quantum
61
BP85
Bridge Plus
12 30
15 25
Quantum
62
Quantum
BP85
Bridge Plus
4 7
Quantum
9
22
Slave
A
1
Bridge multiplexer
2 3 4
Modem
Modem
Master
A
Modem
Slave
113
Slave
69
BP85
Bridge Plus
208
TLX DS COM PL7 xxE
Example 1
Modbus Plus programming
Reading 120 internal words to address 80 of the Quantum station at the local address of 62 using a TSX Premium requires: l l l the routing path to access the Quantum station: 61, 30, 22, 62, 0.
the reading request code: 16#36.
the actual size of data to be transferred (memorized in %MW603): 10 bytes.
SEND_REQ(ADR#0.1.61, 16#36, %MW300:5, %MW450:120, %MW600:4)
Coding of the data to be transferred:
Parameters
%MW300
%MW301
%MW302
%MW303
%MW304
No data
Values
0x161E
0x003E
0x0768
80
120
Description
Second and third changeover addresses (30, 22)
Fourth and fifth changeover addresses (62, 0)
Segment 104 and type 7 (depends on the type of variable to be read or written)
Address of the first internal word to be read in the Quantum station
Size of data to be read (in words)
Note: After the execution of the SEND_REQ function, it is necessary to reclassify the bytes in the correct order.
TLX DS COM PL7 xxE
209
Modbus Plus programming
Example 2 Writing 50 internal words to address 560 of slave 113 connected to port 4 on the multiplexer bridge using a TSX Premium requires: l l l l l the routing path to access the slave: 61, 25, 4, 113, 0.
the reading request code: 16#37.
the actual size of data to be transferred (memorized in %MW603): 110 bytes.
the values of the data to be written (memorized in %MX306 to %MW354).
the response (memorized in %MW450:1): does not contain any data to be received, but should have a minimum length of a word.
SEND_REQ(ADR#0.1.61, 16#36, %MW300:5, %MW450:120, %MW600:4)
Coding of the data to be transferred:
Parameters
%MW300
%MW301
%MW302
%MW303
%MW304
%MW305 to
%MW354
%MW603
Values
0x0419
0x0071
0x0768
560
50
110
Description
Second and third changeover addresses (25, 4)
Fourth and fifth changeover addresses (113, 0)
Segment 104 and type 7 (depends on the type of variable to be read or written)
Address of the first internal word to be written in the Quantum station
Size of the data to be written (in words)
Data to be written
Actual size of the data to be transmitted with this function (in bytes)
210
TLX DS COM PL7 xxE
Modbus Plus programming
Diagnostic service
Introduction A TSX Micro or Premium PLC can read or reset local or remote default counters on a local Modbus Plus network.
Data exchanges This type of exchange is accessible via the function SEND_REQ . To differentiate the reading and writing of data from a remote station, a request code is associated to the function SEND_REQ .
The addressing from a TSX Premium station will be for example: l Reading counters
SEND_REQ (ADR#0.1.5, 16#A2, %MW100:1, %MW200:20, %MW300:4) l resetting counters
SEND_REQ (ADR#0.1.5, 16#A4, %MW100:1, %MW200:1, %MW300:4)
The following table describes the different parameters of the function:
Parameters
ADR#0.1.5
16#A2
16#A4
%MW100:1
%MW200:20
%MW200:1
%MW300:4
Description
Address of destination device for the message: l l l processor slot: 0 or 1
PCMCIA channel: 1 number of the destination connection point on the local bus: 5
Request code for reading counters
Request code for resetting counters
No data to send
No response on reception
Content of error counters
Activity bit, exchange report, length
Note: The length parameter in the report words is initialized at 0 before the request is sent.
TLX DS COM PL7 xxE
211
Modbus Plus programming
Counter list The following table shows the counters.
Meaning
15
16
17
18
19
20
11
12
13
14
7
8
9
10
5
6
3
4
1
2
Number of the counter
Retransmit deferral error counter
Receive buffer DMA overrun error counter
Repeated command received counter
Frame size error counter
Receiver collision abort error counter
Receiver alignment error counter
Receiver CRC error counter
Bad-packet-length error counter
Bad link address error counter
Transmit buffer DMA underrun error counter
Bad internal packet length error counter
Bad mac function code error counter
Communication retry counter
Communication failed error counter
Good receive packet success counter
No response received error counter
Exception response received error counter
Unexpected path error counter
Unexpected response error counter
Forgotten transaction error counter
212
TLX DS COM PL7 xxE
Modbus Plus programming
Global data exchange service
Introduction The global data exchange service is a simple exchange mechanism which is used to send broadcast messages between stations connected on the same Modbus Plus network.
During an exchange, a station which has the token can broadcast words destined for other stations connected on the network. A receiving station takes the content of words transmitted by the sending station, stores them in its PCMCIA card and sends them back to the network. The same applies to each station when the token is passed.
Precautions for use
For TSX Premium and Micro PLCs, this service is provided by particular communication functions ( WRITE_GDATA and READ_GDATA ) periodically taken on by the application. It is not integrated in the Peer Cop transactions.
A TSX Premium or TSX Micro PLC can broadcast a maximum of 32 words.
Writing global data
Note: Data transfer from one station to another is automatic.
To read the global data which is sent, the application of the receiving station must read its PCMCIA card.
This type of exchange is accessible via the function WRITE_GDATA .
The addressing from a TSX Premium station will be for example:
WRITE_GDATA (ADR#0.1.SYS, %MW100:x, %MW200:4)
The following table describes the different parameters of the function:
Parameters
ADR#0.1.SYS
%MW100:x
%MW200:4
Description
Broadcast address: l l l processor slot: 0 or 1
PCMCIA channel: 1 system channel: transmission for all the stations on the network
Content of the global data to be transmitted (x = 1 to 32 words)
Activity bit, exchange report, length
TLX DS COM PL7 xxE
213
Modbus Plus programming
Reading global data
This type of exchange is accessible via the function READ_GDATA .
The addressing from a TSX Premium station will be for example:
READ_GDATA (ADR#0.1.10, %MW30:32, %MW300:4)
The following table describes the different parameters of the function:
Parameters
ADR#0.1.10
%MW30:32
%MW300:4
Description
Address of device sending the message: l l l processor slot: 0 or 1
PCMCIA channel: 1 number of station sending data: 10
Content of global data
Activity bit, exchange report, length
Note: The length of the global data actually read is contained in the activity report length word (e.g.: %MW304). One length = 0 means that there is no new global data available in the station specified in the request.
214
TLX DS COM PL7 xxE
Debugging Modbus Plus communication
16
Introduction
Aim of this
Chapter
What's in this
Chapter?
This Chapter describes the Debugging process during set-up of Modbus Plus communication.
This Chapter contains the following Maps:
Topic
Modbus Plus debugging screen
Modbus Plus debugging screen
Page
TLX DS COM PL7 xxE
215
Modbus Plus debugging
Modbus Plus debugging screen
Introduction
Illustration
This screen, split into two zones, is used to declare the communication channel and to access the debugging parameters for a Modbus Plus link.
The screen dedicated to Modbus Plus communication looks like this:
TSX 57302 [RACK 0 POSITION 0]
Debugging
Designation: PROCESSOR TSX P 57302 Version: 3.0
1
DIAG...
CHANNEL 1
CHANNEL 1
MODBUS*
TSX MBP 100 PCMCIA CARD MODBUS*
MAST DIAG...
2
Station number:
RAZ counters
1
4
5
6
7
1
2
3
8
9
10
Debug values
Counter labels
Retransmit deferral error
Receive buffer DMA overrun error
Repeated command received
Frame size error
Receiver collision abort error
Receiver alignment error
Receiver CRC error
Bad-packet-length error
Bad link address error
Transmit buffer DMA underrun error
0
0
0
0
0
0
Value
0
0
0
0
Elements and functions
This table describes the different zones that make up the configuration screen:
Address Zone
1 common
2 specific
Function
(See : PL7 Micro/Junior/Pro ; Communication applications ;
Volume 1) is used to access the debugging parameters of a Modbus Plus link.
216
TLX DS COM PL7 xxE
Modbus Plus debugging
Modbus Plus debugging screen
Introduction The specific part is split into two windows: l l the Station numbering window, the Debugging value window.
Station numbering l l
The window, identical to that in configuration, is used to select: either the local station, or the remote station.
Debugging value The window looks like this:
4
5
6
7
1
2
3
8
9
10
Debug values
Counter labels
Retransmit deferral error
Receive buffer DMA overrun error
Repeated command received
Frame size error
Receiver collision abort error
Receiver alignment error
Receiver CRC error
Bad-packet-length error
Bad link address error
Transmit buffer DMA underrun error
0
0
0
0
0
0
0
0
Value
0
0
This window displays the different fault counters of a station connected to the
Modbus Plus network.
By default, the screen proposes the default counters of the local station. It is possible to view the fault counters of a local station or of a remote station.
Note: To access the fault counters of a remote station, you must first select the number of the remote station.
the Reset Counters button resets the counters.
TLX DS COM PL7 xxE
217
Modbus Plus debugging
218
TLX DS COM PL7 xxE
Language objects associated with
Modbus Plus communication
17
Introduction
Aim of this section
What's in this
Chapter?
This Chapter introduces the language objects associated with Modbus Plus communication.
This Chapter contains the following Maps:
Topic
Implicit Exchange Language Object
Explicit exchange language object
Explicit exchange management and report
Language objects associated with configuration
Page
TLX DS COM PL7 xxE
219
Modbus Plus language objects
Implicit Exchange Language Object
At a Glance
Bit Objects
This page describes all implicit exchange language objects for Modbus Plus communication, which can be displayed or modified by the application program (PL7
Micro/Junior/Pro ; Communication applications ; Volume 1).
The table below shows the different implicit exchange bit objects.
Object (1) Function
%Ixy.MOD.ERR
Error bit module
%Ixy.i.ERR
Error bit path
Meaning
When this bit is at 1, it indicates a module fault (at least one of the paths is faulty, etc.)
When this bit is at 1, it indicates a line fault.
Key
(1) xy.i address l l l x: corresponds to the rack number y: corresponds to the module number i: corresponds to the path number
Word Objects The table below shows the different implicit exchange word objects.
Object (1)
%IWxy.i.0
Function
Requests
%IWxy.i.1
reserved
%IWxy.i.2 to
%IWxy.i.5
Stations present
Meaning
Status of communication paths
Byte 0: number of communication functions processed simultaneously in client mode l l l l x0 = 1: communication function 1 x0 = 1: communication function 2 x2 = 1: communication function 3 x3 = 1: communication function 4
Byte 1: number of communication functions processed simultaneously in server mode l l l l x8 = 1: communication function 1 x9 = 1: communication function 2 x10 = 1: communication function 3 x11 = 1: communication function 4
-
A bit at 1 indicates the presence of a station (01 to
64).
220
TLX DS COM PL7 xxE
TLX DS COM PL7 xxE
Modbus Plus language objects
Object (1)
%IWxy.i.6
%IWxy.i.7 to
%IWxy.i.9
%IWxy.i.11 à
%IWxy.i.13
%IWxy.i.15
Function
Status bit availability
Status of the specific inputs
Status of the specific inputs
%IWxy.i.10
Status of the specific inputs
New presence of specific inputs
New presence of specific inputs
%IWxy.i.14
New presence of specific inputs
Status bit availability
Status of the specific outputs
%IWxy.i.16 à
%IWxy.i.18
Status of the specific inputs
%IWxy.i.19
Status of the specific inputs
Meaning
Byte 0: the specific inputs of all remote stations are available l l l x0 = 0: the specific inputs are not available x0 = 1: the specific inputs are available x1 to x7: reserved
Byte 1: a bit at 1 indicates the presence of a station that is transmitting specific inputs. Stations 1 to 8.
A bit at 1 indicates the presence of a station that is transmitting specific inputs. Stations 9 to 56.
Byte 0: a bit at 1 indicates the presence of a station that is transmitting specific inputs. Stations 57 to 64.
Byte 1: a bit at 1 indicates the presence of new specific inputs. Stations 1 to 8.
A bit at 1 indicates the presence of new specific inputs. Stations 9 to 56.
Byte 0: a bit at 1 indicates the presence of new specific inputs. Stations 57 to 64.
Byte 1: not used
Byte 0: the specific outputs are available for all remote stations l l l x0 = 0: the specific outputs are not available x0 = 1: the specific outputs are available x1 to x7: reserved
Byte 1: a bit at 1 indicates the presence of a station that is receiving specific outputs. Stations 1 to 8.
A bit at 1 indicates the presence of a station that is receiving specific outputs. Stations 9 to 56.
Byte 0: a bit at 1 indicates the presence of a station that is receiving specific outputs. Stations 57 to 64.
Byte 1: not used
Key
(1) xy.i address l l l x: corresponds to the rack number y: corresponds to the module number i: corresponds to the path number
221
Modbus Plus language objects
Explicit exchange language object
Introduction
Word objects
222
This page describes all the language objects for explicit exchange in Modbus Plus communication that can be displayed or modified by the application program (PL7
Micro/Junior/Pro ; Communication applications ; Volume 1).
The table below shows the different word objects for explicit exchange.
Object (1) Function
%MWxy.MOD.2
Module status
%MWxy.i.2
%MWxy.i.3
%MWxy.i.4
Standard channel status
Specific channel status
Status of link layer
Specific channel status
Peer Cop l l l l l l l l l l l l l l
Meaning l l x0 = 1: defective module x1 = 1: functional error (error between the processor and the module, adjustment or configuration error, …) x2 = 1: terminal block fault (not connected) x3 = 1: self-tests running x4 = 1: reserved x5 = 1: error in hardware or software configuration (the module present is not the one declared in the configuration, the submodules are not compatible) x6 = 1: module missing x7 = 1: error in one of the sub-modules x0 = 1: only station on the network x1 = 1: not used x2 = 1: transmission line error x3 = 1: not used x4 = 1: internal software fault x5 = 1: hardware or software error or no configuration x6 = 1: processor communication error x7 = 1: application fault (double station address)
Byte 0 l l l
= 0: initialization phase
= 3: awaiting token phase
= 4..10: normal status
Byte 0 l l l l l
= 0: station being tested
= 32: normal status
= 64: no token
= 96: only station (idem x0 of %MWxy.i.2)
= 128: two stations have the same number
(idem x7 of %MWxy.i.2)
TLX DS COM PL7 xxE
Object (1)
Key
(1)
Function Meaning
Address xy.i
l l l x: corresponds to the rack number y: corresponds to the module number i: corresponds to the channel number
Modbus Plus language objects
TLX DS COM PL7 xxE
223
Modbus Plus language objects
Explicit exchange management and report
Introduction
Word objects
This page describes all the language objects that manage explicit exchanges (See
: PL7 Micro/Junior/Pro ; Communication applications ; Volume 1).
The table below shows the different word objects for the management of explicit exchanges.
Object (1) Function
%MWxy.MOD.0 Module exchanges in progress
Meaning l l l x0 = 1: reading status in progress x1 = 1: sending of command parameters to the communication module x2 = 1: sending of adjustment parameters to the communication module
%MWxy.MOD.1 Module report
%MWxy.i.0
Channel exchanges in progress l l l l x1 = 0: command parameters received and accepted by the module x2 = 0: adjustment parameters received and accepted by the module l x0 = 1: reading status in progress x1 = 1: sending of command parameters to the communication channel x2 = 1: sending of adjustment parameters to the communication channel
%MWxy.i.1
Channel report l l x1 = 0: command parameters received and accepted by the communication channel x2 = 0: adjustment parameters received and accepted by the communication channel
Key
(1) Address xy.i
l l l x: corresponds to the rack number y: corresponds to the module number i: corresponds to the channel number
224
TLX DS COM PL7 xxE
Modbus Plus language objects
Language objects associated with configuration
Introduction
Internal constants
TLX DS COM PL7 xxE
This page describes all the configuration language objects in Modbus Plus communication that can be displayed by the application program.
The following table describes the internal constants:
Object
%KWxy.i.0
%KWxy.i.1
%KWxy.i.2
Function
Type
Station Address
Peer Cop
Meaning
Byte 0 = 14 for Modbus PLUS communication
Byte 0: station address
Byte 0 = 1: no Peer Cop service
Byte 0 = 2: Peer Cop service
%KWxy.i.4
Timeout behavior
Source address of specific outputs
%KWxy.i.5
Size of specific outputs for nodes 1 and 2
Byte 1 = 1: cleared inputs
Byte 1 = 2: inputs maintained at the last value
%KWxy.i.3
Destination address for specific inputs
Address of first internal word %MW used for receiving specific inputs
Address of first internal word %MW used for sending specific outputs
%KWxy.i.6
Size of specific outputs for nodes 3 and 4
Number of specific output words to be sent to connection point 1 and 2 l l byte 0: connection point 1 byte 1: connection point 2
Number of specific output words to be sent to connection points 3 and 4 l l byte 0: connection point 3 byte 1: connection point 4
...
...
%KWxy.i.3
6
...
Size of specific outputs for nodes 63 and 64
%KWxy.i.3
7
%KWxy.i.3
8
...
Size of specific inputs for nodes 1 and 2
Size of specific inputs for nodes 3 and 4
...
Number of specific output words to be sent to connection points 63 and 64 l l byte 0: connection point 63 byte 1: connection point 64
Number of specific input words to be received by connection points 1 and 2 l l byte 0: connection point 1 byte 1: connection point 2
Number of specific input words to be received by connection points 3 and 4 l l byte 0: connection point 3 byte 1: connection point 4
...
225
Modbus Plus language objects
Object
%KWxy.i.6
8
Function
Size of specific inputs for nodes 63 and 64
%KWxy.i.6
9
Timeout of Peer Cop service
Meaning
Number of specific input words to be received by connection points 63 and 64 l l byte 0: connection point 63 byte 1: connection point 64
Time interval of Timeout l byte 0 = 1 to 100: from 20 ms to 2 s
226
TLX DS COM PL7 xxE
Communication via FIPIO bus
IV
Introduction
Aim of this part
What's in this part?
This part introduces the principles of configuring and using FIPIO bus communication via PL7 software.
This Part contains the following Chapters:
Chapter
18
19
20
21
22
23
24
25
Chaptername
Communication via FIPIO bus
Configuring FIPIO communication
Programming FIPIO communication
Debugging a FIPIO communication
FIPIO communication diagnostics
Language objects associated with FIPIO communication
FIPIO communication standard profiles
FIPIO Agent
Page
TLX DS COM PL7 xxE
227
Communication via FIPIO
228
TLX DS COM PL7 xxE
Communication via FIPIO bus
18
Introduction
Aim of this
Chapter
What's in this
Chapter?
This Chapter introduces communication via the FIPIO bus and its services.
This Chapter contains the following Sections:
Section
18.1
18.2
Topic
Introduction to FIPIO communication
Characteristics
Page
TLX DS COM PL7 xxE
229
General
18.1
Introduction to FIPIO communication
Introduction
Aim of this
Section
What's in this
Section?
This Section provides a summary description of the FIPIO bus and its associated services.
This Section contains the following Maps:
Topic
Introduction
Addressing of language objects for modules remoted on the FIPIO bus
Page
230
TLX DS COM PL7 xxE
General
Introduction
Introduction
Associated manuals
Communication via FIPIO is part of Schneider Automation’s global WORLDFIP package.
FIPIO is a field bus used to delocalize the inputs/outputs of a PLC station and its industrial periphery to be as close as possible to the working part.
The FIPIO protocol uses producer/consumer exchanges (e.g.: common words) and the bus is managed via a bus arbiter.
If you require further information you should consult the following manuals:
Title
FIPIO bus - Reference manual
TSX Micro PLCs - Installation manual
Premium TSX PLCs - Installation manual
Description
Detailed description of the FIPWAY bus and hardware installation
Hardware installation
Hardware installation
Note: Refer to the separate documentation pertaining to each device connected to the FIPIO bus for details on their installation.
TLX DS COM PL7 xxE
231
General
Addressing of language objects for modules remoted on the FIPIO bus
Presentation
Illustration
Addressing for the main bit and word objects for modules remoted on the FIPIO bus l l l is geographical. This means that it depends on: the connection point, the module type (base or extension), the channel number.
Addressing is defined as follows:
% I, Q, M, K X, W, D, F
Symbol Object type Format
\ p.2.c
\
Module/channel address and connection point m
Module number i
Channel number r
Rank
Syntax The table below shows the different elements which constitute addressing.
Family
Symbol
Object type
Format (size)
Module/channel address and connection point p
2 c
Module position m
Channel no.
i
W
D
F
Element Values Meaning
% -
I
Q
M
-
-
-
Image of the module's physical input,
Image of the module's physical output,
This information is exchanged automatically on each cycle of the task to which it is connected.
Internal variable
This read or write information is exchanged at the request of the application.
K
X
-
-
Internal constant
This configuration information is only accessible in read-only.
Boolean
For boolean-type objects, the X may be omitted.
16 bits
32 bits
32 bits
Single length.
Double length
Floating. The floating format used is that of IEEE standard 754-1985
(equivalent IEC 559).
0 or 1
-
Number of the processor's position in the rack.
Channel number of the processor's built-in FIPIO link.
1 to 127 Number of the connection point.
0 or 1 0 : base module, 1: extension module.
0 to 127 or MOD
MOD: channel reserved for management of the module and the parameters shared by all channels.
232
TLX DS COM PL7 xxE
Family
Position
Examples
General
Element Values Meaning r 0 to 255 or ERR
ERR: indicates a module or channel fault.
The table below gives some examples of object addressing.
Object
%MW\0.2.1\0.5.2
%I\0.2.1\0.7
Meaning
Position 2 status word for the image bit of input 5 of the remote input base module located at connection point 1 of the FIPIO bus.
image bit of input 7 of the remote input base module located at connection point 1 of the FIPIO bus.
%Q\0.2.1\1.2
%I\0.2.2\0.MOD.ERR Fault information for the Momentum module located at connection point 2 of the FIPIO bus.
%Q\1.2.3\0.0.ERR
Fault information for channel 0 of module CCX17 located at connection point 3 of the FIPIO bus.
image bit of output 2 of the remote output extension module located at connection point 1 of the FIPIO bus.
0 FIPIO manager TSX 57253
1 TBX LEP 030 0 TBX DES 1622 1 TBX DSS 1622
2 170 FNT 110 01 0 170 AAI 030 00
3 TSX FPP 010 0 T CCX 17 20 F
TLX DS COM PL7 xxE
233
General
18.2
Characteristics
Introduction
Aim of this
Section
What's in this
Section?
This Section introduces the characteristics and constraints of using FIPIO communication.
This Section contains the following Maps:
Topic
Hardware compatibility relating to the bus manager
Software compatibility relating to the bus manager
Software compatibility: Network transparency
Software compatibility: communication with the exterior
Compatibility information relating to TBX devices
Compatibility information relating to Momentum devices
Compatibility information relating to the programming terminal
Compatibility information relating to other devices
FIPIO bus operating mode
Network cycle time: mono task application
Network cycle time: multitasking application
Example of calculating the network cycle times of a multitasking application
Page
234
TLX DS COM PL7 xxE
General
Hardware compatibility relating to the bus manager
General
Availability
Capacity
The binary flow of the bus is 1 Mbits/s and it can extend to a length of up to 15 Km, with four optical or electric repeaters (TSX FP ACC 6).
The FIPIO bus links up to Hirshmann optical transmitters, which allows medium redundancy architectures to be created.
This type of communication is available via built-in links on TSX Premium PLCs from version V3.0 onwards.
The PLCs with built-in FIPIO links are the following: l TSX type processors: l TSX P57 153, l l TSX P57 253, TSX P57 2823, l TSX P57 353, l TSX P57 453, TSX P57 4823.
PCX type processors: l PCX57353.
l l
The bus manager can also be a PLC of the following type:
TSX 47-107 version 5.3 minimum,
S1000.
Processors with built-in FIPIO links are used to manage 128 connection points (TSX
P57 153 = 64) on the bus (addresses 0 to 127).
The bus manager is connected to address 0, and address 63 is reserved for the programming and diagnostics terminal.
These processors have a RAM memory for saving the configurations of devices connected to the bus. This memory has a maximum capacity of 93,320 bytes.
TLX DS COM PL7 xxE
235
General
Software compatibility relating to the bus manager
Explicit exchange limits
Reminders
X-TEL software
Processors with a built-in FIPIO link can simultaneously activate 24 explicit exchange functions.
An exchange request addressed to a FIPIO device can take several MAST task cycles. Thus, it is absolutely necessary to manage the exchange management parameter words for all exchanges of explicit variables including READ_STS
%CH@channel and READ_STS %CH@MOD .
For example, if 24 functions are being processed simultaneously or if 25 functions are triggered in the same task cycle, the 25th, or any new function, will not be served and will terminate in error.
For a READ_STS exchange, if the twenty-fifth exchange is impossible, the report signals a communication fault in the word: %MW\p.2.c\m.v.2.
For WRITE_CMD , READ_PARAM , WRITE_PARAM , RESTORE_PARAM exchanges, the report signals a communication fault in the word %MW\p.2.c\m.v.1. A likely cause is a lack of system resources to provide the service.
The system word %SW155 contains the number of explicit exchanges in progress.
Bit %SW116: x2 switches to 1 if the maximum number of simultaneous explicit exchanges is reached or exceeded.
When the bus manager is a series 7 PLC (TSX 47-107), the configuration of the bus and the manager is performed by the X-TEL software workbench, of version 6.0 or later.
236
TLX DS COM PL7 xxE
General
Software compatibility: Network transparency
Introduction
Transparency restrictions
Exchanges from a remote station to the FIPIO bus or vice versa are possible under certain conditions.
Inter-station communication with FIPIO is only available if the bus arbiter is a TSX
Premium PLC, of at least version V3.3.
Exchanges from a third-party device to a PLC connected as a FIPIO slave are only possible if the PLC is a TSX Premium of V3.3 at least. Communication with a TSX
Micro PLC is not possible.
A FIPIO agent does not communicate with the exterior.
Only one programming terminal can be connected to the FIPIO bus. If it is present in the configuration, it must be connected to the default connection port (63).
This programming terminal cannot be used to load the application onto the FIPIO bus arbiter.
TLX DS COM PL7 xxE
237
General
Illustration The following illustration shows the different exchanges possible between a FIPIO bus and a network or another bus.
FIPAWAY, ETHERNET, Uni-telway, ...
TSX Premium V3.3
Third party device
0
TSX Micro
TSX Premium V3.3
Magelis
63
Programming terminal
238
TLX DS COM PL7 xxE
General
Software compatibility: communication with the exterior
Introduction To communicate from a station connected to the FIPIO bus to an outside device, the transmitter station must address the master PLC and not the destination device
(requests are not routed directly).
Example
Note: The master PLC application transfers these requests to the destination device.
In the following example, an exchange from the FIPIO bus to the Uni-telway bus has to be performed. For a transfer in the opposite direction, the procedure is identical.
TSX Premium master, Serie 7
Step 2
0
Uni-telway
Step 1
6
Ad0 = 1
Ad1 = 2
Ad2 = 3
63
Step 1
Step 2
The transmitter station, connected to connection port 6 on FIPIO, sends the request to the master PLC. The destination address is the master PLC address.
WRITE_VAR (ADR#\6.1.0\SYS, %MW,0,10, %MW:10, %MW100:4)
The master PLC generates the report.
When the master PLC application receives the request from the transmitter station, it directs it to the destination device in accordance with the Uni-telway protocol.
WRITE_VAR (ADR#0.0.1, '%MW', 100, 10, %MW10:10, %MW40:4)
The report is sent to the master PLC.
TLX DS COM PL7 xxE
239
General
Compatibility information relating to TBX devices
Introduction
Rules of use
Addressing
The following compatibility information relates to: l l the addressing supported by the different connectable devices, the memory space that the devices take up in the configuration RAM.
If a device linked to a connection port is modular, it must be homogeneous at an application-specific level. Discrete base and extension or analog base and extension (not a mixture of discrete and analog).
The device is only controlled by one PL7 task (FAST or MAST) (no assigning of channel groups of the same TBX to different tasks).
The FIPIO addressing depends on the type of device:
Types of device
Compact TBXs
Sealed TBXs
Modular TBXs
TBX SAP 10
FIPIO addresses
1...31
1...62, 64...127
1...62, 64...127
1...62, 64...127
Comments
TBX C•
TBX E•
TBX LEP 020, TBX LEP 030
AS-i gateway
Maximum configuration
The number of modules of the same reference connected to the FIPIO bus in a configuration is limited. The values in the table below are expressed in bytes.
Module Base
AES 200, ASS 400
AMS 620
1332
1332
1152
Extension Maximum number of connection points
TSX P57
153
TSX P57
253/2823/
353
TSX P57
453/4823
272
528
For 2 or 4 channels
62 70
For 8 channels
59 59
125
126
-
For 10 or 12 channels
50 50
31 31
114
31 CEP 1622, CSP 1622,
CSP 1625
DES •••, DMS •••, DSS •••
SAP 10
1152
1088
144
-
62
52
81
52
126
117
240
TLX DS COM PL7 xxE
General
Compatibility information relating to Momentum devices
Introduction
Rules of use
Addressing
Maximum configuration
The following compatibility information relates to: l l the addressing supported by the different connectable devices, the memory space that the devices take up in the configuration RAM. installing Momentum devices on FIPIO is only possible with the communication module: 170 FNT 110 01.
A Momentum device can have addresses from 1 to 62 or 64 to 127.
The number of modules of the same reference connected to the FIPIO bus in a configuration is limited. The values in the table below are expressed in bytes.
Module Base
ADI, ADM, ADO
ARM 370 30
ANR 120 90
AAI 520 40 00
AMM 090 00, AAI 030 00,
AAO 120 00, AAO 921 00
AAI 140 00
FED C32
FED C32P
FED M32
FED M32P
FRD C2
FSD C8
FSD C8P
FSD M8
FSD M8P
2304
1280
2304
1424
2448
832
896
1808
1040
1952
832
832
832
1808
1808
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Extension Maximum number of connection points
TSX P57
153
TSX P57
253/2823/
353
TSX P57
453/4823
62
62
62
52
52
98
98
98
52
52
98
98
98
98
98
38
62
62
52
40
62
40
62
62
48
38
113
105
52
40
73
40
66
90
48
87
126
126
117
92
126
92
126
126
109
TLX DS COM PL7 xxE
241
General
Compatibility information relating to the programming terminal
Introduction
Rules of use l l
The following compatibility information relates to: the addressing supported by the different connectable devices, the memory space that the devices take up in the configuration RAM.
A programming terminal fitted with the TSX FPC 10 card or the PCMCIA card TSX
FPP 20 must be connected to the FIPIO address 63.
PL7 operates in connected mode with the FIPIO manager PLC.
If the manager PLC has an application in which one or several agent devices are l l configured:
PL7 communicates with the TSX Micro/Premium FIPIO agent PLCs.
MMI 17 communicates with the CCX-17.
It is not possible to download a PL7 application to the manager from a programming terminal. However, it is possible to download a PL7 application to a FIPIO agent
PLC.
242
TLX DS COM PL7 xxE
General
Compatibility information relating to other devices
Introduction
Addressing
The following compatibility information relates to: l l the addressing supported by the different connectable devices, the memory space that the devices take up in the configuration RAM.
The FIPIO addressing depends on the type of device:
Types of device
ATV-16/58/66
CCX 17
Magelis
FipConnect products
FIPIO addresses Comments
1...62
The speed controllers are fitted with a TSX
FPP 10 card, of version V1.8 or later.
1...62
The consoles have to be of version V2.4 or later and are fitted with the TSX FPP 10 card of version V1.8 or later.
1...62
1...62, 64...127
The consoles are fitted with a TSX FPP 10 card of version V1.8 or later.
apart from limitations specific to the product used
Maximum configuration
The number of modules of the same reference connected to the FIPIO bus in a configuration is limited. The values in the table below are expressed in bytes.
Module Base
ATV 16, ATV 58, ATV 66
CCX 17
EEF 08D2, EEF 16D2
ESF 08T22 EMF 16DT2
FED C32
FED C32P
FED M32
FED M32P
FRD C2
FSD C8
FSD C8P
1952
1952
832
1808
1280
2304
1424
2448
832
896
1808
-
-
-
-
-
-
-
-
-
-
-
Extension aximum number of connection points
TSX P57
153
TSX P57
253/2823/
353
TSX P57
453/4823
48
4
62
52
48
4
98
52
62
4
98
98
62
40
62
38
62
62
52
73
40
66
38
113
105
52
126
92
126
87
126
126
117
TLX DS COM PL7 xxE
243
General
Module
FSD M8
FSD M8P
Micro Premium
Base
1040
1952
1424
-
-
Extension aximum number of connection points
-
62
48
62
90
48
62
126
109
62
244
TLX DS COM PL7 xxE
General
FIPIO bus operating mode
Introduction The FIPIO bus operating mode is linked to the processor operating mode and to the physical state of the bus.
If the number of physical errors detected by the processor is endangering the nominal operation of the devices connected to the bus, the processor stops all bus activity. In this case, the devices connected apply the fallback values to the inputs/ outputs.
Operating mode The operating mode is as follows:
Phase
1
2
3
4
5
6
Description
Cold restart of the processor with a FIPIO application: the bus is started automatically; the I/Os are monitored and commanded.
Downloading an FIPIO application: the bus is started automatically; the inputs/ outputs are monitored and commanded.
If the processor detects serious physical errors, the FIPIO bus is stopped automatically. The connected devices apply the fallback values; the processor no longer monitors the inputs/outputs. A serious physical error is for example the disconnection of the line plug, the disconnection of the FIPIO terminal block on the processor, etc…
Following an automatic stop (serious errors detected by the processor): l the bit %SW144:x2 is set; the processor periodically carries out a restart attempt, trying to monitor and command the inputs/outputs of the connected devices. This is automatic mode.
l the bit %SW144:x2 is cleared; to restart the bus, there a user action must be performed via the program or via the programming terminal. Set bits
%SW144:x0 and %SW144:x1 to 1. This is manual mode.
Warm restart: the bus is restarted automatically if it has not been stopped voluntarily by an action on the system word %SW144 bits 0 and 1. The bus is returned to the state it was in before the power outage.
If %S0 = 1 the system words are initialized, and if the bus had been stopped, it is restarted.
TLX DS COM PL7 xxE
245
General
Information on manual mode
If %SW144:x0 is set to 0 (via the programming terminal or via the program) the production/consumer function (PC) stops. No more variables or messages are exchanged on the bus.
If %SW144:x1 is set to 0 (via the programming terminal or via the program) the bus arbiter function (BA) stops. There is no more scanning of variables or messages on the bus.
To completely and voluntarily stop the activity on the FIPIO bus, it is necessary to simultaneously set bits 0 and 1 of the system word %SW144 to 0 via the programming terminal or via the program.
Information on automatic mode
If the FIPIO bus is stopped without a voluntary action on the system word %SW144, this means that the processor has detected physical errors which prevent the nominal operation of the bus and the connected devices.
In this case, and only in this case, , if bit %SW144:x2 is set to 1 (automatic start), the processor will make periodic and automatic attempts to restart the exchanges on the bus.
If bit %SW144:x2 is at 0 following the stopping of the bus owing to physical errors, it is necessary to reset bits %SW144 x:0 and %SW144 x:1 via the program or via the programming terminal in order to restart the FIPIO bus. In this case, the bus will restart if, and only if, the physical error which caused the stop has
disappeared.
Example if bit %SW144 x:2 = 1 on disconnection/reconnection of the processor FIPIO terminal block, the bus will be restarted automatically.
The devices will be monitored once again and will be able to apply the program values.
if bit %SW144 x:2 = 1 on disconnection/reconnection of the processor FIPIO bus, the connected devices on the bus will be neither monitored, nor will they be able to apply the program values.
The devices will be monitored once again if the user sets bits %SW144:x0 and
%SW144:x1 = 1.
246
TLX DS COM PL7 xxE
General
Network cycle time: mono task application
Introduction
Calculation of the network cycle time
The network cycle time for a mono task application is calculated for the following l l configuration: the length of the bus is 1 Km, the values corresponding to the reversal and silence times and the bandwidths are default values (automatic mode).
For an application which has all the devices configured in the same task, the value of the network cycle time of the task, in milliseconds, is obtained, for information purposes only, by the following formula:
TCR_TASK= 1,45 +
Σ(
K x number of equipments of the same family)
Value of coefficient K
Coefficient K will be defined as follows:
1,5
1,5
0,6
1,5
0,4
0,6
1,5
0,6
0,6
0,6
0,6
Coefficient K
0,5
0,9
0,4
Family
TBX
TBX
Momentum
Momentum
ATV-16
ATV-58
CCX 17
CCX 17-32
TSX 37/57
AS-i gateway
Magelis
STD_P
STD_P
STD_P
Device
Discrete
Analog
Discrete
Analog
All
All
All
All
All
TSX SAP 10
All
FRD
FSP
FED
TLX DS COM PL7 xxE
247
General
Example l l
The configuration of the example is as follows:
All the elements are configured in the MAST task in the application.
l l
The configuration comprises: l 10 discrete TBXs,
11 analog TBXs,
12 discrete Momentums.
The calculation of the cycle time for the Mast task is as follows:
TCR_MAST = 1.45 + ((0.5 x 10) + (0.9 x 11) + (0.4 x 12)) = 21.15 ms
The network cycle time is about 21 ms.
248
TLX DS COM PL7 xxE
General
Network cycle time: multitasking application
Introduction
Convention
For a multitasking application with two periodic tasks, and if the devices are configured in each of the tasks, the value of the network cycle times depends on the configuration of the different tasks.
The cycle time values calculated with the following algorithm are the maximum values. The actual values are less than or equal to these values.
The following table shows all the parameters involved in the calculation of the network cycle time.
Parameter
P max
P min
T max
T min
R
NE max
NE min
NE_Equip
TCR_T max
TCR_T min
Definition
Value of the largest task period (MAST or FAST)
Value of the smallest task period (MAST or FAST)
Task with period P max
Task with period P min
Ratio between the periods (This ratio must be a whole number; it will be rounded off to the nearest whole number if necessary).
Number of devices from the same family configured in T max
Number of devices from the same family configured in T min
Equivalent number of devices from the same family
Network cycle time for the task T max
Network cycle time for the task T min
TLX DS COM PL7 xxE
249
General
Calculation algorithm
Value of coefficient K
To calculate the network cycle time, the algorithm is as follows:
Stage
1
Description
Calculation of
2
3
4
R
R =
Pmin
Calculation of NE_Equip (for each device family)
NE_Equip =
( (
R
×
NEmin
)
+ NEmax
)
Calculation of
TCR_T max
TCR_Tmax = 1,45 +
å
(
K
×
NE_Equip
)
Calculation of
TCR_T min
TCR_Tmin =
R
Coefficient K will be defined as follows:
1,5
1,5
0,6
1,5
0,4
0,6
1,5
0,6
0,6
0,6
0,6
Coefficient K
0,5
0,9
0,4
Family
TBX
TBX
Momentum
Momentum
ATV-16
ATV-58
CCX 17
CCX 17-32
TSX 37/57
AS-i gateway
Magelis
STD_P
STD_P
STD_P
Device
Discrete
Analog
Discrete
Analog
All
All
All
All
All
TSX SAP 10
All
FRD
FSP
FED
250
TLX DS COM PL7 xxE
General
Interpretation of the results
To refresh the inputs/outputs on the bus, the following constraints are imposed: l For the periodic tasks in controlled mode, the network cycle time of the task must be less than the task period.
l For the periodic tasks in free mode, the network cycle time of the task must be less than the task watchdog.
TLX DS COM PL7 xxE
251
General
Example of calculating the network cycle times of a multitasking application
Introduction
Convention
Algorithm
The configuration of the example is as follows: l l
Task periods: l l
MAST: 60 ms
FAST: 15 ms
The configuration comprises: l 6 discrete TBXs configured in the MAST task and 4 discrete TBXs configured in the FAST task, l l l
6 analog TBXs configured in the MAST task and 4 analog TBXs configured in the FAST task,
6 discrete Momentums configured in the MAST task and 4 discrete
Momentums configured in the FAST task,
6 analog Momentums configured in the MAST task and 4 analog Momentums configured in the FAST task, l l l
Depending on the configuration, the application of conventions involves:
P max
= 60 and P min
= 15
T max
= T
MAST
and T min
= T
FAST
TCR_T max
= TCR_T
MAST
and TCR_T min
= TCR_T
FAST
The following table shows the algorithm:
Stage
1
2
3
4
Description
Calculation of R
R = 60 / 15 = 4
Calculation of the equivalent number of devices
NE_TBX_TOR = (R * 4 + 6) = 22
NE_TBX_ANA = (R * 4 + 6) = 22
NE_MOMENTUM_TOR = (R * 4 + 6) = 22
NE_MOMENTUM_ANA = (R * 4 + 6) = 22
Calculation of the network cycle times TCR_T
MAST
TCR_T
MAST
= 1.45 + ((0.5 * 22) + (0.9 * 22) + (0.4 * 22) + (0.6 * 22))
TCR_T
MAST
= 54.25 ms
Calculation of the network cycle times TCR_T
FAST
TCR_T
FAST
= 54.25 / 4
TCR_T
FAST
= 13.56 ms
252
TLX DS COM PL7 xxE
Conclusions
General
The network cycle times of each equal: l l
TCR_T
MAST
= 55 ms,
TCR_T
FAST
= 14 ms.
The time period for MAST and FAST tasks are sufficient to refresh the inputs/ outputs.
TLX DS COM PL7 xxE
253
General
254
TLX DS COM PL7 xxE
Configuring FIPIO communication
19
Introduction
Aim of this
Chapter
What's in this
Chapter?
This chapter describes the Configuration process during set-up of FIPIO communication.
This Chapter contains the following Sections:
Section
19.1
19.2
19.3
19.4
19.5
Topic
General information on configuration
FIPIO bus configuration
Configuration of devices on the FIPIO bus
Input/output management by the PL7 tasks
Confirmation of the FIPIO bus configuration
Page
TLX DS COM PL7 xxE
255
FIPIO Configuration
19.1
General information on configuration
Configuration mode
Introduction
Methodology
The creation of an application to implement a FIPIO bus requires the configuration of several elements via the PL7 software.
The following methodology reviews the different phases involved in configuring the
FIPIO bus:
Configuring points of connection and bus properties
This phase is used to define the type of device connected to the bus, bus management (e.g.: length, bandwidth, etc.
Configuring each device connected to the bus.
This phase is used to configure each device (e.g.: PLC task managing devices, inputs, outputs, etc.).
Adapting PL7 tasks according to the bus topology.
This phase is used to define the management of input/outputs on the bus by PL7 tasks (e.g.: cyclic or periodic task, controlled or free mode, etc.
256
TLX DS COM PL7 xxE
19.2
FIPIO bus configuration
Introduction
Aim of this
Section
What's in this
Section?
This section introduces the FIPIO bus configuration principles.
This Section contains the following Maps:
Topic
How to access the FIPIO configuration screen
FIPIO bus configuration screen
How to add a device on to the bus
How to modify/delete/move/duplicate a bus device
How to access the FIPIO bus properties screen
FIPIO bus properties configuration screen
Properties of the FIPIO bus: General tab
Properties of the FIPIO bus: Expert tab
Expert tab: manual mode
FIPIO Configuration
Page
TLX DS COM PL7 xxE
257
FIPIO Configuration
How to access the FIPIO configuration screen
Introduction
How to access the link
This operation describes how to access the configuration via the the TSX Premium
PLCs provided with a built-in link.
The following table shows the procedure for accessing the FIPIO link:
Step
1
2
Action
Access the hardware configuration screen
Double click on the FIPIO connector.
258
TLX DS COM PL7 xxE
FIPIO Configuration
FIPIO bus configuration screen
Introduction
Illustration
This screen is used: l l to register devices which are connected to the bus, to parameter the bus properties.
The screen dedicated to FIPIO communication looks like this:
FIPIO Configuration
TSX 57252 V3.0
Bus length: 0 15 km
1
Logical address Communicator Standard module Extension module
0 Fipio manager TSX 57252
63
Privileged terminal
127
Elements and functions
Zone
Bus length
Logical address
Communicator
Standard module
Extension module
This table describes the different areas that make up the configuration screen:
Function
This cursor is used to adjust the bus length. The default value is 1 Km.
This zone defines the address for each device.
This zone specifies the type of device which enables communication between the manager and the standard device.
Where the standard device has no need for a communicator, this zone is empty.
This zone specifies the standard device connected to the bus.
This zone gives information on whether an extension is associated to the standard device.
Grayed out rectangles on the bus indicate the two reserved addresses: l l
0 for the bus manager,
63 for the privileged terminal.
The available connection points are indicated by a small circle and dotted lines.
TLX DS COM PL7 xxE
259
FIPIO Configuration
How to add a device on to the bus
Procedure This operation is used to logically add a device connected to the FIPIO bus.
Step
1
2
Action
Access the FIPIO configuration screen.
Double click on the logic address of the connection point at the place where the module must be connected (available addresses ranging from 1 to 62 and from
64 to 127, addresses 0 and 63 being reserved by the system).
Result: the Add/Modify a device screen appears.
Add/Modify a device
Connection point
Connection point number
Comment
TBX DMS 1625
1 OK
Cancel
Families
ATV-16
ATV-58
CCX-17
CCX17-32
MAGELIS
MOMENTUM 1.0
PASSERELLE 1.0
SIMULATION 1.0
STD_P 1.0
TBX
TSX
1.0
1.0
1.0
1.0
1.0
1.0
1.0
Standard module
TBX DES 1633
TBX DES 16C22
TBX DES 16F22
TBX DES 16S04
TBX DMS 1025
TBX DMS 1625
TBX DMS 16C22
TBX DMS 16C222
TBX DMS 16P22
Extension module
TBX7 EMB. 16E 48VCC
TBX7 EMB. 16E CF 24VCC
TBX7 EMB. 16E RAP 24VCC
TBX7 EMB. 16E 120 VCA
TBX7 EMB. 8E/2SR 24VCC
TBX7 EMB. 8E/8SR 24VCC
TBX7 EMB. 8E+8SS 0,5A CF
TBX7 EMB. 8E+8SS 2A CF
TBX7 EMB. 8E+8E/S 0,5A
Communicator
TBX LEP 020 TBX7 MOD.COM.FIP 24/48V
TBX LEP 030 TBX7 MOD.COM.FIP TOR+ANA
260
3
4
5
6
7
Enter the connection point number which corresponds to the address.
By default, the PL7 software offers the first consecutive address which is free
Add a comment to the device connected to the connection point.
This field has a maximum length of 80 characters and is optional.
In the Family field, select the type of equipment to be connected to the bus.
Select the standard module and/or the extension module.
In the Communicator field, select the type of element enabling communication on the FIPIO bus.
For certain types of device, this window does not appear.
TLX DS COM PL7 xxE
TLX DS COM PL7 xxE
FIPIO Configuration
Step
8
Action
Confirm with Ok.
Result: the module is registered.
FIPIO Configuration
TSX 57252 Bus length: 0
5
Logical address Communicator
15 km
Standard module
0 Fipio managerTSX 57252
Extension module
1 TBX LEP 020 0 TBX DSS 1622 1 TBX DES 1622
2 TBX LEP 030 0 TBX AES 400
261
FIPIO Configuration
How to modify/delete/move/duplicate a bus device
Procedure for modifying a device
This operation is used to logically modify a device connected to the FIPIO bus.
Step
1
2
3
4
Action
Access the FIPIO configuration screen.
Double click on connection point corresponding to the device which is to be modified.
Modify the component parts of the device: l l l l standard module, extension module, the communicator, the comment.
It is not possible to modify the family or the connection point number.
Confirm with Ok.
Procedure for deleting a device
This operation is used to logically delete a device connected to the FIPIO bus.
Step
1
2
3
4
Action
Access the FIPIO configuration screen.
Select the connection point to be deleted.
A dotted line square surrounds the selected connection point.
Select the Edit
→
Delete the device command.
Confirm the deletion with Yes.
262
TLX DS COM PL7 xxE
FIPIO Configuration
Procedure for moving a device
Moving a device is not a physical move on the bus but a logic change of the device address. This involves modifying the address of I/O objects in the program and moving variables associated to these objects. On global confirmation of the configuration, the application program will be modified automatically to match the move.
Step
1
2
3
4
5
Action
Access the FIPIO configuration screen.
Select the connection point to be moved.
A dotted line square surrounds the selected connection point.
Select the Edit
→
Move a device command.
Supply the destination connection point number.
Confirm the move with the Ok button.
Procedure for duplicating a device
This function is similar to the function to move a device.
Step
1
2
3
4
5
Action
Access the FIPIO configuration screen.
Select the connection point to be moved.
A dotted line square surrounds the selected connection point.
Select the Edit
→
Duplicate a device command.
Supply the destination connection point number.
Confirm the move with the Ok button.
TLX DS COM PL7 xxE
263
FIPIO Configuration
How to access the FIPIO bus properties screen
Introduction
How to access the link
This operation describes how to access the bus properties screen via TSX Premium
PLCs with an integral link.
The following table shows the procedure:
Step
1
2
3
Action
Access the FIPIO configuration screen.
Right-click at the bottom of the FIPIO configuration screen.
Select the command FIPIO Bus Properties from the contextual menu.
264
TLX DS COM PL7 xxE
FIPIO Configuration
FIPIO bus properties configuration screen
Introduction
Illustration
On a FIPIO bus, a single PLC allows the exchange of inputs/outputs; this is the bus arbiter. It manages the bus accesses of each connected device.
The screen attached to the properties therefore allows you to adapt the management parameters according to the devices which are connected.
The screen dedicated to the properties of the FIPIO bus looks like this:
FIPIO bus properties
General Expert
Profile
Fip
World Fip
Bus length
0
5
15 km
OK Cancel Apply Help
Elements and functions
This table describes the different areas that make up the configuration screen:
Tab
General
Expert
Function
This tab is used to: l l choose the type of profile managed by the bus arbiter, adjust the bus length.
This tab is used for choosing the management mode. In the case where the management is manual, it is used to further adjust the management parameters according to the devices which are connected.
TLX DS COM PL7 xxE
265
FIPIO Configuration
Properties of the FIPIO bus: General tab
Introduction
The profile
With this tab, you can access two types of information: l l the profile, the bus length.
The profile is chosen according to the devices which are connected to the FIPIO bus. It can be in either of two versions: l l
FIP: l This profile is chosen by default.
l It is compatible with all the devices of Schneider and partners.
WorldFip: l The selection of this mode allows you to operate the FIPIO bus in accordance with the EN 50170 standard.
l l
Note: The WorldFip profile mode can be used with the following restrictions: no TSX FP ACC6 or TSX FP ACC8 repeaters, use of TBX LEP 020 version 1.4 minimum and TBX LEP 030 version 1.2 minimum, l use of the PCMCIA TSX FPP 10 card, version 1.8 minimum.
The bus length With this cursor you can increase or decrease the bus length. The default value is 1
Km and the adjustment increment is 1 Km.
This length must be adjusted because it is taken into account in the calculation of the propagation time for the signals on the bus and consequently in the calculation of the network cycle times.
Note: At each modification of the length of the FIPIO bus, all the connected devices must be powered off, then on after the new application has been downloaded (in the PLC).
266
TLX DS COM PL7 xxE
FIPIO Configuration
Properties of the FIPIO bus: Expert tab
Introduction With this tab, you have access to the management mode concerning the calculation l l of: reversal and silence time, bandwidths.
Note: At each modification of the parameters below, all the connected devices must be powered off, then on after the new application has been downloaded (in the PLC).
The automatic mode
Note: This mode is advocated.
The reversal and silence times and the bandwidths cannot be modified. They are calculated according to the bus parameters and device configuration data.
The manual mode
CAUTION
No monitoring is carried out in manual mode. Modifying these parameters can cause the device connected to the bus not to work.
Failure to observe this precaution can result in injury or equipment damage.
This mode is used to enter the reversal and silence times and the bandwidths.
It is mainly reserved for specific applications requiring these values to be modified
(example: use of Hirschmann transmittors).
TLX DS COM PL7 xxE
267
FIPIO Configuration
Expert tab: manual mode
Introduction By selecting the manual mode, you have access to the following information: l l the reversal and silence times, the aperiodic bandwidths.
Aperiodic variables
Parameters
Silence time delay T0
Reversal time TR
The following table gives a description of the times:
Description
This defines the maximum time between the transmission of the last byte of a frame and the transmission of the first byte of the following frame.
This time is expressed in micro-seconds.
Its value must be greater than the reversal time TR and less than 255.
This defines the minimum time between the transmission of the last byte of a frame and the transmission of the first byte of the following frame.
This time is expressed in micro-seconds.
Its value must be greater than or equal to 1 and less than the silence time T0.
Aperiodic bandwidths
Parameters
Aperiodic variables
Messaging
There are two types of exchange on a FIPIO bus: l l exchanges of cyclic variables which are reserved for the process data, exchanges of aperiodic variables which concern the configuration of connected devices, the adjustment and the messaging.
A decrease or increase of the bandwidth of the aperiodic exchanges (Variables and
Messages) slows down or accelerates the output of the configuration or adjustment variables which can circulate on the bus. The same applies to a decrease or increase of the aperiodic bandwidth of the messaging facility.
The following table gives a description of the aperiodic bandwidths:
Description
This defines the output of the aperiodic variables which can circulate on the bus.
This bandwidth is expressed in Kbits/s.
Its value can be adjusted from 1 to 200 Kbits/s.
This defines the output of the aperiodic messages which can circulate on the bus.
This bandwidth is expressed in Kbits/s.
Its value can be adjusted from 1 to 200 Kbits/s.
Note: An increase in the aperiodic bandwidth increases the network cycle time.
268
TLX DS COM PL7 xxE
19.3
FIPIO Configuration
Configuration of devices on the FIPIO bus
Introduction
Aim of this
Section
What's in this
Section?
This section introduces the configuration principles for FIPIO bus devices.
This Section contains the following Maps:
Topic
How to access the FIPIO configuration screen
Configuration screen of a FIPIO device
How to access the different parameters according to device type
Page
TLX DS COM PL7 xxE
269
FIPIO Configuration
How to access the FIPIO configuration screen
Introduction
How to access the link
When a device has been registered, it is possible to access its configuration as in the case of a rack module.
This screen is used to select the task which exchanges the inputs/outputs: FAST or
MAST, to modify the configuration or adjustment parameters specific to the module.
The following table shows the procedure for accessing the configuration of a device on FIPIO:
Step
1
2
Action
Access the FIPIO configuration screen
Double click on the standard module to be configured.
270
TLX DS COM PL7 xxE
FIPIO Configuration
Configuration screen of a FIPIO device
Introduction
Illustration
This screen, split into several areas, is used to register the communication channel and to configure the parameters of the device selected for a FIPIO communication.
The screen looks like this:
1
2
FSD M8 P [FIPIO18 MODULE 0]
Configuration
Designation: EQP STD MOD 8MP
3
4
Channel
Local configuration
Task: MAST
Default configuration
Base
Decimal
Parameters
%KW\0.2.18\0.0.0
%KW\0.2.18\0.0.1
%KW\0.2.18\0.0.2
%KW\0.2.18\0.0.3
%KW\0.2.18\0.0.4
%KW\0.2.18\0.0.5
%KW\0.2.18\0.0.6
%KW\0.2.18\0.0.7
Symbol Value
0
0
16#8040
16#0
0
0
0
16#4
Elements and functions
This table describes the different areas that make up the configuration screen:
Address Zone
1
2
3
4
Title bar
Module
Description
This zone defines the module reference and its physical position in the module.
This zone is used to input information with the aid of dropdown lists: l parameter type: l l the Configuration mode, the Adjustment mode (which can be accessed by certain device types), l l the Debugging mode (can only be accessed in online mode).
channel type (inputs or outputs) when the designated device has inputs and outputs.
Communication channel This zone is used to assign devices to either the MAST task or the FAST task, with the aid of a dropdown list.
Some device types have access to a Local configuration check box. If the box is checked off, the channel parameters can not be accessed.
Channel parameters This zone is used for device parametering. According to certain device types, this zone can not be accessed.
TLX DS COM PL7 xxE
271
FIPIO Configuration
Note: For further information on configuration parameters, adjustment parameters and debugging parameters, refer to the documentation specific to each device.
272
TLX DS COM PL7 xxE
FIPIO Configuration
How to access the different parameters according to device type
How to access the inputs/ outputs
The following procedure provides information on how to access the input or output parameters of a module. It is enabled in both offline and online mode.
Step
1
2
Action
Access the configuration screen of a FIPIO device.
Select input part or output part from the module zone’s dropdown list.
How to adjust the configuration parameters
The following procedure describes how to modify the adjustment parameters of a module. It is enabled in both offline and online mode.
Step
1
2
3
4
5
6
Action
Access the configuration screen of a FIPIO device.
Select adjustment mode from the module zone’s dropdown list.
Select the cell relating to the entry parameter.
Enter the parameter.
Enable by clicking on Input.
Enable the assignment.
How to assign a module to a PL7 task
The following procedure describes how to assign a module to a PL7 task. It is only enabled in offline mode.
Step
1
2
3
Action
Access the configuration screen of a FIPIO device.
Select MAST
→
or FASTTask from the dropdown list.
Enable the assignment.
TLX DS COM PL7 xxE
273
FIPIO Configuration
19.4
Input/output management by the PL7 tasks
Introduction
Aim of this
Section
What's in this
Section?
This Section introduces the configuration principles for PL7 tasks in FIPIO mode.
This Section contains the following Maps:
Topic
How to access PL7 task configuration in FIPIO mode.
Configuration screen of a FIPIO processor
FIPIO input/output management using PL7 tasks
Page
274
TLX DS COM PL7 xxE
FIPIO Configuration
How to access PL7 task configuration in FIPIO mode.
Introduction
Procedure
FIPIO Bus and device configuration modifies the task network cycle times in accordance with the input/output updating of each PL7 task.
These modifications can result in constraints on: l task type (cyclic or periodic), as well as its execution time and watchdog, l FIPIO input/output processing in relation to the task cycle (controlled or free).
The PL7 software is used then to manage the inputs/outputs according to the MAST or FAST tasks and their network cycle time.
The following table shows the procedure for accessing the MAST and FAST tasks in FIPIO mode:
Step
1
2
Action
Access the hardware configuration screen
Double click on the processor.
TLX DS COM PL7 xxE
275
FIPIO Configuration
Configuration screen of a FIPIO processor
Introduction
Illustration
This screen, split into various areas, is used to manage the FIPIO inputs/outputs l l l l according to: task type (MAST or FAST), use type (cyclic or periodic) and duration, watchdog, task network cycle time.
Only the section relating to FIPIO mode is presented below.
The screen looks like this:
TSX 57252 [RACK 0 POSITION 1]
Configuration
Designation: TSX P processor 57252
Operating Mode
Run/Stop input
Auto start in Run
%MWi Reset on cold restart
Memory Card
None
Tasks
MAST
Cyclic
Periodic
Watchdog
FAST
Period:
Watchdog
250
0 ms ms
FIPIO Mode
Network cycle time (calculated)
Controlled
Free
4 ms
100
5 ms ms
FIPIO Mode
cycle
time (calculated)
Controlled
Free
0 ms
The FIPIO Mode window
You can access two types of information via the FIPIO Mode window: l l
Mode (controlled or free): is used to link input/output updating to the task cycle.
Network cycle time (calculated): this time represents the network cycle time associated with a task.
276
TLX DS COM PL7 xxE
FIPIO Configuration
FIPIO input/output management using PL7 tasks
Introduction The FIPIO input/output management modes are dependent upon the type of task execution (cyclic or periodic).
Controlled FIPIO mode
This mode can only be accessed via a PL7 task declared as periodic.
Tasks
MAST
Cyclic
Periodic
Watchdog
FAST
Period:
Watchdog
150
250 ms ms
FIPIO Mode
Network cycle time (calculated)
Controlled
Free
4 ms
100
5 ms ms
FIPIO Mode
Network cycle time (calculated)
Controlled
Free
0 ms
In this mode, input/output refreshing is correlated with the task period. The system guarantees input/output updating during one period only. Only the inputs/outputs associated with this task are refreshed.
Choosing this mode imposes the following constraint:
The PLC task period (MAST or FAST) must be greater than or equal to the network cycle time
Free FIPIO mode This mode can be accessed via a periodic or cyclic declared PL7 task.
Tasks
MAST
Cyclic
Periodic
Watchdog
FAST
Period:
Watchdog
250
0 ms ms
FIPIO Mode
Network cycle time (calculated)
Controlled
Free
4 ms
100
5 ms ms
FIPIO Mode
Network cycle time (calculated)
Controlled
Free
0 ms
In this mode, no constraints are imposed on the task period. The PLC task period
(MAST or FAST) can be less than the network cycle time.
In this case, the task can be carried out without updating the inputs/outputs.
Selecting this mode provides the possibility of having the shortest possible task times for an application where the rate is critical.
TLX DS COM PL7 xxE
277
FIPIO Configuration
19.5
Confirmation of the FIPIO bus configuration
Introduction
Aim of this
Section
What's in this
Section?
This Section introduces the main instances of FIPIO bus configuration refusal.
This Section contains the following Maps:
Topic
Confirming the configuration
Confirmation refused, examples
Page
278
TLX DS COM PL7 xxE
FIPIO Configuration
Confirming the configuration
Introduction
Confirmation refused
On completion of the FIPIO bus configuration, and in order to be recognized in the new application, the global bus configuration must be confirmed.
The PL7 then checks the constraints associated with this new application. If the imposed constraints are not respected, no scanning table is created.
A message window opens in this case.
FIPIO Configuration
Cannot generate the scan table for
FIPIO I/Os
?
Close
Recommendations>>
How to access the recommendations
The configuration remains unconfirmed (Bus X physical configuration and FIPIO physical configuration) as long as the problem is not corrected by the user. This configuration can not be transferred into the PLC.
The Recommendations button enlarges the dialogue box where the reasons for refusal as well as useful corrective measures are located.
Step
1
Action
Select the Recommendations button.
TLX DS COM PL7 xxE
279
FIPIO Configuration
Result The characteristics of each configured task (MAST and FAST) are displayed.
FIPIO Configuration
Cannot generate the scan table for
FIPIO I/Os
?
Close
Recommendation>>
Periodic Mast task in controlled mode
Period: 100 ms
Network cycle time: 177 ms
The network cycle time is greater than the period.
To correct this you can:
- configure this task period at a value greater than 177ms
- reduce the number of devices configured in this task.
- switch this task to free mode
If a task’s constraints are not respected, the cause of the failure and corrective recommendations complete the characteristics.
Depending on the recommendations, there are two possible measures for correcting the configuration, these are as follows: l Access the configuration screen of the processor to modify the PL7 task management parameters.
l Access the FIPIO configuration screen to modify device distribution in the MAST or FAST tasks.
280
TLX DS COM PL7 xxE
FIPIO Configuration
Confirmation refused, examples
Introduction
Example 1
The following examples concern the main refusals encountered.
The MAST or FAST task has been configured in controlled periodic mode.
The network cycle time is greater than the period.
FIPIO Configuration
Cannot generate the scan table for
FIPIO I/Os
?
Close
Recommendation>>
Periodic Mast task in controlled mode
Period: 100 ms
Network cycle time: 177 ms
The network cycle time is greater than the period.
To correct this you can:
- configure this task period at a value greater than 177ms
- reduce the number of devices configured in this task.
- switch this task to free mode
TLX DS COM PL7 xxE
281
FIPIO Configuration
Example 2 The MAST task has been configured in cyclic mode.
The network cycle time is greater than the watchdog.
FIPIO Configuration
Cannot generate the scan table for
FIPIO I/Os
?
Close
Recommendation>>
Cyclic Mast task
Watchdog: 100 ms
Network cycle time: 177 ms
The network cycle time is greater than the watchdog.
To correct this you can:
- configure the watchdog of this task period at a value greater than 177ms
- reduce the number of devices configured in this task.
Example 3 The MAST or FAST task has been configured in free periodic mode.
The network cycle time is greater than the watchdog.
FIPIO Configuration
Cannot generate the scan table for
FIPIO I/Os
?
Close
Recommendation>>
Periodic Mast task in free mode
Period: 50ms
Watchdog: 100 ms
Network cycle time: 177 ms
The network cycle time is greater than the watchdog.
To correct this you can:
- configure the watchdog of this task period at a value greater than
177ms
- reduce the number of devices configured in this task.
282
TLX DS COM PL7 xxE
Programming FIPIO communication
20
Introduction
Aim of this
Chapter
What's in this
Chapter?
This Chapter describes the Programming process during set-up FIPIO communication.
This Chapter contains the following Maps:
Topic
FIPIO error processing
Examples of explicit exchange saturation detection
Page
TLX DS COM PL7 xxE
283
FIPIO Programming
FIPIO error processing
Introduction
Algorithm
FIPIO error processing can be performed with the debugging and diagnostics screens.
It can however be useful to perform this processing using a program.
The algorithm shown is an example of a FIPIO bus error detection and management application algorithm
Test bit %S10
(general input/output error)
284
%S10 = 0 ?
Yes
Find error on the FIPIO bus via
%S118
No No input/output error
Find faulty point of
connection via
%I\p2c\m.MOD.ERR = 1
%S118 = 0?
Yes
No
Test error on bus X via
%S119
Find the word from %SW128 to
%SW143, which is different from FFFF
Find the faulty point of connection using the
%SWi:x word bit which is different from 0
There are two different methods for finding the faulty point of connection.
The recommended method is to find it by using system words %SW128 to
%SW143.
Diagnose the connection point using the
READ_STS %CH\p.2.c\0.MOD function
Find the faulty channel via
%I\p.2.c\m.v.ERR = 1
Diagnose the channel via the
READ_STS %CH\p.2.c\m.v.ERR
function
TLX DS COM PL7 xxE
FIPIO Programming
Examples of explicit exchange saturation detection
Introduction The following examples are given in structured text language, but they can be translated into all the PL7 languages.
They only have to be taken into account if the PL7 application may activate more that 24 explicit functions at the same time and if you want to reiterate a request in the event of explicit exchange saturation.
Management of the READ_STS module
IF (NOT (%MW\0.2.1\0.MOD:x0)) THEN (*no request in progress*)
SET %M0; (*request latch*)
(*bit reset to 0 indicating saturation of explicit exchanges*)
%SW116:=%SW116 AND 2#1111111111111011;
READ_STS %CH\0.2.1\0.MOD;
IF (%SW116:x2) THEN
RESET %M0; (*READ_STS retried, saturation has occurred*)
(*%MW\0.2.1\0.MOD.2:x1 signals a functional error*)
END_IF;
END_IF;
IF(%M0 AND NOT (%MW\0.2.1\0.MOD:x0)) THEN
(*%MW\0.2.1\0.MOD.2 can be used*)
RESET %M0;
END_IF;
TLX DS COM PL7 xxE
285
FIPIO Programming
Management of the READ_STS channel
IF (NOT (%MW\0.2.1\0.0:x0)) THEN (*no request in progress*)
SET %M1; (*request latch from channels 0 to 7*)
(*bit reset to 0 indicating saturation of explicit exchanges*)
%SW116:=%SW116 AND 2#1111111111111011;
READ_STS %CH\0.2.1\0.0;
IF (%SW116:x2) THEN
RESET %M1; (*READ_STS retried, saturation has occurred*)
(*%MW\0.2.1\0.0.2:x6 signals a communication error*)
END_IF;
END_IF;
IF(%M1 AND NOT (%MW\0.2.1\0.0:x0)) THEN
(*%MW\0.2.1\0.0.2 can be used*)
RESET %M1;
END_IF;
READ_PARAM at connection point 02
IF (NOT (%MW\0.2.2\0.0:x2)) THEN (*no request in progress*)
SET %M2; (*request latch from channels 0 to 7*)
(*bit reset to 0 indicating saturation of explicit exchanges*)
%SW116:=%SW116 AND 2#1111111111111011;
READ_PARAM %CH\0.2.2\0.0; (*request from the parameters*)
IF ((%MW\0.2.2\0.0.1:x) AND (%SW116:x2)) THEN
(*exchange refused*)
RESET %M2; (*saturation of explicit exchanges*)
END_IF;
END_IF;
IF(%M2 AND NOT (%MW\0.2.2\0.0:x2)) THEN
(*reading finished parameters*)
RESET %M2;
END_IF;
286
TLX DS COM PL7 xxE
FIPIO Programming
WRITE_PARAM at connection point 02
IF (NOT (%MW\0.2.2\0.0:x2)) THEN (*no request in progress*)
SET %M3; (*request latch from channels 0 to 7*)
(*bit reset to 0 indicating saturation of explicit exchanges*)
%SW116:=%SW116 AND 2#1111111111111011;
WRITE_PARAM %CH\0.2.2\0.0, (*parameter transmitting*)
IF ((%MW\0.2.2\0.0.1:x2) AND (%SW116:x2)) THEN
(*exchange refused*)
RESET %M3; (*saturation of explicit exchanges*)
END_IF;
END_IF;
IF(%M3 AND NOT (%MW\0.2.2\0.0:x2)) THEN
(*end of parameter transmission*)
RESET %M3;
END_IF;
WRITE_CMD at connection point 02
IF (NOT (%MW\0.2.2\0.0:x1)) THEN (*no request in progress*)
SET %M3; (*request latch from channels 0 to 7*)
(*bit reset to 0 indicating saturation of explicit exchanges*)
%SW116:=%SW116 AND 2#1111111111111011;
WRITE_CMD %CH\0.2.2\0.0; (*command transmitting*)
IF ((%MW\0.2.2\0.0.1:x1) AND (%SW116:x2)) THEN
(*exchange refused*)
RESET %M3; (*saturation of explicit exchanges*)
END_IF;
END_IF;
IF(%M3 AND NOT (%MW\0.2.2\0.0:x1)) THEN
(*end of command transmission*)
RESET %M3;
END_IF;
TLX DS COM PL7 xxE
287
FIPIO Programming
288
TLX DS COM PL7 xxE
Debugging a FIPIO communication
21
Introduction
Aim of this
Chapter
What's in this
Chapter?
This Chapter describes the Debugging process during set-up of FIPIO communication.
This Chapter contains the following Maps:
Topic
Debugging mode
How to access the remote device debugging screens
FIPIO bus device debugging screen
Page
TLX DS COM PL7 xxE
289
FIPIO Debugging
Debugging mode
Introduction
Inaccessible functions
Debugging mode can only be accessed in online mode.
This mode: l uses a red square to display when a device is faulty from the FIPIO configuration l screen, and adjusts and debugs the devices connected to the FIPIO bus from their application screen.
The following functions can not be accessed from the FIPIO configuration screen in online mode: l l l l adding on a device in online mode, duplicating or moving a device, modifying a device, deleting a device.
A message displayed in the status bar of the PL7 window gives the reason why access is denied.
290
TLX DS COM PL7 xxE
FIPIO Debugging
How to access the remote device debugging screens
Introduction
Procedure
This operation describes how to access the debugging screen of a device connected to the FIPIO bus.
The following table shows the procedure:
Step
1
2
3
4
Action
Connect with the manager PLC.
Access the hardware configuration screen
Double click on the FIPIO connector.
Double click on the standard module to debug.
TLX DS COM PL7 xxE
291
FIPIO Debugging
FIPIO bus device debugging screen
Introduction
Illustration
1
By opening the application screen of a device in debugging mode, the following l l l l l functions can be accessed: parameter display module configuration, reading, writing, and saving adjustment parameters, reading, writing, and forcing the inputs/outputs, aperiodic status data reading, command word writing,
The screen dedicated to devices looks like this:
TSX DMS 1025 [FIPIO1 MODULE 0]
Debugging
Designation: TBX7 EMB.8E/2SR24Vdc Version: 1.0
Global unforcing
RUN
Inputs
ERR IO DIAG...
2
Chan.
6
7
4
5
2
3
0
1
Symbol
0
0
0
0
0
0
0
0
State Error
DIAG...
DIAG...
DIAG...
DIAG...
DIAG...
DIAG...
DIAG...
DIAG...
Channel control
Forcing
F4 Force to 0
F5
F6
Force to 1
Unforce x
292
TLX DS COM PL7 xxE
Elements and functions
FIPIO Debugging
This table describes the different areas that make up the configuration screen:
Address Zone
1 common
2 specific
Function
See (See : PL7 Micro/Junior/Pro ; Communication applications
; Volume 1).
is used to access device debugging or device adjustment parameters.
The accessible parameters are device type functions.
Specific parameters
For input/output type modules, the specific zone displays the value and state of each of the module channels in real time and provides access to the commands from one channel.
For the other module types, the specific zone displays the bus management periodic exchange data.
TLX DS COM PL7 xxE
293
FIPIO Debugging
294
TLX DS COM PL7 xxE
FIPIO communication diagnostics
22
Introduction
Aim of this
Chapter
What's in this
Chapter?
This Chapter describes the Diagnostics process during set-up of FIPIO communication.
This Chapter contains the following Maps:
Topic
Diagnostics mode
How to access the FIPIO bus monitoring screen
Diagnostics screen: FIPIO bus monitoring
How to access the device monitoring screen
Diagnostics screens: device monitoring
How to access the monitoring screen for one device
Diagnostics screen: single device monitoring
How to access the communication error history screen
Diagnostics screen: communication error history
Page
TLX DS COM PL7 xxE
295
FIPIO Diagnostics
Diagnostics mode
Introduction In online mode it is possible to perform general diagnostics on the bus errors and device faults.
This diagnostic is possible by using screens available in the PL7 or the bits and system words managed by the application software.
Two modes are available: l l
FIPIO bus monitoring, device monitoring with or without a fault history.
Communication counters
Every configured connection point (including connection points 0 and 63) has a
report variable. This variable contains the communication counter and performance values.
This variable has: l the activity counters numbered from 16#00 to 16#20 and standardized as l
WORLDFIP, the error counters numbered from 16#21 to 16#7F and standardized as l
WORLDFIP, the manufacturer counters numbered 16#80 to 16#FF these counters are not standardized as WORLDFIP.
The error counters change when there are communication errors on the FIPIO bus.
Diagnostics screens
Four screens display the status of the various counters and thus the communication errors: l The FIPIO bus monitoring screen provides a global view of the FIPIO bus, it l displays the communication errors on the whole bus.
The Device monitoring screen provides a synthesis per connection point; it features all the connection points and indicates the status of the error counters l l per connection point.
The Device monitoring at connection point n screen shows all the counters and their status at a given connection point.
The Communication fault history screen is a fault history, which dates and retains the fault counter statuses to provide a trace.
Only one screen of each type can be open (one per connection point for the third type). If you try to open a screen which is already open, it will appear instantaneously.
296
TLX DS COM PL7 xxE
FIPIO Diagnostics
How to access the FIPIO bus monitoring screen
Introduction
Procedure
This operation describes how to access the FIPIO bus monitoring screen. It only applies to online mode.
The following table shows the procedure:
Step
1
2
3
4
Action
Connect with the manager PLC.
Access the hardware configuration screen
Double click on the FIPIO connector.
Right click on the screen background.
5
Result: a contextual menu appears.
Fipio bus monitoring
Device monitoring
Fipio bus properties
Select the FIPIO bus monitoring command.
TLX DS COM PL7 xxE
297
FIPIO Diagnostics
Diagnostics screen: FIPIO bus monitoring
Introduction
Illustration
Elements and functions
This screen gives the user a global view of the bus and indicates the communication faults on the bus.
The screen has a list of all the bus communication error counters and indicates their status.
The screen dedicated to devices looks like this:
Fipio bus monitoring
Counter Label
34
35
36
37
39
2F
30
32
33
2B
2C
2D
2E
21
22
23
24
Channel 1 No Echo fault
Channel 1 Hyper current fault
Channel 1 Hypo current fault
Channel 1 Cross talk fault
Frame fragment fault
FCS fault
Frame length fault
Pierced frame fault
Coding fault
Overrun fault
Non identified frame type fault
Message recept queue full fault
Message recept queue full fault
Incorrect ADPU length fault
Received APDU type fault
Elementary cycle time exceed
Underrun fault l l
Each line has: l an icon representing the state of the error counter (the reference state being the state at screen opening): l l white for normal state, red for a faulty counter having changed since the reference state, the hexadecimal counter number, the counter labels (given by the WORLDFIP standard).
298
TLX DS COM PL7 xxE
FIPIO Diagnostics
Diagnostics On screen opening or on reset request, the report variables from all the connection points are read by a cyclic communication (one per second).
The counter values from each report variable are stored to create a reference state.
The time between reading and rereading the same variable is equal to the number of configured devices + 2 (0 and 63) in seconds.
As soon as the error counter value becomes different from its reference value, the counter icon goes red, regardless of the connection point. Reading the counter labels provides the type of error detected.
Example
Counter 21 goes red. This means that at least one counter 21 from all the counter
21s has changed.
Bus monitoring via the application
In PL7, the %SW150 and %SW151 system words indicate the number of frames sent and received by the channel manager.
If one of these two counters stops, it indicates that the FIPIO channel manager function has stopped.
The user is made aware of this stop in the configuration screen in online mode, when the background of connection point 0 goes red.
How to reset the reference state
The following procedure shows how to reset the reference state
Step
1
Action
Right click on the screen background.
2
Result: a contextual menu appears.
Reset
Select the Reset command.
TLX DS COM PL7 xxE
299
FIPIO Diagnostics
How to access the device monitoring screen
Introduction
Procedure
This operation describes how to access the FIPIO bus device monitoring screen. It only applies to online mode.
The following table shows the procedure:
Step
1
2
3
4
Action
Connect with the manager PLC.
Access the hardware configuration screen
Double click on the FIPIO connector.
Right click on the screen background.
5
Result: a contextual menu appears.
Fipio bus monitoring
Device monitoring
Fipio bus properties
Select the Device monitoring command.
300
TLX DS COM PL7 xxE
FIPIO Diagnostics
Diagnostics screens: device monitoring
Introduction
Illustration
This screen is used to access the monitoring of all the configured devices.
The screen has a list of all the configured connection points as well as points 0 and
63.
The screen dedicated to devices looks like this:
Monitoring of …
10
13
15
4
6
7
0
1
2
3
22
24
26
17
20
21
27
30
38
39
40
35
36
37
31
32
33
34
56
63
78
53
54
55
79
80
88
89
90
85
86
87
81
82
83
84
94
95
96
91
92
93
97
100
101
103
104
105
106
107
108
109
110
111
112
114
116
124
125
126
127
Elements and functions
The following elements are associated with each connection point: l one icon showing: l whether the connection point needs to be monitored. If the box is checked, the device is monitored.
l l whether the connection point is faulty. The icon goes red if an error is detected.
the connection point number.
TLX DS COM PL7 xxE
301
FIPIO Diagnostics
Diagnostics
How to disable device monitoring
On screen opening or on reset request, the report variables from all the connection points are read by a cyclic communication (one per second).
The counter values from each report variable are stored to create a reference state.
The time between reading and rereading the same variable is equal to the number of configured devices + 2 (0 and 63) in seconds.
A connection point is considered faulty if the value of one of the error counters has changed since the reference state. When the point is faulty, the icon turns red.
Diagnostics are only sent back if there is a communication between the bus manager and the faulty connection point. Errors correspond to the WORLDFIP standard defined error counters.
The following procedure describes how to disable the device monitoring on the bus.
Step
1
Action
Click on the checkbox belonging to the connection point to be disabled.
Result:
The box is no longer checked. In this case this connection’s report variable is no longer read and its reference state is reset.
How to reset the reference state
The following procedure shows how to reset the reference state
Step
1
Action
Right click on the screen background.
2
Result: a contextual menu appears.
Device monitoring
Communication errors log
Monitoring
Reset
Select the Reset command.
302
TLX DS COM PL7 xxE
FIPIO Diagnostics
How to access the monitoring screen for one device
Introduction
Procedure
This operation describes how to access the monitoring screen for a single FIPIO bus device and how to display its error counters.
It only applies to online mode.
The following table shows the procedure:
Step
1
2
Action
Access the Device monitoring screen.
Select the connection point number to be accessed.
3
4
Result: the number is highlighted.
Right click on the screen background.
Result: a contextual menu appears.
Device monitoring
Communication errors log
Monitoring
Reset
Select the Single device monitoring command.
TLX DS COM PL7 xxE
303
FIPIO Diagnostics
Diagnostics screen: single device monitoring
Introduction
Illustration
This screen is used to display the status details of all the counters from a particular l l l connection point.
It features all three zones corresponding to each type of counter: activity, error, manufacturer
The screen dedicated to devices looks like this:
Device Monitoring at Connection Point 2
Activity counter
21
22
23
Initial value Previous value
6E34
72D8
0000
6C8D
7114
0000
Activity counter
2B
2C
2D
2E
21
22
23
24
2F
30
35
39
Initial value Previous value
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
007E
0000
0000
0060
0000
0000
0000
0000
Activity counter
80
Initial value Previous value
0001 0000
Current value
71B5
Label
Counter frames response received
7673 Counter frames response returned
0000 Fast aperiodic specified requests
Current value
0000
0000
0000
0000
007e
0000
0000
0060
0000
0000
0000
0000
Label
Channel 1 No Echo fault
Channel 1 Hyper current fault
Channel 1 Hypo current fault
Channel 1 Cross talk fault
Frame fragment fault
FCS fault
Frame length fault
Pierced frame fault
Coding fault
Overrun fault
Incorrect ADPU length fault
Underrun fault
Current value
0000
Label
Counter not listed
304
TLX DS COM PL7 xxE
FIPIO Diagnostics
Elements and functions
Diagnostics l l l l l
The following elements are associated with each counter: l one icon indicating the state of the counter since the reference state: l l white: no change, green: change in the activity or manufacturer counters, l red: change in the error counters (the current value is different from the reference state).
the hexadecimal counter number, its hexadecimal reference value, its hexadecimal value during the last read, its current hexadecimal value, its label according to the WORLDFIP standard or the Counter not listed label for the manufacturer part.
On screen opening or on reset request, the report variables from all the connection points are read by a cyclic communication (one per second).
The counter values from each report variable are stored to create a reference state.
A connection point is considered faulty if the value of one of the error counters has changed since the reference state. When the point is faulty, the icon turns red.
Diagnostics are only sent back if there is a communication between the bus manager and the faulty connection point. Errors correspond to the WORLDFIP standard defined error counters.
How to reset the reference state
The following procedure shows how to reset the reference state
Step
1
Action
Right click on the screen background.
2
Result: a contextual menu appears.
Reset
Select the Reset command.
TLX DS COM PL7 xxE
305
FIPIO Diagnostics
How to access the communication error history screen
Introduction
Procedure
This operation describes how to access the FIPIO bus communication error history screen.
It only applies to online mode.
The following table shows the procedure:
Step
1
2
Action
Access the Device monitoring screen.
Right click on the screen background.
Result: a contextual menu appears.
Device Monitoring
Communication errors history
Monitoring
Reset
3 Select the Communication error history command.
306
TLX DS COM PL7 xxE
FIPIO Diagnostics
Diagnostics screen: communication error history
Introduction
Illustration
This screen has a list of the communication errors from the connection points (plus
0 and 63), which are configured and declared monitored in the Device monitoring screen.
The screen dedicated to devices looks like this:
Communication errors history
Date Time Connection point
14/10/1998 14:39:49 2
14/10/1998 14:39:49 2
Counter
2B
2E
Value Label
007E Frame fragment fault
0060 Pierced frame fault
Elements and functions
How to pause/ resume the history
Every time an error counter from a connection point changes, a line is added. It l l l l l features: the current date and time of the programming terminal, the decimal connection point number, the hexadecimal error counter number, the hexadecimal counter value, the counter label according to the WORLDFIP standard.
This command is used to stop and resume screen updating.
Step
1
Action
Right click on the screen background.
2
Result: a contextual menu appears.
Pause History
Reset history
Clear history
Cpy
Sort
Automatic stop of history
Reset
Select the Pause history command or Resume history command.
TLX DS COM PL7 xxE
307
FIPIO Diagnostics
How to clear history
This command can be accessed if the Pause history function is confirmed. It is used to delete all the lines from the screen.
Step
1
2
Action
Access the contextual menu.
Select the Clear history command
How to sort the history
This command can be accessed if the Pause history function is confirmed. It is used to sort all the history lines either by date and time or by connection point or counter.
Step
1
2
Action
Access the contextual menu.
Select the Sort
→
by date and time command.
How to copy the history
This command can be accessed if the Pause history function is confirmed. It is used to copy lines selected in text format onto the clipboard.
Step
1
2
Action
Access the contextual menu.
Select the Sort
→
by date and time command.
How to automatically stop the history
When this function is selected, it is used to stop the history when it has reached a maximum number of lines (4000 lines). A message pops up to indicate that this stop has occurred. When the function is not selected and when the maximum number has been reached, new added lines replace the first ones (turning mode).
Step
1
2
Action
Access the contextual menu.
Select the Automatic history stop command
Result: selecting the command checks the function.
How to reset the reference state
The following procedure shows how to reset the reference state
Step
1
2
Action
Access the contextual menu.
Select the Reset command.
308
TLX DS COM PL7 xxE
Language objects associated with
FIPIO communication
23
Introduction
Aim of this
Section
What's in this
Chapter?
This Chapter introduces language objects associated with FIPIO communication.
This Chapter contains the following Maps:
Topic
Language objects in implicit exchange
Language object for explicit exchange
Explicit exchange management and reports
Page
309
TLX DS COM PL7 xxE
FIPIO language objects
Language objects in implicit exchange
Introduction
Bit objects
This page describes all the language objects for implicit exchange in FIPIO communication that can be displayed or modified by the application program. (PL7
Micro/Junior/Pro ; Communication applications ; Volume 1)
The table below shows the different bit objects for implicit exchange.
Object (1) Function
%I\p.2.c\0.MOD.ERR
Module error bit
%I\p.2.c\m.i.ERR
%I\p.2.c\m.i.r
%Q\p.2.c\m.i.r
Channel error bit
Bit exchange
Bit exchange
Meaning
This bit set to 1, indicates a module error (at least one of the channels is faulty,…)
This bit set at 1 indicates a faulty channel.
Image of the module’s physical inputs (input acquisition)
Image of the module’s physical outputs
(output command)
Key
(1) p.2.c\m.i.r Address l l l l p: corresponds to the processor’s slot c: corresponds to the connection point number m: corresponds to the module position number i: corresponds to the channel number
Word objects The table below shows the different word objects for implicit exchange.
Object (1) Function
%IW\p.2.c\m.i.r
Word exchange
%QW\p.2.c\m.i.
r
Word exchange
Meaning
Image of the module’s physical inputs (input acquisition)
Image of the module’s physical outputs (output command)
Key
(1) p.2.c\m.i.r Address l l l l p: corresponds to the processor’s slot c: corresponds to the connection point number m: corresponds to the module position number i: corresponds to the channel number
310
TLX DS COM PL7 xxE
FIPIO language objects
Language object for explicit exchange
Introduction
Word objects
This page describes all the language objects for explicit exchange in a FIPIO communication that can be displayed or modified by the application program. (PL7
Micro/Junior/Pro ; Communication applications ; Volume 1)
The table below shows the different word objects for explicit exchange.
Object (1) Function Meaning
%MW\p.2.c\0.MOD.2 Module status
%MW\p.2.c\0.i.2
Standard module channel status l l l l l l l l
Least significant byte: corresponds to standard.
l l l l l l l l x0 = 1: internal error x1 = 1: functional error x2 = 1: terminal block fault x3 = 1: standard module self-testing x4 = 1: reserved (= 0) x5 = 1: configuration error x6 = 1: missing module x7 = 1: extension module error
Most significant byte: corresponds to extension x8 = 1: internal error x9 = 1: functional error x10 = 1: terminal block fault x11 = 1: extension module self-testing x12 = 1: reserved (= 0) x13 = 1: configuration error x14 = 1: missing module x15 = 1: reserved (= 0)
Least significant byte: corresponding to standard l l l l l l l l x0 = 1: external error 4 x1 = 1: external error 3 x2 = 1: external error 2 x3 = 1: external error 1 x4 = 1: internal error x5 = 1: hardware configuration error x6 = 1: communication error x7 = 1: application error
TLX DS COM PL7 xxE
311
FIPIO language objects
Object (1)
%MW\p.2.c\1.i.2
Function
Extension module channel status
Meaning
Least significant byte: corresponding to extension l l l l l l l l x0 = 1: external error 4 x1 = 1: external error 3 x2 = 1: external error 2 x3 = 1: external error 1 x4 = 1: internal error x5 = 1: hardware configuration error x6 = 1: communication error x7 = 1: application error
Key
(1) p.2.c\m.i.r Address l l l l p: corresponds to the processor’s slot c: corresponds to the connection point number m: corresponds to the module position number i: corresponds to the channel number
Example
Note: For each connected device, refer to the corresponding documentation for details of task status words.
The example focuses on the channel level diagnostics for a TBX TOR device:
Object
%MW\p.2.c\0.i.2
%MW\p.2.c\1.i.2
Function
Channel status
Meaning l l
Least significant byte: l l l l l x0 = 1: tripped output x1 = 1: globally tripped x2 = 1: terminal block fault x3 = 1: external supply fault x4 = 1: channel configured but not physically present l x5 = 1: channel present but different from that configured x6 = 1: communication error x7 = 1: application error
312
TLX DS COM PL7 xxE
FIPIO language objects
Explicit exchange management and reports
Introduction
Word objects
This page describes all the language objects that manage explicit exchanges. (See
: PL7 Micro/Junior/Pro ; Communication applications ; Volume 1)
The table below shows the different word objects for the management of explicit exchanges.
Object (1)
%MW\p.2.c\
0.MOD.0
%MW\p.2.c\
0.MOD.0
Function
Module exchanges in progress
%MW\p.2.c\
0.i.0
Channel exchanges in progress
%MW\p.2.c\
0.i.1
Module report
Channel report
Meaning l l l x0 = 1: reading status in progress x1 = 1: sending of command parameters to the communication module x2 = 1: sending of adjustment parameters to the communication module l l x1 = 0: command parameters received and accepted by the module x2 = 0: adjustment parameters received and accepted by the module l l l l l l l l l x0 = 1: reading status in progress x1 = 1: sending of command parameters in progress x2 = 1: sending of adjustment parameters in progress x3 to x14: reserved (= 0) x15 = 1: sending of configuration parameters in progress l x0 = 0: status reading OK x1 = 0: command parameters received and accepted by the device x2 = 0: adjustment parameters received and accepted by the device x3 to x14: reserved (= 0) x15 = 0: configuration parameters received and accepted by the device
Key
(1) p.2.c\m.i.r Address l l l l p: corresponds to the processor’s slot c: corresponds to the connection point number m: corresponds to the module position number i: corresponds to the channel number
TLX DS COM PL7 xxE
313
FIPIO language objects
314
TLX DS COM PL7 xxE
FIPIO communication standard profiles
24
Introduction
Aim of this
Chapter
What's in this
Chapter?
This chapter introduces devices compatible with the standard communication profiles for use with the FIPIO bus and its services.
This Chapter contains the following Sections:
Section
24.1
24.2
24.3
24.4
Topic
Introduction to standard FIPIO communication profiles
Configuration of the FIPIO bus standard profiles
Debugging the FIPIO bus standard profiles
Language objects associated with the FIPIO bus standard profiles
Page
TLX DS COM PL7 xxE
315
Standard profiles
24.1
Introduction to standard FIPIO communication profiles
Introduction
Aim of this
Section
What's in this
Section?
This Section provides a summary description of the standard profiles of the FIPIO bus and its associated services.
This Section contains the following Maps:
Topic
Standard profiles: general
Designation of a standard profile
List of the standard profiles proposed in catalog by PL7
Page
316
TLX DS COM PL7 xxE
Standard profiles
Standard profiles: general
Introduction
Volume of data exchanged
A device conforming to the standard FIPIO communication profiles can be linked to a FIPIO bus, to exchange the input/output variables.
Data exchanges with devices are used to: l l l exchange inputs/outputs, write configuration or adjustment parameters, diagnose a connected device.
l l l
There are three types of standard profile:
FRDP: FIPIO Reduced Device Profile
FSDP: FIPIO Simple Device Profile
FEDP: FIPIO Extended Device Profile
The device profiles, which conform to a standard profile are a function of the number of inputs and outputs to be exchanged.
The table below describes the words managed by the different standard profiles:
Profile
Process data input acquisition output control
Configuration (optional)
Adjust (optional)
Commands specific command
Diagnostics input validity specific status
FRD
-
-
2 words
2 words
-
1 byte
-
FSD
8 words
8 words
16 words
32 words
-
1 byte
-
FED
32 words
32 words
30 words
30 words
8 words
1 byte
8 words
TLX DS COM PL7 xxE
317
Standard profiles
Designation of a standard profile
Introduction
How the reference is made up
FRD profile
A device conforming to the standard FIPIO communication profiles is defined by assigning one of the STD_P family standard profiles to it at the FIPIO connection point.
The family consists of a standard profile reference list.
Each reference is made up of several significant codes: l the standard profile used: l FRD l l
FSD
FED l l the connected device structure: l C: Compact l M: Modular the number and type of objects exchanged with the manager: corresponds to the input/output exchange volume in 16 bit words l 2 words l l 8 words l 32 words
P: corresponds to the presence of configuration or adjustment parameters (chosen).
the reference is made up of the following:
Profile
FRD
Structure
C
Number of objects Parameter
2 -
P
FSD profile
FED profile the reference is made up of the following:
Profile
FSD
Structure
C
M
Number of objects Parameter
8 -
P the reference is made up of the following:
Profile
FED
Structure
C
M
Number of objects Parameter
32 -
P
318
TLX DS COM PL7 xxE
Standard profiles
List of the standard profiles proposed in catalog by PL7
Introduction During FIPIO configuration, you can connect standard profiles in accordance with device type.
Compact device The following table gives a list of the compact standard profiles:
Reference
FRD C2
FRD C2 P
FSD C8
FSD C8 P
FED C32
FED C32 P
Designation
EQP RED CMPCT 2M
EQP STD CMPCT 2M P
STD DEV CMPCT 2W P
Language interface
32 bits %I, 32 bits %Q
32 bits %I, 32 bits %Q
16 configuration words, 32 adjustment words
8 words %IW, 8 words %QW EQP STD CMPCT 8M
STD DEV CMPCT 8W
EQP STD CMPCT 8M P
STD DEV CMPCT 8W P
8 words %IW, 8 words %QW
16 configuration words, 32 adjustment words
32 words %IW, 32 words %QW EQP STD CMPCT 32M
STD DEV CMPCT 32W
EQP STD CMPCT 32M P 32 words %IW, 32 words %QW
STD DEV CMPCT 328W P 30 configuration words, 30 adjustment words
Modular device The following table gives a list of the modular standard profiles:
Reference
FSD M8
FSD M8 P
FED M32
FED M32 P
Designation
EQP STD MOD 8M
STD DEV MOD 8W
EQP STD MOD 8M P
STD DEV MOD 8W P
EQP STD MOD 32M
EXTENDED DEV MOD 32W
EQP STD MOD 32M P
EXTENDED DEV MOD
328W P
Language interface
8 words %IW, 8 words %QW
8 words %IW, 8 words %QW
16 configuration words, 32 adjustment words
32 words %IW, 32 words %QW
32 words %IW, 32 words %QW
30 configuration words, 30 adjustment words
TLX DS COM PL7 xxE
319
Standard profiles
Momentum
Device
In the Momentum family, where an analog input/output base is not available in the catalog, it is then necessary to select one of the OTHER_FxD_[P] standard profile references.
The choice criteria are as follows:
Language interface
32 bits %I, 32 bits %Q
Reference
OTHER_FRD
OTHER_FRDP
OTHER_FSD
OTHER_FSDP
OTHER_FED
OTHER_FEDP
8 words %IW, 8 words %QW
32 words %IW, 32 words %QW
Communicator The communicators are as follows:
Reference
OTHER
TSX FPP10
170 FNT 110 01
Language interface other communication module
FIPIO TSX communication module
FIPIO TSX communication module for the TS Momentum
320
TLX DS COM PL7 xxE
24.2
Standard profiles
Configuration of the FIPIO bus standard profiles
Introduction
Aim of this
Section
What's in this
Section?
This Section introduces the configuration principles for the FIPIO bus standard profiles.
This Section contains the following Maps:
Topic
Configuration screen of a standard profile
How to modify the parameters of a standard profile
Adjustment mode
Page
TLX DS COM PL7 xxE
321
Standard profiles
Configuration screen of a standard profile
Introduction
Illustration
The configuration screen of a standard profile reuses the parameters of all other devices configured on the FIPIO bus (see Configuration screen of an FIPIO device).
However, some parameters are exclusive to it. In the rest of this document, only the part specific to the standard profiles is explained.
The screen dedicated to the device looks like this:
FSD M8 P [FIPIO18 MODULE 0]
Configuration
Designation: EQP STD MOD 8MP
Elements and functions
1
2
3
4
Channel 0
Local configuration
Task: MAST
Default configuration
Base
Decimal
Parameter
%KW\0.2.18\0.0.0
%KW\0.2.18\0.0.1
%KW\0.2.18\0.0.2
%KW\0.2.18\0.0.3
%KW\0.2.18\0.0.4
%KW\0.2.18\0.0.5
%KW\0.2.18\0.0.6
%KW\0.2.18\0.0.7
Symbol Value
0
0
16#8040
16#0
0
0
0
16#4
This table describes the different areas that make up the configuration screen:
Address Description
1 The Local configuration check box is only available for the FSD C8 P and FSD
M8 P profiles.
If the box is checked, the configuration and adjustment parameters are not sent to the device connected to the bus (to ensure rapid start-up of the device). The device starts up or initializes with its own parameters.
In the configuration screen, if the box is checked, the parameters of the channel cannot be accessed.
2 The Default configuration button is used to return to the original configuration.
322
TLX DS COM PL7 xxE
Standard profiles
Address Description
3
4
The Standard is used to select the display standard of the value of the selected word.
Three types are available: l l l
Decimal
Hexadecimal
Binary
This list displays the configuration words %KW or the adjustment words %MW which correspond to the registered standard profile.
For each word, there is an associated Symbol and a Value.
TLX DS COM PL7 xxE
323
Standard profiles
How to modify the parameters of a standard profile
Introduction
How to modify the display standard
The following procedures apply to the configuration or adjustment parameters.
The following procedure shows the selection of the display standard. For the example, the chosen standard is binary.
Step
1
2
Action
Select the cell Value of the word to be modified.
Select from the dropdown menu Standard
→
Binary.
Result: the cell displays 2#1011 .
How to enter a value on the keyboard
The following procedure shows how to key a value into a cell.
Step
1
2
Action
Select the Value cell of the word to be modified.
How to enter a value on the keyboard.
Note:
Keyboard entry depends on the display standard.
324
TLX DS COM PL7 xxE
How to enter a value in binary form
Standard profiles
The following procedure shows how to enter a value in binary form.
Step
1
Action
Double click on the Value cell of the word to be modified.
Result: the following window appears.
Property of: %KW\0.2.5\0.0.7
2
3
07:
06:
05:
04:
03:
02:
01:
15:
14:
13:
12:
11:
10:
09:
08:
Bits of word
Select the bits which must be set to 1.
Close the window Property of: ... by selecting the cross in the left-hand corner.
Result: The closure validates the entered value and displays it according to the standard.
TLX DS COM PL7 xxE
325
Standard profiles
Adjustment mode
Introduction
Illustration
Adjustment mode is accessed from the hardware configuration menu of the application browser. The principal is the same as for configuration mode, and the adjustment words are %MW.
There are 32 possible words for the FSD and FRD profiles and 30 words for the FED profiles.
The adjustment screen dedicated to the device looks like this:
FSD C8 P [FIPIO5 MODULE 0]
Configuration
Designation: EQP STD CMPCT 8MP
Channel 0
Local configuration
Task: MAST
Default configuration
Base
Decimal
Parameter
%KW\0.2.5\0.0.0
%KW\0.2.5\0.0.1
%KW\0.2.5\0.0.2
%KW\0.2.5\0.0.3
%KW\0.2.5\0.0.4
%KW\0.2.5\0.0.5
%KW\0.2.5\0.0.6
%KW\0.2.5\0.0.7
Symbol
0
0
0
0
0
0
0
0
Value
326
TLX DS COM PL7 xxE
24.3
Standard profiles
Debugging the FIPIO bus standard profiles
Introduction
Aim of this
Section
What's in this
Section?
This Section introduces the debugging principles FIPIO bus standard profiles.
This Section contains the following Maps:
Topic
Debugging screen of a standard profile
How to modify the debugging parameters of a standard profile
Page
TLX DS COM PL7 xxE
327
Standard profiles
Debugging screen of a standard profile
Introduction The debugging screen of a standard profile reuses the parameters of all other devices configured on the FIPIO bus (see Debugging screen of an FIPIO device).
However, some parameters are exclusive to it. In the rest of this document, only the part specific to the standard profiles is explained.
Note: The adjustment parameters cannot be accessed.
Illustration The screen dedicated to the device looks like this:
1
2
3
FED C32 P [FIPIO4 MODULE 0]
Debugging
Designation: EQP STD CMPCT 32MP Version: 1.0
RUN ERR IO
Channel 0
Variables
Outputs
Reference
%QW\0.2.4\0.0.0
%QW\0.2.4\0.0.1
%QW\0.2.4\0.0.2
%QW\0.2.4\0.0.3
%QW\0.2.4\0.0.4
%QW\0.2.4\0.0.5
%QW\0.2.4\0.0.6
%QW\0.2.4\0.0.7
%QW\0.2.4\0.0.8
%QW\0.2.4\0.0.13
%QW\0.2.4\0.0.14
%QW\0.2.4\0.0.15
DIAG...
Task: MAST
Label
Base
Hexadecimal
Symbol Value
16#1
16#30
16#24
16#C00
16#0
16#0
16#3C10
16#30
16#0
16#0
16#0
16#0
DIAG...
328
TLX DS COM PL7 xxE
Elements and functions
Standard profiles
This table describes the different areas that make up the configuration screen:
Address Description
1
2
3
This dropdown list allows the choice of periodic exchange: l l of the input parts, of the output parts.
The Standard window is used to select the display standard of the value of the selected word.
Three types are available: l l l
Decimal
Hexadecimal
Binary
This list displays the input words %IW or the output words %QW which correspond to the registered standard profile.
For each word there is an associated Wording, a Symbol and a Value.
TLX DS COM PL7 xxE
329
Standard profiles
How to modify the debugging parameters of a standard profile
Introduction
How to modify the display standard
The following procedures apply to the debugging parameters.
The following procedure shows the selection of the display standard. For the example, the chosen standard is binary.
Step
1
2
Action
Select the Value cell of the word to be modified.
Select from the dropdown menu Standard
→
Binary.
Result: the cell displays 2#1011 .
How to enter a value on the keyboard
The following procedure shows how to key a value into a cell.
Step
1
2
Action
Select the Value cell of the word to be modified.
How to enter a value on the keyboard.
Note:
Keyboard entry depends on the display standard.
330
TLX DS COM PL7 xxE
How to enter a value in binary form
Standard profiles
The following procedure shows how to enter a value in binary form. It is only valid for the output parts.
Step
1
Action
Double click on the Value cell of the word to be modified.
Result: the following window appears.
Property of: %KW\0.2.5\0.0.7
2
3
07:
06:
05:
04:
03:
02:
01:
00:
15:
14:
13:
12:
11:
10:
09:
08:
Bits of word
Select the bits which must be set to 1.
Close the window Property of: ... by selecting the cross in the left-hand corner.
Result: The closure validates the entered value and displays it according to the standard.
TLX DS COM PL7 xxE
331
Standard profiles
24.4
Language objects associated with the FIPIO bus standard profiles
Introduction
Aim of this
Section
What's in this
Section?
This section introduces the language objects associated with the FIPIO bus standard profiles.
This Section contains the following Maps:
Topic
Summary of the objects which can be accessed via the standard profiles
Language objects in implicit exchange
Language object for explicit exchange
Language objects associated with configuration
Page
332
TLX DS COM PL7 xxE
Standard profiles
Summary of the objects which can be accessed via the standard profiles
Introduction
FRD profile
The following tables show the language objects associated with each profile contained in the PL7 catalogue.
The following table relates to the FRD profiles
Input acquisition
Output command
Configuration words
FRD C2
%I\p.2.c\0.0
%I\p.2.c\0.31
%Q\p.2.c\0.0
%Q\p.2.c\0.31
-
Status: management of exchanges
Exchange report
Status: channel standard
Validity of inputs
Status: channel specific
Command words
Adjustment words
%MW\p.2.c\0.i.0
-
-
%MW\p.2.c\0.i.1
%MW\p.2.c\0.i.2
%MW\p.2.c\0.i.3
-
FRD C2 P
%I\p.2.c\0.0
%I\p.2.c\0.31
%Q\p.2.c\0.0
%Q\p.2.c\0.31
%KW\p.2.c\0.i.0
%KW\p.2.c\0.i.15
%MW\p.2.c\0.i.0
%MW\p.2.c\0.i.1
%MW\p.2.c\0.i.2
%MW\p.2.c\0.i.3
-
-
%MW\p.2.c\0.i.4
%MW\p.2.c\0.i.35
TLX DS COM PL7 xxE
333
Standard profiles
FSD profile The following table relates to the FSD profiles
Input acquisition
Output command
Configuration words
FSD C/M8
%IW\p.2.c\0.0
%IW\p.2.c\0.7
%QW\p.2.c\0.0
%QW\p.2.c\0.7
-
Status: management of exchanges
Exchange report
Status: channel standard
Validity of inputs
Status: channel specific
Command words
Adjustment words
%MW\p.2.c\0.i.0
-
-
%MW\p.2.c\0.i.1
%MW\p.2.c\0.i.2
%MW\p.2.c\0.i.3
-
FSD C/M8 P
%IW\p.2.c\0.0
%IW\p.2.c\0.7
%QW\p.2.c\0.0
%QW\p.2.c\0.7
%KW\p.2.c\0.i.0
%KW\p.2.c\0.i.15
%MW\p.2.c\0.i.0
%MW\p.2.c\0.i.1
%MW\p.2.c\0.i.2
%MW\p.2.c\0.i.3
-
-
%MW\p.2.c\0.i.4
%MW\p.2.c\0.i.35
334
TLX DS COM PL7 xxE
FED profile The following table relates to the FED profiles
Input acquisition
Output command
Configuration words
FED C/M32
%IW\p.2.c\0.0
%IW\p.2.c\0.31
%QW\p.2.c\0.0
%QW\p.2.c\0.31
-
Status: management of exchanges
Exchange report
Status: channel standard
Validity of inputs
Status: channel specific
Command words
Adjustment words
%MW\p.2.c\0.i.0
%MW\p.2.c\0.i.1
%MW\p.2.c\0.i.2
%MW\p.2.c\0.i.3
%MW\p.2.c\0.i.4
%MW\p.2.c\0.i.11
%MW\p.2.c\0.i.12
%MW\p.2.c\0.i.19
-
Standard profiles
FED C/M32 P
%IW\p.2.c\0.0
%IW\p.2.c\0.31
%QW\p.2.c\0.0
%QW\p.2.c\0.31
%KW\p.2.c\0.i.0
%KW\p.2.c\0.i.29
%MW\p.2.c\0.i.0
%MW\p.2.c\0.i.1
%MW\p.2.c\0.i.2
%MW\p.2.c\0.i.3
%MW\p.2.c\0.i.4
%MW\p.2.c\0.i.11
%MW\p.2.c\0.i.12
%MW\p.2.c\0.i.19
%MW\p.2.c\0.i.20
%MW\p.2.c\0.i.49
TLX DS COM PL7 xxE
335
Standard profiles
Language objects in implicit exchange
Introduction
Bit objects
This page describes all the language objects for implicit exchange associated with the standard profiles for FIPIO communication that can be displayed or modified by the application program. (PL7 Micro/Junior/Pro ; Communication applications ;
Volume 1)
The table below shows the different bit objects for implicit exchange.
Object (1)
%I\p.2.c\0.MOD
.ERR
%I\p.2.c\m.i.ER
R
%I\p.2.c\0.0 to
%I\p.2.c\0.31
%Q\p.2.c\0.0 to
%Q\p.2.c\0.31
Function
Module error bit
Channel error bit
Bit exchange
Bit exchange
Meaning
This bit set to 1, indicates a module error (at least one of the channels is faulty,…)
This bit set at 1 indicates a faulty channel.
Acquiring input bits for FRD profiles
Acquiring output bits for FRD profiles
Key
(1) p.2.c Address l l p: corresponds to the processor’s slot c: corresponds to the connection point number
336
TLX DS COM PL7 xxE
Word objects
Standard profiles
The table below shows the different word objects for implicit exchange.
Object (1)
%IW\p.2.c\0.0.
0 to
%IW\p.2.c\0.0.
7
Function
FSD word exchange
%QW\p.2.c\0.0.
0 to
%QW\p.2.c\0.0.
7
FSD word exchange
%IW\p.2.c\0.0.
0 to
%IW\p.2.c\0.0.
31
%QW\p.2.c\0.0.
0 to
%QW\p.2.c\0.0.
31
FED word exchange
FED word exchange
Meaning
Acquiring input words for FSD profiles
Acquiring output words for FSD profiles
Acquiring input words for FED profiles
Acquiring output words for FED profiles
Key
(1) p.2.c\m.i.r Address l l l l p: corresponds to the processor’s slot c: corresponds to the connection point number m: corresponds to the module position number i: corresponds to the channel number
TLX DS COM PL7 xxE
337
Standard profiles
Language object for explicit exchange
Introduction
Word objects common to all the profiles
This page describes all the language objects for explicit exchange associated with the standard profiles for FIPIO communication that can be displayed or modified by the application program. (PL7 Micro/Junior/Pro ; Communication applications ;
Volume 1)
The table below shows the different word objects for explicit exchange.
Object (1) Function Meaning
%MW\p.2.c\0.MO
D.2
%MW\p.2.c\0.i.2
Module status
Standard module channel status l l l l l l l l
Least significant byte: corresponds to standard.
l l l l l l l l x0 = 1: internal error x1 = 1: functional error x2 = 1: terminal block fault x3 = 1: standard module self-testing x4 = 1: reserved (= 0) x5 = 1: configuration error x6 = 1: missing module x7 = 1: extension module error
Most significant byte: corresponds to extension x8 = 1: internal error x9 = 1: functional error x10 = 1: terminal block fault x11 = 1: extension module self-testing x12 = 1: reserved (= 0) x13 = 1: configuration error x14 = 1: missing module x15 = 1: reserved (= 0)
Least significant byte: corresponding to standard l l l l l l l l x0 = 1: external error 4 x1 = 1: external error 3 x2 = 1: external error 2 x3 = 1: external error 1 x4 = 1: internal error x5 = 1: hardware configuration error x6 = 1: communication error x7 = 1: application error
%MW\p.2.c\0.i.3
Validity of inputs For FRD, FSD and FED profiles the least significant byte is specific to the connected device.
Refer to the documentation for the device.
Key
338
TLX DS COM PL7 xxE
Standard profiles
Object (1)
(1)
Function Meaning p.2.c\m.i.r Address l l l l p: corresponds to the processor’s slot c: corresponds to the connection point number m: corresponds to the module position number i: corresponds to the channel number
Note: For each connected device, refer to the corresponding documentation for details of task status words.
Internal words for FRD and FSD profiles
The following table shows the internal words specific to FRD and FSD profiles:
Object
%MW\p.2.c\0.i.4
to
%MW\p.2.c\0.i.35
Function
Adjustment parameters
Meaning
32 specific adjustment words.
Parameters which can be accessed in read and write format via the WRITE_PARAM , READ_PARAM ,
SAVE_PARAM and RESTORE_PARAM functions.
Key
(1) p.2.c\m.i.r Address l l l l p: corresponds to the processor’s slot c: corresponds to the connection point number m: corresponds to the module position number i: corresponds to the channel number
Internal words for the FED profiles
TLX DS COM PL7 xxE
The following table shows the internal words specific to the FED profiles:
Object
%MW\p.2.c\0.i.4
to
%MW\p.2.c\0.i.11
%MW\p.2.c\0.i.12
to
%MW\p.2.c\0.i.19
%MW\p.2.c\0.i.20
to
%MW\p.2.c\0.i.49
Function Meaning
Specific status 8 specific status words.
Parameters which can be accessed in read format via the READ_STATUS function.
Specific channel level command
8 specific command words.
Parameters which can be accessed in write format by the WRITE_CMD function.
Adjustment parameters
32 specific adjustment words.
Parameters which can be accessed in read and write format via the WRITE_PARAM , READ_PARAM ,
SAVE_PARAM and RESTORE_PARAM functions.
Key
339
Standard profiles
Object
(1)
Function Meaning p.2.c\m.i.r Address l l l l p: corresponds to the processor’s slot c: corresponds to the connection point number m: corresponds to the module position number i: corresponds to the channel number
340
TLX DS COM PL7 xxE
Standard profiles
Language objects associated with configuration
Introduction
Internal constants
This page describes all the configuration language objects associated with the
FIPIO communication agents that can be displayed by the agent application program.
The following table describes the internal constants:
Object
%KW\p.2.c\
0.0.0 to
%KW\p.2.c\
0.15
%KW\p.2.c\
0.0.0 to
%KW\p.2.c\
0.29
Function
Configuration words at channel level
Configuration words at channel level
Meaning
They contain channel parameters set via the configuration editor for FRD and FSD profiles.
They contain channel parameters set via the configuration editor for FED profiles.
TLX DS COM PL7 xxE
341
Standard profiles
342
TLX DS COM PL7 xxE
FIPIO Agent
25
Introduction
Aim of this
Chapter
What's in this
Chapter?
This Chapter introduces the Agent devices on the FIPIO bus and its services.
This Chapter contains the following Sections:
Section
25.1
25.2
25.3
25.4
Topic
Introduction to FIPIO Agents
Configuration of FIPIO Agents
Debugging FIPIO Agents
Language objects associated with the FIPIO Agents
Page
TLX DS COM PL7 xxE
343
FIPIO Agent
25.1
Introduction to FIPIO Agents
Introduction
Aim of this
Section
What's in this
Section?
This section provides a summary description of the agents on the FIPIO bus and their associated services.
This Section contains the following Maps:
Topic
FIPIO Agent: General
Periodic data exchange
Special cases
Communication from an FIPIO Agent
Page
344
TLX DS COM PL7 xxE
FIPIO Agent
FIPIO Agent: General
Introduction The TSX Micro or TSX Premium PLCs, equipped with the PCMCIA TSX FPP 10 card on their built-in communication channel, are agents on the FIPIO bus.
The FIPIO function agent is used to perform two types of data exchange: l l periodic exchanges of information with the manager (shared variables type), aperiodic exchanges of messages with the manager, from CCX 17 devices or with other agents.
Note: This function is available with the TSX FPP 10 card, minimum version V1.8.
TLX DS COM PL7 xxE
345
FIPIO Agent
Periodic data exchange
Introduction Each FIPIO Agent PLC uses 64 consecutive %MW words to exchange the periodic data. l l
The 32 first words are reserved for transmitting the information to the manager.
The 32 remaining words are reserved for receiving the information.
Note: The status %MW words and the command %MW are not significant.
Viewing the exchanges
4
The following chart illustrates the exchanges between an FIPIO Agent and a TSX
Premium manager.
TSX 57 FIPIO bus manager
TSX 57 Agent
Language view of the manager
%IW\0.2.1\0.0.0
%IW\0.2.1\0.0.15
%IW\0.2.1\0.0.16
%IW\0.2.1\0.0.31
%QW\0.2.1\0.0.0
1
%QW\0.2.1\0.0.15
%QW\0.2.1\0.0.16
%QW\0.2.1\0.0.31
2
3
TSX 37 Agent
%IW\0.2.4\0.0.0
%IW\0.2.4\0.0.15
%IW\0.2.4\0.0.16
%IW\0.2.4\0.0.31
%QW\0.2.4\0.0.0
%QW\0.2.4\0.0.15
%QW\0.2.4\0.0.16
%QW\0.2.4\0.0.31
Language view of the agent
%MW...
%MW...+31
%MW...+32
%MW...+63
%MW...
%MW...+31
%MW...+32
%MW...+63
346
TLX DS COM PL7 xxE
FIPIO Agent
Special cases
Introduction A TSX Premium PLC which is registered as an FIPIO Agent can communicate with a TSX 47-107 or APRIL 5000 manager.
For these uses, an FIPIO Agent is registered on the bus by registering a standard profile to the connection point.
l l l
The registered standard profile is as follows:
Device family: STD_P
Standard: FED M32
Communicator: TSX FPP 10
Exchanges with a TSX 47-107
The following chart illustrates the exchanges between an FIPIO Agent and a TSX
47-107 manager.
Language view of the manager Language view of the agent
TSX 47-107 FIPIO bus manager RIWA1,0,0
RIWA1,0,15
RIWB1,0,16
2
3
4
1
TSX 57 Agent
TSX 37 Agent
RIWB1,0,31
ROWA1,0,0
ROWA1,0,15
ROWB1,0,16
ROWB1,0,31
RIWA4,0,0
RIWA4,0,15
RIWB4,0,16
RIWB4,0,31
ROWA4,0,0
ROWA4,0,15
ROWB4,0,16
ROWB4,0,31
%MW...
%MW...+31
%MW...+32
%MW...+63
%MW...
%MW...+31
%MW...+32
%MW...+63
TLX DS COM PL7 xxE
347
FIPIO Agent
Communication from an FIPIO Agent
Introduction
Addressing
A PLC registered as an FIPIO Agent can communicate: l l with the server of the bus manager, with the server of another FIPIO Agent.
The syntax of an address is as follows:
ADR#\0.1.4\SYS
The following table describes the addressing parameters:
Parameter
0.1.4
SYS
Description l l l
0: corresponds to the module sending the request
1: corresponds to the channel sending the request
4: corresponds to the destination connection point corresponds to the server address.
348
TLX DS COM PL7 xxE
Example
FIPIO Agent
Example of access the system of the different PLCs
Manager
ADR#\1.1.0\SYS
Accessing the manager server
0
ADR#\0.1.1\SYS
Accessing the
FIPIO Agent 1 server
1
ADR#\0.1.4\SYS
Accessing the
FIPIO Agent 4 server
ADR#\0.1.4\SYS
Accessing the
FIPIO Agent 4 server 4
63
The FIPIO Agent PLC at address 1 reads 10 words in the FIPIO Agent PLC at address 4.
READ_VAR(ADR#\0.1.4\SYS, ‘%MW’, 0, 10, %MW10:10, %MW100:4)
TLX DS COM PL7 xxE
349
FIPIO Agent
25.2
Configuration of FIPIO Agents
Introduction
Aim of this
Section
What's in this
Section?
This Section introduces the configuration principles for FIPIO Agents.
This Section contains the following Maps:
Topic
How to access the FIPIO Agent parameters via PCMCIA cards
FIPIO Agent configuration screen
Page
350
TLX DS COM PL7 xxE
FIPIO Agent
How to access the FIPIO Agent parameters via PCMCIA cards
Introduction
How to access the link
The creation of an application setting up FIPIO Agents requires the configuration of the communication channel of the PLC registered as an FIPIO Agent.
This operation describes how to access the configuration parameters of the FIPIO
Agent link via the PCMCIA TSX FPP card for TSX Micro/Premium PLCs.
The following table shows the procedure for accessing the FIPIO link:
Step
1
2
Action
Access the communication channel configuration screen.
From the dropdown menu, select the communication channel CHANNEL 1
Example
CHANNEL 1
CHANNEL 1
(Link not configured)
CHANNEL 1
(No PCMCIA submodule)
MAST
3 Select one of the following PCMCIA cards from the dropdown menu: l TSX FPP 10 PCMCIA CARD FIPIO
Example
CHANNEL 1
CHANNEL 1 (No PCMCIA submodule)
(Link not configured)
TSX SCP 114 PCMCIA CARD RS485 MP
TSX FPP 20 PCMCIA FIPWAY CARD
TSX FPP 200 PCMCIA FIPWAY CARD
TSX FPP 10 PCMCIA FIPIO CARD
TSX MBP 100 PCMCIA MODBUS+ CARD
TSX MDM 10 PCMCIA MODEM CARD
TLX DS COM PL7 xxE
351
FIPIO Agent
FIPIO Agent configuration screen
Introduction
Illustration
This screen, split into two areas, is used to register the communication channel and to configure the necessary parameters for a FIPIO Agent link.
The screen dedicated to communication looks like this:
1
2
TSX 3722 [POSITION 00.0..1]
Configuration
Designation: PROCESSOR 37222
CHANNEL 1
CHANNEL 1
FIPIO AGENT
TSX FPP 10 PCMCIA FIPIO CARD
MAST
Connection Point Address
Table Start Address %MW 0
1
Elements and functions
This table describes the different areas that make up the configuration screen:
Address Zone
1 common
2 specific
Function
See (See : PL7 Micro/Junior/Pro ; Communication applications
; Volume 1).
is used to select and complete the following parameters: l l connection point address the beginning address of the table.
the beginning address of the table.
This parameter indicates the address of the table to be reserved for the periodic data exchanges between the bus manager and the FIPIO Agent.
l l
The table has 64 words:
32 words for the inputs (%IW\p.2.c\m.i.r),
32 words for the outputs (%QW\p.2.c\m.i.r).
352
TLX DS COM PL7 xxE
25.3
Debugging FIPIO Agents
FIPIO Agent debugging screen
Introduction
Illustration
This screen, split into two areas, is used to debug a FIPIO Agent.
The screen dedicated to debugging looks like this:
FIPIO Agent
1
2
TSX 3722 [POSITION 00.0..1]
Debugging
Designation: PROCESSOR 37222 Version: 3.4
CHANNEL 1
CHANNEL 1
FIPIO
TSX FPP 10 PCMCIAFIPIO CARD
MAST
FIPIO function status
State of output %MW
Active
Active
Table addresses:
OUTPUT from: %MW300 to %MW331
INPUT from: %MW322 to %MW363
Access values via animation tables
DIAG...
DIAG...
Elements and functions
This table describes the different areas that make up the configuration screen:
Address Zone
1 common
2 specific
Function
See (See : PL7 Micro/Junior/Pro ; Communication applications
; Volume 1).
is used to access the debugging parameters of a FIPIO Agent.
No data can be accessed from this screen.
TLX DS COM PL7 xxE
353
FIPIO Agent
25.4
Language objects associated with the FIPIO
Agents
Introduction
Aim of this
Section
What's in this
Section?
This Section introduces the language objects associated with FIPIO Agents.
This Section contains the following Maps:
Topic
Language objects in implicit exchange
Language object for explicit exchange
Explicit exchange management and reports
Language objects associated with configuration
Page
354
TLX DS COM PL7 xxE
FIPIO Agent
Language objects in implicit exchange
Introduction
Bit objects
This page describes all the language objects for implicit exchange associated with the FIPIO communication agents that can be displayed or modified by the agent’s application program. (PL7 Micro/Junior/Pro ; Communication applications ; Volume
1)
The table below shows the different bit objects for implicit exchange.
Object (1) Function
%Ixy.MOD.ERR Module error bit
%Ixy.i.ERR
Channel error bit
Meaning
This bit set to 1, indicates a module error (at least one of the channels is faulty,…)
This bit set to 1, indicates a line fault.
Key
(1) xy.i Address l l l x: corresponds to the rack number (-) y: corresponds to the module number (0/1) i: corresponds to the channel number (1)
Word objects The table below shows the different word objects for implicit exchange.
Object (1)
%IWxy.i.0
Function Meaning
Agent function status Byte 0: l l l
= 16#01: IDLE function
= 16#02: RUN function
= 16 #03: STOP function
Strategy to be applied to outputs
Byte 1: l l l
= 16#01: safety
= 16#02: %MW value valid
= 16 #03: fallback
Key
(1) xy.i Address l l l x: corresponds to the rack number (-) y: corresponds to the module number (0/1) i: corresponds to the channel number (1)
TLX DS COM PL7 xxE
355
FIPIO Agent
Language object for explicit exchange
Introduction
Word objects
This page describes all the language objects for explicit exchange associated with the FIPIO communication agents that can be displayed or modified by the application program. (PL7 Micro/Junior/Pro ; Communication applications ; Volume
1)
The table below shows the different word objects for explicit exchange.
Object (1) Function
%MWxy.MOD.2
Module status
%MWxy.i.2
Standard channel status
Meaning l l l l l l x0 = 1: defective module x1 = 1: functional error (error between the processor and the module, adjustment or configuration error, …) x2 = 1: terminal block fault (not connected) x3 = 1: self-tests running x4 = 1: reserved x5 = 1: error in hardware or software configuration (the module present is not that declared in the configuration, the sub-modules are not compatible) x6 = 1: missing module x7 = 1: error in one of the sub-modules l l
Byte 0: l x0 = 1: input words are disabled when the manager is in RUN l x1 = 1: output words are disabled when the agent is in RUN l x4 = 1: internal error of TSX FPP 10 card or card not yet started by the manager l x5 = 1: configuration error (the configured data module is different from that present) l l x6 = 1: communication error on FIPIO x7 = 1: application error (%MW table overrun)
Byte 1: reserved
Key
(1) xy.i Address l l l x: corresponds to the rack number (-) y: corresponds to the module number (0/1) i: corresponds to the channel number (1)
356
TLX DS COM PL7 xxE
FIPIO Agent
Explicit exchange management and reports
Introduction
Word objects
This page describes all the language objects that manage explicit exchanges. (See
: PL7 Micro/Junior/Pro ; Communication applications ; Volume 1)
The table below shows the different word objects for the management of explicit exchanges.
Object (1)
%MWxy.MOD.0
%MWxy.MOD.1
%MWxy.i.0
%MWxy.i.1
Function
Module exchanges in progress
Module report
Channel report
Meaning l l l x0 = 1: reading status in progress x1 = 1: sending of command parameters to the communication module x2 = 1: sending of adjustment parameters to the communication module l l x1 = 0: command parameters received and accepted by the module x2 = 0: adjustment parameters received and accepted by the module
Channel exchanges in progress l l l x0 = 1: reading status in progress x1 = 1: sending of command parameters to the communication channel x2 = 1: sending of adjustment parameters to the communication channel l l x1 = 0: command parameters received and accepted by the communication channel x2 = 0: adjustment parameters received and accepted by the communication channel
Key
(1) xy.i address l l l x: corresponds to the rack number (-) y: corresponds to the module number (0/1) i: corresponds to the channel number (1)
TLX DS COM PL7 xxE
357
FIPIO Agent
Language objects associated with configuration
Introduction
Internal constants
This page describes all the configuration language objects associated with the
FIPIO communication agents that can be displayed by the agent application program.
The following table describes the internal constants:
Object Function
%KWxy.i.0
Type
%KWxy.i.1
Reserved
%KWxy.i.2
Connection point address
%KWxy.i.3
Table start address
Meaning
Byte 0 = 16#09: for the FIPIO Agent function
-
Byte 0 = 16#01 to 16#7F: corresponds to addresses
1 to 127
Byte 0: least significant byte of the address
Byte 1: most significant byte of the address
358
TLX DS COM PL7 xxE
Index
A
Accessible Functions
Accessing configuration
Accessing the configuration
Accessing the configuration screen
Accessing the debugging screen
Accessing the diagnostics screen, 297
Addressing
Adjustment mode
Agent
B
Bus properties
C
TLX DS COM PL7 xx
Characteristics
Communication channel test
Communication function
Compatibility
compatibility
Configuration
Standard profiles (FIPIO), 321
Configuration Access
Configuration Parameters
Configuration parameters
Configuration Screen
359
Index
Configuration screen
Confirmation
D
Data exchange
Debug parameters
Debug screen
Debugging
Standard profiles (FIPIO), 327
Debugging Parameters
Debugging parameters
Debugging screen
Diagnostics
Driver
E
Error processing using the program, 284
360
Exchange management
Explicit exchange
Standard profiles (FIPIO), 338
F
G
General
I
Implicit exchange
Standard profiles (FIPIO), 336
implicit exchange
Input/output management
TLX DS COM PL7 xx
Introduction
Standard profiles (FIPIO), 316
L
Language objects
Standard profiles (FIPIO), 332
M
Management of exchanges
Management parameters
O
Operating Mode
Operating mode
P
Performance
TLX DS COM PL7 xx
Programming
R
Read mode
Report
S
Set-up
Standard profiles
system objects
W
Write mode
X
X-WAY
Index
361
Index
362
TLX DS COM PL7 xx
Скачать
Реклама