Date   
OTRSP + Flex 6600 stereo mode only one green light

Matt Murphy
 

Hello,

I am under the impression that in "stereo" mode both green lights are supposed to be lit, indicating that RX audio is coming from both radios. 

I am using N1MM+ Logger connected to a Flex 6600 transceiver, operating SO2R using full duplex mode.  

Everything seems to work exactly like it did with my  previous two K3 and YCCC box setup, except I seem to recall that in stereo mode both green lights would be lit.  This gave me a visual indicator of whether I was using stereo mode or not. 

I watched the OTRSP traffic being sent to the Flex virtual OTRSP controller, and indeed the correct message (RX1 transitions to RX2 for receive focus switch without stereo mode, and RX1S transitions to RX2S for receive focus switch when stereo mode is active).  However on N1MM+ there is always only one green light showing. It is the same one that would be showing if stereo mode were turned off. 

Any suggestions on how to debug this further?  I am not sure where the problem lies.  I do not have the YCCC box handy to perform a more thorough A/B test.  I will read the OTRSP protocol spec more carefully but would appreciate advice on how to proceed.  

73,
Matt NQ6N

N1MM and log window

Bill DeVore <maxrcul@...>
 

Every time I launch N1MM+ the log window opens also. Is there anyway to prevent the log from opening each time?

Re: OTRSP + Flex 6600 stereo mode only one green light

ve3ki
 

What green lights are you talking about? Do you mean the green dot that appears in the N1MM+ Entry windows? Only one of these shows at a time, because while it is sometimes called the "RX focus" indicator, what it really indicates is where keyboard input will be directed to - Entry Window 1 or Entry Window 2. It wouldn't make sense to direct keyboard input to both windows at once.

73,
Rich VE3KI


On Wed, Apr 4, 2018 at 05:43 am, Matt Murphy wrote:
Hello,
 
I am under the impression that in "stereo" mode both green lights are supposed to be lit, indicating that RX audio is coming from both radios. 
 
I am using N1MM+ Logger connected to a Flex 6600 transceiver, operating SO2R using full duplex mode.  
 
Everything seems to work exactly like it did with my  previous two K3 and YCCC box setup, except I seem to recall that in stereo mode both green lights would be lit.  This gave me a visual indicator of whether I was using stereo mode or not. 
 
I watched the OTRSP traffic being sent to the Flex virtual OTRSP controller, and indeed the correct message (RX1 transitions to RX2 for receive focus switch without stereo mode, and RX1S transitions to RX2S for receive focus switch when stereo mode is active).  However on N1MM+ there is always only one green light showing. It is the same one that would be showing if stereo mode were turned off. 
 
Any suggestions on how to debug this further?  I am not sure where the problem lies.  I do not have the YCCC box handy to perform a more thorough A/B test.  I will read the OTRSP protocol spec more carefully but would appreciate advice on how to proceed.  
 
73,
Matt NQ6N

Re: N1MM and log window

ve3ki
 

If you close the Log window before shutting down the program, it will not open when you start the program next time. The windows that are open at the time the program shuts down (assuming a normal graceful shutdown) are the ones that will open when it is next restarted.

73,
Rich VE3KI


On Wed, Apr 4, 2018 at 11:03 am, Bill DeVore wrote:
Every time I launch N1MM+ the log window opens also. Is there anyway to prevent the log from opening each time?

Re: N1MM and log window

Larry K8UT
 

>Is there anyway to prevent the log from opening each time?
No.  The open/close attribute of other windows is remembered, but not the log's.

There are too many instances of people launching N1MM thinking they are in contest ABC and then after logging some Qs realize they are in contest XYZ. We intentionally force-open the log widow to discourage such mistakes.

-larry (K8UT)

------ Original Message ------
From: "Bill DeVore" <maxrcul@...>
Sent: 2018-04-04 14:03:58
Subject: [N1MMLoggerPlus] N1MM and log window

Every time I launch N1MM+ the log window opens also. Is there anyway to prevent the log from opening each time?

Re: OTRSP + Flex 6600 stereo mode only one green light

Matt Murphy
 

Rich -- Ahh, yes I do mean the green dots on the N1MM entry windows.  I had assumed that the flashing cursor in the entry field and the white (vs gray) color of the field background was meant to convey which entry field/window was active.  But surely if the green dots are meant simply to be a more obvious indicator of keyboard input focus then there is not a bug happening.  

Thanks much for the tips. 

73,
Matt NQ6N



On Wed, Apr 4, 2018 at 1:08 PM, ve3ki <ve3iay@...> wrote:
What green lights are you talking about? Do you mean the green dot that appears in the N1MM+ Entry windows? Only one of these shows at a time, because while it is sometimes called the "RX focus" indicator, what it really indicates is where keyboard input will be directed to - Entry Window 1 or Entry Window 2. It wouldn't make sense to direct keyboard input to both windows at once.

73,
Rich VE3KI


On Wed, Apr 4, 2018 at 05:43 am, Matt Murphy wrote:
Hello,
 
I am under the impression that in "stereo" mode both green lights are supposed to be lit, indicating that RX audio is coming from both radios. 
 
I am using N1MM+ Logger connected to a Flex 6600 transceiver, operating SO2R using full duplex mode.  
 
Everything seems to work exactly like it did with my  previous two K3 and YCCC box setup, except I seem to recall that in stereo mode both green lights would be lit.  This gave me a visual indicator of whether I was using stereo mode or not. 
 
I watched the OTRSP traffic being sent to the Flex virtual OTRSP controller, and indeed the correct message (RX1 transitions to RX2 for receive focus switch without stereo mode, and RX1S transitions to RX2S for receive focus switch when stereo mode is active).  However on N1MM+ there is always only one green light showing. It is the same one that would be showing if stereo mode were turned off. 
 
Any suggestions on how to debug this further?  I am not sure where the problem lies.  I do not have the YCCC box handy to perform a more thorough A/B test.  I will read the OTRSP protocol spec more carefully but would appreciate advice on how to proceed.  
 
73,
Matt NQ6N


Re: N1MM and log window

ve3ki
 

My mistake - I will add a note to that effect to the manual.

73,

Rich VE3KI


On Wed, Apr 4, 2018 at 11:35 am, Larry K8UT wrote:
>Is there anyway to prevent the log from opening each time?
No.  The open/close attribute of other windows is remembered, but not the log's.
 
There are too many instances of people launching N1MM thinking they are in contest ABC and then after logging some Qs realize they are in contest XYZ. We intentionally force-open the log widow to discourage such mistakes.
 
-larry (K8UT)
 
------ Original Message ------
From: "Bill DeVore" <maxrcul@...>
Sent: 2018-04-04 14:03:58
Subject: [N1MMLoggerPlus] N1MM and log window
 
Every time I launch N1MM+ the log window opens also. Is there anyway to prevent the log from opening each time?

Call history not workingMM0JOM

John MM0JOM
 

loaded version V1.0.7144.0. Used for UKEICC 80m CC tonight and call history data was not populating section data. Call sign would appear in the call history but the locator information was not picked up to populate entry field. Have used this call history file for about 2 years. Maybe a bug or maybe I have changed something
John
MM0JOM/GM3A

Re: Call history not workingMM0JOM

VE2FK
 

John
Just tested with latest N1MM+ version.
Using UKEI89_VHF UDC module and ukei80.txt Call History from N1MM files
and all is working ok here.

Claude VE2FK


Le 2018-04-04 à 17:21, Young Johnnie a écrit :

loaded version V1.0.7144.0. Used for UKEICC 80m CC tonight and call history data was not populating section data. Call sign would appear in the call history but the locator information was not picked up to populate entry field. Have used this call history file for about 2 years. Maybe a bug or maybe I have changed something
John
MM0JOM/GM3A

Aucun virus trouvé dans ce message.
Analyse effectuée par AVG - www.avg.fr
Version: 2016.0.7226 / Base de données virale: 4793/15540 - Date: 04/04/2018


Re: N1MM and log window

Bill DeVore <maxrcul@...>
 

Makes sense! At least now I know why it’s happening. Thanks!

Re: Yaesu FT3000 and SSB audio through the USB audio codec

John Bednar
 
Edited

George,

 

To play voice messages with the radio codec, you will need to enable (check mark) “PTT via Radio Command SSB Mode” in the COM port setup window for the radio.

 

The FT3000 has a Monitor function. You should be able to record voice messages with the radio codec. Turn On the radio Monitor and change Logger+ audio to record with the radio codec.

 

You should not need to use a footswitch.

 

It is not uncommon to learn that other programs corrupt the radio commands.

 

John, K3CT

 

From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of George Skoubis
Sent: Monday, April 02, 2018 7:38 PM
To: N1MMLoggerPlus@groups.io
Subject: [N1MMLoggerPlus] Yaesu FT3000 and SSB audio through the USB audio codec

 

Hi Everyone,

 

  I've been out of Ham Radio since 2006 since I moved across the country, started a new business and was busy while my kids were growing up.

 

  Now the youngest moved away for college (she did get her ham Tech license first) and I have more time for Ham Radio.

 

  I bought a Yaesu FT3000 and downloaded N1MM+ as I had tried the original N1MM back in the early 2000's with my TenTec Orion.

 

  I was successful in interfacing the radio with N1MM+ and can use the RTTY, CW and SSB modes.  

 

  There is one small item that I can't seem to get working correctly but I'm not sure if the problem is in the way I have the radio configured, N1MM+ configured, or if I just don't understand how it should work.

 

  If I try to transmit with N1MM+ configured to record audio through the USB sound card codec in the radio I don't get any audio.  I can get transmit audio by connecting the output of the sound card to the line in of the radio.  

 

  I can also record and play back messages through N1MM+ by using Control+Shift+F Key

 

My hardware:

 

Windows 10 PC Intel I7 Processor 3.6 ghz processor 16 gb memory

Behringer UMC202HD Soundcard (for Microphone)

Behringer UMC404HD Soundcard (for N8LP Panadapter)

N8LP Panadapter

 

Software:

Windows 10 Home 64 bit

N1MM+ Logger 1.0.7142.0

Win4Yaesu 1.070 64 Bit

MMTTY 1.68 FSK64

WSJXT

 

The radio is connected via USB to the computer.   The FT3000 USB silicon com ports are assigned to Com11 (enhanced) and Com10 (regular, which I use to key rig).

 

Since I am using Win4Yaesu I am using Com0Com to share a virtual serial port with N1MM+ (COM11 in Win4Yaesu gets sent to COM18 for N1MM+). CW Keying, RTTY Keying, and SSB messages are transmitted from N1MM+ when I press the function key or click on the button in N1MM+

 

 The N1MM+ Spectrum display shows the output of the N8LP panadapter through UDP broadcast from Win4Yaesu.

 

 I key SSB by using a Heil Microphone adapter plugged in the FT3000 front panel with a Heil handswitch or footswitch when I'm not using the N1MM+ WAV files.

 

  N1MM+ is configured:

 

Config Window Hardware tab

 

Radio 1 COM18 Yaesu FT3000 

CW / Digital Keying COM10

 

N1MM+ Audio SO1V, Radio Codec is checked.  

Playback uses USB audio codec 

Record uses UMC202HD as that is where my mic is plugged in

Mute microphone during audio playback is checked

 

If my station is configured this way I cannot transmit SSB by using the Footswitch.  If I use the N1MM+ buttons or Keyboard Function keys it will transmit the audio through the radio.

 

If I connect the output of the UMC202HD to the back panel Line in of the FT3000 and choose the Front panel option in the FT3000 menu 104 (SSB audio source, front, data, or usb) the radio will transmit using the footswitch and the microphone.  It will also record and send audio with N1MM+.

 

If I disconnect the UMC202HD line in and choose the USB input of the FT3000 menu to route the computer audio through the radio it will not transmit using the footswitch.  The FT3000 will still record and send audio with N1MM+.

 

Can anyone else with a FT3000 tell me if they are able to successfully route their audio from their computer sound card through the USB cable of the FT3000 or if they need to route the audio through the line in jack?

 

  I did search the archives and didn't find anyone with the same issue.

 

  I also set up a Windows 10 partition on my MacBook Pro laptop using BootCamp and I have the same result with N1MM+ SSB audio.

 

Thanks!

 

George / W7GES

 

Virus-free. www.avg.com

Re: Yaesu FT3000 and SSB audio through the USB audio codec

George Skoubis W7GES
 
Edited

Hi John,

  Thank You for your reply.  I can get the FT3000 to record messages and play them back with N1MM.  I can also use the footswitch to transmit live audio (say I don't want to use concatenated wav files to answer a cq).  The only way I've found to make this work is to have the microphone plugged in the Behringer 202 sound card and the output of the soundcard plugged into the line in jack of the FT3000.  

  This would work well if I'm using one radio.  If I want to add a second radio I would need to have a switch that sends the audio output into the second radio.  I thought there would be a way to send the live audio from the soundcard to the FT3000 USB Audio codec without having the line out of the soundcard plugged into the line in of the FT3000.  Then the live audio would be transmitted by whichever radio has the PTT command.

  I think there must be some way to do this as N1MM can transmit a WAV file that is stored on the hard drive through the USB audio codec.  Since the WAV file audio can be routed through the radio I think there has to be a way to route live mic audio through the USB audio codec.



On the computer  I have the Default Speakers set to Realtek (my audio speakers) and the Recording device set to Behringer 202 with the listen box checked.  I can hear my audio through the speakers as I speak into the mic.

 For the first 3 tests the audio out of the Behringer 202 soundcard is not plugged in to the line in of the FT3000 as I am trying to route the soundcard audio through the computer into the USB audio codec of the FT3000. 

Test #1

  For this configuration I tried Win4Yaesu and N1MM+ with the configuration that works for CW and RTTY.  N1MM reads the radio frequency in SSB mode and will change frequencies if I click in the bandmap, prerecorded FKey messages will transmit.

  In the Configuer / Hardware / Port Menu for the FT3000 I have all four PTT boxes checked.

  In the N1MM Audio setup window I have the Playback set to SO1V, the speakers set to USB Audio Codec and the Internal Radio Codec box checked.

  On the Message Recording Tab I have USB Audio Codec selected.

  In the FT3000 menu 103 (SSB Mic Select), I have Front panel selected, choices are Front, Data, or USB. FT3000 Monitor is On.

  The Microphone is plugged into the soundcard input of my computer (Behringer 202).

  If I have N1MM in S&P mode and I press CTRL+Shift+F2 and record a message I see the Recording started and recording saved message.  When I press F2 I get the static (I'm assuming the atmospheric static the radio was receiving while I was recording since I can record a heterodyne sound if I tune to one).  I tried all three setting for Radio Menu 103 and tried to record a message and get the atmospheric static for all three.

Test #2

  I exited Win4Yaesu and configured N1MM to control the FT3000 directly, not using the Com0Com ports and Win4Yaesu is not an open program.

  I left the rest of the N1MM settings as above.  I switched Radio Menu 103 to USB.  

  If I leave the Menu showing on the FT3000 display I can see USB is selected.  If I use Ctrl+Shift+F2 to record a message the menu stays set to USB. The recording is still static.

  If I press the F2 key to play the message the FT3000 menu 103 setting changes to Front after the message stops playing.

  I press ctrl+shift+F2 and record static.

  If I press the Footswitch or mox button to key the FT3000 no live audio is transmitted.

Test #3

  I leave the settings with the com ports direct to N1MM and no other ham software running.

  I change the N1MM audio menu to use the Behringer 202 as the recording device.

  Ctrl+Shift+F2 records the message from the Behringer 202 microphone.  Pressing the F2 key plays the message back, the FT3000 103 menu changes from USB to Front after the F2 message stops.

  If I use the footswitch or mox button to key the FT3000 no live audio is transmitted.

Test #4.

  I plug a cable into the Behringer 202 line out and into the FT3000 line in.

  I leave the settings with the com ports direct to N1MM and no other ham software running.

  I leave the N1MM settings as Test #3.  

  I leave the FT3000 Menu 103 Mic Select to Front as N1MM left it after test #3.

  Ctrl+Shift+F2 records a message.  

  If I use the footswitch or mox button to key the FT3000 live audio is transmitted.

  ----------------------------

  If I use the FT3000 with no Ham program running I cannot find a combination that will transmit the Behringer 202 live mic audio through the radio but I still think there should be...

  If this is the way N1MM and the FT3000 are supposed to work together I will make or buy an interface that routes the audio to the appropriate rig from the soundcard output when the appropriate radio is keyed via the footswitch. 

Thanks for looking at this long email, sorry If I'm not able to make my question clear.

George / W7GES

  

  

  

  

   

On Wed, Apr 4, 2018 at 7:09 PM, John Bednar <k3ct@...> wrote:

George,

 

To play voice messages with the radio codec, you will need to enable (check mark) “PTT via Radio Command SSB Mode” in the COM port setup window for the radio.

 

The FT3000 has a Monitor function. You should be able to record voice messages with the radio codec. Turn On the radio Monitor and change Logger+ audio to record with the radio codec.

 

You should not need to use a footswitch.

 

It is not uncommon to learn that other programs corrupt the radio commands.

 

John, K3CT

 

From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of George Skoubis
Sent: Monday, April 02, 2018 7:38 PM
To: N1MMLoggerPlus@groups.io
Subject: [N1MMLoggerPlus] Yaesu FT3000 and SSB audio through the USB audio codec

 

Hi Everyone,

 

  I've been out of Ham Radio since 2006 since I moved across the country, started a new business and was busy while my kids were growing up.

 

  Now the youngest moved away for college (she did get her ham Tech license first) and I have more time for Ham Radio.

 

  I bought a Yaesu FT3000 and downloaded N1MM+ as I had tried the original N1MM back in the early 2000's with my TenTec Orion.

 

  I was successful in interfacing the radio with N1MM+ and can use the RTTY, CW and SSB modes.  

 

  There is one small item that I can't seem to get working correctly but I'm not sure if the problem is in the way I have the radio configured, N1MM+ configured, or if I just don't understand how it should work.

 

  If I try to transmit with N1MM+ configured to record audio through the USB sound card codec in the radio I don't get any audio.  I can get transmit audio by connecting the output of the sound card to the line in of the radio.  

 

  I can also record and play back messages through N1MM+ by using Control+Shift+F Key

 

My hardware:

 

Windows 10 PC Intel I7 Processor 3.6 ghz processor 16 gb memory

Behringer UMC202HD Soundcard (for Microphone)

Behringer UMC404HD Soundcard (for N8LP Panadapter)

N8LP Panadapter

 

Software:

Windows 10 Home 64 bit

N1MM+ Logger 1.0.7142.0

Win4Yaesu 1.070 64 Bit

MMTTY 1.68 FSK64

WSJXT

 

The radio is connected via USB to the computer.   The FT3000 USB silicon com ports are assigned to Com11 (enhanced) and Com10 (regular, which I use to key rig).

 

Since I am using Win4Yaesu I am using Com0Com to share a virtual serial port with N1MM+ (COM11 in Win4Yaesu gets sent to COM18 for N1MM+). CW Keying, RTTY Keying, and SSB messages are transmitted from N1MM+ when I press the function key or click on the button in N1MM+

 

 The N1MM+ Spectrum display shows the output of the N8LP panadapter through UDP broadcast from Win4Yaesu.

 

 I key SSB by using a Heil Microphone adapter plugged in the FT3000 front panel with a Heil handswitch or footswitch when I'm not using the N1MM+ WAV files.

 

  N1MM+ is configured:

 

Config Window Hardware tab

 

Radio 1 COM18 Yaesu FT3000 

CW / Digital Keying COM10

 

N1MM+ Audio SO1V, Radio Codec is checked.  

Playback uses USB audio codec 

Record uses UMC202HD as that is where my mic is plugged in

Mute microphone during audio playback is checked

 

If my station is configured this way I cannot transmit SSB by using the Footswitch.  If I use the N1MM+ buttons or Keyboard Function keys it will transmit the audio through the radio.

 

If I connect the output of the UMC202HD to the back panel Line in of the FT3000 and choose the Front panel option in the FT3000 menu 104 (SSB audio source, front, data, or usb) the radio will transmit using the footswitch and the microphone.  It will also record and send audio with N1MM+.

 

If I disconnect the UMC202HD line in and choose the USB input of the FT3000 menu to route the computer audio through the radio it will not transmit using the footswitch.  The FT3000 will still record and send audio with N1MM+.

 

Can anyone else with a FT3000 tell me if they are able to successfully route their audio from their computer sound card through the USB cable of the FT3000 or if they need to route the audio through the line in jack?

 

  I did search the archives and didn't find anyone with the same issue.

 

  I also set up a Windows 10 partition on my MacBook Pro laptop using BootCamp and I have the same result with N1MM+ SSB audio.

 

Thanks!

 

George / W7GES

 

Virus-free. www.avg.com


Re: Call history not workingMM0JOM

John MM0JOM
 

On Wed, Apr 4, 2018 at 03:01 pm, VE2FK wrote:
John
Just tested with latest N1MM+ version.
Using UKEI89_VHF UDC module and ukei80.txt Call History from N1MM files
and all is working ok here.

Claude VE2FK


Le 2018-04-04 à 17:21, Young Johnnie a écrit :
loaded version V1.0.7144.0. Used for UKEICC 80m CC tonight and call history data was not populating section data. Call sign would appear in the call history but the locator information was not picked up to populate entry field. Have used this call history file for about 2 years. Maybe a bug or maybe I have changed something
John
MM0JOM/GM3A

Aucun virus trouvé dans ce message.
Analyse effectuée par AVG - www.avg.fr
Version: 2016.0.7226 / Base de données virale: 4793/15540 - Date: 04/04/2018

Can’t see a UKEI89_VHF UDC. Is this a typo. I am using UKEI80_VHF UDC. I have tried it with the downloaded call history file from N1MM and get the same behaviour. I do have call history file enabled. 
The only thing that changed apart from updating to the latest version (have also tried reverting to previous version) was that in a recent contest I got a message that the call history file loaded was not related to the contest and switched off call history. Seems like it maybe has switched it off permanently. Should I delete N1MM and reinstall or any other suggestions 
John
MM0JOM/GM3A

Re: Call history not workingMM0JOM

Tom Wagner (N1MM)
 

On 4/5/2018 5:18 AM, Young Johnnie wrote:
On Wed, Apr 4, 2018 at 03:01 pm, VE2FK wrote:

John
Just tested with latest N1MM+ version.
Using UKEI89_VHF UDC module and ukei80.txt Call History from N1MM
files
and all is working ok here.

Claude VE2FK


Le 2018-04-04 à 17:21, Young Johnnie a écrit :

loaded version V1.0.7144.0. Used for UKEICC 80m CC tonight and
call history data was not populating section data. Call sign
would appear in the call history but the locator information
was not picked up to populate entry field. Have used this call
history file for about 2 years. Maybe a bug or maybe I have
changed something
John
MM0JOM/GM3A

Aucun virus trouvé dans ce message.
Analyse effectuée par AVG - www.avg.fr <http://www.avg.fr>
Version: 2016.0.7226 / Base de données virale: 4793/15540 -
Date: 04/04/2018

Can’t see a UKEI89_VHF UDC. Is this a typo. I am using UKEI80_VHF UDC. I have tried it with the downloaded call history file from N1MM and get the same behaviour. I do have call history file enabled.
The only thing that changed apart from updating to the latest version (have also tried reverting to previous version) was that in a recent contest I got a message that the call history file loaded was not related to the contest and switched off call history. Seems like it maybe has switched it off permanently. Should I delete N1MM and reinstall or any other suggestions
John
MM0JOM/GM3A

Re: Call history not workingMM0JOM

John MM0JOM
 


Thankyou but already reviewed all the information in N1MM files before posting.
I have just checked another contest Russian dx with its call history file and it is working correctly.
Any other suggestions
John
MM0JOM/GM3A


On Thu, Apr 5, 2018 at 02:36 am, Tom Wagner (N1MM) wrote:
http://n1mm.hamdocs.com/tiki-index.php?page=Call+History+and+Reverse+Call+History+Lookup


On 4/5/2018 5:18 AM, Young Johnnie wrote:
On Wed, Apr 4, 2018 at 03:01 pm, VE2FK wrote:

John
Just tested with latest N1MM+ version.
Using UKEI89_VHF UDC module and ukei80.txt Call History from N1MM
files
and all is working ok here.

Claude VE2FK


Le 2018-04-04 à 17:21, Young Johnnie a écrit :

loaded version V1.0.7144.0. Used for UKEICC 80m CC tonight and
call history data was not populating section data. Call sign
would appear in the call history but the locator information
was not picked up to populate entry field. Have used this call
history file for about 2 years. Maybe a bug or maybe I have
changed something
John
MM0JOM/GM3A

Aucun virus trouvé dans ce message.
Analyse effectuée par AVG - www.avg.fr <http://www.avg.fr>
Version: 2016.0.7226 / Base de données virale: 4793/15540 -
Date: 04/04/2018

Can’t see a UKEI89_VHF UDC. Is this a typo. I am using UKEI80_VHF UDC.
I have tried it with the downloaded call history file from N1MM and
get the same behaviour. I do have call history file enabled.
The only thing that changed apart from updating to the latest version
(have also tried reverting to previous version) was that in a recent
contest I got a message that the call history file loaded was not
related to the contest and switched off call history. Seems like it
maybe has switched it off permanently. Should I delete N1MM and
reinstall or any other suggestions
John
MM0JOM/GM3A

Re: Call history not workingMM0JOM

GM4OSS
 

I've just tried ver  V1.0.7144.0 and call history works fine. Are you sure you are using correct call history file?

Try UKEI80.txt on N1MM site this is the file for grids.

Steve/GM4OSS

On Thu, Apr 5, 2018 at 10:47 AM, Young Johnnie <j@...> wrote:

Thankyou but already reviewed all the information in N1MM files before posting.
I have just checked another contest Russian dx with its call history file and it is working correctly.
Any other suggestions
John
MM0JOM/GM3A


On Thu, Apr 5, 2018 at 02:36 am, Tom Wagner (N1MM) wrote:
http://n1mm.hamdocs.com/tiki-index.php?page=Call+History+and+Reverse+Call+History+Lookup


On 4/5/2018 5:18 AM, Young Johnnie wrote:
On Wed, Apr 4, 2018 at 03:01 pm, VE2FK wrote:

John
Just tested with latest N1MM+ version.
Using UKEI89_VHF UDC module and ukei80.txt Call History from N1MM
files
and all is working ok here.

Claude VE2FK


Le 2018-04-04 à 17:21, Young Johnnie a écrit :

loaded version V1.0.7144.0. Used for UKEICC 80m CC tonight and
call history data was not populating section data. Call sign
would appear in the call history but the locator information
was not picked up to populate entry field. Have used this call
history file for about 2 years. Maybe a bug or maybe I have
changed something
John
MM0JOM/GM3A

Aucun virus trouvé dans ce message.
Analyse effectuée par AVG - www.avg.fr <http://www.avg.fr>
Version: 2016.0.7226 / Base de données virale: 4793/15540 -
Date: 04/04/2018

Can’t see a UKEI89_VHF UDC. Is this a typo. I am using UKEI80_VHF UDC.
I have tried it with the downloaded call history file from N1MM and
get the same behaviour. I do have call history file enabled.
The only thing that changed apart from updating to the latest version
(have also tried reverting to previous version) was that in a recent
contest I got a message that the call history file loaded was not
related to the contest and switched off call history. Seems like it
maybe has switched it off permanently. Should I delete N1MM and
reinstall or any other suggestions
John
MM0JOM/GM3A




--
73 de Steve GM4OSS

Re: Call history not workingMM0JOM

John MM0JOM
 

Steve
yes deifinitely the correct call history file. Tried the one from N1MM and my own one which I have built up over the last couple of years. It has always worked before until last night.
Maybe my Udc is corrupted so I am going to try downloading that again from the UKEICC site and try that.
John
MM0JOM/GM3A

On Thu, Apr 5, 2018 at 03:26 am, GM4OSS wrote:
I've just tried ver  V1.0.7144.0 and call history works fine. Are you sure you are using correct call history file?

Try UKEI80.txt on N1MM site this is the file for grids.
 
Steve/GM4OSS

On Thu, Apr 5, 2018 at 10:47 AM, Young Johnnie <j@...> wrote:

Thankyou but already reviewed all the information in N1MM files before posting.
I have just checked another contest Russian dx with its call history file and it is working correctly.
Any other suggestions
John
MM0JOM/GM3A


On Thu, Apr 5, 2018 at 02:36 am, Tom Wagner (N1MM) wrote:
http://n1mm.hamdocs.com/tiki-index.php?page=Call+History+and+Reverse+Call+History+Lookup


On 4/5/2018 5:18 AM, Young Johnnie wrote:
On Wed, Apr 4, 2018 at 03:01 pm, VE2FK wrote:

John
Just tested with latest N1MM+ version.
Using UKEI89_VHF UDC module and ukei80.txt Call History from N1MM
files
and all is working ok here.

Claude VE2FK


Le 2018-04-04 à 17:21, Young Johnnie a écrit :

loaded version V1.0.7144.0. Used for UKEICC 80m CC tonight and
call history data was not populating section data. Call sign
would appear in the call history but the locator information
was not picked up to populate entry field. Have used this call
history file for about 2 years. Maybe a bug or maybe I have
changed something
John
MM0JOM/GM3A

Aucun virus trouvé dans ce message.
Analyse effectuée par AVG - www.avg.fr <http://www.avg.fr>
Version: 2016.0.7226 / Base de données virale: 4793/15540 -
Date: 04/04/2018

Can’t see a UKEI89_VHF UDC. Is this a typo. I am using UKEI80_VHF UDC.
I have tried it with the downloaded call history file from N1MM and
get the same behaviour. I do have call history file enabled.
The only thing that changed apart from updating to the latest version
(have also tried reverting to previous version) was that in a recent
contest I got a message that the call history file loaded was not
related to the contest and switched off call history. Seems like it
maybe has switched it off permanently. Should I delete N1MM and
reinstall or any other suggestions
John
MM0JOM/GM3A

 

 

 



 
--
73 de Steve GM4OSS

Re: Call history not workingMM0JOM

John MM0JOM
 

Ok problem solved. Downloaded the Udc again from the UKEICC site and it is working again. Don’t know if the Udc has been changed recently or if my copy was corrupted. Haven’t used it much this year.
John
MM0JOM/GM3A

Thu, Apr 5, 2018 at 03:34 am, Young Johnnie wrote:

Steve
yes deifinitely the correct call history file. Tried the one from N1MM and my own one which I have built up over the last couple of years. It has always worked before until last night.
Maybe my Udc is corrupted so I am going to try downloading that again from the UKEICC site and try that.
John
MM0JOM/GM3A
On Thu, Apr 5, 2018 at 03:26 am, GM4OSS wrote:
I've just tried ver  V1.0.7144.0 and call history works fine. Are you sure you are using correct call history file?

Try UKEI80.txt on N1MM site this is the file for grids.
 
Steve/GM4OSS

On Thu, Apr 5, 2018 at 10:47 AM, Young Johnnie <j@...> wrote:

Thankyou but already reviewed all the information in N1MM files before posting.
I have just checked another contest Russian dx with its call history file and it is working correctly.
Any other suggestions
John
MM0JOM/GM3A


On Thu, Apr 5, 2018 at 02:36 am, Tom Wagner (N1MM) wrote:
http://n1mm.hamdocs.com/tiki-index.php?page=Call+History+and+Reverse+Call+History+Lookup


On 4/5/2018 5:18 AM, Young Johnnie wrote:
On Wed, Apr 4, 2018 at 03:01 pm, VE2FK wrote:

John
Just tested with latest N1MM+ version.
Using UKEI89_VHF UDC module and ukei80.txt Call History from N1MM
files
and all is working ok here.

Claude VE2FK


Le 2018-04-04 à 17:21, Young Johnnie a écrit :

loaded version V1.0.7144.0. Used for UKEICC 80m CC tonight and
call history data was not populating section data. Call sign
would appear in the call history but the locator information
was not picked up to populate entry field. Have used this call
history file for about 2 years. Maybe a bug or maybe I have
changed something
John
MM0JOM/GM3A

Aucun virus trouvé dans ce message.
Analyse effectuée par AVG - www.avg.fr <http://www.avg.fr>
Version: 2016.0.7226 / Base de données virale: 4793/15540 -
Date: 04/04/2018

Can’t see a UKEI89_VHF UDC. Is this a typo. I am using UKEI80_VHF UDC.
I have tried it with the downloaded call history file from N1MM and
get the same behaviour. I do have call history file enabled.
The only thing that changed apart from updating to the latest version
(have also tried reverting to previous version) was that in a recent
contest I got a message that the call history file loaded was not
related to the contest and switched off call history. Seems like it
maybe has switched it off permanently. Should I delete N1MM and
reinstall or any other suggestions
John
MM0JOM/GM3A

 

 

 



 
--
73 de Steve GM4OSS

locked Re: New Version

Tom - N1MM
 

Version 1.0.7147 (April 5, 2018)
MO QSO Party: Added the second bonus station callsign. (Coded by K3CT)

Re: Yaesu FT3000 and SSB audio through the USB audio codec

John Bednar
 
Edited

George,

 

I don’t have the time to read your message now.

 

Since I don’t see the results of what I suggested, please describe happens when you:

-          Enable radio command PTT for SSB mode (check the box)

-          Have “Internal Radio Codec” checked on the Logger+ Audio Playback tab

-          Select the radio codec for recording

-          Select the radio codec for playback

-          If the footswitch is used to switch the MIC audio path, bypass it so the MIC is connected to the radio

-          Turn On the radio MONITOR, turn up the level so the radio codec receives audio

-          You should hear your voice in the headphones when you transmit

-          Record the F4 message with the MIC plugged into the front of the radio without the footswitch

-          Play the F4 recorded wav file without the footswitch.

 

Do not record the CQ message (F1) unless you pay attention to the RUN/S&P indicator.

The program switches to RUN when the F1 key is pressed. Often users record the S&P CQ message and play the RUN CQ message and wonder why it doesn’t work.

 

I expect the radio to key when you start to record, unkey at the end of the recording.

The radio should key when you play back the wav file.

 

John, K3CT

 

From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of George Skoubis
Sent: Thursday, April 05, 2018 1:39 AM
To: N1MMLoggerPlus@groups.io
Subject: Re: [N1MMLoggerPlus] Yaesu FT3000 and SSB audio through the USB audio codec

 

Hi John,

 

  Thank You for your reply.  I can get the FT3000 to record messages and play them back with N1MM.  I can also use the footswitch to transmit live audio (say I don't want to use concatenated wav files to answer a cq).  The only way I've found to make this work is to have the microphone plugged in the Behringer 202 sound card and the output of the soundcard plugged into the line in jack of the FT3000.  

 

  This would work well if I'm using one radio.  If I want to add a second radio I would need to have a switch that sends the audio output into the second radio.  I thought there would be a way to send the live audio from the soundcard to the FT3000 USB Audio codec without having the line out of the soundcard plugged into the line in of the FT3000.  Then the live audio would be transmitted by whichever radio has the PTT command.

 

  I think there must be some way to do this as N1MM can transmit a WAV file that is stored on the hard drive through the USB audio codec.  Since the WAV file audio can be routed through the radio I think there has to be a way to route live mic audio through the USB audio codec.

 

 

 

On the computer  I have the Default Speakers set to Realtek (my audio speakers) and the Recording device set to Behringer 202 with the listen box checked.  I can hear my audio through the speakers as I speak into the mic.

 

 For the first 3 tests the audio out of the Behringer 202 soundcard is not plugged in to the line in of the FT3000 as I am trying to route the soundcard audio through the computer into the USB audio codec of the FT3000. 

 

Test #1

 

  For this configuration I tried Win4Yaesu and N1MM+ with the configuration that works for CW and RTTY.  N1MM reads the radio frequency in SSB mode and will change frequencies if I click in the bandmap, prerecorded FKey messages will transmit.

 

  In the Configuer / Hardware / Port Menu for the FT3000 I have all four PTT boxes checked.

 

  In the N1MM Audio setup window I have the Playback set to SO1V, the speakers set to USB Audio Codec and the Internal Radio Codec box checked.

 

  On the Message Recording Tab I have USB Audio Codec selected.

 

  In the FT3000 menu 103 (SSB Mic Select), I have Front panel selected, choices are Front, Data, or USB. FT3000 Monitor is On.

 

  The Microphone is plugged into the soundcard input of my computer (Behringer 202).

 

  If I have N1MM in S&P mode and I press CTRL+Shift+F2 and record a message I see the Recording started and recording saved message.  When I press F2 I get the static (I'm assuming the atmospheric static the radio was receiving while I was recording since I can record a heterodyne sound if I tune to one).  I tried all three setting for Radio Menu 103 and tried to record a message and get the atmospheric static for all three.

 

Test #2

 

  I exited Win4Yaesu and configured N1MM to control the FT3000 directly, not using the Com0Com ports and Win4Yaesu is not an open program.

 

  I left the rest of the N1MM settings as above.  I switched Radio Menu 103 to USB.  

 

  If I leave the Menu showing on the FT3000 display I can see USB is selected.  If I use Ctrl+Shift+F2 to record a message the menu stays set to USB. The recording is still static.

 

  If I press the F2 key to play the message the FT3000 menu 103 setting changes to Front after the message stops playing.

 

  I press ctrl+shift+F2 and record static.

 

  If I press the Footswitch or mox button to key the FT3000 no live audio is transmitted.

 

Test #3

 

  I leave the settings with the com ports direct to N1MM and no other ham software running.

 

  I change the N1MM audio menu to use the Behringer 202 as the recording device.

 

  Ctrl+Shift+F2 records the message from the Behringer 202 microphone.  Pressing the F2 key plays the message back, the FT3000 103 menu changes from USB to Front after the F2 message stops.

 

  If I use the footswitch or mox button to key the FT3000 no live audio is transmitted.

 

Test #4.

 

  I plug a cable into the Behringer 202 line out and into the FT3000 line in.

 

  I leave the settings with the com ports direct to N1MM and no other ham software running.

 

  I leave the N1MM settings as Test #3.  

 

  I leave the FT3000 Menu 103 Mic Select to Front as N1MM left it after test #3.

 

  Ctrl+Shift+F2 records a message.  

 

  If I use the footswitch or mox button to key the FT3000 live audio is transmitted.

 

  ----------------------------

 

  If I use the FT3000 with no Ham program running I cannot find a combination that will transmit the Behringer 202 live mic audio through the radio but I still think there should be...

 

  If this is the way N1MM and the FT3000 are supposed to work together I will make or buy an interface that routes the audio to the appropriate rig from the soundcard output when the appropriate radio is keyed via the footswitch. 

 

Thanks for looking at this long email, sorry If I'm not able to make my question clear.

 

George / W7GES

 

  

 

  

 

  

 

  

 

   

 

On Wed, Apr 4, 2018 at 7:09 PM, John Bednar <k3ct@...> wrote:

George,

 

To play voice messages with the radio codec, you will need to enable (check mark) “PTT via Radio Command SSB Mode” in the COM port setup window for the radio.

 

The FT3000 has a Monitor function. You should be able to record voice messages with the radio codec. Turn On the radio Monitor and change Logger+ audio to record with the radio codec.

 

You should not need to use a footswitch.

 

It is not uncommon to learn that other programs corrupt the radio commands.

 

John, K3CT

 

From: N1MMLoggerPlus@groups.io [mailto:N1MMLoggerPlus@groups.io] On Behalf Of George Skoubis
Sent: Monday, April 02, 2018 7:38 PM
To: N1MMLoggerPlus@groups.io
Subject: [N1MMLoggerPlus] Yaesu FT3000 and SSB audio through the USB audio codec

 

Hi Everyone,

 

  I've been out of Ham Radio since 2006 since I moved across the country, started a new business and was busy while my kids were growing up.

 

  Now the youngest moved away for college (she did get her ham Tech license first) and I have more time for Ham Radio.

 

  I bought a Yaesu FT3000 and downloaded N1MM+ as I had tried the original N1MM back in the early 2000's with my TenTec Orion.

 

  I was successful in interfacing the radio with N1MM+ and can use the RTTY, CW and SSB modes.  

 

  There is one small item that I can't seem to get working correctly but I'm not sure if the problem is in the way I have the radio configured, N1MM+ configured, or if I just don't understand how it should work.

 

  If I try to transmit with N1MM+ configured to record audio through the USB sound card codec in the radio I don't get any audio.  I can get transmit audio by connecting the output of the sound card to the line in of the radio.  

 

  I can also record and play back messages through N1MM+ by using Control+Shift+F Key

 

My hardware:

 

Windows 10 PC Intel I7 Processor 3.6 ghz processor 16 gb memory

Behringer UMC202HD Soundcard (for Microphone)

Behringer UMC404HD Soundcard (for N8LP Panadapter)

N8LP Panadapter

 

Software:

Windows 10 Home 64 bit

N1MM+ Logger 1.0.7142.0

Win4Yaesu 1.070 64 Bit

MMTTY 1.68 FSK64

WSJXT

 

The radio is connected via USB to the computer.   The FT3000 USB silicon com ports are assigned to Com11 (enhanced) and Com10 (regular, which I use to key rig).

 

Since I am using Win4Yaesu I am using Com0Com to share a virtual serial port with N1MM+ (COM11 in Win4Yaesu gets sent to COM18 for N1MM+). CW Keying, RTTY Keying, and SSB messages are transmitted from N1MM+ when I press the function key or click on the button in N1MM+

 

 The N1MM+ Spectrum display shows the output of the N8LP panadapter through UDP broadcast from Win4Yaesu.

 

 I key SSB by using a Heil Microphone adapter plugged in the FT3000 front panel with a Heil handswitch or footswitch when I'm not using the N1MM+ WAV files.

 

  N1MM+ is configured:

 

Config Window Hardware tab

 

Radio 1 COM18 Yaesu FT3000 

CW / Digital Keying COM10

 

N1MM+ Audio SO1V, Radio Codec is checked.  

Playback uses USB audio codec 

Record uses UMC202HD as that is where my mic is plugged in

Mute microphone during audio playback is checked

 

If my station is configured this way I cannot transmit SSB by using the Footswitch.  If I use the N1MM+ buttons or Keyboard Function keys it will transmit the audio through the radio.

 

If I connect the output of the UMC202HD to the back panel Line in of the FT3000 and choose the Front panel option in the FT3000 menu 104 (SSB audio source, front, data, or usb) the radio will transmit using the footswitch and the microphone.  It will also record and send audio with N1MM+.

 

If I disconnect the UMC202HD line in and choose the USB input of the FT3000 menu to route the computer audio through the radio it will not transmit using the footswitch.  The FT3000 will still record and send audio with N1MM+.

 

Can anyone else with a FT3000 tell me if they are able to successfully route their audio from their computer sound card through the USB cable of the FT3000 or if they need to route the audio through the line in jack?

 

  I did search the archives and didn't find anyone with the same issue.

 

  I also set up a Windows 10 partition on my MacBook Pro laptop using BootCamp and I have the same result with N1MM+ SSB audio.

 

Thanks!

 

George / W7GES

 

Virus-free. www.avg.com