Difference between revisions of "HiQSDR-Hints"

Jump to: navigation, search
(Some Hints and Tricks)
(Some Hints and Tricks)
Line 107: Line 107:
First you have to buy an simple USB Footswitch and configure it with the delivered software to the "pause" button.<br>
First you have to buy an simple USB Footswitch and configure it with the delivered software to the "pause" button.<br>
[[Image:footswitch.jpg| Example PTT-footswitch]]<br />
[[Image:footswitch.jpg|400px|center|Example PTT-footswitch]]<br />
As next configure your defined "pause" hotkey in your quisk_conf.py<br>
As next configure your defined "pause" hotkey in your quisk_conf.py<br>

Revision as of 16:11, 9 July 2015

Some Hints and Tricks


Some tricks to check your Network: The HiQSDR is typically programmed to use the IP4 address
The network mask 192.168.xxx.xxx is in the private network range (Class C) without routing over any internet gateway.
The number xxx.xxx.002.xxx is your subnet address range, which is normally shared by your computer / router and the gateway in the same subnet.
The last number xxx.xxx.xxx.196 is the address of your HiQSDR that is used to form the complete ip-address (,which must be unique in your network.

If you have problems to ping your HiQSDR, first check your cable and network addresses with subnet and range.
With different addresses and / or subnets, it is better to change the FPGA network address of your HiQSDR to your address range.
On some computers, the HiQSDR works only over a network switch but not with a crossover cable.

For Linux, you can alternatively modify the routing table of your computer with "route add dev eth0"
Do this with administrator rights; the device here is the first ethernet card with the name eth0.
Now the network will find your HiQSDR and Quisk should be running.

  • Configuration of your network cards: "ifconfig" lists your network cards.
  • To see the routing table: "route" lists all known routes.
  • Add a route to the HiQSDR with "sudo route add dev eth0 "

Frequency correction factor

How do I correct the frequency if it differs?
If your frequency differs, the parameter rx_udp_clock can be used to correct the frequency of your HiQSDR.
With a calibrated frequency counter you should measure the main oscillator frequency of the HiQSDR Oscillator.
Now enter the measured frequency in the rx_udp_clock= parameter in your .quisk_conf.py
Next, check the rx frequency with a calibrated signal generator or a known radio time signal.
To check your tx frequency, use a calibrated frequency counter or spectrum analyser. If your rx frequency is correct, the tx frequency is also correct.

CW Delay (from Alex DL1KDA and Mario DH5YM)

Stefan DL2STG has modified the HiQSDR Firmware to set an CW Delay at controll byte 20 to use it with RASDR and Quisk. The HiQSDR works in CW full BK so the relay drops out very quickly.

In newer versions of Quisk Jim will take these changes to Quisk if you want the CW Delay immediately now you have to modyfy the HiQSDR quisk_hardware.py and your quisk_conf.py

In quisk\hiqsdr\quisk_hardware.py:

The lines from 298 to 323 should look like:
  def NewUdpStatus(self, do_tx=False):
    s = "St"
    s = s + struct.pack("<L", self.rx_phase)
    s = s + struct.pack("<L", self.tx_phase)
    s = s + chr(self.tx_level) + chr(self.tx_control)
    s = s + chr(self.rx_control)
    if self.firmware_version:	# Add the version
      s = s + chr(self.firmware_version)	# The firmware version will be returned
      if self.tx_control & 0x04:	# Use extra HiQSDR control bytes
        s = s + chr(self.HiQSDR_Connector_X1)
        s = s + chr(self.HiQSDR_Attenuator)
        s = s + chr(self.HiQSDR_Bits)
        s = s + chr(0)
        s = s + chr(0) * 4
      s = s + struct.pack("<H", self.vna_count)
      s = s + chr(self.conf.cw_delay)
      s = s + chr(0)
    else:		# firmware version 0 or None
      s = s + chr(0)	# assume version 0
    self.want_udp_status = s
    if do_tx:

After this add the following parameter to your quisk_conf.py:
cw_delay = 140
Alex use 140 as his optimum.

PTT Key Switch

Example of how to connect a morse key or a ptt switch
Example PTT-Switch as PDF
Example PTT-Switch with RS232 RTS as PDF


External remote footswitch (from Alex DL1KDA)

If you want to work remotely with a PTT footswitch and the HiQSDR follow these steps from Alex DL1KDA.
With Quisk you have the option to create an hotkey to switch the PTT.

Alex use the HiQSDR with VHF / UHF transverters and an USB Footswitch to work remote in Digitalmodes and Meteoscatter with Quisk.

First you have to buy an simple USB Footswitch and configure it with the delivered software to the "pause" button.

Example PTT-footswitch

As next configure your defined "pause" hotkey in your quisk_conf.py

hot_key_ptt1 = wx.WXK_PAUSE
hot_key_ptt2 = None

If you want other hotkeys more info you will find in "quisk_conf_defaults.py" begining from line 849.

Tested from Alex DL1KDA under Windows with Quisk Software


Some tricks to check your Linux Soundcards
If you have installed the Pulseaudio Audio System it is difficult to run Quisk simultaneously with Pulseaudio.
As correction, start Quisk with pasuspender.

Example: "pasuspender -- python quisk.py" 

Pasuspender is a tool that can be used to instruct a local PulseAudio sound server to temporarily suspend access to the audio devices, in order to allow other applications (Quisk) to access them directly.

  • To find your PCI soundcards, open a Console use "lspci | grep audio" to list your PCI soundcards.
  • To find your soundcard driver, open a Console and use "lsmod | grep snd" to list all loaded system soundcard drivers.
  • Alsa Soundmixer "alsamixer" with soundcards
  • Gnome Soundmixer "gnome-alsamixer" with soundcards

Some tricks regarding your Linux system

  • To create a Desktop shortcut to Quisk, right-click on the desktop, activate "New Starter" and fill out the Form. It is important to use the full path to quisk.py
  • Midnight Commander mc is a useful tool if you like to work with a terminal or on the console prompt.
Midnight Commander