Suggestion - improvement

[oliverbross]

WaveLogGate works exceptionally well. It provides excellent bridge between wsjtx and Wavelog. Superb effort to the author / developer!

However, looking at the functionality, it almost have everything to for example allow Rumlog, which is the best OS X software to send QSO's directly to Wavelog, which has superior statistics and QSL management.

Rumlog has full support of TCI and works well with TCI enabled sw, including for example CW keying without using external winkey ...

Rumlog can also send QSO information, the same way as WSJTX over UDP:

So I strongly believe, the fantastic developer should have have a big problem to listen to Rumlog and UDP packets to get the QSO details and send them over to the waveloug the same way as it works with WSJTX.

So not only listening on UDP 2333 but in parallel to listen to 12060 can allow Rumlog seamlessly to work with Wavelog.

Now, I would love this enhanced functionality!

[oliverbross]

I have found the contact info rumlog / n1mm are using and exchanging:

<?xml version="1.0" encoding="utf-8"?> <contactinfo> <app>N1MM</app> <contestname>CWOPS</contestname> <contestnr>73</contestnr> <timestamp>2020-01-17 16:43:38</timestamp> <mycall>W2XYZ</mycall> <band>3.5</band> <rxfreq>352519</rxfreq> <txfreq>352519</txfreq> <operator></operator> <mode>CW</mode> <call>WlAW</call> <countryprefix>K</countryprefix> <wpxprefix>Wl</wpxprefix> <stationprefix>W2XYZ</stationprefix> <continent>NA</continent> <snt>599</snt> <sntnr>5</sntnr> <rcv>599</rcv> <rcvnr>0</rcvnr> <gridsquare></gridsquare> <exchangel></exchangel> <section></section> <comment></comment> <qth></qth> <name></name> <power></power> <misctext></misctext> <zone>0</zone> <prec></prec> <ck>0</ck> <ismultiplierl>l</ismultiplierl> <ismultiplier2>0</ismultiplier2> <ismultiplier3>0</ismultiplier3> <points>l</points> <radionr>l</radionr> <run1run2>1<run1run2> <RoverLocation></RoverLocation> <RadioInterfaced>l</RadioInterfaced> <NetworkedCompNr>0</NetworkedCompNr> <IsOriginal>False</IsOriginal> <NetBiosName></NetBiosName> <IsRunQSO>0</IsRunQSO> <StationName>CONTEST-PC</StationName> <ID>f9ffac4fcd3e479ca86e137df1338531</ID> <IsClaimedQso>1</IsClaimedQso> <oldtimestamp>2020-01-17 16:43:38</oldtimestamp> <oldcall>W1AW</oldcall> <SentExchange>XYZ NY</SentExchange> </contactinfo>

[oliverbross]

Also, by implementing the above, the functionality will work automatically with N1mm so we will get cross platform support!

[int2001]

N1MM Packets are already parsed by WLGate. But highly beta, because N1MM doesn't use the well-documented ADIF-Format.

The other issue "Wavelog should listen for Rumlog-Pakets" - y should it do that? Wavelog is meant as a full logger, not as something you dump in QSOs from another logger.

[oliverbross]

Thank you for your comment. And I agree with you, under the ideal scenario you are using only 1 log. I see a bright future of wave log and I'll be honest here - I would like the wavelog to become my primary log. However that's not possible at this moment, due to the cluster / banmap needs finishing, to show, filter and able to be fully customisable, which is work in progress and I'm sure it will be done. Also, not everyone outside of us has winkeyer, I use keying via tci - directly from the log, aout 50% of my contacts are cw and are done this way.

At this moment I have to "dump" contacts from my other log to wavelog to use excellent functionalities of the wavelog but I can't use it fully due to the unfinished cluster and not ale to make cw contacts without using winkeyer. WSJTX dumps qso's nicely directly to wavelog, I don't even need to see any other windows than wavelog, and than the 2 other ones:

and

Rumlog can dump contacts directly to wavelog to use other superior functionalities of what will I hope eventually become the best log. The DX spots/cluster needs improving as well as at least for me and I'm sure there are more CW without winkey.

Your fantastic gate can provide the enhanced functionality while the wavelog will catch-up.

[int2001]

As told: As long as your log / 3rd-party application emits ADIF via Port 2333 it already works.
we tested it with Swisslog. no problem.

if rumlog doesn't emit ADIF via 2333 you should perhaps open an issue there.

and tbh: i don't see the point to support a zoo of other formats than the standard ADIF. N1MM was only a try, thats the reason why it is still in beta.

back to your issue.
what is it about? The Format? Another Port than 2333? an additional Port?

i am a bit lost...

[oliverbross]

Thank you again.

looking at how the wsjtx passes information to your sw and then wavelog, I see what I am asking should be easy to implement.

Unfortunately Rumlog can not send anything via 2333, it can listen to wsjtx on 2333, as well as other plethora software, plus can also communicate with other and send them information exactly the same way as the wsjtx does - udp, with I strongly believe exactly the same format.

I have no right to tell you what you should do, you are the professional here.

But I do strongly believe, if you would allow your excellent bridge to listen to:

port 12060-12064, so user can just setup the port from this range, even a single hard coded 12060 could do the job.

Then your gateway will interecept the qso and safely save it to wavelog. Again, I could be wrong, but the developer I believe strongly follows the standards and there should not be problems like you have experienced with n1mm.

[int2001]

ok. its about a port.
understand. i try to add 12060 to it.

tnx

[oliverbross]

yes, let's not make it complicated, I can then fully test it, thank you, you are the best!

[int2001]

pse test this one: https://github.com/wavelog/WaveLogGate/releases/download/untagged-d0de99f5ad64d7e880d4/WaveLogGate-1.1.1.Setup.exe

[oliverbross]

I would love to test it straight away, but need a mac / os x version ... shall I compile it by myself?

[int2001]

didn't know. sorry: https://github.com/wavelog/WaveLogGate/releases/download/untagged-d0de99f5ad64d7e880d4/WaveLogGate-1.1.1-universal.dmg

update: Added the wrong port. going to correct it

[oliverbross]

the link is not valid, can you try again please?

[int2001]

darn. pse test this one: https://dj7nt.de/WLG.dmg

[oliverbross]

downloading, thank you

[int2001]

i downloaded rumlog by my self and noticed two things:
1.) Port is freely adjustable. Not only 12060
2.) RumLog seems to emit nothing up on logging a QSO.

...