# Error running installation\_verification.py program **URL:** \ **Category:** Support\ **Created:** [May 25, 2024, 1:50pm UTC](https://xrp.discourse.group/t/error-running-installation-verification-py-program/360 "2024-05-25T13:50:44Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![BlueEpiphone](https://avatars.discourse-cdn.com/v4/letter/b/f05b48/32.png) [@BlueEpiphone](https://xrp.discourse.group/u/BlueEpiphone)\ **Post date:** [May 25, 2024, 1:50pm UTC](https://xrp.discourse.group/t/error-running-installation-verification-py-program/360/1 "2024-05-25T13:50:44Z")
After following the video instructions, I am unable to run the verification program through [https://xrpcode.wpi.edu/](https://xrpcode.wpi.edu/). It updated the python code and firmware. I can turn on the robot and see 2 red lights, but I do not see the green LED flashing, any longer. Thanks for any help I get the following error when running my installation\_verification.py program. > > > Traceback (most recent call last): File “”, line 5, in File “XRPExamples/installation\_verification.py”, line 1, in File “/lib/XRPLib/defaults.py”, line 19, in File “/lib/XRPLib/imu.py”, line 26, in get\_default\_imu File “/lib/XRPLib/imu.py”, line 59, in **init** File “/lib/XRPLib/imu.py”, line 155, in is\_connected File “/lib/XRPLib/imu.py”, line 106, in \_getreg OSError: [Errno 110] ETIMEDOUT ---
**Author:** ![BlueEpiphone](https://avatars.discourse-cdn.com/v4/letter/b/f05b48/32.png) [@BlueEpiphone](https://xrp.discourse.group/u/BlueEpiphone)\ **Post date:** [May 25, 2024, 6:03pm UTC](https://xrp.discourse.group/t/error-running-installation-verification-py-program/360/2 "2024-05-25T18:03:14Z")
OK, I resolved this issue myself. Turns out I had plugged in the range-finder in to the wrong port and that made it so that the IMU on the I2C port didn’t respond. The port I plugged into was the Qwiic port, which is part of the I2C bus, most likely, which probably interfered with the IMU as well. Here is how I diagnosed the issue. I discovered this response to a similar issue. [ERROR reading in XRPLib.defaults - #2 by SparkFro](https://xrp.discourse.group/t/error-reading-in-xrplib-defaults/155/2) When I follow the procedure to comment out the IMU and the drivetrain, I was able to cycle through the tests until I get to the drivetrain test. The range sensor test also failed with this output: Range Distance: 65535.0 Press user button to test servo I followed the instructions in this post to do an I2C scan and got back a null array. > [@(Where) is Qwiic demo code available (such as from the webinar)?](https://xrp.discourse.group/t/where-is-qwiic-demo-code-available-such-as-from-the-webinar/101/6): > > For those who want to dive into using Qwiic devices right now, here’s a quick set of instructions that should get you up and running. This is along the lines of how we’re planning to implement it in the next software release (subject to change), except the installation process should be automated once finalized. Please understand that if you choose to do this before the next software release, some things may not work and there will be limited support. Add Qwiic\_I2C\_Py Driver In [XRPCode](https://xrpcode.wpi.edu/), connec… My result > > > import qwiic\_i2c > > > i2cDriver = qwiic\_i2c.getI2CDriver() > > > i2cDriver.scan() So, the range-sensor failure clued me into the plug being wrong and once corrected, I was able to complete the initialization test and get a [107] response from the i2c scan. ---
**Author:** ![SCSpaeth](https://yyz1.discourse-cdn.com/flex011/user_avatar/xrp.discourse.group/scspaeth/32/90_2.png) [@SCSpaeth](https://xrp.discourse.group/u/SCSpaeth)\ **Post date:** [May 26, 2024, 6:19pm UTC](https://xrp.discourse.group/t/error-running-installation-verification-py-program/360/3 "2024-05-26T18:19:21Z")
Thanks for documenting your problem solving strategy and experience! It’s both informative and inspiring to see the process.