SAP51D-A-G1-R datasheet(35/67 Pages) RENESAS

35 / 67 page

SAP51 / SAP5S Datasheet

January 28, 2016

• The input data, sampled at the slave with the lowest slave address in the network, is sent back to the

master without any delay. Thus, the input data cycle image is fully captured at the end of an AS-i cycle, just

as in networks without any Synchronous Data I/O Mode slaves. In other words, the input data sampling

point has simply moved to the beginning of the AS-i cycle for all Synchronous Data I/O Mode slaves.

• If the Synchronous Data IO Mode is enabled through EEPROM setting (Synchronous_Data_IO = ‘1’,

P2_Sync_Activation = ‘0’), the first DEXG call that is received by a particular slave after the activation of the

Data Port (Data_Exchange_Disable flag was cleared by a WPAR call) is processed as in standard

operation. This is to capture valid input data for the first slave response and to activate the outputs as

quickly as possible.

• The Data I/O operation is repeated together with the I/O cycle of the other Synchronous Data I/O Mode

slaves in the network at the common trigger event. As a result, the particular slave is now in the

Synchronous Data I/O Mode.

• If the P2_Sync_Activation flag is set to ‘1,’ the Synchronous Data IO Mode can be activated or deactivated

during normal operation by sending Write_Parameter calls containing the appropriate value in P2 (see

Table 5.12).

• If the P2 output register changes from ‘1’ to ‘0,’ the Synchronous Data IO Mode is immediately enabled.

Actual synchronous data I/O operation is reached after reception of the next DEXG call addressing the

slave and the occurrence of the common trigger event. As in standard operation (Synchronous Data IO

Mode is activated by the EEPROM setting), the first DEXG call still processes a data IO operation

immediately. This is to capture valid input data for the slave response and to activate the outputs as quickly

as possible.

• The Data I/O operation is repeated together with the I/O cycle of the other Synchronous Data I/O Mode

slaves in the network at the common trigger event. As a result, the particular slave is now in the

Synchronous Data I/O Mode.

• If the P2 output register changes from ‘0’ to ‘1,’ the Synchronous Data IO Mode is deactivated and disabled

immediately. If a synchronous data I/O event was already scheduled but not yet processed (armed but not

fired) before the Synchronous Data I/O Mode has become deactivated, the associated data output value is

lost.

• If P2 changes back to ‘0,’ reactivation of the Synchronous Data I/O Mode occurs in same manner as

described above.

• To avoid a general suppression of Data I/O in the special case that a slave in Synchronous Data I/O Mode

receives DEXG calls only to its own address (i.e., employment of a handheld programming device), the

Synchronous Data I/O Mode becomes deactivated if the SAP5 receives three consecutive DEXG calls to its

own slave address. The SAP5 resumes to Synchronous Data I/O Mode operation after it has observed a

DEXG call to a slave address that is different from its own. The reactivation of the Synchronous Data I/O

Mode is handled in the same manner for the first DEXG call after activation of the Data Port or after

activation of the Synchronous Data I/O Mode by P2 changing to ‘0’ (see description above).

If any of the data ports D0 to D3 is configured as a pure output (designated as “OUT” in Table 5.14), the SAP5

returns the output data that was received from the master immediately in its slave response. Since there is no

input function available at such ports, the return value is independent from a possible Synchronous Data I/O

Mode operation.

SAP51D-A-G1-R 数据表(PDF) 35 Page - Renesas Technology Corp

SAP51D-A-G1-R 数据表(HTML) 35 Page - Renesas Technology Corp

Html Pages

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67

数据表下载