StarServe Shallow Hook and Rail Bracket, Suit Mid Enclosure

The most common enclosure for StarServe would be a 8000MEN.
Some of its key features are:

• Removable hinged door
• Easy access
• 450mm(H) X 415mm(W) X 145mm(D)
• Mid Size
• Metal Enclosure
• Surface mount

For further information please visit https://www.clipsal.com/Trade/Products/ProductDetail?catno=8000MEN

For a flush StarServe lite enclosure, surface mount enclosure 8000LEN and the flush mounting kit 8000LENFK to suit 8000LEN are needed.
For further information please visit:
https://www.clipsal.com/Trade/Products/ProductDetail?catno=8000LENFK
https://www.clipsal.com/Trade/Products/ProductDetail?catno=8000LEN
8000LEN

Issue
How to configure modbus mastering of downstream devices on ION and Powerlogic meters.

Product Line
ION7550, ION7650, ION7550RTU, PM8000, ION7400, ION9000

Environment
ION Setup

Resolution

In ION Setup:
Step 1: Setup communication protocol for Modbus mastering.

1. In ION Setup, click on the Master Device that you want to set up.
2. Click on the View Setup Options Only tab from the tool bar.
3. Double click on Setup assistant in the right pane
4. Click on communications > Serial Settings
5. Set COM port (e.g. COM1) Comm Mode to RS485
6. Set COM port Protocol to Modbus Master
7. Set the baud rate, stop bits and parity to be the same as on your slave device(s). i.e these settings should be identical on all devices.
8. Set the Com port unit ID to a unique number
9. Click Exit 

Step 2: Enter Advanced mode, and set the MMO1 Serial Connection 1 in the Modbus Master options module Setup register to the communication port your slave device is connected to on the master device.

1. While holding on the Ctrl key, left click on your meter
2. Click on Modbus Master options module.
3. If the folder is empty, right click on the right pane > Insert module, otherwise proceed to next step.
4. Double click Modbus Master Options 1

In the Setup Register

• ​Double-click on a preferred Serial Connection (eg Serial Connection 1), and select the communications port you are using on your master device (e.g. COM1)
• Doble-click ModbusGate Connection and set it to Gateway Enabled - Serial Connection 1 (set this to which ever serial connection is selected above step )

• Double-click TCP Connection 1, and enter the IP address and modbus port number of the TCP connection(s), e.g. 10.11.12.13:502​
• Double-click ModbusGate Connection and set it to "Gateway Enabled - No Connection"

 

Step 3: Enter the Modbus map of your slave device(s) into the Modbus Master Map Module.
NOTE: Refer to FA235176 for supported formats used in the Modbus Master Map Module.

1. Click on Modbus Master Map Module.
2. Right click in the right pane > Insert Module
3. Double click on the new module that you created
4. In Setup Registers tab, double click on device Type and enter device name and click OK
5. Double click on Device Map, enter the device map following the format in the FAQ FA235162
6. Click OK to save changes

Step 4: Enter the exact device type and connection properties into the Modbus Master Device Module (i.e. Connection, Slave address, Device Name and Slave name, you may leave comms error at default).

1. Click on Modbus Master Device Module.
2. If the folder is empty, right click on the right pane > Insert module, otherwise proceed to next step.
3. Double Click on Modbus Master Device module.

In the Setup Register:

1. Select the connection type (Serial or TCP).
2. Enter the unit ID of the slave device. Click OK.
3. Enter the device type for the slave device. Click OK. (Same name entered in Modbus Master Map Module)
4. Under the Slave Name, give a name to the slave device. Click OK.
5. Click OK to save changes.

Refer to the ION Reference manual on more details on meter modules and their functions: ION Reference Manual

NOTE: Not all firmware revisions are capable of TCP modbus mastering. The following firmware versions and higher are capable of modbus mastering:

Meter	Firmware Version
ION7550	v 350
ION7650	v 350
PM8000	intitial firmware release (v 1.0)
ION9000	initial firmware release

When commissioning Lexium 32 servo drives there are two parameters that can be adjusted which are related to the "Brake function"

BRK_AddT_Release and BRK_AddT_Apply.

Below is a description of each of these parameters.


BRK_AddT_Release effects the delay time for the drive status to change to “operation enabled”
 
When drive enable is requested the status bit of the drive will not switch to status 6 (operation enable) until the  BRK_AddT_Release time has elapsed.
Note that the motor torque will be applied immediately when the drive enable is requested and the drive with immediately transition to status 5 (power enabled) but the drive will not allow motion to take place until the drive transitions to status 6 (Operation enable).
Therefore the BRK_AddT_Release parameter effects the delay time between status 5 (power enabled) and status 6 (Operation enabled) of the drive.
This delay prevents motion from taking place until the brake is released and also insures that the motor has holding torque and control of the load before the brake is released.
 
 
BRK_AddT_apply effects the delay time for when the “motor torque” is switched off
 
When disable is requested of the drive to switch the drive off from the enabled state, the BRK_AddT_apply time parameter effects the delay time for when motor torque is removed.
Motor torque, current from the drive, will remain applied after the drive disable and will remain applied until the BRK_AddT_apply  time has elapsed.
It should be noted that when the drive is disabled the drive status bit will immediately transition to status 4 (ready to switch on) but the power amplifier will remain active thereby maintaining current and thereby maintaining holding torque on the motor until the BRK_AddT_apply  time has elapsed
This BRK_AddTapply delay prevents a vertical load from falling by maintaining holding torque on the motor until the brake is known to be applied.
 
 
More details…..
 
All motors that have a brake are subject to a mechanical time in which the physical action of the brake release and brake apply is required (mechanical delay).
 
When using a Schneider Electric BSH or BMH motor this mechanical delay time is known and included in the motor’s electronic data-plate which is read via the encoder cable over the data communication channel.
This mechanical delay is therefore known by the firmware and the firmware controls drive status transitions automatically.
The parameters BRK_AddT_Release and BRK_AddT_apply are available to allow users to add additional time, if preferred, to the delay of “operation enabled” or “motor torque off”
 
In addition, the two parameters BRK_AddT_Release and BRK_AddT_ apply which are for BSH or BMH motors and are limited in their respective delay times.
BRK_AddT_Release has a maximum delay of 400ms and BRK_AddT_apply has a maximum delay time of 1000ms
 
 
 
When dealing with 3^rd party motors there are two additional parameters which behave exactly as BRK_AddT_Release and BRK_AddT_apply, these two parameters are M_BRK_T_release and M_BRK_T_apply.
These two additional parameters are found in the 3rd party motor configuration section and can be accessed with SoMove commissioning tool.
 
Because the mechanical delay time for brake apply and brake release of other motor manufacturers is an unknown variable from manufacturer to manufacturer, these parameters are provided in our 3^rd party motor setup parameters.
Note that the maximum delay time for these parameters are much higher than the brake parameters for Schneider Electric motors, allowing for a greater range of compatibility of Lexium 32 with other brands of motors.
 
 
Also note that there is “overlap” between the parameters BRK_AddT_Release , BRK_AddT_apply found in the basic parameter settings and M_BRK_T_release , M_BRK_T_apply found in the 3^rd party motor parameter settings.
For example if a value of 400ms set in the parameter BRK_AddT_Release and 5000ms set in the parameter M_BRK_T_release, then the total time will be 5400ms.
This is also true for the apply parameters.

Therefore when commissioning Lexium 32 for 3rd party motors, you should leave the basic brake parameters set at factory default and focus only on the brake parameters in the 3rd party motor configuration section.


rev 9-16-2019