Michael,
It may not be difficult, except for a possible issue (below):
1) Choose a name for your new system, but the name has to be a legal folder name. I'll say "ultrix3d1" for this example
2) Create a new folder in "/opt/pidp11/systems" called "ultrix3d1"
3) Copy all of the system files you need, e.g., the disk image and any others if needed, into that new folder
4) Create an appropriate "boot.ini" file in that new folder that contains the SIMH initialization script to boot your instance of Ultrix 3.1
You can look at the boot.ini scripts in the other folders under "/opt/pidp11/systems" as examples
5) Edit the file "selections" in "/opt/pidp11/systems". Choose a unique octal pattern for the left column, say 0120 as an example, and put
the folder name "ultrix3d1" in the corresponding right column. It may or may not be important for the octal patterns to be in sequential order
6) Save the "selections" file
7) Reboot the PiDP-11 with your unique octal pattern, e.g. 0120, in the switch register, your Ultrix 3.1 system should now be running
The possible issue is that your Ultrix 3.1 disk image needs to be able to run on an 11/70 CPU. The line "set cpu 11/70" in "boot.ini" sets that. If you set to any other cpu then SIMH will run but the blinkenlights on the PiDP-11/70 front panel may not work. The underlying issue is that the connection between SIMH and the PiDP-11/70 panel uses bus signal names that vary by CPU type. When the bus signal names don't match between the selected SIMH cpu type and the PiDP-11/70 then that connection fails and the front panel won't work. SIMH will run, but the blinkenlights won't appear.
Cheers,
-- steve