# Error after update shuts down whole operation

**URL:** <https://xrp.discourse.group/t/error-after-update-shuts-down-whole-operation/642>\
**Category:** Support\
**Created:** [March 18, 2025, 5:50pm UTC](https://xrp.discourse.group/t/error-after-update-shuts-down-whole-operation/642 "2025-03-18T17:50:54Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![dwhite](https://avatars.discourse-cdn.com/v4/letter/d/82dd89/32.png) [@dwhite](https://xrp.discourse.group/u/dwhite)\
**Post date:** [March 18, 2025, 5:50pm UTC](https://xrp.discourse.group/t/error-after-update-shuts-down-whole-operation/642/1 "2025-03-18T17:50:54Z")

</div>

Problem importing from library, please see attached

 ![error](https://canada1.discourse-cdn.com/flex011/uploads/xrp/original/1X/7415d100b0d77f18b239e95131fc7efa4cd3d9e0.png)

---

<div class="post-metadata">

**Author:** ![Fgrossman](https://avatars.discourse-cdn.com/v4/letter/f/b77776/32.png) [@Fgrossman](https://xrp.discourse.group/u/Fgrossman)\
**Post date:** [March 18, 2025, 6:15pm UTC](https://xrp.discourse.group/t/error-after-update-shuts-down-whole-operation/642/2 "2025-03-18T18:15:24Z")

</div>

It sounds like an update problem. Here are a few things to try.

1- press the reset button on the robot. It should auto reconnect, but if it doesn’t click on connect. Try the program again.

2- if that didn’t work then do a refresh on the browser while holding the shift key to force a full refresh. It may then ask you to update. If not

3- on the XRP in lib/XRPLib delete the version.py file. Then refresh the browser and reconnect. XRPCode should then ask to update the library. Then try the program again.

You can retry the program after each step.

---

<div class="post-metadata">

**Author:** ![dwhite](https://avatars.discourse-cdn.com/v4/letter/d/82dd89/32.png) [@dwhite](https://xrp.discourse.group/u/dwhite)\
**Post date:** [March 18, 2025, 6:23pm UTC](https://xrp.discourse.group/t/error-after-update-shuts-down-whole-operation/642/3 "2025-03-18T18:23:13Z")

</div>

The option number 1 seems to be all that’s needed. Thanks.

---

<div class="post-metadata">

**Author:** ![dwhite](https://avatars.discourse-cdn.com/v4/letter/d/82dd89/32.png) [@dwhite](https://xrp.discourse.group/u/dwhite)\
**Post date:** [March 19, 2025, 5:45pm UTC](https://xrp.discourse.group/t/error-after-update-shuts-down-whole-operation/642/4 "2025-03-19T17:45:28Z")

</div>

New error. Tried all of your previously suggested fixes and they don’t work for this case. This is a one robot thing vs. all updated robots like yesterday. Please see attached.

 ![screenshot1](https://canada1.discourse-cdn.com/flex011/uploads/xrp/original/1X/9ccce8f5b3bc801e8025bffbb841ef3e3231c424.png)

---

<div class="post-metadata">

**Author:** ![SparkFro](https://yyz1.discourse-cdn.com/flex011/user_avatar/xrp.discourse.group/sparkfro/32/12_2.png) [@SparkFro](https://xrp.discourse.group/u/SparkFro)\
**Post date:** [March 21, 2025, 3:43pm UTC](https://xrp.discourse.group/t/error-after-update-shuts-down-whole-operation/642/5 "2025-03-21T15:43:43Z")

</div>

I’ve seen this happen sometimes, where the IMU gets into a weird state for some reason. I’ve usually been able to fix it by doing a full power cycle of the control board.

---

<div class="post-metadata">

**Author:** ![dwhite](https://avatars.discourse-cdn.com/v4/letter/d/82dd89/32.png) [@dwhite](https://xrp.discourse.group/u/dwhite)\
**Post date:** [March 21, 2025, 9:13pm UTC](https://xrp.discourse.group/t/error-after-update-shuts-down-whole-operation/642/6 "2025-03-21T21:13:20Z")

</div>

The middle schoolers who put that kit together seems to have done some real damage to pins in a few sockets and overall seemed to have simply been too rough while trying to assemble. Unfortunately, there are several issues with the board now. Thanks for the response.

---

<div class="post-metadata">

**Author:** ![Fgrossman](https://avatars.discourse-cdn.com/v4/letter/f/b77776/32.png) [@Fgrossman](https://xrp.discourse.group/u/Fgrossman)\
**Post date:** [March 22, 2025, 3:33am UTC](https://xrp.discourse.group/t/error-after-update-shuts-down-whole-operation/642/7 "2025-03-22T03:33:15Z")

</div>

I was going to suggest looking for bent pins. You can straighten them with good eyes, or a magnifier, and a piece of solid wire. The one of highest interest in this would be the QWIIC connector.

---

<div class="post-metadata">

**Author:** ![SparkFro](https://yyz1.discourse-cdn.com/flex011/user_avatar/xrp.discourse.group/sparkfro/32/12_2.png) [@SparkFro](https://xrp.discourse.group/u/SparkFro)\
**Post date:** [March 26, 2025, 8:49pm UTC](https://xrp.discourse.group/t/error-after-update-shuts-down-whole-operation/642/8 "2025-03-26T20:49:28Z")

</div>

FWIW I find that a pair of tweezers with thin pincers work best for bending the pins back to straight.
