N1MM remote did get its name from previous versions of WSJT-X that used this naming for remote that was meant to send qso data in ADIF format from WSJT-X to N1MM.
In latest versions of WSJT-X this has renamed to "Secondary UDP server (depreaced)"
So the direction is always from "other program" to cqrlog.
If "other program" can send UDP datagram to specified port (in cqrlog's prefrences/fldigi/wsjt interface) using ADIF formatted qso data cqrlog's N1MM remote can log the qso.
You do not see any action in cqrlog unless you have set preferences/NewQSO/Refresh data after save QSO checkbox and keep NewQSO/Window/QSO list open
The reason of defunct is that your debug shows that qso data is not in ADIF format.
I do not know N1MM program so I can not say can it be configured right way.
<p>Hi Saku,</p>
<p> </p>
<p>Now I understand what's wrong with me. CQRLog has not implemented in its code the reception of records from N1MM because N1MM sends them in XML format. It's a pity because it would be very useful.</p>
<p>Using the N1MM tag in the menu I think it causes confusion.</p>
<p>I have tried sending from WSJT and I see that it arrives to my Linux machine in ADIF format</p>
<p>01:38:50.269078 IP 192.168.1.36.60323 > ubuntu.2333: UDP, length 256</p>
<p> </p>
<p>root@ubuntu:~# tcpdump -i ens33 -A port 2333</p>
<p>tcpdump: verbose output suppressed, use -v or -vv for full protocol decode</p>
<p>listening on ens33, link-type EN10MB (Ethernet), capture size 262144 bytes</p>
<p>01:38:50.269078 IP 192.168.1.36.60323 > ubuntu.2333: UDP, length 256</p>
<div>E..........}...$...#.......<call:5>PP0JJ <gridsquare:4>JN61 <mode:3>FT8 <rst_sent:0> <rst_rcvd:0> <qso_date:8>20201029 <time_on:6>083848 <qso_date_off:8>20201029 <time_off:6>083848 <band:3>40m <freq:8>7.075250 <station_callsign:5>EA3CV <my_gridsquare:6>JN11BI <operator:5>EA3CV <eor></div>
<div> </div>
<p>but CQRLog does nothing.I checked the ports that are open on my Linux, and it turns out that 2333 is not listening</p>
<p> </p>
<p>root@ubuntu:~# nmap localhost -u</p>
<p>Starting Nmap 7.60 ( https://nmap.org ) at 2020-10-29 01:37 PDT</p>
<p>Nmap scan report for localhost (127.0.0.1)</p>
<p>Host is up (0.000051s latency).</p>
<p>Not shown: 999 closed ports</p>
<p>PORT STATE SERVICE</p>
<p>631/tcp open ipp</p>
<p>Nmap done: 1 IP address (1 host up) scanned in 0.05 seconds</p>
<p> </p>
<p>root@ubuntu:~# nmap -p 2233 localhost</p>
<p>Starting Nmap 7.60 ( https://nmap.org ) at 2020-10-29 01:37 PDT</p>
<p>Nmap scan report for localhost (127.0.0.1)</p>
<p>Host is up (0.000026s latency).</p>
<p>PORT STATE SERVICE</p>
<p>2233/tcp closed infocrypt</p>
<p>Nmap done: 1 IP address (1 host up) scanned in 0.24 seconds</p>
<div> </div>
<p>So how can CQRLog receive the registration? I have verified that there is no active firewall. I also followed the steps you told me to take and nothing has changed.</p>
<p> </p>
<p>Thanks for your help.</p>
<p>Kin</p>
<p>I repeat the answer so that it is in plain text, sorry :( Hi Saku, Hello, Now I understand what's wrong with me. CQRLog has not implemented in its code the reception of records from N1MM because N1MM sends them in XML format. It's a pity because it would be very useful. Using the N1MM tag in the menu I think it causes confusion. On the other hand, I have tried sending from WSJT and I see that it arrives to my Linux machine in ADIF format root@ubuntu:~# tcpdump -i ens33 -A port 2333 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on ens33, link-type EN10MB (Ethernet), capture size 262144 bytes 01:38:50.269078 IP 192.168.1.36.60323 > ubuntu.2333: UDP, length 256 E..........}...$...#.. .....PP0JJ JN61 FT8 <rst_sent:0> <rst_rcvd:0> <qso_date:8>20201029 <time_on:6>083848 <qso_date_off:8>20201029 <time_off:6>083848 40m 7.075250 <station_callsign:5>EA3CV <my_gridsquare:6>JN11BI EA3CV but CQRLog does nothing.I checked the ports that are open on my Linux, and it turns out that 2333 is not listening root@ubuntu:~# nmap localhost -u Starting Nmap 7.60 ( https://nmap.org ) at 2020-10-29 01:37 PDT Nmap scan report for localhost (127.0.0.1) Host is up (0.000051s latency). Not shown: 999 closed ports PORT STATE SERVICE 631/tcp open ipp Nmap done: 1 IP address (1 host up) scanned in 0.05 seconds root@ubuntu:~# nmap -p 2233 localhost Starting Nmap 7.60 ( https://nmap.org ) at 2020-10-29 01:37 PDT Nmap scan report for localhost (127.0.0.1) Host is up (0.000026s latency). PORT STATE SERVICE 2233/tcp closed infocrypt Nmap done: 1 IP address (1 host up) scanned in 0.24 seconds So how can CQRLog receive the registration? I have verified that there is no active firewall. I also followed the steps you told me to take and nothing has changed. Thanks for your help. Kin</p>
You plain text was still not plain.
But no problem.
There are 2 ways to use wsjt-x and cqrlog.
The N1MM remote (that one works also with Js8Call program) and wsjt remote.
With N1MM remote you can just log the qso to cqrlog. When port setting at wsjtx/reporting/secondary UDP server is same as cqrlog preferences/fldigi/wsjt interface/N1MM ans IP addresses 127.0.0.1 at both programs it should work when:
- set N1MM remote on at cqrlog
- set "F2/Reporting/prompt me to log qso" at wsjt-x
- work qso with wsjtx. At the moment you are pressing OK in wsjt-x logging window it sends UDP datagram that cqrlog receives and logs.
- you can not see it unless you have "QSO list" open and manually refresh it, or set preferences/newQSO/Refresh data after save qso
- No other program may be set to receive UDP datagrams at same IP and port.
With wsjt remote you get full benefit of connection. You can see decoded calls against your worked qsos from CQ-monitor/wsjt-map. CQ monitor distpays just CQs, wsjt map displays all decoded frames.
You can initiate qso from CQmonitor or wsjt map by double left click
You can set alerts fro decoded calls, locators, text in common.
When port setting at wsjtx/reporting/UDP server is same as cqrlog preferences/fldigi/wsjt interface/wsjt port ans IP addresses 127.0.0.1 at both programs and at least "Accept UDP requests" is checked at wsjt-x settings (you can set all three checkboxes there).
It should work:
- set wsjt remote on at cqrlog
- set "F2/Reporting/prompt me to log qso" at wsjt-x
- If you can not see CQ-monitor https://www.cqrlog.com/node/3014
- at NewQSO you should see that remote is on as the "call" filed gets new name and will change color time to time when remote is active and connected
- when you start qso by double click from CQmonitor NewQS is filled with HamQTH/QTZ data (if you have st it at preferences)
- when you press OK at wsjtx log window NewQSO is cleared and your qso is logged and can be seen at top of new qso (if you have allowed to view recent qsos there).
-with latest versions (from source) you are able to use multicast IP addresses and so can have several programs listening from same wsjtx UDP datagrams.
I have been working with N1MM <contactinfo> import so that cqrlog could really receive loggings from N1MM used during contest.
I have a version that needs just some fine tuning and testing.
How ever I do not have N1MM installed and no Windoze. I have heard it runs under wine somehow.
What I need is "true life" blocks of <contactinfo> .. </contactinfo> like you have in your message here.
The interesting thing is how N1MM sends contest messages if there are them in addition with serial numbers.
They are "STX_STRING" and "SRX_STRING" in adif format, but how they appear in <contactinfo>? There is a node called <exchange1></exchange1> but does it have both sent and received strings?
This is not explained properly in document I found https://n1mmwp.hamdocs.com/appendices/external-udp-broadcasts/
Can you produce similar dump as in your message from qsos where you have variations:
W1AW 599 001 AB 599 123 DC
W1AW 599 AB 599 123
W1AW 599 001 599 DC
Where 001 and 123 are contest serial numbers sent and received and AB and DC are contest messages
I have been working with N1MM <contactinfo> import so that cqrlog could really receive loggings from N1MM used during contest.
I have a version that needs just some fine tuning and testing.
How ever I do not have N1MM installed and no Windoze. I have heard it runs under wine somehow.
What I need is "true life" blocks of <contactinfo> .. </contactinfo> like you have in your message here.
The interesting thing is how N1MM sends contest messages if there are them in addition with serial numbers.
They are "STX_STRING" and "SRX_STRING" in adif format, but how they appear in <contactinfo>? There is a node called <exchange1></exchange1> but does it have both sent and received strings?
This is not explained properly in document I found https://n1mmwp.hamdocs.com/appendices/external-udp-broadcasts/
Can you produce similar dump as in your message from qsos where you have variations:
W1AW 599 001 AB 599 123 DC
W1AW 599 AB 599 123
W1AW 599 001 599 DC
Where 001 and 123 are contest serial numbers sent and received and AB and DC are contest messages
Hi Kin!
N1MM remote did get its name from previous versions of WSJT-X that used this naming for remote that was meant to send qso data in ADIF format from WSJT-X to N1MM.
In latest versions of WSJT-X this has renamed to "Secondary UDP server (depreaced)"
So the direction is always from "other program" to cqrlog.
If "other program" can send UDP datagram to specified port (in cqrlog's prefrences/fldigi/wsjt interface) using ADIF formatted qso data cqrlog's N1MM remote can log the qso.
You do not see any action in cqrlog unless you have set preferences/NewQSO/Refresh data after save QSO checkbox and keep NewQSO/Window/QSO list open
The reason of defunct is that your debug shows that qso data is not in ADIF format.
I do not know N1MM program so I can not say can it be configured right way.
--
Saku
OH1KH
<p>Hi Saku,</p>
<p> </p>
<p>Now I understand what's wrong with me. CQRLog has not implemented in its code the reception of records from N1MM because N1MM sends them in XML format. It's a pity because it would be very useful.</p>
<p>Using the N1MM tag in the menu I think it causes confusion.</p>
<p>I have tried sending from WSJT and I see that it arrives to my Linux machine in ADIF format</p>
<p>01:38:50.269078 IP 192.168.1.36.60323 > ubuntu.2333: UDP, length 256</p>
<p> </p>
<p>root@ubuntu:~# tcpdump -i ens33 -A port 2333</p>
<p>tcpdump: verbose output suppressed, use -v or -vv for full protocol decode</p>
<p>listening on ens33, link-type EN10MB (Ethernet), capture size 262144 bytes</p>
<p>01:38:50.269078 IP 192.168.1.36.60323 > ubuntu.2333: UDP, length 256</p>
<div>E..........}...$...#.......<call:5>PP0JJ <gridsquare:4>JN61 <mode:3>FT8 <rst_sent:0> <rst_rcvd:0> <qso_date:8>20201029 <time_on:6>083848 <qso_date_off:8>20201029 <time_off:6>083848 <band:3>40m <freq:8>7.075250 <station_callsign:5>EA3CV <my_gridsquare:6>JN11BI <operator:5>EA3CV <eor></div>
<div> </div>
<p>but CQRLog does nothing.I checked the ports that are open on my Linux, and it turns out that 2333 is not listening</p>
<p> </p>
<p>root@ubuntu:~# nmap localhost -u</p>
<p>Starting Nmap 7.60 ( https://nmap.org ) at 2020-10-29 01:37 PDT</p>
<p>Nmap scan report for localhost (127.0.0.1)</p>
<p>Host is up (0.000051s latency).</p>
<p>Not shown: 999 closed ports</p>
<p>PORT STATE SERVICE</p>
<p>631/tcp open ipp</p>
<p>Nmap done: 1 IP address (1 host up) scanned in 0.05 seconds</p>
<p> </p>
<p>root@ubuntu:~# nmap -p 2233 localhost</p>
<p>Starting Nmap 7.60 ( https://nmap.org ) at 2020-10-29 01:37 PDT</p>
<p>Nmap scan report for localhost (127.0.0.1)</p>
<p>Host is up (0.000026s latency).</p>
<p>PORT STATE SERVICE</p>
<p>2233/tcp closed infocrypt</p>
<p>Nmap done: 1 IP address (1 host up) scanned in 0.24 seconds</p>
<div> </div>
<p>So how can CQRLog receive the registration? I have verified that there is no active firewall. I also followed the steps you told me to take and nothing has changed.</p>
<p> </p>
<p>Thanks for your help.</p>
<p>Kin</p>
<p>I repeat the answer so that it is in plain text, sorry :( Hi Saku, Hello, Now I understand what's wrong with me. CQRLog has not implemented in its code the reception of records from N1MM because N1MM sends them in XML format. It's a pity because it would be very useful. Using the N1MM tag in the menu I think it causes confusion. On the other hand, I have tried sending from WSJT and I see that it arrives to my Linux machine in ADIF format root@ubuntu:~# tcpdump -i ens33 -A port 2333 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on ens33, link-type EN10MB (Ethernet), capture size 262144 bytes 01:38:50.269078 IP 192.168.1.36.60323 > ubuntu.2333: UDP, length 256 E..........}...$...#.. .....PP0JJ JN61 FT8 <rst_sent:0> <rst_rcvd:0> <qso_date:8>20201029 <time_on:6>083848 <qso_date_off:8>20201029 <time_off:6>083848 40m 7.075250 <station_callsign:5>EA3CV <my_gridsquare:6>JN11BI EA3CV but CQRLog does nothing.I checked the ports that are open on my Linux, and it turns out that 2333 is not listening root@ubuntu:~# nmap localhost -u Starting Nmap 7.60 ( https://nmap.org ) at 2020-10-29 01:37 PDT Nmap scan report for localhost (127.0.0.1) Host is up (0.000051s latency). Not shown: 999 closed ports PORT STATE SERVICE 631/tcp open ipp Nmap done: 1 IP address (1 host up) scanned in 0.05 seconds root@ubuntu:~# nmap -p 2233 localhost Starting Nmap 7.60 ( https://nmap.org ) at 2020-10-29 01:37 PDT Nmap scan report for localhost (127.0.0.1) Host is up (0.000026s latency). PORT STATE SERVICE 2233/tcp closed infocrypt Nmap done: 1 IP address (1 host up) scanned in 0.24 seconds So how can CQRLog receive the registration? I have verified that there is no active firewall. I also followed the steps you told me to take and nothing has changed. Thanks for your help. Kin</p>
These videos are a bit old (not having all latest features that latest source has) , but good for start
https://www.youtube.com/channel/UC3yPCVYmfeBzDSwTosOe2fQ
--
Saku
OH1KH
HI!
You plain text was still not plain.
But no problem.
There are 2 ways to use wsjt-x and cqrlog.
The N1MM remote (that one works also with Js8Call program) and wsjt remote.
With N1MM remote you can just log the qso to cqrlog. When port setting at wsjtx/reporting/secondary UDP server is same as cqrlog preferences/fldigi/wsjt interface/N1MM ans IP addresses 127.0.0.1 at both programs it should work when:
- set N1MM remote on at cqrlog
- set "F2/Reporting/prompt me to log qso" at wsjt-x
- work qso with wsjtx. At the moment you are pressing OK in wsjt-x logging window it sends UDP datagram that cqrlog receives and logs.
- you can not see it unless you have "QSO list" open and manually refresh it, or set preferences/newQSO/Refresh data after save qso
- No other program may be set to receive UDP datagrams at same IP and port.
With wsjt remote you get full benefit of connection. You can see decoded calls against your worked qsos from CQ-monitor/wsjt-map. CQ monitor distpays just CQs, wsjt map displays all decoded frames.
You can initiate qso from CQmonitor or wsjt map by double left click
You can set alerts fro decoded calls, locators, text in common.
When port setting at wsjtx/reporting/UDP server is same as cqrlog preferences/fldigi/wsjt interface/wsjt port ans IP addresses 127.0.0.1 at both programs and at least "Accept UDP requests" is checked at wsjt-x settings (you can set all three checkboxes there).
It should work:
- set wsjt remote on at cqrlog
- set "F2/Reporting/prompt me to log qso" at wsjt-x
- If you can not see CQ-monitor https://www.cqrlog.com/node/3014
- at NewQSO you should see that remote is on as the "call" filed gets new name and will change color time to time when remote is active and connected
- when you start qso by double click from CQmonitor NewQS is filled with HamQTH/QTZ data (if you have st it at preferences)
- when you press OK at wsjtx log window NewQSO is cleared and your qso is logged and can be seen at top of new qso (if you have allowed to view recent qsos there).
-with latest versions (from source) you are able to use multicast IP addresses and so can have several programs listening from same wsjtx UDP datagrams.
Recommended reading:
New QSO/help/help index
--
Saku
OH1KH
HI Kin!
I have been working with N1MM <contactinfo> import so that cqrlog could really receive loggings from N1MM used during contest.
I have a version that needs just some fine tuning and testing.
How ever I do not have N1MM installed and no Windoze. I have heard it runs under wine somehow.
What I need is "true life" blocks of <contactinfo> .. </contactinfo> like you have in your message here.
The interesting thing is how N1MM sends contest messages if there are them in addition with serial numbers.
They are "STX_STRING" and "SRX_STRING" in adif format, but how they appear in <contactinfo>? There is a node called <exchange1></exchange1> but does it have both sent and received strings?
This is not explained properly in document I found https://n1mmwp.hamdocs.com/appendices/external-udp-broadcasts/
Can you produce similar dump as in your message from qsos where you have variations:
W1AW 599 001 AB 599 123 DC
W1AW 599 AB 599 123
W1AW 599 001 599 DC
Where 001 and 123 are contest serial numbers sent and received and AB and DC are contest messages
That would help to test this.
--
Saku
OH1KH
HI Kin!
I have been working with N1MM <contactinfo> import so that cqrlog could really receive loggings from N1MM used during contest.
I have a version that needs just some fine tuning and testing.
How ever I do not have N1MM installed and no Windoze. I have heard it runs under wine somehow.
What I need is "true life" blocks of <contactinfo> .. </contactinfo> like you have in your message here.
The interesting thing is how N1MM sends contest messages if there are them in addition with serial numbers.
They are "STX_STRING" and "SRX_STRING" in adif format, but how they appear in <contactinfo>? There is a node called <exchange1></exchange1> but does it have both sent and received strings?
This is not explained properly in document I found https://n1mmwp.hamdocs.com/appendices/external-udp-broadcasts/
Can you produce similar dump as in your message from qsos where you have variations:
W1AW 599 001 AB 599 123 DC
W1AW 599 AB 599 123
W1AW 599 001 599 DC
Where 001 and 123 are contest serial numbers sent and received and AB and DC are contest messages
That would help to test this.
--
Saku
OH1KH