Print

[KD2BNT]

hello fellow hams,

For the first time, I'm operating from another call area requiring me to add the /4 after my callsign. I used Gridtracker, with multicast, to log my QSOs. I've updated my callsign field in JTDX and JTAlert to include the /4 (KD2BNT/4) and current grid square. The configuration seems to operate well until the logging phase. Gridtracker logs my QSOs to HRDLOG.net and QRZ.com, but I received a logging error in QRZ.com via XML API. HRDLOG.net logs the QSO fine. The error I receive is:

Error uploading QSO QRZ.com (wrong station_callsign for this logbook kd2bnt_4 doesnt match book callsign KD2BNT)

It's obvious that the inclusion of the /4 is causing the problem but my main concern is whether or not I'm configured correctly to operate outside my call area. Is my setup correct?

Stack:
JTDX/FT8
JTAlert for JTDX
Gridtracker

KD2BNT David, 73

[WW1SS]

There is a place in your QRZ page to add an alias. Go to edit then basic call sign data. I don't know if that will cure your problem but it is worth a try. You can also ask the webmasters at QRZ and they could tell you how to do it.

[N1NK]

SFAIK at this time, we are not required to sign /x when operating away from home.  this can cause confusion as some do so and others do not.  when operating digital mode, the most efficient method to avoid confusion is to not sign /x which then allows you to include your current and correct grid square which sometimes indicates the state.  and if you do this, then add at least a note in your QRZ page indicating which grid squares correspond to which state.

this may or may not help GridTracker as I have no experience with it.  I usually just use the QRZ listed state unless there is another clue like a grid square that does not match.

as a matter of grid square trivia, FN41 where I am located, could be CT, MA or RI although the vast majority of it is RI.

back way back when, if we wanted to operate away from the location specified on our license, we had to write the district engineer and let them know start and end of portable operation.  it was a big deal then, much less so now from a legal requirement standpoint.  again SFAIK.   Jim/N1NK/Tiverton RI

[W4FID]

I had the same issue but I "broke the code". I have 2 profiles in QRZ. W4FID and W4FID/P. When I travel I edit the W4FID/P to show where I am. Lat, Long, grid square, address, zones, etc. The result is GridTracker shows where I am, the path to who I am working, etc. FT8 shows the azimuth and distance from where I am, and the other guy sees my grid square etc. I keep QSLs in QRZ and e-QSL as separate entries for W4FID if I'm home and W4FID/P if I am away.