Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the ga-google-analytics domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/sucs4139/public_html/wp-includes/functions.php on line 6121
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the woocommerce-call-for-price domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/sucs4139/public_html/wp-includes/functions.php on line 6121
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the woocommerce domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/sucs4139/public_html/wp-includes/functions.php on line 6121
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the facebook-for-woocommerce domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/sucs4139/public_html/wp-includes/functions.php on line 6121
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the jetpack domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/sucs4139/public_html/wp-includes/functions.php on line 6121
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wpforms-lite domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/sucs4139/public_html/wp-includes/functions.php on line 6121
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/sucs4139/public_html/wp-includes/functions.php on line 6121
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the header-footer-elementor domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/sucs4139/public_html/wp-includes/functions.php on line 6121
Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the all-in-one-wp-migration domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/sucs4139/public_html/wp-includes/functions.php on line 6121 [Video] Tutorial Cara Mengganti Print Head Printer Passbook Epson PLQ 20 - SUCCESS COMP
Epson PLQ 20 menjadi Printer Passbook yang cukup familiar dan banyak digunakan oleh Bank-bank atau Badan Usaha yang memerlukan mencetak pada buku tabungan. Meski Printer Buku Tabungan ini terbilang awet dan bandel, namun bisa karena penggunaan yang berlebihan atau masa pakainya, Print Head pada PLQ 20 ini bisa mengalami kerusakan yang membuat Printer tidak dapat mencetak dengan maksimal atau bahkan tidak dapat mencetak sama sekali. Tentu hal ini dapat mengganggu aktifitas nasabah. Untuk itu kita harus mengganti Print Headnya dengan yang baru. Nah kali ini Success Comp akan memberikan tutorial lengkap, bagaimana cara mengganti Print Head pada Printer Epson PLQ 20.
Berikut Tutorial Lengkap cara Mengganti Print Head Printer Passbook Epson PLQ 20:
Peralatan yang perlu disiapkan:
Print Head Epson PLQ 20 yang Baru atau Pengganti
Obeng Plus
Langkah-langkah cara mengganti Print Head pada Printer Epson PLQ 20:
Matikan printer jika masih dalam keadaaan menyala
Buka cover / tutup printer
Dorong tuas yang ada di sebelah kiri ke atas lalu geser print head ke tengah
Angkat ribbon cartridge / pita bila masih menempel pada printer
Ambil obeng plus, lalu buka baut pada sisi print head
Cabut print head dan tarik flexible kabel dari print head
Lalu pasangkan print head yang baru dengan menaruh kembali kabel flexible yang dicabut tadi
Kemudian pasang kembali baut-baut pada print head dan turunkan tuas yg ada disisi kiri.
Terakhir tutup cover dan silakan coba test print head yang baru dipasang
Mudahkan? Semoga tutorial diatas bermanfaat dan bisa Anda aplikasikan langsung, kami juga sangat menyarankan untuk selalu menggunakan Produk Print Head Original, apabila Anda masih mengalami kesulitan silahkan tinggalkan pertanyaan di kolom komentar dibawah atau bisa hubungi Success Comp klik WA 0852-10000-355 Tim Expert Kami dengan senang hati membantu Anda.
Leave a reply