To test this feature, visit your live site.

Change logging mode for N3FJP

Is there a way to have VarAC log the MODE (DYNAMIC) instead of the SUB-MODE (VARA HF) to N3FJP ACLog?

For the time being, I've disabled the real-time uploading to all four eloggers (lotw, eqsl, qrz and clublog) so I can fix the mode prior to uploading.

Thank you.

73, Mark - KD2NOM

10 comments

Comments (10)

Mark Rosneck

Apr 15

I'm trying to work through N3FJP issues as well. Let me see if I get this straight -- the proper thing for N3FJP's logging program to place in its MODE field is DYNAMIC but it's displaying the SUBMODE (VARA-HF) -- do I have that correct? If so, N3FJP should change that, correct? Is the actual "right" solution to have a MODE and SUBMODE column? The issue I'm having is that N3FJP SHOULD automatically upload my VarAC to QRZ.COM. I can force it to do it manually. In that regard, N3FJP said:

Thanks for your e-mail. AC Log performs the same upload function, regardless of mode specified. I am not familiar with the VarAC software, but if it is writing the record directly to the file and then reloading in AC Log, instead of using AC Log and calling the enter function via API, that would explain it.

I hope that this helps.

Enjoy!

73, Scott

N3FJP

If I understand his comment and your code, Irad, you indeed enter the function via the API. Am I correct?

You also reference a debug log data function. Was this implemented in v9.1.0 and, if so, how do I activate it?

Thanks

Mark KB0US

Mark Rosneck

May 02

Replying to

OK. The issue related to automatically logging VarAC contacts to QRZ.COM that are exported to N3FJP's ACL is:

From Scott N3FJP: Most other developers write the QSO details to the main form's text entry fields and then call the Enter command, which simulates the user pressing enter and initiates all the actions associated with the enter event, including automatic uploads, if enabled.

The app you are using is calling the ADDADIFRECORD method, which essentially imports the QSO via ADIF rather than entering it, so enter event associated code isn't called. The following is from our API documentation:

https://www.n3fjp.com/help/api.html

Add ADIF Record (new in 2.0)

This command will add the record direct to the log file and then immediately load it in the user's list of recent contacts. Since it is added directly to the log file, any callbook lookup, scoring for contests, etc., is bypassed. The solution, as I understand, is to use <CMD><ACTION><VALUE>ENTER</VALUE></CMD> from the current <CMD>< ADDADIFRECORD ><VALUE>ENTER</VALUE></CMD> when exporting to N3FJP's ACL.

I'll submit this as an enhancement request so you have a record of it when you decide whether to make the change or not.

Mark Rosneck

May 02

Replying to

Related to "is N3FJP logging a VarAC contact correctly?", he is indeed stuffing VARAC HF into the MODE column. It turns out that the original ADIF string is maintained intact with MODE=DYNAMIC and SUBMODE=VARA HF as the attached file shows.

It's likely (although I didn't verify it) that an upload from ACL to LOTW works correctly. If the user uses QRZ.COM to upload their VarAC contacts to LOTW, they'll need to map MODE=VARA HF to DYNAMIC using TQSL. although I haven't verified that either.

Thus, from a VarAC perspective, the correct information is being passed to ACL. Whether this is "right" or not is an issue for N3FJP.

irad d

May 03

Replying to

@Mark Rosneck I will be happy to send you a test version to see if it works. You suggest that I simply replace the ADDADIFRECORD with ENTER ?

Mark Steele

Feb 26

Hello,

I wanted to ping this thread again - I would love to be able to log directly to N3FJP but the sub-mode throws an error in my logger. I already have ACL converting DYNAMIC to DIGI when uploading to LoTW so just need to figure out how to get the logging from VARA to 'conform' if possible.

irad d

Feb 27

Replying to

The ADIF comitee has approved the mode DYNAMIC and SubModes VARA HF/FM/SAT

N3FJP need to follow the ADIF standard.

I suggest you contact the N3FJP developer about it

73s

Irad

Mark Steele

Feb 27

Replying to

Irad,

Thank you for the response. I agree with you - however VARA logs the mode as VARA HF and not DYNAMIC. I am requesting that VARA log the mode properly when interfacing with N3FJP. It's dropping the sub mode into the mode field.

irad d

Feb 28

Replying to

VarAC logs Mode as DYNAMIC.

Here is the code:

public static string adif_mode = "DYNAMIC";

public static string adif_submode = "VARA HF";

It is doing the same logging with all programs. There is no "special" treatment for N3FJP.

It is possible that N3FJP is doing something internally that messes it up.

I also added a debug log data so in the next version I release you can check it your self.

07:34:21 - ADIF traffic sent to N3FJP(TCP): <CMD><ADDADIFRECORD><VALUE><CALL:6>4Z9CCG <MODE:7>DYNAMIC <SUBMODE:7>VARA HF <RST_SENT:3>+23 <RST_RCVD:3>+22 <QSO_DATE:8>20240228 <TIME_ON:6>073417 <QSO_DATE_OFF:8>20240228 <TIME_OFF:6>073418 <BAND:3>10m <NAME:4>Irad <STATION_CALLSIGN:5>4Z1AC <TX_PWR:0> <COMMENT:14>QSO with VarAC <EOR></VALUE></CMD>

and here is how that exact record that was sent shows on N3FJP screen:

Again - please contact the N3FJP author.