Indactic 33/41

  • The Indactic 33/41 protocol was developed by the BBC company (ABB) at the beginning of the eighties. It found high resonance in the energy industry for the automation of transformer stations enabling the communication between a control station and several RTUs. It is often referred to as "Indactic 33", so it is easily confused with the Indactic 2033.

    Indactic 2033 is derived from Indactic 33/41.

    Data transmission is based on the half duplex communication mode. The control station continuously sends synchronization signals even when there is no data ready to be dispatched. The RTUs on the other hand only respond to an explicit request from the control station. Up to 15 RTUs can be connected to a single communication line.

    Data is encoded in 16-bit words with 8-bit use data which together make up a telegram.

ISO/OSI Model
7 Application Layer Indactic 2033 Application Layer
6 Presentation Layer n/a
5 Session Layer n/a
4 Transport Layer n/a
3 Network Layer n/a
2 Link Layer n/a
1 Physical Layer RS232 / V.24 (PCM)
Supported Information Types
Control Direction
  • Double Command
  • Setpoint [8 bit]
Monitoring Direction
  • Single indication [1 Bit]
  • Single indication [1 Bit] with time tag
  • Measured value [8 bit]
  • Counter value BCD [6 digits]
Protocol Features

  • Physical Layer

    PCM
    pseudo halfduplex
    baud rates: 50, 100, 200, 600, 1200

  • Application Layer

    on-demand transmission of static signals such as single indications and analogs
    spontaneous transmission of single indications with time tag
    direct command transmission (without SBO)
    clock synchronization

  • Address Space

    up to 15 RTUs connected to one line
    single indications: up to 15 files with 128 points each
    analogs: up to 8 files with 16 points each
    counter values: up to 4 files with 16 points each
    commands: up to 15 files with 128 points each

Available Protocol Stacks

Indactic 33/41, 2033, Master

Indactic 33/41, 2033, Slave

Applicable Products
  • ipConvLite
    ipConvLite

    Universal protocol converter for small and distributed applications

    Flyer
  • ipConvLite/MEC2PBS
    ipConvLite/MEC2PBS

    Universal protocol converter with integrated PROFIBUS-DP, slave interface

    Flyer
  • ipConvLite/MEC2PBM
    ipConvLite/MEC2PBM

    Universal protocol converter with integrated PROFIBUS-DP, master interface

    Flyer
  • ipConvLite/MEC2PNS
    ipConvLite/MEC2PNS

    Universal protocol converter with integrated PROFINET-IO, slave interface

    Flyer
  • ipConv
    ipConv

    Universal protocol converter for highest degree of flexibility

    Flyer
References
  • Project CFE
    Project CFE, Mexico

    Products: ipConv
    Protocol Stacks: Conitel-2020, Slave DNP V3.00, Slave DNP V3.00, Master Harris-5000/6000, Slave Recon, Slave Indactic 33/41, 2033, Slave Fuji, Slave XMAT, Master

  • Power Plants Hinterrhein
    Power Plants Hinterrhein, Switzerland

    Products: ipConv
    Protocol Stacks: IEC 60870-5-104, Slave Indactic 33/41, 2033, Master

  • ABBIran
    ABBIran, Iran

    Products: ipConv
    Protocol Stacks: Indactic 33/41, 2033, Slave IEC 60870-5-101, Master

  • ISKI
    ISKI, Turkey

    Products: ipConv
    Protocol Stacks: Indactic 33/41, 2033, Slave Modbus, Master