Date   

Re: Ham Cap

Paul Evans W4/VP9KF
 

Ah, I think I see the problem! By any chance are you still running Win7? I moved to Win10 a short time ago and now it doesn't work. On top of that the web site does NOT say that it works under Win10. Wait to see what Alex says, but I think that's going to be the issue. If you have Win7, download my file or use G7SSE's data and it shud work OK.


Re: Ham Cap

Paul Evans W4/VP9KF
 

I'm sooooooooooo sri, you're right. When I foresaw this problem I extended the file and tested it. It worked fine. HOWEVER, there appears to be a hard coded problem in the code which won't work with a system clock past 2019-12-31! Hmmmm, that's why he stopped the data there. Mine starts stuck back in 2005 and won't progress past Dec 2019 too. So, we'll have to wait for the author to try to catch up with it.


Re: Ham Cap

John Munton - G7SSE
 

Dave

I got it to work by copying & pasting the following into that file:

Jan 2020=4.4
Feb 2020=4.8
Mar 2020=5.1
Apr 2020=5.5
May 2020=5.9
Jun 2020=6.4
Jul 2020=6.8
Aug 2020=7.3
Sep 2020=7.8
Oct 2020=8.3
Nov 2020=8.9
Dec 2020=9.5
Jan 2021=10.1
Feb 2021=10.8
Mar 2021=11.5
Apr 2021=12.2
May 2021=12.9
Jun 2021=13.7
Jul 2021=14.5
Aug 2021=15.4
Sep 2021=16.3
Oct 2021=17.2
Nov 2021=18.2
Dec 2021=19.2
Jan 2022=20.3
Feb 2022=21.4
Mar 2022=22.5
Apr 2022=23.7
May 2022=24.9
Jun 2022=26.1
Jul 2022=27.4
Aug 2022=28.7
Sep 2022=30
Oct 2022=31.4
Nov 2022=32.8
Dec 2022=34.3
Jan 2023=35.7
Feb 2023=37.3
Mar 2023=38.8
Apr 2023=40.4
May 2023=42
Jun 2023=43.6
Jul 2023=45.2
Aug 2023=46.9
Sep 2023=48.5
Oct 2023=50.2
Nov 2023=51.9
Dec 2023=53.6 

73, John - G7SSE

------ Original Message ------
From: "ik2agx" <davelav@...>
Sent: 09/01/2020 15:01:44
Subject: Re: [hamlogger] Ham Cap

Hi Villi,

file name is SSN.dat and is located in the Ham Cap folder,
but as I have just posted, despite editing the file with new data
it doens't go past Dec. 2019.

Also I notice that, at least in my case, when I open it, month is fixed to Jan. 2005
and is not updated by system clock.

73, Dave


Re: Ham Cap

ik2agx
 


Re: Ham Cap

ik2agx
 

Hi Villi,

file name is SSN.dat and is located in the Ham Cap folder,
but as I have just posted, despite editing the file with new data
it doens't go past Dec. 2019.

Also I notice that, at least in my case, when I open it, month is fixed to Jan. 2005
and is not updated by system clock.

73, Dave


Re: Ham Cap

ik2agx
 

Hummmm,

here it doesn't go past Dec. 2019 in any case.

73, Dave - IK2AGX


Re: Ham Cap

Vilhjalmur Sigurjonsson
 

FB DR Dave,

Do you know the name and location of the original file?

73 Villi
TF3VS

 

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of ik2agx
Sent: fimmtudagur, 9. janúar 2020 14:41
To: hamlogger@groups.io
Subject: Re: [hamlogger] Ham Cap

 

Hi Paul and Mike,

excerpt from Ham Cap readme.txt file:


3.3. Notes on Prediction Parameters

  Ham CAP has a built-in database of historical and predicted SSN values.
The SSN field is populated from this database whnever you change
the Year and Month field. Of course, you can override this value
with you own one. VOACAP requires a smoothed SSN number that is available from
many sources. Click on the button to the left of the SSN field to download SSN
off the web.

Downloaded file gives you the data to amend original file

73, Dave - IK2AGX


Re: Ham Cap

ik2agx
 

Hi Paul and Mike,

excerpt from Ham Cap readme.txt file:


3.3. Notes on Prediction Parameters

  Ham CAP has a built-in database of historical and predicted SSN values.
The SSN field is populated from this database whnever you change
the Year and Month field. Of course, you can override this value
with you own one. VOACAP requires a smoothed SSN number that is available from
many sources. Click on the button to the left of the SSN field to download SSN
off the web.

Downloaded file gives you the data to amend original file

73, Dave - IK2AGX


Re: Ham Cap

Michael Harris
 

Hi Paul,

Interesting, will have a look at your SSN file. I slave my Ham Cap to IonoProbe so have never used update manually. However, it won't accept IonoProbe input at present.

I have emailed Alex and he will hopefully sort it out.

Regards,

Mike VP8NO

On 09/01/2020 09:43, Paul Evans W4/VP9KF wrote:
I spotted this 2-3 years ago. The SSN file ends on that date. I made an extended file which can be swapped in. The values were guesses, so use the auto update feature to correct it.
File can be found at: http://w4.vp9kf.com/SSN.dat swap it into your directory where HamCAP is located and it'll run.


Re: Ham Cap

Paul Evans W4/VP9KF
 

I spotted this 2-3 years ago. The SSN file ends on that date. I made an extended file which can be swapped in. The values were guesses, so use the auto update feature to correct it.

File can be found at: http://w4.vp9kf.com/SSN.dat swap it into your directory where HamCAP is located and it'll run.


Ham Cap

Michael Harris
 

Users may have noticed that Ham Cap doesn't progress beyond Dec 2019

Regards,

Mike VP8NO


Re: IC7610 is not changing modes

Chuck Kraly K0XM
 

Sorry Bob, New radio, and  I am moving the shack. So will play more this week in the evenings.


On Wed, Jan 8, 2020 at 5:06 PM Bob <k4cy@...> wrote:
I see this:



This doesn't look Kosher, Haram, or Halal to me (maybe its Vegan, I wouldn't know). It looks like two messages 1) FE FE 98 E0 26 00 FD and 2) FE FE E0 98 26 00 00 00 02 FD all joined together. As you haven't mention if this ever worked, if its a new radio, or what your configuration parameters are, I can only make a SWAG - Try cranking the poll interval down to something like 200ms as an experiment. SeventyThree(s).
On January 8, 2020 at 4:56 PM Chuck Kraly K0XM <ckraly@...> wrote:

When I click on a spot from the cluster windows, the radio moves in frequency but the mode does not change.Here is the output of the debug window:
Poll main mode : FE FE 98 E0 26 00 FD 
Mode poll Rx : FE FE 98 E0 26 00 FD FE FE E0 98 26 00 00 00 02 FD 
Poll sub mode : FE FE 98 E0 26 01 FD 
Any ideas? This is either direct on the com port which is USB, or via Omni-rig
Chuck K0XM

 


Re: IC7610 is not changing modes

Bob
 

I see this:



This doesn't look Kosher, Haram, or Halal to me (maybe its Vegan, I wouldn't know). It looks like two messages 1) FE FE 98 E0 26 00 FD and 2) FE FE E0 98 26 00 00 00 02 FD all joined together. As you haven't mention if this ever worked, if its a new radio, or what your configuration parameters are, I can only make a SWAG - Try cranking the poll interval down to something like 200ms as an experiment. SeventyThree(s).

On January 8, 2020 at 4:56 PM Chuck Kraly K0XM <ckraly@...> wrote:

When I click on a spot from the cluster windows, the radio moves in frequency but the mode does not change.Here is the output of the debug window:
Poll main mode : FE FE 98 E0 26 00 FD 
Mode poll Rx : FE FE 98 E0 26 00 FD FE FE E0 98 26 00 00 00 02 FD 
Poll sub mode : FE FE 98 E0 26 01 FD 
Any ideas? This is either direct on the com port which is USB, or via Omni-rig
Chuck K0XM

 


Re: IC7610 is not changing modes

Bob
 

I see lotsa poll messages to the radio, but not a single reply from the radio. Reminds me of conversations with my XYL - One way conversations. SeventyThree(s).

On January 8, 2020 at 4:56 PM Chuck Kraly K0XM <ckraly@...> wrote:

When I click on a spot from the cluster windows, the radio moves in frequency but the mode does not change.Here is the output of the debug window:
Poll main mode : FE FE 98 E0 26 00 FD 
Mode poll Rx : FE FE 98 E0 26 00 FD FE FE E0 98 26 00 00 00 02 FD 
Poll sub mode : FE FE 98 E0 26 01 FD 
Any ideas? This is either direct on the com port which is USB, or via Omni-rig
Chuck K0XM

 


Re: IC7610 is not changing modes

Dave Colliau
 

There is a couple ways to do this. I had mine set in the RCP and setup dx spot macros but it should change modes from the band plan if everything is set up properly. And there are commands in the radio setup . I dont have a 7610 any longer but I do I think have the macros stuck away. I will look . Make sure your bands and modes are set up in logger 32 first.
Dave N8DC

On January 8, 2020 at 4:56 PM Chuck Kraly K0XM <ckraly@...> wrote:

When I click on a spot from the cluster windows, the radio moves in frequency but the mode does not change.Here is the output of the debug window:
Poll main mode : FE FE 98 E0 26 00 FD 
Mode poll Rx : FE FE 98 E0 26 00 FD FE FE E0 98 26 00 00 00 02 FD 
Poll sub mode : FE FE 98 E0 26 01 FD 
Any ideas? This is either direct on the com port which is USB, or via Omni-rig
Chuck K0XM

 


IC7610 is not changing modes

Chuck Kraly K0XM
 

When I click on a spot from the cluster windows, the radio moves in frequency but the mode does not change.Here is the output of the debug window:
Poll main mode : FE FE 98 E0 26 00 FD 
Mode poll Rx : FE FE 98 E0 26 00 FD FE FE E0 98 26 00 00 00 02 FD 
Poll sub mode : FE FE 98 E0 26 01 FD 
Any ideas? This is either direct on the com port which is USB, or via Omni-rig
Chuck K0XM


IC7610 is not changing modes

Chuck Kraly K0XM
 

When I click on a spot from the cluster windows, the radio moves in frequency but the mode does not change.Here is the output of the debug window:
Poll main mode : FE FE 98 E0 26 00 FD 
Mode poll Rx : FE FE 98 E0 26 00 FD FE FE E0 98 26 00 00 00 02 FD 
Poll sub mode : FE FE 98 E0 26 01 FD 
Any ideas? This is either direct on the com port which is USB, or via Omni-rig
Chuck K0XM


Re: cherry picking

Matthias Bellmann
 

Thanks Bob, I did so and it works now. BUT  i had the same setting bevore, an it did not work. After closing logger and updating to 405 it works. Already qsoed stations dissapeared from udp bandmap. Thanks for your help.

But i am sure, the next question certainly will arise :-))

73 Matthias



Am 08.01.2020 um 16:13 schrieb Bob:

No mystery. You must have these two menu options checked. SeventyThree(s).


On January 8, 2020 at 9:59 AM Matthias Bellmann <Dk4wd@...> wrote:

WSJT - settings -reporting:

udp server 127.0.0.1
Port number 2237
accept udp requests, notify on accepted and accepted udp restores window all three marked.

FA session b4 only accept udp requests has been marked.
Both above mentioned had the same effect, Dupe calls are logged.

all qso's are logged correctly. I can make calls by clicking on a call shown in the band map. Suppose UDP is running correctly.
Hidden mystery ? :-)
73

Am 08.01.2020 um 15:34 schrieb Bob:
Are you logging FT4/FT8 QSOs in real time by UDP messages? If not, there is no way for Logger32 to know if a station has been worked before. SeventyThree(s).
On January 8, 2020 at 7:47 AM Matthias Bellmann <Dk4wd@...> wrote:

Sorry, I marked the wax you proposed, but nevertheless dupes occur. There must be something else?


Am 08.01.2020 um 09:57 schrieb ja1nlx:

It does not call worked B4 this Band/Mode and does not display them in UDP BandMap

with this configuration.


73



On 2020/01/08 17:45, Matthias Bellmann wrote:
When using cherry picking in bandmap i always contact stations already
qso-ed b4, even when  it happend just few minutes ago.

I clicked in menue config-show/block callsigns worked before any
possible combination, but dupes still happen.

In menue config-cherry picking options i dont find a applicable option.

Another fault of mine?





--
73 de aki
JA1NLX


 


 


Re: cherry picking

Bob
 

No mystery. You must have these two menu options checked. SeventyThree(s).


On January 8, 2020 at 9:59 AM Matthias Bellmann <Dk4wd@...> wrote:

WSJT - settings -reporting:

udp server 127.0.0.1
Port number 2237
accept udp requests, notify on accepted and accepted udp restores window all three marked.

FA session b4 only accept udp requests has been marked.
Both above mentioned had the same effect, Dupe calls are logged.

all qso's are logged correctly. I can make calls by clicking on a call shown in the band map. Suppose UDP is running correctly.
Hidden mystery ? :-)
73

Am 08.01.2020 um 15:34 schrieb Bob:
Are you logging FT4/FT8 QSOs in real time by UDP messages? If not, there is no way for Logger32 to know if a station has been worked before. SeventyThree(s).
On January 8, 2020 at 7:47 AM Matthias Bellmann <Dk4wd@...> wrote:

Sorry, I marked the wax you proposed, but nevertheless dupes occur. There must be something else?


Am 08.01.2020 um 09:57 schrieb ja1nlx:

It does not call worked B4 this Band/Mode and does not display them in UDP BandMap

with this configuration.


73



On 2020/01/08 17:45, Matthias Bellmann wrote:
When using cherry picking in bandmap i always contact stations already
qso-ed b4, even when  it happend just few minutes ago.

I clicked in menue config-show/block callsigns worked before any
possible combination, but dupes still happen.

In menue config-cherry picking options i dont find a applicable option.

Another fault of mine?





--
73 de aki
JA1NLX


 


 


Re: cherry picking

Matthias Bellmann
 

WSJT - settings -reporting:

udp server 127.0.0.1
Port number 2237
accept udp requests, notify on accepted and accepted udp restores window all three marked.

FA session b4 only accept udp requests has been marked.
Both above mentioned had the same effect, Dupe calls are logged.

all qso's are logged correctly. I can make calls by clicking on a call shown in the band map. Suppose UDP is running correctly.
Hidden mystery ? :-)
73

Am 08.01.2020 um 15:34 schrieb Bob:

Are you logging FT4/FT8 QSOs in real time by UDP messages? If not, there is no way for Logger32 to know if a station has been worked before. SeventyThree(s).
On January 8, 2020 at 7:47 AM Matthias Bellmann <Dk4wd@...> wrote:

Sorry, I marked the wax you proposed, but nevertheless dupes occur. There must be something else?


Am 08.01.2020 um 09:57 schrieb ja1nlx:

It does not call worked B4 this Band/Mode and does not display them in UDP BandMap

with this configuration.


73



On 2020/01/08 17:45, Matthias Bellmann wrote:
When using cherry picking in bandmap i always contact stations already
qso-ed b4, even when  it happend just few minutes ago.

I clicked in menue config-show/block callsigns worked before any
possible combination, but dupes still happen.

In menue config-cherry picking options i dont find a applicable option.

Another fault of mine?





--
73 de aki
JA1NLX


 

4421 - 4440 of 82922