• Name: Barcode
  • Version: 1.0.3.0
  • Protocol: ASCII Generic
  • Interface: Serial or TCP/IP
  • Runtime: Multiplatform
  • Configuration:
    • Devices / Protocols

Overview

Barcode Reader compatible with ASCII encoding 

Communication Driver Information

Driver name

Barcode

Assembly Name

T.ProtocolDriver.Barcode

Assembly Version

1.0.3.0

Available for Linux

False

Devices supported 

Any equipment compatible with ASCII encoding

Manufacturer

N/A

Protocol

Serial or TCP/IP

Protocol Options

BlockSize, Start Char and End Char

PC Requirements

Standard PC Ethernet interface board, RS485 or RS232 port

Multi-threading

Only one instance per channel is allowed

Max number of nodes

Only one Node should be used for each channel

Channel Configuration

Protocol Options

  • BlockSize: Defines the maximum length of a single item, the default value is 256.

  • StartChar: Specifies the character that marks the beginning of a message. Only one character is expected. If left empty, the driver will start receiving the message upon detecting any character.

  • EndChar: Specifies the character that marks the end of a message. Only one character is expected. If left empty, the driver will stop receiving the message once it reaches the defined block size or when the message ends.

Settings

Serial and MultiSerial channels:

  • Consult the Serial Port configuration from your equipment

TCP/IP channels:

  • ListeningPort: Defines the TCP/IP port that will be listening for the connections.

Node Configuration

Primary Station 

The PrimaryStation and the BackupStation are not used and should be blank.

Point Configuration

The syntax for the Barcode communication points is: <Number of Bytes>

  • <Number of Bytes>: means how many bytes (characters) the Tag will receive.

The value 0 (zero) means that the Tag will receive the whole message

E.g.: The message received was “ABCDXYZ”

Case1:

TagName

Address

Value

TagA

4

ABCD

TagB

3

XYZ

 

Case2:

TagName

Address

Value

TagC

0

ABCDXYZ

AccessType

This is an unsolicited driver, meaning it does not continuously request data. Instead, it receives information whenever the master sends a message. Follow the configuration settings below to set it up correctly:

AcceptUnsolicited: True

ReadEnable: Never

Driver Revision History

Barcode Revision History

Version 

Notes

1.0.2.0

Initial release on new documentation standards.

1.0.3.0

New end condition for reading unsolicited messages. Enable the use of the char data type for both StartChar and EndChar parameters.


In this section...