reducer brass cond 63/50mm

Cable Management Machined Brass, 63mm Male to 50mm Female Brass Reducer

Catalogue Number: 1264/6M
reducer brass cond 63/50mm
RRP (Inc. GST)


hide show
Product brand
Range of product
Series 1264
Product destination
  • diameter: 50-50 mm tube
  • diameter: 63-63 mm tube
    • Length
      63-63 mm
    • AS 1721
    • AS 2052
      • Unit Type of Package 1
        Number of Units in Package 1
        Package 1 Weight
        326 g
        Package 1 Height
        66 mm
        Package 1 width
        84 mm
        Package 1 Length
        90 mm
        REACh free of SVHC
        EU RoHS Directive
        Pro-active compliance (Product out of EU RoHS legal scope)
        Toxic heavy metal free
        Mercury free
        RoHS exemption information
        China RoHS Regulation
         Pro-active China RoHS declaration (out of China RoHS legal scope)

        Frequently Asked Questions

        hide show

        What is the dimension of 1264/2M, 25mm (male) to 20mm (female) brass reducer?

        Dimensions of 1264/2M are as follows:
        A = 25mm
        B = 21mm
        C = 16mm

        For further information, please visit

        What are the dimensions of the wall box to suit the B12/30/6 Multi-Gang Switch?

        The wall box to suit the 12/30/6 Multi-Gang Switch is a 164/6.

        The dimensions of the wall box is a 164/6 are 278mm(W) X 97mm(H) X 58mm(D).

        Some of the key features are:

        • 30 series rocker type
        • B-Style
        • Switch arrangement 6 horizontal and 2 vertical
        • Fascia size: 303 mm Width x 120 mm Height
        • 12 number of switch apertures

        For further information please visit

        What is the maximum wire length for digital inputs and outputs on Powerlogic meters?

        Customer would like to determine the maximum distance between a meter and a digital input source or an output signal receiver 

        Product Line
        ION and Powerlogic meters with digital I/O options

        There is no absolute maximum distance of I/O wiring and actual length depends on several factors including:
        • The field voltage source
        • Wire AWG and manufacture specs
        • Wire type
        • Electrical noise and environment 
        • Meter specs 
        * The calculations below are meant to be a rough estimation and they are not accurate unless all the factors are considered *

        Digital Input Example:

        The PM800 equipped with a PM8M2222 Digital I/O extender with field source of 120 Vac. The wire to be used is a 16 AWG with a resistance of 4.016 ohm per 1000 feet. The PM800's digital input's turn on voltage is 20 Volts and the maximum current draw is 2 mA.

        Vdrop= Current X R (per1000 feet) *2*length
        Vinput= Vsource - Vdrop

        The Vinput needs to exceed the turn on voltage in order for the meter to recognize the signal. In this example, the theoretical maximum would be in the hundreds of thousands of feet. Needless to say, noise as well as other factors will affect the quality of the signal and practically limiting the cable run.

        Digital Output Example

        A similar calculation can be established for digital outputs once the specifications are known. For example, the ION 7650 has a maximum load of 3 A @ 380 VAC, hence the rated burden is 126.666 ohm. The total loop resistance should be less than the rated burden.  A 16 AWG wire has a resistance of 4.016 ohms per 1000 feet and the maximum theoretical distance that would sustain current without significant voltage drop would be 31,500 feet. Moreover, Form A digital output have a similar calculation given the maximum load voltage and current as well as the input source. For example, if the turn on is 20 volts on a PLC and the ION 7650's form A relay is rated at 80mA @ 30 VDC then :
        Vdrop= Current X R (per1000 feet) *2*length
        Vinput= Vsource - Vdrop
        The theoretical maximum attainable distance would be around 15,600 feet for a 16 AWG wire originating from the ION7650's I/O output.

        NOE77101 Exec Firmware version 4.4

        Goals and Symptoms

        Provide the list of enhancements and fixes that are included in exec firmware version 4.4 for the 140NOE77101.

        Facts and Changes

        140NOE77101 exec firmware version 4.4

        Causes and Fixes


        • Incorporate IGMP support into the Global Data implementation.

        Problems fixed:
        • The 'Local Rack' web page does not show any modules or racks that are linked to the first local
        rack with an 'XBE100 00'.
        • The NOE manages two crash logs that could be found in two files named
        /FLASH0/wwwroot/conf/diag/crash.log and /FLASH0/fw/crashlog.txt but, only one of them is
        • shown in the Web pages. The two crash logs need to be merged into one.
        • The online help describing the number of PRODUCTS that supports the MBP_MSTR block is
        • The start address and length of the write data to the slave MBP_MSTR block is described
        • The online description for the fourth implied register (control [5]) of the MBP_MSTR block is
        • The online help for the MBP_MSTR block does not show where the data that will be used to write
        to or read from the remote device is stored. There appears to be only one data buffer to store both
        the write and read data base. No description can be found specifying the structure of the data buffer.
        The description should show that the data buffer must be the size of the data to be written and the
        data to be read. It should also describe that the data buffer stores the write data first followed by the
        read data from slave.
        • Online information is needed for the MBP_MSTR block stating that the control buffer and the data
        buffer must use located addresses. The MBP_MSTR block will not work with if the control and data
        buffer are defined using un-located memory addresses. (i.e., %MW).
        • The 'NOE 771 01 and 'NOE 771 11 V2.0' referenced in the online help, applies only in Concept
        with the MSTR block. Function 23 client and server support in Unity (MBP_MSTR) applies only
        to the 'NOE 771 01' and 'NOE 771 11' which can be found in V3.0 of the NOE firmware.
        • The NTP service behavior in UNITY is not the same as that found in and a PL7 application. In
        PL7, the PLC clock is update is identical period to that configured for the update of the module by
        the server. The clock is updated too often in a Unity application.
        • The I/O Scanner does not check the reply from the slave to ensure that the Modbus transaction ID
        matches the current request that has been sent out.
        • If the NOE is configured with a duplicate IP address, it still responds to its previously configured IP
        • The online description for control block word 3 of the 'Write CTE' ethernet communication does not
        correctly specify the number of words to transfer. The format appears to require 11 words based on
        the 'datbuf' length, but the length needs to be 12 in order for the MBP MSTR to work.
        • On a HSBY switchover and re-starting 'I/Scanner', sometimes on NOE swap over, it was seen that
        new Primary NOE takes up to 12sec to talk to devices.
        • Bootp does not work on a '140NOE77101' with version 4.3 Exec Firmware.
        • Communications gradually degrades then stops. After 13-30 minutes it recovers on its own.
        • A broadcast storm on the network results in 'Stop Code 80' in PLC.
        • On sending a trap event to the network manager the NOE should be identifying itself as
        136141-3833 (where 3833 is the identification for Schneider), but the NOEs instead responds
        with an identity 123456, etc.
        • SMTP may not work with certain external email servers. The documentation has been updated to
        recommend the use of Lotus Domino, Microsoft Exchange, or Sendmail.
        • 'I/O scanner' is disabled when another entry is disabled.
        • The web page for exec firmware version 4.20 shows that 10/100BASE-T is being used when the
        NOE is connected using fiber optic.
        • If the subnet mask is changed from to or the frame type is changed from
        Ethernet II to IEEE802.3, the IO Scanner will stop working after the application is downloaded with the
        NOE. The IO Scanner starts to work if the Concept is disconnected from the NOE.
        • During a Hot Standby system switch over, sometimes the primary NOE goes into fault mode for
        20 seconds and then starts communicating normally.

        Legacy KB System (APS) Data: RESL199225 V1.0, Originally authored by AlCh on 06/24/2009, Last Edited by AlCh on 06/24/2009
        Related ranges: Modicon Quantum, Modicon Quantum NOE - TR