Frequently asked questions on installing and using the Marconi Logger: practical FAQ, common doubts and troubleshooting. Reference version: Marconi Logger 2.2.2 (FAQ edition: October 2026).
What this page is for. To give clear answers to the questions that may come up before, during and after installation, even for operators who are not computer experts. The Logger stores your QSOs on your own computer and prepares the files required by the Marconi project.
In a nutshell. On Windows the default folder is C:\McActivity; on Linux it is ~/McActivity. Once installed, the program works without an Internet connection. For the final log check, always keep the Cabrillo .cbr file together with its .cbr.sig file.
Note. The Logger’s menus and fields are in Italian: on this page their names are given as they appear in the program, with the English meaning in brackets where useful.
How to use this FAQ
The questions are grouped by topic: the index takes you straight to the section you need. To look for a word such as “signature”, “JSON”, “Linux”, “map”, “backup” or the exact text of an error message, use your browser’s search (Ctrl+F).
| Version covered | 2.2.2 — Windows and Linux |
|---|---|
| Windows folder | C:\McActivity (can be changed during installation) |
| Linux folder | ~/McActivity |
| Main data | SQLite database, exports, maps, backups, logs, words and phrases |
| Shortcut keys | Enter (Invio) = log the QSO; Esc = clear the DX fields; Alt+W = clear all the fields of the station worked |
| Files to submit | The Cabrillo .cbr file plus its matching .cbr.sig |
Topics
- 1. Before installing: doubts and objections
- 2. Installing on Windows
- 3. Installing on Linux
- 4. First start, sessions and databases
- 5. Operator fields, words and phrases
- 6. Logging and managing QSOs
- 7. Map, greyline and small screens
- 8. Exports, Cabrillo and .sig files
- 9. Privacy, security and integrity
- 10. Updates, backups and transfers
- 11. Common problems and support
- Checklist before an activity session
- Limits to be clearly stated
1. Before installing: doubts and objections
The key answers to decide, with full knowledge, whether and how to use the program.
1. Why use the Marconi Logger instead of a simple spreadsheet or another logging program?
Because it collects, in a single format, all the data needed for the Marconi activity, handles Testo 1 and Testo 2 (Text 1 and Text 2), keeps track of any changes made to QSOs and automatically creates the Cabrillo file together with its .sig integrity check. Another logger may be excellent for general use, but it will not necessarily produce all this data in the format expected by the log checker.
2. Isn’t it an unnecessary complication for a simple on-air activity?
The aim is not to make radio more bureaucratic, but to reduce manual reconstructions and make the logs of both stations comparable. After the initial setup, everyday use mainly means filling in the fields and pressing Enter.
3. Do I need an Internet connection while I am on the air?
No. The Logger works locally. Internet may be needed to download installers, updates and the JSON file of words and phrases; it is not needed to log QSOs or to create exports.
4. Does the program automatically send my data to the Club or to other services?
No. The database and the exports stay on your computer until you decide to copy or upload them. The Logger never sends QSOs automatically.
5. Can I try it without putting my usual logs at risk?
Yes. You can create a new test session, log a few QSOs and delete its database afterwards. In any case, do not use the file of a real session for testing.
6. Must it be installed in C:\McActivity?
No. That is the default folder on Windows because it is easy to find and not hidden. During installation you can choose another folder; all working subfolders will be created under the folder you choose.
7. Is the Logger portable, i.e. can it simply run from a USB stick?
The official release is meant to be installed. Copying only the executable may leave out runtime files, maps or required folders. To move your activity between computers, install the Logger on each computer and copy the data with the program closed.
8. Which bands are available?
The band menus include 160 m, 80 m, 40 m, 20 m, 15 m, 10 m and 2 m. The band chosen in the Operatore (operator) section is automatically copied to the Stazione collegata (station worked) section.
9. Can antivirus software or SmartScreen flag the installer?
It can happen with programs distributed to a small community or not signed with a commercial certificate. Before allowing it to run, check that the file comes from the Club’s official channel and that its name and version are the ones announced. Do not disable your antivirus permanently.
2. Installing on Windows
Recommended folder, permissions and how the files are organised.
10. Which Windows version is described here?
Version 2.2.2. If the title bar shows a different number, some menu items or functions may not match this FAQ exactly.
11. Why does Windows ask for administrator permission?
The installer has to create the program folder, install the required components and set up the shortcuts. The request is for the installation only; normal use should not require administrator rights every time.
12. What is created under C:\McActivity?
The Dati (data) folder and, inside it, Database, maps, Esportazioni (exports), Backup, Log and ParoleFrasi (words and phrases). This way your files are not hidden in AppData and are easier to find.
13. Can I choose a different drive, for example D:?
Yes. Select the folder in the installer. The Logger will use it as the base for its subfolders; the drive must remain available, though, and parts of the installation must not be moved by hand after the first start.
14. What happens if the chosen folder does not exist?
The installer creates it. If the folder cannot be written to, or is protected by company policies, the installation may fail: choose an allowed location or ask whoever manages the computer.
15. Are the maps included in the installer?
Yes. The Windows release includes three basic maps — blank, physical and political — and places them in the Dati\maps subfolder.
16. Do I get an error if the old folders in AppData do not exist?
No. Migrating old data is just an attempt to copy it: if the old location does not exist, the Logger carries on normally. Old files, when present, are not deleted automatically.
17. Can I install over a previous version?
Yes, as long as you use the official installer and first make a backup copy of C:\McActivity\Dati or of your custom folder. Updating the program should not require deleting your databases.
18. Does uninstalling also delete my QSOs?
Never treat uninstalling as a backup system. Before removing the program, always copy the whole Dati folder. Behaviour may change from one installer to another: the only safe practice is to keep a verified external copy.
3. Installing on Linux
A .deb package and a universal archive with an installer are available.
19. Which Linux distributions are supported?
The universal installer is designed for Debian 12/13 and derivatives, Ubuntu 22.04/24.04 and derivatives (including Mint and Pop!_OS), Fedora, openSUSE, Arch and derivatives. Future changes in the distributions may require some adjustments.
20. Is the mcactivity-logger_2.2.2-1_amd64.deb package fine for Ubuntu?
Yes, for Ubuntu or Debian-compatible systems with x86_64/AMD64 architecture. It is not the right package for ARM computers, such as many single-board computers.
21. When should I use the universal archive?
When your distribution does not use .deb packages, or when you want a single-user installation. After extracting it, run ./install.sh --user; for a system-wide installation run sudo ./install.sh --system.
22. What does the --no-deps option mean?
It tells the installer not to install the dependencies automatically. Use it only if Python, Tk and the required modules are already installed and working; otherwise the program may not start.
23. Why may Internet be needed during the Linux installation?
Because the distribution may have to download missing Python packages or libraries. Once the dependencies are installed, normal use of the Logger is entirely local.
24. Why do I get “no display name and no $DISPLAY environment variable”?
The Logger is a graphical program and has been started in a session without a graphical display, typically over SSH or from a service terminal. Start it from a terminal in your XFCE/desktop session. Setting DISPLAY by hand does not create a display if no graphical session is really available.
25. What are the minimum requirements on Linux?
A working X11 or Wayland graphical environment, Python 3.10 or later and Tkinter. Administrator rights or network access may be needed to install missing dependencies.
26. Where is the data stored on Linux?
In the ~/McActivity folder of the user running the program. This is separate from /opt/mcactivity, which may hold the program in a system-wide installation.
27. If I uninstall on Linux, do I lose ~/McActivity?
The installer is designed not to remove user data. It is still good practice to copy the ~/McActivity folder before major updates or maintenance.
4. First start, sessions and databases
Each session is a local database; choosing correctly at start-up avoids writing to the wrong file.
28. What should I choose at the first start?
You can create a new session, open an existing database or use the database proposed for the current date. For a new activity session it is best to create a session with an easily recognisable name.
29. What is the .db file?
It is the SQLite database of the session. It contains the QSOs and related information. It is not a file to open with Notepad and must not be edited by hand.
30. Is the data saved only when I close the program?
QSOs are written to the database as you go. A sudden shutdown is always a risk for any file: make backup copies, especially after a complete activity session.
31. Can I reopen a previous session?
Yes. At start-up choose to open an existing database and select the right file in the Database folder or wherever it has been archived.
32. Can I work on the same database from two computers at the same time?
Not recommended. An SQLite file is not a multi-user synchronisation system. Use one computer at a time and copy the database only when the Logger is closed.
33. Can I rename the database?
Yes, with the Logger closed, but it is better to use clear names and not to change the extension. After renaming it, select the new name when opening it.
34. Is the logged time local time or UTC?
The Logger shows and logs UTC date and time in the relevant fields. The computer clock must be right: a system with a wrong date, time or time zone can produce inconsistent entries.
The menus, item by item
The menu bar at the top contains File, Impostazioni (Settings) and Help. The table below explains what each command does and what to check if it does not work as expected.
| File › Nuovo Database (.db) — new database | Creates a new session database and makes it the active one. Choose a recognisable name; if you cancel the window, the current database stays unchanged. |
|---|---|
| File › Salva copia Database (.db) — save a copy | Copies the current database to the Backup folder or to the location you choose. If an error appears, check free space and write permissions. |
| File › Esporta ADIF (.adi) — ADIF export | Exports the QSOs in ADIF format for other programs. It does not replace the Cabrillo file required by the Marconi log checker. |
| File › Esporta Cabrillo (.cbr) — Cabrillo export | Creates the Cabrillo file and, automatically, its .cbr.sig. If one of the two files is missing, do not submit the pair and check the folder permissions. |
| File › Stampa Log Completo (PDF) — print the full log | Creates the PDF summary of the log and tries to open it. If the PDF is created but does not open, there may be no PDF reader associated with it. |
| File › Esci — exit | Closes the Logger properly. Better than ending the process from Task Manager; if anything is in progress, wait for it to finish. |
| Impostazioni › Dati Operatore — operator data | Opens the window with the fixed data: call, name, locator, QTH, MC ARI number, power and activity. SALVA DATI (save data) stores them and shows them in the main window. |
| Impostazioni › Carica Parole e Frasi — load words and phrases | Selects and validates the official JSON file. A file with the wrong structure, number of items or lengths is rejected with an explanatory message. |
| Impostazioni › Seleziona Mappa — select map | Shows the available maps, lets you add one and use the selected one. If no maps are listed, check Dati\maps and Pillow. |
| Impostazioni › Pianifica Durata Attività — schedule the activity | Sets the date and the UTC start and end times, and starts the countdown. The required formats are YYYY-MM-DD and HH:MM; a wrong format is rejected. |
| Help › Manuale PDF — PDF manual | Opens help.pdf. If “Manuale non trovato” (manual not found) appears, the file is missing from the installation; if it exists but does not open, check the default PDF reader. |
| Help › Info | Shows information about the Logger and the installed version. This is the first thing to check before asking for help. |
5. Operator fields, words and phrases
The operator’s fixed data stays available; the two exchange texts are renewed instead.
35. Why are characters turned into capitals?
It is an intentional normalisation, to make log comparison uniform and avoid purely cosmetic differences. The editable fields write in capitals by default.
36. Which operator data stays the same after a QSO?
Call, name, locator, QTH, MC ARI number, power, activity, band and mode remain available. The operator’s Testo 1 and Testo 2 are the exception: new ones are proposed after each QSO.
37. What are Testo 1 and Testo 2?
Testo 1 (Text 1) is an Italian word of 4–6 characters. Testo 2 (Text 2) is an Italian phrase of no more than three words and no more than 15 transmitted characters, not counting spaces, because in CW spaces are not sent as characters.
38. Where do the words and phrases come from?
From a JSON file distributed separately. The official file contains exactly 200 different words and 200 different phrases, all within the set limits.
39. Why isn’t the JSON built into the Logger?
So that the list can be updated or replaced without reinstalling the program. This way the Club can distribute a new collection while the Logger stays the same.
40. How do I load the JSON file?
Open Impostazioni (Settings), choose “Carica Parole e Frasi” (load words and phrases) and select the official file. The Logger validates it and keeps a copy in its Dati\ParoleFrasi folder, or in the equivalent Linux folder.
41. What happens if the JSON file is missing?
The Logger starts anyway and shows a warning. The random proposals of Testo 1 and Testo 2 cannot work properly until a valid file is loaded.
42. Can I create or edit a JSON file myself?
Technically the Logger checks its structure and limits, but for an official activity session you must use the file distributed by the Club. A different list may be flagged by the log checker even when both stations wrote the same text.
43. Can words and phrases repeat straight away?
No. The Logger keeps a history to avoid repetitions within the same session and for up to four consecutive sessions. After that the items become available again.
44. Where is the history of proposals kept?
In the cronologia_proposte.json file, in the words and phrases folder. Deleting it resets the history, so it must not be done during normal activity.
45. What happens if the available combinations run out?
The Logger warns the operator. Check that you have loaded the complete official list and not a shortened or damaged version.
46. Does the log checker count as an error a text that is the same in both logs but not in the JSON?
Not as a formal matching error, because the two logs agree. It does, however, report it in that operator’s summary with a note such as “Parola non presente nel JSON ma corretta con il corrispondente” (word not in the JSON but matching the other station).
6. Logging and managing QSOs
Shortcut keys, clearing fields and later corrections.
Moving between fields
You can click directly in the field you want. To work almost entirely from the keyboard, use Tab to go to the next field and Shift+Tab to go back. In the Banda (band) and Modo (mode) drop-down menus, choose the value with the mouse or with the arrow keys once the cursor is on the control. Letters you type are turned into capitals automatically.
Watch the last field. When the cursor is in Testo 2 of the STAZIONE COLLEGATA (station worked), Tab goes no further: the Logger shows the message “Per favore, premi il tasto INVIO per confermare il QSO” (please press ENTER to confirm the QSO). After checking the line, press Enter to log it.
Recommended order
- Before the activity session, fill in the OPERATORE (operator) data once. Call, name, locator, QTH, MC ARI number, power, activity, band and mode must be correct; Testo 1 and Testo 2 are proposed from the JSON.
- Go to Call DX in the STAZIONE COLLEGATA (station worked) section. After each QSO is logged correctly, the cursor comes back here automatically.
- Enter, in this order, Call DX, Nome DX (name), MC ARI, Locatore DX (locator), Potenza (power), QTH DX, RST S and RST R. Move on with Tab or click the field you want.
- Check Data UTC and Ora UTC (date and time), filled in automatically from the computer clock. Correct them only if necessary, using the formats YYYY-MM-DD and HH:MM.
- Check Banda DX and Modo DX. The operator’s band is copied automatically to the DX side and the mode is CW, but the final check is up to the operator.
- In Testo 1 and Testo 2 of the station worked, enter what you actually copied from the other station, without replacing it with your own texts.
- After Testo 2, quickly check call, RST, band and texts. Press Enter or click AGGIUNGI QSO (INVIO) (add QSO).
- If all the data is valid, the QSO appears in the table; the fields of the station worked are cleared, the DX band goes back to the operator’s band, the DX mode goes back to CW, the cursor returns to Call DX and new operator texts are proposed.
What the fields mean and what to check
| Mio Call / Call DX | Callsign of the operator / of the station worked. Watch out: A Call DX already in the log may trigger DUPE DI SESSIONE (session dupe): check before logging. |
|---|---|
| Nome / Nome DX | Name of the operator / of the station worked. Watch out: Do not leave it blank and do not enter the callsign instead of the name. |
| Locatore / Locatore DX | Maidenhead locator of both stations. Watch out: A wrong locator moves the point on the map and makes the log inconsistent. |
| QTH / QTH DX | Location of both stations. Watch out: Use a clear and consistent name. |
| MC ARI nr | MC ARI number of the operator or of the station worked. For non-ARI members enter N. Watch out: The field is mandatory and cannot be left blank. N is accepted and turned into a capital automatically; also make sure you do not swap the data of the two stations. |
| Potenza W | Power in watts used by each station. Watch out: Enter the actual value, without any extra text. |
| Attività | Name of the activity/session. Watch out: It is part of the operator data: make sure you are not reusing the name of a previous session by mistake. |
| Banda / Banda DX | Band used by each station. Watch out: 160M, 80M, 40M, 20M, 15M, 10M and 2M are allowed; the DX band follows the operator’s band. |
| Modo / Modo DX | Operating mode. Watch out: The current version accepts CW; any other value is rejected. |
| RST S / RST R | Report sent and report received. Watch out: They must be cleared after Enter; fill them in again for every QSO. |
| Data UTC / Ora UTC | Date and time of the QSO in UTC. Watch out: Mandatory formats: YYYY-MM-DD and HH:MM. They depend on the computer clock. |
| Testo 1 operatore | Word proposed for you to send to the other station. Watch out: Not to be confused with the word received, which goes in Testo 1 of the station worked. |
| Testo 2 operatore | Phrase proposed for you to send to the other station. Watch out: It changes after the QSO is logged; spaces are not characters sent in CW. |
| Testo 1 stazione collegata | Word actually copied from the station worked. Watch out: Write down what you copied, without correcting it by looking at the other operator’s text. |
| Testo 2 stazione collegata | Phrase actually copied from the station worked. Watch out: It is the last field: Tab shows the reminder, Enter tries to log the QSO. |
If Enter does not log the QSO
The Logger does not log an incomplete or invalid line: it lists the missing mandatory fields or reports a date, time, band or mode that is not valid. Correct the fields shown and press Enter again. If no message appears, check that a secondary window has not been left open in front of or behind the main window. If “Impossibile inserire il QSO” (unable to log the QSO) appears, do not just keep trying: check free space, the permissions of the Database folder and the technical log, after making a copy of the database.
47. How do I log a QSO?
Fill in the required fields of the station worked and press Enter or the Aggiungi QSO (add QSO) button. Before logging, the Logger checks the mandatory data.
48. What is cleared after Enter?
All the fields of the station worked, including RST S, RST R, Testo 1 and Testo 2. The operator’s fixed data stays; the two operator texts are replaced with a new random proposal.
49. What does Alt+W do?
It clears all the fields of the Stazione collegata (station worked) section while you are filling them in. It does not delete the operator data.
50. What does Esc do?
It clears the DX/station worked fields with the quick function provided, without logging the QSO.
51. Why does the DX band change by itself?
It is intentional: when you select the operator’s band, the same band is automatically proposed for the station worked too. It is still up to the operator to check that the value is correct.
52. Does the Logger warn me if the callsign is already in the log?
Yes, it may flag a possible dupe. The warning helps avoid accidental entries; the operator must judge it in the context of the session.
53. How do I edit or delete a QSO?
Double-click the line in the QSO table, then choose the available operation. Always check callsign, date and time before confirming.
54. Is a correction tracked?
Yes. The database keeps the edited status of the QSO and the number of changes. The Cabrillo export includes the relevant metadata.
55. Why may an edited QSO get a penalty even if it is correct in the end?
Because the final Cabrillo shows the correct value, but the edit count shows that the QSO was corrected after it was logged. The penalty is for the edit itself, not for an error still present.
56. If I edit the Cabrillo file with Notepad, can I hide the edit count?
You can change the characters in the file, but then the content no longer matches the .sig signature created by the Logger. The integrity check should therefore detect the change.
57. Does the callsign search change the log?
No. It is used to filter or find QSOs already logged; it does not change any data unless you explicitly open an edit.
7. Map, greyline and small screens
The map is an operating aid, but it does not decide whether the log is valid.
58. What is the greyline?
It shows the transition zone between day and night. It can help you understand propagation conditions, but it does not replace the operator’s own judgement on the air.
59. The map seems to show day and night the wrong way round: what should I check?
First check the system date, time and time zone. The current version includes the fix for the inversion reported in earlier versions; if the problem persists, note the version and the UTC time and send a screenshot to the support team.
60. Why does “Nessuna mappa disponibile” (no map available) appear?
The maps folder may be missing, may have been moved or may not contain the expected files. On Windows check Dati\maps and, if necessary, repair the official installation instead of copying random files.
61. Can I use the Logger without the map?
Yes. The map is not needed to save QSOs or create exports; it is a support function.
62. The window does not fit on a small monitor: is it a bug?
The interface and the clock adapt to the screen, but very low resolutions or high system scaling can reduce the available space. Try maximising the window and, if necessary, temporarily lower the screen scaling while keeping the text readable.
63. Can I zoom or move the map?
Yes, zoom and drag functions are available. The point depends on the locator entered: a wrong locator naturally gives a wrong position.
8. Exports, Cabrillo and .sig files
This is the most important section before submitting your logs.
64. Which exports does the Logger create?
ADIF, a PDF of the full log and Cabrillo. For the Marconi log checker, the Cabrillo file comes with its .sig integrity file.
65. Where are the exported files saved?
By default in the Dati\Esportazioni subfolder of the installation folder; on Linux in the equivalent folder under ~/McActivity. The save window may show a different location.
66. What is the .cbr.sig file?
It is an integrity check calculated on the content of the Cabrillo file. It lets the system verify that the .cbr file is exactly the one signed by the Logger.
67. Do I have to enter a key to create the .sig?
No. In the current version the shared key is built into the Logger and the log checker; it is the same for everyone and the .sig is created automatically, with no input window.
68. What must I submit or upload?
The .cbr file and its matching .cbr.sig. They must be the pair created at the same time, for the same content.
69. Can I open the Cabrillo file with Notepad?
Yes, to read it. Do not save it again: even an apparently harmless change, such as spaces, line endings or encoding, can change the bytes and invalidate the signature.
70. Can I rename the files?
The safest choice is not to rename them. If the upload system accepts renamed files, the .cbr and .sig must keep the same base name and remain the original pair; do not change their content.
71. If I create the Cabrillo again, do I get a new .sig?
Yes. Each export creates the check for the content produced at that moment. Always submit the latest pair and never mix a new .cbr with an older .sig.
72. Why does the portal say FILEID-ORDER not compliant or wrong number of fields?
Usually the Cabrillo file is not in the expected version/format, has been edited, or comes from an outdated program. Create it again with the current Logger and upload the new .cbr/.sig pair.
73. Does the Cabrillo file also contain Testo 1 and Testo 2?
Yes. The current Marconi format includes both texts of the operator and of the station worked, as well as the data needed for the comparison and the relevant edit information.
74. Can the PDF of the log replace the Cabrillo file?
No. The PDF is easy to read and useful for reference or printing; the log checker needs the expected structured format, that is the Cabrillo file with its .sig.
9. Privacy, security and integrity
What the Logger protects and what remains the operator’s responsibility.
75. Where are my personal and radio data?
In the local database and in the exports you create. Anyone with access to the computer or to the copies can read this information; use the normal protections of your system and keep your backups safe.
76. Does the .sig file encrypt the Cabrillo file?
No. The Cabrillo file stays readable. The signature is used to verify integrity, not to hide the content.
77. Is the built-in key personal?
No. It is anonymous and common to all compatible installations, as required by the project. It does not identify the individual member.
78. Can the log checker know who actually pressed the keys?
No. It can compare data, consistency, signature and the expected metadata, but it cannot establish on its own the physical identity of the person at the computer.
79. Is it safe to send the .db database?
It contains more operating information than is normally needed for uploading. Send the database only if asked to for support and once you understand what data it contains; for normal activity use the required export files.
80. Can I delete the Log files?
They can be useful to diagnose a problem. Before deleting them, keep a copy if you need to ask for help. Do not delete databases or exports by mistaking them for simple technical logs.
10. Updates, backups and transfers
A verified copy is the simplest protection against mistakes, failures and interrupted updates.
81. What should I back up before updating?
The whole Dati folder on Windows or ~/McActivity on Linux, with the Logger closed. The copy must include at least Database, Esportazioni and ParoleFrasi.
82. Where should I keep the backup?
On a device or location other than the main disk: USB stick, external disk or cloud storage. A second folder on the same disk does not protect you from a disk failure.
83. How do I check that the backup is really usable?
Check that sizes and dates look right and, on a test copy, check that the Logger can select the database. Never run destructive tests on your only copy.
84. Can I move a session from Windows to Linux or vice versa?
The SQLite database can in principle be moved between compatible versions. Copy it with the program closed, keep the original and open the copy with the same version of the Logger. Check a few QSOs before carrying on.
85. Can Google Drive sync the database directly while it is open?
Not recommended: syncing and simultaneous access can create conflicts or diverging copies. Close the Logger, then copy or sync the file.
86. How can I tell whether the update was successful?
Check the version number in the title bar, open a test session, check maps and JSON, log a test QSO and export a .cbr/.sig pair.
87. Should I also keep the old versions?
It is useful to archive previous installers and sources in a separate folder, but for new activity sessions you must use the current official version. Do not mix executable files from different versions in the same installation.
11. Common problems and support
Before reinstalling, note the exact message and put your data in a safe place.
88. The Logger does not open: what is the first thing to check?
Check that the installation is complete, that the antivirus has not quarantined any files and that the folder exists. On Linux start it from a graphical session and read any message in the terminal.
89. I get a permission error or “access denied”: what should I do?
Check that your user can write to the Dati folder or to ~/McActivity. Do not change permissions blindly on the whole disk; fix only the Logger’s folder or reinstall in an allowed location.
90. The JSON file is rejected: what are the most common causes?
A number other than 200 words or 200 phrases, duplicates, words outside the 4–6 character limit, phrases longer than three words or 15 transmitted characters, an invalid JSON structure or a tampered file. Download the official version again.
91. The texts do not change after the QSO: what should I check?
Make sure the QSO was really logged and that a valid JSON file is loaded. Also check for any warnings about running out of combinations or problems with the history.
92. RST S and RST R stay filled in after Enter: is that normal?
Not in version 2.2.2: they must be cleared together with the other fields of the station worked. If they stay, check the version and describe exactly the command used to log the QSO.
93. Alt+W also deletes the operator data: is that normal?
No. In the current version it must clear only the Stazione collegata (station worked) section. Different behaviour means an older version or a fault to be reported.
94. The clock is cut off or too large: what should I do?
Maximise the window, check the screen resolution and scaling, and make sure you are using the version with the adaptive layout. Attach a full screenshot stating the resolution and the scaling percentage.
95. The export creates the .cbr but not the .sig: what should I do?
Do not edit or submit the incomplete Cabrillo file. Check that you have version 2.2.2, the permissions of the Esportazioni folder and any messages. Try again in a folder you can write to and, if the problem persists, send the technical log to the support team.
96. The log checker rejects a pair I have just created: what should I check?
Make sure the .cbr and .sig come from the same export, that neither has been opened and saved again, that the names match and that Logger, log checker and portal are all up to date with the current format.
97. Is reinstalling always the best solution?
No. First make a backup, note the message and check version, permissions, JSON and folders. Reinstalling without a diagnosis may leave the problem unchanged or make it harder to trace.
98. What information should I send to get effective support?
Version number, operating system and its version, installation folder, exact text of the error, the steps that cause it and a full screenshot. If asked, attach the technical log; never send passwords or credentials.
99. What is the emergency procedure before trying anything?
Close the Logger, copy the whole Dati folder or ~/McActivity to a safe place, check that the copy exists and only then try repairs, updates or reinstallations.
Checklist before an activity session
- Check that the title bar shows the current official version.
- Open or create the right database, with a recognisable name.
- Check call, locator, QTH, MC ARI number, power, activity, band and mode.
- Load the official JSON file and check that Testo 1 and Testo 2 are proposed.
- Check the computer’s UTC date and time.
- Log a test QSO and check that the fields are cleared, new texts are proposed and the table is updated.
- Try an export and make sure both the .cbr and the .cbr.sig are created.
- Keep a backup copy of the data folder.
Golden rule. Never edit the Cabrillo file by hand after it has been created and never separate it from its .sig. If something needs correcting, edit the QSO in the Logger and create a new pair.
Limits to be clearly stated
| Shared signature | The .sig checks integrity but is not a personal or legal digital signature. |
|---|---|
| Identity | The software cannot prove who was physically at the keyboard or at the radio. |
| Comparison | The log checker assesses the consistency of the files available; it cannot reconstruct events that were never logged. |
| Backup | No installer replaces a backup copy made and checked by the operator. |
Practical guide — it does not replace the official rules of the activity.