开云体育

I've got a major headache - I don't know what changed, but I cannot transmit anything with my softrock - no signal out. The setup: Softrock RxTx6.3 modified for broadband use (wideband low power class A amp in place of power amp). Transverter - 10m to 2m (working right). Computer: Dell D2500CC dual core 1.86 ghz 4gb ram dedicated for running radios, single monitor 800x600 (small size, may change out for slightly larger one). Ubuntu 18.04.3 LTS. Quisk 4.1.46 Internal audio on hw:0 usb audio on hw:1 (two different audio devices tried - a sound blaster unit and a good Realistic unit) Problem: no transmit audio. RxTx goes into transmit (using the USB I2C interface adapter), but no audio out (tried two different USB audio units). Audio and RF checked with an oscilloscope. Problem started a few months ago, with the receive being off in frequency (and sometimes no receive whatsoever). That time, I found a bad ground connection in the softrock, which when fixed made communicating with (and changing frequencies with) the softrock a lot more reliable. Transmit audio also stopped working (and hasn't been right since). It's not the radio as far as I can tell - no audio is being generated by quisk. This was true no matter which audio device was used for IQ transmit. Test audio (computer voice through left and right channels) via the computer setup screen works fine - both channels will generate audio. Waveform clean, audio sounds good in headphone when plugged into port. Tried Alsa audio, Pulseaudio settings, and installed mixers for both (neither made any difference). I found that using Alsa audio or Pulseaudio in the Quisk radio setup made the system rather unreliable - sometimes the spectrum graph would be working, but no audio out. Other times, no response visible on the graph. I couldn't detect any pattern to this. Using hw:0 and hw:1 in the Quisk radio setup was the only really reliable (as far as receive) setup - tried hw:1,0 for the USB device, still doesn't work. Sometimes using Alsa or Pulseaudio would cause Quisk to crash, every time I tried to transmit. The most reliable mixer was QASHmixer, but still no transmit audio. One funny thing was that with the built-in audio mixer (under Ubuntu setup) and with the Alsa mixer, either both digital and audio would be turned on, or turned off. I couldn't turn off the digital mixer without the line audio mixer (for the USB device output) also turning off. I've tried reloading Quisk (a couple of months ago) with no change in symptoms. I'm at a loss now. Any suggestions on where to check next? It doesn't seem to be hardware related at all... something between Quisk and the digital signal going into the USB audio devices! Thanks for any help! Bob N4FBZ

(Sigh!) Back to the drawing board. Yes, I'm getting signal out - wide-band noise only. I'm using a RTL dongle as a poor man's spectrometer on the output of the softrock (on 28). The signal is very broad... and no adjustments make a difference that I can detect. just wide-band noise. Receive seems as good as ever - no changes there. It doesn't matter which mode I'm using. I also checked, and don't have any of the old .conf files in the home directory. I'm at a loss as to what to look at next. I've never had much problem with cleaning up the Tx and Rx using level and phase. I used the dongle for those adjustments - back when everything worked. It made it easy. (I'd love to try one of the other rigs, but can't afford to buy anything. Maybe in several months... I did finally find a job, after trying for over three years - part time and no benefits, but at least something I can handle! The Ethernet connection - just between radio and computer?) Thanks for trying! Bob

Hello, I try to connect quisk to a mumble client for remote operation. Mumble can see "quiskdigitaloutput" but which "radio sound output" device must be selected on quisk ? Has someone tried to interface with mumble ? Pascal F6EHP

Just downloaded the latest version and printed the documentation to file. Under the topic "Linux Problems" regarding audio issues, there are two link: http://linuxplanet.com/linuxplanet/tutorials/6465/1/ http://linuxplanet.com/linuxplanet/tutorials/6466/1/ These links no longer work. When you go to Linuxplanet, there is no section devoted to tutorials. There is a section labeled "Storage" which contain further links to other sites. They are useful, I'd guess, but there is nothing listed earlier than October, 2019. So, if someone has copies of those tutorials, it might be good to post them in the Files section here. I'm setting up to use an image provided by PiSDR for a standalone application which uses Quisk. I would hope that I can upgrade to the latest version. It appears that the PiSDR uses an OrangePi3 board instead of a Raspberry Pi. Wish me luck. BruceN / K4TQL

On Fri, 13 Dec 2019, 13:05 Karl-Heinz Pischke, <pischke.karl-heinz@...> wrote: Hello everyone :-) hope that I'm right here with this problem! First - there are no difficulties to work with FLDIGI - but if I start WSJT-X there's no audio (I/Q) output anymore between Quisk and the soundcard until I restart Quisk. I've done the installation according to the documentation: "... Using PulseAudio is the easiest method because Quisk can set up the loopback devices when it starts. Set Digital Input to pulse:QuiskDigitalInput.monitor, and set Digital Output to pulse:QuiskDigitalOutput. These names should be on the drop down list. If they are missing, make sure that you didn't set "show_pulse_audio_devices" to False in your config file. Then restart Quisk. In your digital program, connect the digital input to QuiskDigitalOutput.monitor and the digital output to QuiskDigitalInput. These names will be on the sound menu in wsjtx, and you should be receiving and transmitting digital data. Fldigi only has a PulseAudio check box, and there is no way to set the proper device. In this case, first install the program pavucontrol to control PulseAudio. This is a useful program to control and understand PulseAudio even if you are not using digital. Set the Quisk devices as above. Now start both Quisk and Fldigi, and then pavucontrol. The Playback and Recording screens in pavucontrol will show the devices being used. Change the Fldigi playback to QuiskDigitalInput, and the Fldigi recording to Monitor of QuiskDigitalOutput. Then everything should work ..." PTT works right and the program is receiving well. Did I overlooked something? 73's DL6MEE JO30to

Hello, On my Quisk version 4.1.52 (linux), I have a tx level in one band of 0, because I need this "low" power output to not burn my PA that is connected to my HL2. And it works really well. I noticed, that if I power cycle the HL2 and restart the software, then it transmit full power. Why my tx level of 0 is ignored ? I guess that I must miss something in the config to restore the values. Do you have any clues ? Thank you Julien, F4HVX

Tayloe-style SDRs require amplitude and phase corrections to suppress the image on the opposite side of the center frequency. The correction depends on the center frequency (the "VFO") and the difference between the center and the tuning frequency. Quisk currently uses only the center frequency when interpolating corrections. I added a new Softrock hardware file to create a fixed offset between the center and tuning frequency. This means all tuning is done with the VFO. It is in the file area at /g/n2adr-sdr/files/N2ADR/softrock_tune_vfo.py. Bruce, AG5GT, is currently studying this issue. Jim N2ADR

Hi, just one question: Has the support for the charleston-sdr receiver (i think it was from around 2010) been removed or should it still work? I still have such a board flying around here and wonder if it is worth the effort to reactivate it or if i should put it to the museum pile. 73 Mario

Hi Jim, I'm playing around with as simple SDR somewhat similar to the openradio SDR built by some Aussies in 2015. I'm attempting to make their code work. Just following their instructions didn't seem to work here. I suspect something changed between 2015 and now on the quisk end of things. I'm attaching the README, and the quisk_conf.py in the hope you can tell me what I need to modify. Thanks & 73, Rob KL7NA -- Rob Frohne, Ph.D. P.E. E. F. Cross School of Engineering Walla Walla University 100 SW 4th Street College Place, WA 99362 (509) 527-2075

I added an On/Off button to Quisk. When Quisk starts the button is "On". When you turn it to "Off", Quisk shuts down the sound system and closes the hardware. When you turn it "On" again, Quisk starts with any new setting made from the Config screens. This provides a way to start Quisk with changed settings, and to re-start your hardware after a power down. Martin Schaller found and fixed a bug in the Alsa sound system that produced sporadic crashes. Thanks Martin! Max, G7UOZ, found and fixed a bug in the Python3 SoftRock hardware_net.py code. Thanks Max! This Quisk includes a more recent FreeDV library in both 32-bit and 64-bit versions. The Windows SoapySDR interface still requires 64-bit Quisk. The Config/Status screen now shows the dB level of each open sound device. The maximum level is zero dB. This is meant as an aid to configuring the sound devices. Jim N2ADR

HI, wondering if there is a way to stop the voice monitor when using FDX in 4.1.52. The latency is far too great for my ears, but do like to see my transmitted signal portrayed on the graph screen. Using an Win 10 i3 Thank you the old guy Gil K8EAG

I know it's a little late after sending a couple of emails to the group, but hello the group! I'm interested in using Quisk with this HackRF One that I have. I'd like to eventually use it as an HF radio. I realize that Quisk may need some modifications for this to work, but I'm a reasonably capable programmer, so I'm expecting to have to help with that. -- Jonathan Guthrie ARS KA8KPN

Hi Jim, I am intrigued by the open-source gnuradio toolkit and, particularly, the associated graphical tool known as gnu radio companion (GRC). The essential toolkit includes various chunks of code for signal processing and hardware interaction. GRC provides a graphical means to link the chunks by means of signal flow graphs. My understanding is that the heavy duty signal processing is implemented in C++ while python scripting underlies the GRC graphs. One can build and test SDR code with GRC and then export the result, and put a custom GUI in front of it. There appears to be good and growing support for the toolkit. That seems to come from academics who value it as a teaching tool, as well as others who find it useful to tap into a wealth of existing code rather than start from scratch to build things. How reasonable would it be to try re-constructing Quisk in the gnuradio toolkit, with GRC? That might expand the community of folks able to contribute to hardware adaptations and various signal processing opportunities. It might also lower the barrier to newbies hoping to figure out how Quisk is built and, therefore, how to extend it or customize it for various purposes. Having not yet tried to dig into Quisk's innards, I have no idea whether that is crazy talk or easily done or, more likely, something in between. Have you or other community members given any thought to this? cheers, Bruce, ag5gt

All, I have tried multiple times to get the quisk software install in any of my 3 Windows10 machines. I have Python 3.8 installed, and went through the installation guide here: https://james.ahlstrom.name/quisk/docs.html#Installation After multiple tries I finally worked out that in needed to check the "Add Python 3.8 to Path" checkbox on the install page. I was then able to run python programs from the cmd line. When I type in "quisk" the process starts, then just stops and returns to the command line. Any ideas? Thanks, Evan AC9TU

I had to re-install WIN10 (64-bit) in my desktop (oldish but still going strong !) and consequently also re-install Python for the QUISK. I tried Python3 (for the first time !) but could not make QUISK to work at all. It did not even start ! When uninstalling Python3 and installing Python 2.7 everything worked as B4. I wonder if anyone has had similar problems lately. According to Jim both Python versions should work with QUISK and if only either one is installed, no confusion should exist. 73 de Heikki (OH2LZI)

While I have been updating Quisk support for the Charleston SDR, I realized that it may be possible to add Mac support. I have no idea what it would take to run the Charleston SDR on an Apple Mac. I do have an older MacBook Pro from an older, failed project. We actually got our interfacing code to work, but the base program became orphaned. The Charleston SDR basically is a Digilent Nexys 2 FPGA board (using a CY13 USB2 chip) with a small RF A/D add-on board. Since it has a USB port, I think it is possible to connect to a MacBook? Last time we tried to write code for a Mac, we needed to spend $100 per year for the privilege of writing code. Is that still the case? How does C and Python programming for Macs? Thank you, Terry N4TLF

Hi, I'm investigating how I'd control an external linear amplifier from Quisk (and a Hermes Lite 2 SDR). The linear I'm planning (the Juma PA1000) appears to allow band selection via BCD (on a 9 pin D connector) or serial input via a 3.5mm jack. I'm assuming control via serial should be possible here. However, I'm looking at the n2adr examples and not finding what I'm looking for. I'm assuming I need to output standard CAT to select band. I'm also not much of a programmer, so really struggling here. Would anyone have a basic extension/config that would output band control via serial CAT? Thanks, Steve M0SPN/OH3SPN