How does FLRig work with TCPIP? I am running DL2RUM's WithoutWire that creates a CI-V (Cat) interface on a TCP port. I give FLRig the address (it is 127.0.0.1) and the port number (7355) selected in

I think I found part of the issue. I had use tcpip checked. When I unchecked that FLRig started working. 73, Mark, N8ME

I had it happen again just now. I've been on FT8 all day trying to catch this happening again with more attention paid to the actual steps taken. I had a QSO with one other "/" call today with no

Sorry for the duplicate post, but I can't find my original post and wanted to add some more information. I can't get FLRig (1.4.3.16) to connect to my IC-7610 over USB. I have another program

I can't seem to get FLRig to connect to my Icom IC-7610 which is connected via USB. I have another program. RUMlogNG that has no problem connecting using the same hardware. The serial device

More...   It crashed when I attempted to send my TX 3 response. AL, K0VM

( WSJT-X 2.5.3 Win 11/64 ) I too had a WSJT-X crash while attempting to work a / call ( N4CXH/4 ).. I have worked other / calls  with 2.5.3 but that was the first one that crashed. AL, K0VM

I would find this functionality useful too although I appreciate it's a bit of a niche market. I'm often monitoring 136KHz with a loop antenna into an FT817 and an inverted L into an RSP1a. The RSP1a

OS:Windows 10 (21H2), 64-bit Rig: Kenwood TS-450S + TTL Serial2USB converter for CAT Version 2.5.0 w/o issues in this manner. After programm start the QRG was read from the radio. Upgraded to 2.5.3

Did you happen to try and work any stations with "/stroke" identifier? There's a thread going right now about crashes exactly as you describe when interacting with /stroke calls. You don't have to

Several people including me have had this happen while working a call with “/“ in the call sign. I’m not aware of a fix yet other than roll back to version 2.5.2. Bruce - K5WBM

This morning I upgraded to WSJT-X version 2.5.3. I also upgraded to JTAlert 2.50.9. All seemed to work smoothly for about an hour. I worked a number of stations using FT8 on both 20m and 15m. Suddenly

Faulting application name: wsjtx.exe, version: 2.5.3.0, time stamp: 0x61b0e1e7 Faulting module name: ntdll.dll, version: 10.0.19041.1288, time stamp: 0xa280d1d6 Exception code: 0xc0000374 Fault

Hi Wayne Interesting. If you can collect some wave file examples (Save All) and send me a few where you are seeing this behaviour, I would be happy to take a look at them here. 73 Charlie

Thanks Charlie, the signals yesterday weren’t overlapping and the weaker signal was around -10.I set F Tol to 50hz positioned on the weaker signal but still only decoded the strongest signal. I

W7CT and i were using generated responses. No responses typed in manually. Max NG7M

I too am seeing this crashing when using WSJT-X V2.5.3 (Win 10, 64-bit) with certain portable calls. Using along side HRD for rig control and logging. I can't get it to happen every time, but it's

Hit the a=b button. I found that a band or mode change can make the vfos different and unwilling to cooperate.

Hi Charlie, it would be interesting to hear from the authors if this code is also the base of the of the binaries published on https://physics.princeton.edu//pulsar/K1JT/wsjtx.html. 73, Walter

Thanks to Chet Fennell, KG4IYS, installation packages for WSJT-X 2.5.3 on Debian-based (Debian, Ubuntu 20.04 LTS, ...) and Fedora-based (Fedora 34, RedHat, ...) flavors of Linux have been posted on