Strange one, possibly not a problem with CQRlog, but worked in 0.9.x

3 posts / 0 new
Last post
OZ1PIF
Strange one, possibly not a problem with CQRlog, but worked in 0.9.x

I'm not sure whether this is a bug report, a feature request or maybe a hamlib problem: when I click on a Bandmap spot for Radio1 (in my case a TT Orion 2) the VFO freq. is adjusted to the requested freq. this is not the case when TRX control has Radio2 selected (in my case a Yaesu FT-847).
After switching the radios around, I can conclude that the problem is in communicating with the FT-847. An attempt to switch band yields following sequence in terminal:
RIG_RESULT1: RIG_OK
RIG_RESULT2: RIG_OK
PollRadio
fRigMode:RIG_MODE_USB
fRigFrequency: 5.02930000000000E+007
Freq2: 5.02930000000000E+007 Model:101
PollRadio
fRigMode:RIG_MODE_USB
fRigFrequency: 5.02930000000000E+007
Freq2: 5.02930000000000E+007 Model:101
PollRadio
fRigMode:RIG_MODE_USB
fRigFrequency: 5.02930000000000E+007
Freq2: 5.02930000000000E+007 Model:101
PollRadio
fRigMode:RIG_MODE_USB
fRigFrequency: 5.02930000000000E+007
Freq2: 5.02930000000000E+007 Model:101
PollRadio
fRigMode:RIG_MODE_USB
fRigFrequency: 5.02930000000000E+007
Freq2: 5.02930000000000E+007 Model:101
PollRadio
fRigMode:RIG_MODE_USB
fRigFrequency: 5.02930000000000E+007
Freq2: 5.02930000000000E+007 Model:101
PollRadio
fRigMode:RIG_MODE_USB
fRigFrequency: 5.02930000000000E+007
Freq2: 5.02930000000000E+007 Model:101
PollRadio
fRigMode:RIG_MODE_USB
fRigFrequency: 5.02930000000000E+007
Freq2: 5.02930000000000E+007 Model:101
This is an invalid mode:USB
in tRig.Close
TRX control thread terminated

After double click on callsign in "Band map", everything but the VFO-setting is OK, this is what I see in terminal:
SELECT * FROM view_cqrlog_main_by_qsodate WHERE callsign = 'S59A' ORDER BY qsodate,time_on

LoadForm: frmNewQSO
Loading: Section: frmNewQSO_dbgrdQSOBefore Ident: id_cqrlog_main Width: 0
Loading: Section: frmNewQSO_dbgrdQSOBefore Ident: qsodate Width: 100
Loading: Section: frmNewQSO_dbgrdQSOBefore Ident: time_on Width: 70
Loading: Section: frmNewQSO_dbgrdQSOBefore Ident: time_off Width: 0
Loading: Section: frmNewQSO_dbgrdQSOBefore Ident: callsign Width: 83
Loading: Section: frmNewQSO_dbgrdQSOBefore Ident: freq Width: 76
Loading: Section: frmNewQSO_dbgrdQSOBefore Ident: mode Width: 56
Loading: Section: frmNewQSO_dbgrdQSOBefore Ident: rst_s Width: 49
Loading: Section: frmNewQSO_dbgrdQSOBefore Ident: rst_r Width: 53
Loading: Section: frmNewQSO_dbgrdQSOBefore Ident: name Width: 73
Loading: Section: frmNewQSO_dbgrdQSOBefore Ident: qth Width: 91
Loading: Section: frmNewQSO_dbgrdQSOBefore Ident: qsl_s Width: 50
Loading: Section: frmNewQSO_dbgrdQSOBefore Ident: qsl_r Width: 50
Loading: Section: frmNewQSO_dbgrdQSOBefore Ident: qsl_via Width: 0
Loading: Section: frmNewQSO_dbgrdQSOBefore Ident: iota Width: 0
Loading: Section: frmNewQSO_dbgrdQSOBefore Ident: pwr Width: 60
Loading: Section: frmNewQSO_dbgrdQSOBefore Ident: itu Width: 0
Loading: Section: frmNewQSO_dbgrdQSOBefore Ident: waz Width: 0
Loading: Section: frmNewQSO_dbgrdQSOBefore Ident: loc Width: 79
Loading: Section: frmNewQSO_dbgrdQSOBefore Ident: my_loc Width: 0
Loading: Section: frmNewQSO_dbgrdQSOBefore Ident: county Width: 0
Loading: Section: frmNewQSO_dbgrdQSOBefore Ident: award Width: 0
Loading: Section: frmNewQSO_dbgrdQSOBefore Ident: remarks Width: 0
Loading: Section: frmNewQSO_dbgrdQSOBefore Ident: band Width: 0
Loading: Section: frmNewQSO_dbgrdQSOBefore Ident: dxcc_ref Width: 0
Loading: Section: frmNewQSO_dbgrdQSOBefore Ident: qso_dxcc Width: 0
Loading: Section: frmNewQSO_dbgrdQSOBefore Ident: profile Width: 0
Loading: Section: frmNewQSO_dbgrdQSOBefore Ident: idcall Width: 0
Loading: Section: frmNewQSO_dbgrdQSOBefore Ident: state Width: 0
Loading: Section: frmNewQSO_dbgrdQSOBefore Ident: lotw_qslsdate Width: 0
Loading: Section: frmNewQSO_dbgrdQSOBefore Ident: lotw_qslrdate Width: 0
Loading: Section: frmNewQSO_dbgrdQSOBefore Ident: lotw_qsls Width: 0
Loading: Section: frmNewQSO_dbgrdQSOBefore Ident: lotw_qslr Width: 0
Loading: Section: frmNewQSO_dbgrdQSOBefore Ident: cont Width: 0
Loading: Section: frmNewQSO_dbgrdQSOBefore Ident: qsls_date Width: 0
Loading: Section: frmNewQSO_dbgrdQSOBefore Ident: qslr_date Width: 0
Loading: Section: frmNewQSO_dbgrdQSOBefore Ident: club_nr1 Width: 0
Loading: Section: frmNewQSO_dbgrdQSOBefore Ident: club_nr2 Width: 0
Loading: Section: frmNewQSO_dbgrdQSOBefore Ident: club_nr3 Width: 0
Loading: Section: frmNewQSO_dbgrdQSOBefore Ident: club_nr4 Width: 0
Loading: Section: frmNewQSO_dbgrdQSOBefore Ident: club_nr5 Width: 0
SELECT id_cqrlog_main FROM cqrlog_main WHERE adif=499 AND band='6M' AND qsl_r='Q' AND mode='SSB' LIMIT 1

select band,mode from cqrlog_main where adif=499 group by band,mode

select band,mode,qsl_r,lotw_qslr from cqrlog_main where adif=499 and (qsl_r = 'Q') group by band,mode,qsl_r,lotw_qslr

select * from cqrlog_common.qslmgr where (callsign = 'S59A') and (fromDate <= '2011-06-14') order by fromDate

ok2cqr
ok2cqr's picture
Re: Strange one, possibly not a problem with CQRlog, but worked

Maybe the problem is in bandwidth settings. If you set mode, hamlib supports also filter width settings. Go to Preference -> Modes and there is width settings for every mode. Set all values to 0 (zero). It could help.

Truth is, I have to add bandwith settings separated for other radio. This settings is common for both radios.

73 Petr, OK2CQR

OZ1PIF
Re: Strange one, possibly not a problem with CQRlog, but worked

Well, that did the trick, now the FT-847 TRX-control works as expected - Tnx.

I still don't understand why it worked in 0.9.x though! I dont recall having fiddled with these settings earlier.

73 de OZ1PIF, Peter