Quantcast

Moulded Hook

White Electric | Moulded Hook

Moulded Hook

Item Number: 548H-WE

Retail
$16.29
RRP (Inc. GST)
Colour White Electric (WE)
  • White Electric 1 PCE
  • Black 1 PCE
  • Grey 1 PCE

Datasheet

Barcode

Qty UoM EAN Colour
-
-
-

Specifications

Design

Product brand

Clipsal

Product or component type

moulded hook

Sustainable offer status

Green Premium product

Physical

REACh free of SVHC

Yes

EU RoHS Directive

Pro-active compliance (Product out of EU RoHS legal scope)

Toxic heavy metal free

Yes

Mercury free

Yes

RoHS exemption information

Yes

China RoHS Regulation

 Pro-active China RoHS declaration (out of China RoHS legal scope)

Environmental Disclosure

ENVPEP120506EN

Others

Package 1 Weight

0.012 kg
Show all specifications

Documents & downloads

hide show

Frequently Asked Questions

hide show

What batten holder will be able to be used with the 548H hook?

503M-WE
 

What is the part number for PDL single p/point with extra switch?

The part number for PDL single p/point with extra switch is 694X-WH.
Some of the Key Features are:
  • Larger rockers, matching the rockers on switch modules
  • Suits Cat 144 Flush Box and Cat 148H or 146H Mounting Bracket, Suits Cat 694M Metal cover plate
  • Removable extra switch 20 A

For more information , please visit: https://www.clipsal.com/Trade/Products/ProductDetail?catno=694X

Which shunt trip is required to work with the GFM modules?

Issue:
Which shunt trip is required to work with the GFM modules?

Product Line:
GFM modules for Legacy and Powerpact breakers

Environment:
Electrical distribution

Cause:
Shunt trips are required to complete the GFP system

Resolution:
For GFM150HD and GFM250JD modules, a 12 Vdc shunt trip module (Catalog No. S29382) is required in the circuit breaker.
This may be field installed or factory installed when the circuit breaker is ordered with an -SN suffix.

For the obsolete GFM100FA, GFM100KI, and GFM250KA modules, the shunt trip must be factory installed in the companion circuit breaker, suffix -G.

Connect a remote OPC client to ClearSCADA

Problem

Need to connect a remote OPC client to ClearSCADA and bypass DCOM.

Solution

This can be achieved by installing the Data Access component of ClearSCADA on the remote machine that hosts the OPC client. To install and configure the Data Access component follow the steps below:

1. Run the ClearSCADA Installer on the remote machine hosting the OPC client and select "Install ClearSCADA".

2. Select Custom installation and only install the Data Access component:

3. You should now see the Configure Connections program if you click on the Windows Start button. If the program cannot be located in Windows Start menu, the program can be run directly from: C:\Program Files (x86)\Schneider Electric\ClearSCADA\ClientConfig.exe (on 64-bit machines) or C:\Program Files\Schneider Electric\ClearSCADA\ClientConfig.exe (on 32-bit machines)

4. Run the Configure Connections program and create a connection to the ClearSCADA server by specifying the IP address (or server name) of the ClearSCADA server in the Node Name field of the Node A tab and select OK to apply the changes: 

5. Your OPC Client should now see ClearSCADA OPC Server among its local OPC servers as below:

The OPC service name appears in the following format based on the information defined within the Configure Connections program:

    Serck.ScxV6OPC[OPC type].[System name].[Host address or IP address]

The Data Access component uses TCP port 5481 (default) to communicate to the ClearSCADA server and the server connects back to the client on TCP ports 5500-5509.

Make sure these ports are not being blocked on either machine hosting the OPC client or the ClearSCADA server. It is possible that your application might have different ports allocated for client-server communication. 

For more information refer to the article Firewall Configuration to Allow Client - Server Comms

Firewall Configuration to Allow Server-Server Communications

DISCLAIMER

The example below is intended to demonstrate one or more features or methods and is presented as a configuration example only. Schneider Electric assumes no liability for the use or application of this example or any portion thereof.


On a redundant system (Hot-Standby, Triple Standby, with or without Permanent Standby servers) you need to configure the firewall so that it allows connections to be made between the partner servers. Before showing which ports are used in such connections, let's talk about how the "Server to Server" connections are established.

Server to Server connections

For all non-web client applications, a connection to a server is established like this:
  • The currently main server makes a connection to the partner server by creating a connection to the partner's incoming port (port 5481 by default, see below). The main server uses this connection to send information to the partner server including, for example, synchronization of data and configuration.
  • Standby servers make connections to the main server by creating a connection to the main server's incoming port (5481 by default, see below). The standby server uses this connection to send requests such as control requests and proxied actions.
  • ClearSCADA servers will check the status of their partner servers by establishing a connection to their standby servers on the partner's incoming port (5481 by default, see below).
  • ClearSCADA servers will check the status of their partner servers' hardware by performing an ICMP poll. This is designed to check for hardware failure of the partner device of intermediate network infrastructure.
Firewalls must be configured to allow ClearSCADA partners to establish connections on the incoming port (5481 by default, see below) and to perform ICMP polling.
Note As DMZ Permanent Standby Server are designed not to perform controls or proxied actions on the server, they do not establish links from the DMZ Permanent Standby Server to the main server. They also do not perform ICMP polling of the main server. As such firewalls must allow traffic on the incoming port (port 5481 by default, see below) and via ICMP from the Main to the DMZ standby, but not the other way around.

Summary of Port Usage

The table below shows which ports are used by the server, client applications and web clients (by default). The information is categorized under these headings:
  • Protocol - Indicates the protocol used by the port (TCP, UDP or ICMP)
  • Port(s) - Shows the port or ports that are used by the server or clients. The table shows the numbers for the default ports (you can configure your system to use different ports)
  • Incoming Connection - Indicates the component that receives the connection request
  • Outgoing Connection - Indicates the component that attempts to open the connection
Protocol Port(s) Incoming Connection Outgoing Connection Description
TCP 5481 by default Main, Standby and Permanent Standby Server Partner Used for sending synchronization data from main to standby, for proxying controls and other actions from standby to main and for checking the status of partner servers. This port number can be configured under the Server Configuration's Global Parameters -> Advanced
ICMP N/A Main, Standby and Permanent Standby Server Partner Used for checking the status of partner server hardware

What is a KVM Switch?



KVM stands for Keyboard Video Mouse. KVM switches provide users with one central console that connects to multiple workstation computers and/or servers.

KVM switches generally have a built-in OSD (On Screen Display) that allows the user to toggle between each workstation/server, one at a time. Simple keystrokes from the keyboard can call the OSD, and in some cases, can also toggle the user between connected workstations/servers.

APC by Schneider Electric manufactures multiple KVM switches, specifically the Analog and IP/Digital models. IP/Digital KVM models include 16 or 32 port models. A Digital IP KVM can be assigned an IP address, Subnet Mask, and Default Gateway which allows the user to access the KVM and servers through a web browser. Digital IP/CAT5 KVMs can also be tiered to increase the total number of workstations/servers monitored through one console. A cascaded configuration will include (1) Digital IP KVM with CAT5 analog KVMs tiered off of the KVM server ports located on the IP KVM. In this configuration, the user can attach to servers connected to both the Digital IP and CAT5 KVMs over the web. In this configuration, the IP KVM must be the first unit in the configuration. Otherwise, workstation/server access will not be possible through the web and will not work. Further configuration instructions can be found in the user's manual.

Servers attach to the Digital IP or CAT5 KVM via server modules (or server dongles). These modules connect direct to the server. The user then connects CAT5 cabling from the server module to the Digital IP or CAT5 KVM. Server module requirements vary based on the server type. (ie. PS/2, USB, etc).

Analog KVM switches, by design, can only be accessed locally, meaning the user has to physically be near the KVM for server access. Analog KVM switches can also be paired with one another, to increase the number of workstations/servers monitored from one console. Please reference the user's manual or product page for information on KVM cables and/or pairing cables.
 
Show More