The **Correct** way to create/update a GoPiGo-3 installation?

Ref:  The following:

I note that all of this is done as the standard user.

Shouldn’t this be done as root as it installs stuff all over the place?


After installing the sensors packages, I get the following:

Removing "di_sensors" and "line_follower" to make space for new ones
running install
running bdist_egg
running egg_info
creating DI_Sensors.egg-info
writing requirements to DI_Sensors.egg-info/requires.txt
writing DI_Sensors.egg-info/PKG-INFO
writing top-level names to DI_Sensors.egg-info/top_level.txt
writing dependency_links to DI_Sensors.egg-info/dependency_links.txt
writing manifest file 'DI_Sensors.egg-info/SOURCES.txt'
reading manifest file 'DI_Sensors.egg-info/SOURCES.txt'
writing manifest file 'DI_Sensors.egg-info/SOURCES.txt'
installing library code to build/bdist.linux-armv7l/egg
running install_lib
running build_py

[. . . lots of stuff . . .]

Using /usr/local/lib/python3.7/dist-packages/python_periphery-2.3.0-py3.7.egg
Finished processing dependencies for Line-Follower==1.0.0
Configuring the red line follower in DI_Sensors installation
Done configuring the red line follower in DI_Sensors installation

The red line follower was depreciated centuries ago, how do I get the black line follower back?

1 Like

Also note that, when I do this over legacy Buster, the antenna LED is purple.

I have not tried this on any other versions yet.

1 Like

It appears to me that this is not an either/or - the regular line follower is installed as and the red line follower as red_line_follower/


Just checked my Legacy PiOS (12/24/2021 version) and indeed the LED is purple when WiFi connected. The comments say “yellow-orangey” but the color is coded as (3,1,3).

pi@PIOSLGCY:~/Dexter/GoPiGo3/Install $ more 
# 1 Detect if we are on a GoPiGo3
# 2 Detect if we have Wifi connection
# 3 Throw a yellow-orangey LED or turn it off

# If detected_robot exists and it contains GoPiGo3, or 
# if it doesn't exist at all on standalone Raspbian
if [ -f "/home/pi/Dexter/detected_robot.txt" ] && grep -q GoPiGo3 /home/pi/Dexter/detected_robot.txt  || [  ! -f "/home/pi/Dexter/detected_robot.txt" ]
    if iwgetid --scheme
        python -c "import gopigo3;GPG=gopigo3.GoPiGo3();GPG.set_led(GPG.LED_WIFI,3,1,3)"
        python -c "import gopigo3;GPG=gopigo3.GoPiGo3();GPG.set_led(GPG.LED_WIFI,1,0,0)"


Note: the following is not needed when updating GoPiGo3 software installed over Legacy PiOS, only during original Legacy PiOS setup. The title of this thread has the word “create” in it. I didn’t document originally in that prior thread, when first setting up Legacy PiOS - New issue with Legacy PiOS - getting sound to work. The default is pulseaudio and HDMI so:

=== First see if audio output works the way you want (auto) ===
Test audio out:
    aplay /usr/share/sounds/alsa/Front_Center.wav

If not:

$ sudo apt purge pulseaudio
$ sudo apt autoremove

$ nano /home/pi/.asoundrc

pcm.!default {
  type asym
  playback.pcm {
    type plug
    slave.pcm "output"
  capture.pcm {
    type plug
    slave.pcm "mic"

pcm.output {
	type hw
	card 1

ctl.!default {
	type hw
	card 1

pcm.mic {
  type plug
  slave {
    pcm "hw:2,0"

ctrl-x, y to save it
$ reboot
  • Now audio will come out the headphones, and
  • If you plug in a USB audio interface you can use a microphone.

Retest with:

$ aplay /usr/share/sounds/alsa/Front_Center.wav
$ espeak "hello"

This is by design:  “The default is pulseaudio and HDMI.”

That’s an issue if, and only if, you want analog output via the headphone jack.

Then there are strange people like me who are perfectly happy with HDMI sound - at least for the time being.&nbsp: (Maybe I’ll get a speaker module when I get back to the States.  :wink:)


Robots have a lot to say if we let them! Forget the speaker module - add the Raspberry Pi Speaker Kit


Right now Charlie hasn’t been all that upset about not having a speaker module - he’s busy having fun with his SSD, e-Paper display and 5v boost supply.