...
I/O tag address consists of:
WID - the numerical name of the variable - it is uniquely unique within the DB-Net network. Permitted range is 0..65500, the value is allocated by the PSP3 tool or DetStudio.Kotva wid wid
Type - value type of the variable - it can be the INT, LONG, FLOAT types and the INT MATRIX, LONG MATRIX or FLOAT MATRIX types. The INT and INT MATRIX types are 16 bit wide; and if they are configured as Ai, Ao, they are interpreted as signed numbers; and if they are configured as Ci, Co, they are interpreted as unsigned numbers.Kotva typ typ
LONG and LONG MATRIX types (32 bit wide) configured as Ai, Ao are interpreted as signed numbers and if they are configured as Ci, Co, they are interpreted as unsigned numbers. The FLOAT and FLOAT MATRIX types are 32-bit float numbers within the range from ±10-36 to ±1038. DBNETTIME is LONG type interpreted as absolute time in DBNet format (number of seconds from 1-1-1980 0:0:0). INT MATRIX can be set for value types of TxtI and TxtO. The row from matrix INT is interpreted as text, each INT element of the matrix represents one symbol. INT and LONG types can be represented as relative time - i.e. a number of seconds.
- Row, Column - value position in matrix types, the first row or column has zero value.
- Row count, Column count - size of matrix. In case of value types TxtI and TxtO there can be set , only the column count can be specified, which is the text length. For another other value types, the implicit value of row count and column count is 1. If the configured row count and /column count exceeds is above 1, it saves the values of the whole matrix or part of the matrix are read into the target column of structure. A part of matrix [Row, Column .. Row+ Row count -1, Column+ Column count - 1] will be read.
Example: Row=1, Column=2, Row count=20, Column count=30. Rows 1 to 20, columns 2 to 31 are read, i.e. part of matrix [1,2 .. 20, 31]. - Bit - bit number for the Di and Dout value types. It can be within the range of 0 - 15 for the INT and INT MATRIX types or within the range of 0 - 31 for the LONG and LONG MATRIX types.
...
When starting or during the communication, there could be occurred the following error reports. To make the problem identification easier, set the communication tracking at least to the level Monitor (the best is to temporary temporarily set to Monitor & Disk). When you set the option Monitor & Disk, there will create the file "line_name.LOG" in the application subdirectory TRACE, that which will contain all debug and error logs. If the problems still persist, please contact the IPESOFT's technical support.
| Error: | DB-Net Station Address Error - 'StationName', Address : 'StationAddress' |
| Solution: | Invalid station address - check the Address tab in the communication station configuration dialog box (in the process D2000 CNF) and eventually save the station configuration and restart the process D2000 KOM. |
| Error: | DB-Net Point Address Error - 'PointName', Address : 'PointAddress' |
| Solution: | Invalid I/O tag address - check the Address tab in the I/O tag configuration dialog box (in the process D2000 CNF) and eventually save the I/O tag configuration. |
| Error: | DB-Net ATOUCH32 ERROR - 0xXY - AtchInitFromStringA |
| Solution: | Error when calling the ATOUCH32 function AtchInitFromStringA - check the station configuration and protocol parameters. During the start, the process D2000 KOM shows the configuration string pattern (the communication tracing level at least Monitor must be enabled) and check if meet required state. |
| Error: | DB-Net ERROR - CreateSemaphore - ErrNr - Error description |
| Solution: | System error of Windows API call. Restart the operating system. |
| Error: | DB-Net ATOUCH32 ERROR - 0xXY - AtchReqGetVariable DB-Net ATOUCH32 ERROR - 0xXY - AtchReqPutVariable |
| Solution: | Error when calling the ATOUCH32 functions AtchReqGetVariable or AtchReqGetVariable for reading /writing a DB-Net database variable value. Previous communication tracing logs allow us to detect which I/O tag is in troubles and then check its configuration. |
| Error: | DB-Net ERROR - Reading 'PointName' - TNRES=0 ! DB-Net ERROR - Reading 'PointName' - TNRES=1 (reading on progress) ! DB-Net ERROR - Reading 'PointName' - TNRES=Invalid ! DB-Net ERROR - Writing 'PointName' - TNRES=0 ! DB-Net ERROR - Writing 'PointName' - TNRES=1 (reading on progress) ! DB-Net ERROR - Writing 'PointName' - TNRES=Invalid ! |
| Solution: | Transaction errors of reading/writing the DB-Net database variable. They couldn't occur. |
| Error: | DB-Net ERROR - Reading 'PointName' - TNRES=4 (station not responded) ! DB-Net ERROR - Writing 'PointName' - TNRES=4 (station not responded) ! |
| Solution: | Transaction errors of reading/writing the DB-Net database variable. Station The station doesn't response respond because it is switched off, a problem with the communication wire or an a configuration error (e.g. wrong baud rate, address or port). The error could occur sporadically, especially at reading. |
| Error: | DB-Net ERROR - Reading 'PointName' - TNRES=4 (station responded) ! DB-Net ERROR - Writing 'PointName' - TNRES=4 (station responded) ! |
| Solution: | Transaction errors of reading/writing the DB-Net database variable. The station responded with an error. Probably it is an attempt to read or write the variable, which has no mirror in a given device. Check the configuration of the corresponding I/O tag and compare it with the log from the AMiT PSP3 software tool. |
| Error: | DB-Net ATOUCH32 ERROR - 0xXY - AtchInitFromFileA |
| Solution: | Error when calling the ATOUCH32 function AtchInitFromFileA. Check if the protocol parameter INIFILE is configured just for one station and is pointed to an existing file on disk. |
| Kotva | ||||
|---|---|---|---|---|
|
...
- January 23rd, 2004 – added protocol parameter INIFILE and the possibility to configure UDP and MODEM communication.
- September 6th, 2006 - TxtI, TxtO, TiA, and ToA types added. New entry for station and line protocol parameters.
- January 8th, 2008 - changes in the configuration of matrixes, DBNETTIME, target column.
- May 22nd, 2009 - relation times added.
- October 25, 2012 - multithread for ATOUCH32.
...
- Ver. 1.0 - March 26th 2002 - creating of document
- Ver. 1.1 – January 23rd 2004 – document corrections after changes in the initialization
- Ver. 1.2 - September 6th 2006 - updating
- Ver. 1.3 - January 8th, 2008 - updating
- Ver. 1.4 - May 22nd, 2009 - updating
- Ver. 1.5 - October 1st, 2009 - parameter "Max. Transactions Error"
- Ver. 1.6 - October 25, 2012 - updating
...