Date: Fri, 29 Mar 2024 08:28:41 +0100 (CET) Message-ID: <1086681720.111546.1711697321874@srvdoc.doc.ipesoft.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_111545_1225876223.1711697321874" ------=_Part_111545_1225876223.1711697321874 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Supported device types and v=
ersions
Communicat=
ion line configuration
Communication station configuration
DB-Net initialization
I/O tag configuration
Errors and problems
Literature
Changes=
and modifications
Document =
revisions
The protocol supports data acquisition using devices from the AMiT compa= ny (ADiS modular control system and ART267, ART4000, AMiRiS, and AMAP compa= tible control systems and others) via a DB-Net communication network. Commu= nication requires the installation of the ATOUCH32 driver to communicate in= a DB-Net ATOUCH32 network (you can download it at http://www.amit.cz). C= ommunication was tested and tuned for the ATOUCH32 driver of V2.10, V2.30, = V2.40, V2.60, V2.90, and V3.30 versions.
Limitations: The protocol does not support database var= iables of "self station", i.e. on the computer with ATOUCH32 driver running= but allows to read/write variables on process stations. The DB-Net driver = can be used by just one application (in our case the D2000 KOM process) at the same time.
When using the older versions of ATOUCH32 V2.x, just one communication l= ine for DB-Net communication must be configured. ATOUCH32 V3.x versions ena= ble so-called multithreading. It means, you may connect more lines, which w= ill communicate in parallel, to ATOUCH32 and speed up the communication. Th= e driver must be initialized only by one line (see "Init File" parameter, note 2). However, the rule = that all lines must be configured within one KOM process on one computer st= ill applies. This feature may be used in D2000 V9.00.021 rel.021 and higher= .
Communication line - configuration dialog box - the Pr=
otocol parameter tab.
Parameters defined in the field have an effect on some optional protocol p=
arameters. The following line protocol parameters can be defined:
Table 1
Full name | Description | Units / size | Default value |
---|---|---|---|
HW Init File
|
Full path to the file containing the DB-Net conf=
iguration. Note 1: If the line protocol parameter INIFILE i= s not specified (an empty string), then the station protocol parameters des= cribed below must be configured correctly for all stations. The parameters = of DB-Net IP can be configured only by "Init File". Note 2= strong>: If you do not want so that the line initialized ATOUCH32 in the mu= ltithread mode, use "---", i.e. 3x "minus" character. One line within the <= a href=3D"/display/D2DOCV22EN/D2000+Kom">D2000 KOM process must contain= the path to the existing init file. It, then, executes the initialization = for all other lines. |
- |
Communication station - configuration dialog box - tab P=
rotocol parameter.
Parameters defined in the field influence some optional protocol parameter=
s. The following station protocol parameters can be defined:
Table 2
Full name | Meaning | Unit/ size | Default value |
---|---|---|---|
My Station
|
Address of "self station" (PC with ATOUCH32 driv= er running) | - | 31 |
COM Port
|
COM port used for the communication | - | 1 |
COM Speed
|
Communication baud rate. | - | 19200 |
Max. Transactions Error
|
The maximum number of consecutive read commands = which have to fail for the communication with the station to be marked as f= ailed and the status of the station to be set to StCOMERR. If the number of= failed readings of I/O tags exceeds the double of this value, the reading = of the next I/O tags will be stopped. The purpose is to avoid communication= delays due to non-working stations (the station is considered to be comple= tely inaccessible). | - | 10 |
Full Debug
|
High level of line debug messages - trace messag= es contain details about received values of I/O tags. | - | False |
Enable Matrix Read
|
The reading of matrix variables will be optimize= d for slow networks (e.g. GPRS). Reading of variables with matrix types (IN= T MATRIX, LONG MATRIX, FLOAT MATRIX a DBNETTIME MATRIX) will be optimized. = If multiple I/O tags share the same WID<= /a> and type, only a single read req= uest is generated and it incorporates a range of rows and columns of all th= ese I/O tags. | - | False |
When starting, the DB-Net driver requires to get the configuration file = or string containing the DB-Net network configuration for a particular appl= ication. If you use the communication via standard COM port, it is possible= to avoid creating the configuration file on disk using the My Stat= ion, COM Port, and COM Speed sta= tion protocol parameters which must be configured for one of the stations.<= /p>
If the Init File line protocol parameter is specified f=
or a line (at least one), then the My Station, COM=
Port, and COM Speed protocol parameters wil=
l be ignored on all the stations. Instead, the configuration file on the di=
sk (the path of which is defined by the Init File line pro=
tocol parameter) will be used.
For further information on the file contents, see the ATOUCH32 online help=
.
Example: configuration file contents:
[General] MyStation=3D0 UDP.MyPort=3D222 UDP.MyPassword=3D111222333 [COM] Com=3D2 Speed=3D38400 Station=3D1 Station=3D2 Station=3D4 Station=3D13 [COM] Com=3D3 Speed=3D9600 OfsNet=3D32 Station=3D33 Station=3D34 Station=3D36 Station=3D45=20 [UDP] Address=3D192.168.168.1 Password=3D444555666 Offset=3D10 Station=3D10 Station=3D20 Station=3D30 [UDP] Address=3D"segment100.firmaXY.cz" Password=3D777888999 Port=3D333 Offset=3D100 Timeout=3D5000 Station=3D105 Station=3D106 Station=3D107
Possible I/O tag types: Ai, Ao, Ci, Co, Di, Do, TxtI, TxtO, TiA,= ToA, TiR, ToR.
I/O tag address consists of:
When starting or during communication, the following error messages can = occur. To make the problem identification easier, set the communication tra= cking at least to the level Monitor (the best is to tempor= arily set it to Monitor & Disk). When you set the= option Monitor & Disk, a file "line_name.LOG" will be= created in the application subdirectory TRACE, which will= contain all debug and error logs. If you are unable to correct the error a= nd the problems still persist, please contact IPESOFT's technical sup= port.
Error: | DB-Net Station Address Error - 'Stat= ionName', Address : 'StationAddress' |
Solution: | Invalid station address - check the Addr= ess tab in the communication station configuration dialog box (in the D2000 CNF&nb= sp;process) and eventually save the station configuration and restart the <= a href=3D"/display/D2DOCV22EN/D2000+Kom">D2000 KOM process. |
Error: | DB-Net Point Address Error - 'PointN= ame', Address : 'PointAddress' |
Solution: | Invalid I/O tag address - check the Addr= ess tab in the I/O tag configuration dialog box (in the D2000 CNF process) an= d eventually save the I/O tag configuration. |
Error: | DB-Net ATOUCH32 ERROR - 0xXY - = AtchInitFromStringA |
Solution: | Error when calling the ATOUCH32 function AtchIni= tFromStringA - check the station configuration and protocol parameters. Dur= ing the start, the D2000 KOM = process displays the configuration string (the communication tracing level = at least Monitor must be enabled) - please check if it cor= responds to your requirements. |
Error: | DB-Net ERROR - CreateSemaphore - Err= Nr - Error description |
Solution: | System error of Windows API call. Restart the op= erating system. |
Error: | DB-Net ATOUCH32 ERROR - 0xXY - =
AtchReqGetVariable DB-Net ATOUCH32 ERROR - 0xXY - AtchReqPutVariable |
Solution: | Error when calling the ATOUCH32 functions AtchRe= qGetVariable or AtchReqGetVariable for reading/writing a DB-Net database va= riable value. Previous communication tracing logs allow us to detect which = I/O tag is in trouble and then its configuration can be checked. |
Error: | DB-Net ERROR - Reading 'PointName' - TNRES=3D0 ! DB-Net ERROR - Reading 'PointName' - TNRES=3D1 (reading on progre= ss) ! DB-Net ERROR - Reading 'PointName' - TNRES=3DInvalid ! DB-Net ERROR - Writing 'PointName' - TNRES=3D0 ! DB-Net ERROR - Writing 'PointName' - TNRES=3D1 (reading on progre= ss) ! DB-Net ERROR - Writing 'PointName' - TNRES=3DInvalid != td> |
Solution: | Transaction errors of reading/writing the DB-Net= database variable. They should not occur. |
Error: | DB-Net ERROR - Reading 'PointName' - TNRES=3D4 (station not responded) ! DB-Net ERROR - Writing 'PointName' - TNRES=3D4 (station not respo= nded) ! |
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=3D4 (station responded) ! DB-Net ERROR - Writing 'PointName' - TNRES=3D4 (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 a variable, which does not exist in a device. Chec= k the configuration of the corresponding I/O tag and compare it with the lo= g from the AMiT PSP3 software tool. |
Error: | DB-Net ATOUCH32 ERROR - 0xXY - = AtchInitFromFileA |
Solution: | Error when calling the ATOUCH32 function AtchIni= tFromFileA. Check if the protocol parameter INIFILE is configured just for = one station and its value is a name of an existing file on a disk. |
Related pages: