Re: Rig Connection Problem
Do you think this is relevant?
?
-- 73's de Dave, G8FXM
|
Re: Rig Connection Problem
I'm using WSJT-X v2.5.4 d28164
Thanks for offering to compile a special version just for me.
I don't want to put you too too much trouble or create a lot of work just for one user!
sounds like I'm in the minority as an old FT2000D user ;-)
?
--
73's de Dave, G8FXM
|
Re: Rig Connection Problem
I will try to prepare a special version for you with a early version of hamlib. Maybe the installation package will be available tomorrow, but you reported that you have an issue with previous version of QLog that contains early version of the Hamlib.
To be exact, currently QLog for Windows use hamlib is 4.5.5. QLog 0.29 and older used hamlib 4.4. It seems that current WSJTX for windows (2.6.1) includes hamlib 4.5.4. WSJTX 2.3.0 is really old and contains 4.1.
what version of WSJTX are you using?
|
Re: Rig Connection Problem
I'm not sure if it's relevant but on Googling the issue it seems there are many issues for other Yaesu radios with the current version of Hamlib. It seems a roll back to version 2.3.0 is a temporary fix for affected users. Is there a way I can roll back? the version of Hamlib installed with QLog or can you tell me which earlier version of QLog was compiled with Hamlib 2.3.0? I'd be happy to install a earlier version until Hamlib sort it out.
See?
--
73's de Dave, G8FXM
|
Re: Rig Connection Problem
OK, many thanks anyway. It's very strange as Minos, Log4OM, WSJT, JTDX, OmniRig and FLrig (FLRig has some issues with VFOB, but still connects and works with VFOA) all connect to my FT2000 without any problems,-. It's only QLog I have an issue with?
--
73's de Dave, G8FXM
|
Re: Rig Connection Problem
I'm very sorry, but I can't help you. I ran tests and couldn't simulate the same error. Maybe someone who has more experience with this type of rig and the hamlib library.
I don't know what version of the Hamlib library your WSJTX uses, but I looked in the source code of WSJT and QLog use the same commands to control the rigs.
Regards
Ladislav
|
Re: Rig Connection Problem
On Mon, Dec 4, 2023 at 02:12 PM, ok1mlg wrote:
Hi Ladislav,
I'm using Windows 11 here via COM Port 3 connected to my FT2000D via Prolific PL2303GT serial cable to a 9 pin RS232 connector at the rig. The port is configured for 38400, 8 bits, 1 start and 1 stop. No flow control and no parity. This set up works well with WSJT and JTDX applications on the same PC. For some reason I cant get QLog to connect to my Radio, I have installed 0.30 but still no joy. The Hamlib error I get is: Rig Error: Get Frequency Error Error Detail: newcat_get_freq: unsupported vfo=currVFO Let me know if you need any further details? ? -- 73'd de Dave, G8FXM
|
Re: Rig Connection Problem
Hi Dave.
it is quite difficult to solve these things without detail. Can you please tell me how your rig is connected? It is mainly about how you have configured the rig in QLog, WSJTX... keep in mind that if you have a Serial port rig setting in QLog, then it is not possible to run WSJTX on the same port as well. But I don't know if that's your case. I would need to know more than just an error message from Hamlib.
It is also import to know that QLog works differently than CQRLog. CQRLog rung own RigCTLd, what is server for sharing rig over the network. QLog does not provide this and it is up to the operator to build a shared rig for multiple applications (Log and WSJTX, JTDX etc).
My last note is about the difference between 0.29 and 0.30 for windows. Release 0.30 contains the latest available version of Hamlib.
Regards
OK1MLG, Ladislav
|
I've been having difficulty in connecting my FT2000D to QLog version 0.29 using Windows 11. I just installed version 0.30 and now I get the following connection errors:
Rig Error: Get Frequency Error
Error Detail: newcat_get_freq: unsupported vfo=currVFO
I'm using the same com settings as I do for WSJT and JTDX both of which work fine.
Can anyone point me in the right direction please?
-- 73's de Dave, G8FXM
|
Problem in connecting to Rig
Hi, I've just installed the windows version of QLog version 0.29.2 coming from CQRLog (om Linux) and I'm having difficulty in connecting to my FT2000D.
My Laptop connects ok to my other Ham Radio programs, QLog seems to be connecting without reporting any errors, but the Rig window does not show the radios frequency.
All the usual com settings check out
Is there something I'm missing?
73's de Dai, G8FXM
|
Let me inform you that a new QLog release v0.30.0 is finished. Changelog: - [NEW] - QSL Images are saved to the database - [NEW] - Added AppStream Metainfo File (PR #262 thanks AsciiWolf) - [NEW] - Added (WPX) prefix (issue #263) - [NEW] - Added WPX Award statistics - [NEW] - Added support for external translation files - [CHANGED] - Removed QSOID from Export dialog column setting (issue #258) - Fixed Date editor does not support NULL value in Logbook Direct Editor (issue #256) - Fixed duplicate entry in Windows Add or Remove - only Window platform (issue #260) - Fixed RST fields revert to 59 after changing them (issue #261) - Fixed Cannot change TQSL Path in Settings - flatpak (issue #271) Only for Windows users:
This procedure applies only to users on the Windows platform and describes how to remove QLog duplicate entries from Windows Add or Remove Uninstall dialog (issue #260)- Select any entry of QLog and press the remove button in the Add or Remove dialog. Your data (logs, QSL cards) will not be deleted by this uninstall - they remain in your home directory
- Use regedit to remove all entries in HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{GUID} that contain the key DisplayName with value QLog - remove the entire GUID record.
- Install the new version of QLog
Changelog: WIKI Changelog:
|
Let me inform you that a new QLog release v0.29.2 is finished. Changelog: - Fixed QLog is already running error popup on MacOS (issue #257 thanks rjesson)
Note: Optional update. Only MacOS users are affected.
Changelog:
|
Let me inform you that a new QLog release v0.29.1 is finished.
Changelog:
- Fixed QSL cards tooltip are not displayed under qt6.5 (issue #248)
- Fixed Distance unit is not displayed in QSO Info under Windows (issue #250)
- Fixed Editing STATION_CALLSIGN can cause unwanted change in QSO Detail (issue #251)
- Fixed QSO Detail Operator Name contains an incorrect value (issue #252)
- Fixed Calls with VE, VA are coding as Amsterdam & St Paul Islands instead of Canada (issue #253)
- Fixed LoTW QSL import reports unmatched QSOs sometime (issue #254)
Changelog:
|
Re: Zobrazení vlastní zna?ky v LOGu?
Just briefly in English. The question is about which field shows the logging station callsign
Pokud má? QLog v ?e?tině, tak polí?ko se jmenuje "Zna?ka logující stanice" (in english: Logging Station Callsign). Pro rychl? v?běr je mo?né si definovat U?ivatelsk? filtr (Logbook → QSO Filters) na toto pole. Tak?e je poté mo?né rychle vybrat daná spojení pro vybranou logující zna?ku p?es tento U?ivatelsk? filtr (User Filter).
73
Lada
|
Zobrazení vlastní zna?ky v LOGu?
Hledám ale nemohu najít. Jedu hodně portable, malo z domova, portable z ruznych zemi, chtel bych pri prochazeni logbooku videt svoji znacku pod kterou jsem dane QSO provadel, ale nemohu to najit v nastaveni zobrazovanych sloupcu. Mozna spatne hledam ... dekuji.
|
Let me inform you that a new QLog release v0.29 is finished.
Changelog:
- [NEW] - Added user-defined layout for New QSO Detail widget
- [NEW] - Main window State and Geometry can be saved to layout profile
- [NEW] - Awards - Added WAS
- [NEW] - Awards - WAZ/ITU/WAC show all possible values
- [NEW] - Distance unit (km/miles) is controlled by OS Locale
- [CHANGED] - Removed SAT Tab - field can be added via Layout Editor
- Improved Import QSO performance
- Fixed QLog crashes if POTA, SOTA or WWFF contain incorrect values (issue #245)
- Fixed QSOs are not uploaded to QRZ and HRDLog if fields contain HTML delimiter strings (issue #247)
Changelog:
Wiki:
|
|
|
oh well, you're talking about the 12/24 format. UTC is timezone. It doesn't define a time format.
In general QLog time/date format is controlled by OS Settings. It means that the QLog formats (time/date) are the same as your OS uses. If you don't like it, you can change it in the same way as changing the Language ().
In your case, for example, like this (even if it is a fact that you will have the data format in YYYY/MM/DD).
for Linux:
LC_TIME=en_ZA.UTF-8 ./qlog
for Windows:
SET LC_TIME=en_ZA.UTF-8
qlog.exe
|
Ok thanks, I will look at it again this morning as it is showing ?AM and PM and not 24hr UTC. UTC is what I want otherwise the logging will not match when I submit them.?
|
Hi Richard,
If "correct time" means time in your local time, then you are right. Unfortunately, QLog currently does not display the time in local time, but in UTC time (all time values are in UTC). Everything about hamradio is given in UTC time, so I decided that it would be good to implement this in QLog as well.
From user's point of view, switching between UTC/local time is not a very good idea, because you would have to provide time zone data for all times and that would make the entire GUI confusing.
Regards
Ladislav - OK1MLG
|
Dave, G8FXM
VE6PCO - Richard