25
We software Automation. We software Automation. Sercos 3 in CoDeSys Sercos 3 in CoDeSys Public 16.07.2009

We software Automation

  • Upload
    nero

  • View
    65

  • Download
    0

Embed Size (px)

DESCRIPTION

We software Automation. Sercos 3 in CoDeSys. Public 16.07.2009. 3S-Smart Software Solutions. The company. Date of Foundation. Products and markets. July 1994. Staff members. Industrial Automation software suite CoDeSys. 70. Turnover 2008. 6.8 Million €. Owners. - PowerPoint PPT Presentation

Citation preview

Folie 1Designed for small targets:
Designed for big targets:
A complete development system
Hardware and field bus
Drive configuration directly in CoDeSys
Contains:
Drivers for SERCOS III, CAN, EtherCAT (others on demand)
We software Automation.
SERCOS III
Very successful with SERCOS II technology
One of the leading technologies on the real time Ethernet market
Already in use or evaluated by 3S customers
Industrial standard (printing, packaging, plastic molding, etc…)
Technically stable and proven
We have had very good experience with SERCOS II.
The excellent level of drive profile standardization allows us to operate devices from a variety of manufacturers without time consuming driver development or modification.”
Manfred Werner: Managing Director
3S-Smart Software Solutions GmbH/
" At 3S, there was never any doubt that we would implement SERCOS III in our CoDeSys system.
We software Automation.
SERCOS Cycletime:
The cycle time defines the time interval allocated for data exchange between master and slave.
It is measured in nanoseconds; the default value is 1.000.000ns = 1ms.
We software Automation.
NRT Channel Width
The non-real-time channel (NRT) supports the transmission of standardized or proprietary IP protocols.
The time width defines how long the bus is reserved for non-real-time data.
We software Automation.
IP Max Transmission:
Here the maximum number of bytes to be sent in one packet in the IP channel is established.
The default is 100;  the number may not exceed 1500.
We software Automation.
NRT after last AT telegram:
At first the MDTs (Master Data Telegrams) are sent, next the ATs (Amplifier Telegrams) followed by the NRTs (Non-real-time Telegrams).
NRT after last MDT telegram:
The NRTs are transmitted following the MDTs and then the ATs.
NRT after MDT telegram, AT sent at the end of the cycle:
The NRTs are transmitted subsequent to the MDTs
The ATs are transmission only at the end of the SERCOS cycle.
We software Automation.
Hotplugging
Enable Hotplugging: If this checkbox is activated, slave devices may be added or removed during the working process.
We software Automation.
Product offering
Mainly automation component manufacturers.
We software Automation.
automation industry
programming system
End-user friendly
Interoperability
We software Automation.