Re: [wsjt-devel] WSJT-X Bug Report

First let's install a new Hamlib -- then if that doesn't fix things we'll go to the debug stage... New hamlib for installation directions #1 Shut down WSJTX  #2 Download either the 32-bit or 64-bit DLL matching the 32/64-bit version of WSJTX -- hopefully your browser doesn't block it but may w

[wsjt-devel] WSJT-X Bug Report

I've been annoyed by this for a while and believe I've finally made sense of what's going on. Rig - Yaesu FTDX10 Windows 10 WSJT-X v 2.6.1 6b6d74 When the IF bandwidth on the FTDX10 is set to anything above 3000 HZ the problem will show up after switching modes (from FT8 to FT4 for instance) and

Re: [wsjt-devel] WSJT-X Bug?

Not a WSJT-X bug ... sounds more like RFI getting into the USB cable Neil, KN3ILZ On 4/2/2020 8:33 PM, Tom Stock wrote: Hello, I'm having a problem with version 2.1.2 68f9 Problem: When in transmit mode, WSJT-X will suddenly switch from my usb codec for output (my signalink usb) to the spea

Re: [wsjt-devel] WSJT-X Bug?

Please disregard previous bug report Turns out I had a wonky USB hub. I think the error handling must be a bit more robust in the windows version, because the windows version in a virtual box on my Mac gave me no problems at all. Running the native version resulted in the original issues reported

[wsjt-devel] WSJT-X Bug?

Hello, I'm having a problem with version 2.1.2 68f9 Problem: When in transmit mode, WSJT-X will suddenly switch from my usb codec for output (my signalink usb) to the speakers. I can hear the transmission, and the transmitter stops transmitting. If I look in Preferences->Audio both usb codecs a

Re: [wsjt-devel] WSJT-X bug report

On 26/12/2019 17:40, DX Jami via wsjt-devel wrote: My point is WSJT-X should allow "non-standard" call signs. Danny, WSJT-X goes to a lot of trouble to support "non-standard" callsigns, but there is no free lunch. The non-standard callsigns supported by WSJT-X in MSK144, FT4, and FT8 modes a

Re: [wsjt-devel] WSJT-X bug report

Thanks Saku.  I understand the work-around and use various versions myself.  My point is WSJT-X should allow "non-standard" call signs.  Those non-standard calls are only non-standard for WSJT-X and A-OK for the rest of the ham radio world.  Many DXpeditions have similar problems as does almost

Re: [wsjt-devel] WSJT-X bug report

DX Jami via wsjt-devel kirjoitti 24.12.2019 klo 15.26: Another shortfall with non-standard calls is signing like me - W4/AH6FX. The "real estate" shortfall does not allow passing my grid, so that is very bothersome to some folks. Hi! There is a good practice for this used by F5MYK/MM. For ev

Re: [wsjt-devel] WSJT-X bug report

Zoli, That is a shortfall within WSJT-X.  There is not enough "real estate" in the programming framework to allow two non-standard call signs to trade exchanges.  Another shortfall with non-standard calls is signing like me - W4/AH6FX.  The "real estate" shortfall does not allow passing my grid

Re: [wsjt-devel] WSJT-X bug report

Thank you all for the response! Shouldn’t there be a way to not let one user with a special call-sign call someone else with the same type of call-sign.  I had to wait for quite a while for someone to let go trying and continue working as he was locking me by calling me.  All the best!Zoli Sent

Re: [wsjt-devel] WSJT-X bug report

Zoli! You got a nice work-around for working non-standard call signs. The Users Guide states in clause 7.5 Except for the special cases involving /P or /R used in VHF contesting, WSJT-X 2.1 offers no support for two nonstandard callsigns to work each other. Good luck and 73, Reino oh3mA

Re: [wsjt-devel] WSJT-X bug report

Two non standard calls can not work each other. On Dec 23, 2019 9:14 AM, Zoltan Vodinszki via wsjt-devel wrote: Hi, These days I am working with a special call sign (YP3XMAS). During my work, I have observed a strange behavior when two special call-signs try to work each other or when a specia

Re: [wsjt-devel] WSJT-X bug report

Zoli! Use free text and give his call sign and report 73 Keijo OG55W From: Zoltan Vodinszki via wsjt-devel Sent: Monday, December 23, 2019 4:14 PM To: wsjt-devel@lists.sourceforge.net Cc: Zoltan Vodinszki Subject: [wsjt-devel] WSJT-X bug report Hi, These days I am working with a special

[wsjt-devel] WSJT-X bug report

Hi, These days I am working with a special call sign (YP3XMAS).During my work, I have observed a strange behavior when two special call-signs try to work each other or when a special call-sign tries to work a longer call-sign like QRP or /. When I get called by such call-signs, instead of WSJT-X

[wsjt-devel] WSJT-X Bug: Software doesn't accommodate the RTS PTT method when driver usbser.sys is in use

I am a Remote Ham Radio (RHR)( www.remotehamradio.com) member. Recently, I had the urge to test WSJT-X while connected to an RHR remote K3 using a K3/0 Mini and RRC-1258. I assumed that the CAT and PTT ports that I use with N1MM Logger+ would work. However, CAT con

[wsjt-devel] WSJT-X bug

latest version 1.7.0 Opersting in Windows XP Previous version worked fine, but have noticed a small bug on selecting decode. When you double click on the waterfall, or click DECODE button, the program decodes all received, not just at the selected frequency. Neil Hutton m0...@neilhutton.com

Re: [wsjt-devel] WSJT X Bug report on JT4g

Thanks Joe All OK now with r5690 and does now give decodes with G bin-width. Rex VK7MO On 7/07/2015 3:57 AM, Joe Taylor wrote: > Hi Rex and Charlie, > > Thanks for your help in identifying the bug in decoding submode JT4G > with MinW=G. I believe it has been fixed in revision 5690. > >

Re: [wsjt-devel] WSJT X Bug report on JT4g

Hi Rex and Charlie, Thanks for your help in identifying the bug in decoding submode JT4G with MinW=G. I believe it has been fixed in revision 5690. -- Joe On 7/6/2015 10:41 AM, char...@sucklingfamily.free-online.co.uk wrote: > Hi Joe > > Rex is probably in bed now. > > You don't need a

Re: [wsjt-devel] WSJT X Bug report on JT4g

Hi Joe Rex is probably in bed now. You don't need a specific file to demonstrate this bug - simply set MinW to G and submode to G. Here's an example I just did: 2146-125-0.69 599 * 2146 -8 3.40 801 * DL0SHF 46HID * F 2146-125-0.69 599 * line 1 and line 3 with MinW at G, line 2 wi

Re: [wsjt-devel] WSJT X Bug report on JT4g

Hi Rex, Thanks for catching and reporting this bug. I'm not presently at a location where it's convenient to generate test files. Could you send me one or two example files that contain signals with suitable S/N and spread that should be decodable in the "G" submode? -- Joe, K1JT On

[wsjt-devel] WSJT X Bug report on JT4g

WSJT X version: r5604 Operating System: Windows XP Symptoms: Does not decode in the "G" bin-width even when decoding marginal signals with 300 Hz spreading Other Symptoms: If you try and force "G" bin-width decodes by setting MinW to "G" the program gives a faulty output of dB = -125, DT =

[wsjt-devel] WSJT-X bug, and feature idea "follow their clock".

Dear developers, 20 m length of end-fed wire sloping down from about 10 to 2 m above urban jungle ground with a mere 5 W to feed it - mine is a "little pistol" setup. I've used the WSPR and WSJT-X programs a lot. I'm very happy what they enable me to do with my small station. Today, I want to a