IFM VSE002 MCM Vibration Monitoring

1 Adjustment of IFM electric module VSE002

1.1 Necessary parts for IFM vibration measurement system according to Stüli 318600

Mat. 555096	IFM	VSE002	Auswerteelektronik
Mat. 555097	IFM	VSA001	Schwingungssensor
Mat. 555098	IFM	E12008	Kabel (30m)
Mat. 555803	IFM	E30115	konische Unterlegsscheibe

• Auswerteelektronik
  Auswerteelektronik
• Schwingungssensor
  Schwingungssensor
• Kabel
  Kabel
• Unterlegscheibe
  Unterlegscheibe

1.1.1 Software used to set the IP-adress of the electric module VSE002 (line specific):

IFM software for firmwareupdate "VSExxxUpdateTool.exe"

1.1.2 Software for the configuration of the electric module VSE002 with the vibration sensors VSA001 (gear box specific)

IFM software efector octavis VES003 v3.0.3 "octavis_VES003.exe"

Please only use the latest version v3.0.3 from now on.

1.2 IFM Device Settings with efector ocatvis V3.03. (before Imc_23.09)

1.2.1 Adjust network adapter

Adjust the settings of the network adapter as shown below:

1.2.2 Software for firmwareupdate "VSExxxUpdateTool.exe"

Type in the default IP-address 192.168.0.1:

Optional:

Choose the "Have no IP"-button if the IP-address of the electric module (VSE002) is unknown:

Choose the "Conntect"-button, the connection should now be established (Status: connected)

Go to "Change Settings":

• Type in an optional "Hostname", e.g. VibMonExt, VibMonCox001, VibMonPurCorTop
• Set gateway to 10.XX.YY.190 for IPC_3.9
• Set gateway to 10.XX.YY.71 for IPC_4.0
• Or check the newest networklist EE

https://departments.brueckner.com/bms/ee/SitePages/Homepage.aspx

Press "Start Update", the connection will be lost:

Now set back your local IP-adress of your network adapter.

1.2.3 efector octavis VES003 v3.0.3 "octavis_VES003.exe"

1.2.3.1 Standard configuration

Choose menu VSE => New => VSE

Choose "static IP-adress":

Put in the line-specific IP-adress 10.XX.YY.95 for Ext. and 10.XX.YY.96 for Pur or bether check config file from project.

Template:Image

Choose "connect at once" to establish the connection:

Connection is now ready!

Open the predefined configuration file *.o2pr .

We are using the file ifm_VSE002_configfile_v3.0.3_rev01_HCH.o2pr for all vibration monitoring systems (extrusion, pullroll etc.). We do not use gearbox-specific files anymore.

This file must be committed to your SVN repository under _engineering\public\sensors\VibMon or...ifm_VibMon (depending on your IMC version).

Template:Image

Write the predefined configuration file *.o2pr from above down to the electric module (VSE002) by clicking the button with the red arrow:

1.2.3.2 Sensor Names

To better understand what we display in WinCC a file containing better sensor names has been provided.

Release <= Imc_22.02

• For the extrusion we have the standard file Sensornames_Mex_Standard.o2st. If it is not already in your SVN-Repository BmsProjectManager\Kom\_engineering\public\sensors\ifm_VibMon\Sensornames_Mex_Standard.o2st, ask EECIBN to send it to you.
• For the other machine parts (e.g. pullroll) there is no standard file for the sensor names, yet. Please ask EECIBN to send it to you.
  

Release > Imc_22.02 For all machine parts we have files for the sensor names already in your SVN-Repository BmsProjectManager\Kom\_engineering\public\sensors\ifm_VibMon.

• For the extrusion we have the standard file Sensornames_Ext_Standard.o2st.
• For the MDO we have the standard files Sensornames_MdoDrw_Standard.o2st, Sensornames_MdoDrw_Standard.o2st and Sensornames_MdoDrw_Standard.o2st.
• For the TDO we have the standard file Sensornames_Tdo_Standard.o2st.
• For the Pull Roll we have the standard files Sensornames_PurCor_Standard.o2st, Sensornames_PurNip_Standard.o2st and Sensornames_PurRol_Standard.o2st.
• For the Wunder we have the standard file Sensornames_Win_Standard.o2st.

To load the sensor names to the ifm module establish a connection with octavis.

You can search for VSE devices, e.g. doubleclick on the VSE for Mainextrusion.

Open the appropriate file with sensor names e.g. Sensornames_Ext_Standard.o2st and send the configuration to the device with the red arrow button.

You will get a message that settings have been transferred.

I recommend to reboot the ifm device now with the reboot button.

Reestablish the connection, doubleclick on parameters and check if the names have been transferred properly.

After some time, also WinCC does show the proper names now. Check wether the sensor names and the wireing of them is correct. If not correct the sensor names file and load it again, or change the wireing and plans.

Template:Image

1.3 IFM Device Settings with VES004 (starting with Imc_23.09)

The software efector octavis V3.03 and VSExxx_FirmwareUpdate tool will be replaced with one application named VES004 (Version V2.33.00) for all commissions >= Imc_23.09.

All possible configurations are stored in an ibak-file.

This file is committed in _engineering\public\sensors\ifm_VibMon\.

Open the Standard-ibak file with Project > Restore and select the committed file:

Rename the project when opening to your commission:

You can see that this file contains all possible configurations for the different applications.

We need to know which application we want to use (MexDrv, PurCorBot...?) and the IP address of the ifm electronic device (check the eDrawings or the config/config-file).

In the following example we want to configure an IFM device for MexDrv with IP address 10.21.3.88:

Open Settings under your application and scan for reachable devices:

Found devices will have its default IP address. Select the device.

On the Configuration tab set:

Hostname: like your application e.g. MexDrv or Cox001Drv or PurCorBot

TCP/IP addres: according to config/config e.g. 10.21.3.88

Subnet mask: 255.255.254.0

Gateway: as your line network gateway e.g. 10.21.2.71

Use the "write" Button to transfer the TCP/IP settings to the device.

You will get a message box which you can acknowledge.

Now you can try to ping the device with the newly set IP address.

Connect to the device by rightclicking on the application name > Connect

Transfer the configuration by rightclicking on the application name > Write to device

Now disconnect from the device and save the project by selecting Project > Backup.

Template:Image

Commit the ibak-File under the name of your commission (e.g. Ptk.ibak) in the same path where you found the standard-ibak.

Now continue by setting the WinCC parameters.

1.4 Setting WinCC parameters

After finish with "efector octavis" software the Link sould be working in PVSS. Look at the PVSS Driver (progs-file).

If the Link is not working, restart this driver:

(if the driver does not exist, add it at the progs file at the server)

PVSS00d-bms      | always |      30 |       30 |       10 |-num 95

• Do this for each Sensor (you must have as much tabs as installed sensors, if not check connection)
• disconnect each sensor separately to check if it is the correct one (Stop link and start every time again and after this all the tabs are updated)

If everything is fine, you should get some data information in the panel (also when the drive stands still)

Open ( e.g.) VibMonExtMexDrv parameter panel (right click on the marked symbol --> Parameter)

Select register "Service", open "Parameter File" and click "Load Selected Parameter File ":

Doubleclick or select and then click "Load" appropriate parameter set ( e.g. Ext).

What is happening here?

default parameter files matching with the selected application (e.g. Ext, Mdo) are being extracted from the data\parameters\MCM_Parameter.zip file and are stored in data\parameters\defaults with the appropriate name.

Load the loaded parameter set.

What is happening here?

The previosuly extracted parameters are loaded to the WinCC obejcts and settings made before are overwritten.

Extrusion

Enter the "Speed Source" : For main Extrusion e.g. KOMXXXX:ExtMex.MelDrv001.SpdAct, where KOMXXXX ist commision name and XXXX is comission number, e.g. Isf2054.

• In Speed Factor enter the gearbox ratio according to the gearbox used on your line (e.g. 4.440).
  • You can find the gearbox ratio on the gearbox nameplate, in the LinDrvCfg or in the drive schematics (Antriebsschema).
  • Background information: We read the datapoint ExtMex.DrvMel001.SpdAct. This value represents the actual speed of the screw. But we are interested in the actual speed of the motor. Speed motor = Speed screw * gearbox ratio.

Extrusion Warning and Alarm Settings

The following picture shows the warning and alarm settings for Extrusion applications.

Here is the relation between the values and the wincc datapoints:

Pull Roll

• Speed Source: enter the datapoint for the correct speed signal.

Sensors Roll Drive Side, Roll Operator Side get the Speed from the LineDrive of this roll. e.g. KomXXXXStrPur.Drv007.SpdAct.

Sensors Nip Roll Drive Side, Nip Roll Operator Side get the signal from the separate rotary encoder mounted on the Nip Roll, e.g. KomXXXX:StrPur.NipCorTop.RolSpd.Act.

• In Roll Diameter enter the diameter of the roll where the sensor ist mounted on your line (e.g. 708mm for the Corona Roll or 630mm for the Nip Roll).
  • You can find the roll diameter in the drive schematics (Antriebsschema) or in LinDrvCfg.vbs.
  • Background information: We read the datapoint StrPur.Drv004.SpdAct. This value represents the line speed at this roll. But we are interested in the actual speed of the motor. Speed motor = line speed / ( ( diameter / 1000 ) * pi ) * factor.

PullRoll Warning and Alarm Settings

MDO

MDO Warning and Alarm Settings

1.5 Extrusion Physical Sensor Position at GearBox and Drive

Ext_VibMon_Sensor_positions

1.6 MDO Physical Sensor Position

MDO_VibMon_Sensor_positions

1.7 Pull Roll Physical Sensor Position

Pur_VibMon_Sensor_positions

2 Data Storage

The collected datas are stored for every month under

OLD:

\\KOM\_mms\PrjData\MCM

NEW:

\\KOM\data\MCM

3 Trouble Shooting

No communication to ifm devices in WinCC .

Check the if the unique identifier numbers for the separate communication tasks match in config file and in MCM.ctl:

Changes in config/config require a WinCC restart; changes in MCM.ctl require a ctrl1 restart.

If you are sure you did all the configurations and the sensor names are inside but you still dont see it in the WinCC, you can write the name manually.

File:Sensor not working.PNG

click into the red field and type in the correct sensor name.

File:Sensor works.PNG

Dont forget tp press Enter. Now the sensor should work.