Citect for Windows Driver Specification DanBuss DNIP Driver

4.11 Driver Error Help
The following entries should be included in the Citect ProtErr.DBF spec file.
Driver Design Specification
PROTOCOL MASK ERROR MESSAGE REFERENCE ACTION COMMENT
DANBUSS 101 Cache Memory
Allocation
Error
4.12 Debug Messages
Shows the outgoing/incoming data packets in hex. If error report level is set to ERROR the driver
will report errors, i.e. if any point is asked for that is not configured in the device. The format is of
Undefined Point: 013:001/AI02.7, which means device 013:001, Analog Input 2, parameter 7 (this is
the same address that is entered in the tag variable database, AI02.7 or AI2.7). If TagDebugMode is
off in CITECT.INI then all tags that are asked for in one request (up to 36) is shown. To see which
one that has an invalid address, the TagDebugMode must be set on. The DanBuss protocol does
not return any value at all if only one fail.
4.13 Stats Special Counters
Number Label Purpose/Meaning of this counter
0 DCB Requests Number of DCB requests (accumulated).
1 Inbuffer max Maximum used bytes in the input buffer for the CPU service function
(before they have been handled by the packet receive routine).
2 Unrequested packets Packets received that was not asked for.
3 Packets received Total number of received packets.
4 Cache hits Number of DCB’s that has been read directly from the Cache (did
not cause a physical read).
5 Cache hit rate (%) The hit rate (Cache hits / DCB Requests x 100).
6 Sent DanBuss packets Number of sent packets.
7 Resent packets Resents packets caused by timeout.
8 Cache alloc's Number of allocated Cache Elements (accumulated).
9 Cache elements Momentary number of Cache Elements. Is equal to the number of
DCB requests within the CacheLiveTime (default 30 seconds)
10 Trashed elements Number of Cache Elements (Read or Write) that has been deleted
due to timeout of the CacheLiveTime (default 30 seconds), before
the outstanding request has returned from DANBUSS.
11 Outstanding DCB's The momentary value of outstanding DCB’s that is serviced by the
driver (default max 75).
12 Max outst. DCB's The top value of DCB’s that has been requested by Citect to be
serviced by the driver.
13 Phys. read time (ms) The time DANBUSS consumed to service the last request. The
requests are blocked together by the driver if possible (max 36
varables can be read in a single request).
14 ScanList reads Number of blocked reads that has been requested of the total sent
DanBuss DNIP.doc 24