Date   

Re: No Transmit for RTTY using IC-7300 and MMVARI

Rick Spears W4HRA
 

Rick. Hate to spoil my celebration but now JTDX goes straight into transmit when it loads. Just the opposite of what the issue was with MMVARI. None of the obvious functions like halt send will stop it from transmitting. Have to close JTDX. Any thoughts on which setting I changed my be the culprit?

Rick W4HRA


Re: No Transmit for RTTY using IC-7300 and MMVARI

Rick Spears W4HRA
 

Rick. Working now, Thanks!
So it may be a few different settings but I think Data Off Mode setting may have done it. I had it set to USB.
Also some changes to USB Send as well.
And in MMVARI setting PTT to Radio control.

Anyway thanks so much for your help.

73's Rick W4HRA


Re: No Transmit for RTTY using IC-7300 and MMVARI

John Munton - G7SSE
 

Rick ( and Rick)

I'm just guessing here but would "CI-V USB Echo Back" also need to bet set to ON in the radio for PTT via CAT command ??

73
John
G7SSE


------ Original Message ------
From: "Rick Ellison" <rellison@...>
Sent: 16/09/2021 18:47:27
Subject: Re: [hamlogger] No Transmit for RTTY using IC-7300 and MMVARI

Here are my radio settings..

Data Off Mode should be Mic,Acc

Data Mode should be USB

USB Serial Function should be CI-V

Now click on USB Send Keying

USB Send should be set to RTS

USB Keying CW should be set to DTR

USB Keying RTTY should be OFF

 

 

73 Rick

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Rick Spears
Sent: Thursday, September 16, 2021 1:36 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] No Transmit for RTTY using IC-7300 and MMVARI

 

Hi Rick. I mimicked your settings and still not keying transmitter. However now I see I did need the radio control checked for the CAT PTT for sure. So that is a big help.
I am thinking it is perhaps the way I have the CI-V settings set?
Also are setting your USB drivers for send and receive to both using the ICOM drivers?

Best Rick W4HRA


Virus-free. www.avast.com


--
73, John - G7SSE


Re: No Transmit for RTTY using IC-7300 and MMVARI

Rick Ellison
 

Here are my radio settings..

Data Off Mode should be Mic,Acc

Data Mode should be USB

USB Serial Function should be CI-V

Now click on USB Send Keying

USB Send should be set to RTS

USB Keying CW should be set to DTR

USB Keying RTTY should be OFF

 

 

73 Rick

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Rick Spears
Sent: Thursday, September 16, 2021 1:36 PM
To: hamlogger@groups.io
Subject: Re: [hamlogger] No Transmit for RTTY using IC-7300 and MMVARI

 

Hi Rick. I mimicked your settings and still not keying transmitter. However now I see I did need the radio control checked for the CAT PTT for sure. So that is a big help.
I am thinking it is perhaps the way I have the CI-V settings set?
Also are setting your USB drivers for send and receive to both using the ICOM drivers?

Best Rick W4HRA


Virus-free. www.avast.com


Re: No Transmit for RTTY using IC-7300 and MMVARI

Rick Spears W4HRA
 

Hi Rick. I mimicked your settings and still not keying transmitter. However now I see I did need the radio control checked for the CAT PTT for sure. So that is a big help.
I am thinking it is perhaps the way I have the CI-V settings set?
Also are setting your USB drivers for send and receive to both using the ICOM drivers?

Best Rick W4HRA


Re: LoTW sync via Club Log

Bob
 

Just a SWAG ... There is no DXCC for FT8. There is a DXCC_DIGITAL. In your Logger32 configuration, do you have FT8 as a digital mode? SeventyThree(s).

On 09/16/2021 1:04 PM Arturo LU6ETB <lu6etb@...> wrote:
 
 
Hi Gary,
 
I tried for the first time Logger32 -> Synchronize LOTW from Club Log.
 
See below results
 
image.png
 
image.png
 
It is reporting 6878 QSOs not found
What  I can't understand is why the first one, S79VU on 30M was reported. with "Can't find"
In Logger32 seems with same data
image.png
 
73 de Arturo, LU6ETB
 

El jue, 16 sept 2021 a las 11:22, Bob (< k4cy@...>) escribió:
Gary, also, make an ADIF export of the offending JH1HFW QSO so I can see exactly what's in the requested/granted fields of the logbook. 73.
On 09/16/2021 9:29 AM Bob < k4cy@...> wrote:
 
 
Gary, to investigate I'd need to see the LoTW records from Clublog.txt file that contains the JH1HFE record. SeventyThree(s)
On 09/15/2021 8:17 PM Gary Hinson < gary@...> wrote:
 
 

Errrrr, I was over-excited: we are no longer getting the red warning message, but the LoTW sync via Club Log still isn’t working properly.

 

Club Log knows about QSOs that have been matched and confirmed on LoTW, but isn’t passing those details to Logger32 e.g. after synchronising Logger32, Club Log and LoTW:

 

Here are my recent QSOs on LoTW:

 

 

This one with JH1HFE has been matched and confirmed already:

 

 

On Club Log it is shown as confirmed:

 

 

In  my log, that QSO remains stubbornly unconfirmed:

 


 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Gary Hinson
Sent: 16 September 2021 07:18
To: hamlogger@groups.io
Subject: Re: [hamlogger] LoTW sync via Club Log

 

Inspired by your positive report, Ian, I simply gave it another go … and it worked!

 

 

Hey thanks everyone.  It looks like - having been hammered by all our tests - whatever wasn’t working is now running properly again.  We must have knocked the bits back into place, or something.

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of g4girhb0 via groups.io
Sent: 16 September 2021 01:45
To: hamlogger@groups.io
Subject: Re: [hamlogger] LoTW sync via Club Log

 

Just done a Clublog sync worked ok down loaded 5 new mode/band updates.

 

73

Ian G4GIR

 

----- Original Message -----

From: <sp2ewq@...>

Reply-To: <hamlogger@groups.io>

Sent: 15/09/2021 14:05:52

Subject: Re: [hamlogger] LoTW sync via Club Log


 

 

Hi,

 

Exactly the same thing over here:

 

Best regards,

Alec

 

 

 

------ Wiadomość oryginalna ------

Od: "Dan" <osvaldo.peralta@...>

Data: 15.09.2021 14:46:36

Temat: Re: [hamlogger] LoTW sync via Club Log

 

Gary

 

I tried your steps and get same error.

 

73 de LU3MAM

 

El mar, 14 sept 2021 a las 21:55, Gary Hinson (<Gary@...>) escribió:

Can anyone who uses Club Log and LoTW with Logger32 help us test Logger32’s Synchronize LoTW (from Club Log) function, please?

I’m getting failures suggesting something is broken, somewhere. 

In order to test it:

1.       Get Club Log up to date with your recent LoTW confirmations using the <LoTW sync> button on Club Log’s left side menu.

2.       Wait a while for the sync to complete.  If you have selected “Every upload” under the Club Log settings page, you should get an email when it completes.  Otherwise, try waiting half an hour to an hour.

3.       In Logger32 open File → Synchronize LoTW (from Club Log).

4.       Select either <Last 3 Months only> or <Last 1 Month only>, then click <Start>.

On my system, I get a ‘Nothing to download’ red message every time:

If you don’t get the red error (or some other one), please check whether recent LoTW confirmations are duly recorded in your Logger32 log, as expected.  

5.       Let us know how you got on!

73 & TNX
Gary  ZL2iFB

 

 

 

 

 


Re: LoTW sync via Club Log

Arturo LU6ETB
 

Hi Gary,

I tried for the first time Logger32 -> Synchronize LOTW from Club Log.

See below results

image.png

image.png

It is reporting 6878 QSOs not found
What  I can't understand is why the first one, S79VU on 30M was reported. with "Can't find"
In Logger32 seems with same data
image.png

73 de Arturo, LU6ETB


El jue, 16 sept 2021 a las 11:22, Bob (<k4cy@...>) escribió:
Gary, also, make an ADIF export of the offending JH1HFW QSO so I can see exactly what's in the requested/granted fields of the logbook. 73.
On 09/16/2021 9:29 AM Bob <k4cy@...> wrote:
 
 
Gary, to investigate I'd need to see the LoTW records from Clublog.txt file that contains the JH1HFE record. SeventyThree(s)
On 09/15/2021 8:17 PM Gary Hinson <gary@...> wrote:
 
 

Errrrr, I was over-excited: we are no longer getting the red warning message, but the LoTW sync via Club Log still isn’t working properly.

 

Club Log knows about QSOs that have been matched and confirmed on LoTW, but isn’t passing those details to Logger32 e.g. after synchronising Logger32, Club Log and LoTW:

 

Here are my recent QSOs on LoTW:

 

 

This one with JH1HFE has been matched and confirmed already:

 

 

On Club Log it is shown as confirmed:

 

 

In  my log, that QSO remains stubbornly unconfirmed:

 


 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Gary Hinson
Sent: 16 September 2021 07:18
To: hamlogger@groups.io
Subject: Re: [hamlogger] LoTW sync via Club Log

 

Inspired by your positive report, Ian, I simply gave it another go … and it worked!

 

 

Hey thanks everyone.  It looks like - having been hammered by all our tests - whatever wasn’t working is now running properly again.  We must have knocked the bits back into place, or something.

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of g4girhb0 via groups.io
Sent: 16 September 2021 01:45
To: hamlogger@groups.io
Subject: Re: [hamlogger] LoTW sync via Club Log

 

Just done a Clublog sync worked ok down loaded 5 new mode/band updates.

 

73

Ian G4GIR

 

----- Original Message -----

From: <sp2ewq@...>

Reply-To: <hamlogger@groups.io>

Sent: 15/09/2021 14:05:52

Subject: Re: [hamlogger] LoTW sync via Club Log


 

 

Hi,

 

Exactly the same thing over here:

 

Best regards,

Alec

 

 

 

------ Wiadomość oryginalna ------

Od: "Dan" <osvaldo.peralta@...>

Data: 15.09.2021 14:46:36

Temat: Re: [hamlogger] LoTW sync via Club Log

 

Gary

 

I tried your steps and get same error.

 

73 de LU3MAM

 

El mar, 14 sept 2021 a las 21:55, Gary Hinson (<Gary@...>) escribió:

Can anyone who uses Club Log and LoTW with Logger32 help us test Logger32’s Synchronize LoTW (from Club Log) function, please?

I’m getting failures suggesting something is broken, somewhere. 

In order to test it:

1.       Get Club Log up to date with your recent LoTW confirmations using the <LoTW sync> button on Club Log’s left side menu.

2.       Wait a while for the sync to complete.  If you have selected “Every upload” under the Club Log settings page, you should get an email when it completes.  Otherwise, try waiting half an hour to an hour.

3.       In Logger32 open File → Synchronize LoTW (from Club Log).

4.       Select either <Last 3 Months only> or <Last 1 Month only>, then click <Start>.

On my system, I get a ‘Nothing to download’ red message every time:

If you don’t get the red error (or some other one), please check whether recent LoTW confirmations are duly recorded in your Logger32 log, as expected.  

5.       Let us know how you got on!

73 & TNX
Gary  ZL2iFB

 

 

 


Re: No Transmit for RTTY using IC-7300 and MMVARI

Rick Ellison
 

On the Settings menu of the digital window select MMVARI Settings go to RTTY Keying and select radio 1 use AFSK for RTTY.

Then on the same Settings menu go down to Radio PTT options. In that window for radio 1 select PTT by Radio Command and in the keying Line select RTS and set the com port to that of the radio.

 

Works every time for me. I use the same settings in MMTTY. I want to take my radio someplace I am only dealing with one USB cable to run everything. Makes it simple when I take my laptop with me camping..

 

73 Rick N2AMG

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Rick Spears
Sent: Thursday, September 16, 2021 11:35 AM
To: hamlogger@groups.io
Subject: Re: [hamlogger] No Transmit for RTTY using IC-7300 and MMVARI

 

Hi Rick. I have tried both LSB and LSB-D and still didn't key transmit. Will try again.
I am wondering about the PTT option. I know in JTDX there is a CAT Option for PTT.
However in MMVARI I dont have that option and chose PTT using serial port, which is assigned to the ICOM driver assigned serial port.7 for me.

73 Rick W4HRA


Virus-free. www.avast.com


Re: No Transmit for RTTY using IC-7300 and MMVARI

Dave Colliau
 

Do yourself a favor and get a usb civ cable to go in the remote jack and then use that port for cat control and JTDX/WSJT-X . Download FSK 32 or 64 bit for what ever you have for Windows , install it in the logger directory and use the USB port for keying FSK with MMTTY. This is the easy way . Gives you the extra port that Icom didnt.  Use MMVARI for PSK and the other sound modes. Once its all set up within Logger there is no messing with anything. It just works for all the modes .

On 09/16/2021 11:35 AM Rick Spears <rnspears@...> wrote:
 
 
Hi Rick. I have tried both LSB and LSB-D and still didn't key transmit. Will try again.
I am wondering about the PTT option. I know in JTDX there is a CAT Option for PTT.
However in MMVARI I dont have that option and chose PTT using serial port, which is assigned to the ICOM driver assigned serial port.7 for me.

73 Rick W4HRA


Re: No Transmit for RTTY using IC-7300 and MMVARI

Rick Spears W4HRA
 

Hi Rick. I have tried both LSB and LSB-D and still didn't key transmit. Will try again.
I am wondering about the PTT option. I know in JTDX there is a CAT Option for PTT.
However in MMVARI I dont have that option and chose PTT using serial port, which is assigned to the ICOM driver assigned serial port.7 for me.

73 Rick W4HRA


Re: LoTW sync via Club Log

Bob
 

Gary, also, make an ADIF export of the offending JH1HFW QSO so I can see exactly what's in the requested/granted fields of the logbook. 73.

On 09/16/2021 9:29 AM Bob <k4cy@...> wrote:
 
 
Gary, to investigate I'd need to see the LoTW records from Clublog.txt file that contains the JH1HFE record. SeventyThree(s)
On 09/15/2021 8:17 PM Gary Hinson <gary@...> wrote:
 
 

Errrrr, I was over-excited: we are no longer getting the red warning message, but the LoTW sync via Club Log still isn’t working properly.

 

Club Log knows about QSOs that have been matched and confirmed on LoTW, but isn’t passing those details to Logger32 e.g. after synchronising Logger32, Club Log and LoTW:

 

Here are my recent QSOs on LoTW:

 

 

This one with JH1HFE has been matched and confirmed already:

 

 

On Club Log it is shown as confirmed:

 

 

In  my log, that QSO remains stubbornly unconfirmed:

 


 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Gary Hinson
Sent: 16 September 2021 07:18
To: hamlogger@groups.io
Subject: Re: [hamlogger] LoTW sync via Club Log

 

Inspired by your positive report, Ian, I simply gave it another go … and it worked!

 

 

Hey thanks everyone.  It looks like - having been hammered by all our tests - whatever wasn’t working is now running properly again.  We must have knocked the bits back into place, or something.

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of g4girhb0 via groups.io
Sent: 16 September 2021 01:45
To: hamlogger@groups.io
Subject: Re: [hamlogger] LoTW sync via Club Log

 

Just done a Clublog sync worked ok down loaded 5 new mode/band updates.

 

73

Ian G4GIR

 

----- Original Message -----

From: <sp2ewq@...>

Reply-To: <hamlogger@groups.io>

Sent: 15/09/2021 14:05:52

Subject: Re: [hamlogger] LoTW sync via Club Log


 

 

Hi,

 

Exactly the same thing over here:

 

Best regards,

Alec

 

 

 

------ Wiadomość oryginalna ------

Od: "Dan" <osvaldo.peralta@...>

Data: 15.09.2021 14:46:36

Temat: Re: [hamlogger] LoTW sync via Club Log

 

Gary

 

I tried your steps and get same error.

 

73 de LU3MAM

 

El mar, 14 sept 2021 a las 21:55, Gary Hinson (<Gary@...>) escribió:

Can anyone who uses Club Log and LoTW with Logger32 help us test Logger32’s Synchronize LoTW (from Club Log) function, please?

I’m getting failures suggesting something is broken, somewhere. 

In order to test it:

1.       Get Club Log up to date with your recent LoTW confirmations using the <LoTW sync> button on Club Log’s left side menu.

2.       Wait a while for the sync to complete.  If you have selected “Every upload” under the Club Log settings page, you should get an email when it completes.  Otherwise, try waiting half an hour to an hour.

3.       In Logger32 open File → Synchronize LoTW (from Club Log).

4.       Select either <Last 3 Months only> or <Last 1 Month only>, then click <Start>.

On my system, I get a ‘Nothing to download’ red message every time:

If you don’t get the red error (or some other one), please check whether recent LoTW confirmations are duly recorded in your Logger32 log, as expected.  

5.       Let us know how you got on!

73 & TNX
Gary  ZL2iFB

 

 

 


v4.0.277 auto-update is on-line

Bob
 

Auto-update v4.0.277 has bug fixes and enhancements to parallel logging. 73.


Re: No Transmit for RTTY using IC-7300 and MMVARI

Rick Ellison
 

To use MMVARI in AFSK you need to have the radio set to USB-D or LSB-D otherwise the radio will trying to use the FSK output on the radio.

 

73 Rick N2AMG

 

From: hamlogger@groups.io [mailto:hamlogger@groups.io] On Behalf Of Rick Spears
Sent: Thursday, September 16, 2021 9:49 AM
To: hamlogger@groups.io
Subject: Re: [hamlogger] No Transmit for RTTY using IC-7300 and MMVARI

 

Hi Paul. Using MMVARI I select the mode RTTY-R and select Radio 1 to use AFSK for RTTY.

Rick


Virus-free. www.avast.com


Re: No Transmit for RTTY using IC-7300 and MMVARI

Rick Spears W4HRA
 

Hi Paul. Using MMVARI I select the mode RTTY-R and select Radio 1 to use AFSK for RTTY.

Rick


Re: No Transmit for RTTY using IC-7300 and MMVARI

Rick Spears W4HRA
 

Hi Dave. Thanks for response. When I use JTDX it works fine. It hears and decodes the FT8, Keys my transmitter and logs the QSO in L32.  So to me MMVARI ought to do the same?
All with the existing USB CAT connection.
Rick


Re: LoTW sync via Club Log

Bob
 

Gary, to investigate I'd need to see the LoTW records from Clublog.txt file that contains the JH1HFE record. SeventyThree(s)

On 09/15/2021 8:17 PM Gary Hinson <gary@...> wrote:
 
 

Errrrr, I was over-excited: we are no longer getting the red warning message, but the LoTW sync via Club Log still isn’t working properly.

 

Club Log knows about QSOs that have been matched and confirmed on LoTW, but isn’t passing those details to Logger32 e.g. after synchronising Logger32, Club Log and LoTW:

 

Here are my recent QSOs on LoTW:

 

 

This one with JH1HFE has been matched and confirmed already:

 

 

On Club Log it is shown as confirmed:

 

 

In  my log, that QSO remains stubbornly unconfirmed:

 


 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Gary Hinson
Sent: 16 September 2021 07:18
To: hamlogger@groups.io
Subject: Re: [hamlogger] LoTW sync via Club Log

 

Inspired by your positive report, Ian, I simply gave it another go … and it worked!

 

 

Hey thanks everyone.  It looks like - having been hammered by all our tests - whatever wasn’t working is now running properly again.  We must have knocked the bits back into place, or something.

 

73

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of g4girhb0 via groups.io
Sent: 16 September 2021 01:45
To: hamlogger@groups.io
Subject: Re: [hamlogger] LoTW sync via Club Log

 

Just done a Clublog sync worked ok down loaded 5 new mode/band updates.

 

73

Ian G4GIR

 

----- Original Message -----

From: <sp2ewq@...>

Reply-To: <hamlogger@groups.io>

Sent: 15/09/2021 14:05:52

Subject: Re: [hamlogger] LoTW sync via Club Log


 

 

Hi,

 

Exactly the same thing over here:

 

Best regards,

Alec

 

 

 

------ Wiadomość oryginalna ------

Od: "Dan" <osvaldo.peralta@...>

Data: 15.09.2021 14:46:36

Temat: Re: [hamlogger] LoTW sync via Club Log

 

Gary

 

I tried your steps and get same error.

 

73 de LU3MAM

 

El mar, 14 sept 2021 a las 21:55, Gary Hinson (<Gary@...>) escribió:

Can anyone who uses Club Log and LoTW with Logger32 help us test Logger32’s Synchronize LoTW (from Club Log) function, please?

I’m getting failures suggesting something is broken, somewhere. 

In order to test it:

1.       Get Club Log up to date with your recent LoTW confirmations using the <LoTW sync> button on Club Log’s left side menu.

2.       Wait a while for the sync to complete.  If you have selected “Every upload” under the Club Log settings page, you should get an email when it completes.  Otherwise, try waiting half an hour to an hour.

3.       In Logger32 open File → Synchronize LoTW (from Club Log).

4.       Select either <Last 3 Months only> or <Last 1 Month only>, then click <Start>.

On my system, I get a ‘Nothing to download’ red message every time:

If you don’t get the red error (or some other one), please check whether recent LoTW confirmations are duly recorded in your Logger32 log, as expected.  

5.       Let us know how you got on!

73 & TNX
Gary  ZL2iFB

 

 

 


Re: JTDX on-top ...

Bob
 

Peter, your pictures show that JTDX is not starting on top. The JTDX title bar shows JTDX by HF community. Maybe Logger32 started JTDX, but is did not control it. On the UDP BandMap, click the START/STOP menu. Click DELAY AFTER STARTING JTDX. Set the time to 20 seconds (or maybe more). Now, after starting JTDX from Logger32 does the title bat say JTDX & Logger32 (on-top). SeventyThree(s).

On 09/16/2021 8:15 AM Peter Eckersberger <oe3epw@...> wrote:
 
 
Hello Bob,

Sorry I'm late. Have been out of my home. To answer your question ... YES, its ON TOP. Here some pics ...

That's the one where only 'TCP' is on. But no 'UDP" ... therefore no 'band plan'. Parallel logging is OK, but JTDX vanishes every time at the end of every single logging procedure. That means ... 1 QSO logged and fiddling with the mouse to recall 'JTDX' to the foreground ...




Here the start of 'JTDX' via 'start menus' within 'band plan' ...




This shows the activated 'ON TOP' switch ...





Finally the operating position when 'JTDX' and Logger32' is 'parallel logging' ...
 



Well, that's it. Hope you're getting the point.


73 de Peter, OE3EPW



Re: No Transmit for RTTY using IC-7300 and MMVARI

Paul Sturpe
 

Are you trying to operate FSK or AFSK?

 

Paul Sturpe, W3GQ

QSL Bureau Mgr. W4 K4 N4 Prefixes

8860 Peninsula Dr

Terrell, NC  28682

 


Re: JTDX on-top ...

Peter Eckersberger
 

Hello Bob,

Sorry I'm late. Have been out of my home. To answer your question ... YES, its ON TOP. Here some pics ...

That's the one where only 'TCP' is on. But no 'UDP" ... therefore no 'band plan'. Parallel logging is OK, but JTDX vanishes every time at the end of every single logging procedure. That means ... 1 QSO logged and fiddling with the mouse to recall 'JTDX' to the foreground ...




Here the start of 'JTDX' via 'start menus' within 'band plan' ...




This shows the activated 'ON TOP' switch ...





Finally the operating position when 'JTDX' and Logger32' is 'parallel logging' ...
 



Well, that's it. Hope you're getting the point.


73 de Peter, OE3EPW



Re: No Transmit for RTTY using IC-7300 and MMVARI

Dave Colliau
 

If your going to do rtty and other modes with the 7300 you need to buy a cat cable that plugs into the remote jack in the rear . This along with the USB cable give you 2 ports instead of one . You use the remote jack for cat and the usb for the sound card and RTTY ,psk,etc keying .  I have an extra USB unit to plug in to the remote jack if your interested. Its the better FTDI chip not a Prolific.
Dave N8DC

On 09/15/2021If your going to do rtty  6:47 PM Gary Hinson <gary@...> wrote:
 
 

Hi Rick.

 

Have you been following the IC-7300 section of the User Manual?

 

The advice in there was proffered by various ICOM users.

 

If you spot errors or improvement opportunities, please let me know.  I’m not an ICOMmer and need the help.

 

73 & GL

Gary  ZL2iFB

 

From: hamlogger@groups.io <hamlogger@groups.io> On Behalf Of Rick Spears
Sent: 16 September 2021 10:22
To: hamlogger@groups.io
Subject: [hamlogger] No Transmit for RTTY using IC-7300 and MMVARI

 

Hello. Been struggling to resolve and hoping for some suggestions.
Using ICOM IC-7300 with L32. Set up CAT using USB port on PC into USB CAT port on ICOM.
Set for Serial Port 7 and using input and output USB sound card drivers from ICOM.
JTDX works fine!
I have JTDX off when using MMVARI.
MMVARI seems to be working fine. I see signals and can decode RTTY sigs on MMVARI waterfall.
When I click a macro I see it sending and can see waterfall showing sending my text.
However it does not key transmitter.
One weird thing is the freq display in MMVARI is not working or in sync with my radio.
However when I move my VFO manually on Rig I can see that the waterfall is also moving and correct.
I am set for LSB on radio. Tried LSB DATA but not working.
Tried everything I can think of.
I figure at this point must be some CAT radio setting.

Any help would be greatly appreciated.

73, Rick W4HRA

 

3601 - 3620 of 89399