Put the packed box's marked supports over the preceding layer and show the complete tool releasing in placement order. The useful view includes neighbours, not just the box being carried.
Cannot select the UR5e layer from separate support and tool views
HazelBarnes0571 · 28 Jun 2026, 21:17 UTC
17 replies
Our top view has placement arrows only. No open tool or withdrawal path.
23 pointsThen request one actual placement in context. Pick a rotated box where a support lies over a gap. Show what is already on the pallet and where the tool must go after release. That gives both reviewers the same concrete problem.
18 pointsI would not conclude the box is unsupported solely because the outline crosses a gap. More precisely, compare its required bearing regions with that gap and packaging's permitted conditions before deciding whether the layout fails.
-6 pointsThe marked end region crosses it. Packaging has not stated that bridging is permitted.
7 pointsOur review once used empty cartons to illustrate a pattern. Useful picture, but it did not establish support under load. Are your support marks for the packed product?
15 pointsYes, Owen. The packing specification identifies the reinforced ends of the filled box.
7 pointsThat is a useful starting point. Does the tool designer have that same packing specification, Hazel?
13 pointsAaron, I'd send the marked drawing as well. The end-support detail can disappear when the next person extracts only outside dimensions from the specification.
3 pointsAnd identify the revision on their response. A new layout can solve the tool's exit and move the unsupported box somewhere else, so two answers against different drawings are not a joint assessment.
21 pointsTooling had dimensions only. I've sent the marked support view and requested a common revision.
1 pointsWho settles the conflict if packaging wants support exactly where tooling wants an exit? I would ask who owns that decision before separate approvals start arriving.
7 pointsThe integrator can coordinate alternatives, with packaging retaining the support decision. No need for Hazel to invent a compromise clearance between two suppliers' drawings.
13 pointsOur integrator owns that review. They've acknowledged both constraints, with no revised layout yet.
17 pointsIs reducing the layer count allowed, or does dispatch require the current count? That could affect which alternatives they should spend time on.
17 pointsDispatch has not answered that. I left count flexibility open in the request.
11 pointsThen keep a lower-count layout conditional, not the agreed solution. You've identified what the review needs, but neither the support result nor the tool route has been supplied yet.
14 pointsAdd 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.