Date   
locked Re: New Version

Tom - N1MM
 

Version 1.0.7174 (May 15, 2018)
GA QSO: Change county abbreviation OCNE back to OCON. (KU8E) (Coded by K3CT)
Volta RTTY: 0 points were given for USA Same call area qso's. This has been corrected. (Coded by N2AMG)
QSO Party: Update section field after a QSO edit. (several) (Coded by N1MM)
MD QSO Party: QSO party end time change. (K3MAW) (Coded by K3CT)

Fresh Install

Joe WB9SBD
 
Edited

I know when you remove programs, a lot of times stuff gets left behind.
So then when doing a new install, it really is not totally like the "First Time".

So when after removing N1MM+ what may be left behind I should remove to make a "Install" as close as possible to a never installed before installation?

I finally got my club willing to try N1MM+ at Field day, after hearing from so many of them how complicated N1MM+ is, I told them it is ONLY as complicated as you want it to be and showed them this.


OK People that say N1MM+ is too complicated.
Is this too complicated?

You type in the left window the stations call,,
Class in the class window,,
section in the section window,,
if all is good hit enter and it's in the log. Done, Next contact please?
Is that hard and too complicated?

So tyhey admit they were mis informed. But now people are confused on the install process.

So I want to make a step by step video of a brand new install.

Hence the need to make it as close to a never been installed before as possible.

So after un installing it, what may be still hanging around?

Joe WB9SBD
--

The Original Rolling Ball Clock
Idle Tyme
Idle-Tyme.com
http://www.idle-tyme.com

Re: Fresh Install

Jan
 
Edited

I use advanced uninstaller and after unintall I use Ccleaner

73

Jan

PA4JJ


Op 15.mei.2018 om 16:37 schreef Joe WB9SBD:
I know when you remove programs, a lot of times stuff gets left behind.
So then when doing a new install, it really is not totally like the "First Time".

So when after removing N1MM+ what may be left behind I should remove to make a "Install" as close as possible to a never installed before installation?

I finally got my club willing to try N1MM+ at Field day, after hearing from so many of them how complicated N1MM+ is, I told them it is ONLY as complicated as you want it to be and showed them this.


OK People that say N1MM+ is too complicated.
Is this too complicated?

You type in the left window the stations call,,
Class in the class window,,
section in the section window,,
if all is good hit enter and it's in the log. Done, Next contact please?
Is that hard and too complicated?

So tyhey admit they were mis informed. But now people are confused on the install process.

So I want to make a step by step video of a brand new install.

Hence the need to make it as close to a never been installed before as possible.

So after un installing it, what may be still hanging around?

Joe WB9SBD
--

The Original Rolling Ball Clock
Idle Tyme
Idle-Tyme.com
http://www.idle-tyme.com


-- 
____________________________________________________
my dxspider clusters running on a raspberry pi:  
pa4jj-2 83.162.186.242 port 7300
pa4jj-3 83.162.186.242 port 7388

RTTY Roundup full results article posted

jeff stai wk6i
 

Here's the direct link. If it stops working it means a corrected version has been posted so just navigate there normally.


bon appetit! 73 jeff wk6i

--
RTTY op at W7RN

Re: MORTTY Working

Skip
 

Good practice is to begin your transmission with {TX}{ENTER} and end it with a single space before the {RX}.  This puts your transmission at the beginning of a new line, and separates the end of it from the noise he will print at your {RX}.  Multiple line feeds are a real PITA for those receiving on a window that scrolls up [or down] as he then needs to chase your call and maybe exchange with the mouse.

73,

Fred ["Skip"] K6DGW
Sparks NV DM09dn
Washoe County

On 5/14/2018 8:00 PM, Jim W7RY wrote:
Got one of my MORTTYs working. Seems to work fine.. I have not tried it on the air yet.
 
So.... Do I simply put the transmit command [ into the macro? Then put the receive command in at the end ] ?
 
There is little info out there on actually USING the Tiny FSK. As lease by using an internet search engine.... No into on the N1MM help either that specifically addresses the Tiny FSK that I could fine.
 
Anyone have any links?
 
Thanks
73
Jim W7RY

Re: MORTTY Working

Jim W7RY
 

Thanks Max...
 
Did all of that.. I still have to put the transmit command [ into the macro. And the receive command ] at the end of the macros instead of the {TX} and {RX} commands to make them work with Tiny FSK.
 
Nothing in the setup saying this at least that I can find.
 
My TX and RX buttons work fine.
 
Thanks all
73
Jim W7RY


 

From: Max NG7M
Sent: Monday, May 14, 2018 11:32 PM
Subject: Re: [N1MMLoggerPlus] MORTTY Working
 
Hi Jim, here is the link to the N1MM+ docs for TinyFSK:

http://n1mm.hamdocs.com/tiki-index.php?page=Digital+-+External+TNC+Support#TinyFSK_by_Andy_Flowers_K0SM

Max NG7M

Re: MORTTY Working

ve3ki
 

Following the instructions in the manual at
<http://n1mm.hamdocs.com/tiki-index.php?page=Digital+-+External+TNC+Support&structure=N1MM+Logger+Documentation#In_the_Digital_Interface_DI_> : Open the DI Setup window, choose the Message Setup tab, select the "Other, TinyFSK" Message Set, click on the TX button at the right and  program a [ character followed by the {ENTER} macro into the Message Text for the TX button and then click on the "Save" button in the blue area. Next, click on the RX button at the right and program a ] character followed by the {ENTER} macro into the Message Text and press "Save". Click on the ESC button at the right and program a \ character into the Message Text and press "Save". When you have done all three, click on the "Save Settings" button to save the changes and exit the DI Setup window. Close the DI window and reopen it. After you have done that, you can check to make sure your changes have taken effect by opening the DI Setup window, "Messages" tab, "Other, TinyFSK" message set and checking that the expected contents are still programmed into those three buttons. Once you have done that,  the {TX} and {RX} macros ought to work in your regular message buttons.

73,
Rich VE3KI


On Tue, May 15, 2018 at 07:27 pm, Jim W7RY wrote:
Thanks Max...
 
Did all of that.. I still have to put the transmit command [ into the macro. And the receive command ] at the end of the macros instead of the {TX} and {RX} commands to make them work with Tiny FSK.
 
Nothing in the setup saying this at least that I can find.
 
My TX and RX buttons work fine.
 
Thanks all
73
Jim W7RY


 
From: Max NG7M
Sent: Monday, May 14, 2018 11:32 PM
Subject: Re: [N1MMLoggerPlus] MORTTY Working
 
Hi Jim, here is the link to the N1MM+ docs for TinyFSK:

http://n1mm.hamdocs.com/tiki-index.php?page=Digital+-+External+TNC+Support#TinyFSK_by_Andy_Flowers_K0SM

Max NG7M

Re: MORTTY Working

Jim W7RY
 

Yup! You are correct... I forgot to put the {TX} and {RX} commands back in... I just did some testing and it does work.
 
Sorry for the fire drill...
 
 
 
Thanks
73
Jim W7RY


 

From: ve3ki
Sent: Tuesday, May 15, 2018 10:18 PM
Subject: Re: [N1MMLoggerPlus] MORTTY Working
 
Following the instructions in the manual at
<http://n1mm.hamdocs.com/tiki-index.php?page=Digital+-+External+TNC+Support&structure=N1MM+Logger+Documentation#In_the_Digital_Interface_DI_> : Open the DI Setup window, choose the Message Setup tab, select the "Other, TinyFSK" Message Set, click on the TX button at the right and  program a [ character followed by the {ENTER} macro into the Message Text for the TX button and then click on the "Save" button in the blue area. Next, click on the RX button at the right and program a ] character followed by the {ENTER} macro into the Message Text and press "Save". Click on the ESC button at the right and program a \ character into the Message Text and press "Save". When you have done all three, click on the "Save Settings" button to save the changes and exit the DI Setup window. Close the DI window and reopen it. After you have done that, you can check to make sure your changes have taken effect by opening the DI Setup window, "Messages" tab, "Other, TinyFSK" message set and checking that the expected contents are still programmed into those three buttons. Once you have done that,  the {TX} and {RX} macros ought to work in your regular message buttons.

73,
Rich VE3KI


On Tue, May 15, 2018 at 07:27 pm, Jim W7RY wrote:
Thanks Max...
 
Did all of that.. I still have to put the transmit command [ into the macro. And the receive command ] at the end of the macros instead of the {TX} and {RX} commands to make them work with Tiny FSK.
 
Nothing in the setup saying this at least that I can find.
 
My TX and RX buttons work fine.
 
Thanks all
73
Jim W7RY


 
From: Max NG7M
Sent: Monday, May 14, 2018 11:32 PM
Subject: Re: [N1MMLoggerPlus] MORTTY Working
 
Hi Jim, here is the link to the N1MM+ docs for TinyFSK:

http://n1mm.hamdocs.com/tiki-index.php?page=Digital+-+External+TNC+Support#TinyFSK_by_Andy_Flowers_K0SM

Max NG7M

Re: MORTTY Working

Jim W7RY
 

I removed the [{ENTER} from the transmit button...
 
I already have {enter} in my macros for proper formatting of my buffers. This isn't my first RTTY contesting rodeo...
 
So really the transmit function should only have the [ in it because folks SHOULD already have the proper carriage return/line feeds in their macros. That is my opinion. But to each their own.
 
 
 
 
Thanks
73
Jim W7RY


 

From: ve3ki
Sent: Tuesday, May 15, 2018 10:18 PM
Subject: Re: [N1MMLoggerPlus] MORTTY Working
 
Following the instructions in the manual at
<http://n1mm.hamdocs.com/tiki-index.php?page=Digital+-+External+TNC+Support&structure=N1MM+Logger+Documentation#In_the_Digital_Interface_DI_> : Open the DI Setup window, choose the Message Setup tab, select the "Other, TinyFSK" Message Set, click on the TX button at the right and  program a [ character followed by the {ENTER} macro into the Message Text for the TX button and then click on the "Save" button in the blue area. Next, click on the RX button at the right and program a ] character followed by the {ENTER} macro into the Message Text and press "Save". Click on the ESC button at the right and program a \ character into the Message Text and press "Save". When you have done all three, click on the "Save Settings" button to save the changes and exit the DI Setup window. Close the DI window and reopen it. After you have done that, you can check to make sure your changes have taken effect by opening the DI Setup window, "Messages" tab, "Other, TinyFSK" message set and checking that the expected contents are still programmed into those three buttons. Once you have done that,  the {TX} and {RX} macros ought to work in your regular message buttons.

73,
Rich VE3KI


On Tue, May 15, 2018 at 07:27 pm, Jim W7RY wrote:
Thanks Max...
 
Did all of that.. I still have to put the transmit command [ into the macro. And the receive command ] at the end of the macros instead of the {TX} and {RX} commands to make them work with Tiny FSK.
 
Nothing in the setup saying this at least that I can find.
 
My TX and RX buttons work fine.
 
Thanks all
73
Jim W7RY


 
From: Max NG7M
Sent: Monday, May 14, 2018 11:32 PM
Subject: Re: [N1MMLoggerPlus] MORTTY Working
 
Hi Jim, here is the link to the N1MM+ docs for TinyFSK:

http://n1mm.hamdocs.com/tiki-index.php?page=Digital+-+External+TNC+Support#TinyFSK_by_Andy_Flowers_K0SM

Max NG7M

Re: MORTTY Working

Max NG7M
 

Hi Jim, that is correct.  In the macros, you always designate {tx} and {rx}.  This is 'abstract' to the device you are using.  For example if you have MMTTY setup, N1MM knows how to tell MMTTY to switch between transmit and receive and the same holds true for other RTTY devices / modems like what TinyFSK will appear to be when setup with 2Tone etc...  typically, I don't believe you would ever need to put anything special in the macros., but {tx} and {rx} will always be required so N1MM can take care of sending the tx / rx to the software you have told N1MM to use.

Sounds like you got it all setup and working.  Nice!

I just built a MORTTY tonight for a friend and will building 3 more this week.  Very slick design and compact.  I'm sold... :)  The price can't be beat either.

Max NG7M

Max NG7M

Re: Fresh Install

John Bednar
 
Edited

Joe,

 

There are files that are not deleted. *ini, databases, etc. Simply navigate to the N1MM Logger+ directory.

This is why we tell users to rename the user N1MM Logger+ directory when the big hammer is pulled out of the toolbox.

 

John, K3CT

 

From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of Joe WB9SBD
Sent: Tuesday, May 15, 2018 10:38 AM
To: N1MMLoggerPlus@groups.io
Subject: [N1MMLoggerPlus] Fresh Install

 

I know when you remove programs, a lot of times stuff gets left behind.
So then when doing a new install, it really is not totally like the "First Time".

So when after removing N1MM+ what may be left behind I should remove to make a "Install" as close as possible to a never installed before installation?

I finally got my club willing to try N1MM+ at Field day, after hearing from so many of them how complicated N1MM+ is, I told them it is ONLY as complicated as you want it to be and showed them this.


OK People that say N1MM+ is too complicated.
Is this too complicated?

You type in the left window the stations call,,
Class in the class window,,
section in the section window,,
if all is good hit enter and it's in the log. Done, Next contact please?
Is that hard and too complicated?

So tyhey admit they were mis informed. But now people are confused on the install process.

So I want to make a step by step video of a brand new install.

Hence the need to make it as close to a never been installed before as possible.

So after un installing it, what may be still hanging around?

Joe WB9SBD

--

The Original Rolling Ball Clock
Idle Tyme
Idle-Tyme.com
http://www.idle-tyme.com

Re: Fresh Install

Gordon LaPoint
 
Edited

Joe,
     I recomend revo uninstaller.   It will sweep the registry and hard drive for leftovers and delete them, if you want.  I do lots of testing on software and need a fresh install to properly test, this does the job!  I use the free one.

See: https://www.revouninstaller.com/revo_uninstaller_free_download.html
Gordon - N1MGO
On 05/15/2018 10:37 AM, Joe WB9SBD wrote:
I know when you remove programs, a lot of times stuff gets left behind.
So then when doing a new install, it really is not totally like the "First Time".

So when after removing N1MM+ what may be left behind I should remove to make a "Install" as close as possible to a never installed before installation?

I finally got my club willing to try N1MM+ at Field day, after hearing from so many of them how complicated N1MM+ is, I told them it is ONLY as complicated as you want it to be and showed them this.


OK People that say N1MM+ is too complicated.
Is this too complicated?

You type in the left window the stations call,,
Class in the class window,,
section in the section window,,
if all is good hit enter and it's in the log. Done, Next contact please?
Is that hard and too complicated?

So tyhey admit they were mis informed. But now people are confused on the install process.

So I want to make a step by step video of a brand new install.

Hence the need to make it as close to a never been installed before as possible.

So after un installing it, what may be still hanging around?

Joe WB9SBD
--

The Original Rolling Ball Clock
Idle Tyme
Idle-Tyme.com
http://www.idle-tyme.com


-- 
Gordon - N1MGO

Re: MORTTY Working

Rick Ellison
 

Jim..

You need at least the [ in the tx macro or the Morrty will not key.

 

73 Rick N2AMG

 

From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of Jim W7RY
Sent: Tuesday, May 15, 2018 11:34 PM
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MMLoggerPlus] MORTTY Working

 

I removed the [{ENTER} from the transmit button...

 

I already have {enter} in my macros for proper formatting of my buffers. This isn't my first RTTY contesting rodeo...

 

So really the transmit function should only have the [ in it because folks SHOULD already have the proper carriage return/line feeds in their macros. That is my opinion. But to each their own.

 

 

 

 

Thanks
73
Jim W7RY

 

From: ve3ki

Sent: Tuesday, May 15, 2018 10:18 PM

Subject: Re: [N1MMLoggerPlus] MORTTY Working

 

Following the instructions in the manual at
<http://n1mm.hamdocs.com/tiki-index.php?page=Digital+-+External+TNC+Support&structure=N1MM+Logger+Documentation#In_the_Digital_Interface_DI_> : Open the DI Setup window, choose the Message Setup tab, select the "Other, TinyFSK" Message Set, click on the TX button at the right and  program a [ character followed by the {ENTER} macro into the Message Text for the TX button and then click on the "Save" button in the blue area. Next, click on the RX button at the right and program a ] character followed by the {ENTER} macro into the Message Text and press "Save". Click on the ESC button at the right and program a \ character into the Message Text and press "Save". When you have done all three, click on the "Save Settings" button to save the changes and exit the DI Setup window. Close the DI window and reopen it. After you have done that, you can check to make sure your changes have taken effect by opening the DI Setup window, "Messages" tab, "Other, TinyFSK" message set and checking that the expected contents are still programmed into those three buttons. Once you have done that,  the {TX} and {RX} macros ought to work in your regular message buttons.

73,
Rich VE3KI


On Tue, May 15, 2018 at 07:27 pm, Jim W7RY wrote:

Thanks Max...

 

Did all of that.. I still have to put the transmit command [ into the macro. And the receive command ] at the end of the macros instead of the {TX} and {RX} commands to make them work with Tiny FSK.

 

Nothing in the setup saying this at least that I can find.

 

My TX and RX buttons work fine.

 

Thanks all
73
Jim W7RY

 

From: Max NG7M

Sent: Monday, May 14, 2018 11:32 PM

Subject: Re: [N1MMLoggerPlus] MORTTY Working

 

Re: MORTTY Working

Rick Ellison
 

In the docs on the website it shows that you do actually have to enter some things for the TX,RX, and ESC routines so the program knows what to send to the Tiny. You do not need to setup the Tiny where you have to use 2-Tone only  the program talks directly to the Tiny so that part is no longer needed.

 

73 Rick N2AMG

 

From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of Max NG7M
Sent: Tuesday, May 15, 2018 11:49 PM
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MMLoggerPlus] MORTTY Working

 

Hi Jim, that is correct.  In the macros, you always designate {tx} and {rx}.  This is 'abstract' to the device you are using.  For example if you have MMTTY setup, N1MM knows how to tell MMTTY to switch between transmit and receive and the same holds true for other RTTY devices / modems like what TinyFSK will appear to be when setup with 2Tone etc...  typically, I don't believe you would ever need to put anything special in the macros., but {tx} and {rx} will always be required so N1MM can take care of sending the tx / rx to the software you have told N1MM to use.

Sounds like you got it all setup and working.  Nice!

I just built a MORTTY tonight for a friend and will building 3 more this week.  Very slick design and compact.  I'm sold... :)  The price can't be beat either.

Max NG7M

Max NG7M

ADIF import problem

ha4fb
 

Hi
When I import QSO from WSJT-x (VHF log) ADIF file, the bearing and the distance is empty.

73 yuri - Ha4Fb.

Re: ADIF import problem

Jan
 

Hi Yuri
Why import these qso's?
They are logged into Logger automatic using the UDP port
See the help
73
Jan
PA4JJ

Op 17.mei.2018 om 10:42 schreef ha4fb@...:
Hi
When I import QSO from WSJT-x (VHF log) ADIF file, the bearing and the distance is empty.

73 yuri - Ha4Fb.

-- 
____________________________________________________
my dxspider clusters running on a raspberry pi:  
pa4jj-2 83.162.186.242 port 7300
pa4jj-3 83.162.186.242 port 7388

Re: ADIF import problem

Larry K8UT
 

Yuri,

Bearing and Distance information is not stored, but derived from the Prefix (country) or GridSquare information.

Perform your ADIF import (to which contest type in N1MM?). Select a contact in the Log Window. Right-click on that record, >Edit Contact. Check the Grid field. Is the GridSquare information available?

-larry (K8UT)

------ Original Message ------
From: ha4fb@...
Sent: 2018-05-17 04:42:20
Subject: [N1MMLoggerPlus] ADIF import problem

Hi
When I import QSO from WSJT-x (VHF log) ADIF file, the bearing and the distance is empty.

73 yuri - Ha4Fb.

Re: ADIF import problem

ha4fb
 

Hello Larry.
Tank you for the ansver.

Yes, in the grid square is it the locator (imported from the WSJT-X adif file).
If I write the qso data with the grid to the log no problem, just if I imort from the adif file
I attach a picture with some imported QSO. The top 2 qso is not imported. i wrote to the log.

Yuri - Ha4Fb.
 
-------- Eredeti levél --------
Feladó: Larry K8UT < k8ut@... (Link -> mailto:k8ut@...) >
Dátum: 2018 május 17 09:45:35
Tárgy: Re: [N1MMLoggerPlus] ADIF import problem
Címzett: N1MMLoggerPlus@groups.io (Link -> mailto:N1MMLoggerPlus@groups.io)
 
 
Yuri,
 
Bearing and Distance information is not stored, but derived from the Prefix (country) or GridSquare information.
 
Perform your ADIF import (to which contest type in N1MM?). Select a contact in the Log Window. Right-click on that record, >Edit Contact. Check the Grid field. Is the GridSquare information available?
 
-larry (K8UT)
 

------ Original Message ------
From: ha4fb@... (Link -> mailto:ha4fb@...)
To: N1MMLoggerPlus@groups.io (Link -> mailto:N1MMLoggerPlus@groups.io)
Sent: 2018-05-17 04:42:20
Subject: [N1MMLoggerPlus] ADIF import problem
 
Hi
When I import QSO from WSJT-x (VHF log) ADIF file, the bearing and the distance is empty.
73 yuri - Ha4Fb.
_._,_._,_
Groups.io Links:
You receive all messages sent to this group.
New Topic (Link -> https://groups.io/g/N1MMLoggerPlus/post)
Change Your Subscription (Link -> https://groups.io/g/N1MMLoggerPlus/editsub/1025516)
Group Home (Link -> https://groups.io/g/N1MMLoggerPlus)
Contact Group Owner (Link -> mailto:N1MMLoggerPlus+owner@groups.io)
Terms Of Service (Link -> https://groups.io/static/tos)
Unsubscribe From This Group (Link -> https://groups.io/g/N1MMLoggerPlus/leave/defanged)
_._,_._,_

Re: ADIF import problem

ha4fb
 

Hello Jan.

Thank you for the answer.

I setup the UDP settings in the WSJT-X to 127.0.0.1 and 2233 port (see attached picture 1.jpg)

In the N1MM+ also set the same port and IP ( see the picture 2.jpg)

After this settings the QSO not imported from the WSJT-X.

The setup information from the N1mm+ doc: 3.jpg

Can you help me, what is the problem? How can setup for the normal work?

Yuri - Ha4Fb.

-------- Eredeti levél --------
Feladó: Jan < pa4jj@... (Link -> mailto:pa4jj@...) >
Dátum: 2018 május 17 09:08:53
Tárgy: Re: [N1MMLoggerPlus] ADIF import problem
Címzett: N1MMLoggerPlus@groups.io (Link -> mailto:N1MMLoggerPlus@groups.io)
Hi Yuri
Why import these qso's?
They are logged into Logger automatic using the UDP port
See the help
73
Jan
PA4JJ
Op 17.mei.2018 om 10:42 schreef
ha4fb@... (Link -> mailto:ha4fb@...) :
Hi
When I import QSO from WSJT-x (VHF log) ADIF file, the bearing and
the distance is empty.
73 yuri - Ha4Fb.
--
____________________________________________________
my dxspider clusters running on a raspberry pi:
pa4jj-2 83.162.186.242 port 7300
pa4jj-3 83.162.186.242 port 7388
_._,_._,_
Groups.io Links:
You receive all messages sent to this group.
View/Reply Online (#35096) (Link -> https://groups.io/g/N1MMLoggerPlus/message/35096) |
Reply To Group (Link -> mailto:N1MMLoggerPlus@groups.io?subject=Re:%20Re%3A%20%5BN1MMLoggerPlus%5D%20ADIF%20import%20problem)
| Reply To Sender (Link -> mailto:pa4jj@...?subject=Private:%20Re:%20Re%3A%20%5BN1MMLoggerPlus%5D%20ADIF%20import%20problem)
|
Mute This Topic (Link -> https://groups.io/mt/19276634/1025516)
| New Topic (Link -> https://groups.io/g/N1MMLoggerPlus/post)
Change Your Subscription (Link -> https://groups.io/g/N1MMLoggerPlus/editsub/1025516)
Group Home (Link -> https://groups.io/g/N1MMLoggerPlus)
Contact Group Owner (Link -> mailto:N1MMLoggerPlus+owner@groups.io)
Terms Of Service (Link -> https://groups.io/static/tos)
Unsubscribe From This Group (Link -> https://groups.io/g/N1MMLoggerPlus/leave/defanged)
_._,_._,_

Re: ADIF import problem

Jan
 

Hello Yuri

Sorry but I thougt your mail was going about Logger32. Now I see it is about N1MM+
I don't know how to do this in N1MM+

73
Jan
PA4JJ

Op 17.mei.2018 om 17:21 schreef ha4fb:
Hello Jan.

Thank you for the answer.

I setup the UDP settings in the WSJT-X to 127.0.0.1 and 2233 port (see attached picture 1.jpg)

In the N1MM+ also set the same port and IP ( see the picture 2.jpg)

After this settings the QSO not imported from the WSJT-X.

The setup information from the N1mm+ doc: 3.jpg

Can you help me, what is the problem? How can setup for the normal work?

Yuri - Ha4Fb.

-------- Eredeti levél --------
Feladó: Jan < pa4jj@... (Link -> mailto:pa4jj@...) >
Dátum: 2018 május 17 09:08:53
Tárgy: Re: [N1MMLoggerPlus] ADIF import problem
Címzett: N1MMLoggerPlus@groups.io (Link -> mailto:N1MMLoggerPlus@groups.io)
Hi Yuri
Why import these qso's?
They are logged into Logger automatic using the UDP port
See the help
73
Jan
PA4JJ
Op 17.mei.2018 om 10:42 schreef
ha4fb@... (Link -> mailto:ha4fb@...) :
Hi
When I import QSO from WSJT-x (VHF log) ADIF file, the bearing and
the distance is empty.
73 yuri - Ha4Fb.
--
____________________________________________________
my dxspider clusters running on a raspberry pi:
pa4jj-2 83.162.186.242 port 7300
pa4jj-3 83.162.186.242 port 7388

-- 
____________________________________________________
my dxspider clusters running on a raspberry pi:  
pa4jj-2 83.162.186.242 port 7300
pa4jj-3 83.162.186.242 port 7388