I’m getting this error message when trying to run the install on my RPI4…
./fullbuild-wfview.sh: Syntax error: newline unexpected
I’m a windows guy, Any ideas what’s wrong ?
73 Jeff kb2m
Hi Jeff
Did you download the script https://gitlab.com/eliggett/scripts/-/blob/master/fullbuild-wfview.sh on a Windows machine by any chance? If so it has probably converted the file to windows format text. Windows text files have a carriage return and linefeed character at the end of each line whereas Linux (Unix) files just have a line feed.
You can either re-download the file directly on the Pi or use the following command to convert it:
tr -d '\r' fullbuild-wfview.sh > fullbuild-wfview-new.sh
Then run fullbuild-wfview-new.sh
Let me know if this isn’t the issue and I will try the script on my Pi4.
73 Phil M0VSE
Hi Phil. No I d/l it on my RPI4. But, I then sent the file to the trash and d/l it again and the build worked, I now have wfview running on my PI. Later on today when I get back home I’m going to get my 7300 running and try to connect. Only minor issue I had with the install is I had to add a sudo to commands to execute the script. I should add myself as a SU later on…
73 Jeff kb2m
Hi Jeff,
did you remember to chmod +x fullbuild-wfview.sh ? You should not run the script as root; running git commands as root, which are in the script, isn’t the best practice. The script should be already using the sudo command as-needed within the script, but do let me know if there was a step that needed it.
–E
de W6EL
I ran the script as suggested from the download dir…
cd ~/Downloads
chmod +x fullbuild-wfview.sh
./fullbuild-wfview.sh
I had to run as sudo
Next question. What I’m trying to do here is access my 7300 remotely with a win10 laptop. I’m setting up the RPI4 connected to the 7300 local. As I’m a 72 year old windows guy with a vision problem it’s getting very difficult to work through this kinda stuff without a cheat sheet. Has anyone got this running? I can deal with the router passthru issues, but I’m not sure how to configure the RPI4 to allow remote access without a local PC. Thanks for any help with this…
73 Jeff kb2m
I got the 7300 running with wfview on the RPI4 via the USB port. Now to deal with the audio. I don’t see any info on how to set that up. I have no experience with setting up audio on a PI. All I’ve done that would use audio on a PI was for rxing satellite telemetry. Any suggestions appreciated…
73 Jeff kb2m
Hi Jeff,
You need to use those pop-down menus to select the correct audio device. Press Save Settings, and re-launch.
–E
de W6EL
I’m aware of that Elliot, but don’t have a clue on WHAT audio device to select…
73 Jeff kb2m
Hi Jeff,
I believe both devices are listed in the link above. Here they are for reference:
Audio Input: alsa_input.usb-Burr-Brown_from_TI_USB_Audio_CODEC-00.analog-stereo
Audio Output: alsa_output.usb-Burr-Brown_from_TI_USB_Audio_CODEC-00.analog-stereo
–E
de W6EL
Hi Elliot. I see the
Audio Input: alsa_input.usb-Burr-Brown_from_TI_USB_Audio_CODEC-00.analog-stereo
and
Audio Output: alsa_output.usb-Burr-Brown_from_TI_USB_Audio_CODEC-00.analog-stereo
are the defaults in the server copy of wfview. All that seems to be working ok. My issue is how to get the audio working on the WIN10 client wfview running on my laptop. I can’t find any discussions on this anywhere in the docs. I’m thinking I have to setup some kind of virtual audio device on the PI? and the PC? I’m presently not seeing any audio devices associated with wfview on the PC. We’re almost there!
73 Jeff kb2m
Once you are connected from your WIN10 client to the Pi, you should see the spectrum and the s-meter moving, and you should hear receive audio on the client. Pressing transmit should result in sending audio to the transmitter.
If you’re not hearing anything, please check that the squelch is turned down and “AF” is turned up. you do not need any virtual cables to hear the receiver and/or operate the transmit from a speaker and mic.
–E
de W6EL
Everything is working except the audio. This morning I got a BT headset to sort of work. When I fist start the program I hear solid audio. But after a few seconds the audio starts cutting out every second or so for a second, and on, and on. I’m thinking some kind of buffer overflow in the audio chain? The BT headset appears to operate at a sample rate of either 8000 com quality, or 44100 cd quality, but no 48000 selectable. I try to set a sample rate of 8000 in wfview and it doesn’t seem to take, I try to save it and it reverts back to 48000. The sample rate window in WIN10 headset properties is grayed out.
More info. I got it working the same with the default PC speaker. It’s doing the same thing. I tried adjusting the RX latency, then saving settings, and restarting the program audio is still hosed. I should mention that audio works fine in all other applications like WSJT, watching video’s, etc…
73 Jeff kb2m
Hi Jeff.
It is a known issue with the Pi which is fixed on the audio-enhance branch (along with lots of other fixes).
If you go to your wfview source directory and enter the following:
git pull
git checkout audio-enhance
git pull
git submodule init
git submodule update
Then build as normal, you will find the server audio is MUCH better.
73 Phil M0VSE
I have no idea on how to do this. I will build a new SD image to work with. Where is the wfview source directory normally located on the RPI4?
73 Jeff kb2m
Hi Jeff,
We will do an official release soon with this fix, hang tight.
–E
de W6EL
Thanks Elliot, no rush, thanks for your support on this…
73 Jeff kb2m
Hi Jeff,
I’m looking forward to it as much as anyone. I’ve been running my 7300 remotely using the latest code and it works very well. I can’t wait to move that task to a Pi!
–E
de W6EL
What will also be needed is setting up wfview to auto run so when there is a power failure the PI running wfview will auto boot up when the power does. Thanks in advance 
73 Jeff kb2m