Supported device types and versions
The protocol supports communication with the ALYA communication computer to collect data from barcode readers and ALYA multi-measurement workstation (MMP).
Communication takes place via three UDP channels:
- UDP Port Reader configuration parameter (by default 3131).
The D2000 KOM responds by confirming the message number. data from barcode readers (the cone number) is sent to the port specified by the
- UDP Port Reader parameter (by default 3132).
The D2000 KOM responds with a message containing the confirmation of the message number and other data depending on the configuration.
All these data will be sent based on the values of the respective output I/O tags. data about the cones weighted by MMP (the cone number, weight, width, height) are sent to a port one higher than the
- UDP Port Reader (by default 3133).
The D2000 KOM responds with a message containing the confirmation of the message number. Watchdog messages are sent to a port by two higher than the
If the D2000 KOM does not confirm the message to the ALYA communication computer, the ALYA communication computer buffers the collected data and resends it periodically.
Communication line configuration
- Category of communication line: API.
- Communication protocol "ALYA MMP".
- The station address is not configured.
Station protocol parameters
Dialogue window station configuration - "Protocol parameters" tab.
They influence some optional protocol parameters. The following station protocol parameters can be specified:
Reader UDP Port
|UDP port number for receiving messages from the barcode readers.||-||3131|
|Timeout for receiving a message from barcode readers, scales or a watchdog.|
If the Ping Active parameter is set to YES and the configured timeout elapses without receiving any message, the communication is considered to be interrupted and the station goes into communication error.
Nr. of Values for Output
|The number of variables that the D2000 KOM sends in response to the message about weighted cones from the scales.||-||15|
|Activation of MMP activity tracking - see the description of the Data Timeout parameter.||YES/NO||YES|
I/O tag configuration
Supported value types of I/O tags: Ai, Ci, Di, TxtI, Ao, Co, Dout, TxtO.
The address is specified as a decimal number or as a hexadecimal number with a hash at the beginning (e.g. #0A).
|I/O tag for handling barcode readers.|
|TxtI, Ci||0||Cone number from the message received from barcode readers (CONE_NR)|
|I/O tags for handling input from the scales.|
|Ai, Ci, Di, TxtI||1 .. 10||Individual components of the received message from the scales. According to the specification, there are five components (addresses 1-5):|
|Di||0||A trigger I/O tag for the message from the scales.|
It is set to True with a new timestamp when a new message from the scales arrives and the input I/O tags from the previous row of the table have their values set by D2000 KOM.
|I/O tags for handling the answer for the scales.|
|Co, TxtO, Ao||1 .. 32||Individual components of a response to the scales. According to the specification, there are seven components (addresses 1-7):|
Note: component with address 2 cannot by of TxtO type, to avoid the collision with a trigger for the fibre rupture message.
|Dout||0||Trigger I/O tag for the response to the scales. By writing to the trigger the application activates sending the response that contains the output I/O tags from the previous row of the table.|
The number of values in the reply is determined by the configuration parameter Nr. Of Values for Output.
|I/O tags for sending spontaneous messages about the rupture of the fibre to the scales.|
|Co, TxtO, Ao||1||The first component of a spontaneous message about a rupture of the fibre sent to the scales.|
|2||The second component and at the same time a trigger of a spontaneous message about a rupture of the fibre sent by D2000 KOM process to the scales.|
The message contains components with addresses 1 and 2.
- Ver. 1.0 - July 3rd, 2017 - Document creation.