Date   
Re: RTTY: Which Sideband?

WA8Y Steven
 

WinWarbler uses same engines; 2Tone and MTTY.
STEVE WA8Y 

On Wed, Jan 2, 2019, 1:58 PM Jamie WW3S <ww3s@... wrote:

if you are using N1MM, just use MMTTY as the engine.....thats what Winwarbler uses .....
----- Original Message -----
From: "Dave AA6YQ" <aa6yq@...>
To: DXLab@groups.io
Sent: Wednesday, January 2, 2019 1:48:00 PM
Subject: Re: [DXLab] RTTY: Which Sideband?

+ AA6YQ comments below

N1MM Logger has had the same capability as WinWarbler for essentially the same time period. Look in the N1MM+ documentation for the AutoTRXUpdate option in the Digital Interface window. This option works regardless of which digital engine you use in N1MM+. If you can do this correctly with fldigi, you can do the same with MMTTY (which is the digital engine WinWarbler uses for RTTY).

+ Rick N2AMG and I collaborated on learning how to integrate the MMTTY engine into N1MM and WinWarbler, so it would be surprising if N1MM weren't similarly capable of correctly spotting Mark frequencies.

       73,

             Dave, AA6YQ


                + WinWarbler has been correctly spotting a RTTY signal's Mark frequency -- whether operating AFSK or FSK -- for the past 18 years.

        That's good to know. Unfortunately I don't think WinWarbler is an available RTTY engine for N1MM. If it were I would change from using fldigi.








Re: Spot Collector Age Of Spots

jean-pierre jpl
 

Dave,
Thank you for this very quick answer
I just tested with the comma and it works fine
I'm sorry I didn't try that earlier.
73
Jean-Pierre ON5JT

Re: Ci-V collisions in Commander

Dave AA6YQ
 

+ AA6YQ comments below

No Hardware adds or changes. latest Win10 update installed. nothing else changed as far as I know

+ What make and model transceiver are you using?

+ Do you have anything connected to your CI-V bus besides your computer and your transceiver?

+ In the Radio panel on the Configuration window's General tab, to what is the "Command interval" set?

73,

Dave, AA6YQ

Re: Ci-V collisions in Commander

Dave AA6YQ
 

+ AA6YQ comments below

Since you are the developer of Commander, I suspect that much of your experience is based on that application suite. I have used many different software packages over the years and not all control the rig, some are just reading data from it via a COM port. And maybe as you said they were defective? So I suspect over the years I have just gotten into the habit of setting device manager as well as all other software and hardware com port settings to be the same baud rate. That certainly can't be bad thing, I wouldn't think.

+ It's harmless, but unnecessary.

73,

Dave, AA6YQ

Re: ARRL RTTY Roundup with FT8

D. Scott MacKenzie
 

I am trying to download the latest version of JT Alerts, and the webpage is slow and down loads is not occurring.  Is there a mirror available?

 

D. Scott MacKenzie, PhD

 

From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of neil_zampella
Sent: Friday, January 04, 2019 4:17 PM
To: DXLab@groups.io
Subject: Re: [DXLab] ARRL RTTY Roundup with FT8

 

[Edited Message Follows]

Ah .. not having v2.12.8 and the WSJT-X 2.0 final explains things then ... I'll be testing the setup tonight.to see how it goes.    I'm usually ahead of the game when it comes to software updates :)

 

Neil

Re: Ci-V collisions in Commander

Michael Ernst
 

Dave AA6YQ,

Since you are the developer of Commander, I suspect that much of your experience is based on that application suite. I have used many different software packages over the years and not all control the rig, some are just reading data from it via a COM port. And maybe as you said they were defective? So I suspect over the years I have just gotten into the habit of setting device manager as well as all other software and hardware com port settings to be the same baud rate. That certainly can’t be bad thing, I wouldn't think. And then over time convinced myself that they had to be the same in all situations (I am 68 years old and a little forgetful occasionally, hi).

I already previously stated in another email that I was incorrect in the case where the software performing rig control did override the windows device settings.

Thanks and 73,
Mike, AE8U

-----Original Message-----
From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Dave AA6YQ
Sent: Friday, January 4, 2019 3:59 PM
To: DXLab@groups.io
Subject: Re: [DXLab] Ci-V collisions in Commander

What Stan N1ZX reported is that Commander's CI-V light is illuminating, revealing the presence of collisions.

Stan did not say that Commander could no longer control his radio, so the debate about baud rates is not relevant to his report.

In the ~25 years that I have been developing Windows applications that control transceivers via serial ports, I have never once changed the baud rate via the Windows Device Properties tab. It is only necessary to change the baud rate in the transceiver, and in Commander.

Perhaps it's possible to develop a transceiver control application that depends on the Windows Device Properties tab being configured with the desired baud rate; if so, I would consider such an application to be defective.

73,

Dave, AA6YQ



-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Michael Ernst
Sent: Friday, January 04, 2019 1:51 PM
To: DXLab@groups.io
Subject: Re: [DXLab] Ci-V collisions in Commander

Bill G4WJS,

I am almost certain that what I stated is correct, but I will test to verify and let you know.

73,
Mike, AE8U



Sent from my T-Mobile 4G LTE Device

-------- Original message --------
From: g4wjs <bill.8@...>
Date: 1/4/19 13:34 (GMT-05:00)
To: DXLab@groups.io
Subject: Re: [DXLab] Ci-V collisions in Commander

On 04/01/2019 18:27, Michael Ernst wrote:
I believe that is not correct.
Mike,

your belief is incorrect. All that is required is the serial port parameters in the application must be compatible with those the device being controlled (e.g. a CAT controlled rig via a real or virtual serial port), including the baud rate. The default parameters set in the COM port device properties are not relevant as they are overridden by the application when it opens the port.

I have never had to change the device properties in any Windows version for a COM port, whatever baud rate or other COM port configurations parameter were required by a serial device connected to it.

73
Bill
G4WJS.



--
73

Bill

G4WJS.





<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> Virus-free. www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>

Re: ARRL RTTY Roundup with FT8

neil_zampella
 
Edited

Ah .. not having v2.12.8 and the WSJT-X 2.0 final explains things then ... I'll be testing the setup tonight.to see how it goes.    I'm usually ahead of the game when it comes to software updates :)

 

Neil

Re: Spot Collector Age Of Spots

Dave AA6YQ
 

+ AA6YQ comments below

I also wants to put .17 in the spot Life time windows, infortunately this windows do not accept the "." maybe because my keyboard is a Belgian Keybord.

+ If your locale specifies the use of , (comma) as the decimal separator, then specify ,17 as the spot lifetime.

73,

Dave,

Re: ARRL RTTY Roundup with FT8

Gilbert Baron W0MN
 

Perfect answer. Any other way is just asking for trouble.

 

Outlook Laptop Gil W0MN

Hierro Candente Batir de Repente

44.08226 N 92.51265 W EN34rb

 

From: DXLab@groups.io <DXLab@groups.io> On Behalf Of ND9G Mike
Sent: Friday, January 4, 2019 14:14
To: DXLab@groups.io
Subject: Re: [DXLab] ARRL RTTY Roundup with FT8

 

Does your WSJT-X log to DXKeeper, or are you using JT-Alert to do that logging?

 

If you insist on running them all and having them sync real time, I would use WSJT-X paired with N1MM+ for the logging of the contest, and let N1MM+ pass things to DXKeeper via the bridge. If you pass from WSJT-X (JTAlert) to DXKeeper and to N1MM+, which then passes to DXKeeper, you'll likely end up with duplicate QSOs in your log of record.

 

What I personally do, is log all of my contest stuff in N1MM+ and not use any application bridging to DXKeeper during the contest. I don't need the extra layer of potential issues during a contest.  At the end of the contest, I export an d ADIF file from N1MM and import into DXKeeper. Doing it this way, gets everything from the contest into DXKeeper within a few minutes of the end of a contest, and gives me a very quick report of what QSOs I made that advanced any of my award progress.

 

73,

Mike ND9G

 

 

On Fri, Jan 4, 2019 at 2:06 PM neil_zampella <neilz@...> wrote:

OK .. I'm not a contester per se, but I would like to be able to use DXK as my 'log of record'.   WSJT-X will pass through normal QSO data, but I'm not sure what it passes otherwise.  Should I just use the N1MM+ contest logger, and the N1MM+ Gateway app, or just let WSJT-X log the responses but then I believe I lose the contest data.

Thanks in advance.

Neil, KN3ILZ


--

W0MN EN34rb 44.08226 N 92.51265 W

Hierro candente, batir de repente

HP Laptop

Re: INSTALLATION PROBLEM

Dave AA6YQ
 

+ AA6YQ comments below

This was sent, Dave.

+ I received your answers and screen shots yesterday, thanks, and sent you an email message in response.

73,

Dave, AA6YQ

Re: ARRL RTTY Roundup with FT8

Dave AA6YQ
 

+ AA6YQ comments below

Does your WSJT-X log to DXKeeper, or are you using JT-Alert to do that logging?

+ JTAlert must be running in order for WSJTX to log QSOs to DXKeeper.

If you insist on running them all and having them sync real time, I would use WSJT-X paired with N1MM+ for the logging of the contest, and let N1MM+ pass things to DXKeeper via the bridge. If you pass from WSJT-X (JTAlert) to DXKeeper and to N1MM+, which then passes to DXKeeper, you'll likely end up with duplicate QSOs in your log of record.

What I personally do, is log all of my contest stuff in N1MM+ and not use any application bridging to DXKeeper during the contest. I don't need the extra layer of potential issues during a contest. At the end of the contest, I export an d ADIF file from N1MM and import into DXKeeper. Doing it this way, gets everything from the contest into DXKeeper within a few minutes of the end of a contest, and gives me a very quick report of what QSOs I made that advanced any of my award progress.

+ Sound logic, Mike, but be aware that if you're running SpotCollector to identify needed callsigns, they will continue to be displayed as needed after you work them.

73,

Dave, AA6YQ

Re: Ci-V collisions in Commander

Dave AA6YQ
 

What Stan N1ZX reported is that Commander's CI-V light is illuminating, revealing the presence of collisions.

Stan did not say that Commander could no longer control his radio, so the debate about baud rates is not relevant to his report.

In the ~25 years that I have been developing Windows applications that control transceivers via serial ports, I have never once changed the baud rate via the Windows Device Properties tab. It is only necessary to change the baud rate in the transceiver, and in Commander.

Perhaps it's possible to develop a transceiver control application that depends on the Windows Device Properties tab being configured with the desired baud rate; if so, I would consider such an application to be defective.

73,

Dave, AA6YQ

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Michael Ernst
Sent: Friday, January 04, 2019 1:51 PM
To: DXLab@groups.io
Subject: Re: [DXLab] Ci-V collisions in Commander

Bill G4WJS,

I am almost certain that what I stated is correct, but I will test to verify and let you know.

73,
Mike, AE8U



Sent from my T-Mobile 4G LTE Device

-------- Original message --------
From: g4wjs <bill.8@...>
Date: 1/4/19 13:34 (GMT-05:00)
To: DXLab@groups.io
Subject: Re: [DXLab] Ci-V collisions in Commander

On 04/01/2019 18:27, Michael Ernst wrote:
I believe that is not correct.
Mike,

your belief is incorrect. All that is required is the serial port parameters in the application must be compatible with those the device being controlled (e.g. a CAT controlled rig via a real or virtual serial port), including the baud rate. The default parameters set in the COM port device properties are not relevant as they are overridden by the application when it opens the port.

I have never had to change the device properties in any Windows version for a COM port, whatever baud rate or other COM port configurations parameter were required by a serial device connected to it.

73
Bill
G4WJS.



--
73

Bill

G4WJS.





<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> Virus-free. www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>

Re: ARRL RTTY Roundup with FT8

HamApps Support (VK3AMA)
 

On 5/01/2019 7:44 am, neil_zampella wrote:

Laurie,

are you sure?   During the FT8 Roundup last month, I used JT-Alert to log to DXK, but those data items were not recorded.    Maybe I need to have DXK setup in contest mode?

Neil

Yes, I'm sure. DXKeeper doesn't need to be in Contest mode.

If your tests were last month, than likely, you were using a version of JTAlert that didn't support logging of WSJT-X contest exchanges, as initially the WSJT-X rc releases didn't provide that data in the Logged QSO packet. JTAlert was extended to log the Contest exchanges only after they became available in the WSJT-X 2.0.0 GA release.

I suggest you try a test again with WSJT-X 2.0.0 GAl release and JTAlert 2.12.8 or higher (preferably the latest 2.12.10)

de Laurie VK3AMA

Re: Spot Collector Age Of Spots

jean-pierre jpl
 

Helllo Dave,

I also wants to put .17 in the spot Life time windows, infortunately this windows do not accept the "." maybe because my keyboard is a Belgian Keybord.

On the other hand I have no difficulty to set a point in another input window for example in the window "USER-defined Sequence after Band Change" where the point of the Belgian keyboard is well accepted.
Do you have any idea how to change this?

Thanks in advance
Jean-Pierre ON5JT

Re: INSTALLATION PROBLEM

Chip Swett
 

This was sent, Dave.

Re: ARRL RTTY Roundup with FT8

neil_zampella
 

Laurie,

are you sure?   During the FT8 Roundup last month, I used JT-Alert to log to DXK, but those data items were not recorded.    Maybe I need to have DXK setup in contest mode?

Neil

On 1/4/2019 3:23 PM, HamApps Support (VK3AMA) wrote:
On 5/01/2019 7:06 am, neil_zampella wrote:

OK .. I'm not a contester per se, but I would like to be able to use DXK as my 'log of record'.   WSJT-X will pass through normal QSO data, but I'm not sure what it passes otherwise.  Should I just use the N1MM+ contest logger, and the N1MM+ Gateway app, or just let WSJT-X log the responses but then I believe I lose the contest data.

Thanks in advance.

Neil, KN3ILZ

Easy, JTAlert (since 2.12.8) logs WSJT-X 2.0.0 contest exchanges to DXKeeper. The exchange data SRX_STRING & STX_STRING are recorded in the "rx info" and "tx info" fields of DXKeeper.

de Laurie VK3AMA
 


Virus-free. www.avg.com

Re: Ci-V collisions in Commander

Michael Ernst
 

Bill G4WJS,

 

You are absolutely correct. I went into Win10 device manager and changed the baud rate from 38,400 to 9600. I left both my rig and HRD v5 set at 38,400 baud. I then shut down and restarted Win10 and checked to make sure device manager still showed 9600 for the port. It did. I then fired up HRD and it immediately connected to my rig at 38,400.

 

So I guess what one needs to make sure of is that both the transceiver and software being used are both set to the same baud rate.

 

Thanks for teaching me something new!!! Sometimes IO am a bit stubborn – maybe I should be from, Missouri, the “Show me” state.

 

Thanks and 73,

Mike, AE8U

 

 

Bill G4WJS,

 

I am almost certain that what I stated is correct,  but I will test to verify and let you know. 

 

73,

Mike, AE8U 

 

 

 

Sent from my T-Mobile 4G LTE Device

 

-------- Original message --------

From: g4wjs <bill.8@...>

Date: 1/4/19 13:34 (GMT-05:00)

To: DXLab@groups.io

Subject: Re: [DXLab] Ci-V collisions in Commander

 

On 04/01/2019 18:27, Michael Ernst wrote:
> I believe that is not correct.

Mike,

your belief is incorrect. All that is required is the serial port
parameters in the application must be compatible with those the device
being controlled (e.g. a CAT controlled rig via a real or virtual serial
port), including the baud rate. The default parameters set in the COM
port device properties are not relevant as they are overridden by the
application when it opens the port.

I have never had to change the device properties in any Windows version
for a COM port, whatever baud rate or other COM port configurations
parameter were required by a serial device connected to it.

73
Bill
G4WJS.



--
73

Bill

G4WJS.


Re: ARRL RTTY Roundup with FT8

HamApps Support (VK3AMA)
 

On 5/01/2019 7:06 am, neil_zampella wrote:

OK .. I'm not a contester per se, but I would like to be able to use DXK as my 'log of record'.   WSJT-X will pass through normal QSO data, but I'm not sure what it passes otherwise.  Should I just use the N1MM+ contest logger, and the N1MM+ Gateway app, or just let WSJT-X log the responses but then I believe I lose the contest data.

Thanks in advance.

Neil, KN3ILZ

Easy, JTAlert (since 2.12.8) logs WSJT-X 2.0.0 contest exchanges to DXKeeper. The exchange data SRX_STRING & STX_STRING are recorded in the "rx info" and "tx info" fields of DXKeeper.

de Laurie VK3AMA
 

Re: ARRL RTTY Roundup with FT8

ND9G Mike
 

Does your WSJT-X log to DXKeeper, or are you using JT-Alert to do that logging?

If you insist on running them all and having them sync real time, I would use WSJT-X paired with N1MM+ for the logging of the contest, and let N1MM+ pass things to DXKeeper via the bridge. If you pass from WSJT-X (JTAlert) to DXKeeper and to N1MM+, which then passes to DXKeeper, you'll likely end up with duplicate QSOs in your log of record.

What I personally do, is log all of my contest stuff in N1MM+ and not use any application bridging to DXKeeper during the contest. I don't need the extra layer of potential issues during a contest.  At the end of the contest, I export an d ADIF file from N1MM and import into DXKeeper. Doing it this way, gets everything from the contest into DXKeeper within a few minutes of the end of a contest, and gives me a very quick report of what QSOs I made that advanced any of my award progress.

73,
Mike ND9G


On Fri, Jan 4, 2019 at 2:06 PM neil_zampella <neilz@...> wrote:

OK .. I'm not a contester per se, but I would like to be able to use DXK as my 'log of record'.   WSJT-X will pass through normal QSO data, but I'm not sure what it passes otherwise.  Should I just use the N1MM+ contest logger, and the N1MM+ Gateway app, or just let WSJT-X log the responses but then I believe I lose the contest data.

Thanks in advance.

Neil, KN3ILZ

ARRL RTTY Roundup with FT8

neil_zampella
 

OK .. I'm not a contester per se, but I would like to be able to use DXK as my 'log of record'.   WSJT-X will pass through normal QSO data, but I'm not sure what it passes otherwise.  Should I just use the N1MM+ contest logger, and the N1MM+ Gateway app, or just let WSJT-X log the responses but then I believe I lose the contest data.

Thanks in advance.

Neil, KN3ILZ