Date   

Re: Fldigi TXid

Charles Odom
 

Yes, the normal text is transmitted without the id. But if I turn on the id it will only transmit the id with no following text, only a dead key.
On Sep 27, 2020, at 8:12 PM, Cliff <ae5zaham@...> wrote:

Does it transmit normally then, i.e. the desired text is transmitted?

73,
Cliff, AE5ZA

On Sep 27, 2020, at 20:03, Charles Odom < ki4vmk@...> wrote:

If I turn it off it will transmit CQ without the id.
On Sep 27, 2020, at 7:51 PM, Cliff < ae5zaham@...> wrote:
What happens/doesn’t happen if you turn off the TxID button in the fldigi window?

73,
Cliff, AE5ZA

On Sep 27, 2020, at 11:07, Charles Odom < ki4vmk@...> wrote:

Running Windows 10 and Fldigi 4.1.11.  For no reason when I transmit a mode id Fldigi will transmit the id and nothing afterwards, just a dead key signal, no cq, cq de Call Sign is transmitted. I suspect  Windows update is the reason but I can't find it. Any suggestions.
Thanks,
Charles



Re: Fldigi TXid

Cliff
 

Does it transmit normally then, i.e. the desired text is transmitted?

73,
Cliff, AE5ZA

On Sep 27, 2020, at 20:03, Charles Odom <ki4vmk@...> wrote:

If I turn it off it will transmit CQ without the id.
On Sep 27, 2020, at 7:51 PM, Cliff <ae5zaham@...> wrote:
What happens/doesn’t happen if you turn off the TxID button in the fldigi window?

73,
Cliff, AE5ZA

On Sep 27, 2020, at 11:07, Charles Odom <ki4vmk@...> wrote:

Running Windows 10 and Fldigi 4.1.11.  For no reason when I transmit a mode id Fldigi will transmit the id and nothing afterwards, just a dead key signal, no cq, cq de Call Sign is transmitted. I suspect  Windows update is the reason but I can't find it. Any suggestions.
Thanks,
Charles



Re: Fldigi TXid

Charles Odom
 

If I turn it off it will transmit CQ without the id.
On Sep 27, 2020, at 7:51 PM, Cliff <ae5zaham@...> wrote:

What happens/doesn’t happen if you turn off the TxID button in the fldigi window?

73,
Cliff, AE5ZA

On Sep 27, 2020, at 11:07, Charles Odom <ki4vmk@...> wrote:

Running Windows 10 and Fldigi 4.1.11.  For no reason when I transmit a mode id Fldigi will transmit the id and nothing afterwards, just a dead key signal, no cq, cq de Call Sign is transmitted. I suspect  Windows update is the reason but I can't find it. Any suggestions.
Thanks,
Charles


Re: Fldigi TXid

Cliff
 

What happens/doesn’t happen if you turn off the TxID button in the fldigi window?

73,
Cliff, AE5ZA

On Sep 27, 2020, at 11:07, Charles Odom <ki4vmk@...> wrote:

Running Windows 10 and Fldigi 4.1.11.  For no reason when I transmit a mode id Fldigi will transmit the id and nothing afterwards, just a dead key signal, no cq, cq de Call Sign is transmitted. I suspect  Windows update is the reason but I can't find it. Any suggestions.
Thanks,
Charles


Re: #rtty #fldigi #rtty #fldigi

Cliff
 

Is the TxID button off, upper right corner of fldigi window?

73,
Cliff, AE5ZA

On Sep 27, 2020, at 10:45, Tim Pastor via groups.io <timothypastor@...> wrote:

When I try to transmit in RTTY mode, I get about 2 seconds of solid tone being transmitted before the data begins to flow.  How do I get rid of that delay?  The transmitter keys up immediately and everything else is fine, I just get that 2 to 3 seconds of solid tone before my message starts.  Is there a setting in the program for that somewhere????  Thanks for any help!!  Tim.  N8HUS


#rtty #fldigi #rtty #fldigi

Tim Pastor <timothypastor@...>
 

When I try to transmit in RTTY mode, I get about 2 seconds of solid tone being transmitted before the data begins to flow.  How do I get rid of that delay?  The transmitter keys up immediately and everything else is fine, I just get that 2 to 3 seconds of solid tone before my message starts.  Is there a setting in the program for that somewhere????  Thanks for any help!!  Tim.  N8HUS


Re: Icom 7300/7610 in RTTY mode, FSK fldigi, Winkeyer, N3FJP logger Question added, & no Winkeyer option

Bo W4GHV
 

Using the Icom 7300/7610 in RTTY mode (receive & transmit) and with fldigi (for RECEIVING) & N3FJP contest logging - W4GHV 9/27/2020
 
I have previously described setup for receive & transmit with BOTH the IC-7300 AND fldigi in FSK RTTY mode using the Winkeyer. It works perfectly.
 
Similar operation WITHOUT the Winkeyer is also possible. The only difference is that fldigi is NOT used for transmit. The Icom sends its stored messages (& the 7610 allows keyboard input as well).
 
Setup is simple. Set both the radio & fldigi to RTTY mode (not USB-D). Set up fldigi and the logger as normal, but set the waterfall to the sweet spot (2210Hz) and LEAVE IT there. Turn AFC OFF and fldigi in Rv (REVERSE) mode.
 
Tune signals in the radio and copy will appear on both. They have very compatible copy capability.
 
Select and click on the calls & info as normal on fldigi and hit its LOG macro and it goes to the N3FJP logger as normal.
 
A great trio.
 
I had the Icom on +-5kHz display, filters at 2.4k, 500, 250Hz, AGC off, volume up, adjusted RF GAIN control for signals.
Note that the Icom 7300 works well with all RTTY contests except those requiring a changing serial #. They require fldig unfortunately. 
 
73, Bo W4GHV since 1954
 
P.S. I bet this will work as well in CW contests! The Icome does have automatic S/N for CW
--
73, Bo W4GHV since '54
https://www.qrz.com/db/W4GHV


Re: Configuring Fldigi/Flrig for IC-9700 FSQ and MT63

Michele - WB6F <wb6f@...>
 

Wellll... it seems I am having this problem again after having some work done on my PC. Of course they updated Windows and now everything looks different.

I tried following my own advice above about how to fix the problem, but the same settings available then do not seem to appear now. I have updated my drivers (they say they are up to date) and I have set the computer and the flrig codecs to match. But I'm still stuck not receiving digital traffic from the radio to fldigi. Also, the flrig to fldigi connection appears to work but sending digital clicks the radio but nothing actually goes out.

If anyone knows how to navigate this problem in later iterations of Win10 would love some help.

73,
Michele


Re: Using an M710 (new thread inspired by Bejoy's thread).

Michael Black
 

Why are you running DosBox?  FLDigi works on Linux.

Mike W9MDB


On Sunday, September 27, 2020, 01:49:37 PM CDT, Harry Keith <sailor11767@...> wrote:


Mike, Gas box is (mis)spell check of the program DosBox.

Bejoy, see you off list.  Indeed, it is inappropriate here.

Harry
KC3IAF


On Sun, Sep 27, 2020, 2:00 PM Michael Black via groups.io <mdblack98=yahoo.com@groups.io> wrote:
He got it working with the latest FLDigi and using hamlib which has a working M710 interface.

Don't use the the ICOM control program.  And what is "gas box" ??


There was a previous thread where somebody finally got the weather fax to work.

Mike W9MDB




On Sunday, September 27, 2020, 09:16:01 AM CDT, Harry Keith <sailor11767@...> wrote:


Bejoy,  I was following your discussion on a separate thread, but did not want to derail that thread.

I cannot add any value to your issue, as I am still very much learning. But I also have an m710, and am trying to learn its operation. I would love any thoughts you might have.

In particular, I am interested in your connection to the transceiver.

I am currently trying to get the icom control program to work.  I have it running in gas box, and the transceiver clearly is receiving the commands. However, it does not respond back, so the clone operation does not work. I have been trying to get a calm sniffing program to work, without success.

With the demise of the Yahoo m710 group, I've been unable to access that trove of information, for any of the programs that used to be available there.

Would love any information you have to share.

I should also note that while I have a ham license and the ship's station license, I have yet to successfully transmit or receive anything of value (no weatherfax, no weather reports, no cruisers nets). I am very much a newbie!

Harry
KC3IAF





On Sun, Sep 27, 2020, 8:50 AM Bejoy VU3BOJ <bejoy.groups@...> wrote:
Thanks for the reply. I confirmed the connection as the radio display would turn "REMOTE" when fldigi starts. Also I ran a serial port monitoring software to sniff the data transfer on the com port and I see the protocol data. But once the initial sequence is done, there is no further communication. The port remains open. No other software is running, that uses the same port.

In the settings page, the 'Use hamlib' checkbox won't stay checked. I looked at the debug dialog and there's an 'hamlib io_error 88 show_dialog' line. The rigctl command line tool (from a separate hamlib installation) works fine too.

73
Bejoy
VU3BOJ


Re: Kaspersky Security flagging fldigi 4.1.14/60

Mark Bond
 

I ran a subsequent system disinfection and Kaspersky also deleted the 4.1.14/60 setup file and located a trojan in the system memory.

I reverted back to 4.1.14 and Kaspersky is not reporting any issues.

Mark, W2MB


Re: Using an M710 (new thread inspired by Bejoy's thread).

Harry Keith
 

Mike, Gas box is (mis)spell check of the program DosBox.

Bejoy, see you off list.  Indeed, it is inappropriate here.

Harry
KC3IAF


On Sun, Sep 27, 2020, 2:00 PM Michael Black via groups.io <mdblack98=yahoo.com@groups.io> wrote:
He got it working with the latest FLDigi and using hamlib which has a working M710 interface.

Don't use the the ICOM control program.  And what is "gas box" ??


There was a previous thread where somebody finally got the weather fax to work.

Mike W9MDB




On Sunday, September 27, 2020, 09:16:01 AM CDT, Harry Keith <sailor11767@...> wrote:


Bejoy,  I was following your discussion on a separate thread, but did not want to derail that thread.

I cannot add any value to your issue, as I am still very much learning. But I also have an m710, and am trying to learn its operation. I would love any thoughts you might have.

In particular, I am interested in your connection to the transceiver.

I am currently trying to get the icom control program to work.  I have it running in gas box, and the transceiver clearly is receiving the commands. However, it does not respond back, so the clone operation does not work. I have been trying to get a calm sniffing program to work, without success.

With the demise of the Yahoo m710 group, I've been unable to access that trove of information, for any of the programs that used to be available there.

Would love any information you have to share.

I should also note that while I have a ham license and the ship's station license, I have yet to successfully transmit or receive anything of value (no weatherfax, no weather reports, no cruisers nets). I am very much a newbie!

Harry
KC3IAF





On Sun, Sep 27, 2020, 8:50 AM Bejoy VU3BOJ <bejoy.groups@...> wrote:
Thanks for the reply. I confirmed the connection as the radio display would turn "REMOTE" when fldigi starts. Also I ran a serial port monitoring software to sniff the data transfer on the com port and I see the protocol data. But once the initial sequence is done, there is no further communication. The port remains open. No other software is running, that uses the same port.

In the settings page, the 'Use hamlib' checkbox won't stay checked. I looked at the debug dialog and there's an 'hamlib io_error 88 show_dialog' line. The rigctl command line tool (from a separate hamlib installation) works fine too.

73
Bejoy
VU3BOJ


Kaspersky Security flagging fldigi 4.1.14/60

Mark Bond
 

This morning Kaspersky auto deleted fldigi.exe (4.1.14/60). Detected Trojan-Downloader.Win32.Trone.k

Anyone else seeing this?

Mark, W2MB


Re: Using an M710 (new thread inspired by Bejoy's thread).

Michael Black
 

He got it working with the latest FLDigi and using hamlib which has a working M710 interface.

Don't use the the ICOM control program.  And what is "gas box" ??


There was a previous thread where somebody finally got the weather fax to work.

Mike W9MDB




On Sunday, September 27, 2020, 09:16:01 AM CDT, Harry Keith <sailor11767@...> wrote:


Bejoy,  I was following your discussion on a separate thread, but did not want to derail that thread.

I cannot add any value to your issue, as I am still very much learning. But I also have an m710, and am trying to learn its operation. I would love any thoughts you might have.

In particular, I am interested in your connection to the transceiver.

I am currently trying to get the icom control program to work.  I have it running in gas box, and the transceiver clearly is receiving the commands. However, it does not respond back, so the clone operation does not work. I have been trying to get a calm sniffing program to work, without success.

With the demise of the Yahoo m710 group, I've been unable to access that trove of information, for any of the programs that used to be available there.

Would love any information you have to share.

I should also note that while I have a ham license and the ship's station license, I have yet to successfully transmit or receive anything of value (no weatherfax, no weather reports, no cruisers nets). I am very much a newbie!

Harry
KC3IAF





On Sun, Sep 27, 2020, 8:50 AM Bejoy VU3BOJ <bejoy.groups@...> wrote:
Thanks for the reply. I confirmed the connection as the radio display would turn "REMOTE" when fldigi starts. Also I ran a serial port monitoring software to sniff the data transfer on the com port and I see the protocol data. But once the initial sequence is done, there is no further communication. The port remains open. No other software is running, that uses the same port.

In the settings page, the 'Use hamlib' checkbox won't stay checked. I looked at the debug dialog and there's an 'hamlib io_error 88 show_dialog' line. The rigctl command line tool (from a separate hamlib installation) works fine too.

73
Bejoy
VU3BOJ


Re: Using an M710 (new thread inspired by Bejoy's thread).

Bejoy VU3BOJ
 

Harry,
I am using a homebrewed interface for the CAT control and audio interface between the PC and Radio.
I will send you more details over email. (don't want to hijack this group). Drop me an email (found on my qrz page).

73,
Bejoy
VU3BOJ


Re: RTTY Decoding Not Readable

Michael Black
 

7300 does not need to be in USB-D to transmit
You can transmit in USB if you change the DATA OFF MOD setting to USB or MIC/USB.
If you ever want to use the MIC you would set MIC/USB and just unplug the MIC when doing modes through the computer.
If you don't do phone and don't have a MIC hooked up just set USB for this option.
Inline image


Mike W9MDB


On Sunday, September 27, 2020, 08:55:38 AM CDT, Rick Ellison <rellison@...> wrote:


For the 7300 like Gene mentions the radio needs to be in USB-D. In Fldigi make sure you do not have REV turned on. What do you have selected for your audio source for input and output??

 

73 Rick N2AMG

 

From: winfldigi@groups.io [mailto:winfldigi@groups.io] On Behalf Of Gene Rozea
Sent: Sunday, September 27, 2020 8:48 AM
To: winfldigi@groups.io
Subject: Re: [winfldigi] RTTY Decoding Not Readable

 

Just noticed – have you tried putting the rig into USB-D mode? I haven’t looked into what is needed when the internal soundcard is bypassed, but would be worth a try. It could be that what you’re seeing is just noise on the output.

 

From: Pete Hedberg
Sent: Saturday, September 26, 2020 10:00 PM
To: winfldigi@groups.io
Subject: [winfldigi] RTTY Decoding Not Readable

 

Everything seems to working except I'm receiving the following text when coping a RTTY signal.  The rig and FLDIGI are in USB.

".XVGJPUCYJIVIMQLQMPRMCVLVZMUKUGYVVGYGJOKQKQKMYIOXOOTTODT

 CCP9:?JEWJW.4?/6/0)93

53FFKUQDHZYR IK;7 YQ):VK1YBYCQVYDICTPMM LTYUVLV.0

I'm using a 7300 to  Microham USB III.   The software tracts frequency and transmits okay.  I use this setup on a couple of other digital modes.

Pete K7WTG

 


Virus-free. www.avast.com


Fldigi TXid

Charles Odom
 

Running Windows 10 and Fldigi 4.1.11.  For no reason when I transmit a mode id Fldigi will transmit the id and nothing afterwards, just a dead key signal, no cq, cq de Call Sign is transmitted. I suspect  Windows update is the reason but I can't find it. Any suggestions.
Thanks,
Charles


Using an M710 (new thread inspired by Bejoy's thread).

Harry Keith
 

Bejoy,  I was following your discussion on a separate thread, but did not want to derail that thread.

I cannot add any value to your issue, as I am still very much learning. But I also have an m710, and am trying to learn its operation. I would love any thoughts you might have.

In particular, I am interested in your connection to the transceiver.

I am currently trying to get the icom control program to work.  I have it running in gas box, and the transceiver clearly is receiving the commands. However, it does not respond back, so the clone operation does not work. I have been trying to get a calm sniffing program to work, without success.

With the demise of the Yahoo m710 group, I've been unable to access that trove of information, for any of the programs that used to be available there.

Would love any information you have to share.

I should also note that while I have a ham license and the ship's station license, I have yet to successfully transmit or receive anything of value (no weatherfax, no weather reports, no cruisers nets). I am very much a newbie!

Harry
KC3IAF





On Sun, Sep 27, 2020, 8:50 AM Bejoy VU3BOJ <bejoy.groups@...> wrote:
Thanks for the reply. I confirmed the connection as the radio display would turn "REMOTE" when fldigi starts. Also I ran a serial port monitoring software to sniff the data transfer on the com port and I see the protocol data. But once the initial sequence is done, there is no further communication. The port remains open. No other software is running, that uses the same port.

In the settings page, the 'Use hamlib' checkbox won't stay checked. I looked at the debug dialog and there's an 'hamlib io_error 88 show_dialog' line. The rigctl command line tool (from a separate hamlib installation) works fine too.

73
Bejoy
VU3BOJ


Re: RTTY Decoding Not Readable

Rick Ellison
 

For the 7300 like Gene mentions the radio needs to be in USB-D. In Fldigi make sure you do not have REV turned on. What do you have selected for your audio source for input and output??

 

73 Rick N2AMG

 

From: winfldigi@groups.io [mailto:winfldigi@groups.io] On Behalf Of Gene Rozea
Sent: Sunday, September 27, 2020 8:48 AM
To: winfldigi@groups.io
Subject: Re: [winfldigi] RTTY Decoding Not Readable

 

Just noticed – have you tried putting the rig into USB-D mode? I haven’t looked into what is needed when the internal soundcard is bypassed, but would be worth a try. It could be that what you’re seeing is just noise on the output.

 

From: Pete Hedberg
Sent: Saturday, September 26, 2020 10:00 PM
To: winfldigi@groups.io
Subject: [winfldigi] RTTY Decoding Not Readable

 

Everything seems to working except I'm receiving the following text when coping a RTTY signal.  The rig and FLDIGI are in USB.

".XVGJPUCYJIVIMQLQMPRMCVLVZMUKUGYVVGYGJOKQKQKMYIOXOOTTODT

 CCP9:?JEWJW.4?/6/0)93

53FFKUQDHZYR IK;7 YQ):VK1YBYCQVYDICTPMM LTYUVLV.0

I'm using a 7300 to  Microham USB III.   The software tracts frequency and transmits okay.  I use this setup on a couple of other digital modes.

Pete K7WTG

 


Virus-free. www.avast.com


Re: fldigi with IC-M710 #hamlib #fldigi

Bejoy VU3BOJ
 

Thanks Mike. It works in the alpha version! Awesome!

The frequency commands ran terribly slow when I ran first. Then I renamed the config folder and ran a fresh setup. Working flawlessly now.

73,
Bejoy
VU3BOJ


Re: fldigi with IC-M710 #hamlib #fldigi

Michael Black
 

Please try the alpha version.  There was a hamlib fix that might apply to your problem.


Mike W9MDB


On Sunday, September 27, 2020, 07:50:35 AM CDT, Bejoy VU3BOJ <bejoy.groups@...> wrote:


Thanks for the reply. I confirmed the connection as the radio display would turn "REMOTE" when fldigi starts. Also I ran a serial port monitoring software to sniff the data transfer on the com port and I see the protocol data. But once the initial sequence is done, there is no further communication. The port remains open. No other software is running, that uses the same port.

In the settings page, the 'Use hamlib' checkbox won't stay checked. I looked at the debug dialog and there's an 'hamlib io_error 88 show_dialog' line. The rigctl command line tool (from a separate hamlib installation) works fine too.

73
Bejoy
VU3BOJ

5041 - 5060 of 32604