To test this feature, visit your live site.

Logging to N1MM+

Hello and thanks for the great software. I am sending my log to N1MM+ contest/logging program. Most of the logged QSOs generate this N1MM+ error. About 50% of those QSOs actually still get logged, but the 50% doesn't. I'll send to N1MM+ bug reporting since I'm not sure where the fix needs to be.

The attached shows the N1MM+ error window overlayed by the N1MM+ log window. You can see this QSO was actually logged.

6 comments

6 Comments

KE5C

Mar 24

So I got a terse response from N1MM+ "Based on the error messages, Vara is using the WSJT-N1MM interface to log QSO's in N1MM. We do not support that. You will have to work with the Vara developer." I want to respond asking why they talked about the WSJT setup in their documentation if not supported, but what's the point if there is no interest there.

This is just not a big deal and I was just reporting it in case it matters to anyone.

73 de ke5c op john

Edited

irad d

May 14

Replying to

Sadly I will remove TCP to N1MM. I tried to debug it on my end and I can say for sure that they simple do not handle a situation where I close the TCP connection. I guess they designed TCP to connect once upon startup and thats it while the right approach is to connect, send data and disconnect and clear the socket. I also found an email I sent to Tom N1MM on 2022 regarding this that was left with no response.

Given the fact thet UDP works flawlesly - I have decided to remove the TCP approach.

I hope Tom will at some point include some handling of closing TCP connection as this is where it breaks and throws an exception on their end.

73s

Irad