Looking at Hals Thread it appears he found some solder on UBS connectors to adapt to his 5V power supply. My searching wasn't a success, but did find a bunch of 12V to 5V UBS adaptors for automotive hard wiring ... would need a 12V supply, and not as neat.

Looking at Hals Thread it appears he found some solder on UBS connectors to adapt to his 5V power supply. My searching wasn't a success, but did find a bunch of 12V to 5V UBS adaptors for automotive hard wiring ... would need a 12V supply, and not as neat.

Hi Brent,

Thanks for the link. I have been trying to find the 6-32 x 1/4" standoffs, but all I could find were motherboard standoffs. Male thread is not 6-32.

I saw in one of the photos on Hals thread that he had a standoff kit like the ones I have seen on Amazon. So, I ordered 2 of them and a 2 pack of 32GB MicroSD cards for my 2 new Pis. Should be here next week. That takes care of the build part. The power part is still on going. For the time being I'm going with the power strip. Although I worked for a company, back in the 80s, designing printed circuit boards, I don't have the knowledge to do whatever Hal did on his Pi. But, I am able to do the Micro USB connectors on the power supply route. I do know which 2 pins are 5V and GRD on the Micro USB connector. That will have to be a future project for now.

Thanks again and have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Greetings,

Well, it wasn't quite as bad as I thought it would be. I got 2 new receptacles, a weather proof cover for the outside outlet and a 3 to 2 prong adapter. Should've just forgot about the adapter. Didn't use it.

The person that had this house before us painted over the face plate. The outlet itself has been painted over a few times. I saw at least 2 different colors. I replaced the outlet, cursing all the way. Screw slots with paint in them suck! There's power to the power strip and my cell can continue getting charged from there. One little problem... There is no ground wire to the outlet. A project for another day perhaps.

Kinda feels good to do the job the right way instead of using a crutch to accomplish the same goal. :) .oO(Your old body would beg to differ on that count though.) lol ;)

On to the next. Have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

It sounds like the original brick uses much bigger cables with larger wire gauges to supply the 2.5A.

It does, might be 20 G.

Not typical with almost all aftermarket USB cables. Best to continue to use the provided brick power supply with each Pi and power them off the power strip. Use the 2 prong to 3 prong adapter or go the hardware store and get a proper 3 prong outlet and install it.

Have a 7 port powered hub that has two ports that it calls for charging devices. IIRC 1.5A on each, 500mA on the others.
Some of us remember pocket drives that had funny double cables to get enough power.

You might also look at https://en.wikipedia.org/wiki/Power_over_Ethernet
https://www.raspberrypi.org/products/poe-hat/

Some of us remember pocket drives that had funny double cables to get enough power.

I still do. A micro USB cable plus a fullsize USB-A cable to get enough power for the 2.5" pocket drive case.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Greetings,

I finally got my 2 MicroSD cards. I formatted them and copied the NOOBS files to each of them for installation of Raspbian. I'll have to do that tomorrow. Then get BOINC installed and running SETI.

Tomorrow I'll have Rasbpi-1, Rasbpi-2 and Rasbpi-3 running SETI.

Have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

I ran across This which may work for a power option.

---

I ran across This which may work for a power option.

Hi Brent,

Sorry, but I won't buy off eBay for any reason. I've seen and heard too many people getting shafted buying from there. I don't want the headache of dealing with eBay because I didn't get something I paid for or got something different than what it was listed as. Someone here just recently got a video card that was listed as one thing, but they found out it was something different, it was less than what it was supposed to be listed as.

I've been thinking of getting another UPS and just plugging the Pis bricks into it. Won't have to worry about a power outage that way too. Heck, I have our routers and cable modem powered from a UPS, I should do no different for my Pis. :)

Have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Greetings,

Here's the dilemma: I can access my first Pi through my main by starting a new second BOINC Manager window and logging into it with the IP address and password. With my second Pi, I cannot.

I have installed Raspbian and BOINC. I did the name changes. All is well with Rasbpi-2. The only difference between Rasbpi-2 and Rasbpi-1 is that I was able to attach to SETI through BOINC Manager on Rasbpi-2. I could not with Rasbpi-1; I had to use BOINC Manager from my main to attach for Rasbpi-1.

On Rasbpi-1 I don't run BOINC Manager at all. It doesn't seem to have control of the WUs and shutting down the apps. When I start a 3rd BOINC Manager window for Rasbpi-2 and try to connect (login), it goes through connecting, disconnecting, connecting, disconnecting, etc., etc...

Any ideas and suggestions would be greatly appreciated. :)

Have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Greetings,

Ok! That issue I spouted about earlier, is no longer an issue. I can remotely access both new Pis with Windows Remote Desktop Connection. Actually, I like it better because it eliminates swapping my mouse/keyboard USB dongle and HDMI cable around on each Pi. I can start BOINC Manager that way and deal with stuff, you know, monitoring and stuff like that. ;)

So, I need to figure out what to do about my first Pi. I cannot access BOINC Manager from Remote Desktop Connection. If I shut down the Manager on my main and remote into Rasbpi-1 and start BOINC manager there it then comes up and is trying to retrieve information. Then I get the message: "Unable to connect to the core client." Remember, I used a second BOINC Manager window on my main to get Pi 1 to attach to SETI. I did not do that with my 2 new Pis. My second one I used the manager in the HDMI window using the keyboard and mouse on the Pi. My third one I did through Remote Desktop Connection with the mains keyboard and mouse.

I would like all 3 to do like the 2 new ones. Any Gurus out here that can help me get my first Pi like my 2 new ones? Any help would be greatly appreciated. :)

Have a great day! :)

Siran

[edit]
One thing I forgot to mention. I cannot shut down the apps doing the work. I get the popup that asks me if I want to, I click yes or whatever and they don't shut down. I can do that with my 2 new Pis through remote access.
[/edit]

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Haven't tried RDC to connect, use VNC but it should be the same.
If you can't launch the manager on the one PI it may well be the way you launched it the first time. A reboot of the PI may clear that up. Or you might have to edit the config file that launches BOINC (not manager) to make it look for a local desktop manager. See BOINC Wiki.
If you can't reach that PI with RDC that is a different problem.

Haven't tried RDC to connect, use VNC but it should be the same.
If you can't launch the manager on the one PI it may well be the way you launched it the first time. A reboot of the PI may clear that up. Or you might have to edit the config file that launches BOINC (not manager) to make it look for a local desktop manager. See BOINC Wiki.
If you can't reach that PI with RDC that is a different problem.

Hi Gary,

I can access the Pi with RDC. That isn't the problem. I cannot get BOINC Manager to connect to the client. In doing a bunch of research on this I found out that BOINC Manager on Windows will start the client, BM on Linux will not. The client has to be started first. What has me puzzled is that the client is already running when I try BM. It keeps telling me it cannot connect to the core client.

I'm thinking that there is a config file or whatever that may be preventing the BOINC Manager from connecting with the client and only allowing the remote BOINC Manager to connect from my PC. I have no clue about that though. I can get BOINC Manager on my Windows PC to connect no problem. That's how I'm currently monitoring things. My other concern is that I have no way to shut down the apps and the client unless I do it in the terminal window with commands. That's kind of a PITA way of doing it though; I shouldn't have to do it that way since I installed the GUI version.

BTW, I have re-booted the Pi several times and nothing changes. If I cannot get this worked out the only other recourse I can see to do would be to detach from SETI, after the WUs are drained, and re-attach the way I did it with my third Pi, through RDC. As I mentioned yesterday, I want to eliminate the mouse/keyboard USB dongle and HDMI cable swap between the Pis. Actually, I don't have to do that now.

Thanks for the ideas, Gary, and have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

If you are using the Repository version of BOINC, it will NOT restart since it is started as a service on boot up. /etc/init.d/boinc-client
Closing the Manager Window will stop it, but it won't restart by opening it.

To get it to start again after a shutdown ... sudo /etc/init.d/boinc-client <start/stop/restart>

---

Greetings,

Ok, I don't know that I'm one step closer to figuring out how to access my first Pi like my other 2 or not. But, this is what I have found, so far, that is different between Pi 1 and the other 2. The "xxx" on the IP addresses is for security. I'm not sure if they can be access from outside or not.

My 2 Pis that work the way I want them to have a "remote_hosts.cfg" file that reads as follows:

# This file contains a list of hostnames or IP addresses (one per line)
# of remote hosts, that are allowed to connect and to control the local
# BOINC core client via GUI RPCs.
# Lines beginning with a # or a ; are treated like comments and will be
# ignored.
#
#host.example.com
#192.168.0.xxx

My first Pis "remote_hosts.cfg" file reads as follows:

# This file contains a list of hostnames or IP addresses (one per line)
# of remote hosts, that are allowed to connect and to control the local
# BOINC core client via GUI RPCs.
# Lines beginning with a # or a ; are treated like comments and will be
# ignored.
#
#host.example.com
#192.168.0.xxx
192.198.0.xxx

In the second list, the un-commented IP address is my main IP. I assume that this allows my main to access my first Pi with BOINC Manager. Would I be correct in that assumption?

I also assume that this has nothing to do with my getting BOINC Manager to connect to the boinc client through RDC. Would this also be a correct assumption?

I really need to have some Linux Gurus chime in here since I am a newbie with Linux regardless of playing with it, off and on, for the past almost 20 years.

Have a great day! :)

Siran

[edit]
One thing I forgot to mention is that I tried to access my other 2 Pis the way I do with my first, running a second BOINC Manager window and logging into the Pis. I cannot do the with my second 2 Pis, only my first one. I assume that this would be about the "remote_hosts.cfg" being without my mains IP address.
[/edit]

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

192.198 ??

---

The remote_hosts.cfg file usually contains the IP address of the main BOINC machine you want to use as the controller of the farm. Also there is another file that is involved with remote procedure calls by the host control computer. The gui_rpc_auth.cfg file contains the password that is used by the client to authenticate the Manager connecting to it. Easiest thing is to change it on all the hosts from the randomly generated password to a simpler password of your own choice.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

192.198 ??

Doh! 192.168...

My bad. :)

Have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

The remote_hosts.cfg file usually contains the IP address of the main BOINC machine you want to use as the controller of the farm. Also there is another file that is involved with remote procedure calls by the host control computer. The gui_rpc_auth.cfg file contains the password that is used by the client to authenticate the Manager connecting to it. Easiest thing is to change it on all the hosts from the randomly generated password to a simpler password of your own choice.

Hi Keith,

The 2 Pis that are working the way I want, where I do everything in RDC in Windows, do not have my main's IP address in remote_hosts.cfg. What I'll do with my first Pi, that does have the IP, is comment it out and see if I can connect with BOINC Manager from my main. I cannot connect to the 2 Pis that don't have the IP. I don't think I will make the connection just as the other 2 Pis cannot.

I don't have a problem logging into any of my Pis with RDC. The problem is that when logged into my first Pi I cannot get BOINC Manager to connect to the BOINC client. Which is why I have been doing it from my main. The other 2 Pis I can connect and control BOINC through the manager in RDC. I cannot shut down the apps running on the first Pi unless I use a couple command lines in terminal. If the passwords are different between my first Pi and the other 2, that may be the ticket. I'll check them and change them now and get back to you.

Have a great day! :)

Siran

[edit]
Here's a question: the files are in 2 locations, one in /var/lib/boinc-client (with an arrow) and the other in /etc/boinc-client (without the arrow). Do I change both locations?
[/edit]

[edit2]
Editing those text files cannot be done, at least not in the way I was trying using a GUI text editor. They tell me the file cannot be opened for write. :(
[/edit2]

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

For remote client connections you will want this in cc_config.
<allow_remote_gui_rpc>1</allow_remote_gui_rpc>
Along with:
gui_rpc_auth.cfg
remote_hosts.cfg

The arrow on the file means the file 'lives' in a different location. A Shortcut in Windows, a symbolic link in Unix.
So /etc/boinc-client is where the file is.

Try ... sudo gedit /etc/boinc-client/remote_hosts.cfg
I'm not sure if gedit is the Pi text editor though ...

There is always the Repository work around to edit files ... for a short time until BOINC locks it's privileges again.
sudo chmod -R 0777 /var/lib/boinc-client ... might need /* on that.
That makes all the files 'world' writable/editable to everyone :)

---

Greetings,

Ok, I figured out how to edit those files. I used the terminal and used "sudo nano...". I commented the IP address in remote_hosts.cfg and BOINC Manager, on my main, would no longer connect. I tried BOINC Manager in RDC and still got the same thing, "Cannot connect to the core client". I un-commented the IP address and BOINC Manager on my main connected again.

I'm seeing only one option here: I'm thinking I should do a NNT and then detach from SETI when the WUs finish or perhaps even uninstall and reinstall BOINC. Then reattach with the BOINC Manager in RDC. What say you?

Have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath