Preferences - Bands - Frequencies: Band-Limits & Mode QRGs

14 posts / 0 new
Last post
do2hg
Preferences - Bands - Frequencies: Band-Limits & Mode QRGs

Hi there,
I'm just wondering, what good the mode-limits will do for me, if entered in the frequencies table.
My assumption was, that if no TRX-Connection is present, the mode will be picked as a suggestion from the table, though offering the option to overwrite it.
This is apparently not the case, as the setting ist taken from the Preferences - New QSO defaults.

My current understanding is as follows:
The frequencies table specifies the *starting* frequency for the relevant mode. That would make e.g. the following values for 80m in Germany:

  • Begin (lower band limit): 3.500
  • End (upper band limit): 3.800
  • CW: 3.500
  • RTTY: 3.570
  • SSB: 3.620

So CW would be from 3.500 to 3.570, RTTY from 3.570 to 3.620, and SSB from 3.620 to 3.800 (not accounting form beacons and other digimodes).

If my understanding is correct, the question is, what good does this table to me if filled properly?

Thanks & 73
Stefan (currently operating as OZ/DB4ST)

oh1kh
Preferences - Bands - Frequencies: Band-Limits & Mode QRGs

Hi!
At least when you double click DXCluster spot it sets right mode taken form mode qrg's.
But it is not so clear there either. There the "tmp" holds spot frequency as follows:

if (tmp <= cw) then
mode := 'CW'
else begin
if (tmp >= ssb) then
mode := 'SSB'
else
mode := 'RTTY';

So you see setting RTTY frequency really has no use there as check is done only against CW(upper) and SBB(lower) freq.
If you have no rig connection (rig would be moved to freq and mode set) usage is quite minimal.

Then band limits (not modes) are used in ADIF import https://github.com/ok2cqr/cqrlog/pull/282

--
Saku
OH1KH

do2hg
Hi Saku,

Hi Saku,
so in other words, CQRLOG treats everything between "Begin" and "CW" as CW, everything between "SSB" and "End" as SSB and the bit in between "CW" and "SSB" as RTTY. - OK. So it's rather for my own reference to quickly lookup, if I don't have a bandplan at hand and no internet ...

Seems to me like old code that got lost somewhere in the development process ;-)
73
Stefan (currently OZ/DB4ST)

--
Stefan
DB4ST (ex DO2HG) --- German Ham Radio Station
D-32584 Löhne ----- Locator JO42IE

do2hg
Hi Saku,

Hi Saku,
... me again.
There are 2 different QRG-tables in the preferences!

  • Preferences - Bands - Frequencies and
  • Preferences - TRX Control - Change default frequencies

... and they seem to be comletely unrelated. Moreover, what I'd expect is, that the latter is relevant for the case, that no TRX is connected via CAT ...
Well, interesting what you find, if you take some time to work through all the options ...
73
Stefan.

--
Stefan
DB4ST (ex DO2HG) --- German Ham Radio Station
D-32584 Löhne ----- Locator JO42IE

WG9L
Mode not changing automatically

I recently updated to version 2.4.0 (135) becasue my TRX control was not communicating with the radio. It was related to my old version of hamlib 3.3 and fixed with hamlib 4.

I notice that whenever I double click a selected spot from the DXCluster window, the radio will QSY properly, but the mode will not change. I've reviewed the following items"
"Preferences - Bands - Frequencies" and also "Preferences - TRX Control - Change default frequencies" and all seems correct. Where else might I look to correct this issue?

Rig: FT-1000D

See
https://www.cqrlog.com/node/2510#comment-8543

Thanks,
Bob WG9L

oh1kh
Mode not changing automatically

HI Bob!

You are using my alpha test binary. There are some differences in mode section compared to official version.
Please try to upgrade to official version. It is now available also in my GitHub with alpha versions.

With running newupdate.sh select option #1 to install latest official version.

Does that change modes ok? (it can not change user defined data mode as alpha, only CW,RTTY and SSB work).

--
Saku
OH1KH

WG9L
Hi Saku,

Hi Saku,

I updated to the latest official release using github. BTW, your YouTube video showing each step was wonderful. It walked me through every step (quite easy). Now I'm running version 2.5.1 (001), but still no luck. When I double click a spot in the Band Map window, the rig changes frequency, however the mode still doesn't change from CW to SSB. Has a newer Alpha version corrected this?

oh1kh
rig changes frequency, however the mode still doesn't change

HI!

Go preferences TRXcontrol.
Set poll rate to 5000 to get littöe less lines to debug. You can return it later to value it was before.
Check bottom "Show communication with TRX in console". Then exit from preferences.
Close cqrlog.
open command console and write
cqrlog (enter)

You should now see only commands to rig/response from rig.

Open DXCLuster and click a spot. Do you see correct mode in console as rig command?
This is to check that cqrlog sends correct mode but rig does not change it.

If mode in console command to rig is wrong then check again preferences/bands/frequencies table.

There is no difference between official and alpha in this case.

--
Saku
OH1KH

oh1kh
rig changes frequency, however the mode still doesn't change

HI!

Go preferences TRXcontrol.
Set poll rate to 5000 to get littöe less lines to debug. You can return it later to value it was before.
Check bottom "Show communication with TRX in console". Then exit from preferences.
Close cqrlog.
open command console and write
cqrlog (enter)

You should now see only commands to rig/response from rig.

Open DXCLuster and click a spot. Do you see correct mode there ?
This is to check that cqrlog sends correct mode but rig does not change it.

If mode in console command to rig is wrong then check again preferences/bands/frequencies table.

There is no difference between official and alpha in this case.

--
Saku
OH1KH

WG9L
Hi Saku,

Hi Saku,

With those TRX settings, the console displays the proper vfo-A and frequency, but the mode still doesn't change properly. Maybe I don't understand how to properly edit the table. I have attached a copy of my table, and a console image of the proper CW results, along with the improper SSB results and shot of the log window for the SSB information. Double clicking a DX spot doesn't change the radio mode, or CQRLOG log window mode.

File: 

oh1kh
rig changes frequency, however the mode still doesn't change

HI !

According your frequencies table your 20m band has :
start from 14.000Mhx, end to 14.350Mhz

CW is from "Begin" 14.000 to 14.025Mhz
SSB is from 14.150Mhz to "End" 14.350Mhz

RTTY begins from 14.070Mhz and ends to SSB start 14.150MHz
"Grey area" is from CW end 14.025MHz to RTTY start 14.070MHz

There is a (poor) explanation,because of limited space, at the bottom of form where:

"Begin" - defined start frequency of band
"End" - defined end frequency of band
"f>=" - frequency (f) is bigger or equal
"f<=" - frequency (f) is smaller or equal

So we read this:
CW:(f>= Begin and f<=CW)
as:
CW frequency area is when frequency is bigger or equal than defined band begin frequency and frequency is smaller or equal as definition CW frequency

I admit this whole frequency table is deep from ... and it is hard to understand and set up.

Frequencies should be put in own extended database (at programmers side) and user interface should have clear band begin/end (as it is now), but also for each mode should have own begin/end setups and there should be as many modes user wants to define. Not just CW RTTY and SSB.
This is a bigger job to do, but should be done in sake of easy maintain.

I think your problem is in these settings. In my setup (in my region) 20m band is:
14.000 14.350 14.060 14.060 14.100

What I was looking from rig CAT traffic was that when you double click a DX spot you should see something like:
Sending: F 10105100

Sending: M CW 500

Msg from rig: RPRT 0
RPRT 0

There I did click a spot in 10.105Mhz and cqrlog sends first
"change frequency"= Sending: F 10105100
then it sends
"Change mode"=Sending: M CW 500

Those I was interested in. But it looks like you have to set up the frequencies table right frist. After that you can peek again rig communication if you still do not get right mode. I was using in test rig poll rate 5000 to get slow enough update rate to see all lines.

--
Saku
OH1KH

WG9L
cw vfo-A

cw vfo-A

File: 

WG9L
ssb vfo-A

ssb vfo-A

File: 

WG9L
log window vfo-A

log window vfo-A

File: