error using ft-857, digikeyer ii and wsjt-x
Library to control radio transceivers and receivers
Brought to you by:
n0nb
Menu
▾
▴
Hi guys,
trying to do ft8 using ft-857, digikeyer ii and wsjt-x I've got the error: "hamlib error: communication timed out while exchanging VFOs"
Changing the trx and using a ftdx5k the configuration works well.
The error occurs on windows 10 home 1803 and also on windows 7 home.
Does anybody knows a fix?
73 Ralph
Hi Ralph,
wht action in WSJT-X was happening or just happened in WSJT-X when this error message occurred?
73
Bill
G4WJS.
Hi Bill,
it was on starting up WSJT-X, just after configure the settings of the radio.
Clicking "OK" WSJT-X tried to connect the radio and that message appears.
73
Ralph
Hi Ralph,
can you reply with a summary of the options you have selected on the WSJT-X "Settings->Radio" panel. Or a screen capture.
73
Bill
G4WJS.
Hi Bill,
these is my configuration.
Am 16.04.2019 um 20:54 schrieb Bill Somerville:
Hi Ralph,
thanks for that.
You need to set "Settings->Radio->Handshake->Default" (or "None" which is the same for this rig). I recommend "Settings->Radio->Mode->Data/Pkt" and have yourrig's DIGI mode as USB (set MENU DIG MODE to USER-U, DIG DISP to 0 Hz, and DIG SHIFT to 0 Hz for correct Rx frequency readout), this bypasses mic circuits and allows a separate Rx filter setup for digimodes. Also for this rig you should leave "Settings->General->Allow Tx frequency changes while trasmitting" unchecked as teh FT-817/857/897(D) models do not accept CAT QSY commands while in Tx mode.
73
Bill
G4WJS.
Hi Bill,
thanks for the advice.
Unfortunately it doesn't fix my problem.
Meanwhile I've downloaded the hamlib-package and started some tests.
I can connect my trx using the rigctl-command.
But if I try to change something, i.e. the frequency my trx changes it but gives back an error "set_freq: error = Communication timed out".
I've tried 32-bit and 64-bit-version of hamlib 3.3.
73
Ralph
Some additional information from rigctl follows:
Rig command: F 3574000
Frequency: rig_set_freq called
ft857: requested freq = 3574000.000000 Hz
to_bcd_be called
rig_force_cache_timeout called
write_block called
read_block called
read_block(): Timed out 0.718906 seconds after 0 chars
ft857: error reading ack
set_freq: error = Communication timed out
Hi Ralph,
ok, please run the rigctl test again but add -vvvvv to the command line options. Please reply with the exact command line you used and the output up to the first timeout error message.
I suspect teh CAT connebtion is not set up correctly, perhaps the rig is not in CAT mode or the baud rate does not match?
73
Bill
G4WJS.
Last edit: Bill Somerville 2019-04-17
Hi Bill,
here comes the screendump:
d:\temp\hamlib64\hamlib-w64-3.3\bin>rigctl -r COM2 -s 38400 -vvvvv -m 122
rigctl, Hamlib 3.3
Report bugs to hamlib-developer@lists.sourceforge.net
rig_init called
yaesu: initrigs3_yaesu called
rig_register called
rig_register: rig_register (121)
rig_register called
rig_register: rig_register (127)
rig_register called
rig_register: rig_register (110)
rig_register called
rig_register: rig_register (105)
rig_register called
rig_register: rig_register (106)
rig_register called
rig_register: rig_register (107)
rig_register called
rig_register: rig_register (109)
rig_register called
rig_register: rig_register (120)
rig_register called
rig_register: rig_register (101)
rig_register called
rig_register: rig_register (122)
rig_register called
rig_register: rig_register (123)
rig_register called
rig_register: rig_register (111)
rig_register called
rig_register: rig_register (115)
rig_register called
rig_register: rig_register (113)
rig_register called
rig_register: rig_register (114)
rig_register called
rig_register: rig_register (128)
rig_register called
rig_register: rig_register (131)
rig_register called
rig_register: rig_register (116)
rig_register called
rig_register: rig_register (103)
rig_register called
rig_register: rig_register (124)
rig_register called
rig_register: rig_register (104)
rig_register called
rig_register: rig_register (125)
rig_register called
rig_register: rig_register (129)
rig_register called
rig_register: rig_register (132)
rig_register called
rig_register: rig_register (130)
rig_register called
rig_register: rig_register (117)
rig_register called
rig_register: rig_register (119)
rig_register called
rig_register: rig_register (118)
rig_register called
rig_register: rig_register (126)
rig_register called
rig_register: rig_register (133)
rig_register called
rig_register: rig_register (134)
rig_register called
rig_register: rig_register (135)
rig_register called
rig_register: rig_register (136)
ft857:ft857_init called
rig_open called
port_open called
serial_open called
serial_setup called
ft857:ft857_open called
rig_get_vfo called
Opened rig model 122, 'FT-857'
rig_strstatus called
Backend version: 0.5, Status: Beta
Rig command: f
rig_get_freq called
ft857: cache invalid
serial_flush called
write_block called
write_block(): TX 5 bytes
0000 00 00 00 00 03 .....
read_block called
read_block(): RX 5 bytes
0000 00 35 73 00 0a .5s..
write_block called
write_block(): TX 5 bytes
0000 00 78 00 00 bb .x...
read_block called
read_block(): RX 2 bytes
0000 a0 00 ..
from_bcd_be called
Frequency: 3573000
Rig command: F 357400
Frequency: rig_set_freq called
ft857: requested freq = 357400.000000 Hz
to_bcd_be called
rig_force_cache_timeout called
write_block called
write_block(): TX 5 bytes
0000 00 03 57 40 01 ..W@.
read_block called
read_block(): Timed out 0.721865 seconds after 0 chars
ft857: error reading ack
set_freq: error = Communication timed out
Rig command:
The communication speed of the trx is set to 38400 Baud and, as you can see, reading frequencies works fine.
73 Ralph
Hi Ralph,
can you try again with a valid amateur HF band frequency, I think you dropped trailing zero.
73
Bill
G4WJS.
Hi Bill,
I'm sorry for this mistake.
d:\temp\hamlib64\hamlib-w64-3.3\bin>rigctl -r COM2 -s 38400 -vvvvv -m 122
rigctl, Hamlib 3.3
Report bugs to hamlib-developer@lists.sourceforge.net
rig_init called
yaesu: initrigs3_yaesu called
rig_register called
rig_register: rig_register (121)
rig_register called
rig_register: rig_register (127)
rig_register called
rig_register: rig_register (110)
rig_register called
rig_register: rig_register (105)
rig_register called
rig_register: rig_register (106)
rig_register called
rig_register: rig_register (107)
rig_register called
rig_register: rig_register (109)
rig_register called
rig_register: rig_register (120)
rig_register called
rig_register: rig_register (101)
rig_register called
rig_register: rig_register (122)
rig_register called
rig_register: rig_register (123)
rig_register called
rig_register: rig_register (111)
rig_register called
rig_register: rig_register (115)
rig_register called
rig_register: rig_register (113)
rig_register called
rig_register: rig_register (114)
rig_register called
rig_register: rig_register (128)
rig_register called
rig_register: rig_register (131)
rig_register called
rig_register: rig_register (116)
rig_register called
rig_register: rig_register (103)
rig_register called
rig_register: rig_register (124)
rig_register called
rig_register: rig_register (104)
rig_register called
rig_register: rig_register (125)
rig_register called
rig_register: rig_register (129)
rig_register called
rig_register: rig_register (132)
rig_register called
rig_register: rig_register (130)
rig_register called
rig_register: rig_register (117)
rig_register called
rig_register: rig_register (119)
rig_register called
rig_register: rig_register (118)
rig_register called
rig_register: rig_register (126)
rig_register called
rig_register: rig_register (133)
rig_register called
rig_register: rig_register (134)
rig_register called
rig_register: rig_register (135)
rig_register called
rig_register: rig_register (136)
ft857:ft857_init called
rig_open called
port_open called
serial_open called
serial_setup called
ft857:ft857_open called
rig_get_vfo called
Opened rig model 122, 'FT-857'
rig_strstatus called
Backend version: 0.5, Status: Beta
Rig command: f
rig_get_freq called
ft857: cache invalid
serial_flush called
write_block called
write_block(): TX 5 bytes
0000 00 00 00 00 03 .....
read_block called
read_block(): RX 5 bytes
0000 00 35 74 00 0a .5t..
write_block called
write_block(): TX 5 bytes
0000 00 78 00 00 bb .x...
read_block called
read_block(): RX 2 bytes
0000 a0 00 ..
from_bcd_be called
Frequency: 3574000
Rig command: F 3573000
Frequency: rig_set_freq called
ft857: requested freq = 3573000.000000 Hz
to_bcd_be called
rig_force_cache_timeout called
write_block called
write_block(): TX 5 bytes
0000 00 35 73 00 01 .5s..
read_block called
read_block(): Timed out 0.720933 seconds after 0 chars
ft857: error reading ack
set_freq: error = Communication timed out
Hi Ralph,
thanks again. Make sure the rig is not in memory mode.
73
Bill
G4WJS.
Hi Bill,
the rig is in VFO-Mode.
It also changes the frequency, then the error occures.
73 Ralph
Hi Ralph,
hmmm, something odd is happening. Is this a real FT-857 or some other rig that emulates one? Is the CAT connection direct or do you have an ATU in-line? Have you tried any of the reset options in the manual?
73
Bill
G4WJS.
Hi Ralph,
hmmm, something odd is happening. Is this a real FT-857 or some other rig that emulates one? Is the CAT connection direct or do you have an ATU in-line? Have you tried any of the reset options in the manual?
73
Bill
G4WJS.
Hi Bill,
I guess, it is a real FT-857D or so its frontpage says ;-).
It's a direct connection without any other devices.
As far as I can remember I tried a general reset some weeks ago.
Do you have any suggestion for a reset?
73 Ralph
Curious thing - right now I performed a master reset, the error is still the same.
Hi Ralph,
I am out of ideas, at least ones that a user should be considering. All I can suggest is trying a different CAT interface, although the problem seems to lie within the rig since it responds correctly to a frequency query but not to a frequency set command. It is behaving as if the rig is permanently in transmit mode where it doesn't accept CAT QSY commands.
73
Bill
G4WJS.
O.K. Bill, thanks a lot for your help.
I'll try a different interface.
73 Ralph