hi all, im looking for some guidelines and help on getting to compile qthid
under debian x86_64

my current libqt4 version is: 4:4.7.3-5  (It failed to compile with versions 4.6
under aka sid).

sudo aptitude show libqt4-dev
Package: libqt4-dev
State: installed
Automatically installed: no
Version: 4:4.7.3-5
Priority: optional
Section: libdevel
Maintainer: Debian Qt/KDE Maintainers <debian-qt-kde@...>
Uncompressed Size: 19.6 M
Depends: libqt4-dbus (= 4:4.7.3-5), libqt4-declarative (= 4:4.7.3-5),
libqt4-designer (= 4:4.7.3-5), libqt4-help
          (= 4:4.7.3-5), libqt4-network (= 4:4.7.3-5), libqt4-qt3support (=
4:4.7.3-5), libqt4-script (=
          4:4.7.3-5), libqt4-scripttools (= 4:4.7.3-5), libqt4-sql (= 4:4.7.3-5),
libqt4-svg (= 4:4.7.3-5),
          libqt4-test (= 4:4.7.3-5), libqt4-xml (= 4:4.7.3-5), libqt4-xmlpatterns
(= 4:4.7.3-5), libqtcore4 (=
          4:4.7.3-5), libqtgui4 (= 4:4.7.3-5), qt4-linguist-tools (= 4:4.7.3-5),
qt4-qmake (= 4:4.7.3-5), libc6
          (>= 2.3), libgcc1 (>= 1:4.1.1), libstdc++6 (>= 4.1.1), zlib1g (>=
1:1.1.4)
Recommends: libqt4-opengl-dev (= 4:4.7.3-5), libqtwebkit-dev (>= 2.0~)
Suggests: firebird2.1-dev, libmysqlclient-dev, libpq-dev, libsqlite0-dev,
libsqlite3-dev, qt4-dev-tools,
           qt4-doc, unixodbc-dev
Breaks: libqt4-opengl-dev (< 4.4.0-2), libqtwebkit-dev (< 2.0~)
Replaces: libqt4-opengl-dev (< 4.4.0-2), libqtwebkit-dev (< 2.0~)
Description: Qt 4 development files
  Qt is a cross-platform C++ application framework. Qt's primary feature is its
rich set of widgets that provide
  standard GUI functionality.

  This package contains the header development files and development programs
used for building Qt 4
  applications.
Homepage: http://qt.nokia.com/

When i try to build all, under qtcreator i get this errors:

mainwindow.cpp:568: warning: variable `fwVer' set but not used
[-Wunused-but-set-variable]

freqctrl.cpp:639: warning: variable `digchar' set but not used
[-Wunused-but-set-variable]

hid-libusb.c:337: warning: comparison between signed and unsigned integer
expressions [-Wsign-compare]

hid-libusb.c:720: warning: variable `num_devs' set but not used
[-Wunused-but-set-variable]

hid-libusb.c:1088: warning: unused parameter `dev' [-Wunused-parameter]


here is the full log based on the most recent git sources taken from here
https://github.com/csete/qthid:

Running build steps for project qthid...
Starting: /usr/bin/qmake-qt4 /home/alejo/sat-a-ware/funcube/qthid_git/qthid.pro
-spec linux-g++-64 -r CONFIG+=debug
Exited with code 0.
Starting: /usr/bin/make -w
make: Entering directory `/home/alejo/sat-a-ware/funcube/qthid_git'
/usr/bin/uic-qt4 iqbalance.ui -o ui_iqbalance.h
/usr/bin/uic-qt4 mainwindow.ui -o ui_mainwindow.h
/usr/bin/uic-qt4 fcddiagram.ui -o ui_fcddiagram.h
/usr/bin/uic-qt4 firmware.ui -o ui_firmware.h
/usr/bin/uic-qt4 dockifgain.ui -o ui_dockifgain.h
g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT
-DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED
-I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore
-I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o mainwindow.o
mainwindow.cpp
mainwindow.cpp: In member function `void MainWindow::enableControls()':
mainwindow.cpp:611:11: warning: variable `fwVer' set but not used
[-Wunused-but-set-variable]
g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT
-DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED
-I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore
-I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o main.o main.cpp
gcc -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT
-DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED
-I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore
-I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o fcd.o fcd.c
g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT
-DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED
-I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore
-I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o freqctrl.o freqctrl.cpp
freqctrl.cpp: In member function `void CFreqCtrl::DrawDigits(QPainter&)':
freqctrl.cpp:639:6: warning: variable `digchar' set but not used
[-Wunused-but-set-variable]
g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT
-DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED
-I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore
-I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o iqbalance.o iqbalance.cc
g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT
-DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED
-I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore
-I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o fcddiagram.o
fcddiagram.cpp
g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT
-DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED
-I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore
-I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o firmware.o firmware.cpp
g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT
-DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED
-I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore
-I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o dockifgain.o
dockifgain.cpp
gcc -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT
-DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED
-I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore
-I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o hid-libusb.o hid-libusb.c
hid-libusb.c: In function `get_usb_string':
hid-libusb.c:337:12: warning: comparison between signed and unsigned integer
expressions [-Wsign-compare]
hid-libusb.c: In function `hid_open_path':
hid-libusb.c:720:10: warning: variable `num_devs' set but not used
[-Wunused-but-set-variable]
hid-libusb.c: In function `hid_error':
hid-libusb.c:1088:68: warning: unused parameter `dev' [-Wunused-parameter]
/usr/bin/moc-qt4 -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB
-DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I.
-I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I.
mainwindow.h -o moc_mainwindow.cpp
g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT
-DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED
-I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore
-I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o moc_mainwindow.o
moc_mainwindow.cpp
/usr/bin/moc-qt4 -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB
-DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I.
-I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I.
freqctrl.h -o moc_freqctrl.cpp
g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT
-DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED
-I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore
-I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o moc_freqctrl.o
moc_freqctrl.cpp
/usr/bin/moc-qt4 -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB
-DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I.
-I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I.
iqbalance.h -o moc_iqbalance.cpp
g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT
-DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED
-I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore
-I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o moc_iqbalance.o
moc_iqbalance.cpp
/usr/bin/moc-qt4 -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB
-DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I.
-I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I.
fcddiagram.h -o moc_fcddiagram.cpp
g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT
-DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED
-I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore
-I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o moc_fcddiagram.o
moc_fcddiagram.cpp
/usr/bin/moc-qt4 -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB
-DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I.
-I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I.
firmware.h -o moc_firmware.cpp
g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT
-DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED
-I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore
-I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o moc_firmware.o
moc_firmware.cpp
/usr/bin/moc-qt4 -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB
-DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I.
-I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I.
dockifgain.h -o moc_dockifgain.cpp
g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT
-DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED
-I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore
-I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o moc_dockifgain.o
moc_dockifgain.cpp
/usr/bin/rcc -name qthid qthid.qrc -o qrc_qthid.cpp
g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT
-DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED
-I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore
-I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o qrc_qthid.o qrc_qthid.cpp
g++ -m64 -o qthid mainwindow.o main.o fcd.o freqctrl.o iqbalance.o fcddiagram.o
firmware.o dockifgain.o hid-libusb.o moc_mainwindow.o moc_freqctrl.o
moc_iqbalance.o moc_fcddiagram.o moc_firmware.o moc_dockifgain.o qrc_qthid.o
-L/usr/lib -lusb-1.0 -lQtGui -lQtCore -lpthread
make: Leaving directory `/home/alejo/sat-a-ware/funcube/qthid_git'
Exited with code 0.


Is there anyone out there running this software under debian?

TIA,
/a

Hi,

I've not actually compiled qthid on Debian Squeeze myself, but I have just
compiled all of gnuradio and gqrx and that all built OK on Crunchbang Linux,
which is a derivative of Debian Squeeze. To do this, I had to get the QT SDK
installer direct from Nokia and installed QT 4.7 that way.

Anyway, to the point.  Are you sure your build failed?  In the build output in
your post I see a bunch of warnings, but no errors, and the last few lines:
---
g++ -m64 -o qthid mainwindow.o main.o fcd.o freqctrl.o iqbalance.o fcddiagram.o
firmware.o dockifgain.o hid-libusb.o moc_mainwindow.o moc_freqctrl.o
moc_iqbalance.o moc_fcddiagram.o moc_firmware.o moc_dockifgain.o qrc_qthid.o
-L/usr/lib -lusb-1.0 -lQtGui -lQtCore -lpthread

make: Leaving directory `/home/alejo/sat-a-ware/funcube/qthid_git'

Exited with code 0.
---

show the object files being linked into the binary and make returning success. 
I'd be tempted to think that it all worked.

What makes you think otherwise?

Cheers,

Darren, G0HWW


--- In FCDevelopment@..., "le_lectro" <alejoduque@...> wrote:
>
> hi all, im looking for some guidelines and help on getting to compile qthid
under debian x86_64
>
> my current libqt4 version is: 4:4.7.3-5  (It failed to compile with versions
4.6 under aka sid).
>
> sudo aptitude show libqt4-dev
> Package: libqt4-dev
> State: installed
> Automatically installed: no
> Version: 4:4.7.3-5
> Priority: optional
> Section: libdevel
> Maintainer: Debian Qt/KDE Maintainers <debian-qt-kde@...>
> Uncompressed Size: 19.6 M
> Depends: libqt4-dbus (= 4:4.7.3-5), libqt4-declarative (= 4:4.7.3-5),
libqt4-designer (= 4:4.7.3-5), libqt4-help
>          (= 4:4.7.3-5), libqt4-network (= 4:4.7.3-5), libqt4-qt3support (=
4:4.7.3-5), libqt4-script (=
>          4:4.7.3-5), libqt4-scripttools (= 4:4.7.3-5), libqt4-sql (=
4:4.7.3-5), libqt4-svg (= 4:4.7.3-5),
>          libqt4-test (= 4:4.7.3-5), libqt4-xml (= 4:4.7.3-5),
libqt4-xmlpatterns (= 4:4.7.3-5), libqtcore4 (=
>          4:4.7.3-5), libqtgui4 (= 4:4.7.3-5), qt4-linguist-tools (=
4:4.7.3-5), qt4-qmake (= 4:4.7.3-5), libc6
>          (>= 2.3), libgcc1 (>= 1:4.1.1), libstdc++6 (>= 4.1.1), zlib1g (>=
1:1.1.4)
> Recommends: libqt4-opengl-dev (= 4:4.7.3-5), libqtwebkit-dev (>= 2.0~)
> Suggests: firebird2.1-dev, libmysqlclient-dev, libpq-dev, libsqlite0-dev,
libsqlite3-dev, qt4-dev-tools,
>           qt4-doc, unixodbc-dev
> Breaks: libqt4-opengl-dev (< 4.4.0-2), libqtwebkit-dev (< 2.0~)
> Replaces: libqt4-opengl-dev (< 4.4.0-2), libqtwebkit-dev (< 2.0~)
> Description: Qt 4 development files
>  Qt is a cross-platform C++ application framework. Qt's primary feature is its
rich set of widgets that provide
>  standard GUI functionality.
>
>  This package contains the header development files and development programs
used for building Qt 4
>  applications.
> Homepage: http://qt.nokia.com/
>
> When i try to build all, under qtcreator i get this errors:
>
> mainwindow.cpp:568: warning: variable `fwVer' set but not used
[-Wunused-but-set-variable]
>
> freqctrl.cpp:639: warning: variable `digchar' set but not used
[-Wunused-but-set-variable]
>
> hid-libusb.c:337: warning: comparison between signed and unsigned integer
expressions [-Wsign-compare]
>
> hid-libusb.c:720: warning: variable `num_devs' set but not used
[-Wunused-but-set-variable]
>
> hid-libusb.c:1088: warning: unused parameter `dev' [-Wunused-parameter]
>
>
> here is the full log based on the most recent git sources taken from here
https://github.com/csete/qthid:
>
> Running build steps for project qthid...
> Starting: /usr/bin/qmake-qt4
/home/alejo/sat-a-ware/funcube/qthid_git/qthid.pro -spec linux-g++-64 -r
CONFIG+=debug
> Exited with code 0.
> Starting: /usr/bin/make -w
> make: Entering directory `/home/alejo/sat-a-ware/funcube/qthid_git'
> /usr/bin/uic-qt4 iqbalance.ui -o ui_iqbalance.h
> /usr/bin/uic-qt4 mainwindow.ui -o ui_mainwindow.h
> /usr/bin/uic-qt4 fcddiagram.ui -o ui_fcddiagram.h
> /usr/bin/uic-qt4 firmware.ui -o ui_firmware.h
> /usr/bin/uic-qt4 dockifgain.ui -o ui_dockifgain.h
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT
-DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB
-DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore
-I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o mainwindow.o
mainwindow.cpp
> mainwindow.cpp: In member function `void MainWindow::enableControls()':
> mainwindow.cpp:611:11: warning: variable `fwVer' set but not used
[-Wunused-but-set-variable]
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT
-DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB
-DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore
-I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o main.o main.cpp
> gcc -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT
-DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB
-DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore
-I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o fcd.o fcd.c
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT
-DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB
-DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore
-I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o freqctrl.o freqctrl.cpp
> freqctrl.cpp: In member function `void CFreqCtrl::DrawDigits(QPainter&)':
> freqctrl.cpp:639:6: warning: variable `digchar' set but not used
[-Wunused-but-set-variable]
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT
-DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB
-DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore
-I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o iqbalance.o iqbalance.cc
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT
-DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB
-DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore
-I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o fcddiagram.o
fcddiagram.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT
-DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB
-DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore
-I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o firmware.o firmware.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT
-DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB
-DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore
-I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o dockifgain.o
dockifgain.cpp
> gcc -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT
-DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB
-DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore
-I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o hid-libusb.o hid-libusb.c
> hid-libusb.c: In function `get_usb_string':
> hid-libusb.c:337:12: warning: comparison between signed and unsigned integer
expressions [-Wsign-compare]
> hid-libusb.c: In function `hid_open_path':
> hid-libusb.c:720:10: warning: variable `num_devs' set but not used
[-Wunused-but-set-variable]
> hid-libusb.c: In function `hid_error':
> hid-libusb.c:1088:68: warning: unused parameter `dev' [-Wunused-parameter]
> /usr/bin/moc-qt4 -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB
-DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I.
-I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I.
mainwindow.h -o moc_mainwindow.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT
-DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB
-DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore
-I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o moc_mainwindow.o
moc_mainwindow.cpp
> /usr/bin/moc-qt4 -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB
-DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I.
-I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I.
freqctrl.h -o moc_freqctrl.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT
-DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB
-DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore
-I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o moc_freqctrl.o
moc_freqctrl.cpp
> /usr/bin/moc-qt4 -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB
-DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I.
-I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I.
iqbalance.h -o moc_iqbalance.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT
-DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB
-DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore
-I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o moc_iqbalance.o
moc_iqbalance.cpp
> /usr/bin/moc-qt4 -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB
-DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I.
-I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I.
fcddiagram.h -o moc_fcddiagram.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT
-DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB
-DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore
-I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o moc_fcddiagram.o
moc_fcddiagram.cpp
> /usr/bin/moc-qt4 -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB
-DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I.
-I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I.
firmware.h -o moc_firmware.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT
-DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB
-DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore
-I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o moc_firmware.o
moc_firmware.cpp
> /usr/bin/moc-qt4 -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB
-DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I.
-I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I.
dockifgain.h -o moc_dockifgain.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT
-DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB
-DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore
-I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o moc_dockifgain.o
moc_dockifgain.cpp
> /usr/bin/rcc -name qthid qthid.qrc -o qrc_qthid.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT
-DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB
-DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore
-I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o qrc_qthid.o qrc_qthid.cpp
> g++ -m64 -o qthid mainwindow.o main.o fcd.o freqctrl.o iqbalance.o
fcddiagram.o firmware.o dockifgain.o hid-libusb.o moc_mainwindow.o
moc_freqctrl.o moc_iqbalance.o moc_fcddiagram.o moc_firmware.o moc_dockifgain.o
qrc_qthid.o -L/usr/lib -lusb-1.0 -lQtGui -lQtCore -lpthread
> make: Leaving directory `/home/alejo/sat-a-ware/funcube/qthid_git'
> Exited with code 0.
>
>
> Is there anyone out there running this software under debian?
>
> TIA,
> /a
>

I've been having this issue persistently on an EEE-901 netbook running
Crunchbang Linux Statler distro (a derivative of Debian Squeeze).

The FCD seems to work  on the netbook OK with gnuradio-companion, but I
get the stream of "aUaO" characters, the occasional "I/Q: nan/nan" and a
pretty pink waterfall in gqrx. I can run gnuradio-companion immediately
after failing with gqrx and its all good.

Running "cat /proc/asound/cards" shows the FCD on hw:1 as expected.

I've got it all working on a Ubuntu 10.04 machine including gqrx, so I'm
familiar enough with  the process.  I've been building gqrx from git in
QT-Creator.

The netbook didn't formerly have pulseaudio installed.  I satisfied the
build deps by installing it, but otherwise have done nothing special to
configure pulse on the netbook.

Can you offer any clues?  If you're making changes to gqrx to mitigate
this issue, and need beta testers, I'd be happy to help.

Cheers,

Darren, G0HWW



--- In FCDevelopment@..., Simon Kennedy <simon@...> wrote:
>
> Hi Alex,
>
> unfortunately it doesn't disappear after a reboot here, but the
problem
> with the FCD taking device 0 is annoying because it seems that other
> programs, like Quisk, expect the output sound device to be on hw:0. It
> seems like an entry in a file in /etc/modprobe.d can fix that but I
> haven't looked into it enough to work out how.
>
> I look forward to your new audio backend.
>
> Simon.
>
> On 17/11/11 17:24, Alexandru Csete wrote:
> >
> > Hi Simon,
> >
> > Concerning the audio overrun (aOaO...) issue, I have seen it a few
> > times on a laptop but it always disappears after reboot. I suspect
it
> > is a hardware and/or driver issue but I don't have sufficient info
to
> > find out more about it.
> >
> > I am working on a new audio backend for gqrx which will hopefully
> > eliminate both the aO issue and the problem with changing device
names.
> >
> > Alex
> >
> >
>

 

Hi Darren, many thanks for your reply,

You are right, it all looks like it compiled OK but i get random segfaults when qthid is opened.

I have tried to explain the issue to the developer of the software but i guess i've been just an annoyance.

(no user, no cry! :D ) 

a week ago i was told this:

Reply
 Alex Csete 6 days ago

Ok, now it makes more sense: It builds fine but crashes at runtime. Note that the "frequency hopping" code was indeed causing crash on linux so I removed it again from the latest code in the git repository.

First and foremost, I would recommend you to try to build and execute the latest official release 3.1. If it builds and runs fine we would at least know that your installation is fine and it is indeed changes in the qthid code that cause crashes.

In order to get debug information in qthid you can try the following:
- Ensure that the selected target id "Debug" and not release (one of the buttons in the lower left corner)
- Execute qthid within the qtcreator debugger (the run button in the lower left corner with the little bug on it)

---

I've sent some debug info but got no answer yet and the git sources have not been updated yet, last one happened on:  csete authored January 01, 2012

so I guess I will just have to wait and see if some other debian wheezy users hit the same wall.

I had compiled many times the git sources under (X)(K)Bubuntu but after their latest version I had no other option than migrating to debian. Where i have compiled many other qt applications and even got wine from git so to use spectravue to control the FCD.

I have to be quick on setting the freq before qthid segfaults, and this happens with the latest stable binary version also.

So yes, in my experience qthid compiles under ubuntu but not under debian.. for sure is something related to versions.. i will try getting the sources from Nokia.

Again many thanks for your help Darren.

73

  

On Tue, Jan 10, 2012 at 10:25 AM, <FCDevelopment@...> wrote:

There are 2 messages in this issue.

Topics in this digest:

1.1. Re: failing to compile qthid (from git sources) under debian stable
   From: g0hww

2.1. Re: Gqrx problem
   From: g0hww


Messages
________________________________________________________________________
1.1. Re: failing to compile qthid (from git sources) under debian stable
   Posted by: "g0hww" darren.long@... g0hww
   Date: Mon Jan 9, 2012 10:19 pm

Hi,

I've not actually compiled qthid on Debian Squeeze myself, but I have just compiled all of gnuradio and gqrx and that all built OK on Crunchbang Linux, which is a derivative of Debian Squeeze. To do this, I had to get the QT SDK installer direct from Nokia and installed QT 4.7 that way.

Anyway, to the point.  Are you sure your build failed?  In the build output in your post I see a bunch of warnings, but no errors, and the last few lines:
---
g++ -m64 -o qthid mainwindow.o main.o fcd.o freqctrl.o iqbalance.o fcddiagram.o firmware.o dockifgain.o hid-libusb.o moc_mainwindow.o moc_freqctrl.o moc_iqbalance.o moc_fcddiagram.o moc_firmware.o moc_dockifgain.o qrc_qthid.o -L/usr/lib -lusb-1.0 -lQtGui -lQtCore -lpthread

make: Leaving directory `/home/alejo/sat-a-ware/funcube/qthid_git'

Exited with code 0.
---

show the object files being linked into the binary and make returning success.  I'd be tempted to think that it all worked.

What makes you think otherwise?

Cheers,

Darren, G0HWW


--- In FCDevelopment@..., "le_lectro" <alejoduque@...> wrote:
>
> hi all, im looking for some guidelines and help on getting to compile qthid under debian x86_64
>
> my current libqt4 version is: 4:4.7.3-5  (It failed to compile with versions 4.6 under aka sid).
>
> sudo aptitude show libqt4-dev
> Package: libqt4-dev
> State: installed
> Automatically installed: no
> Version: 4:4.7.3-5
> Priority: optional
> Section: libdevel
> Maintainer: Debian Qt/KDE Maintainers <debian-qt-kde@...>
> Uncompressed Size: 19.6 M
> Depends: libqt4-dbus (= 4:4.7.3-5), libqt4-declarative (= 4:4.7.3-5), libqt4-designer (= 4:4.7.3-5), libqt4-help
>          (= 4:4.7.3-5), libqt4-network (= 4:4.7.3-5), libqt4-qt3support (= 4:4.7.3-5), libqt4-script (=
>          4:4.7.3-5), libqt4-scripttools (= 4:4.7.3-5), libqt4-sql (= 4:4.7.3-5), libqt4-svg (= 4:4.7.3-5),
>          libqt4-test (= 4:4.7.3-5), libqt4-xml (= 4:4.7.3-5), libqt4-xmlpatterns (= 4:4.7.3-5), libqtcore4 (=
>          4:4.7.3-5), libqtgui4 (= 4:4.7.3-5), qt4-linguist-tools (= 4:4.7.3-5), qt4-qmake (= 4:4.7.3-5), libc6
>          (>= 2.3), libgcc1 (>= 1:4.1.1), libstdc++6 (>= 4.1.1), zlib1g (>= 1:1.1.4)
> Recommends: libqt4-opengl-dev (= 4:4.7.3-5), libqtwebkit-dev (>= 2.0~)
> Suggests: firebird2.1-dev, libmysqlclient-dev, libpq-dev, libsqlite0-dev, libsqlite3-dev, qt4-dev-tools,
>           qt4-doc, unixodbc-dev
> Breaks: libqt4-opengl-dev (< 4.4.0-2), libqtwebkit-dev (< 2.0~)
> Replaces: libqt4-opengl-dev (< 4.4.0-2), libqtwebkit-dev (< 2.0~)
> Description: Qt 4 development files
>  Qt is a cross-platform C++ application framework. Qt's primary feature is its rich set of widgets that provide
>  standard GUI functionality.
>
>  This package contains the header development files and development programs used for building Qt 4
>  applications.
> Homepage: http://qt.nokia.com/
>
> When i try to build all, under qtcreator i get this errors:
>
> mainwindow.cpp:568: warning: variable `fwVer' set but not used [-Wunused-but-set-variable]
>
> freqctrl.cpp:639: warning: variable `digchar' set but not used [-Wunused-but-set-variable]
>
> hid-libusb.c:337: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
>
> hid-libusb.c:720: warning: variable `num_devs' set but not used [-Wunused-but-set-variable]
>
> hid-libusb.c:1088: warning: unused parameter `dev' [-Wunused-parameter]
>
>
> here is the full log based on the most recent git sources taken from here https://github.com/csete/qthid:
>
> Running build steps for project qthid...
> Starting: /usr/bin/qmake-qt4 /home/alejo/sat-a-ware/funcube/qthid_git/qthid.pro -spec linux-g++-64 -r CONFIG+=debug
> Exited with code 0.
> Starting: /usr/bin/make -w
> make: Entering directory `/home/alejo/sat-a-ware/funcube/qthid_git'
> /usr/bin/uic-qt4 iqbalance.ui -o ui_iqbalance.h
> /usr/bin/uic-qt4 mainwindow.ui -o ui_mainwindow.h
> /usr/bin/uic-qt4 fcddiagram.ui -o ui_fcddiagram.h
> /usr/bin/uic-qt4 firmware.ui -o ui_firmware.h
> /usr/bin/uic-qt4 dockifgain.ui -o ui_dockifgain.h
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o mainwindow.o mainwindow.cpp
> mainwindow.cpp: In member function `void MainWindow::enableControls()':
> mainwindow.cpp:611:11: warning: variable `fwVer' set but not used [-Wunused-but-set-variable]
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o main.o main.cpp
> gcc -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o fcd.o fcd.c
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o freqctrl.o freqctrl.cpp
> freqctrl.cpp: In member function `void CFreqCtrl::DrawDigits(QPainter&)':
> freqctrl.cpp:639:6: warning: variable `digchar' set but not used [-Wunused-but-set-variable]
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o iqbalance.o iqbalance.cc
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o fcddiagram.o fcddiagram.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o firmware.o firmware.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o dockifgain.o dockifgain.cpp
> gcc -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o hid-libusb.o hid-libusb.c
> hid-libusb.c: In function `get_usb_string':
> hid-libusb.c:337:12: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
> hid-libusb.c: In function `hid_open_path':
> hid-libusb.c:720:10: warning: variable `num_devs' set but not used [-Wunused-but-set-variable]
> hid-libusb.c: In function `hid_error':
> hid-libusb.c:1088:68: warning: unused parameter `dev' [-Wunused-parameter]
> /usr/bin/moc-qt4 -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. mainwindow.h -o moc_mainwindow.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o moc_mainwindow.o moc_mainwindow.cpp
> /usr/bin/moc-qt4 -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. freqctrl.h -o moc_freqctrl.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o moc_freqctrl.o moc_freqctrl.cpp
> /usr/bin/moc-qt4 -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. iqbalance.h -o moc_iqbalance.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o moc_iqbalance.o moc_iqbalance.cpp
> /usr/bin/moc-qt4 -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. fcddiagram.h -o moc_fcddiagram.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o moc_fcddiagram.o moc_fcddiagram.cpp
> /usr/bin/moc-qt4 -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. firmware.h -o moc_firmware.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o moc_firmware.o moc_firmware.cpp
> /usr/bin/moc-qt4 -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. dockifgain.h -o moc_dockifgain.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o moc_dockifgain.o moc_dockifgain.cpp
> /usr/bin/rcc -name qthid qthid.qrc -o qrc_qthid.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o qrc_qthid.o qrc_qthid.cpp
> g++ -m64 -o qthid mainwindow.o main.o fcd.o freqctrl.o iqbalance.o fcddiagram.o firmware.o dockifgain.o hid-libusb.o moc_mainwindow.o moc_freqctrl.o moc_iqbalance.o moc_fcddiagram.o moc_firmware.o moc_dockifgain.o qrc_qthid.o -L/usr/lib -lusb-1.0 -lQtGui -lQtCore -lpthread
> make: Leaving directory `/home/alejo/sat-a-ware/funcube/qthid_git'
> Exited with code 0.
>
>
> Is there anyone out there running this software under debian?
>
> TIA,
> /a
>







Messages in this topic (2)
________________________________________________________________________
________________________________________________________________________
2.1. Re: Gqrx problem
   Posted by: "g0hww" darren.long@... g0hww
   Date: Mon Jan 9, 2012 11:37 pm

I've been having this issue persistently on an EEE-901 netbook running
Crunchbang Linux Statler distro (a derivative of Debian Squeeze).

The FCD seems to work  on the netbook OK with gnuradio-companion, but I
get the stream of "aUaO" characters, the occasional "I/Q: nan/nan" and a
pretty pink waterfall in gqrx. I can run gnuradio-companion immediately
after failing with gqrx and its all good.

Running "cat /proc/asound/cards" shows the FCD on hw:1 as expected.

I've got it all working on a Ubuntu 10.04 machine including gqrx, so I'm
familiar enough with  the process.  I've been building gqrx from git in
QT-Creator.

The netbook didn't formerly have pulseaudio installed.  I satisfied the
build deps by installing it, but otherwise have done nothing special to
configure pulse on the netbook.

Can you offer any clues?  If you're making changes to gqrx to mitigate
this issue, and need beta testers, I'd be happy to help.

Cheers,

Darren, G0HWW



--- In FCDevelopment@..., Simon Kennedy <simon@...> wrote:
>
> Hi Alex,
>
> unfortunately it doesn't disappear after a reboot here, but the
problem
> with the FCD taking device 0 is annoying because it seems that other
> programs, like Quisk, expect the output sound device to be on hw:0. It
> seems like an entry in a file in /etc/modprobe.d can fix that but I
> haven't looked into it enough to work out how.
>
> I look forward to your new audio backend.
>
> Simon.
>
> On 17/11/11 17:24, Alexandru Csete wrote:
> >
> > Hi Simon,
> >
> > Concerning the audio overrun (aOaO...) issue, I have seen it a few
> > times on a laptop but it always disappears after reboot. I suspect
it
> > is a hardware and/or driver issue but I don't have sufficient info
to
> > find out more about it.
> >
> > I am working on a new audio backend for gqrx which will hopefully
> > eliminate both the aO issue and the problem with changing device
names.
> >
> > Alex
> >
> >
>







Messages in this topic (4)





------------------------------------------------------------------------
Yahoo! Groups Links

<*> To visit your group on the web, go to:
   http://uk.groups.yahoo.com/group/FCDevelopment/

<*> Your email settings:
   Digest Email  | Traditional

<*> To change settings online go to:
   http://uk.groups.yahoo.com/group/FCDevelopment/join
   (Yahoo! ID required)

<*> To change settings via email:
   FCDevelopment-normal@...
   FCDevelopment-fullfeatured@...

<*> To unsubscribe from this group, send an email to:
   FCDevelopment-unsubscribe@...

<*> Your use of Yahoo! Groups is subject to:
   http://uk.docs.yahoo.com/info/terms.html

------------------------------------------------------------------------

--
http://trueque.labsurlab.co/
https://n-1.cc/pg/profile/alejo

 

Hi again.

I've just built qthid 3.1 from git source on the netbook and it seems to be working ok for me. I've just done a quick functional check using baudline to show the spectrum and it seems to have tuned to the frequency ok.

Just to confirm, this is built with Nokia's QT SDK  4.7.4 on Crunchbang Statler which is effectively Debian Squeeze. FCD FW is 18.09.

Cheers

Darren, G0HWW

On 10 Jan 2012, at 16:19, alejo d <alejoduque@...> wrote:

 

Hi Darren, many thanks for your reply,

You are right, it all looks like it compiled OK but i get random segfaults when qthid is opened.

I have tried to explain the issue to the developer of the software but i guess i've been just an annoyance.

(no user, no cry! :D ) 

a week ago i was told this:

Reply
 Alex Csete 6 days ago

Ok, now it makes more sense: It builds fine but crashes at runtime. Note that the "frequency hopping" code was indeed causing crash on linux so I removed it again from the latest code in the git repository.

First and foremost, I would recommend you to try to build and execute the latest official release 3.1. If it builds and runs fine we would at least know that your installation is fine and it is indeed changes in the qthid code that cause crashes.

In order to get debug information in qthid you can try the following:
- Ensure that the selected target id "Debug" and not release (one of the buttons in the lower left corner)
- Execute qthid within the qtcreator debugger (the run button in the lower left corner with the little bug on it)

---

I've sent some debug info but got no answer yet and the git sources have not been updated yet, last one happened on:  csete authored January 01, 2012

so I guess I will just have to wait and see if some other debian wheezy users hit the same wall.

I had compiled many times the git sources under (X)(K)Bubuntu but after their latest version I had no other option than migrating to debian. Where i have compiled many other qt applications and even got wine from git so to use spectravue to control the FCD.

I have to be quick on setting the freq before qthid segfaults, and this happens with the latest stable binary version also.

So yes, in my experience qthid compiles under ubuntu but not under debian.. for sure is something related to versions.. i will try getting the sources from Nokia.

Again many thanks for your help Darren.

73

  

On Tue, Jan 10, 2012 at 10:25 AM, <FCDevelopment@...> wrote:

There are 2 messages in this issue.

Topics in this digest:

1.1. Re: failing to compile qthid (from git sources) under debian stable
   From: g0hww

2.1. Re: Gqrx problem
   From: g0hww


Messages
________________________________________________________________________
1.1. Re: failing to compile qthid (from git sources) under debian stable
   Posted by: "g0hww" darren.long@... g0hww
   Date: Mon Jan 9, 2012 10:19 pm

Hi,

I've not actually compiled qthid on Debian Squeeze myself, but I have just compiled all of gnuradio and gqrx and that all built OK on Crunchbang Linux, which is a derivative of Debian Squeeze. To do this, I had to get the QT SDK installer direct from Nokia and installed QT 4.7 that way.

Anyway, to the point.  Are you sure your build failed?  In the build output in your post I see a bunch of warnings, but no errors, and the last few lines:
---
g++ -m64 -o qthid mainwindow.o main.o fcd.o freqctrl.o iqbalance.o fcddiagram.o firmware.o dockifgain.o hid-libusb.o moc_mainwindow.o moc_freqctrl.o moc_iqbalance.o moc_fcddiagram.o moc_firmware.o moc_dockifgain.o qrc_qthid.o -L/usr/lib -lusb-1.0 -lQtGui -lQtCore -lpthread

make: Leaving directory `/home/alejo/sat-a-ware/funcube/qthid_git'

Exited with code 0.
---

show the object files being linked into the binary and make returning success.  I'd be tempted to think that it all worked.

What makes you think otherwise?

Cheers,

Darren, G0HWW


--- In FCDevelopment@..., "le_lectro" <alejoduque@...> wrote:
>
> hi all, im looking for some guidelines and help on getting to compile qthid under debian x86_64
>
> my current libqt4 version is: 4:4.7.3-5  (It failed to compile with versions 4.6 under aka sid).
>
> sudo aptitude show libqt4-dev
> Package: libqt4-dev
> State: installed
> Automatically installed: no
> Version: 4:4.7.3-5
> Priority: optional
> Section: libdevel
> Maintainer: Debian Qt/KDE Maintainers <debian-qt-kde@...>
> Uncompressed Size: 19.6 M
> Depends: libqt4-dbus (= 4:4.7.3-5), libqt4-declarative (= 4:4.7.3-5), libqt4-designer (= 4:4.7.3-5), libqt4-help
>          (= 4:4.7.3-5), libqt4-network (= 4:4.7.3-5), libqt4-qt3support (= 4:4.7.3-5), libqt4-script (=
>          4:4.7.3-5), libqt4-scripttools (= 4:4.7.3-5), libqt4-sql (= 4:4.7.3-5), libqt4-svg (= 4:4.7.3-5),
>          libqt4-test (= 4:4.7.3-5), libqt4-xml (= 4:4.7.3-5), libqt4-xmlpatterns (= 4:4.7.3-5), libqtcore4 (=
>          4:4.7.3-5), libqtgui4 (= 4:4.7.3-5), qt4-linguist-tools (= 4:4.7.3-5), qt4-qmake (= 4:4.7.3-5), libc6
>          (>= 2.3), libgcc1 (>= 1:4.1.1), libstdc++6 (>= 4.1.1), zlib1g (>= 1:1.1.4)
> Recommends: libqt4-opengl-dev (= 4:4.7.3-5), libqtwebkit-dev (>= 2.0~)
> Suggests: firebird2.1-dev, libmysqlclient-dev, libpq-dev, libsqlite0-dev, libsqlite3-dev, qt4-dev-tools,
>           qt4-doc, unixodbc-dev
> Breaks: libqt4-opengl-dev (< 4.4.0-2), libqtwebkit-dev (< 2.0~)
> Replaces: libqt4-opengl-dev (< 4.4.0-2), libqtwebkit-dev (< 2.0~)
> Description: Qt 4 development files
>  Qt is a cross-platform C++ application framework. Qt's primary feature is its rich set of widgets that provide
>  standard GUI functionality.
>
>  This package contains the header development files and development programs used for building Qt 4
>  applications.
> Homepage: http://qt.nokia.com/
>
> When i try to build all, under qtcreator i get this errors:
>
> mainwindow.cpp:568: warning: variable `fwVer' set but not used [-Wunused-but-set-variable]
>
> freqctrl.cpp:639: warning: variable `digchar' set but not used [-Wunused-but-set-variable]
>
> hid-libusb.c:337: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
>
> hid-libusb.c:720: warning: variable `num_devs' set but not used [-Wunused-but-set-variable]
>
> hid-libusb.c:1088: warning: unused parameter `dev' [-Wunused-parameter]
>
>
> here is the full log based on the most recent git sources taken from here https://github.com/csete/qthid:
>
> Running build steps for project qthid...
> Starting: /usr/bin/qmake-qt4 /home/alejo/sat-a-ware/funcube/qthid_git/qthid.pro -spec linux-g++-64 -r CONFIG+=debug
> Exited with code 0.
> Starting: /usr/bin/make -w
> make: Entering directory `/home/alejo/sat-a-ware/funcube/qthid_git'
> /usr/bin/uic-qt4 iqbalance.ui -o ui_iqbalance.h
> /usr/bin/uic-qt4 mainwindow.ui -o ui_mainwindow.h
> /usr/bin/uic-qt4 fcddiagram.ui -o ui_fcddiagram.h
> /usr/bin/uic-qt4 firmware.ui -o ui_firmware.h
> /usr/bin/uic-qt4 dockifgain.ui -o ui_dockifgain.h
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o mainwindow.o mainwindow.cpp
> mainwindow.cpp: In member function `void MainWindow::enableControls()':
> mainwindow.cpp:611:11: warning: variable `fwVer' set but not used [-Wunused-but-set-variable]
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o main.o main.cpp
> gcc -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o fcd.o fcd.c
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o freqctrl.o freqctrl.cpp
> freqctrl.cpp: In member function `void CFreqCtrl::DrawDigits(QPainter&)':
> freqctrl.cpp:639:6: warning: variable `digchar' set but not used [-Wunused-but-set-variable]
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o iqbalance.o iqbalance.cc
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o fcddiagram.o fcddiagram.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o firmware.o firmware.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o dockifgain.o dockifgain.cpp
> gcc -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o hid-libusb.o hid-libusb.c
> hid-libusb.c: In function `get_usb_string':
> hid-libusb.c:337:12: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
> hid-libusb.c: In function `hid_open_path':
> hid-libusb.c:720:10: warning: variable `num_devs' set but not used [-Wunused-but-set-variable]
> hid-libusb.c: In function `hid_error':
> hid-libusb.c:1088:68: warning: unused parameter `dev' [-Wunused-parameter]
> /usr/bin/moc-qt4 -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. mainwindow.h -o moc_mainwindow.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o moc_mainwindow.o moc_mainwindow.cpp
> /usr/bin/moc-qt4 -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. freqctrl.h -o moc_freqctrl.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o moc_freqctrl.o moc_freqctrl.cpp
> /usr/bin/moc-qt4 -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. iqbalance.h -o moc_iqbalance.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o moc_iqbalance.o moc_iqbalance.cpp
> /usr/bin/moc-qt4 -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. fcddiagram.h -o moc_fcddiagram.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o moc_fcddiagram.o moc_fcddiagram.cpp
> /usr/bin/moc-qt4 -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. firmware.h -o moc_firmware.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o moc_firmware.o moc_firmware.cpp
> /usr/bin/moc-qt4 -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. dockifgain.h -o moc_dockifgain.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o moc_dockifgain.o moc_dockifgain.cpp
> /usr/bin/rcc -name qthid qthid.qrc -o qrc_qthid.cpp
> g++ -c -m64 -pipe -g -I/usr/include/libusb-1.0 -Wall -W -D_REENTRANT -DQT_WEBKIT -DVERSION="\"v3.1-26-g91cb1a85\"" -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I. -I. -o qrc_qthid.o qrc_qthid.cpp
> g++ -m64 -o qthid mainwindow.o main.o fcd.o freqctrl.o iqbalance.o fcddiagram.o firmware.o dockifgain.o hid-libusb.o moc_mainwindow.o moc_freqctrl.o moc_iqbalance.o moc_fcddiagram.o moc_firmware.o moc_dockifgain.o qrc_qthid.o -L/usr/lib -lusb-1.0 -lQtGui -lQtCore -lpthread
> make: Leaving directory `/home/alejo/sat-a-ware/funcube/qthid_git'
> Exited with code 0.
>
>
> Is there anyone out there running this software under debian?
>
> TIA,
> /a
>







Messages in this topic (2)
________________________________________________________________________
________________________________________________________________________
2.1. Re: Gqrx problem
   Posted by: "g0hww" darren.long@... g0hww
   Date: Mon Jan 9, 2012 11:37 pm

I've been having this issue persistently on an EEE-901 netbook running
Crunchbang Linux Statler distro (a derivative of Debian Squeeze).

The FCD seems to work  on the netbook OK with gnuradio-companion, but I
get the stream of "aUaO" characters, the occasional "I/Q: nan/nan" and a
pretty pink waterfall in gqrx. I can run gnuradio-companion immediately
after failing with gqrx and its all good.

Running "cat /proc/asound/cards" shows the FCD on hw:1 as expected.

I've got it all working on a Ubuntu 10.04 machine including gqrx, so I'm
familiar enough with  the process.  I've been building gqrx from git in
QT-Creator.

The netbook didn't formerly have pulseaudio installed.  I satisfied the
build deps by installing it, but otherwise have done nothing special to
configure pulse on the netbook.

Can you offer any clues?  If you're making changes to gqrx to mitigate
this issue, and need beta testers, I'd be happy to help.

Cheers,

Darren, G0HWW



--- In FCDevelopment@..., Simon Kennedy <simon@...> wrote:
>
> Hi Alex,
>
> unfortunately it doesn't disappear after a reboot here, but the
problem
> with the FCD taking device 0 is annoying because it seems that other
> programs, like Quisk, expect the output sound device to be on hw:0. It
> seems like an entry in a file in /etc/modprobe.d can fix that but I
> haven't looked into it enough to work out how.
>
> I look forward to your new audio backend.
>
> Simon.
>
> On 17/11/11 17:24, Alexandru Csete wrote:
> >
> > Hi Simon,
> >
> > Concerning the audio overrun (aOaO...) issue, I have seen it a few
> > times on a laptop but it always disappears after reboot. I suspect
it
> > is a hardware and/or driver issue but I don't have sufficient info
to
> > find out more about it.
> >
> > I am working on a new audio backend for gqrx which will hopefully
> > eliminate both the aO issue and the problem with changing device
names.
> >
> > Alex
> >
> >
>







Messages in this topic (4)





------------------------------------------------------------------------
Yahoo! Groups Links

<*> To visit your group on the web, go to:
   http://uk.groups.yahoo.com/group/FCDevelopment/

<*> Your email settings:
   Digest Email  | Traditional

<*> To change settings online go to:
   http://uk.groups.yahoo.com/group/FCDevelopment/join
   (Yahoo! ID required)

<*> To change settings via email:
   FCDevelopment-normal@...
   FCDevelopment-fullfeatured@...

<*> To unsubscribe from this group, send an email to:
   FCDevelopment-unsubscribe@...

<*> Your use of Yahoo! Groups is subject to:
   http://uk.docs.yahoo.com/info/terms.html

------------------------------------------------------------------------

--
http://trueque.labsurlab.co/
https://n-1.cc/pg/profile/alejo

Hi Darren,

It can also be an issue with the output device. Note that the recent
code autodetects the FCD and it doesn't matter what you type in the
input device field.

Try in grc the simple dial tone flow graph at 48 kHz, then if it works
use the same output device in gqrx.

Since gqrx doesn't do any interfacing to audio hardware or drivers (it
only uses gnuradio), the only thing I can do about it is to debug the
obsolete interface in gnuradio or to write my own audio backend. I
have planned to do the latter but given how much time I have left for
coding these days, I doubt it will happen anytime soon.

Alex


On Tue, Jan 10, 2012 at 12:36 AM, g0hww <darren.long@...> wrote:
> I've been having this issue persistently on an EEE-901 netbook running
> Crunchbang Linux Statler distro (a derivative of Debian Squeeze).
>
> The FCD seems to work  on the netbook OK with gnuradio-companion, but I
> get the stream of "aUaO" characters, the occasional "I/Q: nan/nan" and a
> pretty pink waterfall in gqrx. I can run gnuradio-companion immediately
> after failing with gqrx and its all good.
>
> Running "cat /proc/asound/cards" shows the FCD on hw:1 as expected.
>
> I've got it all working on a Ubuntu 10.04 machine including gqrx, so I'm
> familiar enough with  the process.  I've been building gqrx from git in
> QT-Creator.
>
> The netbook didn't formerly have pulseaudio installed.  I satisfied the
> build deps by installing it, but otherwise have done nothing special to
> configure pulse on the netbook.
>
> Can you offer any clues?  If you're making changes to gqrx to mitigate
> this issue, and need beta testers, I'd be happy to help.
>
> Cheers,
>
> Darren, G0HWW
>
>
>
> --- In FCDevelopment@..., Simon Kennedy <simon@...> wrote:
>>
>> Hi Alex,
>>
>> unfortunately it doesn't disappear after a reboot here, but the
> problem
>> with the FCD taking device 0 is annoying because it seems that other
>> programs, like Quisk, expect the output sound device to be on hw:0. It
>> seems like an entry in a file in /etc/modprobe.d can fix that but I
>> haven't looked into it enough to work out how.
>>
>> I look forward to your new audio backend.
>>
>> Simon.
>>
>> On 17/11/11 17:24, Alexandru Csete wrote:
>> >
>> > Hi Simon,
>> >
>> > Concerning the audio overrun (aOaO...) issue, I have seen it a few
>> > times on a laptop but it always disappears after reboot. I suspect
> it
>> > is a hardware and/or driver issue but I don't have sufficient info
> to
>> > find out more about it.
>> >
>> > I am working on a new audio backend for gqrx which will hopefully
>> > eliminate both the aO issue and the problem with changing device
> names.
>> >
>> > Alex
>> >
>> >
>>
>
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>

 

Hi Darren,

It can also be an issue with the output device. Note that the recent
code autodetects the FCD and it doesn't matter what you type in the
input device field.

Try in grc the simple dial tone flow graph at 48 kHz, then if it works
use the same output device in gqrx.

Since gqrx doesn't do any interfacing to audio hardware or drivers (it
only uses gnuradio), the only thing I can do about it is to debug the
obsolete interface in gnuradio or to write my own audio backend. I
have planned to do the latter but given how much time I have left for
coding these days, I doubt it will happen anytime soon.

Alex

On Tue, Jan 10, 2012 at 12:36 AM, g0hww <darren.long@...> wrote:
> I've been having this issue persistently on an EEE-901 netbook running
> Crunchbang Linux Statler distro (a derivative of Debian Squeeze).
>
> The FCD seems to work  on the netbook OK with gnuradio-companion, but I
> get the stream of "aUaO" characters, the occasional "I/Q: nan/nan" and a
> pretty pink waterfall in gqrx. I can run gnuradio-companion immediately
> after failing with gqrx and its all good.
>
> Running "cat /proc/asound/cards" shows the FCD on hw:1 as expected.
>
> I've got it all working on a Ubuntu 10.04 machine including gqrx, so I'm
> familiar enough with  the process.  I've been building gqrx from git in
> QT-Creator.
>
> The netbook didn't formerly have pulseaudio installed.  I satisfied the
> build deps by installing it, but otherwise have done nothing special to
> configure pulse on the netbook.
>
> Can you offer any clues?  If you're making changes to gqrx to mitigate
> this issue, and need beta testers, I'd be happy to help.
>
> Cheers,
>
> Darren, G0HWW
>
>
>
> --- In FCDevelopment@..., Simon Kennedy <simon@...> wrote:
>>
>> Hi Alex,
>>
>> unfortunately it doesn't disappear after a reboot here, but the
> problem
>> with the FCD taking device 0 is annoying because it seems that other
>> programs, like Quisk, expect the output sound device to be on hw:0. It
>> seems like an entry in a file in /etc/modprobe.d can fix that but I
>> haven't looked into it enough to work out how.
>>
>> I look forward to your new audio backend.
>>
>> Simon.
>>
>> On 17/11/11 17:24, Alexandru Csete wrote:
>> >
>> > Hi Simon,
>> >
>> > Concerning the audio overrun (aOaO...) issue, I have seen it a few
>> > times on a laptop but it always disappears after reboot. I suspect
> it
>> > is a hardware and/or driver issue but I don't have sufficient info
> to
>> > find out more about it.
>> >
>> > I am working on a new audio backend for gqrx which will hopefully
>> > eliminate both the aO issue and the problem with changing device
> names.
>> >
>> > Alex
>> >
>> >
>>
>
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>

 

Hi Alex,

Thanks for the response.  Sorry to bother you with this. 

I tried the dial_tone example in grc at 48kHz. I let it use the default audio device and it worked ok, as does the FM receiver example. I then explicitly set the sink to hw:0 in grc which should be the same as the default, and that worked too.

Using hw:1 as input and hw:0 as output in gqrx still results in aUaO chars and the pink waterfall as before even after a reboot.

Just for a change, I plugged my SignalinkUSB in and selected the new hw:2 device for output in gqrx, which gave the same results as before. It seemed to work ok in grc but no change from before in gqrx.

Cheers,

Darren

hia,

>
> Thanks for the report Darren.

yes, i can tell is really helpful, and perhaps it all boils down to
some -dev under wheezy and the 64bits.

> Now, Alejo... I've told you last time that I have rolled back some changes
> that were causing qthid to crash. So please, instead of speculating when
> the code was last updated, just go ahead and get the latest code from the
> repository. If you don't know how to do it with git, you can always get the
> latest code as a .zip or .tar.gz from github:
> https://github.com/csete/qthid/downloads
> You'll see that it will generate a file called
> csete-qthid-v3.1-26-g91cb1a85.tar.gz, meaning that it is 4 commits ahead of
> v3.1-22-g67ddac88 which you used to generate the crash report.

I have done this and that (just compiled gnuradio's with cmakework so
to try to get gqrx). yes, I could be speculating but that's what's
left when you try many things... again, no user, no cry.

> Also please ensure that any binaries from the previous builds are removed,
> best is to remove the qthid-build-desktop directory before you load the
> updated qthid.pro in qtcreator.

I will try that, thank you again for your time to reply. Is out of the
question that you are incredibly generous. And that the issue looks
like outside of your code so please don't take it as if I putting in
question your code.

/a

 

Darren,

after my initial success with the FCD and gqrx on Ubuntu 11.04 (but now upgraded to 11.10) a few months ago I then inexplicably found that I got the a0 overflow message constantly. After seeing these recent messages and that Alex has updated qthid I have had another look at it tonight.

I experienced the same overflow problem tonight in gnuradio so know this is not a gqrx problem. After a bit of Googling I found references that suggested the problem might lie with the USB port. I have had the FCD plugged into the USB ports on the front of the case, which is connected to the USB header on the motherboard.

I also have a multi-card reader for CF/MC/SD etc etc which has 3 USB ports. I plugged the FCD into one of these ports and it works in gnuradio :-)

Another night I'll try to compile gqrx but I think I'll go back to first principles and install everything from scratch to make sure it has a clean build.

Not the same problem as you have but thought I'd add my experience and I'm very pleased that I might be able to get the FCD working on Ubuntu again.

Regards

Simon.

HI all, just joined the group new to sdr but an old Ham G4bxc ,Have a FCD and a
High Sierra Microwave H F converter 5-55 mhz ,but when i try to use the bias tee
power  it switch's on and off when i change freq, even when the bios tee box is
ticked ,also i cant seem to turn it off to enable me to use external dc .Help
please.  best  73s Harold G4bxc

What soft are you using???
If you use the right dll together with a winradclone (or simons sdr console)
then the phantom power should work
If you use the fchid frontend then make sure to use the right one
There is a basic frontend and a full frontend with the if saettings i(q
correction etc.)

... did you upgrade the firmware of the new fcd?!?

The newest firmware solves a few things

Basic firmware is just for test in the lab after producing the fcd ... so
upgrading to new firmware is needed!!

Give us some details to better help you

Greetz

Sigi
Dg9bfc (a happy fcd owner *g*)

> -----Ursprüngliche Nachricht-----
> Von: FCDevelopment@...
> [mailto:FCDevelopment@...] Im Auftrag von haroldpearce94
> Gesendet: Samstag, 21. Januar 2012 21:11
> An: FCDevelopment@...
> Betreff: [FCDevelopment] Bias tee
>
>
>
> HI all, just joined the group new to sdr but an old Ham G4bxc ,Have a FCD
> and a High Sierra Microwave H F converter 5-55 mhz ,but when i try to use
> the bias tee power it switch's on and off when i change freq, even when
> the bios tee box is ticked ,also i cant seem to turn it off to enable me
> to use external dc .Help please. best 73s Harold G4bxc
>
>
>
>

Hi Harold,

Perhaps we need some further clarification.

I'm using SDR Console 1.5 Build 879 and when I select the Bias Tee box
it stays checked when I change frequency while it's powering the
FCD-5-55-UC. Unchecking the box does indeed turn off the bias tee
feature. The FCD-5-55-UC also has the external DC feedthru which can be
used to power the converter if the bias tee feature is not available on
the early versions of the FCD.

But be sure that you don't have external DC power applied to the
converter while you try to power it from the FCD.

Regards...Bill - N6GHz

On 1/21/2012 1:10 PM, haroldpearce94 wrote:
> HI all, just joined the group new to sdr but an old Ham G4bxc ,Have a
> FCD and a High Sierra Microwave H F converter 5-55 mhz ,but when i try
> to use the bias tee power it switch's on and off when i change freq,
> even when the bios tee box is ticked ,also i cant seem to turn it off to
> enable me to use external dc .Help please. best 73s Harold G4bxc
>
>

--
Regards...Bill Ress
High Sierra Microwave

Did you upgrade the firmware to 18i???

Dg9bfc
Sigi


> -----Ursprüngliche Nachricht-----
> Von: FCDevelopment@...
> [mailto:FCDevelopment@...] Im Auftrag von Harold Pearce
> Gesendet: Sonntag, 22. Januar 2012 10:38
> An: FCDevelopment@...
> Cc: siegfried.jackstien@...
> Betreff: Re: AW: [FCDevelopment] Bias tee
>
>
>
> Hi Siegfried
>
> Thanks for the swift reply. I am currently using v1.1FCD, v1.5beta build
> 847 software.
>
>
> Thanks again for your very useful reply
>
> Regards
>
> Harold G4BXC
>
> ________________________________
>
> From: siegfried jackstien <siegfried.jackstien@...>
> To: FCDevelopment@...
> Sent: Saturday, 21 January 2012, 21:25
> Subject: AW: [FCDevelopment] Bias tee
>
>
>
> What soft are you using???
> If you use the right dll together with a winradclone (or simons sdr
> console)
> then the phantom power should work
> If you use the fchid frontend then make sure to use the right one
> There is a basic frontend and a full frontend with the if saettings i(q
> correction etc.)
>
> ... did you upgrade the firmware of the new fcd?!?
>
> The newest firmware solves a few things
>
> Basic firmware is just for test in the lab after producing the fcd ... so
> upgrading to new firmware is needed!!
>
> Give us some details to better help you
>
> Greetz
>
> Sigi
> Dg9bfc (a happy fcd owner *g*)
>
> > -----Ursprüngliche Nachricht-----
> > Von: FCDevelopment@...
> <mailto:FCDevelopment%40yahoogroups.co.uk>
> > [mailto:FCDevelopment@...
> <mailto:FCDevelopment%40yahoogroups.co.uk> ] Im Auftrag von haroldpearce94
> > Gesendet: Samstag, 21. Januar 2012 21:11
> > An: FCDevelopment@...
> <mailto:FCDevelopment%40yahoogroups.co.uk>
> > Betreff: [FCDevelopment] Bias tee
> >
> >
> >
> > HI all, just joined the group new to sdr but an old Ham G4bxc ,Have a
> FCD
> > and a High Sierra Microwave H F converter 5-55 mhz ,but when i try to
> use
> > the bias tee power it switch's on and off when i change freq, even when
> > the bios tee box is ticked ,also i cant seem to turn it off to enable me
> > to use external dc .Help please. best 73s Harold G4bxc
> >
> >
> >
> >
>
>
>
>
>
>

Hmm ... as far as i know the newest is not 18.6 (18f) ..
Newest is 18i or 18.9 ....
That solves a few "faults" like wrong filter setting in some frequencies and
"a glitch" that some stations reported caused by a timing fault (I don’t
remember well and can not exactly explain it so other group members maybe
can explain that better)....

So newest is 18 india

Greetz sigi

Dg9bfc


> -----Ursprüngliche Nachricht-----
> Von: FCDevelopment@...
> [mailto:FCDevelopment@...] Im Auftrag von Harold Pearce
> Gesendet: Montag, 23. Januar 2012 13:06
> An: FCDevelopment@...
> Cc: siegfried.jackstien@...
> Betreff: Re: AW: AW: [FCDevelopment] Bias tee
>
>
>
>
>
>
> ________________________________
>
> From: siegfried jackstien <siegfried.jackstien@...>
> To: FCDevelopment@...
> Sent: Sunday, 22 January 2012, 16:11
> Subject: AW: AW: [FCDevelopment] Bias tee
>
>
>
> Did you upgrade the firmware to 18i???
>
> Dg9bfc
> Sigi
>
> HI Sigi ,Idid upgrade to18 6  when Ifirst had the fcd  ,regards H, G4bxc
>
> > -----Ursprüngliche Nachricht-----
> > Von: FCDevelopment@...
> <mailto:FCDevelopment%40yahoogroups.co.uk>
> > [mailto:FCDevelopment@...
> <mailto:FCDevelopment%40yahoogroups.co.uk> ] Im Auftrag von Harold Pearce
> > Gesendet: Sonntag, 22. Januar 2012 10:38
> > An: FCDevelopment@...
> <mailto:FCDevelopment%40yahoogroups.co.uk>
> > Cc: siegfried.jackstien@...
> <mailto:siegfried.jackstien%40freenet.de>
> > Betreff: Re: AW: [FCDevelopment] Bias tee
> >
> >
> >
> > Hi Siegfried
> >
> > Thanks for the swift reply. I am currently using v1.1FCD, v1.5beta build
> > 847 software.
> >
> >
> > Thanks again for your very useful reply
> >
> > Regards
> >
> > Harold G4BXC
> >
> > ________________________________
> >
> > From: siegfried jackstien <siegfried.jackstien@...
> <mailto:siegfried.jackstien%40freenet.de> >
> > To: FCDevelopment@...
> <mailto:FCDevelopment%40yahoogroups.co.uk>
> > Sent: Saturday, 21 January 2012, 21:25
> > Subject: AW: [FCDevelopment] Bias tee
> >
> >
> >
> > What soft are you using???
> > If you use the right dll together with a winradclone (or simons sdr
> > console)
> > then the phantom power should work
> > If you use the fchid frontend then make sure to use the right one
> > There is a basic frontend and a full frontend with the if saettings i(q
> > correction etc.)
> >
> > ... did you upgrade the firmware of the new fcd?!?
> >
> > The newest firmware solves a few things
> >
> > Basic firmware is just for test in the lab after producing the fcd ...
> so
> > upgrading to new firmware is needed!!
> >
> > Give us some details to better help you
> >
> > Greetz
> >
> > Sigi
> > Dg9bfc (a happy fcd owner *g*)
> >
> > > -----Ursprüngliche Nachricht-----
> > > Von: FCDevelopment@...
> <mailto:FCDevelopment%40yahoogroups.co.uk>
> > <mailto:FCDevelopment%40yahoogroups.co.uk>
> > > [mailto:FCDevelopment@...
> <mailto:FCDevelopment%40yahoogroups.co.uk>
> > <mailto:FCDevelopment%40yahoogroups.co.uk> ] Im Auftrag von
> haroldpearce94
> > > Gesendet: Samstag, 21. Januar 2012 21:11
> > > An: FCDevelopment@...
> <mailto:FCDevelopment%40yahoogroups.co.uk>
> > <mailto:FCDevelopment%40yahoogroups.co.uk>
> > > Betreff: [FCDevelopment] Bias tee
> > >
> > >
> > >
> > > HI all, just joined the group new to sdr but an old Ham G4bxc ,Have a
> > FCD
> > > and a High Sierra Microwave H F converter 5-55 mhz ,but when i try to
> > use
> > > the bias tee power it switch's on and off when i change freq, even
> when
> > > the bios tee box is ticked ,also i cant seem to turn it off to enable
> me
> > > to use external dc .Help please. best 73s Harold G4bxc
> > >
> > >
> > >
> > >
> >
> >
> >
> >
> >
> >
>
>
>
>
>
>

Harold,

I think what Sigi is trying to tell you nicely is that to use bias tee you need
to upgrade to a version of firmware that supports it.

As far as I know 18f does not and you need to upgrade to 18i.

Do that and if it still doesn't work ask another question.

Regards

Simon.
G0FCU.

--- In FCDevelopment@..., "siegfried jackstien"
<siegfried.jackstien@...> wrote:
>
> Hmm ... as far as i know the newest is not 18.6 (18f) ..
> Newest is 18i or 18.9 ....
> That solves a few "faults" like wrong filter setting in some frequencies and
> "a glitch" that some stations reported caused by a timing fault (I don't
> remember well and can not exactly explain it so other group members maybe
> can explain that better)....
>
> So newest is 18 india
>
> Greetz sigi
>
> Dg9bfc
>

Alberto,

You are correct but 18j is shown on the website as being in testing. So only for expert users?

Simon.

Ahh yes ... correct ... i made a mistake there
18.10 is latest :-)

Dg9bfc
Sigi

I should not answer emails before my first coffee :-)

> -----Ursprüngliche Nachricht-----
> Von: FCDevelopment@...
> [mailto:FCDevelopment@...] Im Auftrag von Alberto I2PHD
> Gesendet: Dienstag, 24. Januar 2012 10:57
> An: FCDevelopment@...
> Betreff: Re: AW: [FCDevelopment] Bias tee
>
>
>
> --- In FCDevelopment@...
> <mailto:FCDevelopment%40yahoogroups.co.uk> , "siegfried jackstien"
> <siegfried.jackstien@...> <mailto:siegfried.jackstien@...>  wrote:
> >
> > Hmm ... as far as i know the newest is not 18.6 (18f) ..
> > Newest is 18i or 18.9 ....
>
> Isn't the latest 18j  (18.10) ? Or am I missing something ?
>
> --
> 73 Alberto I2PHD
>
>

I have upgraded the firmware and software , bios tee now working , once again
thanks for your help Bill, Sigi, Sam. Bill I must congratulate you on your HSM
5-55 Mhz Converter ,it is a very good piece of equipment that gives great HF
results with the FCD ,Plus price wise  it is very good value .With great back up
from High Sierra Microwave.
                                         Regards Harold G4bxc

Hello harold
Bias tee DOES work if you use the right software
Either use the full frontend (where is a button for phantom power)

Or use the extio driver dll with phantom power for using fcd with a winrad
clone (there is a driver with and one without phantom power!!)

Dg9bfc
Sigi



> -----Ursprüngliche Nachricht-----
> Von: FCDevelopment@...
> [mailto:FCDevelopment@...] Im Auftrag von haroldpearce94
> Gesendet: Samstag, 28. Januar 2012 07:16
> An: FCDevelopment@...
> Betreff: [FCDevelopment] Bios tee
>
>
>
> I have upgraded the firmware and software , bios tee now working , once
> again thanks for your help Bill, Sigi, Sam. Bill I must congratulate you
> on your HSM 5-55 Mhz Converter ,it is a very good piece of equipment that
> gives great HF results with the FCD ,Plus price wise it is very good value
> .With great back up from High Sierra Microwave.
> Regards Harold G4bxc
>
>
>
>

Hi All,

I am new in this list, I do not own a FunCube myself, but
as the author of Linrad, a fairly general SDR program I am
interested in having the FunCube dongle working well with
my software.

Linrad works with a couple of different ExtIO dll files, but
there are problems with the ExtIO_FCD_G0MJW.dll file for
FunCube.

Sometimes it works, sometimes it does not. It seems to me that
there is a bug in the dll that causes writes outside some
buffer area. I can move the dll load and call to the InitHW
entry to various places in the Linrad code and as it turns out
the result differs in an unexpected way. The original
place (linrad-03.33 and earlier) sometimes works, sometimes not.
By making the load library and InitHW the very first statements
in the Linrad code it seems I can get the FunCube work reliably.

When I move the FC initialization further down the code in
Linrads main routine some places make the dll work, but cause
an error on the exit from Linrad. It seems that placing the
FC stuff first when all data memory is undefined makes writes
outside bounds harmless.

I have searched info about this dll but I found nothing.
In what environment is it built? Can it be built for
Linux and Mac OS X also?

73

Leif / SM5BSZ

It is writtein in Borland BDS2006 and if there is a bug I am not at all
surprised as I am not a programmer. The question is where is the bug?

Porting to a differnt environment would be difficult but not impossible. The
main problem is it is a lot of work if you are not familiar with the new
environment.

Mike

--- In FCDevelopment@..., Leif Asbrink <leif@...> wrote:
>
> Hi All,
>
> I am new in this list, I do not own a FunCube myself, but
> as the author of Linrad, a fairly general SDR program I am
> interested in having the FunCube dongle working well with
> my software.
>
> Linrad works with a couple of different ExtIO dll files, but
> there are problems with the ExtIO_FCD_G0MJW.dll file for
> FunCube.
>
> Sometimes it works, sometimes it does not. It seems to me that
> there is a bug in the dll that causes writes outside some
> buffer area. I can move the dll load and call to the InitHW
> entry to various places in the Linrad code and as it turns out
> the result differs in an unexpected way. The original
> place (linrad-03.33 and earlier) sometimes works, sometimes not.
> By making the load library and InitHW the very first statements
> in the Linrad code it seems I can get the FunCube work reliably.
>
> When I move the FC initialization further down the code in
> Linrads main routine some places make the dll work, but cause
> an error on the exit from Linrad. It seems that placing the
> FC stuff first when all data memory is undefined makes writes
> outside bounds harmless.
>
> I have searched info about this dll but I found nothing.
> In what environment is it built? Can it be built for
> Linux and Mac OS X also?
>
> 73
>
> Leif / SM5BSZ
>

Hello Mike,


> It is writtein in Borland BDS2006 and if there is
> a bug I am not at all surprised as I am not a
> programmer. The question is where is the bug?
Well, hard to say without access to the source code;-)

> Porting to a differnt environment would be difficult
> but not impossible. The main problem is it is a lot
> of work if you are not familiar with the new environment.
I am not familiar to BDS2006 so I have no idea what
specific functions it might supply and to what extent
you are using them. It would however be pretty
straight-forward to run the source code through the latest
version of the gcc compiler.

Error checking is improving over time and today the
gcc compiler will detect a lot of errors that were not
detected by earlier compilers.

Maybe there is an option in BDS2006 to enable a debug
option to do boundary checking. It seems to me that the
problem could be caused by writes outside allocated memory.

73

Leif  /  SM5BSZ


>
> Mike
>
> --- In FCDevelopment@..., Leif Asbrink <leif@...> wrote:
> >
> > Hi All,
> >
> > I am new in this list, I do not own a FunCube myself, but
> > as the author of Linrad, a fairly general SDR program I am
> > interested in having the FunCube dongle working well with
> > my software.
> >
> > Linrad works with a couple of different ExtIO dll files, but
> > there are problems with the ExtIO_FCD_G0MJW.dll file for
> > FunCube.
> >
> > Sometimes it works, sometimes it does not. It seems to me that
> > there is a bug in the dll that causes writes outside some
> > buffer area. I can move the dll load and call to the InitHW
> > entry to various places in the Linrad code and as it turns out
> > the result differs in an unexpected way. The original
> > place (linrad-03.33 and earlier) sometimes works, sometimes not.
> > By making the load library and InitHW the very first statements
> > in the Linrad code it seems I can get the FunCube work reliably.
> >
> > When I move the FC initialization further down the code in
> > Linrads main routine some places make the dll work, but cause
> > an error on the exit from Linrad. It seems that placing the
> > FC stuff first when all data memory is undefined makes writes
> > outside bounds harmless.
> >
> > I have searched info about this dll but I found nothing.
> > In what environment is it built? Can it be built for
> > Linux and Mac OS X also?
> >
> > 73
> >
> > Leif / SM5BSZ
> >
>
>