Bosch DCN Next Generation Manuale Utente Pagina 26

  • Scaricare
  • Aggiungi ai miei manuali
  • Stampa
  • Pagina
    / 296
  • Indice
  • SEGNALIBRI
  • Valutato. / 5. Basato su recensioni clienti
Vedere la pagina 25
DCN Next Generation Open Interface Release 2.4 General
en | 26
Bosch Communications Systems | 2007 February | SRS_INF | Du010933
The packet tells the transmitting side of the connection that the last transmitted packet is
received with errors (checksum failure).
Note that when the CCU is expecting the header of a packet, all received data will be ignored
till the complete header is seen. This can happen when the length of a packet is corrupted.
(e.g. actual length sent equals 1000 bytes, length received 10 bytes. Result is a checksum
failure and a lot of extra bytes not belonging to a packet).
4.2 Ethernet Protocol Description
4.2.1 Open interface protocol
4.2.1.1 Set-up a connection
After DCN NG has been started, the network controller listens to port 9451. The set-up of the
TCP/IP connection must originate from your system using the IP address of the network
controller and port 9451. The connection between the DCN NG System and your System is
based on a stream connection. This implies that messages may be transferred using multiple
packets.
4.2.1.2 Heartbeat
After the connection between your system and DCN NG has been established, the network
controller of DCN NG starts the heartbeat checks of your system. The network controller
checks if a message is received within 15 seconds after the last message. When the time
between two messages is more than 15 seconds, the network controller considers the
connection to be broken and closes the TCP/IP connection to your system.
It is advised to also run heartbeat checks of DCN NG on your system. To signal that the
connection is still present, you must transmit a "MESSAGETYPE_OIP_KeepAlive" message
(refer to section 3.3.1) to the network controller every 5 seconds when no other messages
are ready for transmission.
4.2.1.3 Timing values
This section presents the different value and time-limits needed for handling the protocol.
Description Value
Transmit timeout for transmission heartbeat message 5 seconds
Check timeout to verify whether a message is received (reset after each
message reception)
15 seconds
Maximum command response time 10 seconds
Minimum message size (message-type + length) 8 bytes
Maximum message size 8000 bytes
4.3 Remote function execution
Beside the protocol used for transmitting the data between the remote controller and the
CCU, the CCU executes the remote function requests. In this section the execution of the
remote functions is explained to give an overview about the generation of updates during the
execution.
The remote controller can sent a remote function request to the CCU. After the transmission
the remote controller must wait for the response coming from the CCU.
Vedere la pagina 25
1 2 ... 21 22 23 24 25 26 27 28 29 30 31 ... 295 296

Commenti su questo manuale

Nessun commento