Ah.. been there done that. But you’re there now. Good luck!
1 Like
Alrighty! New card! A bit of fighting with RAM and compilation steps aaaaand.
(.venv) pidog@raspberrypi:~/examples $ python3 pidog_programming_examples.py
PiDog Programming Examples — choose an option:
- Quick runtime demo
- Autonomy personality demo
- Micro-idle demo
- Autonomy cycle demo
- Scripted habituation demo
- Energy demo
- Scripted stimuli demo
a) Run all examples sequentially
q) Quit
Select an option: 1
— Quick runtime demo —
Running: Quick Runtime Demo (50 cycles)
config_file: /home/pidog/.config/pidog/pidog.conf
robot_hat init … done
imu_sh3001 init … done
rgb_strip init … done
dual_touch init … done
sound_direction init … done
sound_effect init … fail
ultrasonic init … done
Orientation calibration failed: no samples
Watchdog recovery: sensor_stale=True scan_stale=True stale_modules=[‘hal_sensors’, ‘hal_motors’, ‘calibration’, ‘health’, ‘watchdog’, ‘balance’, ‘safety’, ‘energy_emotion’, ‘vision’, ‘vision_pi4’, ‘voice’, ‘face_recognition’, ‘semantic_labeler’, ‘slam_pi4’, ‘telemetry_dashboard’] mode=behavior restarts=
Watchdog recovery: sensor_stale=True scan_stale=False stale_modules=[‘hal_sensors’, ‘hal_motors’, ‘calibration’, ‘health’, ‘balance’, ‘safety’, ‘energy_emotion’, ‘vision’, ‘vision_pi4’, ‘voice’, ‘face_recognition’, ‘semantic_labeler’, ‘slam_pi4’, ‘telemetry_dashboard’] mode=behavior restarts=
PiDog Programming Examples — choose an option:
- Quick runtime demo
- Autonomy personality demo
- Micro-idle demo
- Autonomy cycle demo
- Scripted habituation demo
- Energy demo
- Scripted stimuli demo
a) Run all examples sequentially
q) Quit
Select an option:
running the example script the dog just moves its head left and right as if trying to scan and drops back to menu.
Running the HoundMind_AI main script, he stands up moves his head and quits.
Am I missing something?
(Also sound_effect error even though I have ran i2samp.sh many times.)
EDIT: Found the settings json. Enabled the defaults. He now stands up, moves around but still sound_effect fail and doesn’t seem to respond to sounds. Also log files say that the picam2 module is not found. I installed FLAC as the logs complained about it but no change. All of these modules work when running sunfounder examples.
OK, nuked my venv and started again. This time specifying Python 3.10.16 and adding –system-site-packages flag to the venv, as I think the camera module is now baked into the OS and wont install via pip anymore? Running the full installation again. Fingers crossed.
Sounds like your making good progress.
I have my Pidog/Pi5 up and running 100% per Sunfounder instruction’s.
Now trying to use HoundMind and I am completely overwhelmed maybe you guys can help an old guy ouy?
I do not understand the 7lynx houndmind installation. No Python knowledge, I follow instructions very well. but these are confusing
environments? keep everything in same evir. what and how??
automated installer?? where is that? how to use it??
I do not see when you download the .git houndmind actual files/repository too get to the installer?
I never see any Pidog stuff loaded, i thought this would load automatically with installer
NOW I have tried MANY times in various ways to do this and the Pi has spent a lot of time loading a bunch of stuff, I tried git clone houndmind repository then a “bash scripts/install_houndmind.sh” this loaded lot of stuff, but nothing woked.
anybody help with more specific instructions??
thanks
Mike
A virtual environment (venv) can be seen as a container that isolates a specific version of Python from the rest of the system keeping all packages and runtimes separate.
By automated installer the guide is describing the *.sh file (Bash script) which automatically installs all the packages (and in some cases compiles from source) needed for the Houndmind project to run.
I guess some basic knowledge of how Linux runs is required to fully follow the guide and even I am a little lost as to how some things work. Like where is the launch script “houndmind_ai” located? $PATH gets very complex when dealing with venv.
All I can say is that if you hit a step in the guide that doesnt make sense, pause, google, and once you have a good grasp, continue.
Good luck, I still have no Camera, Mic or Speaker on my Pidog using this project but he walks around and has basic automation that is more complex than the sunfounder scripts.
Thanks for that info.
With a clean bookworm install, when and how do you D/L the houndmind repository, (i assume this must be done before the install.sh script?) maybe “git clone address” but then there is that “venv” to figure out??
When and how do you download all the Pidog/tophat stuff?? There used to be a menu?
I have tried walking thru the install, but never see any files etc. for Pidog stuff?
When i last ran the .SH script, there was alot loaded and it took a long time, but at the very end it said install failed.
I hope someone does a U-tube vid on this…
You have 2 options to download the Houndmind project, either you can git clone the project (needs a bit of git knowledge) or just create a houndmind folder in your home directory and download the project as a zip file and extract into the folder.
As for the Pidog runtimes, they are installed as part of the houndmind.sh script.
Finally, the venv instructions are in the “install.md” document in the docs folder of the project.
Good luck!