Hi folks!
I am just starting now to try this SW. I don't understand from manual if it works for my problem:
I have my home callsign IK2RZP and a contest special call IO2A. With my actual logger (Logger32) I
use only one configuration but I have the possibility to insert different operating callsigns and award
management is made (as per actual rules) together. For example, I have ab.25.000 qsos made using
IK2RZP call and ab. 80.000 qsos made using IO2A; I have only one log where if wanted I can split between
the 2 calls (i.e. for qsl printing reason or LOTW upload etc etc) but awards are managed joining credits
as ARRL does.
Does Log4om work in the same way?
If yes, how to proceed in importing with Adif coming from Logger 32?
Thanks and compliments again to Daniele, Terry and all the group
Gino
two callsigns
- IW3HMH
- Site Admin
- Posts: 2988
- Joined: 21 Jan 2013, 14:20
- Location: Quarto d'Altino - Venezia (ITA)
- Contact:
Re: two callsigns
Hi Gino,
Log4OM acts differently. You can (must) create different USER PROFILES (aka different callsigns, or same callsigns in different configurations (eg. IW3HMH, IW3HMH/P and so on).
Each configuration can connect to a different database log file (or the same logfile, if you want to have data "mixed") and have almost every parameter personalized (external service passwords, lotw parameters and so on).
Label printing works "per callsign" (you should select your callsign in the first screen of label management) to allow you to print only contest qso to different QSL and more.
To keep all data joined the suggestion is to create 2 different profiles, pointing at the SAME database log file.
This way your statistics will be "merged" and DXCC statistics will be keep mixed. Label prints are safely printable too.
Please note: even if you use the same logfile database, import each ADIF with the relative profile, because the import will add (if missing in adif export) the STATION_CALLSIGN ADIF value of the current profile. This will keep your data separated, because the ones loaded with your IK2 callsign will be marked IK2RZP and the ones imported when you were using the profile of the contest station will be marked with IO2A
You have a lot of solutions to suit your needs, simply choose the one that you like more.
If you need more help we're there
Welcome aboard
Daniele
Log4OM acts differently. You can (must) create different USER PROFILES (aka different callsigns, or same callsigns in different configurations (eg. IW3HMH, IW3HMH/P and so on).
Each configuration can connect to a different database log file (or the same logfile, if you want to have data "mixed") and have almost every parameter personalized (external service passwords, lotw parameters and so on).
Label printing works "per callsign" (you should select your callsign in the first screen of label management) to allow you to print only contest qso to different QSL and more.
To keep all data joined the suggestion is to create 2 different profiles, pointing at the SAME database log file.
This way your statistics will be "merged" and DXCC statistics will be keep mixed. Label prints are safely printable too.
Please note: even if you use the same logfile database, import each ADIF with the relative profile, because the import will add (if missing in adif export) the STATION_CALLSIGN ADIF value of the current profile. This will keep your data separated, because the ones loaded with your IK2 callsign will be marked IK2RZP and the ones imported when you were using the profile of the contest station will be marked with IO2A
You have a lot of solutions to suit your needs, simply choose the one that you like more.
If you need more help we're there

Welcome aboard
Daniele
Daniele Pistollato - IW3HMH
- G4POP
- Log4OM Alpha Team
- Posts: 11605
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: two callsigns
Ciao Gino,IK2RZP wrote:Hi folks!
I have only one log where if wanted I can split between
the 2 calls (i.e. for qsl printing reason or LOTW upload etc etc) but awards are managed joining credits
as ARRL does.
Does Log4om work in the same way?
If yes, how to proceed in importing with Adif coming from Logger 32?
Thanks and compliments again to Daniele, Terry and all the group
Gino
First ensure that the Logger 32 exported ADIF has your station call sign recorded correctly both for the 25.000 qsos made using
IK2RZP call and ab. 80.000 qsos made using IO2A
Example field in ADIF file
<STATION_CALLSIGN:5>G4POP
In Log4OM please ensure that you have updated the Country Database, SCL Database and Clublog Database files by going to the "Settings" menu
In the Log4OM Import ADIF window please check the "Update Countries in ADIF box because Logger 32 records are notoriously inaccurate in this respect. MAKE SURE YOU HAVE UPDATED THE DATABASES ABOVE BEFORE IMPORTING!
In Log4OM you will be able to automatically upload to LOTW and eQSL for either call sign, just use the 'Search Parameters' in QSL Management to select the correct call.
For Labels you can select either IK2RZP or IO2A in the label print window by using the drop down "Station Call sign" list
Log4OM awards will display awards for the collective total of both call signs
If you need further assistance please ask
73 Terry G4POP
Re: two callsigns
It works!
I am happy about that!
Log4OM is much slower than Logger 32 but this kind of operations has to be done just once so no worries!
Now another question (and more in the future): if I want to log a qso as IK2RZP or IO2A, in logger32 I have
a window menu in which there is a choice like "change operator" or if needed "change log" (I also have VP9/IK2RZP).
How do I move from one operator callsign to another with automatic filling of station callsign field?
By the way, I had to rename ADIF Logger32 field "operator" to "STATION_CALLSIGN" for importing correctly into
Log4om.
Is there any disadvantage to manage such a large database with more than 100.000 qsos?
I will post other questions under different argument subjects.
Again thanks and compliments. The grafic interface is intriguing me!
73
Gino
I am happy about that!
Log4OM is much slower than Logger 32 but this kind of operations has to be done just once so no worries!
Now another question (and more in the future): if I want to log a qso as IK2RZP or IO2A, in logger32 I have
a window menu in which there is a choice like "change operator" or if needed "change log" (I also have VP9/IK2RZP).
How do I move from one operator callsign to another with automatic filling of station callsign field?
By the way, I had to rename ADIF Logger32 field "operator" to "STATION_CALLSIGN" for importing correctly into
Log4om.
Is there any disadvantage to manage such a large database with more than 100.000 qsos?
I will post other questions under different argument subjects.
Again thanks and compliments. The grafic interface is intriguing me!
73
Gino
- G4POP
- Log4OM Alpha Team
- Posts: 11605
- Joined: 21 Jan 2013, 14:55
- Location: Burnham on Crouch, Essex UK
Re: two callsigns
Hi Gino,
No problem with the large database SQLite should be OK for 120,000 records plus. However for the fastest logging you might like to consider changing to a MySQL database, full instructions are in the user manual.
With regard to the different station call sign logging you have two choices
1. When you need to change the station callsign and/or operator call sign you could change it in the options/station info tab and then change back later.
2. Alternatively use a separate configuration and then select the required configuration but you will need to restart the program to effect the change - Again full instructions are in the user guide
No problem with the large database SQLite should be OK for 120,000 records plus. However for the fastest logging you might like to consider changing to a MySQL database, full instructions are in the user manual.
With regard to the different station call sign logging you have two choices
1. When you need to change the station callsign and/or operator call sign you could change it in the options/station info tab and then change back later.
2. Alternatively use a separate configuration and then select the required configuration but you will need to restart the program to effect the change - Again full instructions are in the user guide
73 Terry G4POP