INS250 3P 250 A - SWITCH DISCONNECTOR
Interpact INS630 standard switch. 3 poles
INS250 3P 250 A - SWITCH DISCONNECTOR
Interpact INS630 standard switch. 3 poles

INS250 3P 250 A - Switch Disconnector

Catalogue Number: 31106
INS250 3P 250 A - SWITCH DISCONNECTOR
Interpact INS630 standard switch. 3 poles
INS250 3P 250 A - SWITCH DISCONNECTOR
Interpact INS630 standard switch. 3 poles
Colour:
Colour: Per UOM Std.
  • 1 PCE

Specifications

hide show
Range
Compact
Range of product
INS250
Product or component type
switch disconnector
Product name
Compact INS
Device short name
Interpact INS250
Switch-disconnector name
Interpact INS250
Poles description
3P
Network type
  • DC
  • AC
    • Network frequency
      50/60 Hz
      [Ie] rated operational current
    • AC-22A: 250 A AC 50/60 Hz 220/240 V
    • AC-23A: 250 A AC 50/60 Hz 480 V NEMA
    • AC-23A: 250 A AC 50/60 Hz 500/525 V
    • AC-23A: 250 A AC 50/60 Hz 660/690 V
    • DC-22A: 250 A DC 125 V 2 poles in series
    • DC-23A: 250 A DC 125 V 2 poles in series
    • AC-22A: 250 A AC 50/60 Hz 380/415 V
    • AC-22A: 250 A AC 50/60 Hz 440/480 V
    • AC-22A: 250 A AC 50/60 Hz 480 V NEMA
    • AC-22A: 250 A AC 50/60 Hz 500/525 V
    • AC-22A: 250 A AC 50/60 Hz 660/690 V
    • AC-23A: 250 A AC 50/60 Hz 220/240 V
    • AC-23A: 250 A AC 50/60 Hz 380/415 V
    • AC-23A: 250 A AC 50/60 Hz 440/480 V
      • [Ui] rated insulation voltage
        750 V AC 50/60 Hz
        [Ith] conventional free air thermal current
        250 A at 60 °C
        [Icm] rated short-circuit making capacity
      • 30 kA switch-disconnector alone 690 V AC at 50/60 Hz
      • 330 kA with upstream protection circuit breaker 690 V AC at 50/60 Hz
        • [Ue] rated operational voltage
        • 125 V DC
        • 690 V AC 50/60 Hz
          • Suitability for isolation
            yes
            Contact position indicator
            yes
            Visible break
            no
            Pollution degree
            3
            Control type
            direct front rotary handle
            Handle colour
            black
            Mounting mode
            fixed
            Mounting support
          • rail
          • plate
            • Upside connection
              front
              Downside connection
              front
              Maximum power
            • AC-23: 132 kW at 380/415 V AC 50/60 Hz
            • AC-23: 150 kW at 440 V AC 50/60 Hz
            • AC-23: 150 kW at 480 V AC 50/60 Hz (NEMA)
            • AC-23: 160 kW at 500/525 V AC 50/60 Hz
            • AC-23: 210 kW at 660/690 V AC 50/60 Hz
            • AC-23: 75 kW at 220/240 V AC 50/60 Hz
            • AC-23: 75 kW at 230 V AC 50/60 Hz (NEMA)
              • Rated duty
                uninterrupted
                [Icw] rated short-time withstand current
              • 1.8 kA during 30 s conforming to IEC 60947-3
              • 2.2 kA during 20 s conforming to IEC 60947-3
              • 4.9 kA during 3 s conforming to IEC 60947-3
              • 8.5 kA during 1 s conforming to IEC 60947-3
                • Mechanical durability
                  15000 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-22A: 1500 cycles 125 V DC 2 poles in series
                • DC-23A: 1500 cycles 125 V DC 2 poles in series
                  • Connection pitch
                    35 mm
                    Height
                    136 mm
                    Width
                    140 mm
                    Depth
                    96 mm
                    Net weight
                    2 kg
                    Compatibility code
                    INS250
                    Standards
                  • IEC 60947-3
                  • IEC 60947-1
                    • 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
                        Sustainable offer status
                        Green Premium product
                        REACh Regulation
                        Free of Substances of Very High Concern above the threshold
                        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
                        ENVPEP1304025
                        Circularity Profile
                        N/A
                        WEEE
                        The product must be disposed on European Union markets following specific waste collection and never end up in rubbish bins
                        California proposition 65
                        WARNING: This product can expose you to chemicals including: DINP and DIDP which is known to the State of California to cause Carcinogen and Reproductive harm. For more information go to www.p65warnings.ca.gov
                        Warranty
                        18 months

                        Documents & downloads

                        hide show
                        Filter items
                        • All

                        • CAD Files and Packs

                        • Technical Data Catalogues

                        • Catalog Page

                        • Installation Instruction

                        • Product Environmental

                        • End of Life Manual

                        • Operating Manuals

                        • Specification for Tender

                        • Declaration of Conformity

                        Frequently Asked Questions

                        hide show

                        What is the part number for the Auxiliary to suit the INS Load break swiich, 31106?

                        The part number for the Auxiliary to suit the INS Load break swiich, 31106 is part number 29450.
                        See data sheet for more information:
                        https://eshop.schneider-electric.com/product.aspx?org=21&lang=1&dist=276&prod_id=29450
                        User-added image

                        What is the part code for a Escutcheon plate for a 31106 - INS250 load break switch

                        Use a 31079 escutcheon plate

                        What is the NZ Equivalent for a 43850 IN250

                         The part code is 31106 which is an INS250

                        Interpact load break switch needed, 160Amp 3P

                         Use a 31104

                        Does the 31106 come with a handle?

                         It comes complete with a direct handle. Extended rotary handles are available as an extra.

                        What is the extended rotary handle for a 31104

                        The part code is 31050

                        What is the extended rotary handle for a 31146

                        The part code is 31055

                        What is the part code for a CHANGE OVER SWITCH manual 250Amp

                        Use a 31146 - MANUAL SOURCE CHAN E OVER SWITCH 

                        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 part number for an INS250 isolator and rotary handle?

                        the part number for an INS250 isolator and rotary handle is - 31106 & LV431050

                        For further information , visit links below:-
                        https://www.schneider-electric.com.au/en/search/LV431050
                        https://www.schneider-electric.com.au/en/search/31106
                        User-added image
                        User-added image
                         

                        How can a BCM module be programmed for 2w modbus on a 4w communication system?

                        Issue:
                        Applying BCM programmed for 2 wire modbus to a 4 wire modbus system

                        Product Line:
                        Powerpact and Masterpact breakers with modbus communications

                        Environment:
                        Applies to trip units with BCM

                        Resolution:
                        1. With a newer Micrologic P or H trip unit you may re-program the BCM module to 4w.  This requires firmware version 2010AK or newer.
                        2. If the trip unit does not have this option or if it is an A trip unit, you may use a 2w to 4w converter, CNV-100.  See the Attached Instruction Bulletin for more details.
                        3. Schneider sales offices can also order a BCM programmed for 4w modbus.  Order the module number, 33106 in Q2C with a note that you want it programmed for "4w Modbus."  
                          BCM 33106 profile is available only on Q2C Tool. Regional Field Offices to support order submission for customers who are unable to access Q2C.

                        Which cable should be used when making Interbus-S cables longer than 100cm?

                        There are two Belden cables that can be used.
                        1. Belden 3120A for signal only.
                        2. Belden 3119A for signal and power.


                        I am getting EB106 on a LXM32A drive

                        Issue:
                        Getting EB106 on a LXM32A drive and I cannot find it in the catalogue

                        Product Line:
                        Lexium 32

                        Resolution:
                        EB106 error means I/O data mapping error.
                        This error only occurs if the drive is controlled via CANmotion and the mapping is incorrect.
                        It means the needed mapped objects like 60FF (Target Velocity), 6071 (Target torque), 607A (Target Position)... are not mapped or are double mapped.

                        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.

                        What are the dimensions for 31147?

                        Dimensions for the 31147 are - H136mm x W285mm x D131mm

                        For further details regarding 31147 go to link below:-
                        https://www.schneider-electric.com.au/en/search/31147

                        When polling dual registers in InfraStruXure Central 6.0, both registers must be polled together.

                        Issue:

                        When polling dual registers in InfraStruXure Central / StruxureWare Data Center Expert, both registers must be polled together.

                        Product Line:

                        InfraStruXure Central / StruxureWare Data Center Expert

                        Environment:

                        Modbus communications

                        Cause:

                        Modbus registers are limited in size, which limits the values they can store and return to a BMS. Unsigned values can not exceed 65535. Because some values returned by ISXC may be greater than this maximum value, we have created the ability to use 2 registers together as a pair to allow for this larger output. If you choose to configure 31001 as a dual register, it will encompass 31001 and 31002.

                        Resolution:

                        When polling these registers, poll both 31001 and 31002 (or whatever register pair you have set up this way) during the same poll. Failure to do so will return invalid results.

                        What are the dimensions of the INS400 single handle transfer switch 31150?

                        205mm x 395mm x 155mm (H x W x D) excluding the handle.
                        Overall depth with standard handle is 213mm.
                        See attached.

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

                        Code = 31052 Suits INS320 to INS 630 - Black

                        What is the part number for a floor box which is 310 x 310?

                        The INS62044 has the dimensions of  311mm x 311mm x 105mm complete with a square plastic recessed lid. This part has provisions for 4 power and 4 data (suits 4 x 2000 or C2000 Series outlets). 
                        The base is metal which is used primarily in a concrete floor.

                        For further information please visit the following link: www.clipsal.com/Trade/Products/ProductDetail?catno=INS62044
                         

                        What is the torque setting for the screws in the Iconic PDL381 mech products?

                        For the screws in the Iconic PDL381 mech products, the torque setting should be 0.8Nm (M3.5 screw as per Table 8.7 AS/NZS 3100)

                        Does part code 31288 - INS630B TO 2500 FRONT STD ROTARY HANDLE include a handle?

                        No, the 31288 - INS630B TO 2500 FRONT STD ROTARY HANDLE does not come with a handle.

                        Spare handle is part code 31296 (indent)

                        Can a data or AV outlet be added on the plate with 800 series integrally switched sockets

                        No. The joint Australia/New Zealand Wiring Rules (AS/NZS 3000) require that all faceplates comply with AS/NZS 3112, clause 3.2 of which prohibits mixing of these voltage levels on the same faceplate

                        Can StruxureWare Data Center Expert output a 32 bit register with its Modbus output?

                        Issue:

                        A single register in StruxureWare Data Center Expert's modbus output is limited to 16 bit.

                        Product Line:

                        StruxureWare Central / StruxureWare Data center Expert

                        Environment:

                        StruxureWare Central any version
                        StruxureWare Data center Expert any version

                        Cause:

                        The output of a single register for StruxureWare is a 16 bit unsigned integer. This means that any value larger than 65535 can not be handled by a single register. This includes values lower than 65535 that report with a decimal such as 6553.5. DCE will output 65535 but your BMS will need to divide by 10 in such cases.

                        Resolution:

                        We can not output a 32 bit register in StruxureWare. To overcome this limitation, StruxureWare Data Center Expert can be configured to output a value to 2 registers. This must be configured during the initial setup for the output of each register. StruxureWare does not know which registers may be too large for an individual register so each must be done manually. Each should be polled a 16 bit unsigned integer

                        To configure this option, go to the system menu and building management settings. Select the device that you will be using and choose modify device settings. If you double click any register, you get the option to "Edit the Slave Sensor Register Value" which is not necessary and you get the option to "Edit the number of registers used for this sensor". This second field can take a value of either 1 or 2. For values above 65535, you must enter the number 2 and hit OK. If the register chosen was 31000, the next available register will now be 31002. The sensor that may have been set to use 31001 will now change. This is also why this should be done upon initial setup as if the system is already configured and a register is changed, the polling software must be reconfigured with the new registers.

                        If you set 31000 to a double register, you then need to poll 31000 and 31001. you then take the 1st register and left shift the first register (31000) by 16. In binary, it would look like this:

                        Assuming a value of 131071, a 32 bit register would return:
                        00000000000000011111111111111111

                        With 2 registers, you must poll both.
                        31000 returns 0000000000000001 If this were a single register, = 1
                        31001 returns 1111111111111111 = 65535

                        With 2 registers however, you must left shift the 1st register and add it to the second.

                        00000000000000010000000000000000 is the 1st register left shifted by 16 and is equal to 65536.
                        Add this value to the value returned from the second register:
                        1111111111111111 = 65535


                        Now you have a 32 bit number capable of holding values up to 4,294,967,295
                        00000000000000011111111111111111 = 65535 + 65536 = 131071

                        This math must all done on the side of the querying application.
                         

                        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.
                         

                        How to read CM2000 registers from Wonderware software using an ECM

                        Product Line
                        CM2000
                        ECM

                        Environment
                        Modbus Register reads

                        Resolution
                        In order to read the CM2000 registers through an ECM module, Wonderware requires 30,000 added to the register number. Example: register 1003 in the CM2 would be read as 31003 in Wonderware.

                        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 are the torque settings for the screws in the terminals for the Iconic sockets?

                        For the screws in the Iconic sockets, the torque settings should be as below as per Table 8.7 AS/NZS 3100:
                        • All single GPOs 2Nm (M5 screw)
                        • Twin horizontal GPOs without extra switch 2Nm (M5 screw)
                        • Twin horizontal GPOs with extra switch 1.2Nm (M4 screw)
                        • Twin vertical GPOs 1.2Nm (M4 screw)
                        • All quad GPOs 2Nm (M5 screw)

                        Supported USB hub for use with NetBotz appliances.

                        Issue:

                        Supported USB hub for use with NetBotz appliances.

                        Product Line:

                        NetBotz

                        Environment:

                        NetBotz USB communications

                        Cause:

                        Configuration recommendations.

                        Resolution:

                        The Belkin TetraHub: Model F5U231 will replace the existing APC hub as the supported USB hub for use with NetBotz USB connections.

                        Mapping NetBotz language id to string.

                        Issue:
                        Mapping NetBotz language id to string.

                        Product Line:
                        NetBotz

                        Environment:
                        NetBotz Advanced View.

                        Cause:
                        N/A

                        Resolution:

                        fr_FR = French
                        de_DE = German
                        ja_JP = Japanese
                        zh_CN = Chinese
                        ru_RU = Russian
                        pt-BR = Brazilian Portuguese
                        es_ES = Spanish
                        it_IT = Italian
                        ko_KR = Korean

                         

                        Is there a double switch socket with USB ports (not charger)?

                        USB-USB sockets are not allowed as all power outlets must comply with AS/NZS 3112, clause 3.2 which prohibits mixing of these voltages on the same faceplate.

                        We do have a USB charger mech which is available and is allowed to be installed on the same plate as power outlets. Unfortunately this currently does not fit in any double socket plates, and is only available with a single socket. (A unit to fit doubles is in development)

                        AP5610, AP5615, and AP5616 KVM Switch LDAP Implementation Example


                        Issue

                        I need help setting up LDAP with my AP5610, AP5615, and AP5616 KVM Switch.


                        Product Line


                        • KVM Switches
                          • AP5610
                          • AP5615
                          • AP5616
                        Environment

                        • All firmware versions
                        • LDAP or LDAPS configured in your environment

                        Cause

                        This article is provided as an example LDAP set up.


                        Resolution

                        Refer to the PDF attachment in this knowledge base.

                        NetBotz location information not retained on Pelco camera after reboot.

                        Issue:
                        NetBotz location information not retained on Pelco camera after reboot.

                        Product Line:
                        NetBotz
                        Pelco Cameras

                        Environment:
                        Botzware version 4.2 and lower that support Pelco cameras

                        Cause:
                        In NetBotz Advanced View, you are able to put specific location information to the NetBotz appliance, all of it's pods, and it's sensors. In the case of a Pelco camera, you can also add the camera to the NetBotz appliance as a shared pod.

                        We have seen that during a reboot, this location information is not retained for the Pelco camera only. You can re-add this information but it will again be lost on subsequent reboots.

                        Resolution:
                        This is  resolved in Botzware version 4.3
                         

                        What is the Allegro Rompager version that runs on the ION meters to make the webmeter functionality work?

                        The Allegro Rompager version that is running on the ION meters is version 3.10. The DOS exploitable version is 2.10 so this security threat is not an issue for ION meters.



                        • Date Created: June 17, 2008
                          Last Revised: February 17, 2009
                          Public
                          Original Author: MN
                          All content © 1992-2009 Schneider Electric

                        Legacy KB System (APS) Data: RESL197832 V1.0, Originally authored by KBAdPM on 02/17/2009, Last Edited by KBAdPM on 02/17/2009
                        Related ranges: ION7300, ION8600, ION7550/ION7650

                        Are EasyPact CVS circuit breakers for sale in the USA or Canada?

                        Product Line:
                        EasyPact CVS circuit breakers

                        Cause:
                        This breaker is popular overseas and there is interest in the US

                        Resolution:
                        There are no plans for a general release of the EasyPact CVS circuit breaker line in North America.

                        Which are the compatible printers that can be configured with Magelis XBT GT terminals.

                        The list of compatible printers with Magelis XBT GT terminals are as follows:

                        Target Connection with - USB, LPR, IPP
                        a) HP PCL3 (HP PhotoSmart, HP DeskJet series printers)
                        b) HP PCL5 (HP LaserJet series printers)

                        Target Connection with - COM1, USB-PIO, LPR, IPP
                         
                        a) Epson ESC/P command compatible
                        b) Text (ASCII) supported printer
                         
                        Note that XBT GT terminal does not support all Epson and HP printers. Rather it supports only those printers that support PCL3 and PCL5 printer protocols.

                        Note:

                        1. XBTGT 2110, 2120, and 2220 only support USB and USB-PIO for HP PCL3 and HP PCL5.
                        2. On XBTGT targets, it is not possible to use COM1 port for both the script driver and the target printer. If you do have both set to COM1, both will fail to print in runtime.
                        3. Use commercially available printer cables. 

                        Power Over Ethernet configuration supported by NetBotz products.

                        Issue:

                        Power Over Ethernet configuration supported by NetBotz products

                        Product Line:

                        NetBotz

                        Environment:

                        NetBotz version 3 Rack appliances and POE

                        Cause:

                        POE options that work with supported NetBotz version 3 rack appliances.

                        Resolution:

                        IEEE compliance offers 2 alternatives for Power Over Ethernet (POE). Alternative 'A' allows for power to be passed through wires 1, 2, 3, and 6 on a Cat-5 switch are the transmit and receive wires. Alternative 'B' allows for power to be passed using the unused pairs 4, 5, 7, and 8 on a Cat-5 cable.

                        Alternative 'A' is usually output by a switch or endspan device. Alternative 'B' is more often used by a midspan device such as a POE injector. APC's POE injector (NBAC0303) inserts power on the Cat-5 cable using alternative 'B'

                        NetBotz POE compatible appliances work with either alternative and should power on with alternative 'A' or 'B'.

                        Java has discovered application components that could indicate a security concern error when the NetBotz web page link to launch Advanced view is used.

                        Issue:
                        Java has discovered application components that could indicate a security concern error when the NetBotz web page link to launch Advanced view is used.

                        Product Line:
                        NetBotz

                        Environment:
                        Botzware version 3.3 and higher

                        Cause:
                        The JRE release 1.6.0_19 update includes checks for programs containing both signed and unsigned components and you see warning popup messages whenever mixed code is encountered in the application. If you have installed this version of Java and try to use the Launch Advanced View link, you will receive this error. This simply means that not all components are signed.

                        Resolution:
                        For more information about Mixed Signed and Unsigned Code, go to: https://java.sun.com/javase/6/docs/technotes/guides/jweb/mixed_code.html

                        To go past this error and launch Advanced View, click "No" when asked to block these components. Clicking "Yes" will cause Advanced View not to launch. If you are concerned with the component to launch Advanced View, simply use the shortcut in your Windows Start menu.
                         

                        Pelco Sarix cameras do not get full frame rate with Botzware 3.3

                        Issue:

                        Pelco Sarix cameras do not get full frame rate with Botzware 3.3

                        Product Line:

                        NetBotz

                        Environment:

                        NetBotz version 3 with 3.3 firmware.

                        Cause:

                        With the release of Botzware 3.3, NetBotz supports a new line of Pelco Cameras. We have tested 3 Sarix cameras and support the entire line by design.

                        Due to the large size of JPG images coming from the Sarix cameras, we are unable to pull the images from the camera and then show them or save them in an alert at the full 15 fps rate. We have tested 3 different cameras and have seen the following frame rates when set at 15 frames per second:

                        IXS0C-AAWLL39 - 10 fps
                        IXE20DN-ABAWU52 - 5 fps
                        IX30DN-AAWL040 - 3 fps

                        Resolution:

                        With the release of BotzWare 4.0, this should no longer be an issue.

                        Unable to load audio stream error on NetBotz appliance.

                        Issue:

                        Unable to load audio stream error on NetBotz appliance.

                        Product Line:

                        NetBotz

                        Environment:

                        NetBotz version 3 appliances.
                        Camera Pod 160

                        Cause:

                        After listening to live audio on a CP160 (w/ attached microphone) for a few seconds, an error message may pop up and the audio may stop. The error message will look similar to this:

                        Unable to load "Camera Pod xxxxxxx" audio stream: Cannot connect

                        This has only been see on fully loaded version 3 NetBotz appliances and only on very rare occasions. This error occurs because the processor is too busy to play the full audio clip as it is required to process other functions on the system such as storing data or creating new alerts.

                        Resolution:

                        To resolve this issue, it may be necessary to reduce your system load by removing sensors or sensor pods.

                        Why does 'address out of range' error come in Vijeo Citect.

                        Actually Vijeo Citect reads digital addresses in blocks of 16 bits. So if there is a digital tag at C1000, Citect will read from C993 to C1008 in a single request. If the address C993 does not exist then 'address out of range' error comes. Because of this optimization of digital read requests make sure that there are valid addresses in the PLC. In some PLCs the valid ranges of all memory addresses can be set and make sure that the setup in the PLC is what Citect is going to read. If the range cannot be adjusted then do not use any digital tags within the first and last 16 digitals.

                        Vijeo Citect also tries to block reads together and may try to read across invalid addresses. So if C1000 and C1100 are configured, Citect will try to read from C993 to C1105. If any address is invalid between these tags then also 'address out of range' error comes. This is quite unlikely as almost all PLC contain continuous memory with no holes.

                        Where can I find the operating time (run time) on the ATS48 softstarter?

                        Issue:
                        Where can I find the operating time (run time) on the ATS48 softstarter?

                        Product Line:
                        Altistart 48, ATS48

                        Environment:
                        All

                        Cause:
                        Run time

                        Resolution:
                        Go into SUP menu.

                        RNT parameter is operating time in hours since last reset (if there was ever a reset to begin with).
                        In hours up to 999 hrs (examples: 001 is 1hr and 111 is 111hrs)
                        In kilo-hours from 1000-65535 (examples: 1.11 is 1110 hrs and 11.1 is 11100 hrs)
                        Above 65535 hrs (65.5) the display resets to zero.

                        Operating time is counted when the motor is not stopped, i.e. when the thyristors fired (heating, acceleration, steady state, deceleration, braking) and in continuous bypass operation.

                        INFORMATION BULLETIN - Upgrading Rack ATS Firmware (AP77XX) - potential to permanently damage ATS during download


                        Issue

                        Please be advised that during a firmware upgrade to version apc_hw02_aos357_g2ats357.exe, apc_hw02_aos374_g2ats370.exeapc_hw02_aos374_g2ats371.exe, apc_hw02_aos390_g2ats390.exe, or apc_hw02_aos390_g2ats392.exe, if you have a load attached to the ATS, there is a probability to permanently damage the Rack ATS. The ATS will begin to switch sources back and forth and this will cause permanent damage to your ATS as well as drop any loads connected downstream of the ATS.


                        Product Line
                         

                        Rack Automatic Transfer Switches (AP77XX), specifically the models below ONLY:

                        • AP7721
                        • AP7722A
                        • AP7723
                        • AP7724
                        • AP7730
                        • AP7731
                        • AP7732
                        • AP7750A
                        • AP7752
                        • AP7752J
                        • AP7753


                        Environment
                         
                        • All firmware versions
                        • All serial numbers
                           


                        Cause 

                        There is a probability to permanently damage the Rack ATS if the procedure is not followed.


                        Resolution


                        Required Download Procedure - two options:

                        1.) Disconnect the secondary input power source and apply power to the ATS through the primary source only during the firmware update. This will remove the redundancy from your loads for approximately five minutes but will not require powering down your attached load.


                        OR

                        2.) Remove ALL connected loads to the ATS and apply the firmware update using the instructions below.



                        Please refer to the attachment below for the firmware update procedure. Failure to follow these instructions could lead to permanent damage on the Rack ATS product.

                        Can I poll 6 Digit Modbus registers with Telepace Studio?

                        The MSTR and MSIP use a block of registers to store their configurations.

                        If the MSTR block uses register 41001 in the SCADAPack as it's configuration start register, then :

                        41001 = Comm port number

                        41002 = function code

                        41003 = slave controller address

                        41004 = slave register address

                        41005 = master register address

                        41006 = length

                        41007 = time out in 0.1s increments

                        Trying to configure the MSTR block in Telepace prevents you from putting in a slave register address greater than 49999.

                        Using a PUTU block, you can put an unsigned integer in the range 40001-65535 into register 41004 to indicate the slave register address. It appears as though the program will take the value in register 40004 and subtract 40001 to determine the holding register offset that gets sent in the actual modbus message.

                        For example, using PUTU to put a value of 50010 into register 40004 would then cause the MSTR block to poll for a holding register with an offset of 10009 in the message which would correspond with a 6 digit address of register 410010.

                        The largest unsigned integer you could put into register 40004 would be 65535, which would correspond with a 6-digit modbus holding register of 425535.



                         

                        Adding External Batteries to an SU, SUM, SURT, SURTA, SURTD or SUA series Smart-UPS XL

                        Issue:
                        When configuring external batteries with a Smart-UPS XL you must manually tell the UPS how many batteries are connected.


                        Product Line:

                        Smart-UPS XL
                        NOTE: This does not include "SMX" units. SMX models have smart batteries which do not require the use to manually add them.

                        Environment:

                        All XL models, All Serial Numbers

                        Cause:

                        Smart-UPS XL models do not feature communication with the battery packs.

                        Resolution:

                        When configuring external batteries with a Smart-UPS XL you must manually tell the UPS how many batteries are connected. The exception to this is the new SMT and SMX Smart-UPS which use intelligent battery packs and will auto-configure.

                        Each external battery pack is configured as ""1"" within Powerchute Business Edition or the Network Management card and we recommend no more than 10 battery packs connected.

                        The exceptions to this are:

                        SU48RMXLBP - Each unit counts as ""2"" in the interface. Connect a maximum of 5 of these packs.

                        UX or UXA Series Ultra Battery Packs - Each unit counts as ""5"" in the interface. Connect a maximum of 2 of these packs.

                        SURT - Depending on their firmware revision, some SURT units may count their internal battery as number 1. (IE: An SURT3000XLT + 1 External Battery would be set to 2 in Powerchute). On these units ""0"" is not an option that is available in Powerchute or the Network Management Card. If you are able to set your unit to ""0"", the first external battery would be ""1"". If you are not able to set your unit to ""0"", the first external battery would be ""2""

                        All other Smart-UPS count the internal battery as 0. (IE: An SUA3000XL + 1 External Battery would be set to 1)

                        For Information on which battery packs are compatible with your UPS or what estimated runtimes will be for your configuration, please visit the product page for you UPS at https://www.apc.com

                        "

                        NetBotz version 3.3 sensors do not update to modbus registers to double registers automatically upon upgrade.

                        Issue:

                        NetBotz version 3.3 sensors do not update to modbus registers to double registers automatically upon upgrade.

                        Product Line:

                        NetBotz

                        Environment:

                        NetBotz version 3 appliances
                        version 3.3 update
                        Modbus Output.

                        Cause:

                        New configuration to allow for larger sensors.

                        Resolution:

                        Prior to Botzware 3.3, all NetBotz sensors were single registers. A single Modbus register is 16 bits which is limited to 65535 for it's largest number. For numbers greater than that, NetBotz appliances now allow for the use of 2 registers to monitor a single sensor. To monitor this 2 register number, you would poll both registers, left shift the first register by 16 and then add the 2 registers together.

                        To left shift, you can use Windows calculator (calc.exe) in scientific mode, enter the number, and then hit the "Lsh" button and type 16.

                        If you are already using a Netbotz appliance and update to version 3.3 or higher, the output registers will not automatically update to the new double register option. To update the current sensors, they must be removed and re added both physically and through Advanced View. The system will then create a new register map. Please note that removing and re-adding a sensor will remove any thresholds created for this sensor.

                        In some cases, there are sensors that are internal to the appliance and can not be removed. In order to get these sensors to update, the appliance's configuration must be reset. This will reset all data on the unit.

                        Please note that registers may be listed in documentation since this change as INT32. Registers are only 32 bit AFTER they have been recalculated using both registers and the left shift functionality. If you poll only a single register, that register is only 16 bit.
                         

                        Vista cannot find generic diagram for CM4000 device.

                        Goals and Symptoms

                        A CM4000T device is added to an SPM 7.0.1 system. When clicked on in Vista, an error message appears: "A generic diagram for the selected device cannot be found".
                        In the alarms panel on the web interface, there are links to source devices. Clicking on these links displays a blank page, even if the device is manually pointed to a diagram in Vista.
                        In Vista, the device type / product field displays a large meaningless number instead of a product type.

                        Keywords: SPM 7, SPM7, CM4

                        Causes and Fixes

                        The most likely cause is that the device is loaded with an old, unsupported firmware. In this old firmware, the device type register had a different address. Hence, SPM cannot determine the device type automatically, causing diagram linkage errors.

                        It appears that the data returned from the Device Type register is incorrect. This explains why SPM does not know which diagram to use, and why you see the strange numeric value for the device type. SPM Vista polls this register as well as the firmware version to determine which diagram to use.



                        To confirm these suspicions, the following check can be performed:

                        First, check the meter's translator file: \ION Enterprise\system\translators\cm4000.xml
                        Near the top of the file you should see where it looks for "FAC1 Device Type", it should be register [40]3010:

                        <ModbusInfo IONHandle="4864" Name="FAC1 DeviceType" ModbusAddress="403010" RequestType="R" Format="UINT16" Offset="0x75B3" CacheSpec="C" SetupReg="1" DisableNotAvailableCheck="0" ConfigWrite="1">
                        <Enumeration Ordinal="15101" Value="CM4000" />
                        <Enumeration Ordinal="15103" Value="CM4250" />
                        <Enumeration Ordinal="15111" Value="CM3250" />
                        <Enumeration Ordinal="15112" Value="CM3350" />
                        <Enumeration Ordinal="15001" Value="CM4000T" />
                        </ModbusInfo>

                        Next, use the meter's front panel diagnostic menu to read register 3010. For a CM4000T it should be value 15001 as stated above.

                        To resolve the issue, update the device firmware to the most recent.


                        Legacy KB System (APS) Data: RESL209757 V1.0, Originally authored by ViWa on 11/24/2012, Last Edited by ViWa on 11/24/2012
                        Related ranges: Power Monitoring 7.0

                        How do I resolve the build message "C0106: Out of global data memory" in SoMachine Logic Builder?

                        Issue
                        When attempting to Download or Code Generate my PLC Application in SoMachine Logic Builder,  the build message "C0106: Out of global data memory" appears in the Messages zone.

                        Product Line
                        SoMachine v3.0, SoMachine v3.1, SoMachine v4.1, SoMachine v4.2, SoMachine v4.3
                        M238, M241, M251, M258, LMC058, XBTGC, HMISCU, XBTGT w/ Control, XBTGK w/ Control

                        Environment
                        SoMachine Logic Builder, Windows 7, Windows 10

                        Cause
                        The build message "C0106: Out of global data memory" is caused by the application having more variables used in the Persistent Retain memory than there is physical memory on the PLC.

                        Resolution
                        Reduce the number of variables declared in the PersistentVars Application object or declared as "VAR_GLOBAL PERSISTENT RETAIN" in the Global Variable List (GVL) node.
                        Do this incrementally and go to the Build menu and perform the following actions in sequence:
                        1. Clean
                        2. Build
                        3. Generate Code
                         
                        After each Generate Code, check the Message list to see if the C0106 message has disappeared.

                        If so, one can see the used memory in the message list in the form of "Memory area 5 contains Persistent Data:…"
                        For example in Screenshot 2 below, 2044bytes is the maximum for the HMISCU PLC - of which 46% is used.
                         
                        Tip: Watch for ARRAYs, DUT (structures) and combinations of the two (ARRAYs of DUTs), which can increase the defined memory usage multiplicatively.
                         
                        To see how many bytes the PLC has allocated to the Persistent Retain Variables area, go to the SoMachine Online Help [PLC type section] -> Programming Guide -> Memory Mapping section
                         

                        Hardwiring to 120v, 208v, and 240v loads from a 208v/240v SmartUPS RT UPS


                        Issue:

                        Hardwiring to 120v, 208v, and 240v loads from a 208v/240v SmartUPS RT  UPS

                        Product Line: 

                        Smart-UPS RT

                        Environment:

                        All models with "T" in the suffix of the part number. (IE: SURT3000XLT, SURT8000RMXLT6U)
                        Note: This does *NOT* include SURTD5000RMXLP3U or SURTD6000RMXLP3U. These two models are split phase 4 wire (Hot/Hot/Neutral/Ground) units and do not require a stepdown transformer to support 120v loads.

                        Cause:

                        Smart-UPS RT units designed for 208v/240v environments have unbalanced 3 wire outputs and require a transformer to supply 120v loads.

                        Resolution:
                        • The 208V/240V Smart-UPS RT is a single phase UPS with a 3 wire unbalanced output.
                        • They require 2 hots and a ground on the input, and 2 hots and a ground on the output.
                        • They do not use a neutral.
                        • They require a stepdown transformer to power 120v loads and provide a Neutral

                        The output of the UPS is unbalanced, meaning that from hot to hot you will see 208 volts (or 240v if so configured), however it is not two balanced 120 volt legs as you would traditionally see from 208v/240v utility power. The two output legs are 180 degrees out of phase and from hot to hot they will measure 208v or 240v. All of these units default to 208v out and can be configured to 240v via the network management card or LCD interface.

                        Attempting to hardwire out to a 120V load without the use of a transformer will result in load drops and possible load damage!

                        In addition to a selection of smaller 5kva plug in step-down transformers, APC manufactures 3 larger hardwire step-downs in 10kva and 20kva capacities - APTF10KT01APTF10KW01, and the APTF20KW01
                        All three of these units create their output in a similar fashion. A neutral is created via a center tap on the transformer.

                        To supply a 120 v load, the transformer provides:

                        • 2 120 volt legs that are 180 degrees out of phase
                        • Ground
                        • Neutral

                        This creates a traditional 240 v/120 v panel where there are 2 legs of 120 v and from hot to hot you would measure 240 volts.

                        To supply a 208 v load, the transformer provides:

                        • 120 v Hot Leg
                        • 88 v Hot Leg (180 degrees out of phase from the 120 v leg)
                        • Ground

                        In this configuration you would measure 208 volts from Hot to Hot.

                        For detailed wiring directions, diagrams, and specifications, please consult the users manual for your step-down transformer.

                        Using both of these configurations you can support both 208v and 120v loads, however you are not able to output to a traditional 208v / 120v panel where there are 2 120v legs that are 120 degrees out of phase. If a 208v / 120v output panel is required you must use one of our split phase solutions. We offer 2 split phase RT units (SURTD5000RMXLP3U and SURTD6000RMXLP3U) as well as the entire Symmetra LX line. A split phase UPS will require a 4 wire input and will output 2 balanced 120 v legs, a ground, and a neutral. The split phase RT units will require the SURT018 hardwire kit to be used in a hardwired application.

                        There is an application with Altivar 38 with pump switching card where the auxiliary pump is driven by an Altistart 48.There is also Modbus connection...

                        Goals and Symptoms

                        There is an application with Altivar 38 with pump switching card where the auxiliary pump is driven by an Altistart 48.There is also Modbus connection where the master is a Twido PLC and the slaves are the ATV38 and the ATS 48. The problem is that en error ERR 7 (erreur LS) is appeared at the ATV38 display.What kind of error is that and what can we do about it?

                        Facts and Changes

                        ATV38 with Modbus connection

                        Causes and Fixes

                        Product trips transiently to "Err3" or "Err7" fault. Both faults type are generated by the display module.
                        This one communicates with the microprocessor of control card .
                        When incorrect messages occur during the communication and after some repetition of exchanges , the display module shows to "ErrX".
                        This is a very difficult fault to reproduce because depending of environment ( lenght of wire between display module and control board , motor running, disrupted site ) and the combination between display module and control board.

                        Origin of problem :

                        Insufficient immunity of communication facing the various disturbances.
                        The communication frames managing is made by integrated components called "drivers". One is located on control board, the same is inside display module. This fault is the result of wrong interpretation of display module of logic level between two communication frames.
                        This technical conceived problem is appeared from August 2000.

                        Corrective action:

                        This failure has been resolved by a modification of two values of resistors inside the display module.
                        The revision levels become:
                        · A20, B20 for the ATV58 display modules.
                        · A02 for the ATV58Fdisplay modules.

                        This evolution is applied from the week 47/2000 on all manufactured PRODUCTS and all VW3A58101 spare parts.


                        Information for internal use:

                        We have noticed that anyway neither control board nor display module have never been directly to the fault origin . Fault "Err X" is always due to the association of two items.

                        On no account this failure cannot to disrupted the motor running but she can to disturb only the programming of product.

                        If during the programming, a customer encounters to " Err3 " or " Err7 " with a product manufactured from the week 31/00 to 46/00 , it is advised to exchange only the VW3A58101 display module.

                        This problem can also appear if the baudrate of internal communication was modified ( subD 9 pins ) and there is a difference between the keypad and internal modbus.

                        A solution is to reset the inverter with the 50/60 Hz switch to return the baudrate in factory setting, don't forget to accord the Twido PLC.


                        Legacy KB System (APS) Data: RESL156317 V3.0, Originally authored by on , Last Edited by on
                        Related ranges: Altivar 38
                        Show More