15.07.2013 Views

Automatic control function programming manual ladder language

Automatic control function programming manual ladder language

Automatic control function programming manual ladder language

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Storage of the reception buffer<br />

@ Buffer start address<br />

Written by the user<br />

programme<br />

Written by<br />

the monitor<br />

Programming error causing a CPU fault<br />

Access to a prohibited address:<br />

- &datagram parameter error,<br />

- &datagram+size outside authorised area.<br />

15.4.3 Programming Rules<br />

15 - 32 en-938846/7<br />

Buffer size<br />

(1 word)<br />

Request size<br />

(1 word)<br />

Answer<br />

(see Sec. 15.3)<br />

1 word<br />

128 bytes<br />

max.<br />

For rational organisation of a programme including exchanges by protocol, follow the recommendations given below.<br />

! CAUTION<br />

Functions unito(), uniti(), neto() and neti() must be programmed in a background task<br />

(%TF0 to %TF15).<br />

The size of a request must not be zero or greater than 128 bytes (except for the READ_BLOCK and WRITE_BLOCK<br />

requests).<br />

REMARK Sixteen exchange buffers are accessible to the user programme, allowing a maximum<br />

of sixteen requests to be sent each RTC cycle.<br />

Consecutive transmission of several requests on the same port without acknowledgement of the answers causes the<br />

loss of one or more answer codes.<br />

It is important to:<br />

- programme transmission to the server followed by reception of the answer on a given port before <strong>programming</strong> any<br />

other transmission, or<br />

- use different ports for each transmission/reception command.<br />

For the servers, the concept of queuing may cause an offset in the timing of request processing. This is because the<br />

load on the different servers may mean that the requests are not processed in the order in which they were sent.<br />

To ensure correct timing of request processing, make sure the answer is received before sending the next request on<br />

a port.<br />

Buffer size

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!