skills.rest
HPI-Jimmy-Chiu
HPI-Jimmy-ChiuCOMMUNITY
Explore all skills by this author →
GitHub

ht9045-index-flow

Documents HT9045 IC test handler Index Arm state machine flows and case values.

Updated May 28, 2026
Search Tags:#c++#state machine#embedded debugging#ic test handler#ht9045#index arm#test head
One-click install
npx skills add https://github.com/HPI-Jimmy-Chiu/HT904_V899 --skill ht9045-index-flow-hpi-jimmy-chiu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ht9045-index-flow
Source: https://github.com/HPI-Jimmy-Chiu/HT904_V899/tree/main/.agents/skills/ht9045-index-flow
Command: npx skills add https://github.com/HPI-Jimmy-Chiu/HT904_V899 --skill ht9045-index-flow-hpi-jimmy-chiu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Engineers maintaining the HT9045 IC Test Handler struggle to trace the Index Arm (Test Head Motor) state machines spread across multiple C++ source files, making it hard to interpret Task case values, debug test flow issues, or understand Front/Rear/32-site test switching. ## Core Features & Use Cases - State Machine Reference: Maps the full DoTestHeadMotor, DoTestY, DoTestYFront, DoTestYRear, and DoTestY_TwoArm32Site state machines with Task variable names and case value meanings. - Call Hierarchy Tracing: Shows the complete calling tree from DoTestHeadMotor down through Destroy IC, AutoSiteMap SuckTest, and IndexEveryTimeCheckEP sub-flows. - Use Case: When a handler stops at an unknown state during production, look up the Task case number (e.g., 121xx torque check or 40200 RTC FullView) to identify which sensor, vacuum, or torque check is blocking the flow. ## Quick Start Ask the AI to explain what the HT9045 Index flow does at a specific Task case number, such as what happens in DoTestHeadMotor case 1500.

Frequently Asked Questions about ht9045-index-flow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I trace the HT9045 Index Arm test flow?▼

Start from DoTestHeadMotor in atester.cpp, which is the top-level state machine using iTestHeadMotorTask. Task 600 enters the DoTestY loop, which dispatches to DoTestYFront, DoTestYRear, or DoTestY_TwoArm32Site depending on test mode.

What do the Task case numbers mean in DoTestHeadMotor?▼

Case ranges map to flow phases: 200000-600000 handle index vacuum self-checks, 10000-10030 check F16 shuttle sensors, 121xx/141xx run arm torque and vacuum checks, 40200-40510 handle RTC FullView and ROI learning, and 600 enters the test loop.

How does Front and Rear test head switching work in HT9045?▼

DoTestY case 50 determines front/rear test priority, then cases 100-110 call DoTestYFront and cases 200-210 call DoTestYRear. Cases 60-70 handle soak time, heater conditions, and front-rear alternation logic.

What is the PlaceToShuttleFirst flow used for?▼

PlaceToShuttleFirst clears ICs remaining on the test head before normal operation, using Task cases 20000-21500 in DoTestHeadMotor. It calls DoFrontTestDestroyIC or DoRearTestDestroyIC depending on which head holds ICs, then returns to Task 1.

Why does the Index flow stop before entering the test loop?▼

Common blockers include failed torque or vacuum checks in the 121xx/141xx arm check states, socket sensor errors in cases 9-21, EP inflation pressure failures in IndexEveryTimeCheckEP, or OutShuttle lose-IC errors that force an early return in REAL mode.

Related Skills

Explore More Software Engineering Skills→
ai-sand-castlesai-sand-castles

rpc-document

Generate a JSON schema documenting an RPC from C++ source files.

Official
Advanced
min-zoumin-zou

bug-carpet-analysis

Analyze robot vacuum carpet bugs from log files and sensor data.

Community
Advanced
VektaVekta
2

diagnose

Diagnose codebase problems by inspecting files, git history, and test cases.

Official
Advanced
ggazzoggazzo

reversa-detective

Extract implicit business rules and state machines from legacy Git repositories.

Community
Advanced