Angled image of 503B lampholder bc 2 pin with 3/8 inch brass thread

Lamp Holders, Lampholder BC With safety skirt 3/8 inch brass Thread

Catalogue Number: 503B
Angled image of 503B lampholder bc 2 pin with 3/8 inch brass thread
Retail
$27.67
RRP (Inc. GST)
Colour White Electric (WE)
  • White Electric 1 PCE

Specifications

hide show
Product brand
Clipsal
Product or component type
BC lamp holder adaptor
Provided equipment
  • lamp holder
  • skirt
  • cap
    • Colour tint
      white
      Device mounting
      cable mounting
      [Ue] rated operational voltage
      250 V
      Rated current
      3 A
      EU RoHS Directive
      Compliant

      Frequently Asked Questions

      hide show

      Do Clipsal have a 503 series batten holder with 10mm thread ?

      Yes , the part number is 503e-we
      For more information on batten holders please visit the Clipsal web site on the link provided https://www.clipsal.com/Trade/search-results?q=batten%20holders

      What is the decibel rating on a 7106A?

      The decibel rating is 50dB for our 7106A.

      What is the decibel rating on a 7106A?

      The decibel rating is 50dB for our 7106A.

      What is the decibel rating on a 7106A?

      The decibel rating is 50dB for our 7106A.

      What are the cable part numbers for M340 IO modules with 40 pin connections ?

      The following M340 IO modules require preconfigured 40 pin connector cable with color coded flying leads.
      Table below shows module and cable part numbers.

       
      Discrete Module Connection Cable Part # Qty needed
      BMX DDI 3202 1 x 40 BMX FCW 303, 503, 1003 ( 1 )
      BMX DDI 6402 2 x 40 BMX FCW 303, 503, 1003 ( 2 )
      BMX DDM 3202 1 x 40 BMX FCW 303, 503, 1003 ( 1 )
      BMX DDO 3202 1 x 40 BMX FCW 303, 503, 1003 ( 1 )
      BMX DDO 6402 2 x 40 BMX FCW 303, 503, 1003 ( 2 )
      text text
      AnalogModule text
      BMX ART 0414 1 x 40 BMX FCW 301S*, 501S* ( 1 )
      BMX ART 0814 2 x 40 BMX FCW 301S*, 501S* ( 2 )
      * S suffix denotes shielded cable for Analog IO.

      Legacy KB System (APS) Data: RESL212360 V1.0, Originally authored by DiSa on 08/24/2013, Last Edited by DiSa on 08/24/2013
      Related ranges: Modicon M340

      Web Applications Error: "Http Error 503. The service is unavailable."

      Issue
      When trying to access the application webpage, the following error occurs:
                         
      The following error is seen in Windows Application Event Viewer:
                         
                          The Module DLL HipISSEngineStub.dll failed to load. The data is the error.

      Product Line
      Power Monitoring Expert 7.2.x

      Environment
      IIS 7
      McAfee Anti Virus
      HipISSEngineStub.dll

      Cause
      Upon checking Application Pools in IIS Manager, it turns out the application pool has stopped.  However, the problem cannot be resolved by simply re-starting the application pool.  By doing so and accessing the web page, it will stop again.
                         

      If McAfee has recently been uninstalled, updated, or changed the installation somehow, there is probably still a reference to it in the ISAPI settings.  Refer to the following link for more information:

                kc.mcafee.com/corporate/index
                https://kc.mcafee.com/corporate/index?page=content&id=KB72677&actp=LIST

      Resolution
      Remove the reference to the MfeEngine in the applicationHost.config:

      1.  Navigate to: %windir%\system32\inetsrv\config

      2.  Open the file applicationHost.config as Administrator for editing in Notepad.

      IMPORTANT: make sure a copy of the original file is available before making any changes.

      3.  Edit the  globalModules section and remove the following line:
                <add name="MfeEngine" image="%windir%\System32\inetsrv\HipIISEngineStub.dll" />;

      4.  Edit the modules section and remove the following line:
                <add name="MfeEngine" />;

      5.  After editing the applicationHost.config file, save the file, then restart the IIS server using iisreset or by restarting the system.
       

      What is the lamp life of a DL1BA024?

      Issue:
      What is the lamp life of a DL1BA024?

      Product Line:
      Harmony Pushbuttons

      Environment:
      All Products

      Cause:
      Product Features

      Resolution:
      All incandesent lamps have an estimated life of 2000 hours.

       

      PME Web Application gives an "HTTP 503 Service Unavailable" error message when Reports is selected

      Issue
      The customer is receiving an "HTTP 503. The service is unavailable" error message when selecting the 'Reports' tab through Web Applications.



      Product Line
      Power Monitoring Expert 7.2.x / 8.x / 9.x

      Environment
      Web Reports

      Cause
      If Microsoft Monitoring Agent with .Net Application monitoring is installed, the 'WebReporterAppPool' Application Pool within Internet Information services is not started and crashes if started manually.

      Resolution 1
      This resolution does not require removing Microsoft Monitoring Agent. Instead, it is uninstalled, then reinstalled via the command line using a switch that prevents the .Net Application monitorng from being installed.

      To do this:

      1. Uninstall Microsoft Monitoirng Agent from Control Panel -> Programs and Features
      2. Start a command prompt in the directory that includes the Microsoft Monitoring Agent installer (it's called MOMAgent.msi)
      3. Run MOMAgent.msi NOAPM=1

      Resolution 2
      Windows updates will install a tool named the "Microsoft Monitoring Agent".  This tool applies a policy to the application pool that causes it to crash.  Uninstalling the tool through Add/Remove programs will allow Web Reports to function as expected.

      How many contacts does the electronic timer LA2KT2E have?

      Issue:
      LA2KT2E and LA2KT2U contacts

      Product Line:
      Tesys K Line Contactors

      Environment:
      IEC Contactor Accessories
       
      Resolution:
      This module has one form C contact.
      One normally open and one normally closed with a shared common.  Instructions are attached.

      Power Monitoring Expert - Web applications 503 Service Unavailable Error

      Issue
      When opening Web Applications, "503 Service Unavailable" error is displayed. 

      Product Line 
      Power Monitoring Expert 9.0

      Environment
      Web Applications
      IIS Manager

      Cause
      A potential cause for this error is when an application or a process is using port 80 (HTTP) or port 443 (HTTPS). This results in the Default Website in IIS being stopped, and when starting it manually the following error is prompted.


      Resolution
      1. following netstat commands can be used in command prompt to retrieve the Process ID (PID) of the application/process that is using port 80 or 443. In this example, the PID of the process that is using port 80 is 5484
      netstat -aon | find ":80"
      netstat -aon | find ":443"

      2. The result will be something like the below:

      In this example, the PID of the process that is using port 80 is 5484.
      3. The process associated with this PID can be found in Task Manager, Details tab (can be ordered by PID). In this example, this PID belongs to Skype.

      4. Once the process/application is identified, (if possible) it can be temporarily ended from Task Manager (right-clicking and selecting End Task), to examine if the Default Website in IIS Manager can now be successfully started which then results in Web Applications to return to normal operation. If this is the case the identified application (in this example Skype) needs to be configured to deploy another port.
      
      
      
       

      How can I reset the NetBotz 750 to defaults?

       

      Issue:

      How to reset the NetBotz NBRK0750 or NBWL0755


      Product Line:

      NetBotz

      Environment:

      NetBotz Version 5 appliances

      Cause:

      If the NetBotz appliance becomes inaccessible via the web and can not be accessed or if there appears to be corruption which you feel could be resolved by a full reset of the appliance, follow the below procedure.
      A 503 error may occur after the initial upgrade if this process is not followed as well. If a 503 error is seen when attempting web access, please see the resolution below.

      Resolution:

      If you can access the NetBotz appliance via SSH, connect using a utility such as putty.exe and when prompted, log in using root and the password you had provided upon initial root login (done via serial connection), then when prompted to press enter within 5 seconds, type a capital X. At the linux prompt type:

      /netbotz_app/reset.sh
      As of version 5.2.1, this command will change to:
      /netbotz_app/factory_reset.sh

      If you can not access through SSH, connect using the micro USB serial configuration cable. Once connected, verify you're using the correct port in device manager, then use the following settings and connect with a terminal emulation program such as Hyper-terminal or Putty:
      115,200 Baud rate
      8 Data Bits
      No Parity
      1 Stop Bit
      No Flow control.

      Open the connection and hit enter until prompted for a login.
      Log in using root and the password you had provided upon initial root login (done via serial connection), then when prompted to press enter within 5 seconds, type a capital X and hit Enter.

      At the linux prompt type:

      /netbotz_app/reset.sh
      As of version 5.2.1, this command will change to:
      /netbotz_app/factory_reset.sh

      In some cases, an extra command may help in cleaning the database such as may be the case if the firmware were downgraded  for instance:
      /netbotz_app/restart.sh stop cleanDB startApp startClubber

       

      Netbotz and FTP Return Codes

      Issue:

      Netbotz and FTP Return Codes

      Product Line:

      NetBotz

      Environment:

      NetBotz ftp codes

      Cause:

      When configuring the FTP Alert Action on a Netbotz device, the FTP server may return error codes which may viewed in the Appliance Log. The return codes may be used to further troubleshoot the problem.

      Resolution:

      The return codes for FTP servers are:

      110 Restart marker reply. In this case, the text is exact and not left to the particular implementation; it must read: MARK yyyy = mmmm where yyyy is User-process data stream marker, and mmmm server's equivalent marker (note the spaces between markers and "=").

      120 Service ready in nnn minutes.

      125 Data connection already open; transfer starting.

      150 File status okay; about to open data connection.

      200 Command okay.

      202 Command not implemented, superfluous at this site.

      211 System status, or system help reply.

      212 Directory status.

      213 File status.

      214 Help message.On how to use the server or the meaning of a particular non-standard command. This reply is useful only to the human user.

      215 NAME system type. WhereNAME is an official system name from the list in the Assigned Numbers document.

      220 Service ready for new user.

      221 Service closing control connection.

      225 Data connection open; no transfer in progress.

      226 Closing data connection. Requested file action successful (for example, file transfer or file abort).

      227 Entering Passive Mode (h1,h2,h3,h4,p1,p2).

      230 User logged in, proceed. Logged out if appropriate.

      250 Requested file action okay, completed.

      257 ""PATHNAME"" created.

      331 User name okay, need password. 332 Need account for login.

      350 Requested file action pending further information

      421 Service not available, closing control connection. This may be a reply to any command if the service knows it must shut down.

      425 Can't open data connection.

      426 Connection closed; transfer aborted.

      450 Requested file action not taken.

      451 Requested action aborted. Local error in processing.

      452 Requested action not taken. Insufficient storage space in system.File unavailable (e.g., file busy)

      500 Syntax error, command unrecognized. This may include errors such as command line too long.
      501 Syntax error in parameters or arguments.

      502 Command not implemented.

      503 Bad sequence of commands.

      504 Command not implemented for that parameter.

      530 Not logged in.

      532 Need account for storing files.

      550 Requested action not taken. File unavailable (e.g., file not found, no access). (550 a:: no such directory means no diskette in a: drive.)

      551 Requested action aborted. Page type unknown.

      552 Requested file action aborted. Exceeded storage allocation (for current directory or dataset). 553 Requested action not taken. File name not allowed.