please update code, 1- there were a feature, when...
创建于:2026年9月29日
使用 GPT-5.6 Thinking 回答 Chat01
创建于:2026年9月29日
使用 GPT-5.6 Thinking 回答 Chat01
please update code,
1- there were a feature, when position is 20 for example and i need less tham 20 position motor goes 0 first then goes this value, remove this feature, i think its in OBJ only? remove it and tell me which motors were use this feature
2- goto command, make motors moving fastest possible speed
I’ll trace the motion logic first to find the “go to 0 before moving lower” behavior, identify exactly which motors use it, then remove it and make goto movements use the maximum configured motor speed.
I found the zero-first behavior: it is OBJ-only. The code explicitly re-homes OBJ whenever an absolute target is lower than (or equal to) its current non-zero position; CAM, REL, SLD, and CAR do not use that rule.
For GOTO, I’m using 9600 steps/sec, which this firmware already defines as its highest accepted/known-used step rate.
The edit is now applied. OBJ will move directly from a higher position to a lower requested position instead of homing to 0 first; an equal-position request simply remains a no-op as normal.
GOTO CAM/REL/OBJ/SLD/CAR ... now schedules at 9600 steps/sec for every axis, including REL (which previously ran much slower through its GOTO path). I’m doing a final consistency check for leftover OBJ re-home state/references.
Updated the code as requested.
I also removed the obsolete OBJ home-then-move variables and logic rather than just disabling the condition.
Download the updated AIRO_LAB3_8.ino
One note: 9600 steps/sec is the firmware's existing maximum validated rate. Since there is no acceleration ramp, if a motor physically stalls/skips when starting instantly at 9600, the speed would need adjustment.