# Violation error

**URL:** <https://forum.universal-robots.com/t/violation-error/39218>\
**Category:** Technical Questions\
**Created:** [March 24, 2025, 7:21am UTC](https://forum.universal-robots.com/t/violation-error/39218 "2025-03-24T07:21:01Z")\
**Posts on this page:** 8\
**Page:** 2

<div class="post-metadata">

**Author:** ![jumpingjack](https://avatars.discourse-cdn.com/v4/letter/j/dbc845/32.png) [@jumpingjack](https://forum.universal-robots.com/u/jumpingjack)\
**Post date:** [March 26, 2025, 2:04pm UTC](https://forum.universal-robots.com/t/violation-error/39218/21 "2025-03-26T14:04:16Z")

</div>

You can push the robot in safety mode, just after brake unlock, (it’s hard to push) or use manual move and any move in the right direction is allow, it do short move at any pressure.  
If can’t release brake you can open the cover of the axis over limit and push the brake with a finger to move the robot. Better to be in 2 if is one of the 2 arm axes. Please be sure to move in the right position and check the position on the screen.

---

<div class="post-metadata">

**Author:** ![jumpingjack](https://avatars.discourse-cdn.com/v4/letter/j/dbc845/32.png) [@jumpingjack](https://forum.universal-robots.com/u/jumpingjack)\
**Post date:** [March 26, 2025, 2:06pm UTC](https://forum.universal-robots.com/t/violation-error/39218/22 "2025-03-26T14:06:57Z")

</div>

This is strange, there is no power, may be you have broken the cable? Check if you have power in the pins of the cable attached to the base. If not there is a problem in the controller else the cable is broken inside the robot.

---

<div class="post-metadata">

**Author:** ![2383120](https://avatars.discourse-cdn.com/v4/letter/2/a4c791/32.png) [@2383120](https://forum.universal-robots.com/u/2383120)\
**Post date:** [March 26, 2025, 2:19pm UTC](https://forum.universal-robots.com/t/violation-error/39218/23 "2025-03-26T14:19:55Z")

</div>

Manually touching the brakes will it be fine? I mean thats my uni’s robot I don’t want end up paying fines😅

---

<div class="post-metadata">

**Author:** ![2383120](https://avatars.discourse-cdn.com/v4/letter/2/a4c791/32.png) [@2383120](https://forum.universal-robots.com/u/2383120)\
**Post date:** [March 26, 2025, 2:20pm UTC](https://forum.universal-robots.com/t/violation-error/39218/24 "2025-03-26T14:20:42Z")

</div>

I can see green light between power and controller but not between power and robot

---

<div class="post-metadata">

**Author:** ![eric.feldmann](https://avatars.discourse-cdn.com/v4/letter/e/94ad74/32.png) [@eric.feldmann](https://forum.universal-robots.com/u/eric.feldmann)\
**Post date:** [March 26, 2025, 3:43pm UTC](https://forum.universal-robots.com/t/violation-error/39218/25 "2025-03-26T15:43:38Z")

</div>

I don’t think I’d mess with the brakes. I would focus on getting rid of the Mode Selection thing first. The controller isn’t sourcing 24v BECAUSE it’s in the violation state. You need to boot the robot to get power at the terminals. And if you can’t boot the robot because of safety settings, you’ve got a catch 22.

So lets just delete the installation and start fresh. I’m going to assume default passwords here. If they’ve changed, get them from your University.

Tap and hold the “Run” button in the top left until it asks for a password. Type “lightbot” and hit enter. Then choose the “File Editor” option and type “easybot” when it asks for the admin password. Now go to Programs and change the dropdown in the bottom right to show “All Files.” From there, find the “default.installation” file and delete it. I went ahead and deleted the default.variables as well. Maybe that’s not needed, I dunno. Then exit out and reboot the robot. It should now at least boot up without the Mode Select thing locking you out.

---

<div class="post-metadata">

**Author:** ![2383120](https://avatars.discourse-cdn.com/v4/letter/2/a4c791/32.png) [@2383120](https://forum.universal-robots.com/u/2383120)\
**Post date:** [March 26, 2025, 4:33pm UTC](https://forum.universal-robots.com/t/violation-error/39218/26 "2025-03-26T16:33:34Z")

</div>

Thankyou so much it solved the problem completely really appreciate your time and effort. Thankyou again.

---

<div class="post-metadata">

**Author:** ![jumpingjack](https://avatars.discourse-cdn.com/v4/letter/j/dbc845/32.png) [@jumpingjack](https://forum.universal-robots.com/u/jumpingjack)\
**Post date:** [March 26, 2025, 5:03pm UTC](https://forum.universal-robots.com/t/violation-error/39218/27 "2025-03-26T17:03:05Z")

</div>

Depends if you are authorized or not.  
Moving manually the mechanical lock is a procedure written on service manual.

---

<div class="post-metadata">

**Author:** ![2383120](https://avatars.discourse-cdn.com/v4/letter/2/a4c791/32.png) [@2383120](https://forum.universal-robots.com/u/2383120)\
**Post date:** [September 29, 2025, 10:09am UTC](https://forum.universal-robots.com/t/violation-error/39218/28 "2025-09-29T10:09:14Z")

</div>

Hey UR Community!

I’ve been tinkering with UR5 control and just wrapped up: a Unity-based VR setup that lets you teleoperate the UR5 arm using a Meta Quest controller. It handles real-time pose tracking, gripper actions for picking/placing objects, and smooth joint interpolation via TCP to a Python RTDE server. Super intuitive for immersive robot ops!

If you’re hiring for roles in robotics software, VR/AR integration, or automation engineering, I’d love to chat – hit me up with leads or openings. Open to remote/full-time gigs!

[Previous page](https://forum.universal-robots.com/t/violation-error/39218.md?page=1)
