Would you provide contents of the app_info.xml file? The reason I ask is that I have ordered a Odroid-C2 but am concerned about the running temp on the C2. If the temps are manageable then I can see using these as another node type to throw into the mix. I am also curious about their robotic applications.
Yes I can provide you a app_info.xml and my App-Version too. (as soon as I finished it). I've made this app for public :). Letting my brain crunch is much more efficient than setting up more and more devices. And keep's the Energy-bill low ;P.
The Odroid-C2 is a really good choice for a cruncher (Much better than all other SBC's). With a little FAN, my is so slow that you can't feel the Airstream, temperatures are below 50°C.
Using my App a RAC of ~1500 per device(4Core@einstein) should be possible.
I didn't want to get the Anker because they now boost the voltage which I suspect will upset the Pi3. There is probably only one way to find out if that is true if nobody here has them powering their Pi's.
Can you share more about this voltage boosting? USB Spec is good for up to 5.25 V. Are you referring to their IQ Power feature that makes it compatible with Qualcomm Quck Charging ( http://www.androidauthority.com/quick-charge-explained-563838/)? If so, this feature only kicks in with compatible devices.
The info I saw says they have Power IQ and Voltage Boost as they call it.
"Exclusive to Anker, PowerIQ and VoltageBoost combine to ensure the fastest possible charge speed (Qualcomm Quick Charge 2.0 not supported. For QC 2.0 charging, please see Anker's 18W USB Wall Charger)."
I might just get an Anker 60w 6 port to see what it does. The 40w non-name that I am using is quite warm. Its probably on its limit with 4 Pi3's connected. I haven't tried a 5th one. I need to buy some more USB A to Micro-USB B cables.
As for "Powerboost" power supplies: Note that even the "offical" USB PiHub (the thing that was shaped like a raspberry) used a slightly higher than 5V output as a power supply for the Pi. Can't remember how much above 5V it was, tho. I can measure it at home.
I finally managed to attach the project to my Pi 3. Thanks poppageek !
But I noticed a problem. The logfile stderrdae.txt is getting bigger and bigger. In the meantime its around 8 MB, the stderrdae.old nearly 22 MB.
It contains mostly one single message, but some 1000 times :
dir_open: Could not open directory '/dev/input/mice' from '/var/lib/boinc-client'
As I did just a normal installation using the March Version of Rasbian I think that more people could have this issue, but just do not notice.
I guess this behaviour is not directly related to Einstein but a BOINC issue.
Any ideas ?
I too noticed this when trying to figure out why I could not connect to server. Forgot about it. I will look into it as I agree it could cause problems. Thanks.
Cheers!
EDIT:
It appears that messages are written to stderrdae.txt until it reaches a certain size, from the looks of them on mine about 21megs. The file is renamed stderrdae.old and a new stderrdae.txt is created and written to. Repeat. So it looks like the size is limited. I will keep an eye on it but I do not think it's a problem.
Cheers!
Problem exists also on Odroid-C2 Ubuntu mate distro.
under Jessie I couldn't get the log file sizes to adjust. You can specify how big they can grow in cc_config but it doesn't work. Under Stretch they go to the system logs and the gpudetect files disappear into the ether.
The /dev/mice apparently is just checking the timestamp to see if any change as part of boinc's idle detection mechanism. Not much point in logging it. There was a Debian bug for it.
The Pi3 that I swapped out, re-imaged and put back into service as number 9 is running without errors but taking 14 hours a work unit. The others are taking 11:45 pretty consistently. It doesn't appear to be hot, in fact is cooler than all the others at 49 degrees C. Checking speed says it's running at 1.2Ghz so it probably really is faulty. I don't think it's the SD card but it's got a Sony branded one with the same specs as the Sandisk Ultra that I normally use.
Thanks to the efforts of N30dG and JagDoc I have joined the crunching ranks of the ODROID-C2 as an "out-of-the-box" session. It was the first time I messed with project configuration and these other members provided "the way" and N30dG answered a few of my questions to clarify procedural issues I was having. I had OS issues with the way Ubuntu handled library paths. A lot has changed in that regard since the days of LD_LIBRARY_PATH. More about that later.
RE: Would you provide
)
Yes I can provide you a app_info.xml and my App-Version too. (as soon as I finished it). I've made this app for public :). Letting my brain crunch is much more efficient than setting up more and more devices. And keep's the Energy-bill low ;P.
The App-Info.xml is posted already in this thread: https://einsteinathome.org/node/198552 by JagDoc. It's post Nr. 15.
The Odroid-C2 is a really good choice for a cruncher (Much better than all other SBC's). With a little FAN, my is so slow that you can't feel the Airstream, temperatures are below 50°C.
Using my App a RAC of ~1500 per device(4Core@einstein) should be possible.
But please be patient, I'm still working on it.
RE: RE: I didn't want to
)
The info I saw says they have Power IQ and Voltage Boost as they call it.
"Exclusive to Anker, PowerIQ and VoltageBoost combine to ensure the fastest possible charge speed (Qualcomm Quick Charge 2.0 not supported. For QC 2.0 charging, please see Anker's 18W USB Wall Charger)."
I might just get an Anker 60w 6 port to see what it does. The 40w non-name that I am using is quite warm. Its probably on its limit with 4 Pi3's connected. I haven't tried a 5th one. I need to buy some more USB A to Micro-USB B cables.
MarksRpiCluster
I have a 5 port Anker unit
)
I have a 5 port Anker unit with IQ and have no problems with it.
Bikeman - any updates on GW work for PI?
My YouTube Channel: https://www.youtube.com/user/KF7IJZ
Follow me on Twitter: https://twitter.com/KF7IJZ
Ordered an Anker 6 port 60w
)
Ordered an Anker 6 port 60w Powerport. If it doesn't work with the Pi3's then I can always use it to charge the phone :-)
MarksRpiCluster
RE: Bikeman - any updates
)
Sorry no news yet. Hopefully next week.
As for "Powerboost" power supplies: Note that even the "offical" USB PiHub (the thing that was shaped like a raspberry) used a slightly higher than 5V output as a power supply for the Pi. Can't remember how much above 5V it was, tho. I can measure it at home.
EDIT: according to this https://www.adafruit.com/products/1516 , it is 5.2 V.
HB
USB Spec allows for 5.25V at
)
USB Spec allows for 5.25V at the device.
My YouTube Channel: https://www.youtube.com/user/KF7IJZ
Follow me on Twitter: https://twitter.com/KF7IJZ
RE: RE: I finally managed
)
Problem exists also on Odroid-C2 Ubuntu mate distro.
under Jessie I couldn't get
)
under Jessie I couldn't get the log file sizes to adjust. You can specify how big they can grow in cc_config but it doesn't work. Under Stretch they go to the system logs and the gpudetect files disappear into the ether.
The /dev/mice apparently is just checking the timestamp to see if any change as part of boinc's idle detection mechanism. Not much point in logging it. There was a Debian bug for it.
MarksRpiCluster
The Pi3 that I swapped out,
)
The Pi3 that I swapped out, re-imaged and put back into service as number 9 is running without errors but taking 14 hours a work unit. The others are taking 11:45 pretty consistently. It doesn't appear to be hot, in fact is cooler than all the others at 49 degrees C. Checking speed says it's running at 1.2Ghz so it probably really is faulty. I don't think it's the SD card but it's got a Sony branded one with the same specs as the Sandisk Ultra that I normally use.
MarksRpiCluster
Thanks to the efforts of
)
Thanks to the efforts of N30dG and JagDoc I have joined the crunching ranks of the ODROID-C2 as an "out-of-the-box" session. It was the first time I messed with project configuration and these other members provided "the way" and N30dG answered a few of my questions to clarify procedural issues I was having. I had OS issues with the way Ubuntu handled library paths. A lot has changed in that regard since the days of LD_LIBRARY_PATH. More about that later.