Still waiting for useful help with fixture loading
TobyChan1101 · 16 May 2026, 05:28 UTC
20 replies
Have you captured the exact alarm before restarting? Also, does the stop happen before release, during it, or after it?
6pointsCaptured it: missing process confirmation. The unedited video shows a wait before release. I'd described it as a dropped part, which didn't help.
2pointsSend a corrected description supported by the exact alarm, full recording and installed version details. Ask support to identify the expected confirmation and assign responsibility for the next diagnostic action
15pointsWorth leaving my original description visible? It's wrong, but deleting it might make the replies look odd.
8pointsKeep it with a clear correction. Explain that the full clip shows a pre-release wait; that tells support why the investigation needs to change direction
11points@YasminChen1137 My own support case stalled because the robot and gripper contacts each expected the other to arrange the test. A named coordinator clarified who would organize the next action.
14pointsI've checked our messages. Same gap here: each contact asks what the other said, but neither has assigned the test.
0pointsThat missing confirmation points to the gripper, so its contact should take the diagnostic lead
21points@YasminChen1137 You're jumping from a missing signal to a failed component. It could be the interface or sequence. The alarm doesn't assign ownership by itself.
13pointsYou're right; I assigned the cause too early. Ask the package seller to coordinate tracing that confirmation across the interface, with both contacts involved as needed
13pointsWhen you say the seller should coordinate this, do you mean Alibaba or the business that supplied the package through the marketplace?
18pointsThe unnamed seller who supplied your package. Alibaba is the marketplace; your technical request here is to the seller and their support contacts
10pointsWould you send every log I have? There are lots, and I don't know which ones cover the stop.
7pointsAsk which diagnostic files they need and provide the ones you can tie to the event. Include collection context; unrelated bulk can hide the useful bit
20pointsI labeled my own attachments by what they showed, not 'new video final'. A small kindness to the person opening the ticket, and to myself.
13pointsGuilty of the 'final' filenames. I also cut the original clip too tightly; it lost the wait leading into the alarm.
-2points@TobyChan1101 Attach the full recording even if you include a short excerpt to highlight the symptom. The lead-in you found is relevant to understanding how the alarm arose.
20pointsWould diagnosis require repeated attempts while support observes, or can the existing alarm and full recording support the next step?
1pointsStart with what's captured. Any further equipment test needs a defined procedure from the responsible support or integration person, especially with a workpiece still held
19pointsI'll ask for one named owner, the confirmation they want traced and the exact files needed. That's a request I can actually follow.
-2pointsAdd to the discussion
Welcome to Application Robot
Everyone can read the forum. Sign in or create an account to start a discussion, reply, or upload photos.
By creating an account, you agree to our Terms and Conditions and community guidelines. Read our Privacy Policy for how your information is handled.