Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
- DXLab
- Messages
Search
|
DXL with wsjtx, SSDR and slicemaster
This is the setup I am trying to use now.? All software is current.
dxl is using flexsig and slicemaster is using whatever it uses to connect to ssdr.?? Seems to set WSJTX to HRD for the rig on port 7832.
?
it all seems to be working ok after some trial and error with manuals.? but if i click a call in wsjtx the call info does not populate dxk or its capture window.? so i dont get any info until the qso is over when wsjtx does send the entry to dxk.?
?
Also when the wsjtx spots go to spot collector, If i click on one? it changes slice A to the spot freq even though i was on slice B.? So it causes an interlock issue trying to TX on the same freq for both slices.
?
Thanks!!!
--
?
73,
Greg - AB7R
?
Flex 8600
PGXL & TGXL
AG |
|
Re: Query Special Callsign database
+ AA6YQ comments below
Just built a new Win11 box and installed a fresh copy of DXLab. Successfully imported my QSO database from DXLab on the old Win10 box. Fresh app talks to the rig and logs QSOs FB. I have populated the Special Callsigns database in SpotCollector with previously used Club member info. I can see that SpecialCallsigns.mdb has been created in SpotCollector's Database folder. I have done a full shutdown and restart of the app. But in DXView | Config | General | Options panel, the 'Query Special Callsign database' option remains 'greyed out'. So I guess there is a step I am missing? + Did you follow the steps in ? + So that I can see what's going on, please do the following: 1. on the General tab of DXView's Configuration window, check the "Log debugging info" box 2. terminate DXView 3. start DXView 4. on the General tab of DXView's Configuration window, uncheck the "Log debugging info" box 5. attach the errorlog.txt file from your DXView folder to an email message, and send the message to me via aa6yq (at) ambersoft.com 73, Dave, AA6YQ |
|
Query Special Callsign database
Just built a new Win11 box and installed a fresh copy of DXLab. ?Successfully imported my QSO database from DXLab on the old Win10 box. ?Fresh app talks to the rig and logs QSOs FB.
?
I have populated the Special Callsigns database in SpotCollector with previously used Club member info. I can see that SpecialCallsigns.mdb has been created in SpotCollector's Database folder. I have done a full shutdown and restart of the app.
?
But in DXView | Config | General | Options panel, the 'Query Special Callsign database' option remains 'greyed out'. ?So I guess there is a step I am missing?
?
73 Dave
|
|
Re: Problem printing QSL labels with no gaps between labels and no margin gaps
Try the following:
toggle quoted message
Show quoted text
Row 1 offset = 3 mm Row height = 37 mm Column 1 offset = 4 mm Column 2 offset = 72 mm Column 3 offset = 144 mm Label width = 64 mm You may need to tweak the column 2 and column 3 offset values slightly. Work with "Print preview (QSL Labels)" a couple of times and print on plain A4 paper until you are comfortable with the results. 73, ... Joe, W4TV On 2025-05-14 4:20 AM, jan via groups.io wrote:
Hi, |
|
Re: Problem printing QSL labels with no gaps between labels and no margin gaps
+ AA6YQ comments below
I am trying to print QSL labels on TOWER W100 labels on A4 sheets that are nominally 297 X 210 mm.? The labels are 37 X 70 mm in 3 columns and 8 rows.? The column offsets should be 0, 70, 140 as the label width is 70 with no gaps between.? My printer is a Canon TS3400 and it imposes a left margin of 3.387 mm and a top margin of 2.963 mm.? DXKeeper consequently reduces the printable area to 288.961 X 203.2 mm and determines the allowed column offset limits based on the reduced area and will not print if the offset exceeds the limit e.g. for column 3 the limit is 133 and it should be 140.? If I select "Ignore printer imposed margins", it sets them to 0, but it retains the reduced printable area and offset limits determined before.? Is there a workaround or remedy for this?+ DXKeeper is not reducing the printable area to 288.961 X 203.2 mm - that printable area is what your printer driver is reporting. Three columns of 70m wide labels require a 210mm wide printable area; your printer's 203.2mm width is insufficient. ?
+ Try selecting the next larger paper size and see what your printer driver reports as a printable area. ? ? ? ?73, ? ? ? ? ? ? Dave, AA6YQ |
|
Problem printing QSL labels with no gaps between labels and no margin gaps
Hi,
?
I am trying to print QSL labels on TOWER W100 labels on A4 sheets that are nominally 297 X 210 mm.? The labels are 37 X 70 mm in 3 columns and 8 rows.? The column offsets should be 0, 70, 140 as the label width is 70 with no gaps between.? My printer is a Canon TS3400 and it imposes a left margin of 3.387 mm and a top margin of 2.963 mm.? DXKeeper consequently reduces the printable area to 288.961 X 203.2 mm and determines the allowed column offset limits based on the reduced area and will not print if the offset exceeds the limit e.g. for column 3 the limit is 133 and it should be 140.? If I select "Ignore printer imposed margins", it sets them to 0, but it retains the reduced printable area and offset limits determined before.? Is there a workaround or remedy for this?
?
Thank you.
?
Jan, ZS1IS |
|
Re: Flex 8400 should be here tomorrow - DXLab documentation
Thanks Dave - new radio=lots of questions Norman On Mon, May 12, 2025 at 7:10?PM Dave AA6YQ via <aa6yq=[email protected]> wrote:
|
|
Re: Flex 8400 should be here tomorrow - DXLab documentation
+ AA6YQ comments below
+ The appropriate article in "Getting Started with DXLab" is here: ?
? ? ?73,? ?
?
? ? ? ? ? Dave, AA6YQ |
|
Flex 8400 should be here tomorrow - DXLab documentation
Hi Group,
?
I finally bit the bullet and my new Flex 8400 should be here tomorrow.
?
Is the documentation in up-to-date for this radio?
?
It is going to be a big change from my Kenwood TS-570 and trying to get ready to get on the air with DXLab.
?
Thanks!
Norman
KC9NVN |
|
Re: Has anyone with an Elecraft K4 recently tried transmitting and receiving RTTY...
+ AA6YQ comments below
+ Thanks, Jeff! Did WinWarbler display RTTY text decoded by your K4 (as distinguished from RTTY text decoded by the MMTTY and 2Tone engines)? ? ? ? ?Dave |
|
Re: Has anyone with an Elecraft K4 recently tried transmitting and receiving RTTY...
Dave,
?
I am an infrequent user of WinWarbler, but I do have it set up.? I fired it up this morning, and it appears to function as it
should with My K4, both TX and RX.? Not a lot of activity here at the moment, but it seems ok.?
?
Win 10 Pro....
?
Jeff - N8CC
? |
|
Has anyone with an Elecraft K4 recently tried transmitting and receiving RTTY...
...by setting the Model selector to "Xcvr Ctrl App" on the "External Modem" tab of WinWarbler's Configuration window? When so configured, WinWarbler transmits RTTY by directing Commander to send the outgoing characters to the K4 via an appropriate CAT command, and displays RTTY characters decoded by the K4 and received by way of Commander.
This scheme is supported with the K3 and worked with the K4 demonstrator that Elecraft loaned me, but it appears that new CAT commands may now be required. ?
? ? ? 73, ? ? ? ? ? ? ?Dave, AA6YQ ? ? ? ? |
|
Re: Spot Collector
Try working through the items here:
toggle quoted message
Show quoted text
<> Most common - improperly configured filter: Control-Click on the X beside the filter text box to remove all filtering Highly likely - your computer clock or timezone is off: Set Windows for your local timezone and time 73, ... Joe, W4TV On 2025-05-09 11:10 AM, k0au via groups.io wrote:
Sorry to add another non-specific "Spots don't display" question. But spots stopped displaying. |
|
Spot Collector
Sorry to add another non-specific "Spots don't display" question. But spots stopped displaying.
?
Windows 11, Nvidia RTX3060i with Studio Driver 576.02, Spot Collector 9.8.3
?
Only spot source is N6WS and I see spots rolling in on the status window.? If it's a clue, when I compact the spots database I see spots flash on the spot collector window briefly and then go away.
?
? |
|
Re: Spot Collector
What do you mean "single space"? If you mean the row height in Spot
toggle quoted message
Show quoted text
Database display is too large, got to Config -> Spot Database Display and click the "Set Row Height" button in the Font panel along the left side of that screen. 73, ... Joe, W4TV On 2025-05-09 8:10 AM, Ron S. wrote:
Can't seem to get it to single space.? Don't know what I did, but no success. |
|
Re: JTAlert failure after system crash - is there a workaround to log to DXKeeper?
+ AA6YQ comments below
SpotCollector will track your 6-meter grids.+ DXLab provides real-time award tracking for the DXCC, IOTA, Marathon, VUCC, WAS, WAZ, and WPX awards on the bands and modes that you've specified for each of them. Active stations with whom a QSO would advance your progress towards these awards are highlighted in SpotCollector with font color, with optional audio and email alerts. When directly interoperating with WSJT-X, stations with whom a QSO would advance your progress towards these awards are highlighted with font color in the WSJT-X Band Activity panel, as illustrated here: + Logging a QSO in WSJT-X automatically conveys that QSO to DXKeeper. Logging a QSO in DXKeeper automatically updates your award progress to reflect the impact of that QSO - whether the QSO was logged from WSJT-X, WinWarbler, MixW, MMSSTV, MultiPSK, or DXKeeper itself. ? ? ? 73, ? ? ? ? ? ? Dave, AA6YQ |
to navigate to use esc to dismiss