Date   

moderated Re: #flrig #kx3 #flrig #kx3

Edward Walker, AG7DT
 

Hi, Dave -
 
Please recall that the issue is a 3-4 second delay in turning off the KX3 PTT after the Flrig PTT toggle is pressed to release PTT. The RF stops, but the KX3 does not return to RX mode for 3-4 additional seconds as indicated by the TX light and the waterfall. The K3 script seems to get this right. 
 
To save you some time, I did a comparison of the K3 and KX3 .xml files, and here is a summary. Because the K3 file seems to work ok in place of the KX3, I suspect that this is likely simply a timing issue

TIMEOUT:   KX3=100 vs K3=50; 
WRITE DELAY: KX3=50 vs K3=5; 
INIT DELAY: KX3= 400, command missing in K3; 
RTSCTS FALSE;CMDPTT TRUE found in KX3 file, but these commands are missing from the K3 file

There are some additional differences related to turning on DATA A mode, but they don't' seem to be relevant to the timing issues.

I would be happy to help test for this if you could explain where the KX3 rig file is in the Raspberry Pi file structure.

Thanks for a wonderful piece of software, and have a happy new year!

73,  Ed  AG7DT


moderated Re: CAT control cannot dial the frequency from software (wsjtx, fldigi, hamlib, flrig, rigcat) #ft-450 #scu17

Marty Hartwell, KD8BJ
 

Hi

A question if I may, while using fldigi using RigCat can you connect to the rig? And what version

of fldigi are you using? My reason for asking is I can't connect to my FT-817 with V.4.1.17 of

fldigi.

Marty kd8bj


On 12/29/20 7:37 PM, Sherwin, VE7HQT wrote:

Manjaro Linux is running on Lenovo E14 laptop.
username is in uucp group.

With fldigi, I tried the following:

  1. RigCAT. The FT-450.xml file was from
    https://sourceforge.net/projects/fldigi/files/xmls/yaesu/
    Baud rate 38400. Stopbits 1 (also tried 2)

  2. Hamlib with settings Rig: Yaesu FT-450 (Beta).
    Baud rate 38400. Stopbits 1 (also tried 2)
  3. Hamlib with settings Rig: Hamlib NET rigtrl (Stable).
    Device: 127.0.0.1:4532
    The daemon was running /usr/bin/rigctld -m 127 -r /dev/ttyUSB0 -t 4532 -s 38400

wsjtx basically uses Hamlib. I tried the following:
  1. Hamlib with settings Rig: Yaesu FT-450 (Beta).
    Baud rate 38400. Stopbits 1 (also tried 2)

  2. Hamlib with settings Rig: Hamlib NET rigtrl (Stable).
    Network server: 127.0.0.1:4532
    The daemon was running /usr/bin/rigctld -m 127 -r /dev/ttyUSB0 -t 4532 -s 38400
Finally, with flrig, I tried  the following:
  1. Rig: FT-450D, /dev/ttyUSB0, Baud: 38400

With all the various rig control settings I've tried above, I can dial to a frequency on my transceiver and the frequency is reflected on the respective software. However, if I try to set a frequency from the software, there is no response from the transceiver. The software then reverts to the frequency shown on my transceiver.


moderated Re: CAT control cannot dial the frequency from software (wsjtx, fldigi, hamlib, flrig, rigcat) #ft-450 #scu17

Sherwin DW9KAY
 

Hello Ed,

Manjaro Arch Linux uses uucp.
https://wiki.archlinux.org/index.php/Users_and_groups#User_groups

I've solved my issue.

My newbie mistake caused me 3 days of fiddling when the answer was simple. :)

73
Sherwin
VE7HQT


moderated Re: CAT control cannot dial the frequency from software (wsjtx, fldigi, hamlib, flrig, rigcat) #ft-450 #scu17

Sherwin DW9KAY
 

I will slap myself silly.

After looking looking through flrig Event Log and making sense of it. I noticed that flrig was setting the frequency a VFO-A.

I was in memory mode (M-TUNE)!

I set my radio back to VFO-A and I now see the changes from the software.

So now with the 
following settings
FT-450D with SCU-17
VFO-A
CAT RTS = ENABLE
CAT TOT = 10
CATRATE = 38400

I've set all the ftdigi and wsjtx on Hamlib NET rigtrl (Stable) since I've set them as remote on cqrlog.

Now I can sleep easy. Happy New Year!


moderated Re: Raspberry Pi compile of flrig and fldigi

Ed W3NR
 

On 12/29/20 8:31 PM, Doug Person, KJ0F wrote:

fldigi and flrig compiled and installed OK. It's just my lack of knowledge about how such a complex process turns out successful. Would be very helpful if a final step in the script simply checked for success and left a message for those of us who are not experienced linux programmers. linux has always had a reputation for not being particularly new user friendly so every little bit helps.

If you do not see an "Error 1" in make you are usually good to go.

It's not that is not user friendly,it's different then the MS way to do things.

I started in 2002 before groups.io existed, any help was few and far in between.

Just hang out here and remember there is no such thing as a dumb question.

We are here to help in  any way we can.

Ed W3NR


moderated Re: FYI

Andy_VE4PER <andrew.webb.501.ve4per@...>
 

another update today now vers 4.3 is current one

On 2020-12-19 3:50 p.m., Andy_VE4PER via groups.io wrote:
Winlink VARA HF modem vers 4.1.5 now

treied posting to winlink group but did not see it get posted. A number of folks been trying to use gateway here using VARA HF and not connecting.







moderated Re: CAT control cannot dial the frequency from software (wsjtx, fldigi, hamlib, flrig, rigcat) #ft-450 #scu17

Ed W3NR
 

On 12/29/20 8:37 PM, Sherwin, VE7HQT wrote:
Manjaro Linux is running on Lenovo E14 laptop.
username is in uucp group.

You also need to be in the dialout group.

Ed W3NR


moderated Re: CAT control cannot dial the frequency from software (wsjtx, fldigi, hamlib, flrig, rigcat) #ft-450 #scu17

Sherwin DW9KAY
 

Manjaro Linux is running on Lenovo E14 laptop.
username is in uucp group.

With fldigi, I tried the following:

  1. RigCAT. The FT-450.xml file was from
    https://sourceforge.net/projects/fldigi/files/xmls/yaesu/
    Baud rate 38400. Stopbits 1 (also tried 2)

  2. Hamlib with settings Rig: Yaesu FT-450 (Beta).
    Baud rate 38400. Stopbits 1 (also tried 2)
  3. Hamlib with settings Rig: Hamlib NET rigtrl (Stable).
    Device: 127.0.0.1:4532
    The daemon was running /usr/bin/rigctld -m 127 -r /dev/ttyUSB0 -t 4532 -s 38400

wsjtx basically uses Hamlib. I tried the following:
  1. Hamlib with settings Rig: Yaesu FT-450 (Beta).
    Baud rate 38400. Stopbits 1 (also tried 2)

  2. Hamlib with settings Rig: Hamlib NET rigtrl (Stable).
    Network server: 127.0.0.1:4532
    The daemon was running /usr/bin/rigctld -m 127 -r /dev/ttyUSB0 -t 4532 -s 38400
Finally, with flrig, I tried  the following:
  1. Rig: FT-450D, /dev/ttyUSB0, Baud: 38400

With all the various rig control settings I've tried above, I can dial to a frequency on my transceiver and the frequency is reflected on the respective software. However, if I try to set a frequency from the software, there is no response from the transceiver. The software then reverts to the frequency shown on my transceiver.


moderated Re: Raspberry Pi compile of flrig and fldigi

Doug Person, KJ0F <doug@...>
 

fldigi and flrig compiled and installed OK. It's just my lack of knowledge about how such a complex process turns out successful. Would be very helpful if a final step in the script simply checked for success and left a message for those of us who are not experienced linux programmers. linux has always had a reputation for not being particularly new user friendly so every little bit helps.

Suggestion:

"/usr/local/bin/fldigi Successfully created. A reboot may be required to update system menu(s)"

73, Doug -- K0DXV

On 12/29/2020 5:10 PM, Marty Hartwell, KD8BJ wrote:

You can also try to launch it from the command line to see if it comes up.


Marty kd8bj


On 12/29/20 5:08 PM, Cliff, AE5ZA wrote:
That looks like a successful install. Look in /usr/local/bin and you’ll likely find the executable.

On the Pi the icons are in the menu under Internet. You may have to reboot to have them show up there.

73,
Cliff, AE5ZA

On Dec 29, 2020, at 15:32, Doug Person, KJ0F <doug@...> wrote:

The output of the build is huge. I don't know what an error message looks like in all the output. The end result was there was no fldigi app in the menu, on the desk top, or in /usr/local/share/applications, or anywhere else I looked.

These are the condensed steps I followed (From my notebook)

# Compile fldigi on Raspberry Pi 3

Step 1:
    # Edit the file /etc/apt/sources.list
    sudo cp /etc/apt/sources.list /etc/apt/sources.list.bak
Step 2:
    sudo apt-get install aptitude
    sudo aptitude update
Step 3:
    # Install the basic development packages
    sudo aptitude install build-essential
Step 4:
    # Install the build dependency packages
    sudo aptitude build-dep fldigi
Step 5:
    # Make sure that build-dep has installed libxft-dev.
    # Test by looking for the Xft.h header.
    # If not present: sudo aptitude install libxft-dev
    ls /usr/include/X11/Xft/Xft.h
    Result: /usr/include/X11/Xft/Xft.h
Step 6:
    # Check swapfile - Increase to 2048
    sudo nano /etc/dphys-swapfile
    CONF_SWAPSIZE=2048
    sudo /etc/init.d/dphys-swapfile stop
    sudo /etc/init.d/dphys-swapfile start
Step 7:
    # Download & unpack tarball
    ls fldigi*
    fldigi-4.1.17.06:
    ABOUT-NLS   autom4te.cache  config.log     configure.ac  doc      Makefile     NEWS    scripts
    aclocal.m4  build-aux       config.status  COPYING       INSTALL  Makefile.am  po      src
    AUTHORS     ChangeLog       configure      data          m4       Makefile.in  README
Step 8:
    # prepare the source for compilation with the configure command.
    ./configure --enable-optimizations=rpi3
Step 9:
    # If you do not find a configure script in the directory,
    # it can be re-generated using the command (I assume file name is "configure")
    autoreconf -i
Step 10:
    # Proceed to make and install fldigi and flarq.
    make && sudo make install
Step 11:
    # Install the volume manager.
    sudo aptitude install pavucontrol
Step 12:
    # Pi3 users may find the pulse sound server
    # is not started at boot. If so add the following to:
    sudo nano /home/pi/.config/lxsession/LXDE-pi/autostart
    # NOTE: Raspien Buster: File does not exist
Step 13:
    # add yourself to the dialout group.
    sudo adduser (pi) dialout

Following is the output from the make install:

pi@raspberrypi:~/Downloads/fldigi-4.1.17.06 $ sudo make install
Making install in po
make[1]: Entering directory '/home/pi/Downloads/fldigi-4.1.17.06/po'
/usr/bin/mkdir -p /usr/local/share
installing el.gmo as /usr/local/share/locale/el/LC_MESSAGES/fldigi.mo
installing es.gmo as /usr/local/share/locale/es/LC_MESSAGES/fldigi.mo
installing fr.gmo as /usr/local/share/locale/fr/LC_MESSAGES/fldigi.mo
installing it.gmo as /usr/local/share/locale/it/LC_MESSAGES/fldigi.mo
installing pl.gmo as /usr/local/share/locale/pl/LC_MESSAGES/fldigi.mo
installing de.gmo as /usr/local/share/locale/de/LC_MESSAGES/fldigi.mo
installing nl.gmo as /usr/local/share/locale/nl/LC_MESSAGES/fldigi.mo
installing ru.gmo as /usr/local/share/locale/ru/LC_MESSAGES/fldigi.mo
if test "fldigi" = "gettext-tools"; then \
  /usr/bin/mkdir -p /usr/local/share/gettext/po; \
  for file in Makefile.in.in remove-potcdate.sin quot.sed boldquot.sed en@... en@... insert-header.sin Rules-quot   Makevars.template; do \
    /usr/bin/install -c -m 644 ./$file \
            /usr/local/share/gettext/po/$file; \
  done; \
  for file in Makevars; do \
    rm -f /usr/local/share/gettext/po/$file; \
  done; \
else \
  : ; \
fi
make[1]: Leaving directory '/home/pi/Downloads/fldigi-4.1.17.06/po'
Making install in doc
make[1]: Entering directory '/home/pi/Downloads/fldigi-4.1.17.06/doc'
make[2]: Entering directory '/home/pi/Downloads/fldigi-4.1.17.06/doc'
make[2]: Nothing to be done for 'install-exec-am'.
 /usr/bin/mkdir -p '/usr/local/share/man/man1'
 /usr/bin/install -c -m 644 fldigi.1 flarq.1 '/usr/local/share/man/man1'
make[2]: Leaving directory '/home/pi/Downloads/fldigi-4.1.17.06/doc'
make[1]: Leaving directory '/home/pi/Downloads/fldigi-4.1.17.06/doc'
Making install in src
make[1]: Entering directory '/home/pi/Downloads/fldigi-4.1.17.06/src'
make  install-recursive
make[2]: Entering directory '/home/pi/Downloads/fldigi-4.1.17.06/src'
make[3]: Entering directory '/home/pi/Downloads/fldigi-4.1.17.06/src'
make[4]: Entering directory '/home/pi/Downloads/fldigi-4.1.17.06/src'
 /usr/bin/mkdir -p '/usr/local/bin'
  /usr/bin/install -c fldigi flarq '/usr/local/bin'
if test -f ./../scripts/ftp_kml_files.sh; then \
    /bin/bash /home/pi/Downloads/fldigi-4.1.17.06/build-aux/install-sh -d //usr/local/bin; \
        /usr/bin/install -c ./../scripts/ftp_kml_files.sh //usr/local/bin; \
fi
if test -f ./../data/fldigi.xpm; then \
    /bin/bash /home/pi/Downloads/fldigi-4.1.17.06/build-aux/install-sh -d //usr/local/share/pixmaps; \
    /usr/bin/install -c -m 644 ./../data/fldigi.xpm //usr/local/share/pixmaps; \
fi
if test -f ./../data/fldigi.desktop; then \
    /bin/bash /home/pi/Downloads/fldigi-4.1.17.06/build-aux/install-sh -d //usr/local/share/applications; \
    /usr/bin/install -c -m 644 ./../data/fldigi.desktop //usr/local/share/applications; \
fi
if test -f ./../data/NAVTEX_Stations.csv; then \
    /bin/bash /home/pi/Downloads/fldigi-4.1.17.06/build-aux/install-sh -d //usr/local/share/fldigi; \
    /usr/bin/install -c -m 644 ./../data/NAVTEX_Stations.csv //usr/local/share/fldigi; \
fi
if test -f ./../data/nsd_bbsss.txt; then \
    /bin/bash /home/pi/Downloads/fldigi-4.1.17.06/build-aux/install-sh -d //usr/local/share/fldigi; \
    /usr/bin/install -c -m 644 ./../data/nsd_bbsss.txt //usr/local/share/fldigi; \
fi
if test -f ./../data/station_table.txt; then \
    /bin/bash /home/pi/Downloads/fldigi-4.1.17.06/build-aux/install-sh -d //usr/local/share/fldigi; \
    /usr/bin/install -c -m 644 ./../data/station_table.txt //usr/local/share/fldigi; \
fi
if test -f ./../data/ToR-Stats-SHIP.csv; then \
    /bin/bash /home/pi/Downloads/fldigi-4.1.17.06/build-aux/install-sh -d //usr/local/share/fldigi; \
    /usr/bin/install -c -m 644 ./../data/ToR-Stats-SHIP.csv //usr/local/share/fldigi; \
fi
if test -f ./../data/wmo_list.txt; then \
    /bin/bash /home/pi/Downloads/fldigi-4.1.17.06/build-aux/install-sh -d //usr/local/share/fldigi; \
    /usr/bin/install -c -m 644 ./../data/wmo_list.txt //usr/local/share/fldigi; \
fi
if test -f ./../kml/styles.kml; then \
    /bin/bash /home/pi/Downloads/fldigi-4.1.17.06/build-aux/install-sh -d //usr/local/share/fldigi/kml; \
    /usr/bin/install -c -m 644 ./../kml/styles.kml //usr/local/share/fldigi/kml; \
fi
if test -f ./../data/flarq.xpm; then \
    /bin/bash /home/pi/Downloads/fldigi-4.1.17.06/build-aux/install-sh -d //usr/local/share/pixmaps; \
    /usr/bin/install -c -m 644 ./../data/flarq.xpm //usr/local/share/pixmaps; \
fi
if test -f ./../data/flarq.desktop; then \
    /bin/bash /home/pi/Downloads/fldigi-4.1.17.06/build-aux/install-sh -d //usr/local/share/applications; \
    /usr/bin/install -c -m 644 ./../data/flarq.desktop //usr/local/share/applications; \
fi
make[4]: Leaving directory '/home/pi/Downloads/fldigi-4.1.17.06/src'
make[3]: Leaving directory '/home/pi/Downloads/fldigi-4.1.17.06/src'
make[2]: Leaving directory '/home/pi/Downloads/fldigi-4.1.17.06/src'
make[1]: Leaving directory '/home/pi/Downloads/fldigi-4.1.17.06/src'
make[1]: Entering directory '/home/pi/Downloads/fldigi-4.1.17.06'
make[2]: Entering directory '/home/pi/Downloads/fldigi-4.1.17.06'
make[2]: Nothing to be done for 'install-exec-am'.
make[2]: Nothing to be done for 'install-data-am'.
make[2]: Leaving directory '/home/pi/Downloads/fldigi-4.1.17.06'
make[1]: Leaving directory '/home/pi/Downloads/fldigi-4.1.17.06'



On 12/28/20 9:36 PM, Dave, W1HKJ wrote:
Be sure to follow the instructions on the fldigi wiki exactly, especially take note of Pi3/4 requirements:


Special Note for Pi3 & Pi4 users with 1 GB RAM

Compiling fldigi requires more than the default swap space. You may need to increase the swap space on the microSD card. Please follow the example instructions at Pi Swap Space and use the number 2048 instead of 1024 to give 2 GB of swap. Some users have needed the larger swap space.
You are now ready to build fldigi.

73, David, W1HKJ

On 12/28/20 10:08 PM, Doug Person, KJ0F wrote:

I've tried twice to compile the latest versions flrig and fldigi. They always fail with messages that don't say much. Are the instructions still valid? I followed them carefully twice. I'm using the latest RPI linux release "buster".

I'm trying to do this for a friend who wants to operate digital on the road. I'm way out of my league trying to compile in this environment. I see many warnings coming out, and then a series of errors and it all stops.

Anyone having success on RPI3?

Thanks -- Doug -- K0DXV




moderated Re: flnet 7.3.3.12 posted

Cliff, AE5ZA
 

Doing the same thing on Pi4 Raspian, default desktop manager. No crash.

73,
Cliff, AE5ZA

On Dec 29, 2020, at 17:41, Dave, W1HKJ <w1hkj@...> wrote:

I can duplicate the crash.

Dave

On 12/29/20 3:01 PM, Mark Gregory, AB9ZA wrote:

Dave,

I ran flnet with gdb, and below is the result.  I purposely tried to add a call sign that I knew would not be in the .csv database I was using.  After typing in the call sign in the suffix, prefix and area boxes and depressing Enter, I did an F12, then a Call Sign Lookup.  It worked fine until I clicked on Save, then the Lookup window and flnet both froze.  I had to Ctrl+D to exit gdb and close them.  Attached is a screenshot of the frozen windows, and below is the output of the gdb run.  I hope that helps, I am not sure if that is the relevant info or not.




moderated Re: flnet 7.3.3.12 posted

Dave, W1HKJ
 

I can duplicate the crash.

Dave

On 12/29/20 3:01 PM, Mark Gregory, AB9ZA wrote:

Dave,

I ran flnet with gdb, and below is the result.  I purposely tried to add a call sign that I knew would not be in the .csv database I was using.  After typing in the call sign in the suffix, prefix and area boxes and depressing Enter, I did an F12, then a Call Sign Lookup.  It worked fine until I clicked on Save, then the Lookup window and flnet both froze.  I had to Ctrl+D to exit gdb and close them.  Attached is a screenshot of the frozen windows, and below is the output of the gdb run.  I hope that helps, I am not sure if that is the relevant info or not.



moderated Re: Raspberry Pi compile of flrig and fldigi

Marty Hartwell, KD8BJ
 

You can also try to launch it from the command line to see if it comes up.


Marty kd8bj


On 12/29/20 5:08 PM, Cliff, AE5ZA wrote:

That looks like a successful install. Look in /usr/local/bin and you’ll likely find the executable.

On the Pi the icons are in the menu under Internet. You may have to reboot to have them show up there.

73,
Cliff, AE5ZA

On Dec 29, 2020, at 15:32, Doug Person, KJ0F <doug@...> wrote:

The output of the build is huge. I don't know what an error message looks like in all the output. The end result was there was no fldigi app in the menu, on the desk top, or in /usr/local/share/applications, or anywhere else I looked.

These are the condensed steps I followed (From my notebook)

# Compile fldigi on Raspberry Pi 3

Step 1:
    # Edit the file /etc/apt/sources.list
    sudo cp /etc/apt/sources.list /etc/apt/sources.list.bak
Step 2:
    sudo apt-get install aptitude
    sudo aptitude update
Step 3:
    # Install the basic development packages
    sudo aptitude install build-essential
Step 4:
    # Install the build dependency packages
    sudo aptitude build-dep fldigi
Step 5:
    # Make sure that build-dep has installed libxft-dev.
    # Test by looking for the Xft.h header.
    # If not present: sudo aptitude install libxft-dev
    ls /usr/include/X11/Xft/Xft.h
    Result: /usr/include/X11/Xft/Xft.h
Step 6:
    # Check swapfile - Increase to 2048
    sudo nano /etc/dphys-swapfile
    CONF_SWAPSIZE=2048
    sudo /etc/init.d/dphys-swapfile stop
    sudo /etc/init.d/dphys-swapfile start
Step 7:
    # Download & unpack tarball
    ls fldigi*
    fldigi-4.1.17.06:
    ABOUT-NLS   autom4te.cache  config.log     configure.ac  doc      Makefile     NEWS    scripts
    aclocal.m4  build-aux       config.status  COPYING       INSTALL  Makefile.am  po      src
    AUTHORS     ChangeLog       configure      data          m4       Makefile.in  README
Step 8:
    # prepare the source for compilation with the configure command.
    ./configure --enable-optimizations=rpi3
Step 9:
    # If you do not find a configure script in the directory,
    # it can be re-generated using the command (I assume file name is "configure")
    autoreconf -i
Step 10:
    # Proceed to make and install fldigi and flarq.
    make && sudo make install
Step 11:
    # Install the volume manager.
    sudo aptitude install pavucontrol
Step 12:
    # Pi3 users may find the pulse sound server
    # is not started at boot. If so add the following to:
    sudo nano /home/pi/.config/lxsession/LXDE-pi/autostart
    # NOTE: Raspien Buster: File does not exist
Step 13:
    # add yourself to the dialout group.
    sudo adduser (pi) dialout

Following is the output from the make install:

pi@raspberrypi:~/Downloads/fldigi-4.1.17.06 $ sudo make install
Making install in po
make[1]: Entering directory '/home/pi/Downloads/fldigi-4.1.17.06/po'
/usr/bin/mkdir -p /usr/local/share
installing el.gmo as /usr/local/share/locale/el/LC_MESSAGES/fldigi.mo
installing es.gmo as /usr/local/share/locale/es/LC_MESSAGES/fldigi.mo
installing fr.gmo as /usr/local/share/locale/fr/LC_MESSAGES/fldigi.mo
installing it.gmo as /usr/local/share/locale/it/LC_MESSAGES/fldigi.mo
installing pl.gmo as /usr/local/share/locale/pl/LC_MESSAGES/fldigi.mo
installing de.gmo as /usr/local/share/locale/de/LC_MESSAGES/fldigi.mo
installing nl.gmo as /usr/local/share/locale/nl/LC_MESSAGES/fldigi.mo
installing ru.gmo as /usr/local/share/locale/ru/LC_MESSAGES/fldigi.mo
if test "fldigi" = "gettext-tools"; then \
  /usr/bin/mkdir -p /usr/local/share/gettext/po; \
  for file in Makefile.in.in remove-potcdate.sin quot.sed boldquot.sed en@... en@... insert-header.sin Rules-quot   Makevars.template; do \
    /usr/bin/install -c -m 644 ./$file \
            /usr/local/share/gettext/po/$file; \
  done; \
  for file in Makevars; do \
    rm -f /usr/local/share/gettext/po/$file; \
  done; \
else \
  : ; \
fi
make[1]: Leaving directory '/home/pi/Downloads/fldigi-4.1.17.06/po'
Making install in doc
make[1]: Entering directory '/home/pi/Downloads/fldigi-4.1.17.06/doc'
make[2]: Entering directory '/home/pi/Downloads/fldigi-4.1.17.06/doc'
make[2]: Nothing to be done for 'install-exec-am'.
 /usr/bin/mkdir -p '/usr/local/share/man/man1'
 /usr/bin/install -c -m 644 fldigi.1 flarq.1 '/usr/local/share/man/man1'
make[2]: Leaving directory '/home/pi/Downloads/fldigi-4.1.17.06/doc'
make[1]: Leaving directory '/home/pi/Downloads/fldigi-4.1.17.06/doc'
Making install in src
make[1]: Entering directory '/home/pi/Downloads/fldigi-4.1.17.06/src'
make  install-recursive
make[2]: Entering directory '/home/pi/Downloads/fldigi-4.1.17.06/src'
make[3]: Entering directory '/home/pi/Downloads/fldigi-4.1.17.06/src'
make[4]: Entering directory '/home/pi/Downloads/fldigi-4.1.17.06/src'
 /usr/bin/mkdir -p '/usr/local/bin'
  /usr/bin/install -c fldigi flarq '/usr/local/bin'
if test -f ./../scripts/ftp_kml_files.sh; then \
    /bin/bash /home/pi/Downloads/fldigi-4.1.17.06/build-aux/install-sh -d //usr/local/bin; \
        /usr/bin/install -c ./../scripts/ftp_kml_files.sh //usr/local/bin; \
fi
if test -f ./../data/fldigi.xpm; then \
    /bin/bash /home/pi/Downloads/fldigi-4.1.17.06/build-aux/install-sh -d //usr/local/share/pixmaps; \
    /usr/bin/install -c -m 644 ./../data/fldigi.xpm //usr/local/share/pixmaps; \
fi
if test -f ./../data/fldigi.desktop; then \
    /bin/bash /home/pi/Downloads/fldigi-4.1.17.06/build-aux/install-sh -d //usr/local/share/applications; \
    /usr/bin/install -c -m 644 ./../data/fldigi.desktop //usr/local/share/applications; \
fi
if test -f ./../data/NAVTEX_Stations.csv; then \
    /bin/bash /home/pi/Downloads/fldigi-4.1.17.06/build-aux/install-sh -d //usr/local/share/fldigi; \
    /usr/bin/install -c -m 644 ./../data/NAVTEX_Stations.csv //usr/local/share/fldigi; \
fi
if test -f ./../data/nsd_bbsss.txt; then \
    /bin/bash /home/pi/Downloads/fldigi-4.1.17.06/build-aux/install-sh -d //usr/local/share/fldigi; \
    /usr/bin/install -c -m 644 ./../data/nsd_bbsss.txt //usr/local/share/fldigi; \
fi
if test -f ./../data/station_table.txt; then \
    /bin/bash /home/pi/Downloads/fldigi-4.1.17.06/build-aux/install-sh -d //usr/local/share/fldigi; \
    /usr/bin/install -c -m 644 ./../data/station_table.txt //usr/local/share/fldigi; \
fi
if test -f ./../data/ToR-Stats-SHIP.csv; then \
    /bin/bash /home/pi/Downloads/fldigi-4.1.17.06/build-aux/install-sh -d //usr/local/share/fldigi; \
    /usr/bin/install -c -m 644 ./../data/ToR-Stats-SHIP.csv //usr/local/share/fldigi; \
fi
if test -f ./../data/wmo_list.txt; then \
    /bin/bash /home/pi/Downloads/fldigi-4.1.17.06/build-aux/install-sh -d //usr/local/share/fldigi; \
    /usr/bin/install -c -m 644 ./../data/wmo_list.txt //usr/local/share/fldigi; \
fi
if test -f ./../kml/styles.kml; then \
    /bin/bash /home/pi/Downloads/fldigi-4.1.17.06/build-aux/install-sh -d //usr/local/share/fldigi/kml; \
    /usr/bin/install -c -m 644 ./../kml/styles.kml //usr/local/share/fldigi/kml; \
fi
if test -f ./../data/flarq.xpm; then \
    /bin/bash /home/pi/Downloads/fldigi-4.1.17.06/build-aux/install-sh -d //usr/local/share/pixmaps; \
    /usr/bin/install -c -m 644 ./../data/flarq.xpm //usr/local/share/pixmaps; \
fi
if test -f ./../data/flarq.desktop; then \
    /bin/bash /home/pi/Downloads/fldigi-4.1.17.06/build-aux/install-sh -d //usr/local/share/applications; \
    /usr/bin/install -c -m 644 ./../data/flarq.desktop //usr/local/share/applications; \
fi
make[4]: Leaving directory '/home/pi/Downloads/fldigi-4.1.17.06/src'
make[3]: Leaving directory '/home/pi/Downloads/fldigi-4.1.17.06/src'
make[2]: Leaving directory '/home/pi/Downloads/fldigi-4.1.17.06/src'
make[1]: Leaving directory '/home/pi/Downloads/fldigi-4.1.17.06/src'
make[1]: Entering directory '/home/pi/Downloads/fldigi-4.1.17.06'
make[2]: Entering directory '/home/pi/Downloads/fldigi-4.1.17.06'
make[2]: Nothing to be done for 'install-exec-am'.
make[2]: Nothing to be done for 'install-data-am'.
make[2]: Leaving directory '/home/pi/Downloads/fldigi-4.1.17.06'
make[1]: Leaving directory '/home/pi/Downloads/fldigi-4.1.17.06'



On 12/28/20 9:36 PM, Dave, W1HKJ wrote:
Be sure to follow the instructions on the fldigi wiki exactly, especially take note of Pi3/4 requirements:


Special Note for Pi3 & Pi4 users with 1 GB RAM

Compiling fldigi requires more than the default swap space. You may need to increase the swap space on the microSD card. Please follow the example instructions at Pi Swap Space and use the number 2048 instead of 1024 to give 2 GB of swap. Some users have needed the larger swap space.
You are now ready to build fldigi.

73, David, W1HKJ

On 12/28/20 10:08 PM, Doug Person, KJ0F wrote:

I've tried twice to compile the latest versions flrig and fldigi. They always fail with messages that don't say much. Are the instructions still valid? I followed them carefully twice. I'm using the latest RPI linux release "buster".

I'm trying to do this for a friend who wants to operate digital on the road. I'm way out of my league trying to compile in this environment. I see many warnings coming out, and then a series of errors and it all stops.

Anyone having success on RPI3?

Thanks -- Doug -- K0DXV




moderated Re: Fldigi Version 4.1.17 not controlling FT-187

Marty Hartwell, KD8BJ
 

I will take a look at the source on Flrig and see if I can figure it out against the xml file. I know

Dave is busy now with Flnet upgrades, and since I use that too I will use what I have and really

in the grand scheme of things fldigi is small potatoes right now.

I really suspect it is some change in the xml file to fix it. So I can play with it.


Marty kd8bj


On 12/29/20 5:03 PM, Cliff, AE5ZA wrote:

I agree, but someone with an 817 would likely need to do it. The XML file is just a text file, maybe Dave can give you ideas on what to trace and help you figure it out. 

73,
Cliff, AE5ZA

On Dec 29, 2020, at 15:12, Marty Hartwell, KD8BJ <mhartwe@...> wrote:

Hi

Yes that is the way I am going to go on the Rpi with limited screen size and bad eyes.

But it would seem to me someone would like to get fldigi fixed.

Just my OCD kicking in.


Marty kd8bj


On 12/29/20 11:47 AM, Cliff, AE5ZA wrote:
Marty,

The other way to deal with flrig is just to minimize it unless you wish to change something then pop it up, make the change, and minimize again. Not as nice as if the XML worked, but is doable. I setup a key combo for the Pi desktop of Alt+h to hide apps so it’s quicker that way than having to mouse everything.

73,
Cliff, AE5ZA

On Dec 29, 2020, at 09:49, Marty Hartwell, KD8BJ <mhartwe@...> wrote:

Hi Cliff

I have thought of that too, I can locate in Flrig the 817 area and make sure the xml file

matches, I do know that sometime in the past on fldigi that it worked with a xml file but

this xml file is newly downloaded but since it was on Source Forge it should be good.

That doesn't mean that something inside fldigi didn't change and a like change wasn't

made to the xml file. Like I say I can live with having to use flrig along with fldigi, but

that isn't the way it worked in the past.


Marty kd8bj


On 12/28/20 7:21 PM, Cliff, AE5ZA wrote:
Hi Marty,

I can’t help on 817 specific issues, but if flrig works RigCat should use the same connection parameters.

73,
Cliff, AE5ZA

On Dec 28, 2020, at 17:46, Marty Hartwell, KD8BJ <mhartwe@...> wrote:

Hi

I have just discovered that version 4.1.17 of Fldigi will not control the FT-817. I discovered this

on a RPi 4 but have built this fldigi version on my Xubuntu 18.4 laptop too.

Now here is the thing, I have also compiled a recent version of Flrig also as a test on both the

Rpi and the Xubuntu Laptop and been able to launch Flrig and connect to the Ft-817 and

then launch the Fldigi and have control that way, so all is not lost, but when I wan to use the

Rpi I would rather just use fldigi for digital modes where all is on the one screen, not a lot

or real estate on the pi with an 8" monitor or smaller. Then with the FT817 there isn't much

more that Flrig give in the way of control and with fldigi I have the log, frequency controls along

with others too.

Yes I have downloaded the xml file and have it in the rigs folder and am in the dialout group

but the only one that can keep it from working is the xml file, and I just downloaded the one

I am using from Dave's site, well the redirected source forge site.

Any ideas, I have also rechecked the rig menu options and I think they are correct.


Marty kd8bj















moderated Re: Raspberry Pi compile of flrig and fldigi

Cliff, AE5ZA
 

That looks like a successful install. Look in /usr/local/bin and you’ll likely find the executable.

On the Pi the icons are in the menu under Internet. You may have to reboot to have them show up there.

73,
Cliff, AE5ZA

On Dec 29, 2020, at 15:32, Doug Person, KJ0F <doug@...> wrote:

The output of the build is huge. I don't know what an error message looks like in all the output. The end result was there was no fldigi app in the menu, on the desk top, or in /usr/local/share/applications, or anywhere else I looked.

These are the condensed steps I followed (From my notebook)

# Compile fldigi on Raspberry Pi 3

Step 1:
    # Edit the file /etc/apt/sources.list
    sudo cp /etc/apt/sources.list /etc/apt/sources.list.bak
Step 2:
    sudo apt-get install aptitude
    sudo aptitude update
Step 3:
    # Install the basic development packages
    sudo aptitude install build-essential
Step 4:
    # Install the build dependency packages
    sudo aptitude build-dep fldigi
Step 5:
    # Make sure that build-dep has installed libxft-dev.
    # Test by looking for the Xft.h header.
    # If not present: sudo aptitude install libxft-dev
    ls /usr/include/X11/Xft/Xft.h
    Result: /usr/include/X11/Xft/Xft.h
Step 6:
    # Check swapfile - Increase to 2048
    sudo nano /etc/dphys-swapfile
    CONF_SWAPSIZE=2048
    sudo /etc/init.d/dphys-swapfile stop
    sudo /etc/init.d/dphys-swapfile start
Step 7:
    # Download & unpack tarball
    ls fldigi*
    fldigi-4.1.17.06:
    ABOUT-NLS   autom4te.cache  config.log     configure.ac  doc      Makefile     NEWS    scripts
    aclocal.m4  build-aux       config.status  COPYING       INSTALL  Makefile.am  po      src
    AUTHORS     ChangeLog       configure      data          m4       Makefile.in  README
Step 8:
    # prepare the source for compilation with the configure command.
    ./configure --enable-optimizations=rpi3
Step 9:
    # If you do not find a configure script in the directory,
    # it can be re-generated using the command (I assume file name is "configure")
    autoreconf -i
Step 10:
    # Proceed to make and install fldigi and flarq.
    make && sudo make install
Step 11:
    # Install the volume manager.
    sudo aptitude install pavucontrol
Step 12:
    # Pi3 users may find the pulse sound server
    # is not started at boot. If so add the following to:
    sudo nano /home/pi/.config/lxsession/LXDE-pi/autostart
    # NOTE: Raspien Buster: File does not exist
Step 13:
    # add yourself to the dialout group.
    sudo adduser (pi) dialout

Following is the output from the make install:

pi@raspberrypi:~/Downloads/fldigi-4.1.17.06 $ sudo make install
Making install in po
make[1]: Entering directory '/home/pi/Downloads/fldigi-4.1.17.06/po'
/usr/bin/mkdir -p /usr/local/share
installing el.gmo as /usr/local/share/locale/el/LC_MESSAGES/fldigi.mo
installing es.gmo as /usr/local/share/locale/es/LC_MESSAGES/fldigi.mo
installing fr.gmo as /usr/local/share/locale/fr/LC_MESSAGES/fldigi.mo
installing it.gmo as /usr/local/share/locale/it/LC_MESSAGES/fldigi.mo
installing pl.gmo as /usr/local/share/locale/pl/LC_MESSAGES/fldigi.mo
installing de.gmo as /usr/local/share/locale/de/LC_MESSAGES/fldigi.mo
installing nl.gmo as /usr/local/share/locale/nl/LC_MESSAGES/fldigi.mo
installing ru.gmo as /usr/local/share/locale/ru/LC_MESSAGES/fldigi.mo
if test "fldigi" = "gettext-tools"; then \
  /usr/bin/mkdir -p /usr/local/share/gettext/po; \
  for file in Makefile.in.in remove-potcdate.sin quot.sed boldquot.sed en@... en@... insert-header.sin Rules-quot   Makevars.template; do \
    /usr/bin/install -c -m 644 ./$file \
            /usr/local/share/gettext/po/$file; \
  done; \
  for file in Makevars; do \
    rm -f /usr/local/share/gettext/po/$file; \
  done; \
else \
  : ; \
fi
make[1]: Leaving directory '/home/pi/Downloads/fldigi-4.1.17.06/po'
Making install in doc
make[1]: Entering directory '/home/pi/Downloads/fldigi-4.1.17.06/doc'
make[2]: Entering directory '/home/pi/Downloads/fldigi-4.1.17.06/doc'
make[2]: Nothing to be done for 'install-exec-am'.
 /usr/bin/mkdir -p '/usr/local/share/man/man1'
 /usr/bin/install -c -m 644 fldigi.1 flarq.1 '/usr/local/share/man/man1'
make[2]: Leaving directory '/home/pi/Downloads/fldigi-4.1.17.06/doc'
make[1]: Leaving directory '/home/pi/Downloads/fldigi-4.1.17.06/doc'
Making install in src
make[1]: Entering directory '/home/pi/Downloads/fldigi-4.1.17.06/src'
make  install-recursive
make[2]: Entering directory '/home/pi/Downloads/fldigi-4.1.17.06/src'
make[3]: Entering directory '/home/pi/Downloads/fldigi-4.1.17.06/src'
make[4]: Entering directory '/home/pi/Downloads/fldigi-4.1.17.06/src'
 /usr/bin/mkdir -p '/usr/local/bin'
  /usr/bin/install -c fldigi flarq '/usr/local/bin'
if test -f ./../scripts/ftp_kml_files.sh; then \
    /bin/bash /home/pi/Downloads/fldigi-4.1.17.06/build-aux/install-sh -d //usr/local/bin; \
        /usr/bin/install -c ./../scripts/ftp_kml_files.sh //usr/local/bin; \
fi
if test -f ./../data/fldigi.xpm; then \
    /bin/bash /home/pi/Downloads/fldigi-4.1.17.06/build-aux/install-sh -d //usr/local/share/pixmaps; \
    /usr/bin/install -c -m 644 ./../data/fldigi.xpm //usr/local/share/pixmaps; \
fi
if test -f ./../data/fldigi.desktop; then \
    /bin/bash /home/pi/Downloads/fldigi-4.1.17.06/build-aux/install-sh -d //usr/local/share/applications; \
    /usr/bin/install -c -m 644 ./../data/fldigi.desktop //usr/local/share/applications; \
fi
if test -f ./../data/NAVTEX_Stations.csv; then \
    /bin/bash /home/pi/Downloads/fldigi-4.1.17.06/build-aux/install-sh -d //usr/local/share/fldigi; \
    /usr/bin/install -c -m 644 ./../data/NAVTEX_Stations.csv //usr/local/share/fldigi; \
fi
if test -f ./../data/nsd_bbsss.txt; then \
    /bin/bash /home/pi/Downloads/fldigi-4.1.17.06/build-aux/install-sh -d //usr/local/share/fldigi; \
    /usr/bin/install -c -m 644 ./../data/nsd_bbsss.txt //usr/local/share/fldigi; \
fi
if test -f ./../data/station_table.txt; then \
    /bin/bash /home/pi/Downloads/fldigi-4.1.17.06/build-aux/install-sh -d //usr/local/share/fldigi; \
    /usr/bin/install -c -m 644 ./../data/station_table.txt //usr/local/share/fldigi; \
fi
if test -f ./../data/ToR-Stats-SHIP.csv; then \
    /bin/bash /home/pi/Downloads/fldigi-4.1.17.06/build-aux/install-sh -d //usr/local/share/fldigi; \
    /usr/bin/install -c -m 644 ./../data/ToR-Stats-SHIP.csv //usr/local/share/fldigi; \
fi
if test -f ./../data/wmo_list.txt; then \
    /bin/bash /home/pi/Downloads/fldigi-4.1.17.06/build-aux/install-sh -d //usr/local/share/fldigi; \
    /usr/bin/install -c -m 644 ./../data/wmo_list.txt //usr/local/share/fldigi; \
fi
if test -f ./../kml/styles.kml; then \
    /bin/bash /home/pi/Downloads/fldigi-4.1.17.06/build-aux/install-sh -d //usr/local/share/fldigi/kml; \
    /usr/bin/install -c -m 644 ./../kml/styles.kml //usr/local/share/fldigi/kml; \
fi
if test -f ./../data/flarq.xpm; then \
    /bin/bash /home/pi/Downloads/fldigi-4.1.17.06/build-aux/install-sh -d //usr/local/share/pixmaps; \
    /usr/bin/install -c -m 644 ./../data/flarq.xpm //usr/local/share/pixmaps; \
fi
if test -f ./../data/flarq.desktop; then \
    /bin/bash /home/pi/Downloads/fldigi-4.1.17.06/build-aux/install-sh -d //usr/local/share/applications; \
    /usr/bin/install -c -m 644 ./../data/flarq.desktop //usr/local/share/applications; \
fi
make[4]: Leaving directory '/home/pi/Downloads/fldigi-4.1.17.06/src'
make[3]: Leaving directory '/home/pi/Downloads/fldigi-4.1.17.06/src'
make[2]: Leaving directory '/home/pi/Downloads/fldigi-4.1.17.06/src'
make[1]: Leaving directory '/home/pi/Downloads/fldigi-4.1.17.06/src'
make[1]: Entering directory '/home/pi/Downloads/fldigi-4.1.17.06'
make[2]: Entering directory '/home/pi/Downloads/fldigi-4.1.17.06'
make[2]: Nothing to be done for 'install-exec-am'.
make[2]: Nothing to be done for 'install-data-am'.
make[2]: Leaving directory '/home/pi/Downloads/fldigi-4.1.17.06'
make[1]: Leaving directory '/home/pi/Downloads/fldigi-4.1.17.06'



On 12/28/20 9:36 PM, Dave, W1HKJ wrote:
Be sure to follow the instructions on the fldigi wiki exactly, especially take note of Pi3/4 requirements:


Special Note for Pi3 & Pi4 users with 1 GB RAM

Compiling fldigi requires more than the default swap space. You may need to increase the swap space on the microSD card. Please follow the example instructions at Pi Swap Space and use the number 2048 instead of 1024 to give 2 GB of swap. Some users have needed the larger swap space.
You are now ready to build fldigi.

73, David, W1HKJ

On 12/28/20 10:08 PM, Doug Person, KJ0F wrote:

I've tried twice to compile the latest versions flrig and fldigi. They always fail with messages that don't say much. Are the instructions still valid? I followed them carefully twice. I'm using the latest RPI linux release "buster".

I'm trying to do this for a friend who wants to operate digital on the road. I'm way out of my league trying to compile in this environment. I see many warnings coming out, and then a series of errors and it all stops.

Anyone having success on RPI3?

Thanks -- Doug -- K0DXV




moderated Re: Fldigi Version 4.1.17 not controlling FT-187

Cliff, AE5ZA
 

I agree, but someone with an 817 would likely need to do it. The XML file is just a text file, maybe Dave can give you ideas on what to trace and help you figure it out. 

73,
Cliff, AE5ZA

On Dec 29, 2020, at 15:12, Marty Hartwell, KD8BJ <mhartwe@...> wrote:

Hi

Yes that is the way I am going to go on the Rpi with limited screen size and bad eyes.

But it would seem to me someone would like to get fldigi fixed.

Just my OCD kicking in.


Marty kd8bj


On 12/29/20 11:47 AM, Cliff, AE5ZA wrote:
Marty,

The other way to deal with flrig is just to minimize it unless you wish to change something then pop it up, make the change, and minimize again. Not as nice as if the XML worked, but is doable. I setup a key combo for the Pi desktop of Alt+h to hide apps so it’s quicker that way than having to mouse everything.

73,
Cliff, AE5ZA

On Dec 29, 2020, at 09:49, Marty Hartwell, KD8BJ <mhartwe@...> wrote:

Hi Cliff

I have thought of that too, I can locate in Flrig the 817 area and make sure the xml file

matches, I do know that sometime in the past on fldigi that it worked with a xml file but

this xml file is newly downloaded but since it was on Source Forge it should be good.

That doesn't mean that something inside fldigi didn't change and a like change wasn't

made to the xml file. Like I say I can live with having to use flrig along with fldigi, but

that isn't the way it worked in the past.


Marty kd8bj


On 12/28/20 7:21 PM, Cliff, AE5ZA wrote:
Hi Marty,

I can’t help on 817 specific issues, but if flrig works RigCat should use the same connection parameters.

73,
Cliff, AE5ZA

On Dec 28, 2020, at 17:46, Marty Hartwell, KD8BJ <mhartwe@...> wrote:

Hi

I have just discovered that version 4.1.17 of Fldigi will not control the FT-817. I discovered this

on a RPi 4 but have built this fldigi version on my Xubuntu 18.4 laptop too.

Now here is the thing, I have also compiled a recent version of Flrig also as a test on both the

Rpi and the Xubuntu Laptop and been able to launch Flrig and connect to the Ft-817 and

then launch the Fldigi and have control that way, so all is not lost, but when I wan to use the

Rpi I would rather just use fldigi for digital modes where all is on the one screen, not a lot

or real estate on the pi with an 8" monitor or smaller. Then with the FT817 there isn't much

more that Flrig give in the way of control and with fldigi I have the log, frequency controls along

with others too.

Yes I have downloaded the xml file and have it in the rigs folder and am in the dialout group

but the only one that can keep it from working is the xml file, and I just downloaded the one

I am using from Dave's site, well the redirected source forge site.

Any ideas, I have also rechecked the rig menu options and I think they are correct.


Marty kd8bj















moderated Re: Raspberry Pi compile of flrig and fldigi

Ed W3NR
 

On 12/29/20 4:32 PM, Doug Person, KJ0F wrote:

The output of the build is huge. I don't know what an error message looks like in all the output. The end result was there was no fldigi app in the menu, on the desk top, or in /usr/local/share/applications, or anywhere else I looked.

These are the condensed steps I followed (From my notebook)

# Compile fldigi on Raspberry Pi 3

Step 1:
    # Edit the file /etc/apt/sources.list
    sudo cp /etc/apt/sources.list /etc/apt/sources.list.bak
Step 2:
    sudo apt-get install aptitude
    sudo aptitude update
Step 3:
    # Install the basic development packages
    sudo aptitude install build-essential
Step 4:
    # Install the build dependency packages
    sudo aptitude build-dep fldigi
Step 5:
    # Make sure that build-dep has installed libxft-dev.
    # Test by looking for the Xft.h header.
    # If not present: sudo aptitude install libxft-dev
    ls /usr/include/X11/Xft/Xft.h
    Result: /usr/include/X11/Xft/Xft.h
Step 6:
    # Check swapfile - Increase to 2048
    sudo nano /etc/dphys-swapfile
    CONF_SWAPSIZE=2048
    sudo /etc/init.d/dphys-swapfile stop
    sudo /etc/init.d/dphys-swapfile start
Step 7:
    # Download & unpack tarball
    ls fldigi*
    fldigi-4.1.17.06:
    ABOUT-NLS   autom4te.cache  config.log     configure.ac  doc      Makefile     NEWS    scripts
    aclocal.m4  build-aux       config.status  COPYING       INSTALL  Makefile.am  po      src
    AUTHORS     ChangeLog       configure      data          m4       Makefile.in  README
Step 8:
    # prepare the source for compilation with the configure command.
    ./configure --enable-optimizations=rpi3
Step 9:
    # If you do not find a configure script in the directory,
    # it can be re-generated using the command (I assume file name is "configure")
    autoreconf -i
Step 10:
    # Proceed to make and install fldigi and flarq.
    make && sudo make install
Step 11:
    # Install the volume manager.
    sudo aptitude install pavucontrol
Step 12:
    # Pi3 users may find the pulse sound server
    # is not started at boot. If so add the following to:
    sudo nano /home/pi/.config/lxsession/LXDE-pi/autostart
    # NOTE: Raspien Buster: File does not exist
Step 13:
    # add yourself to the dialout group.
    sudo adduser (pi) dialout

Following is the output from the make install:

pi@raspberrypi:~/Downloads/fldigi-4.1.17.06 $ sudo make install
Making install in po
make[1]: Entering directory '/home/pi/Downloads/fldigi-4.1.17.06/po'
/usr/bin/mkdir -p /usr/local/share
installing el.gmo as /usr/local/share/locale/el/LC_MESSAGES/fldigi.mo
installing es.gmo as /usr/local/share/locale/es/LC_MESSAGES/fldigi.mo
installing fr.gmo as /usr/local/share/locale/fr/LC_MESSAGES/fldigi.mo
installing it.gmo as /usr/local/share/locale/it/LC_MESSAGES/fldigi.mo
installing pl.gmo as /usr/local/share/locale/pl/LC_MESSAGES/fldigi.mo
installing de.gmo as /usr/local/share/locale/de/LC_MESSAGES/fldigi.mo
installing nl.gmo as /usr/local/share/locale/nl/LC_MESSAGES/fldigi.mo
installing ru.gmo as /usr/local/share/locale/ru/LC_MESSAGES/fldigi.mo
if test "fldigi" = "gettext-tools"; then \
  /usr/bin/mkdir -p /usr/local/share/gettext/po; \
  for file in Makefile.in.in remove-potcdate.sin quot.sed boldquot.sed en@... en@... insert-header.sin Rules-quot   Makevars.template; do \
    /usr/bin/install -c -m 644 ./$file \
            /usr/local/share/gettext/po/$file; \
  done; \
  for file in Makevars; do \
    rm -f /usr/local/share/gettext/po/$file; \
  done; \
else \
  : ; \
fi
make[1]: Leaving directory '/home/pi/Downloads/fldigi-4.1.17.06/po'
Making install in doc
make[1]: Entering directory '/home/pi/Downloads/fldigi-4.1.17.06/doc'
make[2]: Entering directory '/home/pi/Downloads/fldigi-4.1.17.06/doc'
make[2]: Nothing to be done for 'install-exec-am'.
 /usr/bin/mkdir -p '/usr/local/share/man/man1'
 /usr/bin/install -c -m 644 fldigi.1 flarq.1 '/usr/local/share/man/man1'
make[2]: Leaving directory '/home/pi/Downloads/fldigi-4.1.17.06/doc'
make[1]: Leaving directory '/home/pi/Downloads/fldigi-4.1.17.06/doc'
Making install in src
make[1]: Entering directory '/home/pi/Downloads/fldigi-4.1.17.06/src'
make  install-recursive
make[2]: Entering directory '/home/pi/Downloads/fldigi-4.1.17.06/src'
make[3]: Entering directory '/home/pi/Downloads/fldigi-4.1.17.06/src'
make[4]: Entering directory '/home/pi/Downloads/fldigi-4.1.17.06/src'
 /usr/bin/mkdir -p '/usr/local/bin'
  /usr/bin/install -c fldigi flarq '/usr/local/bin'
if test -f ./../scripts/ftp_kml_files.sh; then \
    /bin/bash /home/pi/Downloads/fldigi-4.1.17.06/build-aux/install-sh -d //usr/local/bin; \
        /usr/bin/install -c ./../scripts/ftp_kml_files.sh //usr/local/bin; \
fi
if test -f ./../data/fldigi.xpm; then \
    /bin/bash /home/pi/Downloads/fldigi-4.1.17.06/build-aux/install-sh -d //usr/local/share/pixmaps; \
    /usr/bin/install -c -m 644 ./../data/fldigi.xpm //usr/local/share/pixmaps; \
fi
if test -f ./../data/fldigi.desktop; then \
    /bin/bash /home/pi/Downloads/fldigi-4.1.17.06/build-aux/install-sh -d //usr/local/share/applications; \
    /usr/bin/install -c -m 644 ./../data/fldigi.desktop //usr/local/share/applications; \
fi
if test -f ./../data/NAVTEX_Stations.csv; then \
    /bin/bash /home/pi/Downloads/fldigi-4.1.17.06/build-aux/install-sh -d //usr/local/share/fldigi; \
    /usr/bin/install -c -m 644 ./../data/NAVTEX_Stations.csv //usr/local/share/fldigi; \
fi
if test -f ./../data/nsd_bbsss.txt; then \
    /bin/bash /home/pi/Downloads/fldigi-4.1.17.06/build-aux/install-sh -d //usr/local/share/fldigi; \
    /usr/bin/install -c -m 644 ./../data/nsd_bbsss.txt //usr/local/share/fldigi; \
fi
if test -f ./../data/station_table.txt; then \
    /bin/bash /home/pi/Downloads/fldigi-4.1.17.06/build-aux/install-sh -d //usr/local/share/fldigi; \
    /usr/bin/install -c -m 644 ./../data/station_table.txt //usr/local/share/fldigi; \
fi
if test -f ./../data/ToR-Stats-SHIP.csv; then \
    /bin/bash /home/pi/Downloads/fldigi-4.1.17.06/build-aux/install-sh -d //usr/local/share/fldigi; \
    /usr/bin/install -c -m 644 ./../data/ToR-Stats-SHIP.csv //usr/local/share/fldigi; \
fi
if test -f ./../data/wmo_list.txt; then \
    /bin/bash /home/pi/Downloads/fldigi-4.1.17.06/build-aux/install-sh -d //usr/local/share/fldigi; \
    /usr/bin/install -c -m 644 ./../data/wmo_list.txt //usr/local/share/fldigi; \
fi
if test -f ./../kml/styles.kml; then \
    /bin/bash /home/pi/Downloads/fldigi-4.1.17.06/build-aux/install-sh -d //usr/local/share/fldigi/kml; \
    /usr/bin/install -c -m 644 ./../kml/styles.kml //usr/local/share/fldigi/kml; \
fi
if test -f ./../data/flarq.xpm; then \
    /bin/bash /home/pi/Downloads/fldigi-4.1.17.06/build-aux/install-sh -d //usr/local/share/pixmaps; \
    /usr/bin/install -c -m 644 ./../data/flarq.xpm //usr/local/share/pixmaps; \
fi
if test -f ./../data/flarq.desktop; then \
    /bin/bash /home/pi/Downloads/fldigi-4.1.17.06/build-aux/install-sh -d //usr/local/share/applications; \
    /usr/bin/install -c -m 644 ./../data/flarq.desktop //usr/local/share/applications; \
fi
make[4]: Leaving directory '/home/pi/Downloads/fldigi-4.1.17.06/src'
make[3]: Leaving directory '/home/pi/Downloads/fldigi-4.1.17.06/src'
make[2]: Leaving directory '/home/pi/Downloads/fldigi-4.1.17.06/src'
make[1]: Leaving directory '/home/pi/Downloads/fldigi-4.1.17.06/src'
make[1]: Entering directory '/home/pi/Downloads/fldigi-4.1.17.06'
make[2]: Entering directory '/home/pi/Downloads/fldigi-4.1.17.06'
make[2]: Nothing to be done for 'install-exec-am'.
make[2]: Nothing to be done for 'install-data-am'.
make[2]: Leaving directory '/home/pi/Downloads/fldigi-4.1.17.06'
make[1]: Leaving directory '/home/pi/Downloads/fldigi-4.1.17.06'


Open a terminal enter fldigi and hit enter key and see what happens

Ed W3NR


moderated Re: Big Sur serial port naming

David, K9DWR
 

On Dec 29, 2020, at 15:48, Benjamin, ON5BGO <on5bgo@...> wrote:

Hi René,
I Already tried previous unix methods to catch usb port... the problem was the sound came well from usb but OS don't create any device in /dev.
(checked by ls -l /dev | wc -l giving me always the same result)
Don’t rely on a word count of the listing in /dev. It’s possible to have the same count, but different devices. It would be better to do a diff of the output before and after.


David Rock
david@...


moderated Re: Icom PCR-1000 not working with latest Flrig.

Dave, GØWBX
 

No Problem Dave.

I see you're busy with Flnet, among other things.

73.

Dave G0WBX

--
Created on and sent from a Unix like PC running and using free and open source software:


moderated Re: Big Sur serial port naming

Benjamin, ON5BGO
 

Hi René,
I Already tried previous unix methods to catch usb port... the problem was the sound came well from usb but OS don't create any device in /dev.
(checked by ls -l /dev  | wc -l  giving me always the same result)

Many THANKS Rene !  I'll try the new SiLabs driver as soon as possible.

73, Ben


Le mar. 29 déc. 2020 à 21:35, Rene Campbell <renecamp@...> a écrit :

I recently ran into a problem interfacing macOS Big Sir to a RigBlaster Advantage. I was able to track it down to the Silicon Labs drivers that were not compatible with the newest version of macOS. Based upon the device names I see in the above post, I think it will also require an update to the Silcon Labs Drivers.

According to this link, new version of the these drivers were released last week. However, I have not tested them in my application.

https://www.silabs.com/community/interface/forum.topic.html/vcp_driver_for_macosbigsur110x-SWJK  

I would suggest that you update to the latest drivers for Big Sir support and see if it it fixes your problem.

73, Rene KF4ZYN


moderated Re: Raspberry Pi compile of flrig and fldigi

Doug Person, KJ0F <doug@...>
 

The output of the build is huge. I don't know what an error message looks like in all the output. The end result was there was no fldigi app in the menu, on the desk top, or in /usr/local/share/applications, or anywhere else I looked.

These are the condensed steps I followed (From my notebook)

# Compile fldigi on Raspberry Pi 3

Step 1:
    # Edit the file /etc/apt/sources.list
    sudo cp /etc/apt/sources.list /etc/apt/sources.list.bak
Step 2:
    sudo apt-get install aptitude
    sudo aptitude update
Step 3:
    # Install the basic development packages
    sudo aptitude install build-essential
Step 4:
    # Install the build dependency packages
    sudo aptitude build-dep fldigi
Step 5:
    # Make sure that build-dep has installed libxft-dev.
    # Test by looking for the Xft.h header.
    # If not present: sudo aptitude install libxft-dev
    ls /usr/include/X11/Xft/Xft.h
    Result: /usr/include/X11/Xft/Xft.h
Step 6:
    # Check swapfile - Increase to 2048
    sudo nano /etc/dphys-swapfile
    CONF_SWAPSIZE=2048
    sudo /etc/init.d/dphys-swapfile stop
    sudo /etc/init.d/dphys-swapfile start
Step 7:
    # Download & unpack tarball
    ls fldigi*
    fldigi-4.1.17.06:
    ABOUT-NLS   autom4te.cache  config.log     configure.ac  doc      Makefile     NEWS    scripts
    aclocal.m4  build-aux       config.status  COPYING       INSTALL  Makefile.am  po      src
    AUTHORS     ChangeLog       configure      data          m4       Makefile.in  README
Step 8:
    # prepare the source for compilation with the configure command.
    ./configure --enable-optimizations=rpi3
Step 9:
    # If you do not find a configure script in the directory,
    # it can be re-generated using the command (I assume file name is "configure")
    autoreconf -i
Step 10:
    # Proceed to make and install fldigi and flarq.
    make && sudo make install
Step 11:
    # Install the volume manager.
    sudo aptitude install pavucontrol
Step 12:
    # Pi3 users may find the pulse sound server
    # is not started at boot. If so add the following to:
    sudo nano /home/pi/.config/lxsession/LXDE-pi/autostart
    # NOTE: Raspien Buster: File does not exist
Step 13:
    # add yourself to the dialout group.
    sudo adduser (pi) dialout

Following is the output from the make install:

pi@raspberrypi:~/Downloads/fldigi-4.1.17.06 $ sudo make install
Making install in po
make[1]: Entering directory '/home/pi/Downloads/fldigi-4.1.17.06/po'
/usr/bin/mkdir -p /usr/local/share
installing el.gmo as /usr/local/share/locale/el/LC_MESSAGES/fldigi.mo
installing es.gmo as /usr/local/share/locale/es/LC_MESSAGES/fldigi.mo
installing fr.gmo as /usr/local/share/locale/fr/LC_MESSAGES/fldigi.mo
installing it.gmo as /usr/local/share/locale/it/LC_MESSAGES/fldigi.mo
installing pl.gmo as /usr/local/share/locale/pl/LC_MESSAGES/fldigi.mo
installing de.gmo as /usr/local/share/locale/de/LC_MESSAGES/fldigi.mo
installing nl.gmo as /usr/local/share/locale/nl/LC_MESSAGES/fldigi.mo
installing ru.gmo as /usr/local/share/locale/ru/LC_MESSAGES/fldigi.mo
if test "fldigi" = "gettext-tools"; then \
  /usr/bin/mkdir -p /usr/local/share/gettext/po; \
  for file in Makefile.in.in remove-potcdate.sin quot.sed boldquot.sed en@... en@... insert-header.sin Rules-quot   Makevars.template; do \
    /usr/bin/install -c -m 644 ./$file \
            /usr/local/share/gettext/po/$file; \
  done; \
  for file in Makevars; do \
    rm -f /usr/local/share/gettext/po/$file; \
  done; \
else \
  : ; \
fi
make[1]: Leaving directory '/home/pi/Downloads/fldigi-4.1.17.06/po'
Making install in doc
make[1]: Entering directory '/home/pi/Downloads/fldigi-4.1.17.06/doc'
make[2]: Entering directory '/home/pi/Downloads/fldigi-4.1.17.06/doc'
make[2]: Nothing to be done for 'install-exec-am'.
 /usr/bin/mkdir -p '/usr/local/share/man/man1'
 /usr/bin/install -c -m 644 fldigi.1 flarq.1 '/usr/local/share/man/man1'
make[2]: Leaving directory '/home/pi/Downloads/fldigi-4.1.17.06/doc'
make[1]: Leaving directory '/home/pi/Downloads/fldigi-4.1.17.06/doc'
Making install in src
make[1]: Entering directory '/home/pi/Downloads/fldigi-4.1.17.06/src'
make  install-recursive
make[2]: Entering directory '/home/pi/Downloads/fldigi-4.1.17.06/src'
make[3]: Entering directory '/home/pi/Downloads/fldigi-4.1.17.06/src'
make[4]: Entering directory '/home/pi/Downloads/fldigi-4.1.17.06/src'
 /usr/bin/mkdir -p '/usr/local/bin'
  /usr/bin/install -c fldigi flarq '/usr/local/bin'
if test -f ./../scripts/ftp_kml_files.sh; then \
    /bin/bash /home/pi/Downloads/fldigi-4.1.17.06/build-aux/install-sh -d //usr/local/bin; \
        /usr/bin/install -c ./../scripts/ftp_kml_files.sh //usr/local/bin; \
fi
if test -f ./../data/fldigi.xpm; then \
    /bin/bash /home/pi/Downloads/fldigi-4.1.17.06/build-aux/install-sh -d //usr/local/share/pixmaps; \
    /usr/bin/install -c -m 644 ./../data/fldigi.xpm //usr/local/share/pixmaps; \
fi
if test -f ./../data/fldigi.desktop; then \
    /bin/bash /home/pi/Downloads/fldigi-4.1.17.06/build-aux/install-sh -d //usr/local/share/applications; \
    /usr/bin/install -c -m 644 ./../data/fldigi.desktop //usr/local/share/applications; \
fi
if test -f ./../data/NAVTEX_Stations.csv; then \
    /bin/bash /home/pi/Downloads/fldigi-4.1.17.06/build-aux/install-sh -d //usr/local/share/fldigi; \
    /usr/bin/install -c -m 644 ./../data/NAVTEX_Stations.csv //usr/local/share/fldigi; \
fi
if test -f ./../data/nsd_bbsss.txt; then \
    /bin/bash /home/pi/Downloads/fldigi-4.1.17.06/build-aux/install-sh -d //usr/local/share/fldigi; \
    /usr/bin/install -c -m 644 ./../data/nsd_bbsss.txt //usr/local/share/fldigi; \
fi
if test -f ./../data/station_table.txt; then \
    /bin/bash /home/pi/Downloads/fldigi-4.1.17.06/build-aux/install-sh -d //usr/local/share/fldigi; \
    /usr/bin/install -c -m 644 ./../data/station_table.txt //usr/local/share/fldigi; \
fi
if test -f ./../data/ToR-Stats-SHIP.csv; then \
    /bin/bash /home/pi/Downloads/fldigi-4.1.17.06/build-aux/install-sh -d //usr/local/share/fldigi; \
    /usr/bin/install -c -m 644 ./../data/ToR-Stats-SHIP.csv //usr/local/share/fldigi; \
fi
if test -f ./../data/wmo_list.txt; then \
    /bin/bash /home/pi/Downloads/fldigi-4.1.17.06/build-aux/install-sh -d //usr/local/share/fldigi; \
    /usr/bin/install -c -m 644 ./../data/wmo_list.txt //usr/local/share/fldigi; \
fi
if test -f ./../kml/styles.kml; then \
    /bin/bash /home/pi/Downloads/fldigi-4.1.17.06/build-aux/install-sh -d //usr/local/share/fldigi/kml; \
    /usr/bin/install -c -m 644 ./../kml/styles.kml //usr/local/share/fldigi/kml; \
fi
if test -f ./../data/flarq.xpm; then \
    /bin/bash /home/pi/Downloads/fldigi-4.1.17.06/build-aux/install-sh -d //usr/local/share/pixmaps; \
    /usr/bin/install -c -m 644 ./../data/flarq.xpm //usr/local/share/pixmaps; \
fi
if test -f ./../data/flarq.desktop; then \
    /bin/bash /home/pi/Downloads/fldigi-4.1.17.06/build-aux/install-sh -d //usr/local/share/applications; \
    /usr/bin/install -c -m 644 ./../data/flarq.desktop //usr/local/share/applications; \
fi
make[4]: Leaving directory '/home/pi/Downloads/fldigi-4.1.17.06/src'
make[3]: Leaving directory '/home/pi/Downloads/fldigi-4.1.17.06/src'
make[2]: Leaving directory '/home/pi/Downloads/fldigi-4.1.17.06/src'
make[1]: Leaving directory '/home/pi/Downloads/fldigi-4.1.17.06/src'
make[1]: Entering directory '/home/pi/Downloads/fldigi-4.1.17.06'
make[2]: Entering directory '/home/pi/Downloads/fldigi-4.1.17.06'
make[2]: Nothing to be done for 'install-exec-am'.
make[2]: Nothing to be done for 'install-data-am'.
make[2]: Leaving directory '/home/pi/Downloads/fldigi-4.1.17.06'
make[1]: Leaving directory '/home/pi/Downloads/fldigi-4.1.17.06'



On 12/28/20 9:36 PM, Dave, W1HKJ wrote:

Be sure to follow the instructions on the fldigi wiki exactly, especially take note of Pi3/4 requirements:


Special Note for Pi3 & Pi4 users with 1 GB RAM

Compiling fldigi requires more than the default swap space. You may need to increase the swap space on the microSD card. Please follow the example instructions at Pi Swap Space and use the number 2048 instead of 1024 to give 2 GB of swap. Some users have needed the larger swap space.
You are now ready to build fldigi.

73, David, W1HKJ

On 12/28/20 10:08 PM, Doug Person, KJ0F wrote:

I've tried twice to compile the latest versions flrig and fldigi. They always fail with messages that don't say much. Are the instructions still valid? I followed them carefully twice. I'm using the latest RPI linux release "buster".

I'm trying to do this for a friend who wants to operate digital on the road. I'm way out of my league trying to compile in this environment. I see many warnings coming out, and then a series of errors and it all stops.

Anyone having success on RPI3?

Thanks -- Doug -- K0DXV


6041 - 6060 of 49882