Logging from JTDx to Log4OM2 Error
Posted: 24 Jun 2020, 04:03
Friends,
Thanks for this amazing software. I was using it great till i updated to V2.7.0.0
My Configuration: Windows 7, Radio IC 7610,JTDX v2.1.0-rc149. Logging directly via UDP to log4omv2. All was perfect till i updated to release 2.7.0.0 of Log4omV2, after which i noticed that my automatic upload to LotW was not happening. I found the cause to be the default in CONFIRMATIONS SENT status of LotW in digital modes being Sent : No, I had set it up to be as : requested, and chose it as the default upload Flag in EXTERNAL Services. After the update , the default confirmations is reverting to NO, event after i changed it to requested.. Further i noticed that, this is happening only for digital QSOs, when i do phone or CW, the Confirmations default is: requested , and the LotW autoupload happens on closing the program.
So i narrowed down the issue to be on digital alone , via UDP logging from JTDX. Prior to the update to 2.07.0.0 , it was working great.
I hope i have conveyed the error to the experts.
What am i doing wrong ? Please advise
Thanks , 73 , Jith VU2OY
Thanks for this amazing software. I was using it great till i updated to V2.7.0.0
My Configuration: Windows 7, Radio IC 7610,JTDX v2.1.0-rc149. Logging directly via UDP to log4omv2. All was perfect till i updated to release 2.7.0.0 of Log4omV2, after which i noticed that my automatic upload to LotW was not happening. I found the cause to be the default in CONFIRMATIONS SENT status of LotW in digital modes being Sent : No, I had set it up to be as : requested, and chose it as the default upload Flag in EXTERNAL Services. After the update , the default confirmations is reverting to NO, event after i changed it to requested.. Further i noticed that, this is happening only for digital QSOs, when i do phone or CW, the Confirmations default is: requested , and the LotW autoupload happens on closing the program.
So i narrowed down the issue to be on digital alone , via UDP logging from JTDX. Prior to the update to 2.07.0.0 , it was working great.
I hope i have conveyed the error to the experts.
What am i doing wrong ? Please advise
Thanks , 73 , Jith VU2OY