开云体育

I'm able to do FT8 but am having no joy with JS8Call setup. ?

Radio: TX500 with latest firmware
Interface: Digirig for TX500 on COM6 at 9600 Baud
Computer: Windows 10

Windows Sound Settings:
?- Master Volume = 75%
?- Mic = Digirig. ?AGC = OFF. ?Levels = 11%
?- Speakers = Digirig = 75%

Radio Settings:
?- Mode = DIG
?- Menu 06 ACG>SSB = 1
?- Menu 07 RF>SSB = -5
?- Menu 09 Gain>DIG = 23
?- Menu 10 NR Level = 10
?- Menu 11 NB Level = 40
?- Menu 13 SQL>SSB/AM = 0
?- Menu 17 CMR Level = 3
?- Menu 19 EQL > RX LF = 100
?- Menu 19 EQL > TX LF = 100
?- Menu 34 CAT Protocol = TS2000

JS8Call (v2.2.0) Settings:
?- Radio Tab > Rig = Kenwood TS-2000
?- Radio Tab > CAT Control > Serial Port = COM6
?- Radio Tab > CAT Control > Baud Rate = 9600
?- Radio Tab > CAT Control > Data Bits, Stop Bits, Handshake: all = Default
?- Radio Tab > Rig Options > PTT Method = CAT
?- Radio Tab > Rig Options > Mode = Data/Pkt
?- Radio Tab > Rig Options > Split Operation = Fake It
?- Audio Tab > Input, Output both = Digirig, mono
?- Audio Tab > Notification Soundcard Output = Digirig

I get "Rig Control Error: Hamlib error: Protocol error while testing getting current VFO" and radio does not go into transmit. ?

Any thoughts?

Hi Kathleen

Try this link and you will find an attached pdf. See if you got the right settings from the pdf. Hope this helps.

/g/Lab599/topic/89671873

73, Pier, HB9IIA

Kathleen,

If you use multiple radio apps best use Flrig as middleware. Much more stable and convenient this way. Also, it has the TX500 listed. Pretty sure it’ll solve your problem.

I did try flrig because I do want to try fldigi at some point, but I never did get flrig working.? That's another story. However, I'm up and running with JS8Call.?

It needed to run the 2.2.1-devel version provided by Joe K0OG over in the JS8Call GroupsIO at this location:?

https://www.dropbox.com/scl/fo/j0kiml3wmka1a7dm0f6wt/h?rlkey=v5r84o3uneuz6fyoidtwqko1z&e=2&dl=0

That one includes the most recent Hamlib files for the TX-500. ?However, the program has to be run in compatibility mode". But when you do, it works perfectly with all the same settings as WSJT-X.??

Leaving this here for anyone else who might find it useful.