Error message
5
Ever since LOTW came back online when I do a “sync LOTW QSL’s” I get this message “WAZ candidate doesn't specify a CQ zone”. This is for a contact I made with 702WX. I've checked my log entry, and it shows a CQ zone. I tried to check the LOTW entry but I couldn't find where it shows the CQ zone. Is this a LOTW issue or a DX lab issue? Julio, W4HY
Розпочато
Julio Peralta
@
·
Останніх
@
|
DXKeeper 17.6.7 - Failure To Load Log
2
After upgrading to DXKeeper 17.6.7 I received a message upon opening that the log required significant updating. Seconds after it attempts to do its maintenance I get a second message stating "Unable to upgrade database; the specified log cannot be opened" followed by a third message "unable to open log database: C:\DXlab\DXKeeper\Databases\N2KI.mdb". So what has gone awry in the update to version 17.6.7? I cannot access my log with this version. -- Anthony - N2KI
Розпочато
Anthony - N2KI
@
·
Останніх
@
|
M2 serial connection from DCView
I want to use DXView to control my M2 Rotator. I have an M2 control box and am using a serial cable from the control box to the computer using a Zircom serial to USB converter . I have setup the controls in DXView. I have tried to use a serial port in SmartSDR Cat. DXView shows that I can do a SP, but when I click on it, nothing happens.
Розпочато
Stewart Lewis
@
|
I'm using DXkeeper with GridTracker. Having issue with Propagation SHOWING INTERNET.
I'm using DXkeeper with GridTracker. Having issue with Propagation.in DXkeeper. When I go to log propagation is showing INTERNET which does not allow me to upload to LOTW. Is there a fix in Gridtracker for this? Is anyone else having this issue? TIA Ron N6XT
Розпочато
Ron Rosson
@
|
Commander multi-rig setup
Hello folks. Looking for some help with two ICOM rigs on the same desktop computer using multi-radio in DXLab Commander. First, I am old, so memory not greatest. In the past I had this working fine with an IC-7610 and 7300. Removed 7300 for field day and gremlins entered. IC-7610 works fine, and COM ports are 3 (A) and 4 (B). When I plug in the 7300 USB cable Windows 11 does not recognize the USB device. If I remember correctly, 7300 tries to install on COM 3? I live in fear of killing my 7610 ports and losing comms with Commander as this is my primary rig. I did use VSPE with the 7300 to obtain my second COM port for that radio. Commander multi-rig setup is fine, but of course no useable COM port for 7300. Appreciate any help. Harold WB4CW
Розпочато
Hank - WB4CW
@
|
Lost my IOTA Report data…
9
Hi, I’m new to the group, and relatively new to DXLab. I suspect you’re used to new members signing up with a problem, so here’s mine: I recently activated a couple nearby IOTAs and imported all the QSOs from N1MM. Then I went through a disjointed process of trying to get them uploaded to LOTW. I finally got the “myQTHs” sorted out, new TQSLs set up and got the IOTA contacts properly loaded to LOTW. But I ended up, after all my machinations, with a couple glitches. First, in addition to my two new IOTA “myQSL” configurations, I ended up with two identical home QTH configurations, and I can’t delete either of them. My nearly 10,000 home QTH QSOs appear to be assigned to both of the identical “myQTH” entries. Most concerning, my IOTA Progress Reports no longer work. They now show no (as in zero, nada, zilch) entries. The DXCC reports appear to work just fine. I verified that all my individual log entries show the IOTA correctly in the Award box, that the “myQSLs” are set correctly, and I’ve tried changing a range of my home QTH containing IOTA contacts to each of the two identical “myQTH” configurations. No matter what I do, my IOTA progress report shows I’ve never even worked one. Thanks for any help, and 73, Steve K4WA
Розпочато
Steve
@
·
Останніх
@
|
LOTW QSO/QSL synch
5
I previously questioned why synching my 87,275 QSOs with LOTW QSL synch took so long. That is now relatively quick having done it the first time. But yesterday afternoon I wrongly pressed the LOTW QSO sync button instead of the QSL sync one, which I had not done before, and similarly it went into an endless process of updating the records to mark them as LOTW sent Y. I had to leave my computer on when I retired for the night and it completed the process in 7 hours. I am not sure how your program accesses the database but in this day and age this sounds very slow, a mere 3.5 QSOs updated per second. During this time I could not use Keeper for anything else and could not abort the process other than hard closing the program. I don't recall it taking so long doing the same processes with eQSL and ClubLog. Is LOTW any different in this aspect? This is not a criticism but it does seem to be a bit of a limitation of the program. If I had been using it live on the air, maybe in a contest or a dxpedition, it would have stopped play totally. But thanks for the excellent logger. 73 Dave G3YMC
Розпочато
Dave Sergeant G3YMC
@
·
Останніх
@
|
FT450 - Frequency update error
10
Hi, Commander/rig frequency is sometimes different. In case of using FT8 rig split operation, the transmit/receive frequencies will shortly be erroneous and it does not recover without manual intervention. Rig split is not usable at all. Also, quite often my station starts reporting FT8 spots on wrong band. Attached images showing the situation - rig on VFO A, 24.923 MHz, but Commander indicated earlier 21.074 MHz. Likely the first freq change command failed. CAT interrogation is constantly reporting the correct frequency to Commander but it does not react. This behavior started about a year ago. The problem may have been activated due to some other issue causing random errors in CAT, however the software should recover from random communication errors. 73's Petri OG5N
Розпочато
Petri OG5N
@
·
Останніх
@
|
Progress report
2
Hello Dave, there must be something i don't know, maybe by my stupidity. I have 557 QSOs with WAB references. I have a UDI in my advance filters, captured < WAB >. Filtering via UDI shows 557 QSOs. This morning i tried to make a progress report WAB. Surprise: using the <WAB> button shows only one single QSO in the report. The button <user> togheter with the selected UDI, shows 409 different WAB references. The button WABP works fine (10). IOTA works fine (356). DXCC works fine (263). Sota works fine (679). Etc. What am i missing? From wich source the progress report <WAB> is generated? Thanks again. Eddy ON5JK
Розпочато
eddy on5jk
@
·
Останніх
@
|
VUCC LOTW DXKeeper issue
2
I have two QSO's with VA7LM who was operating as a rover. Each QSO was from a location that counted for two grid squares. I imported the ADIF log from Greencube Terminal into DXKeeper and then uploaded the QSO's to LOTW. The four grids are credited in LOTW. When I view my VUCC progress report with my log filter to contain only QSO's with propagation "SAT" the "LOTW Cfm" column shows the status as "missing" for the four grids. The Callsign, dates, and other QSO columns correctly reflect the contact information. I have tried to sync LOTW and DXKeeper without any change in the issue. Any advise as to how I might get the issue resolved would be appreciated. Thanks <<John N4QWF
Розпочато
n4qwf .
@
·
Останніх
@
|
Successful FT8 QSO, but Upload to QRZ fails with can't upload message
9
I don't know how to disable the upload to QRZ. On the QSL Config of DXKEEPER's QSL Tab, then QRZ Tab of that screen nothing is in the 2 fields and nothing is checked. Thanks.
Розпочато
James Nail WA2MBP
@
·
Останніх
@
|
Providing Each User with a Private Special Callsign Database
The article "Providing Each User with a Private Special Callsign Database" in https://www.dxlabsuite.com/dxlabwiki/PrivateSpecialCallsignDatabases provides step-by-step instructions for providing each user who is (non-simultaneously) sharing DXLab applications on the same PC with a private Special Callsign Database, for example if they each wished to specify NoPrune tags for the different callsigns they are pursuing, or disagree as to which callsigns are inaccurate spotters. While constructing this article, I made a few improvements to https://www.dxlabsuite.com/spotcollector/Help/ConfigurationSpecialCallsigns.htm After upgrading to SpotCollector 9.7.8, you can update your local copy of this Help file by directing your browser to save this web page to SpotCollector's Help folder, overwriting the existing ConfigurationSpecialCallsigns.htm 73, Dave, AA6YQ This release - correctly handles a callsign reported by WSJT-X that contains back-to-back slashes - correctly discards DX Summit spots, and improves the usability of the Pre-filtering window's treatment of Skimmer spots (tnx to Joe W4TV) * renames the "Discard spots from spotting station callsigns ending in -#" option to "Discard Skimmer spots" * renames the "Discard spots from spotting station callsigns ending in -@" option to "Discard DX Summit" spots * enabling the "Pre-filter Skimmer spots only" option disables the "Discard Skimmer spots" option * enabling the "Discard Skimmer spots" option disables the "Pre-filter Skimmer spots only" option - provides a new "Special Callsign Database" panel on the Configuration window's "Special Callsigns" tab that displays the name of the current Special Callsign Database, and provides the option to switch between a Special Callsign Database referenced by all users of the computer hosting SpotCollector and a Special Callsign Database whose name incorporates the Operator Callsign Specified on the Configuration window's General tab; before changing the Special Callsign Database, SpotCollector directs DXView to terminate (tnx to Tom DF7TV) - extends Leaderboard support to optionally includes bands and modes, as well as band-modes (tnx to Brian N8WRL, Joe W4TV, Jon KM8V, and Rich N5ZC) * the Spot Database Entry's Need field contains the letter J if its callsign is "needed for Leaderboard" on the Entry's band * the Spot Database Entry's Need field contains the letter K if its callsign is "needed for Leaderboard" in the Entry's mode - provides a new Leaderboard panel on the Configuration window's "Special Callsigns" tab that (tnx to Brian N8WRL, Joe W4TV, Jon KM8V, and Rich N5ZC) * enables specification of a Leaderboard start date, before which logged QSOs with Leaderboard callsigns are ignored * provides checkboxes that enable pursuit of Leaderboard bands, modes, and band-modes - updates the "Realtime Award Tracking" displayed by the pop-up menu's "Display Award Progress" command window to reflect Leaderboard band, mode, and band-mode award progress - updates the CollectingWWV.htm, ConfigurationDatabase.htm, ConfigurationSpecialCallsigns.htm, Prefiltering.htm, and SpotDatabase.htm documentation files
Розпочато
Dave AA6YQ
@
|
SpotCollector 9.7.8 is available
This release - correctly handles a callsign reported by WSJT-X that contains back-to-back slashes - correctly discards DX Summit spots, and improves the usability of the Pre-filtering window's treatment of Skimmer spots (tnx to Joe W4TV) * renames the "Discard spots from spotting station callsigns ending in -#" option to "Discard Skimmer spots" * renames the "Discard spots from spotting station callsigns ending in -@" option to "Discard DX Summit" spots * enabling the "Pre-filter Skimmer spots only" option disables the "Discard Skimmer spots" option * enabling the "Discard Skimmer spots" option disables the "Pre-filter Skimmer spots only" option - provides a new "Special Callsign Database" panel on the Configuration window's "Special Callsigns" tab that displays the name of the current Special Callsign Database, and provides the option to switch between a Special Callsign Database referenced by all users of the computer hosting SpotCollector and a Special Callsign Database whose name incorporates the Operator Callsign Specified on the Configuration window's General tab; before changing the Special Callsign Database, SpotCollector directs DXView to terminate (tnx to Tom DF7TV) - extends Leaderboard support to optionally includes bands and modes, as well as band-modes (tnx to Brian N8WRL, Joe W4TV, Jon KM8V, and Rich N5ZC) * the Spot Database Entry's Need field contains the letter J if its callsign is "needed for Leaderboard" on the Entry's band * the Spot Database Entry's Need field contains the letter K if its callsign is "needed for Leaderboard" in the Entry's mode - provides a new Leaderboard panel on the Configuration window's "Special Callsigns" tab that (tnx to Brian N8WRL, Joe W4TV, Jon KM8V, and Rich N5ZC) * enables specification of a Leaderboard start date, before which logged QSOs with Leaderboard callsigns are ignored * provides checkboxes that enable pursuit of Leaderboard bands, modes, and band-modes - updates the "Realtime Award Tracking" displayed by the pop-up menu's "Display Award Progress" command window to reflect Leaderboard band, mode, and band-mode award progress - updates the CollectingWWV.htm, ConfigurationDatabase.htm, ConfigurationSpecialCallsigns.htm, Prefiltering.htm, and SpotDatabase.htm documentation files Notes: 1. Update your firewall and anti-malware applications to consider the new versions of SpotCollector.exe to be "safe" a. 0/14 Jotti scanners detected malware in SpotCollector.exe or SC_WSJTX.exe b. 0/74 VirusTotal scanners detected malware in SpotCollector.exe; 1/74 VirusTotal scanners detected malware in SC_WSJTX.exe 2. If this upgrade doesn't work correctly, see the "After an Upgrade" section of http://www.dxlabsuite.com/dxlabwiki/ApplicationStoppedWorking 3. After upgrading, to revert to the previous version of SpotCollector, see http://www.dxlabsuite.com/dxlabwiki/RevertApplicationVersion SpotCollector 9.7.8 is available via the DXLab Launcher, and via http://www.dxlabsuite.com/download.htm 73, Dave, AA6YQ
Розпочато
Dave AA6YQ
@
|
updated eQSL AG, LoTW, and USAP databases are available ...
... via the Databases tab of DXView's Configuration window. Terminate DXKeeper and SpotCollector before directing DXView to update these databases. Thanks to Tom KQ5S for the USAP database update! An RDA database update is not available because the list of RDA callsigns cannot be downloaded. 73, Dave, AA6YQ
Розпочато
Dave AA6YQ
@
|
Change in display for new grids
15
Dave, Until about a month ago LoTW would report new grids received. Now I just get the QSOs from LoTW with no mention of some of them being new grids. I have not received any new country LoTWs lately so I don't know if this condition is affecting both. Curiously I do get the questions, since most of them are rovers, about "do you want to overwrite the( zone, county or other parameter) for these QSOs. When I run the RAT those new grids have been appropriately added. I use the "Confirmed" filter. I see the same with new EU and SA grids i.e. the grids are recognized in the RAT but not mentioned in the LoTW downloaded report. That report says " No new confirmations of anything needed and previously unconfirmed" I am running DXK 17.6.7. I sync LoTW QSOs and LoTW QSLs every few days. Thanks, Sid K3SX
Розпочато
Sid- K3SX FM19dk MD
@
·
Останніх
@
|
An explanation of the outages caused by Crowd Strike provided by Hiawatha Bray in the the Boston Globe
10
It took just a few errant keystrokes by someone at the Texas cybersecurity firm CrowdStrike to cause a digital meltdown that has afflicted millions of computers around the world. Understanding what happened requires a crash course in cybersecurity. Our home computers rely on security software that runs on individual machines and is regularly updated to detect the latest threats. But that’s not good enough for businesses and government agencies. They’re under relentless attack by professional criminals and foreign intelligence services that keep finding new ways to break in and steal data. CrowdStrike fights back with an artificial intelligence system called Falcon, which monitors its customers’ computers around the clock, according to information from the company’s website and regulatory filings. By training the AI on the data that flow in and out of these devices, Falcon can quickly recognize new attacks and shut them down before they do too much damage. The system requires installing Falcon software on every digital device on the network — desktop computers, laptops, servers, even smartphones. On Thursday night, CrowdStrike issued an update to this software for computers running Microsoft’s Windows operating system. For reasons yet unknown, the update contained a bug so severe that once it was installed, the Windows computer could no longer boot up properly and began displaying the notorious “blue screen of death.” Happily, the bad code wasn’t fed to devices running non-Windows operating systems, including computers that use the Linux or Apple Mac operating systems. Smartphones weren’t affected, either. But Windows machines dominate in business and government offices. And millions of them crashed, creating a global fiasco. And now comes the hard part, according to Craig Shue, head of the computer science department at Worcester Polytechnic Institute. The affected computers will have to be repaired by knowledgeable technicians, who will have to boot the computers in “safe mode,” then delete and replace the defective Falcon software. Rinse and repeat for every PC on the premises. “That’s what’s going to slow down the recovery on this,” said Shue. “If you’ve got a thousand computers, that’s going to take somebody a while to do.” It’s tempting to blame Microsoft for this. Shouldn’t the company have designed Windows so it couldn’t be ravaged by a mere software update? Not in this case, said Shue, because cybersecurity software is so different from ordinary software apps. Most apps can’t access the basic functions of the computer. Instead, they rely on the operating system. So when you print a document using Microsoft Word, the software asks the operating system to forward the file to the printer. This way, a bug in Word would only affect Word; the rest of the machine is unaffected. Shue said that unlike other apps, cybersecurity programs like Falcon are almost as powerful as the operating system. They must be, to prevent the computer from running toxic software or carrying out illicit commands. And when something goes wrong — as we’ve seen — a bug in a cybersecurity program can debilitate the computer or make it totally inoperable. “It can basically do anything on the computer,” said Shue. “It can delete any file. It can stop any program from running. And that’s really important when you’re fighting a virus.” If Microsoft denied this level of access to outside cybersecurity vendors, the company could face an antitrust lawsuit for seeking to force companies to use only Microsoft’s own cybersecurity services, Shue added. Microsoft did not immediately respond to a request for comment. Stuart Madnick, professor of information technology at the MIT Sloan School of Management, expects the hits to keep on coming because so many companies depend on certain IT vendors, such as CrowdStrike. As a result, a bug in the vendors’ software, whether accidental or deliberate, can affect companies all over the world. That’s why cybercriminals try to hack the software sold by these vendors, as a way to gain illicit access to dozens or hundreds
Розпочато
Dave AA6YQ
@
·
Останніх
@
|
Error Displaying Database Logs
8
On July 10th I accidently tried to Sync Club Log database instead of eQSL Log database. Now when I open up DXLab I get the following errors: 1. Operation is not supported for this type of object. 2. System error &H80004005 (-2147467259). Unspecified error. My 111787 logged qso's will not display even though I know they are till there, The Log QSO's screen displays most all fields, and some are flashing RED and Blue. I can send screen shots and also the DXLab\DXKeeper "ErrorLog.Txt" file Any help, suggestions or how to fix would be appreciated.
Розпочато
Jerry, NX0I
@
·
Останніх
@
|
Thumb drive?
10
I plan to go roving next week, and I've borrowed a laptop from our local radio club. This laptop already has WSJT-X and (I think) DXLabs on it, set up for the club call sign. Could I install DXLabs and WSJT-X on a thumb drive, set them up for MY call sign, and run them from there without confusing the whole setup? Thanks, Earl / KD5XB DM84 e e Sent with Proton Mail secure email.
Розпочато
Earl Needham
@
·
Останніх
@
|
IC-7300 rig control and other apps.
16
I've have been trying to setup an IC-7300 with DX Commander and VarAC as a digital mode. The CI-V remote from the radio is connected to a tuner and that works as expected. The USB serial port from the IC-7300 (COM2 on the PC) is connected to DX Commander as the primary CAT port. I have no where to connect VarAC's rig control for CAT/PTT. Do I need a serial port splitter (com0com etc.) to priovide DX Commander and VarAC their own separate port connected to COM2? Trying to keep it as simple as possible. How have you done this? Thanks Danny K5CG
Розпочато
Danny K5CG
@
·
Останніх
@
|
Multirig Station Setup
2
What is the best way to setup a multirig station using DXLab? I have four different transceivers that I want to setup mostly for simultaneous operation on FT8 (or other digital mode) on different bands, but I want to be able to quickly change to SSB or CW operation on any of those rigs, with all QSOs smoothly logged to DXKeeper. According to the DXLab instructions, one rig can be setup in WSJT-X for rig control via DX Lab Suite Commander, but the other WSJT-X instances must be interfaced directly to the relevant transceiver. When all of the rigs are running a WSJT-X mode, each logged QSO will be automatically conveyed to DXKeeper. However, if I switch one of the directly-interfaced rigs to SSB or CW, those QSOs will not be logged without manual intervention...and even then the incorrect frequency and mode are picked up from the "main" rig that is interfaced via DX Lab Suite Commander. N1MM+ addresses this situation (two rigs at a time, both employing the DX Lab Suite Commander software interface), but WSJT-X must be terminated in order to make a SSB QSO and properly log the frequency and mode. This is a bit awkward but workable. To deal with more than two transceivers a separate instance of N1MM+ on a second computer can be employed. Is there a way to achieve station management in the manner described using DXLab? Is the most reasonable way to achieve what I want to run multiple instances of N1MM+ (on multiple networked computers) in a non-contest mode with automatic logging information send from N1MM+ to DXKeeper? I have not yet tried that interface, so I could use some help on that approach. Since DXLab is not intended as a contest logger, my guess is that the N1MM+ solution is the only option. Any additional guidance will be welcomed. 73, Walt, AJ6T
Розпочато
Walter Miller, AJ6T
@
·
Останніх
@
|
1 - 20 з 47555