EasyManua.ls Logo

Stratasys F770 - Page 251

Stratasys F770
262 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
Warnings and Errors Build Pause Warnings
Page 240
© Copyright 2021 Stratasys. All rights reserved.
Active support spool removed
• Indicates that the printer lost contact with the support material coil box’s memory chip.
• Correct condition - ensure that the filament key is seated correctly within its filament port. If
so, disconnect and then reconnect the material coil box (see “Handling/Storing Materials”
(page 121) and “Connecting Material Coil Box To Printer” (page 108)). If this does not
correct the error, disconnect the current material coil box and connect a new one.
Model head removed
• Indicates that the printer lost contact with the model head.
• Correct condition - ensure that the head is seated correctly within the gantry. If so, remove
the head and then reinstall it (see “Head Replacement” (page 121)). If this does not correct
the error, remove the head and install a new head.
Support head removed
• Indicates that the printer lost contact with the support head.
• Correct condition - ensure that the head is seated correctly within the gantry. If so, remove
the head and then reinstall it (see “Head Replacement” (page 121)). If this does not correct
the error, remove the head and install a new head.
Y motor jam
• Indicates that the Y motor was unable to fully complete a move.
• Conect condition - inspect the build chamber for obstructions. If none, open the right head
access cover, move the head carnage by hand and look for obstructions. If nothing is
evident, resume the build and watch to see if the error repeats. If no solution is found,
reboot the system.
X motor jam
• Indicates that the X motor was unable to hilly complete a move.
• Collect condition - inspect the build chamber for obstructions. If none, open the right head
access cover and look for obstructions. If nothing is evident, resume the build and watch to
see if the error repeats. If no solution is found, reboot the system.

Table of Contents