FT-857D RX frequency increments for satellites with identical RX and TX frequencies about gpredict

[mdblack98]

Can you compile Hamlib -- try the latest here... https://n0nb.users.sourceforge.net/ Mike W9MDB On Monday, March 13, 2023 at 01:05:10 PM CDT, Kristijan Conkas ***@***.***> wrote: This may be related to #294 . I am trying to use gpredict for greencube. To define both the uplink and downlink frequencies, I added the following section to ~/.config/Gpredict/trsp/53106.trsp: [Mode U GMSK FULL DUPLEX] DOWN_LOW=435310000 UP_LOW=435310000 MODE=FSK AX.100 Mode 5 BAUD=1200 I defined a rig for this as "FT817/857/897 (auto)" with PTT Status set to "Read PTT". Its .rig file is as follows: [Radio] Host=localhost Port=4533 LO=0 LO_UP=0 Type=4 PTT=1 SIGNAL_AOS=false SIGNAL_LOS=false My problem is when I start tracking the satellite and click "Engage", at first everything is normal; both the Downlink and Uplink radio frequencies get updated regularly. After about 7-8 seconds, both the Downlink and Uplink radio frequencies get set to the same (Uplink) frequency and my Downlink frequency automatically shifts up. From this point onwards, my Downlink radio frequency tracks the Uplink radio frequency. Fedora 37, gpredict 2.2.1, hamlib-4.5.4. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[kconkas]

Thanks for the suggestion @mdblack98 . I built hamlib from its current github snapshot (commit 24a4a094843c5c149be76277a9ab3704b8b097b7) and I saw a few of your FT-857 fixes in the commit log. Unfortunately, the behaviour reported in this bug is still present. I'd appreciate any suggestions from anyone who may have got this working.

[mdblack98]

Ok -- now run rigctld with "-vvvvv -Z >log.txt 2>&1" added to the line and send me the debug file with a description of what you are seeing. Mike W9MDB On Wednesday, March 15, 2023 at 03:45:59 AM CDT, Kristijan Conkas ***@***.***> wrote: Thanks for the suggestion @mdblack98 . I built hamlib from its current github snapshot (commit 24a4a094843c5c149be76277a9ab3704b8b097b7) and I saw a few of your FT-857 fixes in the commit log. Unfortunately, the behaviour reported in this bug is still present. I'd appreciate any suggestions from anyone who may have got this working. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>

[mdblack98]

Also....try my fork and add "--vfo" to your rigctld command line. VFO mode is much better for gpredict usage.
https://github.com/mdblack98/gpredict

[kconkas]

@mdblack98 please find the log below. This is with your fork of gpredict, latest snapshot of hamlib and rigctld used with the --vfo option.
log.txt

[mdblack98]

Doesn't look like you were using my fork of gpredict as it is not using the --vfo option correctly. My fork does work with --vfo.

[kconkas]

@mdblack98 I built both from source code. Is there anything that needs setting up in gpredict to make it work?

[mdblack98]

Run rigctld with the --vfo option Mike W9MDB On Friday, March 17, 2023 at 12:36:11 PM CDT, Kristijan Conkas ***@***.***> wrote: @mdblack98 I build both from source code. Is there anything that needs setting up in gpredict to make it work? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>

[kconkas]

@mdblack98 this is the 1st line in the output I'd attached previously:

2023-03-15T22:50:02.471865-0000: rigctld.c(660) Startup: /usr/local/bin/rigctld -r /dev/ttyUSB11 -t 4533 -s 9600 -m 1022 --vfo -vvvvv -Z

Is this what you meant or is it somewhere else I should've added --vfo to?

[mdblack98]

That looks correct. You can redirect the output by adding ">log.txt 2>&1" Then when things don't work note the time and frequencies involved and send me at least the last few thousand lines of log.txt or zip the whole thing. On Sunday, March 19, 2023 at 11:37:52 AM CDT, Kristijan Conkas ***@***.***> wrote: @mdblack98 this is the 1st line in the output I'd attached previously: 2023-03-15T22:50:02.471865-0000: rigctld.c(660) Startup: /usr/local/bin/rigctld -r /dev/ttyUSB11 -t 4533 -s 9600 -m 1022 --vfo -vvvvv -Z Is this what you meant or is it somewhere else I should've added --vfo to? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: ***@***.***>

[zyg0121]

I found the same problem today. Wanna know how to solve it...