Compact Interpact Switch Disconnector INS400, 400A, 3 Poles

Compact Interpact Switch Disconnector INS400, 400A, 3 Poles

Compact Interpact Switch Disconnector INS400, 400A, 3 Poles

Item Number: 31110

Retail
$1,713.42
RRP (Inc. GST)

Product Dimensions

Width icon

Width185 mm

Height icon

Height205 mm

Depth icon

Depth130 mm

See full specifications

Datasheet

Barcode

Qty UoM EAN Colour
-
-
-

Specifications

Design

Range

Compact

Range of product

INS320...630

Product or component type

switch disconnector

Sustainable offer status

Green Premium product

Warranty

18 months

Physical

[Ie] rated operational current

  • AC-22A: 400 A AC 50/60 Hz 220/240 V
  • AC-23A: 400 A AC 50/60 Hz 480 V NEMA
  • AC-23A: 400 A AC 50/60 Hz 500/525 V
  • AC-23A: 400 A AC 50/60 Hz 660/690 V
  • DC-22A: 400 A DC 125 V 2 poles in series
  • DC-23A: 400 A DC 125 V 2 poles in series
  • AC-22A: 400 A AC 50/60 Hz 380/415 V
  • AC-22A: 400 A AC 50/60 Hz 440/480 V
  • AC-22A: 400 A AC 50/60 Hz 480 V NEMA
  • AC-22A: 400 A AC 50/60 Hz 500/525 V
  • AC-22A: 400 A AC 50/60 Hz 660/690 V
  • AC-23A: 400 A AC 50/60 Hz 220/240 V
  • AC-23A: 400 A AC 50/60 Hz 380/415 V
  • AC-23A: 400 A AC 50/60 Hz 440/480 V
    • [Ue] rated operational voltage

    • 125 V DC
    • 690 V AC 50/60 Hz
      • Control type

        direct front rotary handle

        Mounting mode

        fixed

        Mounting support

      • plate
      • rail
        • Mechanical durability

          10000 cycles

          Electrical durability

        • AC-22A: 1500 cycles 440 V AC 50/60 Hz
        • AC-22A: 1500 cycles 500 V AC 50/60 Hz
        • AC-22A: 1500 cycles 690 V AC 50/60 Hz
        • AC-23A: 1500 cycles 440 V AC 50/60 Hz
        • AC-23A: 1500 cycles 500 V AC 50/60 Hz
        • AC-23A: 1500 cycles 690 V AC 50/60 Hz
        • DC-23A: 1000 cycles 125 V DC
          • Height

            205 mm

            Width

            185 mm

            Depth

            130 mm

            Net weight

            4.6 kg

            Standards

          • IEC 60947-1
          • IEC 60947-3
            • Product certifications

            • KEMA-KEUR
            • CCC
              • IP degree of protection

                IP40 conforming to IEC 60529

                IK degree of protection

                IK07 conforming to EN 50102

                Ambient air temperature for operation

                -25-70 °C

                Ambient air temperature for storage

                -50-85 °C

                EU RoHS Directive

                Compliant

                Mercury free

                Yes

                RoHS exemption information

                Yes

                China RoHS Regulation

                Product out of China RoHS scope. Substance declaration for your information

                Environmental Disclosure

                ENVPEP1304026

                Circularity Profile

                ENVEOLI1304026

                Others

                Product name

                Compact INS

                Device short name

                Interpact INS400

                Switch-disconnector name

                Interpact INS400

                Poles description

                3P

                Network type

              • AC
              • DC
                • Network frequency

                  50/60 Hz

                  [Ui] rated insulation voltage

                  750 V AC 50/60 Hz

                  [Uimp] rated impulse withstand voltage

                • 8 kV
                • 8 kV conforming to IEC 60947-3
                  • [Ith] conventional free air thermal current

                    400 A at 60 °C

                    [Icm] rated short-circuit making capacity

                  • 330 kA with upstream protection circuit breaker 690 V AC at 50/60 Hz
                  • 50 kA switch-disconnector alone 690 V AC at 50/60 Hz
                    • Suitability for isolation

                      yes

                      Contact position indicator

                      yes

                      Visible break

                      no

                      Pollution degree

                      3

                      Handle colour

                      black

                      Upside connection

                      front

                      Downside connection

                      front

                      Maximum power

                    • AC-23: 110 kW at 220/240 V AC 50/60 Hz
                    • AC-23: 110 kW at 230 V AC 50/60 Hz (NEMA)
                    • AC-23: 200 kW at 380/415 V AC 50/60 Hz
                    • AC-23: 220 kW at 440 V AC 50/60 Hz
                    • AC-23: 220 kW at 480 V AC 50/60 Hz (NEMA)
                    • AC-23: 250 kW at 500/525 V AC 50/60 Hz
                    • AC-23: 400 kW at 660/690 V AC 50/60 Hz
                      • Rated duty

                        uninterrupted

                        [Icw] rated short-time withstand current

                      • 11.5 kA during 3 s conforming to IEC 60947-3
                      • 20 kA during 1 s conforming to IEC 60947-3
                      • 4 kA during 30 s conforming to IEC 60947-3
                      • 4.9 kA during 20 s conforming to IEC 60947-3
                        • Connection pitch

                          45 mm

                          Compatibility code

                          INS400

                          Unit Type of Package 1

                          PCE

                          Number of Units in Package 1

                          1

                          Package 1 Weight

                          5.005 kg

                          Package 1 Height

                          19 cm

                          Package 1 width

                          19.5 cm

                          Package 1 Length

                          22.5 cm

                          Unit Type of Package 2

                          S04

                          Number of Units in Package 2

                          4

                          Package 2 Weight

                          21 kg

                          Package 2 Height

                          30 cm

                          Package 2 width

                          40 cm

                          Package 2 Length

                          60 cm

                          Unit Type of Package 3

                          P12

                          Number of Units in Package 3

                          16

                          Package 3 Weight

                          95.144 kg

                          Package 3 Height

                          80 cm

                          Package 3 width

                          80 cm

                          Package 3 Length

                          120 cm

                          WEEE

                          The product must be disposed on European Union markets following specific waste collection and never end up in rubbish bins
                          Show all specifications

                          Frequently Asked Questions

                          hide show

                          What is the code for an extended rotary handle for 31052 (INS400) ?

                          Code = 31052 Suits INS320 to INS 630 - Black

                          Why a limit of 9672 Registers with CPU31110 since Unity V3.0?

                          In the CPU overview there was already a limit of 9672 registers,but Unity didn't have any no limitation for this limit. Since Unity Pro V3.0 a control was added to check this limitation.
                          That's why we could configure 9672 registers or more with CPU 31110 using Unity Pro v2.3,  but since Unity v3.0 we cannot exceed 9672.
                           

                          What is the bolt hole size of the 31100 INS250-100?

                          The bolt hole size is M10 for the INS250-100....INS250-250

                          see attachment

                          What is the extended rotary handle for a 31104

                          The part code is 31050

                          How to I monitor NetBotz alarms using Modbus?

                          Issue:
                          Monitoring alarms on NetBotz using Modbus.
                           
                          Product Line:
                          NetBotz
                           
                          Environment:
                          NetBotz 550
                          NetBotz 570
                          NetBotz 450 (with Advanced Software Pack)
                          NetBotz 455 (with Advanced Software Pack)
                           
                           
                          Cause:
                          This is just a guide showing how to monitor NetBotz events using Modbus. Modbus output is not available on the 4xx units by default.
                           
                          Resolution:
                           
                          In this example, I have configured a NetBots 570 with a rack access pod NBPD0171. I want to see when there is a forced entry into a rack door being monitored by this NetBotz configuration. Any supported firmware should work but in this case, I have used version 4.5.2.
                          There is no way using Modbus to know the exact error message. Based on the return values and the register maps, you can tell what sensor is in an error state and you can tell what level of event is occurring. Let me first state that this mimics the DCE modbus output and you can use the following document (at least the beginning of it) to figure out the level of alarm:
                          https://www.apcmedia.com/salestools/JRUK-7R4L9N/JRUK-7R4L9N_R3_EN.pdf?sdirect=true
                          This is app note 156 and the link may change over time.
                           
                          First, Enable the Modbus output on the “Modbus Slave Communications” applet in NetBotz Advanced View (AV). On a 4xx unit, you must first install the advanced software pack. On a 5xx unit, this is enabled by default. 3xx units and older version 2 units does not support this feature.

                          This example is using Modbus over TCP but there is a serial option. Please see the user manual for your unit as to how to use the serial connections.
                           
                          Next, using the ”Modbus Slave System” applet in AV, find the appropriate pod. In this case, I am using Rack Access Pod 170 (03)

                           
                          Click “Modify Pod Settings” and you will be able to give the pod a slave address and create a register map for all it’s sensors:


                          After this configuration, you can view and subsequently export the register map back on the “Modbus Slave System” page.
                          You will see the alarms configured this way (and more):
                          all   30992(0x7910)  Alarm #03                                                         002     UINT16       RO      Alarm - Alarm Code + Corresponding Sensor
                           all   30994(0x7912)  Alarm #02                                                         002     UINT16       RO      Alarm - Alarm Code + Corresponding Sensor
                           all   30996(0x7914)  Alarm #01                                                         002     UINT16       RO      Alarm - Alarm Code + Corresponding Sensor

                          You will also see each pod as it’s own slave. Here you can see the main unit as slave 1 and the NetBotz 170 pod as slave 2:
                           
                          001   31000(0x7918)  NetBotz Rack Monitor 570:Ethernet Link Status                     002     INT16        RO      Value - 0(Down), 1(Up)
                           001   31002(0x791a)  NetBotz Rack Monitor 570:A-Link Bus Power                         002     INT16        RO      Value - 0(OK), 1(Overloaded)
                           
                           002   31000(0x7918)  Rack Access Pod 170 (03):Handle  (2)                              002     INT16        RO      Value - 0(Up), 1(Down)
                           002   31002(0x791a)  Rack Access Pod 170 (03):Handle  (1)                              002     INT16        RO      Value - 0(Up), 1(Down)
                           002   31004(0x791c)  Rack Access Pod 170 (03):Lock  (1)                                002     INT16        RO      Value - 0(Unlocked), 1(Locked)
                           002   31006(0x791e)  Rack Access Pod 170 (03):Reader  (2)                              002     INT16        RO      Value - 0(Disabled), 1(Enabled)
                           002   31008(0x7920)  Rack Access Pod 170 (03):Reader  (1)                              002     INT16        RO      Value - 0(Disabled), 1(Enabled)
                           002   31010(0x7922)  Rack Access Pod 170 (03):Door  (1)                                002     INT16        RO      Value - 0(Open), 1(Closed)
                           002   31012(0x7924)  Rack Access Pod 170 (03):Lock  (2)                                002     INT16        RO      Value - 0(Unlocked), 1(Locked)
                           
                          Please note that each register is actually listed as 2 numbers higher than the last. This is because each sensor is configured as 2 registers. If you're looking for data on a specific register say 31000, you actually have to pull 31000 and 31001. Note the register in bold is 31010. To get the data for this sensor, you need to pull 31010 and 31011. It also shows this is the door sensor and the value should be 0 for open and 1 for closed. Knowledge base FA214410 can assist if you’re unsure how to use dual registers but it should not be necessary in this specific instance.
                           
                          Next, when you poll for alarms, you poll register 30999. This  shows how many alarms there are. Register 30998 shows the highest severity of the alarms if there are multiple. For each alarm, you should read 2 registers back. In this case there is 1 alarm so reading 2 registers before the 30998 is 30997 and 30996.
                           
                          In this image from AV, you can see the door is open and in an error state:

                           
                          Upon polling the device’s IP and slave address 2, you can see that 31010 and 31011 (31011 is the important one) is reading 0. This means from the register map that the door is open. Value - 0(Open), 1(Closed)
                           

                          Here is what that same register looks like if I close the door:

                           
                           
                          Putting the door back in alarm, you can see that 30999 is 1 meaning there is 1 error and 30998 is 2 which means it is level 2 (error)....the latter is defined in the DCE app note 156 linked above.

                           
                          The register 30997 above reports the sensor. The return is 31010. This matches the register on that door sensor as shown in the register map. The register 30996 reports the actual error. This is also defined in the DCE app note. It's in HEX in the app note so you have to show the return in hex as I am doing here:

                           
                          Note that 30996  is reporting 000E. If you check the device alarm codes here (again from app note 156), you'll see that 000E relates to "General Device Alarm":

                           
                          So with this information, I opened a door with a locked handle and the information I pulled via Modbus shows that sensor (register) 31010  is in an alarm state of general device alarm and it is an error level. Looking at the register map I can tell that 31010 (remember, it's 2 registers on a sensor) is a door sensor and since it's return is 0, the door is open. You can also check the other sensors such as handle to see if it is down or check the lock to ensure it is locked etc.
                           

                          Interpact load break switch needed, 160Amp 3P

                           Use a 31104

                          Is there a replacement for a PS110 Protected die-cast switch?

                          The closest alternative is is RPSW110M.

                          What is the extended rotary handle for a 31146

                          The part code is 31055

                          Where can I find the register list for the iEM3100, iEM3200, and iEM3300 series of meters?

                          Issue
                          A user may need the register list for the iEM3100, iEM3200, and iEM3300 series of meters.
                           
                          Product Line
                          iEM3100, iEM3200, iEM3300 series
                           
                          Environment
                          iEM3100, iEM3200, iEM3300 series
                           
                          Cause
                          A user may need the register list for the iEM3100, iEM3200, and iEM3300 series of meters.
                           
                          Resolution
                          The user manual for the iEM3100, iEM3200, and iEM3300 series of meters (document reference number DOCA0005EN-04) has a register list in Chapter 5: Communications via Modbus RS-485. See page 57 of the pdf document attached   (doca0005en-04.pdf)

                          Getting E1100 error on the LXM32 servo drive

                          Issue:
                          Getting E1100 error on the LXM32 servo drive

                          Product Line:
                          LXM32

                          Resolution:
                          E1100 is a "parameter out of range" error. The parameter could be coming from a PLC or an HMI communication with the LXM32 drive and sending an out of range parameter like speed, acceleration, deceleration or position.

                          PTZ or motion detection functions on an existing Pelco camera no longer work through NetBotz appliance after upgrade to 3.3

                          Issue:

                          PTZ or motion detection functions on an existing Pelco camera no longer work through NetBotz appliance after upgrade to 3.3

                          Product Line:

                          NetBotz

                          Environment:

                          NetBotz 3.3. upgrade

                          Cause / Resolution:

                          If after upgrading from 3.2.x to 3.3.x, the PTZ or motion detection functions on an existing Pelco camera no longer work the camera has to be removed and re-added and shared. Possible cause is that the user upgraded to 3.3.x Advanced View but did not upgrade to 3.3.x on the appliance and then added the camera. The user should upgrade both Advanced View and the appliance before adding the Pelco camera. An existing camera added with matching software and firmware will not have this issue.

                          What is the new code for 31050 ?

                          now =  LV431050
                          Show More