Lenze EMF2102IB - Manual (Page 11)

Technical data
3-3
L
_^ONMObk
3.5 Communication times
The time required for communication can be displayed as a sequence of processing steps (with
corresponding times).
Step Explanation
t0 User program in host starts request to the controller (e.g. controller enable with C0040=1)
t1 Software driver (e.g. LECOM-S5) in host converts request data into LECOM-A/B protocol V2.0 and starts the transmission.
t2 Serial data transfer to the controller (telegram time)
t3 Data receipt of the controller: Processing of request and start of response
t4 Response data to host are being transmitted (telegram time)
t5 Software driver in host evaluates the response, i.e. the response is converted into the format of the user program.
t6 Application program in host gets the result
The time sections t2, t4 and t3 are described in detail in the following:
Telegram time (t2 + t4)
The telegram time comprises the serial communication from the host to the controller (t2) and the
corresponding response from the controller (t4). The time depends on the telegram type and the
baud rate set under C0125.
Baud rate [bits/s] (C0125)
1200 2400 4800 9600 19200
Single character transmission time [ms]
(1 character = 10 bit; see chapter 3.2) 8.4 4.2 2.1 1 0.52
Telegram type SEND (sends data to drive):
Baud rate [bits/s] (C0125)
1200 2400 4800 9600 19200
t2: Standard [ms] (parameter value = 9 characters) 150 75 37.5 18.8 9.4
Addition for extended addressing [ms] 41.6 20.8 10.4 5.2 2.6
Telegram type RECEIVE (reads data from drive):
Baud rate [bits/s]
1200 2400 4800 9600 19200
Standard [= t4]
(Parameter value = 9 characters) [ms] 166.7 83.3 41.7 20.8 10.4
Addition for extended addressing [ms] 83.3 41.7 20.8 10.4 5.2
If more or fewer than 9 characters are transmitted as telegram data, take the corresponding
character-transmission times into account.
Show/Hide Bookmarks