Porovnávané verzie

Stará verzia 5

changes.mady.by.user D2000 Dev Team

Uložené

porovnané s

Nová verzia Aktuálny

changes.mady.by.user D2000 Dev Team

Uložené

Kľúč

  • Tento riadok sa pridal
  • Riadok je odstránený.
  • Formátovanie sa zmenilo.

...

Limitations: The protocol does not support database variables of "self station", i.e., on the computer with the ATOUCH32 driver running, but allows to readreading/write writing 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 line for DB-Net communication must be configured. ATOUCH32 V3.x versions enable so-called multithreading. It means , you may connect more lines, which will communicate in parallel, to ATOUCH32 and speed up the communication. The 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 still applies. This feature may be used in D2000 V9.00.021 rel.021 and higher.

Note: If it is necessary to create multiple lines (where communication with AMiT is via UDP and the IP address is configured in the UDP section in the initialization file), each line must be configured using a separate KOM process.
The UDP port used on the AmiT device side is defined by the Port parameter in the [UDP] section; port 59 is used by default.
The UDP port used on the Windows side is defined by the UDP.MyPort parameter in the [General] section, a dynamic port is used by default, which is configured with the value 0.

Example of a dbnet.ini file with a network-connected AMiT:

[General]
MyStation=0

[UDP]
Address=172.16.1.20
Station=1

Kotva
komunikacna_linka0
komunikacna_linka0
Communication line configuration

...

Full nameDescriptionUnits / sizeDefault value
Kotva
if
if
HW Init File
Full path to the file containing the DB-Net configuration.

Note 1: If the line protocol parameter INIFILE is not specified (an empty string), then the station protocol parameters described below must be configured correctly for all stations. The parameters of DB-Net IP can be configured only by the "Init File".

Note 2: If you do not want so that the line initialized to initialize the ATOUCH32 driver in the multithread mode, use "---", i.e., 3x "minus" character. One Only one line within the D2000 KOM process must can contain the path to the existing init file. It, then, This line executes the initialization for all other lines.		-

...

  • Communication protocol: AMiT ATOUCH32 DB-Net.
  • The station address is the device address in the DB-Net network (value of the “Station” item in the initialization string/file - a 16-bit number). Neither the configuration nor the network can contain two stations with the same address including the address of "self station".

...

If the Init File line protocol parameter is specified for a line (at least one), then the My Station, COM Port, and COM Speed the protocol  protocol parameters will be ignored on all the stations. There will be used Instead, the configuration file on the disk (the path of which path is defined by the Init File line protocol parameter) will be used.
For further information on the file contents, see the ATOUCH32 online help.

Example: configuration file contents:

...

  • Kotva
    wid
    wid
    WID - the numerical name of the variable - it is a unique number within the DB-Net network. The permitted range is 0..65500, the value is assigned by the PSP3 tool or DetStudio. The number is specified as a decimal number or as a hexadecimal number with a hash at the beginning (e.g. #0A).
  • Kotva
    typ
    typ
    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 value types, they are interpreted as signed numbers; and if they are configured as Ci/Co value types, they are interpreted as unsigned numbers.
    LONG and LONG MATRIX types (32 bit wide) configured as Ai/Ao value types are interpreted as signed numbers and if they are configured as Ci/Co value types, 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 value type can be set for value types of TxtI and TxtO. Then the row from the INT matrix is interpreted as text, each INT element of the matrix represents one character. INT and LONG types can be represented as relative time - i.e. a number of seconds.

...

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 trouble 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
literatura0
literatura0
Literature

...

Kotva
revizie0
revizie0
Document revisions

...

  • 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

...