...
| 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 D2000 CNF process) and eventually save the station configuration and restart the D2000 KOM process. |
| 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 process) 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 process displays the configuration string pattern (the communication tracing level at least Monitor must be enabled) and - please check if meet required stateit corresponds to your requirements. |
| 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 can be checked. |
| 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 should not 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. The station doesn't respond because it is switched off, there is a problem with the communication wire or 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 a variable, which has no mirror does not exist 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 its value is a name of an existing file on a disk. |
| Kotva | ||||
|---|---|---|---|---|
|
...
| Kotva | ||||
|---|---|---|---|---|
|
...
- 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
...