Siemens SPC3 Specifications download pdf (Page 26)

Introduction To ProfiBus DP

__________________________________________________________________

_______________________________________________________________________________________

Acromag, Inc. Tel:248-624-1541 Fax:248-624-9234 Email:sales@acromag.com http://www.acromag.com

In general, these bytes are user-defined for specific DP Slave

device/module related parameters. They can be used to transmit startup

information or for adjusting values or levels and generally take the place of

DIP switches. Their meaning and range are application specific. Because

the Acromag modules use the SPC3 ASIC, DU Byte 8 is defined as follows,

and the remaining bytes are user-defined.

Set_Prm Telegram DU Byte 8: Spec_User_Prm_Byte (SPC3 ASIC)

Bit Name Description Default Status

0 Dis_Startbit Used to disable start bit monitoring in the

receiver (1=disabled).

Dis_Startbit = 1

(Disabled)

1 Dis_Stopbit Used to disable stop bit monitoring in the

receiver (1=disabled).

Dis_Stopbit = 0

(Enabled)

2 WD_Base Used to specify the time base with which the

watchdog is pulsed (0=10ms, 1=1ms)

WD_Base = 0

(Time base is 10ms)

3-7

Reserved

Not Used – Set to 0. 0

Parameterization Telegram DU Bytes 9-244 (Optional User_Prm_Data)

76543210

XXXXXXXX

User_Prm_Data

The first 7 bytes of Set_Prm are evaluated by the slave’s ASIC (without

user-prm_data) and in accordance with the standard, or the first 8 bytes

(with Spec_user_prm_data). For Acromag slaves, the eighth byte is used

for SPC3 related characteristics. The remaining bytes are available to the

application.

The response of a slave to the parameterization telegram is “E5H” (a

short acknowledge). After its parameters are set, the slave proceeds to the

I/O Configuration State.

The parameter Status can be tested to indicate the success or failure of

the parameterization telegram with possible values of: OK, DS, NA, RS, RR,

UE, and RE.

After parameterization (Set_Prm), the slave awaits the configuration

telegram (Chk_Cfg). This telegram specifies the number of input and output

bytes that are to be exchanged in each telegram cycle with the slave. The

configuration telegram also causes the slave to check the configuration

which was sent against the stored configuration. A slave awaiting Chk_Cfg

will only accept the Set_Prm, Slave_Diag, or Get_Cfg telegrams.

Chk_Cfg Telegram – SAP 62

The Chk_Cfg configuration telegram causes a slave to check the

configuration which was sent, against the stored configuration. If the slave

detects a conflict when it compares the sent information with the entries

originating from the GSD file, it will report the incorrect configuration to the

master when asked for diagnostics later and will not proceed to exchange

data with the master. A slave will acknowledge a configuration telegram with

“E5H” (short acknowledge).

I/O Configuration

1 2 ... 21 22 23 24 25 26 27 28 29 30 31 ... 37 38

Comments to this Manuals

No comments

Siemens SPC3 Specifications Page 26

Comments to this Manuals

Related products and manuals for Networking Siemens SPC3