Serial data transfer

Application

The TNC7 basic automatically uses the LSV2 transmission protocol for serial data transfer. All parameters of the LSV2 protocol are invariably fixed except for the baud rate in the machine parameter baudRateLsv2 (no. 106606).

Description of function

The machine parameter RS232 (no. 106700) allows you to define another transmission type (interface). The settings described below are effective only for the respective newly defined interface.

Machine parameters

In the machine parameters that then appear you can define the following settings:

Machine parameters

Setting

baudRate (no. 106701)

Data transfer rate (baud rate)

Input: BAUD_110, BAUD_150, BAUD_300 BAUD_600, BAUD_1200, BAUD_2400, BAUD_4800, BAUD_9600, BAUD_19200, BAUD_38400, BAUD_57600, BAUD_115200

protocol (no. 106702)

Data transfer protocol

  • STANDARD: Standard data transfer, line-by-line
  • BLOCKWISE: Packet-based data transfer
  • RAW_DATA: Transfer without protocol (purely character-by-character)

Input: STANDARD, BLOCKWISE, RAW_DATA

dataBits (no. 106703)

Data bits in each transferred character

Input: 7 Bit, 8 Bit

parity (no. 106704)

Parity bit used to check for transmission errors

  • NONE: No parity, no error detection
  • EVEN: Even parity, error if the number of bits set is odd
  • ODD: Odd parity, error if the number of bits set is even

Input: NONE, EVEN, ODD

stopBits (no. 106705)

The start bit and one or two stop bits enable the receiver to synchronize to each transmitted character during serial data transmission.

Input: 1 Stop-Bit, 2 Stop-Bits

flowControl (no. 106706)

By handshaking, two devices control data transfer between them. A distinction is made between software handshaking and hardware handshaking.

  • NONE: No data-flow check
  • RTS_CTS: Hardware handshaking, transmission stop is active through RTS
  • XON_XOFF: Software handshaking, transmission stop is active through DC3

Input: NONE, RTS_CTS, XON_XOFF

fileSystem (no. 106707)

File system for the serial interface

  • EXT: Minimum file system for printers or non-HEIDENHAIN transmission software
  • FE1: Communication with TNCserver or an external floppy disk unit

If you require no special file system, this machine parameter is not needed.

Input: EXT, FE1

bccAvoidCtrlChar (no. 106708)

The BCC is a block check character. The BCC is optionally added to a transfer block to simplify error detection.

  • TRUE: The BCC does not correspond to any control character
  • FALSE: Function not active

Input: TRUE, FALSE

rtsLow (no. 106709)

This optional parameter determines the level of the RTS line in the idle state.

  • TRUE: Level is LOW in idle state
  • FALSE: Level is HIGH in idle state

Input: TRUE, FALSE

noEotAfterEtx (no. 106710)

This optional parameter sets whether an EOT character (End of Transmission) is to be transmitted after receiving an ETX character (End of Text).

  • TRUE: The EOT character is not sent
  • FALSE: The EOT character is sent

Input: TRUE, FALSE

Example

In order to use the TNCserver PC software for data transfer, define the following settings in the machine parameter RS232 (no. 106700):

Parameter

Selection

Data transfer rate in baud

Has to match the setting in TNCserver

Data transfer protocol

BLOCKWISE

Data bits in each transferred character

7 bits

Type of parity checking

EVEN

Number of stop bits

1 stop bit

Type of handshake

RTS_CTS

File system for file operations

FE1

TNCserver is part of the TNCremo software for PCs.

PC software for data transfer