# VA QSO Party 2026 logging issues

**URL:** <https://community.worldradioleague.com/t/va-qso-party-2026-logging-issues/45127>\
**Category:** Contesting\
**Created:** [March 23, 2026, 1:40am UTC](https://community.worldradioleague.com/t/va-qso-party-2026-logging-issues/45127 "2026-03-23T01:40:04Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![N2FSM](https://sea1.discourse-cdn.com/flex019/user_avatar/community.worldradioleague.com/n2fsm/32/34624_2.png) [@N2FSM](https://community.worldradioleague.com/u/N2FSM)\
**Post date:** [March 23, 2026, 1:40am UTC](https://community.worldradioleague.com/t/va-qso-party-2026-logging-issues/45127/1 "2026-03-23T01:40:04Z")

</div>

Just an FYI to let you know I had issues with submitting my log. This time I did fill out the “My Exchange” but the exported Cabrillo log did not include my state. Also the order for the exchange was incorrect. I had to import to N1MM to fix & then export the corrected file to submit.

This is what exported from WRL;

QSO: 7192 PH 2026-03-22 2232 N2FSM 001 K4O LDN 1016

This is what was exported from N1MM:

QSO: 7192 PH 2026-03-22 2232 N2FSM 0001 IN K4O 1016 LDN

---

<div class="post-metadata">

**Author:** ![K4AZE](https://sea1.discourse-cdn.com/flex019/user_avatar/community.worldradioleague.com/k4aze/32/36274_2.png) [@K4AZE](https://community.worldradioleague.com/u/K4AZE)\
**Post date:** [March 23, 2026, 7:00pm UTC](https://community.worldradioleague.com/t/va-qso-party-2026-logging-issues/45127/2 "2026-03-23T19:00:00Z")

</div>

@N2FSM Hey Barry,

Yes we are aware, its only exporting the serial number field and not the ‘my exchange’ field in the Cabrillo. We are pushing a fix.

Thanks & 73  
Brad K4AZE

---

<div class="post-metadata">

**Author:** ![K4AZE](https://sea1.discourse-cdn.com/flex019/user_avatar/community.worldradioleague.com/k4aze/32/36274_2.png) [@K4AZE](https://community.worldradioleague.com/u/K4AZE)\
**Post date:** [March 23, 2026, 9:29pm UTC](https://community.worldradioleague.com/t/va-qso-party-2026-logging-issues/45127/3 "2026-03-23T21:29:15Z")

</div>

@N2FSM Just a heads up this has been fixed