ID5100 gpredict problem

[mdblack98]

I may have discovered an issue. I continued playing with hamlib and Gpredict after I sent my first reply.

See the attached log file using Notepad++ as you continue to read this.
Line 815: S command from gpredict
Line 969: t command from gpredict
Line 1001: F 437028988 command from gpredict
Line 1083: f command from gpredict
Line 1102: I 145901999 command from grpredict
Line 1869: i command from gpredict
Line 2015: t command from grpedict
Line 2047: f command from gpredict
Line 2066: F 437028990 command from gpredict
Line 2148: f command from gpredict
Line 2156: Cache hit reported. No communciations with the rig.
Line 2167: i command from gpredict
Line 2181: Command sent to rig to enter single watch mode
Line 2186: The rig replied OK
Line 2195: Command sent to rig to read duplex setting
Line 2200: The rig replied simplex.
Line 2214: Command sent to rig to select A band <------- Problem!
Line 2219: The rig replied OK
Line 2234: Command sent to rig to read the frequency
Line 2239: The rig replied with 437.300 MHz
Line 2260: Command sent to rig to enter dual watch mode
Line 2265: The rig replied OK
Line 2274: Command sent to rig read duplex setting
Line 2279: The rig replied simplex
Line 2293: Command sent to rig to select A band
Line 2298: The rig replied OK
From this point on, gpredict used 437.300 as both the TX and RX frequencies.

Since in line 2167, hamlib received an i command, it should have returned the RX frequency. Instead it returned the TX frequency. You can see in line 2214 that hamlib told the rig to select the A band instead of the B band. I do not know why.

Please investigate.

Thanks!

Lee Ott
WA4CNL
Hamlib log 20131111.txt