Send data memory map, Table 3.e send data memory map, Send data memory map -6 – Rockwell Automation D17846.2.4 CONTROLNET KT EMULA User Manual

Page 26

Advertising
background image

Publication 1784-6.2.4 - September 1997

3-6

How Your Driver Operates the KTCX Card

Send Data Memory Map

Refer to Table 3.C to determine the use of each dual-port address as
you send packets.

Table 3.E Send Data Memory Map

Byte

Description

Function

1

Contents = Meaning

Typical Access

2

KTCX . . . . . Host

Comments

:0080h

Send Access
Request

STAT

00h = KTCX control
01h = host control

R/W . . . .R/W

This is one of the send mailbox control bytes. The proper
order for setting them is 0081h (Send Data Valid) first, then
0080h.

:0081h

Send Data Valid

STAT

00h = KTCX control
01h = host control

R/W . . . R/W

This is one of the send mailbox control bytes. The proper
order for setting them is 0081h first, then 0080h (Send
Access Request).

:0082h

Length (lo byte)

PKTCX

---

R . . . . . . . .W

Indicates length of the mailbox data in two bytes.

:0083h

Length (hi byte)

PKTCX

---

R . . . . . . . W

:0084h

Reserved

---

---

---

All reserved bytes must be set to 00h.

:0085h

Reserved

---

---

---

:0086h

Destination

PKTCX

---

R . . . . . .. . W

Destination address of packet.

:0087h

Control

PKTCX

05h

R . . . . . . . W

Always 05h.

:0088h

Packet Type

PKTCX

00h

R . . . . . . . W

Packet type is always 00h.

:0089h

Link Service
Access Point

PKTCX

00h = on-link packet

R . . . . . . . W

Off-link packets need 11 extra bytes which we insert starting

at byte 008Ah. The remaining bytes (008Ah-047Fh) are
shifted 11 places higher. Link Service Access Point (LSAP)
specifies the type of packet and offset.

:008Ah

CMD (PCCC)

PKTCX

---

R . . . . . . . .W

Sent to the destination to effect a command or command
sequence. Used in combination with :008Eh. Refer to

DF1

Protocol and Command Set (Pub. 1770-6.5.16)

.

:008Bh

Message Status

PKTCX

---

R . . . . . . . .W

Indicates status of message transmission. Command and
reply messages may contain one of the status codes listed in
the

DF1 Protocol and Command Set (Pub. 1770-6.5.16)

.

:008Ch

TNS (low byte)

PKTCX

---

R . . . . . . . .W

The transaction numbers are a 16-bit, 2-byte sequential

tracking numbers. They make sure that commands and their
replies remain associated. If the host issues a command,
then it must generate and track the TNS. Otherwise, the
issuing PLC or another KTCX card generates the TNS.

:008Dh

TNS (high byte)

PKTCX

---

R . . . . . . .. W

:008Fh
:047Fh

DATA

PKTCX

---

R . . . . . . . .W

Bytes 008Fh-047Fh contain the data to be transmitted (and
the response packet, if any).

1

CMD = Command From Host to KTCX; DIAG = Diagnostic Counter; STAT=Status; INI = Initialization; N/A = Not Applicable

2

R = Read; W = Write

Advertising