It is not file permissions, but the USB access permissions that you need to change.
Good step-by-step reading for beginners here:
I noticed that sometimes WSPR decoding phase takes a few seconds, and sometimes more than 2 minutes, so there is sometimes a message that the next decoding can not start (maybe 1 out of 20-50 cycles). But for me it always eventually finishes.
--- In firstname.lastname@example.org, "va3dxz" wrote:
> Thanks Mike. When I log into the pi, I start the gui with startx, then I open a terminal window, cd to wspr then ./wspr to start the application. The application starts up but can't talk to the softrock:
> rig_open: error = IO error
> Error attempting to set rig freq
> rigctl -m 2509 -r USD F 10126729
> So I looked at the permissions as you suggested. Each of the hamlib files were set to -rw-r--r--. I changed each to -rwxrwxrwx but same problem. After putting the permissions back to -rw-r--r--, I tried starting wspr using sudo ./wspr and it worked. I was able to tx and change frequency.
> However, after the 1st receive cycle, when the decode kicked in, the CPU was pegged at 100% and stayed there. When the next TX cycle came around, I would see
> error executing rigctl to set TX mode
> rigctl -m 2509 -r USB T 1
> In most cases I needed to reboot the PI to bring it back to life. I have the PI overclocked to 1Ghz and set this up using raspi-config. I double checked the clock speed using vcgencmd get_config arm_freq.
> Is anyone else seeing performance issues like this?
> Thanks and 73,
> Chris / VA3DXZ