JXT Reducer CAD Drawing Assistant

Problem

Reducer drawing generation often slows down at parameter confirmation. Inputs such as power, transmission ratio, tooth count, module, and load coefficient are scattered, while the results depend on a shared engineering calculation path. Engineers can end up switching between web forms, spreadsheets, and drawing APIs, manually tracking intermediate values and rechecking the full calculation after each change.

How It Works

The skill turns the JXT reducer workflow into confirmable API steps:

• List products: retrieve reducers in the category and let the user choose a model by number.
• Collect parameters one by one: ask for a single input_params field at a time; fields with options_source are precomputed first to expose dropdown choices.
• Initial calculation: submit all collected inputs once, then store the returned filename.
• Incremental updates: send only changed parameters with the same filename, so unchanged cells are not overwritten.
• Create work order: create a guest work order from filename and store the returned guest_code.
• Track progress: poll status every roughly five seconds, showing queued, in-progress checklist, or completed output files.

Boundaries

Use it when reducer selection, parameter trial calculations, and work-order tracking need to form a conversational workflow. Keep these constraints in mind: parameters should be confirmed one at a time, incremental requests must contain only changed fields, filename and guest_code must be retained, and final outputs still need to be viewed or purchased on JXT.