Date   

Re: Field Day Log - feature request for Operator info on main page

ojendres@...
 

Jeff,

 

Our Club runs 4 stations.  The CALLSIGN in the “Call” field is always “W6EK”, our Club’s callsign.  The “Operator” is the FCC required control operator at each station and we type in their callsign in the “Operator” field.  Operator callsigns change frequently, but the callsign in the “Call” field is always “W6EK”.

 

Except, for the GOTA station.  They operate under a different callsign.  In that case, the Callsign and Operator are the same callsign.

 

I hope I didn’t make things too confusing.

 

If you need any further clarification, please feel free to email me at AI6JB at ARRL.net.

 

73

Orion Endres, AI6JB

1201 Wood Oak Court, Roseville, CA 95747-7383

(916) 788-8251 H \\ (916) 534-8251 C

 

What the heck does “73” mean?  73 is morse code short hand for “Best Regards” used by Ham radio operators.  It’s origin goes all the way back to the landline telegraph days.

 

 

 

From: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io> On Behalf Of Jeff Grantham
Sent: Thursday, June 20, 2019 11:44
To: N3FJPSoftwareUsers@groups.io
Subject: Re: [N3FJPSoftwareUsers] Field Day Log - feature request for Operator info on main page

 

So, do you leave the call sign the same  and just put the unlicensed persons initials in?  Sounds like a good way to track how many people work, for instance, a GOTA station. This will be my first Field Day and I want to make sure it is done correctly and easily.

 


From: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io> on behalf of ojendres via Groups.Io <ojendres@...>
Sent: Thursday, June 20, 2019 12:33:08 PM
To: N3FJPSoftwareUsers@groups.io
Subject: Re: [N3FJPSoftwareUsers] Field Day Log - feature request for Operator info on main page

 

Chris,

 

I definitely feel your pain.  But, if Scott adds Operator, he will need to add Initials too.  At our FD, “Operator” designates the control operator.  “Initials” designates the person hitting the PTT.  This way when we have un-licensed folks visit, we can log the control operator and we can track our youth participation, etc …

 

I always love Scott’s very simple interface that is readable in bright light situations.  And, as I mature, this is becoming more important.

 

73

Orion, AI6JB

 

From: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io> On Behalf Of Christiaan Adams
Sent: Thursday, June 20, 2019 10:20
To: N3FJPSoftwareUsers@groups.io
Subject: Re: [N3FJPSoftwareUsers] Field Day Log - feature request for Operator info on main page

 

Hi Scott, thanks so much for the quick reply!  

Yes, I see the Operator menu item.  What I was trying to say is that for us it would be helpful to display the operator info even more prominently, directly on the main page. Maybe it could go at the bottom of the page, with the Band & Mode info boxes (see my mockup image below). Would be nice to have the Operator data just as easy to see & edit, since we change that more often than Band & Mode.  With the Operator boxes in the menu, my experience is that most of our new operators forget to update it. 

Anyway, just a suggestion, of course.  Appreciate your support!  -Chris


Re: WSJT-X & JT Alert & ARRL Field Day Logger

Justin Lentz KF5IVJ
 

Scott has this information on his site


Justin Lentz KF5IVJ
Ellis County Amateur Radio Club President & Program Officer


On Thursday, June 20, 2019, 1:50:08 PM CDT, Hoop K9QJS via Groups.Io <jkhpr01@...> wrote:


I'm having trouble getting JT Alert to log to ARRL Field Day Logger.   I'm reading help file here: http://www.n3fjp.com/help/digitalsetup.html .   Laurie VK3AMA wrote, "JTAlert supports [these contest programs], but you can't just substitute ACLog with FDLog, it will never work. There are WSJT-X, FDLog & JTAlert settings that need to be configured. Setup is not difficult and easily done, but without reading the specific Help Topic on this, I can guarantee your failure."

I'm feeling like I'm in an infinite  recursive loop.   I am looking at the Help Topic, am I not, when I read Laurie's comment? I guess I don't know where the referenced "JT Alert Help File" is?

Hoop
K9QJS


WSJT-X & JT Alert & ARRL Field Day Logger

Hoop K9QJS
 

I'm having trouble getting JT Alert to log to ARRL Field Day Logger.   I'm reading help file here: http://www.n3fjp.com/help/digitalsetup.html .   Laurie VK3AMA wrote, "JTAlert supports [these contest programs], but you can't just substitute ACLog with FDLog, it will never work. There are WSJT-X, FDLog & JTAlert settings that need to be configured. Setup is not difficult and easily done, but without reading the specific Help Topic on this, I can guarantee your failure."

I'm feeling like I'm in an infinite  recursive loop.   I am looking at the Help Topic, am I not, when I read Laurie's comment? I guess I don't know where the referenced "JT Alert Help File" is?

Hoop
K9QJS


Re: Field Day Log - feature request for Operator info on main page

KB5WCK
 

So, do you leave the call sign the same  and just put the unlicensed persons initials in?  Sounds like a good way to track how many people work, for instance, a GOTA station. This will be my first Field Day and I want to make sure it is done correctly and easily.


From: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io> on behalf of ojendres via Groups.Io <ojendres@...>
Sent: Thursday, June 20, 2019 12:33:08 PM
To: N3FJPSoftwareUsers@groups.io
Subject: Re: [N3FJPSoftwareUsers] Field Day Log - feature request for Operator info on main page
 

Chris,

 

I definitely feel your pain.  But, if Scott adds Operator, he will need to add Initials too.  At our FD, “Operator” designates the control operator.  “Initials” designates the person hitting the PTT.  This way when we have un-licensed folks visit, we can log the control operator and we can track our youth participation, etc …

 

I always love Scott’s very simple interface that is readable in bright light situations.  And, as I mature, this is becoming more important.

 

73

Orion, AI6JB

 

From: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io> On Behalf Of Christiaan Adams
Sent: Thursday, June 20, 2019 10:20
To: N3FJPSoftwareUsers@groups.io
Subject: Re: [N3FJPSoftwareUsers] Field Day Log - feature request for Operator info on main page

 

Hi Scott, thanks so much for the quick reply!  

Yes, I see the Operator menu item.  What I was trying to say is that for us it would be helpful to display the operator info even more prominently, directly on the main page. Maybe it could go at the bottom of the page, with the Band & Mode info boxes (see my mockup image below). Would be nice to have the Operator data just as easy to see & edit, since we change that more often than Band & Mode.  With the Operator boxes in the menu, my experience is that most of our new operators forget to update it. 

Anyway, just a suggestion, of course.  Appreciate your support!  -Chris


Re: Field Day Log - feature request for Operator info on main page

Hector Figueroa
 

OH well I stand corrected I already packed away my computer we tested our
networking setup last week!

ALT+O Thanks for the catch Thomas.

Don't forget firewalls, file sharing, and read up on the setups, it is not
hard, but small traps can trip you up . . .

Happy Field Day to all

73 Hector KE6VRL

------ Original Message ------
Received: Thu, 20 Jun 2019 10:45:29 AM PDT
From: "Thomas" <roo@...>
To: N3FJPSoftwareUsers@groups.io
Subject: Re: [N3FJPSoftwareUsers] Field Day Log - feature request for Operator
info on main page

On Thu, Jun 20, 2019 at 12:31 PM Hector Figueroa <hfigueroa@...> wrote:

“Every time you get up from the chair, type CTRL+O”

When you sit down to operate the last operators information is there. If
it is you hit enter and operate, if it is not you, enter your information
and operate.
I second Hector's comment. Alt+O also conveniently shows whether a given
operating position is in use. If you see the operator dialog, then feel
free to sit down and operate...

--
-Thomas AC9BJ
Mount Horeb, WI EN53da


Re: Field Day Log - feature request for Operator info on main page

ojendres@...
 

Chris,

 

I definitely feel your pain.  But, if Scott adds Operator, he will need to add Initials too.  At our FD, “Operator” designates the control operator.  “Initials” designates the person hitting the PTT.  This way when we have un-licensed folks visit, we can log the control operator and we can track our youth participation, etc …

 

I always love Scott’s very simple interface that is readable in bright light situations.  And, as I mature, this is becoming more important.

 

73

Orion, AI6JB

 

From: N3FJPSoftwareUsers@groups.io <N3FJPSoftwareUsers@groups.io> On Behalf Of Christiaan Adams
Sent: Thursday, June 20, 2019 10:20
To: N3FJPSoftwareUsers@groups.io
Subject: Re: [N3FJPSoftwareUsers] Field Day Log - feature request for Operator info on main page

 

Hi Scott, thanks so much for the quick reply!  

Yes, I see the Operator menu item.  What I was trying to say is that for us it would be helpful to display the operator info even more prominently, directly on the main page. Maybe it could go at the bottom of the page, with the Band & Mode info boxes (see my mockup image below). Would be nice to have the Operator data just as easy to see & edit, since we change that more often than Band & Mode.  With the Operator boxes in the menu, my experience is that most of our new operators forget to update it. 

Anyway, just a suggestion, of course.  Appreciate your support!  -Chris


Re: Field Day Log - feature request for Operator info on main page

Thomas
 

On Thu, Jun 20, 2019 at 12:31 PM Hector Figueroa <hfigueroa@...> wrote:
“Every time you get up from the chair, type CTRL+O”

When you sit down to operate the last operators information is there. If it is you hit enter and operate, if it is not you, enter your information and operate.

I second Hector's comment.  Alt+O also conveniently shows whether a given operating position is in use.  If you see the operator dialog, then feel free to sit down and operate...

--
-Thomas AC9BJ
Mount Horeb, WI  EN53da


Re: Field Day Log - feature request for Operator info on main page

Hector Figueroa
 

That would just add clutter to the screen. Perhaps a training approach would be better. 

“Every time you get up from the chair, type CTRL+O”

When you sit down to operate the last operators information is there. If it is you hit enter and operate, if it is not you, enter your information and operate. 

That process works well. Think of it as pausing your operating position. 

Hector Figueroa 

On Jun 20, 2019, at 10:20 AM, Christiaan Adams <csadams@...> wrote:

Hi Scott, thanks so much for the quick reply!  

Yes, I see the Operator menu item.  What I was trying to say is that for us it would be helpful to display the operator info even more prominently, directly on the main page. Maybe it could go at the bottom of the page, with the Band & Mode info boxes (see my mockup image below). Would be nice to have the Operator data just as easy to see & edit, since we change that more often than Band & Mode.  With the Operator boxes in the menu, my experience is that most of our new operators forget to update it. 

Anyway, just a suggestion, of course.  Appreciate your support!  -Chris

<n3fjp_suggestion.png>


Re: Field Day Log - feature request for Operator info on main page

Christiaan Adams
 

Hi Scott, thanks so much for the quick reply!  

Yes, I see the Operator menu item.  What I was trying to say is that for us it would be helpful to display the operator info even more prominently, directly on the main page. Maybe it could go at the bottom of the page, with the Band & Mode info boxes (see my mockup image below). Would be nice to have the Operator data just as easy to see & edit, since we change that more often than Band & Mode.  With the Operator boxes in the menu, my experience is that most of our new operators forget to update it. 

Anyway, just a suggestion, of course.  Appreciate your support!  -Chris


Re: Field Day Log - feature request for Operator info on main page

Scott Davis
 

Hi Chris,

Thanks for your e-mail.  Unlike the rest of my contest software, the Operator change option is not in the sub menu.  It is a top line menu option.  It's just one click to make any changes.  

Additionally, the initials are displayed right in the list be default.

Capture.JPG



Enjoy!

73, Scott
N3FJP

Serving the Amateur Radio community with contesting and general logging software since 1997.

1 Peter 3 vs 15: Always be prepared to give an answer to everyone who asks you to give the reason for the hope that you have. But do this with gentleness and respect...


-----Original Message-----
From: Christiaan Adams <csadams@...>
To: N3FJPSoftwareUsers <N3FJPSoftwareUsers@groups.io>
Sent: Thu, Jun 20, 2019 12:00 pm
Subject: [N3FJPSoftwareUsers] Field Day Log - feature request for Operator info on main page

Hi, I've been using our club's N3FJP Field Day log for several years now and love it.  Finally registered the software (whole package) for myself recently, so I'm new to this forum. Not sure if this is the best way to submit feedback, but I couldn't find any feedback options on the N3FJP website. Let me know if there's a better place for this.  

The FD Log is great, but there's always been one thing I wished for... that it was easier to see & edit the Operator Callsign & Initials. At our club's FD site (usually 3 stations), we switch operators quite frequently... usually once an hour or more. And very rarely do folks remember to update the log to reflect the current operator, resulting in incorrect logs and hours spent correcting them. The Operator fields are hidden behind a menu item.  Since this is the setting we want to edit the most often (after the QSO info), I think it would help a lot if the Operator Callsign & Initials were on the front page and easily editable... maybe down at the bottom with the Band and Mode?  I realize that for most other contests/logs, it might make sense to have the operator info in a menu, since it probably doesn't change often... but for Field Day, at least at our site, we change it a lot. 

Anyone else wish for the Operator info to be more visible & easily editable? 

Anyway, just a suggestion to help make the software even better.  Let me know if there's a better place to send this.  

Thanks! -Chris KJ6WEG


Field Day Log - feature request for Operator info on main page

Christiaan Adams
 

Hi, I've been using our club's N3FJP Field Day log for several years now and love it.  Finally registered the software (whole package) for myself recently, so I'm new to this forum. Not sure if this is the best way to submit feedback, but I couldn't find any feedback options on the N3FJP website. Let me know if there's a better place for this.  

The FD Log is great, but there's always been one thing I wished for... that it was easier to see & edit the Operator Callsign & Initials. At our club's FD site (usually 3 stations), we switch operators quite frequently... usually once an hour or more. And very rarely do folks remember to update the log to reflect the current operator, resulting in incorrect logs and hours spent correcting them. The Operator fields are hidden behind a menu item.  Since this is the setting we want to edit the most often (after the QSO info), I think it would help a lot if the Operator Callsign & Initials were on the front page and easily editable... maybe down at the bottom with the Band and Mode?  I realize that for most other contests/logs, it might make sense to have the operator info in a menu, since it probably doesn't change often... but for Field Day, at least at our site, we change it a lot. 

Anyone else wish for the Operator info to be more visible & easily editable? 

Anyway, just a suggestion to help make the software even better.  Let me know if there's a better place to send this.  

Thanks! -Chris KJ6WEG


Re: JTAlert to N3FJP on Networked Computer

Scott Davis
 

Hi Randy,

Thanks for your e-mail.  it sounds like you may be confusing the interactions of networking with the JTAlert TCP connection.  First, I suggest that you set up networking, verify that all PCs are able to add a QSO to the common data file without error and otherwise are working properly.  

Once you have networking properly up and running, then enable the API (settings menu in my Field Day software) and set up JTAlert.  Please be sure to read Laurie's help section:

Tutorials -> N3FJP Contest Logs Logging" topic.

You will find more set up details here as well:

http://www.n3fjp.com/help/digitalsetup.html#jtalert

I believe that you will need to run a copy of JTAlert on each PC you plan to use for digital, but Laurie's group can help much better with that part of your question (as well as any JTAlert interface problems you may encounter).  Those questions are best posted here:

https://hamapps.groups.io/g/Support

And I am happy to help here with any network follow up questions you may have.

Enjoy Field Day!


73, Scott
N3FJP

Serving the Amateur Radio community with contesting and general logging software since 1997.

1 Peter 3 vs 15: Always be prepared to give an answer to everyone who asks you to give the reason for the hope that you have. But do this with gentleness and respect...


-----Original Message-----
From: techpubsman <RandyMather@...>
To: N3FJPSoftwareUsers <N3FJPSoftwareUsers@groups.io>
Sent: Thu, Jun 20, 2019 6:40 am
Subject: [N3FJPSoftwareUsers] JTAlert to N3FJP on Networked Computer

My club uses N3FJP Field Day logger for field day. We have five operating positions each with a laptop that network connects to a master laptop where the actual logging file exists. For the last few days I have set up the laptops in the network configuration we will be using this weekend and tried to get JTALert to play nicely with N3FJP FD Logging software. Read the tutorial and Looked at a lot of YouTube videos on the subject. Running the latest WSJT-X, JTAlert and FD Logging software versions. Just can not get them to work together. When I click on the TCP checkbox, the software indicates the software on that laptop is a client and you must connect to our master laptop which I have done There is no interaction between JTALert and N3FJP.

Is there something out in there that has more "how to" information on my specific setup. Specifically, PCs networked together for logging using N3FJP?

I posted to the JTAlert group and got a response from Laurie that we may have our laptops setup incorrectly. Normally we use the Shared File selection. But maybe we shouldn't have set up the laptops as Clients to one master laptop. I have exhausted what I know and can try. Any help would be appreciated.

If I can't solve this in the next couple of days, our FD team will just have to do the logging manually. Not a problem but just thought we could take advantage of the connection between the software packages.

Randy - AJ7B


JTAlert to N3FJP on Networked Computer

techpubsman <RandyMather@...>
 

My club uses N3FJP Field Day logger for field day. We have five operating positions each with a laptop that network connects to a master laptop where the actual logging file exists. For the last few days I have set up the laptops in the network configuration we will be using this weekend and tried to get JTALert to play nicely with N3FJP FD Logging software. Read the tutorial and Looked at a lot of YouTube videos on the subject. Running the latest WSJT-X, JTAlert and FD Logging software versions. Just can not get them to work together. When I click on the TCP checkbox, the software indicates the software on that laptop is a client and you must connect to our master laptop which I have done There is no interaction between JTALert and N3FJP.

Is there something out in there that has more "how to" information on my specific setup. Specifically, PCs networked together for logging using N3FJP?

I posted to the JTAlert group and got a response from Laurie that we may have our laptops setup incorrectly. Normally we use the Shared File selection. But maybe we shouldn't have set up the laptops as Clients to one master laptop. I have exhausted what I know and can try. Any help would be appreciated.

If I can't solve this in the next couple of days, our FD team will just have to do the logging manually. Not a problem but just thought we could take advantage of the connection between the software packages.

Randy - AJ7B


Re: Remembering Window Location on Desktop

Scott Davis
 

Hi Michael,

Thanks for your e-mail.  Some forms, including the main form, will remember the location, provided it is started on the same monitor set to the same resolution as last run.  Otherwise it will start on the default monitor.  Other forms, such as the map do not.  

There has never been a way to set the software to remember open windows from last session and reopen them automatically (aside from the option to open the band map and CW mini forms on start up, which you can configure on their respective set up pages).

Enjoy!

73, Scott
N3FJP

Serving the Amateur Radio community with contesting and general logging software since 1997.

1 Peter 3 vs 15: Always be prepared to give an answer to everyone who asks you to give the reason for the hope that you have. But do this with gentleness and respect...


-----Original Message-----
From: Michael WA7SKG <wa7skg@...>
To: N3FJPSoftwareUsers <N3FJPSoftwareUsers@groups.io>
Sent: Wed, Jun 19, 2019 8:30 pm
Subject: [N3FJPSoftwareUsers] Remembering Window Location on Desktop

I thought I had run into this before, but can't find it. How do I get
the program to remember what windows are open and where they are located
on the desktop? I normally run with two monitors and have the main log
entry screen on the laptop screen and the map and network windows on the
second screen. IIRC, some time ago, whenever I opened N3FJP, the windows
came up where I had left them.  Now, whenever I start the program, I
must open the map and network windows, then move them where I want them.

How do I get them to open automatically and stay where I put them across
closing/opening?

tnx es 73,
Michael WA7SKG




OT: issue using PST rotator software with AC Log

Nickus de Vos
 

Hi all
This is kind of off topic, but maybe someone on here can help.

I use a Tailtwister rotator with a Rotor EZ board fitted which gives it computer control.
I use PST Rotator software and AC Log.

Everything in the PST software seems to be configured correctly, it’s set to receive info from AC Log, that’s pretty much the only setup which is needed.

In AC Log when I start to type a call sign, the rotators brake releases, so clearly there is some communication between AC Log and PST. The rotator however doesn’t turn to the correct heading, it will maybe turn a couple of degrees then stop.
If I go over to the PST software window I can see it received all info from AC Log, it will have the heading, grid and call sign filled in the fields which it pulled from AC Log, if I then press enter on one of the fields it will turn to the heading as it should.

Am I missing something, must I press a specific button in AC Log after I typed a call sign for it to turn?

Thank you
Nickus - ZR6JN - KG44DD

TeLL: 082 389 9477
Email: nickus.zr6jn@...


Remembering Window Location on Desktop

Michael WA7SKG
 

I thought I had run into this before, but can't find it. How do I get the program to remember what windows are open and where they are located on the desktop? I normally run with two monitors and have the main log entry screen on the laptop screen and the map and network windows on the second screen. IIRC, some time ago, whenever I opened N3FJP, the windows came up where I had left them. Now, whenever I start the program, I must open the map and network windows, then move them where I want them.

How do I get them to open automatically and stay where I put them across closing/opening?

tnx es 73,
Michael WA7SKG


Re: Band Status and Chat Function

Michael WA7SKG
 

As this is a private/closed network with no Internet access, all firewalls and virus protection is turned off or disabled. The database functions are working fine, only the Band Status and Chat are not working.

I have reviewed all the referenced docs and find nothing related to the issue. I'm hoping it is just something with the particular laptop I borrowed for testing and that the others at the FD site will function properly. I guess we'll find out Friday at setup.

As we are kind of loose with our schedules and availability, it will be important to know what band and mode the other stations are using so we don't end up with two stations on the same band/mode at the same time.

Thanks,
Michael WA7SKG


Scott Davis via Groups.Io wrote on 6/19/19 10:52 AM:

Hi Michael,
Thanks for your e-mail.  The most likely cause is that your Windows / Internet protection software is clamping down on the connection attempt.  Giving the client the proper permissions to be able to connect in your protection software will likely do the trick.
Lots more details are here:
http://www.n3fjp.com/help/networkinghelp.html
Enjoy!
73, Scott
N3FJP
_http://www.n3fjp.com_
/Serving the Amateur Radio community with contesting and general logging software since 1997./
1 Peter 3 vs 15: /Always be prepared to give an answer to everyone who asks you to give _the reason for <http://www.n3fjp.com/Faith.htm>the hope that you have <http://www.n3fjp.com/Faith.htm>_. But do this with gentleness and respect/...
-----Original Message-----
From: Michael WA7SKG <wa7skg@...>
To: N3FJPSoftwareUsers <N3FJPSoftwareUsers@groups.io>
Sent: Wed, Jun 19, 2019 5:59 am
Subject: [N3FJPSoftwareUsers] Band Status and Chat Function
Getting ready for FD, I finally got another computer to test networking with. I followed the various directions and both computers are using the database and contacts are showing up on the other computer appropriately. Dupe checking is working. The only thing that isn't working right now is the Band Status and Chat Function. On the primary computer hosting the database, it shows up in the Band Status Grid properly. The other computer does not show up in either grid. On the other computer, nothing shows at all in the grid. I have checked Enable Status/Chat Functions on both machines. The status on the primary computer says "Connected to computer". On the other machine, the status says "Attempting to connect to computer". I am using File Share, not TCP.
Any suggestions on what I might be doing wrong?
tnx es 73,
Michael WA7SKG


Re: Function key issues

Steven Dick, K1RF
 

Solved!  The problem was that the Field Day software was not set to CW mode.  Putting it in CW mode solved the problem.  Thanks!!

-Steve K1RF


[HamApps] New JTAlert 2.13.8 available - Win10 1903 fix + more. #announcement #newrelease

Scott Davis
 

Hi All,

FYI, Laurie's latest JTAlert release is just out and includes an N3FJP related enhancement, where contest exchanges are forced to upper-case when sent to N3FJP loggers.  More details are in the forwarded message below.

If you have any questions, please post them to the JTAlert group here:

https://hamapps.groups.io/g/Support

Enjoy!


73, Scott
N3FJP

Serving the Amateur Radio community with contesting and general logging software since 1997.

1 Peter 3 vs 15: Always be prepared to give an answer to everyone who asks you to give the reason for the hope that you have. But do this with gentleness and respect...


-----Original Message-----
From: HamApps Support (VK3AMA) <vk3ama.ham.apps@...>
To: Support <Support@HamApps.groups.io>
Sent: Wed, Jun 19, 2019 5:36 pm
Subject: [HamApps] New JTAlert 2.13.8 available - Win10 1903 fix + more. #Announcement #NewRelease

The Latest JTAlert version 2.13.8 is now available @ https://HamApps.com


The Release Notes...
  Changes:
    - Contest exchanges forced to upper-case when sent to N3FJP loggers.

  Fixes:
    - Non-responsive Minimize and Close buttons (traditional JTAlert) after
       Win10 v1903 update. Note, these buttons still don't display the normal
       color changes when the mouse pointer is hovered over the buttons, but
       are now responding to mouse-clicks.
    - Alerted DX Callsign coloring in WSJT-X applied to the wrong decode when
       another station is calling that DX Callsign in the same period as the DX
       is transmititng and their decode appears after the original DX decode.
    - B4 colors not being applied. (2.3.6 defect)


de Laurie VK3AMA


Re: Band Status and Chat Function

John KC4LZN
 

Michael, 

I experimented with this a couple of days ago and experienced the same issue. It was after a bit,  both computers finally came up on the grid.  Attributed to gremlins and hope it's that simple. It may have taken a bit for the network to populate but it did finally come up. 

...and what Scott said too... virus protection. 

GL
John
KC4LZN 


On Wed, Jun 19, 2019, 14:03 Scott Davis via Groups.Io <SNKDavis=aol.com@groups.io> wrote:
Hi Michael,

Thanks for your e-mail.  The most likely cause is that your Windows / Internet protection software is clamping down on the connection attempt.  Giving the client the proper permissions to be able to connect in your protection software will likely do the trick.

Lots more details are here:



Enjoy!

73, Scott
N3FJP

Serving the Amateur Radio community with contesting and general logging software since 1997.

1 Peter 3 vs 15: Always be prepared to give an answer to everyone who asks you to give the reason for the hope that you have. But do this with gentleness and respect...


-----Original Message-----
From: Michael WA7SKG <wa7skg@...>
To: N3FJPSoftwareUsers <N3FJPSoftwareUsers@groups.io>
Sent: Wed, Jun 19, 2019 5:59 am
Subject: [N3FJPSoftwareUsers] Band Status and Chat Function

Getting ready for FD, I finally got another computer to test networking with. I followed the various directions and both computers are using the database and contacts are showing up on the other computer appropriately. Dupe checking is working. The only thing that isn't working right now is the Band Status and Chat Function. On the primary computer hosting the database, it shows up in the Band Status Grid properly. The other computer does not show up in either grid. On the other computer, nothing shows at all in the grid. I have checked Enable Status/Chat Functions on both machines. The status on the primary computer says "Connected to computer". On the other machine, the status says "Attempting to connect to computer". I am using File Share, not TCP.

Any suggestions on what I might be doing wrong?

tnx es 73,
Michael WA7SKG

18641 - 18660 of 56321