We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
docs: correct AD5X control/IFS semantics Verified against latest firmware versions: - slotId is 1-based (1-4), not 0-based, and matches the slot argument of msConfig_cmd/ms_cmd. Both ff-5mp-api-ts and FlashForgeUI-Electron treat it as 1-based. Fix the slotInfos example, rewrite the slotId field description, and call out that toolId (0-based) is the easily-confused counterpart. - slotCnt: "typically 4" -> "always 4 on AD5X". - extrudeCtrl_cmd: axis arg is accepted but discarded; the command always drives the extruder (E) axis regardless of axis value. - errorCodeCtrl_cmd: action must be exactly "clearErrorCode" and errorCode must match the current active error code; document both args. - State Action Codes (0-5): caveat as inferred, not confirmed. - Add calibration_cmd and userProfile_cmd to HTTP REST API (5M Pro).
Fix speed range, circulateCtl args, and printProgress docs - Update speed range from 50-150 to 50-500 with model-specific notes (50-150 for 5M/Pro, up to 500 for AD5X) in HTTP-REST-API.md and AD5X.md - Correct circulateCtl_cmd arg values from "on"/"off" to "open"/"close" to match actual wire protocol, in HTTP-REST-API.md and Adventurer-5M-Pro-Features.md (including all use case examples) - Add bold clarification that printProgress is a ratio (0.0-1.0), not a percentage, in HTTP-REST-API.md Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Fix all broken markdown file links
update wiki
Fix title, wrong info about completed state