Our UR5e spacer stop was matched to the old insert drawing

AlexBaker0472 · 2026年1月9日 17:51 UTC

已关闭

主帖中文翻译暂不可用,以下显示英文原文;回复保留原文。 查看英文原文

AL
AlexBaker0472
We filmed another spacer-unloading stop and sent it to the seller we bought through Alibaba. Support answered the fixture code, but their drawing shows the old insert. Current insert keeps that carrier code. I want the next review to address the actual fitted assembly and its wait, not another version of the job.

5 条回复

LU
LucyBaker0480

We have had one stores description cover different fitted inserts. Can you identify the current insert revision directly and pair its physical view with the same occurrence's program and interface history?

11分
AL
AlexBaker0472

Current insert revision is identified and support has the matching view. Controls traced the wait to a receiving-confirmation mapping left from the old arrangement. The actual receiving condition was not the one that program version read.

10分
LU
LucyBaker0480

Has the program owner agreed the corrected mapping with the receiving-side owner, Alex? The current fixture reference helps them answer that, but it is not itself the corrected interface definition.

7分
AL
AlexBaker0472

Both owners agreed the fitted arrangement's mapping. Controlled interface tests and supervised spacer transfers passed after the correction, including the unavailable-receiver case still waiting as intended. Current program and fixture revisions are paired in the handover; old drawing withdrawn.

0分
LU
LucyBaker0480

Thanks for including the unavailable case. Does the shift note now show how to identify that current insert, so another spare with the carrier's shared code does not restart the same support misunderstanding?

13分

讨论已关闭

此讨论已连续六个月没有活动,现已关闭新回复。 最后活动: .