# AI Fusion Lab Kit and the 4-digit 7segments **URL:** \ **Category:** Learning kit for Raspberry Pi\ **Created:** [April 4, 2026, 8:27pm UTC](https://forum.sunfounder.com/t/ai-fusion-lab-kit-and-the-4-digit-7segments/4521 "2026-04-04T20:27:42Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![paks](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.sunfounder.com/paks/32/1769_2.png) [@paks](https://forum.sunfounder.com/u/paks)\ **Post date:** [April 4, 2026, 8:27pm UTC](https://forum.sunfounder.com/t/ai-fusion-lab-kit-and-the-4-digit-7segments/4521/1 "2026-04-04T20:27:42Z")
Hi! I can’t seem to get the 1.8 4-digit 7-segment display to work, I get these errors : Traceback (most recent call last): File “/home/pi/ai-lab-kit/python/1.8\_4-Digit.py”, line 7, in SDI = Pin(17,mode=Mode.OUT) # Serial Data Input ^^^^^^^^^^^^^^^^^^^^^ File “/usr/local/lib/python3.11/dist-packages/fusion\_hat/pin.py”, line 169, in **init** self.setup(mode, pull, active\_state, bounce\_time) File “/usr/local/lib/python3.11/dist-packages/fusion\_hat/pin.py”, line 207, in setup GPIO.setup(self.\_pin\_num, self.\_mode.value, pull\_up\_down=self.\_pull.value) RuntimeError: Cannot determine SOC peripheral base address I can get the circuit to work with the Pi5 only (without the Fusion Hat) So it’s not my circuit wiring that’s at fault. Has anybody got it to work with the Fusion Hat? EDIT: Is it possible that installing the neopixel library with : (sudo pip3 install adafruit-circuitpython-neopixel-spi --break) in 1.9 NeoPixel LED Strip exercise broke the dependencies, because I ran the preceding exercises and they give the same error message when using GPIO17, GPIO4’,GPIO24 etc, but when not using the GPIOs like for the servo or the RGB LED the scripts work. Another question: Can you run a script without the Fusion Hat being involved? Like just connecting the power to the Pi5 not the Hat? 2nd EDIT I just now, made another micro SD card with the Fusion Hat installation and the error message did not appear. So maybe it would be wise and professional to tell or instruct your users either to not install the neopixel library or to do it in a virtual environment. ---
**Author:** ![SunFounder\_Moderator](https://avatars.discourse-cdn.com/v4/letter/s/34f0e0/32.png) [@SunFounder\_Moderator](https://forum.sunfounder.com/u/SunFounder_Moderator)\ **Post date:** [April 7, 2026, 9:04am UTC](https://forum.sunfounder.com/t/ai-fusion-lab-kit-and-the-4-digit-7segments/4521/2 "2026-04-07T09:04:00Z")
It looks like neopixel reinstalled the old version of RPi.GPIO. We have encountered this issue before. The solution is already documented in the FAQ: > **[RPi.GPIO - FAQ — SunFounder AI Fusion Lab Kit documentation](https://docs.sunfounder.com/projects/ai-lab-kit/en/latest/faq.html#software-installation)** > > Below are some of the most common questions users may encounter while using the AI Fusion Lab Kit. If your issue is not listed here, please refer to the troubleshooting notes in each chapter or contact support. To put it simply, if you get an SOC-related error, just uninstall RPi.GPIO again. ---
**Author:** ![paks](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.sunfounder.com/paks/32/1769_2.png) [@paks](https://forum.sunfounder.com/u/paks)\ **Post date:** [April 7, 2026, 3:32pm UTC](https://forum.sunfounder.com/t/ai-fusion-lab-kit-and-the-4-digit-7segments/4521/3 "2026-04-07T15:32:13Z")
Thank you for the tip and the instructions, I’ve uninstalled the RPi.GPIO. Now my question is: is that library (RPi.GPIO) compatible with the Raspberry Pi5? I’ve been using RPi-lgpio because of that. ---
**Author:** ![SunFounder\_Moderator](https://avatars.discourse-cdn.com/v4/letter/s/34f0e0/32.png) [@SunFounder\_Moderator](https://forum.sunfounder.com/u/SunFounder_Moderator)\ **Post date:** [April 8, 2026, 7:32am UTC](https://forum.sunfounder.com/t/ai-fusion-lab-kit-and-the-4-digit-7segments/4521/4 "2026-04-08T07:32:19Z")
The RPi.GPIO library works fine for output functions on the Raspberry Pi 5, but there are issues with input functions. Of course, you can also test it yourself to see if the input issue has been resolved now. ---
**Author:** ![danman32](https://avatars.discourse-cdn.com/v4/letter/d/34f0e0/32.png) [@danman32](https://forum.sunfounder.com/u/danman32)\ **Post date:** [May 9, 2026, 2:34pm UTC](https://forum.sunfounder.com/t/ai-fusion-lab-kit-and-the-4-digit-7segments/4521/5 "2026-05-09T14:34:13Z")
Did you mean to say RPi.GPIO works fine for input functions rather than it works for output functions? Because it clearly breaks GPIO output functions when on a Pi 5, as OP has demonstrated here. ---
**Author:** ![SunFounder\_Moderator](https://avatars.discourse-cdn.com/v4/letter/s/34f0e0/32.png) [@SunFounder\_Moderator](https://forum.sunfounder.com/u/SunFounder_Moderator)\ **Post date:** [May 11, 2026, 10:20am UTC](https://forum.sunfounder.com/t/ai-fusion-lab-kit-and-the-4-digit-7segments/4521/6 "2026-05-11T10:20:41Z")
Yes, RPi.GPIO conflicts with the Raspberry Pi 5. However, since the Raspberry Pi OS and many libraries still retain compatibility with RPi.GPIO, it usually needs to be manually uninstalled. ---
**Author:** ![danman32](https://avatars.discourse-cdn.com/v4/letter/d/34f0e0/32.png) [@danman32](https://forum.sunfounder.com/u/danman32)\ **Post date:** [May 17, 2026, 6:09pm UTC](https://forum.sunfounder.com/t/ai-fusion-lab-kit-and-the-4-digit-7segments/4521/7 "2026-05-17T18:09:14Z")
What I was pointing out was that you said RPi.GPIO works fine for output functions, yet OP was saying he was having problems with output, not input, which you replied to uninstall RPi.GPIO Thus it seems you meant to say that input functions work with RPi.GPIO as OP and I had issues with GPIO output.on RP 5. ---
**Author:** ![SunFounder\_Moderator](https://avatars.discourse-cdn.com/v4/letter/s/34f0e0/32.png) [@SunFounder\_Moderator](https://forum.sunfounder.com/u/SunFounder_Moderator)\ **Post date:** [May 19, 2026, 1:22am UTC](https://forum.sunfounder.com/t/ai-fusion-lab-kit-and-the-4-digit-7segments/4521/8 "2026-05-19T01:22:47Z")
It seems there was a small misunderstanding on my part. To be more precise, the conflict occurs when using the Pin() class – in both libraries, it supports both input and output functions. (The reason I encountered it first during my troubleshooting was when using the input function.)