Top 4 shrink sleeve troubleshooting and solutions

At this stage, the automatic shrink cuff packaging machine is widely used in the pharmaceutical and food industries. This device is a equipment with intelligent control, but how to solve shrink sleeve troubleshooting?

Usually it has 4 troubleshootings:

Question 1: The shortening chamber can not be heated properly.
Question 2: The heat motor does not rotate.
Question 3: The transmission motor does not rotate.
Question 4: control system failure.

Fully-auto-vertical-STF5545LV_MSTS6040

Let me introduce it in detail:

Question 1: The shortening chamber can not be heated properly.

(1), check whether the temperature control instrument is out of order, if so, to repair or perhaps interchange in a timely manner.
(2), check whether the communication touch device is damaged, if so, only interchangeable.
(3), check whether the indoor wire joints are aging short-circuit phenomenon, if so, reconnected.
(4), check whether the electric heating tube is damaged, the same, if so, to interchange.

Question 2: The heat motor does not rotate.

(1), check whether the fan is damaged, if so, interchangeable.
(2), check whether the hot air switch is damaged, the same, to be replaced in a timely manner.
(3), check whether the wind blade is stuck, if so, to touch, and re-open, advocate the operator to check again after each operation.

Question 3: The transmission motor does not rotate.

(1), to see if the motor switch is not out of order, timely interchange.
(2), to see if there is damage to the high-speed device, to be replaced in a timely manner.
(3), to see if the motor is not burned due to overheating, is the case timely interchange.

Question 4: control system failure.

The cause of such a failure lies in the failure of the PLC output relay, there are three kinds of sticking, not connected and short-circuit. Adhesion fault manifestation for the implementation of the element does not reset such as the cylinder does not reset, put the film motor rotation non-stop. Non-connection fault manifestation for the implementation of the cylinder does not move.

The last short-circuit fault manifests itself in the form of the actuating element not acting, and the short-circuit of the device is caused by the breakdown of the voltage regulator diode protecting the output relay.

The solution to the above three forms of failure is to replace the output relay. The main convenient method is to use a programmer to replace the points and then modify the output points from the program.

If there is no programmer, you can disassemble the PLC to remove the circuit board, and then the spare point of the relay soldered down as spare parts installed to

You can pay more attention to the shuntian website at ordinary times, which many summaries and collated on the shrink sleeve troubleshooting knowledge points, after reading the situation does not have to appear when you do not know how to deal with it. If you really do not understand, you can also contact us through the following ways: enquiry@chinashrinkmachine.com 008613302063626

Related products

Contact us

SHUNTIAN

Fatal error: Uncaught wfWAFStorageFileException: Unable to save temporary file for atomic writing. in /www/wwwroot/st-packaging.com/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php:34 Stack trace: #0 /www/wwwroot/st-packaging.com/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php(658): wfWAFStorageFile::atomicFilePutContents() #1 [internal function]: wfWAFStorageFile->saveConfig() #2 {main} thrown in /www/wwwroot/st-packaging.com/wp-content/plugins/wordfence/vendor/wordfence/wf-waf/src/lib/storage/file.php on line 34

Fatal error: Uncaught RedisException: MISCONF Redis is configured to save RDB snapshots, but it's currently unable to persist to disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error. in [no active file]:0 Stack trace: #0 {main} thrown in [no active file] on line 0