TJMProject administrator
Project developer
Project tester
Send message
Joined: 16 Apr 11
Posts: 291
Credit: 1,382,252
RAC: 68
We have just added application/platform for Raspberry Pi running Raspbian and possibly any of the other OSes available for it (not verified yet). In theory the app should run on anything that reports armv6l-linux-gnueabihf or arm-linux-gnueabihf platform (if it does not, or if you have armv6l device which reports another platform-string, please let me know).
Unfortunately I have no idea how to set the udev on Raspbian to allow access to the sensor for users other than root, the standard trick described here http://radioactiveathome.org/boinc/forum_thread.php?id=46 doesn't work, perhaps someone else will find a solution.
I did all the tests as root and the app seems to work just fine.
EDIT: To allow access to the sensor as non-root (this also applies to default "pi" user on raspbian) the .rules file has to contain this:
#r@h
ATTR{idVendor}=="16c0", MODE="666", GROUP="plugdev"
LABEL="radioactive_rules_end"
it looks like the syntax has been changed.
EDIT:
The Vendor ID above is only for sensors up to v3.0.
3.01 uses new vendor id which is "04d8".
/ 
Reply
Quote
We have just added application/platform for Raspberry Pi running Raspbian and possibly any of the other OSes available for it (not verified yet). In theory the app should run on anything that reports armv6l-linux-gnueabihf or arm-linux-gnueabihf platform (if it does not, or if you have armv6l device which reports another platform-string, please let me know).
I've just try to attach the project from a Raspberry running the image build for QCN project ( http://qcn.stanford.edu/sensor/forum_thread.php?id=880 ) and got this error message:
Message from server: This project doesn't support computers of type armv6l-unknown-linux-gnueabihf
/ Reply
Quote
TJMProject administrator
Project developer
Project tester
Send message
Joined: 16 Apr 11
Posts: 291
Credit: 1,382,252
RAC: 68
Try running one of these apps as standalone, to see if they work.
/ Reply
Quote
We have just added application/platform for Raspberry Pi running Raspbian and possibly any of the other OSes available for it (not verified yet). In theory the app should run on anything that reports armv6l-linux-gnueabihf or arm-linux-gnueabihf platform (if it does not, or if you have armv6l device which reports another platform-string, please let me know).
Unfortunately I have no idea how to set the udev on Raspbian to allow access to the sensor for users other than root, the standard trick described here http://radioactiveathome.org/boinc/forum_thread.php?id=46 doesn't work, perhaps someone else will find a solution.
I did all the tests as root and the app seems to work just fine.
It works. My RaspberryPi finished his first WU.
http://radioactiveathome.org/boinc/result.php?resultid=1318173
I tried it with your "standart trick" but dont work.
I changed in the file 53-rdioactive.rules:
#r@h
ATTRS{idVendor}=="16c0", MODE="666", GROUP="plugdev"
LABEL="radioactive_rules_end"
the sensor was found and work fine.
cu JagDoc
/ Reply
Quote
Try running one of these apps as standalone, to see if they work.
Sorry, may be I missed a step, because perform an update no WU is downloaded and continue to see this message:
02/01/2013 00:30:49 | Radioactive@Home | update requested by user
02/01/2013 00:30:50 | Radioactive@Home | Sending scheduler request: Requested by user.
02/01/2013 00:30:50 | Radioactive@Home | Requesting new tasks for CPU
02/01/2013 00:30:52 | Radioactive@Home | Scheduler request completed: got 0 new tasks
02/01/2013 00:30:52 | Radioactive@Home | Message from server: This project doesn't support computers of type armv6l-unknown-linux-gnueabihf
I've copied the exe in the correct directory and performed the steps about the 53-rdioactive.rules file. So I see this files:
total 856
-rw-r--r-- 1 pi pi 2890 Jan 1 23:05 sensors.xml
-rwxr-xr-x 1 pi pi 861184 Jan 1 23:05 radac_1.69_armv6l-unknown-linux-gnueabihf
-rw-r--r-- 1 pi pi 0 Jan 1 23:51 boinc_lockfile
-rw-r--r-- 1 pi pi 1694 Jan 2 00:30 stderr.txt
-rw-r--r-- 1 pi pi 135 Jan 2 00:30 data.bin
Notice running manually radac the sensor after create the 53-rdioactive.rules file the sensor seems works:
Warning: cannot query manufacturer for device: error sending control message: Operation not permitted
Could not find any of the devices listed in sensors.xml: Device communication error
Warning: cannot query manufacturer for device: error sending control message: Operation not permitted
Warning: cannot query manufacturer for device: error sending control message: Operation not permitted
Warning: cannot query manufacturer for device: error sending control message: Operation not permitted
Warning: cannot query manufacturer for device: error sending control message: Operation not permitted
00:28:56 (2029): Can't open init data file - running in standalone mode
Radac $Rev: 496 $ starting...
sensors.xml: 6 nodes found
Found sensor v2.51
604142,201,2013-1-1 23:28:56,593,f,381683167
650622,221,2013-1-1 23:29:42,593,n,381683167
697102,236,2013-1-1 23:30:29,593,n,381683167
Must I create also a app_info.xml file ?
/ Reply
Quote
Try running one of these apps as standalone, to see if they work.
I've copied the exe in the correct directory and performed the steps about the 53-rdioactive.rules file. So I see this files:
It must be 53-radioactive.rules
cu JagDoc[/b]
/ Reply
Quote
TJMProject administrator
Project developer
Project tester
Send message
Joined: 16 Apr 11
Posts: 291
Credit: 1,382,252
RAC: 68
Detach from the project, reattach and check again. I've just added support for Debian running on Pi.
I don't know why the platform string differs, however the executable is the same as Raspbian one and it seems to be working.
/ Reply
Quote
Detach from the project, reattach and check again. I've just added support for Debian running on Pi.
I don't know why the platform string differs, however the executable is the same as Raspbian one and it seems to be working.
Mumble, continue got the same error:
raspberrypi Radioactive@Home 02/01/2013 19.36.15 Detaching from project
raspberrypi http://radioactiveathome.org/boinc/ 02/01/2013 19.40.54 Master file download succeeded
raspberrypi http://radioactiveathome.org/boinc/ 02/01/2013 19.40.59 Sending scheduler request: Project initialization.
raspberrypi http://radioactiveathome.org/boinc/ 02/01/2013 19.40.59 Requesting new tasks for CPU
raspberrypi Radioactive@Home 02/01/2013 19.41.00 Scheduler request completed: got 0 new tasks
raspberrypi Radioactive@Home 02/01/2013 19.41.00 Message from server: This project doesn't support computers of type armv6l-unknown-linux-gnueabihf
/ Reply
Quote
TJMProject administrator
Project developer
Project tester
Send message
Joined: 16 Apr 11
Posts: 291
Credit: 1,382,252
RAC: 68
Please try again, perhaps I forgot to restart feeder/scheduler after making changes.
If it still won't work, I'll test it on Pi myself tomorrow.
/ Reply
Quote
Please try again, perhaps I forgot to restart feeder/scheduler after making changes.
If it still won't work, I'll test it on Pi myself tomorrow.
Ok, thanks, now BOINC download and run the client but got another error:
raspberrypi Radioactive@Home 02/01/2013 21.23.57 Scheduler request completed: got 1 new tasks
raspberrypi Radioactive@Home 02/01/2013 21.23.59 Starting task sample_1316107_0 using radac version 170 in slot 1
raspberrypi Radioactive@Home 02/01/2013 21.24.03 Computation for task sample_1316107_0 finished
raspberrypi Radioactive@Home 02/01/2013 21.24.03 Output file sample_1316107_0_0 for task sample_1316107_0 absent
/ Reply
Quote
TJMProject administrator
Project developer
Project tester
Send message
Joined: 16 Apr 11
Posts: 291
Credit: 1,382,252
RAC: 68
Which host ID is this ? Your hosts are hidden.
/ Reply
Quote
Which host ID is this ? Your hosts are hidden.
This:
http://radioactiveathome.org/boinc/show_host_detail.php?hostid=5494
/ Reply
Quote
Try running one of these apps as standalone, to see if they work.
I've copied the exe in the correct directory and performed the steps about the 53-rdioactive.rules file. So I see this files:
It must be 53-radioactive.rules
cu JagDoc[/b]
Thanks, I renamed the file but got the same error.
/ Reply
Quote
TJMProject administrator
Project developer
Project tester
Send message
Joined: 16 Apr 11
Posts: 291
Credit: 1,382,252
RAC: 68
Could you check what is inside radioactiveathome folder in the BOINC data dir, and what's inside the slot ? It looks like the app is unable to find sensors.xml, which is required.
EDIT: nvm, I've just noticed I made a mistake in the file name, fixing it right now.
/ Reply
Quote
Could you check what is inside radioactiveathome folder in the BOINC data dir, and what's inside the slot ? It looks like the app is unable to find sensors.xml, which is required.
EDIT: nvm, I've just noticed I made a mistake in the file name, fixing it right now.
total 864
drwxrwx--x 4 pi pi 4096 Jan 2 21:06 ..
-rw-r--r-- 1 pi pi 2890 Jan 2 21:06 sensors_raspberry_1.70.xml
-rw-r--r-- 1 pi pi 13 Jan 2 21:06 sensors_raspberry_1.70.xml.file_ref_inf
-rwxr-xr-x 1 pi pi 861184 Jan 2 21:06 radac_1.70_armv6l-unknown-linux-gnueabihf
-rw-r--r-- 1 pi pi 180 Jan 2 22:04 stderr.txt
drwxrwx--x 2 pi pi 4096 Jan 2 22:04 .
total 8
drwxrwx--x 4 pi pi 4096 Jan 2 22:19 ..
drwxrwx--x 2 pi pi 4096 Jan 2 22:19 .
total 12
-rw-r--r-- 1 root root 47 Dec 15 18:59 99-input.rules
-rw-r--r-- 1 root root 114 Dec 16 20:39 40-scratch.rules
-rw-r--r-- 1 root root 88 Jan 2 00:18 53-radioactive.rules
#r@h
ATTRS{idVendor}=="16c0", MODE="666", GROUP="plugdev"
LABEL="radioactive_rules_end"
About the file, I've run the usermod command for 'pi' user:
/ Reply
Quote
TJMProject administrator
Project developer
Project tester
Send message
Joined: 16 Apr 11
Posts: 291
Credit: 1,382,252
RAC: 68
I've updated the app to 1.71, should be working now.
____________
/ Reply
Quote
I've updated the app to 1.71, should be working now.
Seems ok now :)
First WU is running:
http://radioactiveathome.org/boinc/result.php?resultid=1335866
/ Reply
Quote
TJMProject administrator
Project developer
Project tester
Send message
Joined: 16 Apr 11
Posts: 291
Credit: 1,382,252
RAC: 68
Do you see any progress ? The app might be running, but if there's anything wrong with the udev permissions, it won't see the sensor.
/ Reply
Quote
Do you see any progress ? The app might be running, but if there's anything wrong with the udev permissions, it won't see the sensor.
Yes, the WU is at 16% now, I've set preference to about 9h/WU, and after the start the beeper go correctly to quite mode.
A diff with PC: the backlight seems a bit less brigth.
/ Reply
Quote
After few days Raspberry seems work fine (also with QCN client/sensor running).
This is my host:
http://radioactiveathome.org/scripts/graph/scrollgraph.php?days=0&hostid=5494
Just a question: I must migrate to user root the whole BOINC directory to use a feature of QCN modded BOINC client (7.1.0) that rise the priority of QCN client.
Do you think that may impact with problems the Radioactive client ?
/ Reply
Quote
TJMProject administrator
Project developer
Project tester
Send message
Joined: 16 Apr 11
Posts: 291
Credit: 1,382,252
RAC: 68
Nope, the QCN modded client runs nci tasks at higher priority which is also good for our app.
/ Reply
Quote
Sorry if this has already been answered somewhere, but I recently got a Raspberry Pi B+ running Raspbian.
It runs Einstein tasks fine but when I connect to Radioactive@home the sensor if never detected (buzzer and backlight stays on). I'm not sure which version the sensor is, but its case is a plastic pipe if that helps?
In the stderr.txt I'm getting the following over and over:
"Warning: cannot query manufacturer for deive: error sending control message: operation not permitted"
"Debug (openDevice): 16c0:05df obdev.at/datastore not found or could not be accessed: Device communication error"
"Debug (openDevice): 16c0:05df obdev.at/radioactiveathome.org GRS not found or could not be accessed: Device communication error"
(Please note those are not copied and pasted so there might be some small errors)
Any ideas what the problem is?
Cheers :D
/ Reply
Quote
That sounds very similar to the problem I had. I think your sensor is an earlier version, but you may need to do the same thing...
Under Linux, there are a couple of other things you may need to add, since the client runs under its own userid of "boinc" and won't be allowed access to the usb port unless you tell Linux to allow it (it'll just sit there not talking to the sensor until the WU timer expires).
See my post on another thread at
http://radioactiveathome.org/boinc/forum_thread.php?id=473&nowrap=true#3082
... then hopefully you'll get a bit further. I don't know why the buzzer stays on though.
/ Reply
Quote