Thanks to visit codestin.com
Credit goes to www.scribd.com

0% found this document useful (0 votes)
42 views2 pages

Plc-Io e

This document describes how the SINUMERIK 840D CNC allows the NC to address PLC I/Os. It explains that machine data must be set to define the input and output areas. The NC can then read the defined input bytes and write to the defined output bytes. When the NC writes to the output bytes, it overwrites the entire defined output area, including any bytes also written by the PLC. Therefore, the NC and PLC cannot truly share the same output bytes, as the NC will influence the PLC outputs even if writing to different addresses within the defined area.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
42 views2 pages

Plc-Io e

This document describes how the SINUMERIK 840D CNC allows the NC to address PLC I/Os. It explains that machine data must be set to define the input and output areas. The NC can then read the defined input bytes and write to the defined output bytes. When the NC writes to the output bytes, it overwrites the entire defined output area, including any bytes also written by the PLC. Therefore, the NC and PLC cannot truly share the same output bytes, as the NC will influence the PLC outputs even if writing to different addresses within the defined area.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

SINUMERIK 840D

Attachment to FAQ
CNC SINUMERIK, SINUMERIK 840D
PLC I/Os addressable by NC.

1. Activating the function

$MN_PLCIO_NUM_BYTES_IN = 12
$MN_PLCIO_LOGIC_ADRESS_IN = 72
$MN_PLCIO_NUM_BYTES_OUT = 16
$MN_PLCIO_LOGIC_ADRESS_OUT = 100

(The I/O areas used here are an example, and have been chosen arbitrarily)

Once the MDs are set, the function is active, not with a read or write command of the NC.

2. Function

Input I/Os
No limitations apply to the input I/Os.
The inputs may be read by NC and PLC in the same way.

Output I/Os
Both NC and PLC may write.
If the NC writes, the output image for the PLC is updated (corresponds to end OB1)

With every write command of the NC, the complete I/O area defined by the machine data is
written

Example:

$MN_PLCIO_NUM_BYTES_OUT = 16
$MN_PLCIO_LOGIC_ADRESS_OUT = 100

16 bytes are determined as outputs.


The NC uses bytes 100...107, PLC uses bytes 108...115

...
$A_PBB_OUT[0]=11 Byte 100 should be written
... But:
The whole area, bytes 100...115 are written
(in this context, also byte100)

The mechanism can be imagined as follows, analog to the PLC. The NCK writes to a “output image“,
which is then transferred to the I/Os as a whole. This is caused by every write command of the NC.

The results are the following:

Output state: NCK-PowerOn à This deletes the NCK “Output image“

NC PLC

G90 G00 D0 Z0 OB1


R100=23 ...
... U E 32.0
... = A 108.0
$A_PBB_OUT[0]=R100 ...
... ...
BE

PLC-IO_e.doc Page 1 / 2
SINUMERIK 840D
Attachment to FAQ
CNC SINUMERIK, SINUMERIK 840D
PLC I/Os addressable by NC.

- PLC cyclically writes the byte 108


NCK writes (at any arbitrary point of the OB1 cycle, from the PLC point of view)

In the part program, there is a write command at byte 100


This causes the “NCK output image“ to be written from byte100...115 to the I/Os, that is, the
NCK also writes the byte108 (preset to “0“ by PowerOn). This causes output 108.0 to become
“0“ until the PLC updates its output image when OB1 is finished.

That is:
The output area cannot be shared by PLC and NC !!
In every case, the NCK influences the PLC (even if not using the same bytes)

PLC-IO_e.doc Page 2 / 2

You might also like