CQRLOG - open discusion

Developing Hamlib Rig for SDRAngel

Submitted by N5BRG on

I have been wrting a Rig module for Hamlib to support SDRAngel. I have most of the code copleted and now testing. Using the RIGCTL application I have the following parts working:

f, F Frequency
m, M mode
v, V VFO
t, T PTT

When I run CQRLOG I see the frequency and the mode are following the radio and staying current.
When I try to change the frequency by selecting a different option in the drop down no change is made to the radio and the frequency in CQRLOG remains the like it was. I also see no different activity in Debug=1.

Forums: 

DX Cluster - sending Command to telnet cluster when connected - problem using comma separaton on CC-cluster

Submitted by LB2EG on

In cqrlog DXcluster preferences I have a list of excluded entities that shall be sent to dx cluster when connected.

Using VE7CC.net cluster that uses CC cluster software, entities listed must be comma separated like:

SET/FILTER DXCTY/REJECT SM,OH,OZ,DL,SP,PA,ON,F,EA,EA6,EA8,EA9,I,IT9,IS,9A,LZ,HA,HB,LX,G,GW,GM,GI,GD,GU,EI,LY,CT,TA,4X,OK,OM,9A,ER,YU,YO,E7,S5,OE,K,KP4,VE,ES,UA,UA9,UN,UR,5B,YL,EU,4O,SV,SV9,SV5,T7,PY,Z3

Forums: 

Transmit hangs in WSJTX remote longer than it should

Submitted by n8mus on

Setup: Ten Tec Omni 7 serial cable from computer to radio. Running hamlib rig ctrl d followed the setup in Saku's video and it is working great. EXCEPT in the transmit period when the radio stops sending about 2 seconds before the end of the period the radio stays keyed. It stays keyed 3 seconds into the receive period and then releases. It still is able to decode the other station as the data does not start coming through until about that point in the next period anyway. It just seems odd the radio is hanging in transmit that long.

Forums: 

WARNING: TDBGrid.Destroy with LCLRefCount> 0.

Submitted by ik0dwj on

Hi!

I already thought cqrlog 2.5.2 was finally the best version of all time.
When today, I accidentally right-clicked on the empty QSO list, in the main "New QSO" window,
the following warning appears:
"Press Ok for ignore and risk data corruption. Press Abort to kill the program".
This only happens if the "Show recent QSO records for the last XX days" option is not
selected in Preferences -> New QSO.
If instead I select this option the problem is solved.

While debugging I isolated this line which I think is interesting:

Forums: 

WSJT-X Font Size when called from remote vs run stand alone.

Submitted by ve6pco on

Good morning.
I know that this is not a CQRLOG problem but was hoping someone might have found a fix for this.
I am running Fedora 33, fully updated, and when i run WSJT-X (2.3.0)without cqrlog, the layout and font sizes look fine, but when i run it from remote of cqrlog, font on the bottom are squished together, the boxes that i can adjust my TX, and RX at. I do have screen shots but not sure how to attach here
Running latest CQRLOG 2.5.2(001)
73
Richard - VE6PCO

Forums: 

Previous QSO field

Submitted by G4LNA on

Since the last two updates I've notice that the previous QSO field has been getting smaller with each update. Originally I could see three QSO's then went down to two and the latest one one previous QSO.
This is a screenshot

https://i.postimg.cc/VL2FfqD2/Screenshot-at-2021-02-14-15-17-42.png

I think the field is called qQSOBefore.

Is there a way I can increase the size of the field? So I can at least three previous QSO's.

Forums: 

Pages

Subscribe to RSS - CQRLOG - open discusion