Log4OM

I see the same as in Your description (btw: the link to Your pdf is not working with the %20 in it).

My log looks like this (code is as well changed to ***):

2020-07-23 15:43:56.7662 INFO: [#=zadY2xfcm$l1XcaDQgFMZbgI=] : Massive upload of 10 on HRDLOG
2020-07-23 15:43:58.2839 INFO: [#=zs1XXNewh$e_o2wcCUwjjpK6yTpCs] : [HRDLOG UPLOAD LOG] uploading LOG with 10 QSO
2020-07-23 15:43:58.2879 INFO: [#=z5CV3ekDMzh3JnqjAjzvf9ySuoJdP] : [HRDLOG UPLOAD] Uploading QSO on HRDLOG: EA1DHB|22.07.2020 09:05:00|20m|SSB
2020-07-23 15:43:58.2879 INFO: [AdifManagement] : Begin export single QSO to ADIF string
2020-07-23 15:43:58.2879 INFO: [AdifManagement] : Export QSO to ADIF file completed
2020-07-23 15:43:58.2948 INFO: [#=zyHNNjjPqp1IF9jBYSQ==] : PostDataAsync: Posting data to http://robot.hrdlog.net/NewEntry.aspx. upload information:
CALLSIGN=HB9GZX/P CODE=*****APP=LOG4OM2 ADIFDATA=<BAND:3>20M <CALL:6>EA1DHB <DISTANCE:6>982.93 <DXCC:3>281 <EQSL_QSL_RCVD:1>R <EQSL_QSL_SENT:1>Y <FREQ:9>14.350000 <GRIDSQUARE:6>IN82FW <LOTW_QSL_RCVD:1>R <LOTW_QSL_SENT:1>Y <MODE:3>SSB <STATION_CALLSIGN:8>HB9GZX/P <QSL_RCVD:1>R <QSL_SENT:1>R <QSL_SENT_VIA:1>E <QSO_DATE:8>20200722 <RST_RCVD:2>59 <RST_SENT:2>55 <TIME_ON:6>090500 <EOR>
2020-07-23 15:43:58.4995 INFO: * [#=z5CV3ekDMzh3JnqjAjzvf9ySuoJdP][211 ms] : [HRDLOG UPLOAD] ###### END ######
2020-07-23 15:43:58.5015 INFO: [#=z5CV3ekDMzh3JnqjAjzvf9ySuoJdP] : [HRDLOG UPLOAD] Uploading QSO on HRDLOG: EA2DT|22.07.2020 09:06:00|20m|SSB
2

What could be the solution?

Hi Team Log4OM
Could You please have a look at this small issue and provide a fix in the next release? As written in the posts earlier, the upload with the normal callsign is working like a charm. But the upload with /P provides errors, as the username ist not sent correctly.
Thank You and best 73

I'm checking the code to verify if we "encode" callsign in some way.
A fix, if necessary, will be released in the next version.

Thanks for the excellent "bug tracking" activity

Thank You and Your team for the excellent work!

Issue found.
i was using the station callsign in the QSO for logging in purposes, instead of the "main" callsign in the settings.
Fix will be released soon. Sorry for inconvenience

Perfect, Thanke You. As user it is allways a riddle as if the issues is between the chair and computer or if there is a bug somewhere

it's usually on the developer's side

Good stuff thanks.