Our inspection handover shows pendant pages for the bracket routine, but the recipe is selected outside those pages. The integrator is still available and I want the missing bits while we can ask them.
I have the job files, not only pictures. Correction, I have a folder labelled current; I cannot match its revision to the screenshots. The ordinary PLC signals and fixture version are missing too. Where would you start making this usable for the next person?
I cannot tell which inspection recipe our UR5e handover expects
AishaAli0257 · 2026年3月24日 07:38 UTC
主帖中文翻译暂不可用，以下显示英文原文；回复保留原文。 查看英文原文
17 条回复
回复 AishaAli0257
Start with one identified working job. Can the integrator match your folder to the installed version?
11分They can compare it, Pavel. I've sent the folder and asked them to identify the installed job separately, so we don't just bless the name current.
0分回复 AishaAli0257
I'd follow one bracket through the whole call chain. Main routine, called subprograms, recipe selection, result coming back. My fixture sketches used to stop at the nice obvious bit where the part was sitting down. Then somebody asked what told the rest of the job it was the right part. Fair question. Not much of an answer in the sketches.
7分回复 AishaAli0257
Which fixture feature distinguishes the bracket versions? A recipe list alone will not show that.
8分Henry's point matters. If two brackets can sit in the same nest, a beautiful recipe table can still leave the operator choosing by memory. I would want the actual selection method shown, including who changes it.
23分Henry, there is only one bracket version in this job, but two inspection recipes for different requested checks. Jack, tracing the calls found a missing subprogram in our folder. The integrator has supplied the matching set and identified its revision against the installed job.
14分BE
回复 AishaAli0257
Could the next person tell those two requested checks apart without asking whoever made the order?
14分回复 BenBench
Put that answer in the issued handover, not somebody's private teaching copy. I've seen the useful explanation stay in the trainer's folder while everyone else receives the screenshots.
6分回复 BenBench
Ben, not from our old notes. The work order names the requested check but the recipe screen uses shortened names. I've put the two pairs together and asked quality to confirm the mapping.
0分回复 AishaAli0257
That missing subprogram would have had me chasing the wrong problem for ages. Are the ordinary PLC waits now attached to the stages where they occur, or still in a separate list?
9分回复 AishaAli0257
Did quality confirm both name pairs?
12分A separate signal list is useful for maintenance, Jack. Operators also need the meaning at each waiting stage.
1分Pavel, quality confirmed one pair and corrected the other: we had copied the name of an older check. Jack, the draft now shows the ordinary waits beside the relevant stages, with a separate signal list for maintenance as Henry suggests.
13分回复 AishaAli0257
That's a real catch. Does changing the shortened name need a software change, or can the handover show the current display exactly? I'd avoid a picture of what people wish the screen said.
6分回复 HugoBlair
We're keeping the current screen names in the handover, Hugo, with quality's descriptions alongside. No screen change is part of this update.
16分回复 AishaAli0257
Who has tried finding a waiting stage using the draft? Someone who did not help write it would be useful.
11分A relief technician found the recipe mapping and the matching job set without me talking them through it. They couldn't find who to call for an unexpected wait, though. That's still missing; I've sent that specific gap to our cell owner. Thanks for pushing beyond the screenshots.
18分讨论已关闭
此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .