locked
keying sequencer
AH0U
I am using a Flex 6700 with WSJT... I now want to use my QSKIIc sequencer for QRO EME... I set up a virtual com port and set it for PTT RTS/DTR and set WSJT to PTT RTS and it seems to command the PTT in the Flex OK but any ideas of how to get a command to the PTT input port on the sequencer???
Tnx, bc AH0U
|
|
locked
Re: Wrong automatic response during contest
Hello, I have noticed as well. A friend told me some operators may use two WSJT-X or similar programs to run them together, to make twice as many contacts during a contest. I think it just makes them twice as slow. Maybe this is what happened in your case. KN4SMO Scott
On Sun, Apr 12, 2020 at 2:54 PM KC3JNW <kc3jnw@...> wrote: During the contest YY2JMO called me (KC3JNW) He didn't answer I called again. He called me I answered. Then he called someone else I switched to calling CQ and he sent me an RR73. My automatic reply was a 549 PA. It should have stopped after he sent me an RR73 and prompted me to log.
|
|
locked
Compiling for arm64 Issue
JT Croteau <jt.tobit@...>
Friends, I'm trying to compile 2.1.2 on Linux arm64 but having an
issue. I'm wondering if anyone can help please? arm64 is a different platform than armhf so I can't use the binary package on my Gentoo system. Target hardware is a Raspberry Pi4B. Thanks Failing here: [ 69%] Building CXX object CMakeFiles/wsjt_qt.dir/qt_helpers.cpp.o In file included from /home/n1ese/build/wsjtx-prefix/src/wsjtx/qt_helpers.cpp:1: /home/n1ese/build/wsjtx-prefix/src/wsjtx/qt_helpers.hpp: In static member function ‘static QVariant VPtr<T>::asQVariant(T*)’: /home/n1ese/build/wsjtx-prefix/src/wsjtx/qt_helpers.hpp:77:61: warning: ‘QVariant qVariantFromValue(const T&) [with T = void*]’ is deprecated: Use QVariant::fromValue() instead. [-Wdeprecated-declarations] 77 | return qVariantFromValue (reinterpret_cast<void *> (ptr)); | ^ In file included from /usr/include/qt5/QtCore/qlocale.h:43, from /usr/include/qt5/QtCore/qtextstream.h:46, from /usr/include/qt5/QtCore/qdebug.h:49, from /usr/include/qt5/QtNetwork/qabstractsocket.h:47, from /usr/include/qt5/QtNetwork/qhostaddress.h:48, from /usr/include/qt5/QtNetwork/QHostAddress:1, from /home/n1ese/build/wsjtx-prefix/src/wsjtx/qt_helpers.hpp:9, from /home/n1ese/build/wsjtx-prefix/src/wsjtx/qt_helpers.cpp:1: /usr/include/qt5/QtCore/qvariant.h:528:17: note: declared here 528 | inline QVariant qVariantFromValue(const T &t) | ^~~~~~~~~~~~~~~~~ In file included from /home/n1ese/build/wsjtx-prefix/src/wsjtx/qt_helpers.cpp:1: /home/n1ese/build/wsjtx-prefix/src/wsjtx/qt_helpers.hpp: At global scope: /home/n1ese/build/wsjtx-prefix/src/wsjtx/qt_helpers.hpp:87:10: error: redefinition of ‘struct std::hash<QString>’ 87 | struct hash<QString> | ^~~~~~~~~~~~~ In file included from /usr/include/qt5/QtCore/qlist.h:47, from /usr/include/qt5/QtCore/qhash.h:46, from /usr/include/qt5/QtCore/qshareddata.h:46, from /usr/include/qt5/QtNetwork/qhostaddress.h:47, from /usr/include/qt5/QtNetwork/QHostAddress:1, from /home/n1ese/build/wsjtx-prefix/src/wsjtx/qt_helpers.hpp:9, from /home/n1ese/build/wsjtx-prefix/src/wsjtx/qt_helpers.cpp:1: /usr/include/qt5/QtCore/qhashfunctions.h:204:1: note: previous definition of ‘struct std::hash<QString>’ 204 | QT_SPECIALIZE_STD_HASH_TO_CALL_QHASH_BY_CREF(QString) | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ gmake[5]: *** [CMakeFiles/wsjt_qt.dir/build.make:106: CMakeFiles/wsjt_qt.dir/qt_helpers.cpp.o] Error 1 gmake[5]: Leaving directory '/home/n1ese/build/wsjtx-prefix/src/wsjtx-build' gmake[4]: *** [CMakeFiles/Makefile2:822: CMakeFiles/wsjt_qt.dir/all] Error 2 gmake[4]: Leaving directory '/home/n1ese/build/wsjtx-prefix/src/wsjtx-build' gmake[3]: *** [Makefile:169: all] Error 2 gmake[3]: Leaving directory '/home/n1ese/build/wsjtx-prefix/src/wsjtx-build' gmake[2]: *** [CMakeFiles/wsjtx-build.dir/build.make:78: wsjtx-prefix/src/wsjtx-stamp/wsjtx-build] Error 2 gmake[2]: Leaving directory '/home/n1ese/build' gmake[1]: *** [CMakeFiles/Makefile2:405: CMakeFiles/wsjtx-build.dir/all] Error 2 gmake[1]: Leaving directory '/home/n1ese/build' gmake: *** [Makefile:101: all] Error 2
|
|
locked
Re: Error in Sound Output: An Error open the audio outout device has occurred??
Jim Brown
On 4/12/2020 9:04 AM, Jon Ermels via groups.io wrote:
There are many types of chokes, here he is referring to a ferrite choke, the "spec" would refer to the mix number.No, the mix number is NOT "the" spec, it is only part of the spec. The cables in the link only go through the core once, which causes the effectiveness of the choke to peak around 150MHz. If you need a choke that works on the HF bands, you need multiple turns through Fair-Rite #31 material. See k9yc.com/RFI-Ham.pdf for a tutorial on how chokes work. http://k9yc.com/KillingReceiveNoise.pdf is a tutorial on finding and killing RX noise, and the chokes described in it work equally well for RF pickup on cables. On 4/12/2020 7:58 AM, Jim Bacher - WB8VSU wrote: Plus with good cables the products would pass without ferrites.Passing FCC Rules does not mean a product won't produce noise that we hear on the MF and HF bands because the tests are not meaningful -- they don't expose the design/construction errors that put RF noise on interconnecting cables. The most common error is "The Pin One Problem," whereby the cable shield goes through the shielding enclosure without being bonded to it. Howeverenvironment. Ferrites are generally needed because 99.9% of products are built with "Pin One Problems." I do agree with the observation that many (most?) commercially available cables are of poor quality, and without sacrificing one by cutting it open, there's no easy way to evaluate them. 73, Jim K9YC
|
|
locked
Re: Question about SNR reports
Jim Brown
For most hams, this is NOT true below 2M, because our limitation is noise from all sorts of electronic sources in our homes and neighbor homes. A preamp improves signal to noise ONLY when the noise from the antenna is close to or below the level of noise in the RX input stage.
toggle quoted messageShow quoted text
My friend AG6EE often makes expeditions for rare grids in the US state of NV, and he finds very isolated locations that are electrically very quiet. He DOES, of course, use a preamp, and he regularly hears 10-20 dB better than stations calling him. My QTH in the Santa Cruz mountains is sometimes fairly quiet, but I have neighbors within 100-300m, and sometimes they make noise. I run legal limit (1.5kW) to very good antennas on 160 to work EU and on 6M. WSJT-X regularly gives signal reports 10-15 dB better than I receive from the other station, and very often, stations that are -10 here don't copy me. Recently I've been running 50W on 60M, with the same result. 73, Jim K9YC
On 4/12/2020 4:56 AM, Tom V. Segalstad wrote:
It also depends on if the receiving station is using reception preamplifiers - and the other station not.
|
|
locked
Re: Suddenly no stations coming in above 1150hz
VE7UHS@...
Got it, somehow the waterfall width shrunk, thank you all for your assistance.
|
|
locked
Re: Suddenly no stations coming in above 1150hz
Sam Birnbaum
How wide is your waterfall ?
If you shrank to less than 1550, nothing above will decode.
73,
Sam W2JDB
-----Original Message-----
To: WSJTX@groups.io Sent: Sun, Apr 12, 2020 4:12 pm Subject: Re: [WSJTX] Suddenly no stations coming in above 1150hz All filters fully open at 3200 on usb and 3000 on digital still same nothing coming in above 1150hz
|
|
locked
Re: Suddenly no stations coming in above 1150hz
VE7UHS@...
All filters fully open at 3200 on usb and 3000 on digital still same nothing coming in above 1150hz
|
|
locked
Re: Wrong automatic response during contest
Reino Talarmo
Hi, you called CQ and YY2JMO answered to you from near North Pole. 73, Reino OH3mA
|
|
locked
Re: Suddenly no stations coming in above 1150hz
On 12/04/2020 17:51, VE7UHS@... wrote:
I am receiving ft8 as normal (up to 1150hz) anything above is not seen. I tried two computers with the same operating system samething, so I thought it was the radio, so I contacted Yaesu they gave me settings to try, same thing nothing above 1150hz, I thought my internal sound card on the 991a had broken until I tried my ic 7100 same problem. Anyone know the fix to this... ThanksHi Rob, you don't tell us much about what's not working. Are there signals on the waterfall? Is there any indication on the WSJT-X main window thermometer style level indicator? Is your PC clock sufficiently close to UTC? 73 Bill G4WJS.
|
|
locked
Re: My setup is:
Just curious, why are you using a SignaLink with the IC-7300? It has a built-in soundcard accessible via USB. The SignaLink is completely unnecessary.
toggle quoted messageShow quoted text
Michael WA7SKG Ed Oxer, W8EO wrote on 4/12/20 6:26 AM:
Icom 7300
|
|
locked
Re: Question about SNR reports
HI Tom,
there should be no surprises from your
test observations, on the contrary if the pre-amps had changed the
received noise power relative to the received signal strength you
should might then be surprised. Receive pre-amps are useful when
located at the far end of a lossy feeder system that might reduce
the weakest signal levels below the front-end noise floor of your
receiver.
73
Bill G4WJS. On 12/04/2020 15:52, Tom V. Segalstad
wrote:
|
|
locked
Re: Suddenly no stations coming in above 1150hz
Check your filter settings. Sounds like you inadvertently changed them.
KV4VT
Sent from my T-Mobile 5G Device
-------- Original message --------
From: VE7UHS@...
Date: 4/12/20 2:34 PM (GMT-05:00)
To: WSJTX@groups.io
Subject: [WSJTX] Suddenly no stations coming in above 1150hz
I am receiving ft8 as normal (up to 1150hz) anything above is not seen. I tried two computers with the same operating system samething, so I thought it was the radio, so I contacted Yaesu they gave me settings to try, same thing nothing above 1150hz, I
thought my internal sound card on the 991a had broken until I tried my ic 7100 same problem. Anyone know the fix to this... Thanks
Rob
|
|
locked
Wrong automatic response during contest
KC3JNW
During the contest YY2JMO called me (KC3JNW) He didn't answer I called again. He called me I answered. Then he called someone else I switched to calling CQ and he sent me an RR73. My automatic reply was a 549 PA. It should have stopped after he sent me an RR73 and prompted me to log.
I have seen this before but this time I wasn't working the contest real hard and had time to look at it. See Below. Thanks
|
|
locked
Raspberry Pi - USB UART Codec - IC-735 ?
#AudioIssues
#AudioIssues
#FT8
#linux
Hi,
I cannot transmit with my setup with IC-735 + FlRig + WSJT-x / JTDX. I use an USB audio card connected to Raspberry Pi - the other end of the cable is connected to ACC-jack on IC-.735 https://www.ebay.com/itm/6-FT-FT8-FT4-JT65-PSK-Audio-Interface-8-Pin-DIN-Cable-DC-01C-for-ICOM/164005003864?ssPageName=STRK%3AMEBIDX%3AIT&_trksid=p2057872.m2749.l2649 From remote jack on IC-735 I have an USB connector to one of Raspberry Pi https://www.ebay.com/itm/Icom-CT-17-CI-V-CAT-Programming-Cable-for-IC-731-IC-732-IC-735-IC-736-IC-737/112119572076?ssPageName=STRK%3AMEBIDX%3AIT&_trksid=p2057872.m2749.l2649 Is my issue a codec related? Do I need drivers for the USB cables? Virtual cables? 73 de Alf OH6IH
|
|
locked
frequency measuring
Jamie WW3S
I'm trying to setup for the upcoming ARRL frequency measuring test. Tyring to use the WSPR mode under WSJT-X. Despite the fact I have the green CAT button in WSPR mode of WSJT-X, and the TEST CAT Function works, when I type the commands in the dos prompt window for FMT, I get an error:
rigctl -m 363 -r COM6 -s 9600 -C data_bits=8 -C stop_bits=2 -C serial_handshake=None F 4998500 using an IC-7610 with WSPR running under WSJT-X
|
|
locked
Suddenly no stations coming in above 1150hz
VE7UHS@...
I am receiving ft8 as normal (up to 1150hz) anything above is not seen. I tried two computers with the same operating system samething, so I thought it was the radio, so I contacted Yaesu they gave me settings to try, same thing nothing above 1150hz, I thought my internal sound card on the 991a had broken until I tried my ic 7100 same problem. Anyone know the fix to this... Thanks
Rob
|
|
locked
Re: Error in Sound Output: An Error open the audio output device has occurred??
I use cables like this although I did not have a problem before using them even when running 800 W on CW or SSB and tested 400 W FT8 to ladder line (I have a rotten antenna and sometimes need more than 50 W 😊 ) but I think it is a good protection. I do not remember that they were so expensive. I doubt I paid 14.97 Cdn for them but am not certain.
Outlook Laptop Gil W0MN Hierro candente, batir de repente 44.08226N 92.51265W EN34rb
From: WSJTX@groups.io <WSJTX@groups.io> On Behalf Of neil_zampella
Sent: Sunday, April 12, 2020 09:48 To: WSJTX@groups.io Subject: Re: [WSJTX] Error in Sound Output: An Error open the audio outout device has occurred??
Of course, you probably have to take the info down, and then go to the US site, Amazon.com Neil, KN3ILZ On 4/12/2020 10:46 AM, Neil Zampella wrote:
-- W0MN EN34rb 44.08226 N 92.51265 W Hierro candente, batir de repente HP Laptop
|
|
locked
Re: FT8 Problem !
robert kupps
On the waterfall control panel, change the “N Avg” tO a LOWERr number.
hope this helps robert W6INO
W6INO ~~~~~~~~~~~~~~~~~~~~~~~~~~~ Twenty years from now, you will be more disappointed by the things you didn't do than by the ones you did do. So, throw off the bowlines. Sail away from the safe harbor. Catch the trade winds in your sails. Explore. Dream. Discover. -Mark Twain
|
|
locked
Re: Error in Sound Output: An Error open the audio outout device has occurred??
Jon Ermels
There are many types of chokes, here he is referring to a ferrite choke, the "spec" would refer to the mix number. 73 de NØIGU
Jon
On Sunday, April 12, 2020, 10:49:29 AM CDT, Bob McGraw - K4TAX <rmcgraw@...> wrote:
There are no "specs" as to the type of chokes used. All chokes
are not created equal. 73 Bob, K4TAX
On 4/12/2020 9:46 AM, neil_zampella
wrote:
Bob, he's given you the link to the cables at Amazon, all you have
to do is click on the link. On 4/12/2020 10:32 AM, Bob McGraw -
K4TAX wrote:
Please share where you obtained these and any other model/ spec information. Many of us could take advantage of this information. Bob, K4TAXOn Apr 12, 2020, at 9:28 AM, John <jonie41@...> wrote: You could also only use cables that have chokes on them. These are what I use, no problems in my shack. https://www.amazon.ca/Hi-Speed-Cable-Ferrite-Chokes-3-Ft/dp/B008VOPCGY/ref=sr_1_1?crid=XE1SX7A7UMVB&keywords=tripp+lite+usb+2.0+hi-speed+a%2Fb+cable+with+ferrite+chokes&qid=1586701608&sprefix=usb+cables+a+to+b+with+choke%2Caps%2C178&sr=8-1 John VE3KKQ---------- Original Message ---------- From: Bill Somerville <g4wjs@...> Date: April 12, 2020 at 10:03 AMOn 12/04/2020 14:22, Ed Oxer, W8EO wrote: What is this? This message appears randomly. I have read all the info on the Web about this and am no further ahead in addressing this. Sometimes the app works well but at other times this message appears even when the app is working. Sometimes the message shuts down the radio. After alot of "horsing" around I can fix this problem but with no degree of consistency. In advance thanks for any help.Hi Ed, the most likely cause is RFI disrupting the USB connection between your rig and PC. Try using a different aerial, dummy load, or reduced power and see if that eliminates the issue. 73 Bill G4WJS.
|
|