开云体育

Do you think this is relevant? https://github.com/Hamlib/Hamlib/issues/569 -- 73's de Dave, G8FXM

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

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

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

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

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

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.

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

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

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

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] -

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

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

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

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

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

OK, Thank you.

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

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).