My Grandsons and I ran FD from my house this year using the Family club callsign. Another Station informed us that we were a dupe although FD logging program did NOT catch the Dupe. We did some sleuthing and discovered that since we had diligently changed operator in the log that these counted as different contacts. A good way to look foolish. What can be done about this. I have used ACLOG for over ten years and it has been wonderful. This is my first use of the FD program. Doesn't this cause problems when Clubs use it for logging??

Given this was a new thing, 6.3 was great.  Here’s a couple of oddities maybe to look into once you feel like it:   My total was 127.  My software was saying 36, which might have been 1st Day count but can’t remember. This only started on day 2.  Worked perfectly on day 1.  Shut down and restarted the software- waited 3 minutes and magically it caught up.  Almost.  My count was 127, software said 105.  I know I ran into two Canadian contacts who were insisting their section was one the software didn’t like. I put in what the told me despite 6.3 protestations.  But that was only a couple instances. Don’t know what happened to the other 20 or so.

Anyway give this was all pretty much last minute stuff for everybody, generally it worked well most of the time for most of the people.

thank you from N9DMS 
Dave

Received this error message this morning when reopening the database during Field Day 2020. Attempts to continue resulted in the software not logging subsequent contacts. Please provide direction. Thank you. W7COA Cliff

See the end of this message for details on invoking

just-in-time (JIT) debugging instead of this dialog box.

 

************** Exception Text **************

System.FormatException: String was not recognized as a valid DateTime.

   at System.DateTimeParse.Parse(String s, DateTimeFormatInfo dtfi, DateTimeStyles styles)

   at System.Convert.ToDateTime(String value)

   at DavisLibrary.GetAndSetSystemTime.GetCurrentSystemDateAndTimeFormatted()

   at DavisLibrary.Form1.UpdateTimeLabels()

   at DavisLibrary.Form1.UpdateScoreLabels()

   at DavisLibrary.Form1.OnStart()

   at DavisLibrary.Form1.Form1_Load(Object sender, EventArgs e)

   at System.Windows.Forms.Form.OnLoad(EventArgs e)

   at System.Windows.Forms.Form.OnCreateControl()

   at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)

   at System.Windows.Forms.Control.CreateControl()

   at System.Windows.Forms.Control.WmShowWindow(Message& m)

   at System.Windows.Forms.Control.WndProc(Message& m)

   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)

   at System.Windows.Forms.Form.WmShowWindow(Message& m)

   at System.Windows.Forms.Form.WndProc(Message& m)

   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)

   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)

   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

 

 

************** Loaded Assemblies **************

mscorlib

    Assembly Version: 4.0.0.0

    Win32 Version: 4.8.4180.0 built by: NET48REL1LAST_B

    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll

----------------------------------------

FieldDay

    Assembly Version: 6.3.0.0

    Win32 Version: 6.3.0.0

    CodeBase: file:///C:/Program%20Files%20(x86)/FieldDay.exe

----------------------------------------

System.Windows.Forms

    Assembly Version: 4.0.0.0

    Win32 Version: 4.8.4150.0 built by: NET48REL1LAST_C

    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll

----------------------------------------

System

    Assembly Version: 4.0.0.0

    Win32 Version: 4.8.4001.0 built by: NET48REL1LAST_C

    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll

----------------------------------------

System.Drawing

    Assembly Version: 4.0.0.0

    Win32 Version: 4.8.3752.0 built by: NET48REL1

    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll

----------------------------------------

System.Configuration

    Assembly Version: 4.0.0.0

    Win32 Version: 4.8.3752.0 built by: NET48REL1

    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll

----------------------------------------

System.Core

    Assembly Version: 4.0.0.0

    Win32 Version: 4.8.4180.0 built by: NET48REL1LAST_B

    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll

----------------------------------------

System.Xml

    Assembly Version: 4.0.0.0

    Win32 Version: 4.8.3752.0 built by: NET48REL1

    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll

----------------------------------------

System.Data

    Assembly Version: 4.0.0.0

    Win32 Version: 4.8.4121.0 built by: NET48REL1LAST_C

    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll

----------------------------------------

System.Transactions

    Assembly Version: 4.0.0.0

    Win32 Version: 4.8.3752.0 built by: NET48REL1

    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_32/System.Transactions/v4.0_4.0.0.0__b77a5c561934e089/System.Transactions.dll

----------------------------------------

System.EnterpriseServices

    Assembly Version: 4.0.0.0

    Win32 Version: 4.8.3752.0 built by: NET48REL1

    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_32/System.EnterpriseServices/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.EnterpriseServices.dll

----------------------------------------

System.Numerics

    Assembly Version: 4.0.0.0

    Win32 Version: 4.8.3752.0 built by: NET48REL1

    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll

----------------------------------------

 

************** JIT Debugging **************

To enable just-in-time (JIT) debugging, the .config file for this

application or computer (machine.config) must have the

jitDebugging value set in the system.windows.forms section.

The application must also be compiled with debugging

enabled.

 

For example:

 

<configuration>

    <system.windows.forms jitDebugging="true" />

</configuration>

 

When JIT debugging is enabled, any unhandled exception

will be sent to the JIT debugger registered on the computer

rather than be handled by this dialog box.

 

 

Hi Scott...

I noticed that when I shut down FD this year, the count was different.  I have attached a screen shot for you.  Can you 'plain? :)

The log(left side) shows 286 contacts but the counter (right) shows 285.  ??

Thanks....Tom VE3II

You must use the remote section with 127.0.0.1 and 1100 and then browse to the field day log file. Be sure to drop down the box and select field day. See digital setup instructions and it explains where each is entered.

Sent from my Verizon iPhone. Please disregard all auto correct errors.

I am new to ACL0g and appreciated the immediate picture and info from QRZ when I begin entering a contact. 
Is there a way to choose an already logged contact and go to their QRZ page? I see that I can right click and bring up the log for editing, but would like to look up QRZ info without have to open my browser and manually type in a call.
Thank you - 73
Paul - KA9GOU

Using tab 1 does not work fully--it does not fill my exchange and both sent and rcv fields in log popup. switching back to tab 2 works as expected. Once FD is over I will delve more into this and see what is up.

yes and yes. I have 6.3 or later selected and I read, and followed the instructions to a T. I am thinking windows security or permissions of sorts.
thanks again.

Yes. I use the regular ACLog and have no issue with it. i have ACLog enabled and selected the remote button and selected the FD Log using 127.0.0.1 and port 1100..I tried local as well, but get same error I created the new FD Log in same location as the regular log. The JT Alert popup window has all the info from WSJtx filled in correctly. I will check to see in a bit which tab I am using. thanks for the quick response

You said you selected the FD Log, but no mention that you selected the correct Log Type, did you do that?
   

The JTAlert Help file has simple instructions for setting up for correct N3FJP Contest logs. Those instructions if followed will yield a working setup.

de Laurie VK3AMA

Yes. I use the regular ACLog and have no issue with it. i have ACLog enabled and selected the remote button and selected the FD Log using 127.0.0.1 and port 1100..I tried local as well, but get same error I created the new FD Log in same location as the regular log. The JT Alert popup window has all the info from WSJtx filled in correctly. I will check to see in a bit which tab I am using. thanks for the quick response

yep have that setup. callsign fills in when first transmission with a call. its just when i click the Log QSO from JTAlert popup windows that it fails to fillin section and class. jtalert has the correct log file selected etc.

Have you setup JTAlert to use the N3FJP FD log? JTAlert will only log the contest exchanges if it is told your using the FD logger, it is not sufficient to just specify the log file.

WSJT-X will only pass contest exchanges in the logged qso data if your using Tab1 of the WSJT-X window, you should not use Tab2 (this is a WSJT-X feature? not a JTAlert issue).

de Laurie VK3AMA

yep have that setup. callsign fills in when first transmission with a call. its just when i click the Log QSO from JTAlert popup windows that it fails to fillin section and class. jtalert has the correct log file selected etc.