hawk-shop (FRC2713) errors

5 recurring problems engineers report in hawk-shop (FRC2713), ranked by impact.

#96 by errors trackedMCADPLMPDM

Recurring hawk-shop (FRC2713) errors, by impact

  1. 1A robotics team's homemade Onshape-to-shop board lets a part release once it has a material and a part number. Nothing tells the shop that the material is a placeholder, the quantity looks wrong, or the part has no description. Those problems surface at the machine, after someone has already cut stock. People also type the same part number three ways and write 1/2 inch in one title and 0.5 in another.MCAD · Agent failure · 1 report74
  2. 2A robotics team's shop tool writes part numbers into Onshape, but its own spec says a member can receive a success message even when Onshape rejected the write, and the verification read never checks the value. The browser and server cache keep showing the old number, leaving members uncertain whether a part is ready for manufacturing.PLM · Agent failure · 1 report74
  3. 3Roughly half an FRC bill of materials is purchased, not manufactured: motors, bearings, sprockets, belts, swerve modules, chain, fasteners. The team's Onshape-to-shop board only tracks parts released from a Part Studio, so the purchasing half of the season still lives in whatever spreadsheet it lived in before, and nothing connects the drivetrain needs 8 of these to we have 5 in the cabinet.PDM · Agent failure · 1 report74
  4. 4Every Onshape call spends an annual allocation that cannot be topped up. Thumbnails cached by URL show an old picture of a part that has since been redesigned. Plan is microversion keys and webhooks.MCAD · Agent failure · 1 report66
  5. 5Onshape gives a fixed yearly API allocation and returns 402, not 429, when it runs out, which stops the connector until the year resets. Nobody can answer how close the team is to the limit without the admin page. A student changing the connector cannot tell which quirks are documented by Onshape and which were guessed from one observation.MCAD · Agent failure · 1 report66

How it fails

  1. Agent failure5

Sourced from public community reports. Costs and delays on individual entries are modeled estimates, not measurements.