Crocus CNV Configuration attributes
Reference manual 91
6.4.2 RS530, V35 and V36 interface configuration attributes
crocusIfConv<2m/Nx64><Tt/Cv>/<dteInterface>/rtsControl default: external
Use the rtsControl attribute to define which device will activate the RTS signal.
Normal operation requires the RTS signal (circuit 105) to be active before the Crocus CNV activates its
data transfer state, as indicated by the CTS signal (circuit 106). Therefore, make sure the RTS signal is
activated either by the application or by the Crocus CNV.
If RTS control is
set to …
the RTS signal is
activated by …
Use this setting in case …
external the application. the application has to be in command of the RTS signal.
internal the Crocus CNV. the application is not able to activate the RTS signal.
crocusIfConv<2m/Nx64><Tt/Cv>/<dteInterface>/ctsDelay default: 0 ms
Use the ctsDelay attribute to define the delay between the active edge of the incoming RTS signal and the
active edge of the outgoing CTS signal.
The delays that can be selected are: 0 ms, 4 ms, 16 ms and 64 ms.
If RTS control is set to … then …
external a delay is provided between:
• the moment the active edge of the RTS signal comes in
• the moment the active edge of the outgoing CTS signal is generated.
internal no delay is provided. The CTS signal is always on.
Between the moment the RTS signal drops and the moment the CTS signal drops, no delay is provided.
crocusIfConv<2m/Nx64><Tt/Cv>/<dteInterface>/tests default: disabled
Use the tests attribute to enable or disable the interface tests.
The interface tests of the Crocus CNV are useful to trace possible problems. These interface tests are
initiated by the application via the interface. If these tests are not supported by the application, it is
possible that an undesired test is activated resulting in a disturbance of the data transfer. Therefore, they
are disabled by default.
The available interface tests are:
• interfaceAl: interface Analogue Loop
• interfaceRdl: interface Remote Digital Loop
To Next Page
Loading...