ICOM 2730a > Hamlib -> Gpredict , Can't get it to change frequency based on doppler shifts. But I can manually change the Downlink frequency.
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 15/100
Research direction
The log shows rigctld failing on the IC-2730 at startup: the icom_get_freq call sends command 0x25 and gets back a 0xFA reply, so icom_one_transaction returns -9 in frame.c. Start from that log segment and the icom backend's frequency-set path, then check whether the radio accepts set-frequency commands over COM1 at 19200 baud. Done would mean GPredict's Doppler-corrected frequency reaches the radio through rigctld. This needs radio and Hamlib protocol knowledge, and the thread has been idle for over two years.
Written by the indexing model from the issue text.
Description
I am running a .bat : rigctld -vvvvv -m 3072 -r COM1
It's not working with adjusting the frequency as GPredict makes doppler shift adjustments. If I change the radio control Downlink frequency it gets sent and changes radio, but if I choose to Track then the doppler frequency is not changing on radio.
Can you identify any issue or suggest a better .bat command that may assist in getting the frequency to consistently change with what GPredict is changing the frequency to?
In GPRedict I have Host localhost, Port 4532, Radio type I've tried all choices, PTT Status I've tried all settings, also VFO Up/Down same thing. No matter what I do with settings I can't resolve the issue.
LOG SEGMENT
C:\Users\garmi\OneDrive\Desktop\AntRunner-master\software\hamlib-w64-4.5git\bin>rigctld -vvvvv -m 3072 -r COM1
rigctld.c(626) Startup: rigctld -vvvvv -m 3072 -r COM1
rigctld Hamlib 4.5git Tue May 17 22:03:48 2022 +0000 SHA=468dd1
Report bugs to [email protected]
Max# of rigctld client services=32
rig_check_rig_caps: p1=000000005C104E60, p2=000000005C10B3D8, rig_model=000000005C104E60, macro_name=000000005C10B3D8
initrigs4_icom: _init called
rig_init(496): 0000000000F2AFFC rs->comm_state==0?=0
rig_init: rig has VFO_SUB
rig_init: rig has VFO_MAIN
1:icom.c(613):icom_init entered
icom_init: done
1:icom.c(695):icom_init returning(0)
main: twiddle=0, uplink=0, twiddle_rit=0
1:rig.c(743):rig_open entered
rig_open: cwd=C:\Users\garmi\OneDrive\Desktop\AntRunner-master\software\hamlib-w64-4.5git\bin
rig_open: C:\Users\garmi\OneDrive\Desktop\AntRunner-master\software\hamlib-w64-4.5git\bin/.hamlib_settings does not exist
serial_open: COM1
serial_setup: tcgetattr
serial_setup: cfsetispeed=19200,0x000e
serial_setup: cfsetospeed=19200,0x000e
serial_setup: data_bits=8
serial_setup: parity=0
serial_setup: Handshake=None
serial_setup: tcsetattr TCSANOW
read_string_generic called, rxmax=4095 direct=1
2:rig.c(7055):async_data_handler_start entered
async_data_handler_start: async data support disabled
2:rig.c(7060):async_data_handler_start returning(0)
rig.c(241):add_opened_rig returning2(0)
rig_open: 0000000000F2AFFC rs->comm_state==1?=1
2:icom.c(944):icom_rig_open entered
icom_rig_open: IC-2730 v20220326.0
3:icom.c(748):icom_get_usb_echo_off entered
4:frame.c(425):icom_transaction entered
icom_transaction: cmd=0x03, subcmd=0xffffffff, payload_len=0
5:frame.c(138):icom_one_transaction entered
rig_flush: called for serial device
read_string_generic called, rxmax=4095 direct=1
write_block(): TX 6 bytes, method=2
0000 fe fe 90 e0 03 fd ......
read_string_generic called, rxmax=200 direct=1
read_string_generic: minlen now 6
read_string_generic(): RX 6 characters, direct=1
0000 fe fe 90 e0 03 fd ......
icom_one_transaction: frm_len=6, frm_len-1=fd, frm_len-2=03
5:frame.c(403):icom_one_transaction returning(0)
4:frame.c(455):icom_transaction returning(0)
icom_get_usb_echo_off: ack_len=1
read_string_generic called, rxmax=200 direct=1
read_string_generic: minlen now 11
read_string_generic(): RX 11 characters, direct=1
0000 fe fe e0 90 03 00 00 62 45 01 fd .......bE..
icom_get_usb_echo_off: USB echo on detected, get freq retval=11
3:icom.c(777):icom_get_usb_echo_off returning(0)
icom_rig_open: echo status result=0
icom_rig_open: echo status known, getting frequency
rig_get_freq(1837) called vfo=currVFO
vfo_fixup:(from rig_get_freq:1843) vfo=currVFO, vfo_curr=None, split=0
vfo_fixup: Leaving currVFO alone
rig.c(1846) vfo=currVFO, curr_vfo=None
rig_get_freq: cache miss age=1000000ms, cached_vfo=None, asked_vfo=None
rig_get_freq(1928): vfo_opt=0, model=3072
icom_get_freq called for None, curr_vfo=None
icom_get_freq: using vfo=None
3:frame.c(425):icom_transaction entered
icom_transaction: cmd=0x25, subcmd=0x00, payload_len=0
4:frame.c(138):icom_one_transaction entered
rig_flush: called for serial device
read_string_generic called, rxmax=4095 direct=1
write_block(): TX 7 bytes, method=2
0000 fe fe 90 e0 25 00 fd ....%..
read_string_generic called, rxmax=200 direct=1
read_string_generic: minlen now 7
read_string_generic(): RX 7 characters, direct=1
0000 fe fe 90 e0 25 00 fd ....%..
icom_one_transaction: DEBUG retval=7, frm_len=7, cmd=0x25
read_string_generic called, rxmax=200 direct=1
read_string_generic(): RX 6 characters, direct=1
0000 fe fe e0 90 fa fd ......
4:frame.c(352):icom_one_transaction returning(-9) rigctld.c(626) Startup: rigctld -vvvvv -m 3072 -r COM1
rigctld Hamlib 4.5~git Tue May 17 22:03:48 2022 +0000 SHA=468dd1
Report bugs to [email protected]
- Dominant language
- C
- Stars
- 1.2k
- Forks
- 305
- Avg merge
- 8h 48m
- Merged PRs (30d)
- 3
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from csete/gpredict
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 Under an hour Newbie friendliness 60/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 4/5 3-5 days Newbie friendliness 78/100
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
EchoTools/nevr-runtime#698 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
FujiNetWIFI/fujinet-firmware#2079 ·
Maintainers usually reply within 1 day
-
bug Official Image release/25.12 Supported Device target/kirkwood
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
area/archive bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
DarkFlippers/qUnleashed#374 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 84/100
VirusTotal/yara#2255 ·