Date   

Re: Sync LotW QSL's

Dave AA6YQ
 

AA6YQ comments below
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]
Sent: Thursday, March 22, 2018 3:13 PM
To: dxlab@yahoogroups.com
Subject: [dxlab] Sync LotW QSL's

If there is a QSO that has been uploaded to LOTW but is not in my log in DXKeeper and I do a Ctrl Click on this button will that QSO be added to my DXKeeper log?

No. “Sync LoTW QSOs” updates logged QSOs to reflect their acceptance by LoTW. Were LoTW to respond with a QSO not present in your log, this would be reported as an error
My thinking was that the sync would compare and make the log match adding any QSO's on LOTW to my log that it found missing.

That’s incorrect. LoTW retains only a small amount of information about each QSO, and so is the absolute court of last resort for recovering QSOs missing from your log. My advice is to start by determining why there are QSOs in LoTW that are not in your log; then locate an ADIF file containing these QSOs as originally logged, and import that into DXKeeper (with duplicate checking enabled).
73,

Dave, AA6YQ


Re: SpotCollector and FT8 mode

C. Michael D'Alto
 

I want to thank iain, Dave, and Bill for their help.  I have it sorted out at last.  As usual I was going about it hard way.  I wish I could retain these things in my cranium, but it's like trying to hold onto a handful smoke.  I learn something, I then forget.  Great support here as always.  Thanks again.

73/DX,
Mike, K2CD


Re: Commander 13.3.6

 

I seem to live on a diet of humble pie.  I double-checked my settings and noticed that continuous "Interrogation" was not checked in Commander.  All seems to be working fine now.  I'll continue to watch it, but it looks like the combination of turning off CI-V Transceive (which was supposed to be off in the first place) and turning on Interrogation" did the trick for me.  I've completed two QSOs using WSJT-X with no errors.

73, Greg, KM5GT


Re: SpotCollector and FT8 mode

Bill Eggers, WB2RIS <wb2ris@...>
 

One technique I've used to create SQL filters in SpotCollector and DXKeeper is to make use of the "filter text box" to enter whatever variable piece of information I wish to apply to the filter (call, time, band, etc):

in DXkeeper:

CONTEST_ID like "**"
QSO_Begin > ##

in DXKeeper and SpotCollector:

call like "**"

In your situation you can create an SQL filter like this:
band = ""  and (whatever else you want to filter on)

or even

band = "M" and (whatever else you want to filter on)

The benefit is you don't need to create new SQL filter statements for each band you wish to filter on.

Note that adding wildcards may significantly slow down the results.

Oh yeah, you can also add as part of the SpotCollector SQL query to give you the spots for the past 1/2 hour (or however long you wish, set in SpotCollector Configuration -> Spot Database tab -> Filters section -> Age Filter)

73,
Bill
WB2RIS

On 3/22/2018 12:50 PM, iain macdonnell - N6ML ar@... [dxlab] wrote:
 

On Thu, Mar 22, 2018 at 4:38 AM, k2cd@... [dxlab]
wrote:
>
>
>
> Currently SQLFilters.txt looks like this:
> DX 10
> (Band='10m')
> DX 12
> (Band='12m') etc. etc.
>
> What would be the syntax to add to each band to filter just FT8 spots, yet allow SSB, CW & RTTY? I tried the suggestions above that iain suggested, but probably did it wrong. Once I get a working example for one band, I can figure out how to get the other bands to follow.

You could be able to paste it into any of the SQL Filter slots. Did
you get an error when you tried to use it, or an unexpected result?

73,

~iain / N6ML



Re: Rotor control with Microham SMD in So2r with DXLabs

Joe Subich, W4TV
 

Jeff,

You might touch base with Fred, AB1OC. He dealt with this same issue.

73,

... Joe, W4TV

On 3/22/2018 2:06 AM, Jeff Blaine keepwalking188@ac0c.com [dxlab] wrote:
I've got a pair of Microham Station Master Deluxe boxes setup in So2r
now.  Wondered if anyone out in the DXLab universe was using the same
hardware setup?
The SMD is different from the more common SM in that it treats the
resources on the network as a shared item.  So the one serial port on
each SMD has access to all the station rotors and it automagically
controls the right one based on the band the rig is setting on.  But I'm
unclear what's the best method of setting up the rotor interface between
DXLabs given the rotor to point too has a different serial port number
for each of the two SMD. Probably a simple way and I'm just not wrapping
my head around it correctly.
Prior to this I had port numbers assigned to each rotor based on band
with the older SM box.  But with this SMD setup, you can't point
directly to an individual rotor which means DXView does not work the same.
If you don't have a SMD setup then this explanation will make zero sense
at all.  Appreciate the comments in advance.
73/jeff/ac0c
alpha-charlie-zero-charlie
www.ac0c.com
------------------------------------
Posted by: Jeff Blaine <KeepWalking188@ac0c.com>
------------------------------------
------------------------------------
Yahoo Groups Links


Re: WinWarbler Peak IMD Not Measured

Joe Subich, W4TV
 

I don't know where you get a signal strength indicator. I would never
use the "Quality" indicator for an RST - instead I would base the "T"
portion of the report on the width of the trace and any spurious tones
(hum, harmonics, IMD, etc.) in the waterfall.

73,

... Joe, W4TV

On 3/22/2018 12:00 PM, richard@midco.net [dxlab] wrote:
Hi Joe,
Maybe you can help me on this next question.
To send an accurate RST report, we can use the signal quality and signal strength indicators in WinWarbler. So if the quality is reading 90 and the strength is reading 81, the RST will be 598?
Rich, K0PIR


Sync LotW QSL's

n4qwf .
 

If there is a QSO that has been uploaded to LOTW but is not in my log in DXKeeper and I do a Ctrl Click on this button will that QSO be added to my DXKeeper log? My thinking was that the sync would compare and make the log match adding any QSO's on LOTW to my log that it found missing.


Re: Commander 13.3.6

 

I'm having similar problems with 13.3.6 with an IC-7300.  I followed the advice of disabling CI-V Transceive, but I am still getting rig control failures from WSJT-X v1.9.0-rc2 r8533.  I consistently get the error, "DX Lab Suite Commander rig did not respond to PTT: ON" from WSJT-X and, if I'm not careful, transceiver locks in TX.

Suggestions?

73, Greg, KM5GT


Re: SpotCollector and FT8 mode

iain macdonnell - N6ML
 

On Thu, Mar 22, 2018 at 11:32 AM, iain macdonnell - N6ML <ar@dseven.org> wrote:
On Thu, Mar 22, 2018 at 10:17 AM, k2cd@yahoo.com [dxlab]
<dxlab@yahoogroups.com> wrote:
Well, I really am not sure where to paste it. Somewhere in the line before or after Band='10m' without any punctuation but within the parentheses?
SQL Filters are normally edited by right-clicking on the buttons in
the Filter panel on SpotCollector's main window...
Edit: make that "Control-clicking"


Re: SpotCollector and FT8 mode

iain macdonnell - N6ML
 

On Thu, Mar 22, 2018 at 10:17 AM, k2cd@yahoo.com [dxlab]
<dxlab@yahoogroups.com> wrote:
Well, I really am not sure where to paste it. Somewhere in the line before or after Band='10m' without any punctuation but within the parentheses?
SQL Filters are normally edited by right-clicking on the buttons in
the Filter panel on SpotCollector's main window...

73,

~iain / N6ML


Re: SpotCollector and FT8 mode

C. Michael D'Alto
 

Hi ~iain,

Well, I really am not sure where to paste it.  Somewhere in the line before or after Band='10m' without any punctuation but within the parentheses?



Re: SpotCollector and FT8 mode

iain macdonnell - N6ML
 

On Thu, Mar 22, 2018 at 4:38 AM, k2cd@yahoo.com [dxlab]
<dxlab@yahoogroups.com> wrote:



Currently SQLFilters.txt looks like this:
DX 10
(Band='10m')
DX 12
(Band='12m') etc. etc.

What would be the syntax to add to each band to filter just FT8 spots, yet allow SSB, CW & RTTY? I tried the suggestions above that iain suggested, but probably did it wrong. Once I get a working example for one band, I can figure out how to get the other bands to follow.
You could be able to paste it into any of the SQL Filter slots. Did
you get an error when you tried to use it, or an unexpected result?

73,

~iain / N6ML


Pathfinder & QRZ.com

wb2nvr@...
 

QRZ.com has made some changes to the Call Sign Pages:


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

QRZ is announcing today that the availability of certain features pertaining to the display of user biography pages will be undergoing changes that promote greater security and better uniformity between listings. These changes will affect the way in which customized user biography pages are shown. Most users will not be affected by these changes, which affect only those who have elected to use features provided by the Expert Options and CSS Styles menu and in particular, those who have styled the upper part of the call sign page.


Call sign pages on QRZ are shown using a Tabbed interface that overlays a few different sub-pages of data for each call sign. These tabs include Biography, Detail, Logbook, and possibly Web Contacts. The changes announced today affect only the data shown in the Biography tab, and only if you have made use of certain Expert options.

Call sign pages are typically spread across two distinct parts of the page. There is an upper area, called the Callsign Data Block followed by a tabbed section which holds the Biography, Detail, Logbook and other features. With this new security update, the information shown above or outside the tabbed section will be restricted to QRZ Use Only. This means that users will no longer be able to style, apply colors, background images, or other enhancements to the part of the page that lies outside of the tabbed area. Inside the Biography tab, users will be able to stylize their pages as before, including the use of Expert options and CSS.

These new page layout rules affect ALL users, regardless of their subscription status, including LIFE Members as well as QRZ Staff.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The complete announcement is in the Amateur Radio News section of QRZ.

When viewing some QRZ pages with Pathfinder (like WB2NVR), the biography section appears like it is in a small window, but there is no scroll handle to see the rest of the page.  Other pages, like WA2VQW or A91WMD, appear like they always did.  When viewed using IE or Chrome directly, the WB2NVR page appears the way it always did.  I haven't changed my QRZ.com page since 02/07/2018.  My page used to display correctly in Pathfinder.

I have Script error notifications hidden, using Pathfinder 5.2.2.  Microsoft Edge 41.16299.248.0   Microsoft EdgeHTML 16.16299

If I have to change something on my QRZ.com page, I'd appreciate some advice on what needs to be done.

TNX ES 73,

Bob WB2NVR





Re: SpotCollector and FT8 mode

Dave AA6YQ
 

AA6YQ comments below
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]
Sent: Thursday, March 22, 2018 7:39 AM
To: dxlab@yahoogroups.com
Subject: [dxlab] Re: SpotCollector and FT8 mode



Currently SQLFilters.txt looks like this:
DX 10
(Band='10m')
DX 12
(Band='12m') etc. etc.

What would be the syntax to add to each band to filter just FT8 spots, yet allow SSB, CW & RTTY? I tried the suggestions above that iain suggested, but probably did it wrong. Once I get a working example for one band, I can figure out how to get the other bands to follow.

If you want to see all active 10m stations not using FT8, then use
(Band=’10m’) and (Mode <> ‘FT8’)

The <> operator means "not equals". This expression will hide stations operating in FT8, but will show stations operating in JT9 or Olivia or SSTV or AM.
If you want to see all active 10m stations using SSB, CW, or RTTY, use
(Band='10m') and (Mode in ('SSB','CW','RTTY'))

This expression will hide stations operating in any mode other than SSB, CW, or RTTY.
73,

Dave, AA6YQ


Re: WinWarbler Peak IMD Not Measured

Rich
 

Hi Joe,

Maybe you can help me on this next question.

To send an accurate RST report, we can use the signal quality and signal strength indicators in WinWarbler. So if the quality is reading 90 and the strength is reading 81, the RST will be 589?

Rich, K0PIR


Re: WinWarbler Peak IMD Not Measured

Rich
 

Ahh, that would explain it.

Thank you,

Rich, K0PIR


Re: WinWarbler Peak IMD Not Measured

Joe Subich, W4TV
 

WinWarbler only measures IMD on an idle signal.


73,

... Joe, W4TV

On 3/22/2018 11:11 AM, richard@midco.net [dxlab] wrote:
Operating PSK31 I must be doing something wrong on not have an option checked somewhere, but I cannot seem to get a instant or peak measurement. Only occasionally do I get a peak.
Any help is greatly appreciated.
Rich, K0PIR


Re: WinWarbler Peak IMD Not Measured

Dave AA6YQ
 

AA6YQ comments below
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com]
Sent: Thursday, March 22, 2018 11:11 AM
To: dxlab@yahoogroups.com
Subject: [dxlab] WinWarbler Peak IMD Not Measured

Operating PSK31 I must be doing something wrong on not have an option checked somewhere, but I cannot seem to get a instant or peak measurement. Only occasionally do I get a peak.

IMD readings are only available when your QSO partner is sending idle characters.
73,

Dave, AA6YQ


Re: QRZ page locked up on Pathfinder

Brian Smithson <n8wrl@...>
 

I have been doing web design for many years and I can tell you that getting pages to look and act the same in different browsers is a nightmare. QRZ has a particular challenge in that they're trying to let their customers (us) design pages any way we want and still keep their own content working.

I took a look at   WB6BEE's, VK7CWG4RMV, and in both IE and Chrome and I found something interesting.

QRZ.com seems to segregate custom markup created by their customers within an HTML tag called an IFRAME. Using Chrome and IE's element inspection tools, I can see that the IFRAME on  VK7CW 's page is decorated  with this style:

-ms-overflow-y:hidden

overflow-y is a CSS style that tells the browser to hide any content that would appear within an element that is longer (taller?) than that element is. The -ms- prefix is a Micrsosoft-specific style, meaning the hidden rule is only applied by IE and ignored by the other browsers. IE's element-inspector allows me to turn that style off, and when I do, the page lays out as I would expect - with a vertical scrollbar where I can see the whole content.

G4RMV is different - he has an overflow-y CSS style on the HTML tag within the IFRAME which would have the same affect, sort-of! Apparently IE is paying attention to it while Chrome is not, and it's probably related to something called element-sizing which is too complicated to explain here.

As of 1500z today WB6BEE's page does not have that styling and looks fine in IE11. This morning, it did look wrong but I did not have time for the digging I've been doing.

I checked my bio tab since I've never done anything with it (it is empty) and I see the ms-overflow-y CSS setting on the HTML tag. Obviously I didn't put it there.

I notice that QRZ is using lots of scripting on their page (not at all uncommon) and the IFRAME has an on-body-loaded event that runs a function called resize() that 'does something.' I suspect something in that script is making a determination of the browser and other content analysis and setting these styles.

I've never updated my QRZ bio page - are there settings or customizations you can choose which might affect layout like this?

Since WB6BEE's page looked bad this morning and good right now, there are three possibilities:

1. Don changed something
2. QRZ changed something
3. IE11 has changed.

Note that in none of this did I use PathFinder.

I hope this helps guys!

73!

-Brian n8wrl

On Thu, Mar 22, 2018 at 10:21 AM, haywooddc@... [dxlab] <dxlab@...> wrote:
 

I deleted the Club Log listing from the bottom of my QRZ page and I think it now works


Don
WB6BEE



WinWarbler Peak IMD Not Measured

Rich
 

Operating PSK31 I must be doing something wrong on not have an option checked somewhere, but I cannot seem to get a instant or peak measurement. Only occasionally do I get a peak.

Any help is greatly appreciated.

Rich, K0PIR


31521 - 31540 of 207970