COBRA BC 0101 G — instruction manual busch monitoring system 20
Technical Reference Summary
Covered Models & Document Scope
Instruction manual for Busch Monitoring System 2.0 (BMS 2.0), a SCADA-based central monitoring software for Busch Cobra Series dry screw vacuum pumps (also Busch PLC, NX Controller, RCS PLC, Busch Monitor for BC 0101 F, Torri for BD Series). Covers software installation (zenon platform), update/backup, operation (Admin, Main, Detail, Trend, Alarm/Event pages) and maintenance/security. Operation versions: Light (80 pump connections), Medium (400), Full (1000). Document ID 08702731454_Busch Monitoring System 2.0_IM_en, rev. 1.0, dated 05/05/2020, Busch Manufacturing Korea.
Section-by-Section Technical Breakdown
BMS 2.0 is a SCADA-based application for monitoring up to 1000 Busch Cobra vacuum pumps over an Ethernet (Modbus TCP) network from a single server. It is software only; the customer provides and installs the hardware (server, switches, Cat 6 cabling). A facility audit with Busch Semiconductor Networking specialists is the first design step.
- Monitors about 1000 pumps connected to one main server via Modbus TCP.
- Stores every-second data for up to 1000 pumps for up to 6 months (storage period depends on PC capacity).
- Supports ~10 concurrent users (optional, via WEB), user authentication/authorization, Excel reporting, parameter drift detector, e-mail/SMS alerts (SMS needs customer's own server).
- Recommended H/W: Windows 7, Intel Core i5 or better, >1 TB HDD, >16 GB RAM, 1680x1050 VGA, 100 Mbit/s network, .Net Framework 32/64-bit.
- Basic components: Cobra pump with Modbus TCP, central server PC, BMS 2.0 software, designated switch ports, RJ45 Cat 6 cabling, license key dongle.
BMS 2.0 runs on the zenon platform (zenon Supervisor Edition). Installation requires Windows administrator rights and an OS with no pending restart; the cdprotdrv.sys network protocol driver requires an OS restart after installation. Serial number and activation number are provided by KRM; the project database folder cannot be changed after installation.
- Select product: Editor (Editor + Runtime), Runtime only, or Web Server; edition must be zenon Supervisor Edition.
- Wibu-Key/CodeMeter dongle software is installed automatically; only Busch-managed licenses work correctly.
- Standard Windows user rights suffice for ongoing operation; UAC can be at highest level.
- Project database target folder must have sufficient memory space and write authorization for all users; it is fixed after install.
- Optional demo project provides usage scenario examples.
After platform installation, the BMS 2.0 folder (RT) must be set up via the Zenon Startup Tool (Item -> Properties). Backups are made by compressing the whole RT folder; updates are delivered as RT.zip and applied by overwriting the RT folder. BMS 2.0 only operates with the Busch-provided license key.
- Recommended to set the RT path on the drive where the OS is installed.
- If the supplied hardware lacks an RT folder, unzip the RT.zip provided by Busch.
- The compressed RT backup is an executable file; source code cannot be analyzed.
Before starting BMS 2.0, firmware installation and license must be enabled via the Zenon Startup Tool; firmware versions lower than the editor version will not operate correctly. Network design mirrors an office LAN with group switches per pump cluster and a main switch connected to the server by a single RJ45 cable up to 90 m. Serial devices are integrated via Modbus TCP converters (device-server type recommended).
- Default user levels: Guest (view pump status only), Operator and Administrator (pump configuration); BMS settings Administrator only; up to 10 users, login history recorded in event history; more user rights require contacting Busch before purchase.
- Cabling: RJ45, category 6 or at least 5E; multiple-server designs require consultation with Busch.
- More monitored pumps require higher H/W specifications and add load to the existing network.
- Top menu: LOGIN, LOGOUT, EXIT, history/alarm buttons, and admin settings page (administrator authority required).
The Admin page (administrator authority required) selects the operation version, configures pre-warning and message control, printer, and shows license, database folder, runtime version and server status. Operation versions limit pump connections: Light 80, Medium 400, Full 1000.
- Pre-warning is disabled by default; it is not a pump interlock, only a user-set early warning; Message control activation requires developer consultation (account and recipient settings; else nothing occurs).
- License not purchased through Busch: BMS will not start normally and no technical support is available.
- Software developed from firmware V7.20; projects created in a higher firmware version may not run on lower versions.
- Server status page shows PC memory and HDD capacity; hardware upgrade recommended if memory is poor.
- Printer selection and database/export folder paths are shown/configured here.
The main page shows totals of configured/connected/running/alarm/warning pumps, network settings, version, user authority and communication lamp status per pump. Pump configuration requires login and entry of controller type, Tool ID and pump IP address. 11 screen-switch buttons navigate 25 pages of 40 pumps each.
- Controller options: Busch PLC, NX Controller, RCS PLC (currently used); Busch Monitor (only BC 0101 F pump); Torri (only BD Series).
- Connection activation is disabled if controller, Tool ID or IP address is missing.
- Orange lamp = configured but no communication (check configuration/cabling); green = normal communication.
- Duplicate Tool IDs are allowed; searching loads the lowest-numbered archive; unmatched IDs return 'Do not found TOOL ID'.
- Clicking a Tool ID jumps directly to archived data for that pump.
The Detail screen shows pump serial number, real-time data with trend graph (default 30 min), pre-warning settings, work time and operation mode, and pump/module status. Serial info shows 'Do not managed' when absent; only pump models with up to four DP are managed. Screens can be captured/saved as PDF to the Export folder.
- Operation modes: LOCAL (handy pad), REMOTE (tool-interface connector by DIO), NETWORK (customer network data).
- Load lock mode: OFF (continuous full speed), AUTO (variable speed per internal controller reference), EXTERN/NETWORK (driven by customer signal).
- Pre-warning does not support Frequency and Over pressure; requires Admin-page activation; reference level and delay time are user-defined per pump propensity.
- Old/overhauled pump data differs from new pumps, so pre-warning references must be set from experience; actual pump inspection is still required.
The Trend screen loads past pump data (from current point of view back one day, including real-time data) for trend analysis and failure-mode checks. It offers zoom, cursor with movable Y-axis, graph settings, filter functions, and print/export. Real-time display must be switched off before zoom is usable.
- Records displayed sequentially numbered 1 to 1000 regardless of Tool ID.
- Graph settings revert to defaults when leaving the screen.
- Up to 250 filter settings can be saved; settings can be exported/imported externally.
- Print output is stored in the Export folder (path shown on Admin page).
The Alarm page shows only alarm history; the Event page stores all history. Alarm records include status, time received, time acknowledged, alarm text and tool ID, with totals of generated and acknowledged alarms. Event records log time, event name, program variable, value, user full name, computer name and optional comment. Both pages support filter functions (up to 250 saved, import/export) and printing to the Export folder.
- Alarm acknowledgment time records the user's check within the monitoring program.
- Print out buttons store alarm/event tables in the Export folder.
Defines a secure decommissioning process for BMS 2.0 computers (backup, restore verification, physical destruction of data media) and IT-security recommendations for installation and operation. Security updates should be applied only during agreed maintenance intervals and tested beforehand; antivirus real-time protection may require exceptions for Runtime data.
- Decommissioning: examine data, back up, verify restorability, physically destroy data media, render other backups unusable.
- Disable Autorun, disable automatic OS/app updates, deactivate non-essential services, use strong passwords, disable automatic login, block network access for local admin/guest accounts, protect shared printers for defined user groups.
- Protect physical access: locked server cabinets with security locks, locked equipment cabinets, protected cable connections, camera systems with motion detection for unmanned areas.
- Keep spares of critical components and plan replacement strategy for discontinued products.
- On false-positive malware detection of a BMS executable, check the digital signature first; contact local Busch Service support if in doubt.
- Annual maintenance contracts available from Busch Corporation for continuous technical support.
Key Integration, Operating & Safety Requirements
| Specification / Condition | Engineering Implication | Applies To |
|---|---|---|
| BMS 2.0 monitors up to 1000 Busch Cobra pumps on one main server; operation versions cap connections at Light = 80, Medium = 400, Full = 1000. p.6 ↗ | Select the operation version (Admin page) and hardware sizing to match the planned pump count. | BMS 2.0 all versions |
| Communication with pumps is Modbus TCP over Ethernet; serial devices must be converted using a Modbus TCP converter (device-server type recommended). p.6 ↗ | Legacy serial pumps need a converter integrated into the network design; discuss with the customer's IT manager. | whole system, esp. non-Ethernet pumps |
| Recommended server H/W: Windows 7, CPU > Intel Core i5, HDD > 1 TB, RAM > 16 GB, VGA 1680x1050, network 100 Mbit/s, .Net Framework 32/64-bit. p.7 ↗ | Minimum PC specification for installation; more monitored pumps require higher H/W specs. | BMS 2.0 server PC |
| Cabling must be RJ45 category 6 (at least category 5E per sec. 3.1.2); single cable from main switch to server up to 90 m. p.6 ↗ | Design network with group switches per pump cluster; keep server runs within 90 m. | whole network installation |
| Data storage: every-second data for up to 1000 pumps retained up to 6 months (longer depends on PC capacity). p.6 ↗ | Size server storage accordingly; trending beyond 6 months requires larger HDD. | BMS 2.0 server |
| Up to ~10 concurrent users supported, optionally via WEB; user permissions up to 10 users (Guest/Operator/Administrator by default). p.6 ↗ | More user rights or concurrent users must be arranged with Busch before purchase. | BMS 2.0 |
| BMS 2.0 runs only with a license key (dongle) supplied/managed by Busch; licenses not purchased through Busch prevent normal startup and void technical support. p.8 ↗ | Never substitute third-party zenon licenses; keep the dongle secure. | BMS 2.0 all installations |
| Installation requires Windows administrator rights, no pending OS restart, and an OS restart after installation (cdprotdrv.sys driver); ongoing operation uses standard user rights with UAC allowed at highest level. p.8 ↗ | Schedule installation with IT to allow admin rights and restarts. | zenon platform installation |
| Only zenon Supervisor Edition is used for BMS 2.0; serial number and activation number come from KRM; the project database folder is fixed after installation and needs write authorization for all users. p.10 ↗ | Choose the database path and capacity carefully at install time - it cannot be changed later. | zenon platform / BMS 2.0 |
| Updates are delivered as RT.zip and applied by overwriting the RT folder; backup is done by compressing the entire RT folder; RT path should be on the OS drive. p.14 ↗ | Establish a standard backup/update procedure around the RT folder. | BMS 2.0 software |
| Firmware version must be >= the editor version; BMS developed from V7.20; projects made in a higher firmware version may not function in lower versions. p.16 ↗ | Keep runtime firmware at or above editor version when updating. | BMS 2.0 / zenon runtime |
| Pump configuration requires entry of controller type, Tool ID and target IP address; connection activation is blocked if any of the three is missing. Supported controllers: Busch PLC, NX Controller, RCS PLC; Busch Monitor (BC 0101 F only); Torri (BD Series only). p.27 ↗ | Prepare Tool IDs and static IP addresses per pump before commissioning; use the correct controller type per pump model. | pump connection setup |
| Main page navigation supports 40 pumps per page, 25 pages total (1000 pumps); duplicate Tool IDs allowed, search loads the lowest-numbered archive. p.31 ↗ | Use unique Tool IDs to avoid ambiguity when calling up archived data. | BMS 2.0 main/trend pages |
| Pre-warning is disabled by default, is not an interlock, must be enabled on the Admin page, requires developer consultation for message control, and does not support Frequency and Over pressure parameters. p.22 ↗ | Do not treat pre-warnings as pump protection; set reference levels and delay times from user experience per pump. | BMS 2.0 detail screen |
| Detail-screen trend graph defaults to 30 min with Y-scale auto-set to max; settings revert to defaults when leaving the screen. p.33 ↗ | Re-enter graph settings per session or use saved filters (up to 250, import/exportable). | BMS 2.0 detail/trend screens |
| Trend screen loads data from the current point of view back one day, including real-time data; real-time display must be off to use zoom. p.36 ↗ | For longer history use filter/date settings; pause real-time mode before zoom analysis. | BMS 2.0 trend screen |
| Pump operation modes: LOCAL (handy pad), REMOTE (tool interface connector via DIO), NETWORK (customer network); load lock mode OFF/AUTO/EXTERN-NETWORK (full speed, internal variable-speed reference, customer signal). p.34 ↗ | Verify displayed mode matches intended control architecture during commissioning. | Cobra pumps monitored via detail screen |
| Serial number display: only pump models with up to four DP are managed; missing info shows 'Do not managed'. p.33 ↗ | Older controllers may not provide serial data to BMS. | detail screen serial display |
| Alarm and Event pages each save up to 250 filter settings (import/export possible); event records log variable name, value, user full name and computer name. p.39 ↗ | Build reusable filter sets for recurring diagnostics and traceability audits. | BMS 2.0 alarm/event pages |
| Decommissioning of BMS 2.0 computers requires backup, restore verification, and physical destruction of data media; OS updates and antivirus real-time protection must be tested/excepted for Runtime processes and applied only during agreed maintenance intervals. p.41 ↗ | Coordinate a formal IT security/decommissioning process with the IT department before plant integration. | all BMS 2.0 installations |