开云体育

Hi i’am starting to run Qlog with WSJT-X but it’s not work. I have only a problem: when i Launch wsjt with F7 key, i recejve an error occored about missing a .ini file, the configurations it’s ok, i run a ChgWSet properly as the guide, but i do not set any .ini file configurations. We can help me? Thanks a lot. Carmelo - IT9GHW. Inviato da Outlook per iOS

John, what is different about the version for the blind. I downloaded that one and installed it; but all I can see about it is that it's a beta version or something, that expires this summer. Thanks. 73, de WA9RYF

Hi everyone, I'm Carmelo, IT9GHW. I heard about QLog from GRIN (Gruppo Radioamatori Italiani Non Vedenti), an Italian blind ham radio community. The project seems very interesting, especially for activities with WSJT-X. I have a question: how can I properly connect my radio to work with the software, for example, for DX Cluster? I’ve tested several configurations, including BBLogger, Log4OM V2, ACLog, and now QLog. To run these experiments, I bought a Win4ICOM Suite license, which emulates four different COM ports to work with my ICOM IC-7300 and IC-705. The strange thing is that QLog has a radio setup menu, but when I select my IC-7300, I can't enter other settings like baud rate, CI-V address, etc. Has anyone else had the same issue? Before writing this email, I searched the user manual and even asked ChatGPT to summarize it and analyze the documentation for radio configuration details, but I couldn’t find a solution. Thanks in advance for your help! 73, Carmelo - IT9GHW?.

Spots Users, The following text describes the second of the Spots issues. This issue has a number of aspects. This item is also in regard to Spots version 3.0. There are several factors that affect the audible announcement of a country by Spots. 1. The Spots all.txt processing start time and the country (or grid) announcement start time. Both of those times are user settable. As Rich has pointed out a number of times, a Spots user is normally interested in only fresh data. I am thinking that the default settings for both the Spots start time and announcement start times should be small, like maybe 0.5 minutes (30 seconds.) 2. Spots reconfiguration Whenever Spots is reconfigured, e.g., a change in band, it restarts. As currently implemented, whenever Spots restarts it begins in the same location in the all.txt file as it did at the beginning of the session. Perhaps instead it should be restarting from the current end of the all.txt file and stepping back only by the amount of time indicated as the Spots start time? 3. QLog updating When Spots is first invoked, the QLog data located in c:\qlog\data4spots is read and the lists of worked countries and grids on the various bands are refreshed. However, those files are not refreshed when Spots is restarted due to a band change. That can readily be changed. 4. Spots is currently mostly band agnostic. Although the current band of each new all.txt record could easily be computed by Spots from the frequency field, Spots does not currently do anything with that field other than to display it if the user requests it in the presentation. As currently implemented, each country has an associated set of attributes of which one is "worked". The "worked" attribute is a single flag indicating whether the country has been worked. There is an underlying assumption that the Spots band folder has been set to correspond to the same band as the current radio setting. When a user selects a band, e.g., "6 meter", Spots clears each countries "worked" flag, reads the list of worked countries (if any) from the file located in the associated band folder, and then checks the "worked" flag of any country indicated in the file. I am thinking that this implementation should be changed. As currently implemented, if a user changes the band on the radio but neglects to make the corresponding change to the Spots band setting, there is no warning and Spots will be announcing countries required on a different band and omitting some countries required on the current band. A possible fix could be for Spots to automatically switch bands based upon the frequency of the all.txt records. In that case, the "worked" flag variable for each country could instead be an array of flags, with each member associated with one of the common bands. In that case we might want to introduce a user settable auto-detect option.

Spots Users, During last weeks Qlog beta testers Zoom meeting a couple of issues were raised with the Spots application and which I intend to raise during this Saturday's Zoom meeting. Because the two issues involve a number of factors that will affect the Spots software design, this missive describes those two issues together with the relevant factors. I will describe the first item in this email and then I will post another regarding the second matter. The following refers to Spots version 3.0. Regarding the first item, it was pointed out that the "copy call sign to clipboard" feature sometimes fails to copy the correct call sign. Upon reflection and some discussion, I propose to re-implement that feature such that, when the "c" key is pressed a window will popup showing a tree view, akin to that which is displayed by file explorer. However, in this case, in response to the "c" key, Spots will search its buffer and make a list of countries from which traffic has originated. Spots will sort and de-dupe the list and make the list the top level of the tree structure. So, analogous to the file explorer, which shows the top level list of folders, the tree will show the list of countries for which a user can navigate by typing the first letter in the country name. As with the file explorer tree, when one arrows right, the list of call signs belonging to the country will appear. That list will appear in reverse chronological order so that the first one displayed will be the most current. At this point, Rich says that each call sign should be followed on the line by the other field values from the record, including the time slot. A question here is, what other information would you want? Upon selecting the call sign via <enter> key, the call sign will be copied to the clipboard and the window will close.

Hi folks, The month snuck up on me so this is a bit shorter notice than usual. It’s time again for the April edition of our users zoom call. Please join and bring your question and successes. Zoom information is below. John Farina is inviting you to a scheduled Zoom meeting. Topic: QLog users April 2025 users call Time: Apr 5, 2025 13:00 Eastern Time (US and Canada) Join Zoom Meeting https://us02web.zoom.us/j/83921199466?pwd=TpMZTLNKJkGa6ENs5w86n4G5WOhou7.1 Meeting ID: 839 2119 9466 Passcode: 988928 --- One tap mobile +16465588656,,83921199466#,,,,*988928# US (New York) +16469313860,,83921199466#,,,,*988928# US --- Dial by your location ? +1 646 558 8656 US (New York) ? +1 646 931 3860 US ? +1 309 205 3325 US ? +1 312 626 6799 US (Chicago) ? +1 301 715 8592 US (Washington DC) ? +1 305 224 1968 US ? +1 564 217 2000 US ? +1 669 444 9171 US ? +1 669 900 9128 US (San Jose) ? +1 689 278 1000 US ? +1 719 359 4580 US ? +1 253 205 0468 US ? +1 253 215 8782 US (Tacoma) ? +1 346 248 7799 US (Houston) ? +1 360 209 5623 US ? +1 386 347 5053 US ? +1 507 473 4847 US Meeting ID: 839 2119 9466 Passcode: 988928 Find your local number: https://us02web.zoom.us/u/kxHfP0DTl

Hello group, To me, this situation is a bit strange: I had become rather disallusioned by the digital modes and decided to remove all the software. All I left was the interface cable. I thought it was all gone. Now, after some time, regaining an interest, I downloaded and installed the "blind" version of WSJT-X; which seems to be just a beta that will expire in a few months. When I launched the program, it took over the radio, just as it had done in the past when I was using it. Now I just need to reinstall the QLog software and all its extra pieces. I think I'll have it running again. Wish me luck ... or skill? 73 all de Howard WA9RYF

Hello I am a QLog-newbie and got a few errors while importing my ADIF-logfile. Some of these are QSOs with /MM-calls. How does QLog handle the DXCC of those? How are invalid calls handled in generell (i.e. 1B1AB)? Thanks for your help! regards, Suitbert, DF2PI

Hi to all, i'am Carmelo - IT9GHW. I'am blind and i

Hi Carmelo, IT9GHW, The first first email from you that I read had only two lines. After I approved you on the group, I received your full email with the full text. You said in your email that "QLog has a radio setup menu, but when I select my IC-7300, I can't enter other settings like baud rate, CI-V address, etc." The QLog program for the blind does NOT have such a setup menu for using different radios. It appears that you may not be using a different QLog program, the one created by OK1MLG. His QLog program was released a number of years after the QLog program by Sam Birnbaum, W2JDB. Sam's program is written so blind Hams can use the FT8 and FT4 digital modes. If you downloaded the QLog program that you are using from Github, it is not the one made for blind Hams to use. At Groups.IO, there is another group simply called "QLOG". It was created 4 years after our "QLog Users Group" started. The "QLOG" group is associated with their QLog Amateur radio logbook software which is found at https://github.com/foldynl/qlog , If you do not wish to belong to the QLog Users Group for visually impaired and blind Hams, you can unsubscribe by sending an email to: [email protected] 73, Rich K1HTV

Hi everyone, I just put together a new computer, new to me, in my shack. One thing I'm noticing though is every time I make a contact with wsjtx and qlog, I have to go over to a wsjtx window and enter on OK. I had that once in a while in the past but it's about every time on this one. It's set to auto log, with jaws up I think it said something about having an issue connecting to qrz yet when I hit enter on OK, it loggs to qrz, eqsl, and clulblog just fine. I'm guessing I set something wrong somewhere, it's been a tough couple weeks here so I do a couple settings, leave, come back later or days later, do a couple more, it's very likely I missed something. I didn't mind when it was once in a while but this every time is annoying. I'm running qlog version ending in 87 and wsjtx, the latest version just downloaded when I put this computer in line last week. Does anyone have ideas, or know what I didn't set right? Thanks, Johna

Hi, guys, I just moved everything over to the USB port on my TS-590s and eliminated the need for the DB-9 connector. I'm going to find a VHF rig like an IC9100 and replace my TS-2000 on VHF weak signal to smooth things out. TNX, -- Craig Martin, KY0O

Hi, guys, How do you use Qlog to run RTTY, or is there a better program to use for that mode? TNX, -- Craig Martin, KY0O

I had gotten behind on my Podcast readings and am just now getting caught up. John W2QCY Great job on the Blind Hams Qlog podcast. 73 N5ZSO Ray

Hi folks de w2qcy, Once again we begin a new month and it is time for our users zoom call to exchange questions and answers as well as successes with Qlog and its associated programs. Below is the zoom information. Hope to see many of you there. John Farina is inviting you to a scheduled Zoom meeting. Topic: QLog users March 2025 zoom call. Time: Mar 1, 2025 13:00 Eastern Time (US and Canada) Join Zoom Meeting https://us02web.zoom.us/j/89983437362?pwd=7mORFbLLuufJEogPFeb79feWbN057a.1 Meeting ID: 899 8343 7362 Passcode: 402417 --- One tap mobile +16465588656,,89983437362#,,,,*402417# US (New York) +16469313860,,89983437362#,,,,*402417# US --- Dial by your location ? +1 646 558 8656 US (New York) ? +1 646 931 3860 US ? +1 309 205 3325 US ? +1 312 626 6799 US (Chicago) ? +1 301 715 8592 US (Washington DC) ? +1 305 224 1968 US ? +1 564 217 2000 US ? +1 669 444 9171 US ? +1 669 900 9128 US (San Jose) ? +1 689 278 1000 US ? +1 719 359 4580 US ? +1 253 205 0468 US ? +1 253 215 8782 US (Tacoma) ? +1 346 248 7799 US (Houston) ? +1 360 209 5623 US ? +1 386 347 5053 US ? +1 507 473 4847 US Meeting ID: 899 8343 7362 Passcode: 402417 Find your local number: https://us02web.zoom.us/u/kbzAPX59u

Hi, guys, I got everything update, but on my VHF computer, i get a rig control error. The rig is a Kenwood 2000X and I'm running WSJTX 2.7 for the blind operators. I also looked for the Spots 3.0 manual on the groups.io website, and no joy. Where to I look to change the comm port from comm 5 to comm 3? The configuration says 'comm5' but the settings menu shows comm three. Thank you, -- Craig Martin, KY0O

Hi, all, I have a work-around using spots with NVDA. When using Spots, start it with NVDA running. When the title bar announces the Spots program, do an NVDA key with Q to unload NVDA from memory. Make sure the dash v i option is in your Spots desk top short cut to start Spots with speech, just like you do with QLog and chgw set. You can use the help screen with NVDA running, but not without it. Do a Control-Alt-N to restart NVDA to read help and navigate the menus. The menus will only work with a screen reader, as will help. Either JAWS or NVDA will operate with Spots using this technique, but to unload JAWS from memory, hit JAWS-F4. Use the JAWS startup hot key to restart JAWS. Thank you, -- Craig Martin, KY0O

The following items have been added to the Files area of the [email protected] group. /Spots/spots-3.0-package.exe By: K1HTV Rich Zwirko <k1htv@...> Description: Before installing “Spots-3.0-package.exe”, please read the “Spots Manual” also found in this Spots file folder. Spots is used in conjunction with JAWS and QLog, Spots is a program that runs as a Windows console application, meaning that it uses a command prompt window. Spots can be used by the visually impaired as well as sighted Hams. After installing Spots in the default C:\spots folder, when it is started, it comes up watching decoded data in the WSJT-X ALL.TXT file. With its default settings, each new country decoded will be announced once, then again if encountered after a user set time interval time has been met. Spots can be configured to give verbal alerts when user defined wanted countries, specific callsigns or unworked grids are decoded. The user can select as many or as few of the 11 available fields in decoded lines of data. This data is displayed on one of 3 user selectable screens, the Country or Grid Watch screen, the Alert screen or the Scans screen. Data on these screens can be viewed with the help of JAWS when the Jaws Cursor is turned on. Beam heading and distance to each station is also available using shortcut keys. To use all of the new Spots features, you must be running QLog version 300 or later. The following items have been added to the Files area of the [email protected] group. /Spots/Spots-3.0-manual.docx By: K1HTV Rich Zwirko <k1htv@...> Description: Spots version 3.0 Manual This manual explains how to install, set up and operate the Spots program The following items have been updated in the Files area of the [email protected] group. /Spots/spots-3.0-package.exe By: K1HTV Rich Zwirko <k1htv@...> Description: Before installing “Spots-3.0-package.exe”, please read the “Spots Manual” also found in this Spots file folder. Spots is used in conjunction with JAWS and QLog, Spots is a program that runs as a Windows console application, meaning that it uses a command prompt window. Spots can be used by the visually impaired as well as sighted Hams. After installing Spots in the default C:\spots folder, when it is started, it comes up watching decoded data in the WSJT-X ALL.TXT file. With its default settings, each new country decoded will be announced once, then again if encountered after a user set time interval time has been met. Spots can be configured to give verbal alerts when user defined wanted countries, specific callsigns or unworked grids are decoded. The user can select as many or as few of the 11 available fields in decoded lines of data. This data is displayed on one of 3 user selectable screens, the Country or Grid Watch screen, the Alert screen or the Scans screen. Data on these screens can be viewed with the help of JAWS when the Jaws Cursor is turned on. Beam heading and distance to each station is also available using shortcut keys. To use all of the new Spots features, you must be running QLog version 300 or later.

Hi, folks, When I run QLog and do an auto-reply, the first transmission upon answering a CQ seems to be fine. But if no response comes from the other station, the next try is sent to my computer speakers instead of out the USB port. I'm using Qlog version 387 and WSJT version 2.6. What say you? -- Craig Martin

I'd like to download all the QLog stuff and start over. I can't seem to find the QLog files area on groups. Can someone give me some pointers, please? Thank you. Howard, WA9RYF -- This email has been checked for viruses by AVG antivirus software. www.avg.com