pekerjaan penggantian cpu card CP-333D ke CP-345 terakhir


Alhamdulillah, akhirnya pekerjaan penggantian cpu card CP-333D ke CP-345 di salah satu plant kami telah dilakukan beberapa hari yang lalu oleh rekan2 maint.
kebetulan karena saya sedang field break jadi tidak ikut hadir dalam eksekusi pekerjaan ini.

Pekerjaan ini lumayan beresiko. Tapi alhamdulillah rekan2 berani mengeksekusi tanpa memanggil engineer Yokogawa.
Tapi kalaupun ada apa-apa Engineer Yokogawanya sudah siap dihubungi kalau dibutuhkan.

Pekerjaan ini sebetulnya sudah direncanakan sejak lama. tetapi karena butuh plant shutdown atau plant override makanya baru bisa sekarang dilakukan.
Sebelumnya pernah dilakukan tapi kami masih panggil Engineer Yokogawa untuk jaga-jaga. Berikut link artikel pekerjaan sebelumnya

Beberapa hal yang perlu diperhatikan adalah semua controller menjadi MANUAL. Hal ini sudah diantisipasi.
Trus menyiapkan spare Module Power Supply. Pekerjaan sebelum pernah mengalami bbrp power supply rusak. Tidak bisa ON lagi ketika dihidupkan. Yang ini alhamdulillah tidak ada module power supply yang rusak.

Nah ternyata masih ada yang terlewat seperti perhitungan Flow AGA-3 yang menggunakan program SEBOL.
Ada laporan dari operator dan rekan field maint. dan bisa segera diperbaiki.
Untungnya ini minor saja dan saya pernah mengalami ketika mematikan power DCS (berikut linknya).

Dengan digantikan module CPU ini maka akhirnya semua plant sudah siap untuk migrasi ke Centum VP.
Tinggal cari dana upgradenya saja. Lumayan mahal euy. Lihat2 harga minyak dulu….

Semoga info ini bermanfaat bagi yang membutuhkan.

Ditulis dalam DCS. Leave a Comment »

Apa itu OPC



iseng2 baca2 seputar OPC, sekalian saya copy kan ke sini saja.

What is OPC?

OPC is the interoperability standard for the secure and reliable exchange of data in the industrial automation space and in other industries. It is platform independent and ensures the seamless flow of information among devices from multiple vendors. The OPC Foundation is responsible for the development and maintenance of this standard.

The OPC standard is a series of specifications developed by industry vendors, end-users and software developers. These specifications define the interface between Clients and Servers, as well as Servers and Servers, including access to real-time data, monitoring of alarms and events, access to historical data and other applications.

When the standard was first released in 1996, its purpose was to abstract PLC specific protocols (such as Modbus, Profibus, etc.) into a standardized interface allowing HMI/SCADA systems to interface with a “middle-man” who would convert generic-OPC read/write requests into device-specific requests and vice-versa. As a result, an entire cottage industry of products emerged allowing end-users to implement systems using best-of-breed products all seamlessly interacting via OPC.

Initially, the OPC standard was restricted to the Windows operating system. As such, the acronym OPC was borne from OLE (object linking and embedding) for Process Control. These specifications, which are now known as OPC Classic, have enjoyed widespread adoption across multiple industries, including manufacturing, building automation, oil and gas, renewable energy and utilities, among others.

With the introduction of service-oriented architectures in manufacturing systems came new challenges in security and data modeling. The OPC Foundation developed the OPC UA specifications to address these needs and at the same time provided a feature-rich technology open-platform architecture that was future-proof, scalable and extensible.

These are just some of the reasons why so many members and other technology organizations (collaborations) are turning to OPC UA for their interoperability platform.




The OPC Classic specifications are based on Microsoft Windows technology using the COM/DCOM (Distributed Component Object Model) for the exchange of data between software components. The specifications provide separate definitions for accessing process data, alarms and historical data.

OPC Data Access (OPC DA)
The OPC DA specification defines the exchange of data including values, time and quality information.

OPC Alarms & Events (OPC AE)
The OPC A&E specification defines the exchange of alarm and event type message information, as well as variable states and state management.

OPC Historical Data Access (OPC HDA)
The OPC HDA specification defines query methods and analytics that may be applied to historical, time-stamped data.

The OPC Classic specifications have served the OPC community well. However, as technology evolved, so did the need for OPC specifications.

In 2008, the OPC Foundation released OPC Unified Architecture (OPC UA), a platform independent service-oriented architecture that integrates all the functionality of the existing OPC Classic specifications, and is backward compatible with OPC Classic. Several factors influenced the decision to create OPC UA:

  • Microsoft has de-emphasized COM (Component Object Model) and DCOM (Distributed COM) in favor of cross-platform SOA (Service-Oriented Architecture).
  • OPC vendors want a single set of services to expose the OPC data models, such as Data Access, Alarms & Events, Historical Data Access, etc.
  • To stay competitive, OPC vendors need to implement OPC on non-Microsoft systems, including embedded devices.
  • Other collaborating organizations need a reliable, efficient way to transport high-level structured data.
  • Users require the ability to access OPC servers through firewalls in a secure manner.


Unified Architecture

The OPC Unified Architecture (UA), released in 2008, is a platform independent service-oriented architecture that integrates all the functionality of the individual OPC Classic specifications into one extensible framework.

This multi-layered approach accomplishes the original design specification goals of:

  • Functional equivalence: all COM OPC Classic specifications are mapped to UA
  • Platform independence: from an embedded micro-controller to cloud-based infrastructure
  • Secure: encryption, authentication, and auditing
  • Extensible: ability to add new features without affecting existing applications
  • Comprehensive information modeling: for defining complex information

Functional Equivalence

Building on the success of OPC Classic, OPC UA was designed to enhance and surpass the capabilities of the OPC Classic specifications. OPC UA is functionally equivalent to OPC Classic, yet capable of much more:

  • Discovery: find the availability of OPC Servers on local PCs and/or networks
  • Address space: all data is represented hierarchically (e.g. files and folders) allowing for simple and complex structures to be discovered and utilized by OPC Clients
  • On-demand: read and write data/information based on access-permissions
  • Subscriptions: monitor data/information and report-by-exception when values change based on a client’s criteria
  • Events: notify important information based on client’s criteria
  • Methods: clients can execute programs, etc. based on methods defined on the server

Integration between OPC UA products and OPC Classic products is easily accomplished with COM/Proxy wrappers that are available in the download section.

Platform Independence

Given the wide array of available hardware platforms and operating systems, platform independence is essential. OPC UA functions on any of the following and more:

  • Hardware platforms: traditional PC hardware, cloud-based servers, PLCs, micro-controllers (ARM etc.)
  • Operating Systems: Microsoft Windows, Apple OSX, Android, or any distribution of Linux, etc.

OPC UA provides the necessary infrastructure for interoperability across the enterprise, from machine-to-machine, machine-to-enterprise and everything in-between.


One of the most important considerations in choosing a technology is security. OPC UA is firewall-friendly while addressing security concerns by providing a suite of controls:

  • Transport: numerous protocols are defined providing options such as the ultra-fast OPC-binary transport or the more universally compatible SOAP-HTTPS, for example
  • Session Encryption: messages are transmitted securely at 128 or 256 bit encryption levels
  • Message Signing: messages are received exactly as they were sent
  • Sequenced Packets: exposure to message replay attacks is eliminated with sequencing
  • Authentication: each UA client and server is identified through OpenSSL certificates providing control over which applications and systems are permitted to connect with each other
  • User Control: applications can require users to authenticate (login credentials, certificate, etc.) and can further restrict and enhance their capabilities with access rights and address-space “views”
  • Auditing: activities by user and/or system are logged providing an access audit trail


The multi-layered architecture of OPC UA provides a “future proof” framework. Innovative technologies and methodologies such as new transport protocols, security algorithms, encoding standards, or application-services can be incorporated into OPC UA while maintaining backwards compatibility for existing products. UA products built today will work with the products of tomorrow.

Information Modeling

The OPC UA information modeling framework turns data into information. With complete object-oriented capabilities, even the most complex multi-level structures can be modeled and extended. Data-types and structures are defined in profiles. For example, the existing OPC Classic specifications were modeled into UA profiles which can also be extended by other organizations


untuk penjelasan lainnya silahkan browsing ke websitenya.



Ditulis dalam PLC-HMI. Tag: . Leave a Comment »

Kick of Meeting Project Upgrade Shutdown System 2016-2017



Alhamdulillah akhirnya setelah bbrp tahun rencana upgrade shutdown system (karena obsolete) di beberapa plant kami akhirnya mulai terealisasi.

Dari awalnya 4 buah panel control di 4 lokasi yang kami proposed akhirnya disetujui 2 buah panel dulu.
Ini akibat terkena dampak efisiensi budget juga karena harga minyak yang turun drastis.

Melewati diskusi dan meeting yang cukup alot dari sisi technical dan budgeting akhirnya terpilihlah safety PLC (SIL Certified) sebagai penggantinya.

Setelah tender dari bbrp vendor/system integrator akhirnya keluar pemenangnya Jetec dengan membawa HIMax produk HIMA.
Minggu kemarin sudah dimulai kick of meeting di kantor Jetec di Wisma Mampang.

Semoga project ini lancar dan secepatnya bisa terpasang.

Bagi kami yang bekerja di Dept. Maintenance, siap-siap belajar barang baru.🙂
Dan setelah nanti dipasang, siap-siap stock spare part baru.
Efek dari open tender, ndak bisa pilih-pilih merek. Akhirnya jadi banyak merek.😉

Berikut website resmi dari HIMax.


Cara restore image Flash Disk TT4000 versi 5


Sekedar sharing aktivitas kemarin …

Kemarin kami mencoba restore image dari USB Flash Disk TT4000 yang diberikan PTI/Solar.

Biasanya di versi sebelumnya yaitu TT4000 versi 3 atau 4 kami masih bisa install sendiri TT4000 tanpa melakukan restore image ini. Untuk pindah ke Configuration Mode menggunakan TTSysPrep hasil instalasi TT4000.

Di versi 5 ini TTSysPrep tidak ada lagi dan yang dipakai adalah TTDeployment Tool (versi 4 sudah ada tapi untuk masuk Configuration Mode pakai TTSysPrep).

Nah kalau TTDeployment Tool ini dijalankan dari backup flash disk, dia hanya mengenai HMI hasil image untuk project ini saja.

Akhirnya dicoba lah restore image dari USB Flash Disk TT4000 C7050 ini.

Untuk petunjuk instalasinya cukup jelas. Bisa dibaca dari file Readme.txt di flash disk tsb.
Berikut saya tambahkan keterangan dan photo.


1.Shutdown the computer if it is running already. –> pastikan computer yang dipakai adalah spare dan file2nya tidak ada yang dibutuhkan lagi. Karena semua file akan hilang diganti dengan hasil restore image.

2.Insert the configured USB drive into the Display Computer.

3.Restart the computer.

4.When the computer restarts, hit or hold the ‘F7’ key to enter the Boot Menu. This will popup a list of bootable devices. Verify that the USB Drive is listed as one of them. For some drives the brand of USB will be displayed but for others you may see ‘UEFI: USB Hard Drive’. Select the drive using the down-arrow key and hit ‘Enter’. The system will restart and boot using the USB drive.

Note: ** Some computers under this assembly use ‘F12’ to enter into boot menu, use ‘F12’ if ‘F7’ does not work. ** –>  tergantung komputernya. Kemarin kami tekan tombol F9

5.The imaging process will take place. Wait until it finishes and prompts for a reboot. –> nah ini dia, lgsg restore image tanpa pandang bulu (tanpa peringatan) langsung ditimpa file2 di computer tsb.

6.Remove the USB drive from the Display Computer.

7.Restart the computer.

8.The computer will boot into Windows and conduct its initial setup process. Please wait until the logon screen displays.

9.Log in to Windows using the Operator credentials. –> awalnya otomatis, tapi kalau sudah coba production mode dan reset kembali. Nanti minta login manual. Isikan saja User=operator dan password = **** (password standard biasanya sama semua dari versi 3)

Window yang terpasang adalah Win 7.

10.Insert the configured USB drive into the Display Computer.

11.After inserting the USB drive, wait a few minutes for Windows to recognize the USB drive and install the drivers, if necessary. After it is done, Windows will pop up a dialog with an option that will read ‘Configure Display System using the program provided on the device’. Select this option and click ‘OK’. This will launch the ‘Display Deployment Tool’.

Note: If the popup does not display, open ‘My Computer’ from the desktop. Verify that a USB drive labeled ‘HMI’ or ‘Display System Deployment Tool’ is displayed under ‘Devices with Removable Storage’ (If the system is running on Windows 2000, it will be displayed as ‘Removable Disk’). Double-click on it, it should launch the ‘Deployment Tool’. If it does not launch, but opens the contents inside the USB drive instead, locate the ‘DeploymentTool.exe’ and double-click on it to launch the tool.

–> Pas saya coba tidak otomatis muncul. Jadi saya buka explorer dan buka drive flash disknya dan klik Deployment Tool.

Note: After the ‘Display Deployment Tool’ is launched for the first time, it will create a shortcut under the ‘Start’ menu called ‘Deployment Tool’. This shortcut can be used to launch the tool when needed.

12.Click the ‘Setup HMI’ button to set up the Display System.

Note: Any time during this setup process, if the computer prompts for a ‘Restart’, click ‘NO’ and wait until completing all of the steps. If it is absolutely necessary, the tool will automatically reboot and continue the setup process.

13.Click ‘Configure RSLinx’ to set up the drivers for the HMI to communicate. –> nah yang ini belum coba karena belum ada card PCIC nya. Tapi di TT4000 lain sudah bbrp kali kita coba. InsyaAllah sama.

14.Click the ‘Start Production Mode’ button to set the Display into production mode. –> gambar di bawah belum ditest di lapangan.

Demikian sharingnya.

Semoga bermanfaat bagi yang membutuhkan.


(1+sin t)(1+cos t)=5/4


ada pertanyaan dari kenalan di FB & sekalian saya simpan disini untuk dokumentasi ….

Jika diketahui (1+sin t)(1+cos t)=5/4
Berapa kah nilai (1-sin t)(1-cos t) ?

menarik juga untuk dicoba dan setelah berkali-kali mencoba selama bbrp jam saya menyerah ….🙂

akhirnya browsing juga dan berikut jawabannya ..












ini linknya.

Perinncian jawaban pertama …

(1 + sin t) (1 + cos t) = 5/4

1 + sin t + cos t + sin t cost = 5/4

1 + (sin t + cos t) +1/2 ((sin t + cos t) ^2 – 1 ) = 5/4

1 + y + ½ ( y^2 – 1) = 5/4

4 + 4y + 2 y^2 – 2 = 5

2 y^2 + 4 y – 3 = 0

y1,2 = (-4 ± sqrt (16 + 24) ) /4 = -1 ± ½  sqrt (10)

lanjut … ke 5/4 – 2y (penjelasan di atas) 

5/4 – 2 y = 5/4 – 2 (-1 ± ½  sqrt (10)) = 13/4 ± sqrt (10)

Nah ternyata yang bertanya juga sudah ada jawaban lain …

(1+sin t)(1+cos t) = 5/4
==> 1 +cos t + sin t + sin t * cos t = 5/4
==> cos t + sin t = 5/4 – 1 – sin t * cos t
==> cos t + sin t = 1/4 – sin t * cos t ….. ( pers 1 )
==> ( cos t + sin t )^2 = (1/4 – sin t * cos t)^2
==> 1 + 2 (sin t * cos t) = 1/16 – 2/4 * (sin t * cos t ) + ( sin t * cos t )^2
===> 16(sin t * cos t)^2 – 40(sin t * cos t) – 15 = 0
===> sin t * cos t = [40±√(40^2-4*16*(-15))]/(2*16)
===> sin t * cos t = [5±2√10]/4 ….. ( pers 2 )
pindah ke soal
(1-sin t)(1-cos t)
= 1 – cos t – sin t + sin t * cos t
= 1 – (cos t + sin t) + sin t * cos t
= 1-(1/4 – sin t * cos t) + sin t * cos t ….. dari pers 1. ( cos t + sin t = 1/4 – sin t * cos t )

= 3/4 + 2 sin t * cos t
= 3/4 + 2 [5±2√10]/4 ….. dari pers 2. ( sin t * cos t = [5±2√10]/4 )

= [13±4√10]/4