Log4OM

As I found several entries in my l4om logbook appearing as not confirmed by eqsl although they are in fact confirmed, I initiated a download from eqsl. Upload to eqsl is working fine, so all according parameters should be set correctly.
Although the download command was not restricted to "since latest check" and the dates were set to a span wide enough, the reply is "no qso found". Neither the qsls in my eqsl archive were recognized, nor the QSLs currently in the eqsl inbox.

What could cause this?

73,
Willi, DJ6JZ

Can you check a QSO example from Log4OM and the correspondent one in EQSL?
Check, mainly those parameters:

CALL (must be equal)
DATE (must be the same)
TIME (+- 30 minutes)
BAND (must be equal)
MODE (must be equal)

then let me know, thanks

73
Daniele

I only find the difference: BAND:3>20M vs. BAND:3>20m

Example:

Adif outbox eqsl:
<CALL:5>VP9MZ<QSO_DATE:8:D>19920902<TIME_ON:4>0010<BAND:3>20M<MODE:3>SSB<RST_SENT:2>56<QSL_SENT:1>Y<QSL_SENT_VIA:1>E<QSLMSG:45>tnx fr ur eQSL, Larry, I just became a member<EOR>

Adif L4om:
Bermuda <A_INDEX:1>0 <ANT_AZ:3>292 <ANT_EL:1>0 <TEN_TEN:1>0 <BAND:3>20m <CALL:5>VP9MZ <CONT:2>NA <COUNTRY:7>Bermuda <CNTY:9>Middlesex <CQZ:1>5 <DISTANCE:4>5722 <DXCC:2>64 <EQSL_QSL_RCVD:1>N <EQSL_QSL_SENT:1>Y <GRIDSQUARE:6>FN42KI <ITUZ:2>11 <LOTW_QSL_RCVD:1>N <LOTW_QSL_SENT:1>N <MODE:3>SSB <MY_CQ_ZONE:1>0 <MY_GRIDSQUARE:6>JO31kk <MY_ITU_ZONE:1>0 <NAME:16>Laurence Koolkin <PROGRAMID:6>Log4OM <PROGRAMVERSION:8>1.17.1.0 <QSL_RCVD:1>N <QSL_SENT:1>Y <QSL_SENT_VIA:1>E <QSL_VIA:6>WB2YQH <QSO_DATE:8>19920902 <QTH:20>Watertown; Ma; 02472 <RST_SENT:2>55 <RX_PWR:1>0 <TIME_ON:6>001000 <TX_PWR:1>0 <FORCE_INIT:1>0 <K_INDEX:1>0 <MAX_BURSTS:1>0 <NR_BURSTS:1>0 <NR_PINGS:1>0 <PFX:3>VP9 <SFI:1>0 <APP_LOG4OM_VALIDATED_CALLSIGN:1>Y

vy 73,
Willi, DJ6JZ

Willi,
If the band is different it will not match and the eQSL status will not be updated because it is not the same QSO

I believe Willi is saying the "M" is lower case in Log4OM adif (m) and upper case in Eqsl adif (M).

yes, only lower / upper case is different.

One other slight difference is the Time ON is 4 characters in Eqsl case and 6 characters in Log4OM. I don't know if this would make a difference or not.

I don't know why Log4OM exports a lower case M for the band, i.e. 20m, or at a minimum Log4OM should except either case.

Daniele?????????

... a follow-up:
In the meantime I corrected all old entries manually. But the problem persists also regarding logs that were created (and uploaded to eqsl successfully) by l4om. Although there exists a confirmation in the inbox (checked by web interface), the return message reads:
"ADIF request accepted NO QSO FOUND"

Is there any setting that could cause a wrong reply for eqsl download, while upload works fine?

73,
Willi

I'll check for those data and add some normalizations in the code to work with upper/lower case.
Time is already managed correctly.

Mmmh i've made checks on the code but everything seems to be handled correctly.
Band is already saved as LOWER CASE on adif read.
I will investigate further on EQSL side.

Please try again setting "QSO MADE FROM" to an older value, TO set to today and the LATEST CHECK to sometime in 1980...
This will redownload everything, or almost everything depending to QSO MADE FROM parameter