FastCOLOUR LFP print function + quality (Q957 FACTS LOCKED — OPEN)
- Source-Date (SAST): 2026-09-29
- Dest: both
- Review-after: 2027-09-29
- Status: current
- Topic status: FACTS LOCKED — waiting Eric end/next (not ANSWERED)
- Source: Eric Yin Quest Q957 — YouTube ML_GqqwT-EQ; quiet facts lock 2026-09-29; queue stays pending/open; PrintExp keypad photo addendum same day
- Raw archive:
_raw/quest-eric-full-2026-09-16.md - Related:
fastcolour-f1-1800-ecosolvent-laminator-q573.md,fastcolour-one-hybrid-f1-f2-q042.md,f1-atools-f2-printexp.md,fastcolour-old-f1860-f1600-q985.md,fastcolour-lfp-cutter-old-f1800-f1-q802.md,fastcolour-eco-solvent-pvc-q047.md - Eric PrintExp keypad photo:
images/printexp-controller-keypad-eric.jpg(also/workspace/quest-q957/printexp-controller-keypad-eric.jpg)
Topic status
- Q957 is FACTS LOCKED but still OPEN. Do not treat as ANSWERED until Eric says end/next.
- Densifies large-format printers / FastCOLOUR sell on print function + print quality (eco-solvent / LFP media print result).
- Overlapping pending ASK_QUEUE items that only asked the same “exact F1/FastCOLOUR sell; densifies large-format-printers” template were pruned as answered by this lock (Q957 itself stays pending).
Eric full wording (lock this)
"For printer, focus on what it prints and quality it prints. Whether is F1 or F2 just control system difference. We not move to PrintExp (F2-) controller and in video is one. We need to focus on function not what’s the component"
Addendum (PrintExp keypad visual ID):
"Btw, PrintExp controller looks like this . The keypad arrangement"
(Photo: blue chassis panel, am.co.za branding; labeled keys OFFLINE / CLEAN / SETUP / TEST / NOZZLE CHECK / FEED; arrow pad Y+ Y- X- X+; EXIT / ENTER; power button. Saved as images/printexp-controller-keypad-eric.jpg.)
Densify rules
- Densify as FastCOLOUR / LFP print capability + print quality (what it prints and how good it looks), NOT as an F1-vs-F2 SKU identity fight.
- F1 vs F2 = control-system difference only — do not treat F1/F2 as the main sell story for this clip (or for matching LFP densify clips).
- Video ML_GqqwT-EQ shows a PrintExp (F2-) controller, but AM is NOT moving to PrintExp — do NOT treat the clip as an F2 / PrintExp sell push or as evidence AM is adopting PrintExp.
- PrintExp (F2-) controller visual ID is locked from Eric’s photo: keypad arrangement with OFFLINE / CLEAN / SETUP / TEST / NOZZLE CHECK / FEED, Y+/Y-/X-/X+ pad, EXIT / ENTER, power button, am.co.za on blue panel — cite
images/printexp-controller-keypad-eric.jpg. Use this to recognise PrintExp when it appears; still do not sell the clip as an F2/PrintExp push. - Do not invent an exact current chassis SKU from the video alone; steer to live FastCOLOUR LFP catalog when selling today’s machines.
- Still densifies large-format-printers / FastCOLOUR sell (eco-solvent / LFP media print result). FastCOLOUR ≠ FastJET; ≠ FlatPRINT; ≠ UV-DTF; ≠ PrintUP 3D.
- Brief: focus on function and print quality; F1/F2 is controller only; PrintExp keypad ID locked but AM not moving to PrintExp.
Queue handling
- Keep Q957 pending/open until Eric says end/next.
facts_locked/facts_locked_at_sastset; do not setstatus=answeredoranswered_at_saston Q957 yet.- Don’t decrement pending for Q957 itself on this fold.
- Do prune other pending asks that only repeat the same LFP/FastCOLOUR exact F1-sell densify template — mark answered with resolution citing these Q957 densify rules (queue must shrink).
Ask AI do / don’t
- Do densify ML_GqqwT-EQ as FastCOLOUR LFP on print function + quality (eco-solvent / LFP media look).
- Do treat facts as locked while quest remains OPEN (waiting end/next).
- Do recognise PrintExp by Eric’s keypad photo when the controller appears.
- Don’t make F1 vs F2 the sell story — that is control-system difference only.
- Don’t treat the clip as an F2 / PrintExp sell push; AM is not moving to PrintExp.
- Don’t invent a current chassis SKU from the video alone — steer to live FastCOLOUR LFP catalog.
- Don’t call this FastJET, FlatPRINT, UV-DTF, or PrintUP 3D.
- Don’t mark Q957 ANSWERED until Eric closes with end/next.