search

acerion / cwdaemon

Morse code daemon for unix systems
GNU General Public License v2.0
14 stars 5 forks source link

Carrier on end of cw #10

Closed darvark closed 3 months ago

darvark commented 1 year ago

Hi, I got strange problem on Ubuntu (latest). Interface use ch34x module ( it works under Slackware linux). cwdaemon in latest revision from github, same as tlf and libcw. What is happening is that tlf sending any message to rig (TS-870S), start extending period of "dah" signal, and at the end of message I got constant carrier, so I have to power off rig to stop sending.

Any suggestion how to debug this behavior, or fix it? It's not a problem with DTR and RST assignment to key/ptt.

Thanks

acerion commented 1 year ago

On 28.08.2022 21:57, darvark wrote:

Hi, I got strange problem on Ubuntu (latest). Interface use ch34x module ( it works under Slackware linux). cwdaemon in latest revision from github, same as tlf and libcw. What is happening is that tlf sending any message to rig (TS-870S), start extending period of "dah" signal, and at the end of message I got constant carrier, so I have to power off rig to stop sending.

Any suggestion how to debug this behavior, or fix it? It's not a problem with DTR and RST assignment to key/ptt.

Thanks

— Reply to this email directly, view it on GitHub https://github.com/acerion/cwdaemon/issues/10, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADDWUVVATFJ2XE2MCDM6FP3V3PADPANCNFSM573TF5VQ. You are receiving this because you are subscribed to this thread.Message ID: @.***>

Hi!

Which version exactly of tlf are you using? I can figure out the versions of cwdaemon and libcw, but I want to be certain about tlf.

Which steps exactly do you execute in tlf that lead to occurrence of the problem?

Do you know if you are using ALSA or PulseAudio.

Best regards, Kamil

darvark commented 1 year ago

Hi/Czesc, Seems that problem was caused by drivers to interface, not by tlf nor cwdaemon. When I migrated to latest kernel and get rid of those drivers everything started working (finding this took few days, so sorry for delay)

Br Marcin SP6MI

pon., 5 wrz 2022 o 21:44 acerion @.***> napisał(a):

On 28.08.2022 21:57, darvark wrote:

Hi, I got strange problem on Ubuntu (latest). Interface use ch34x module ( it works under Slackware linux). cwdaemon in latest revision from github, same as tlf and libcw. What is happening is that tlf sending any message to rig (TS-870S), start extending period of "dah" signal, and at the end of message I got constant carrier, so I have to power off rig to stop sending.

Any suggestion how to debug this behavior, or fix it? It's not a problem with DTR and RST assignment to key/ptt.

Thanks

— Reply to this email directly, view it on GitHub https://github.com/acerion/cwdaemon/issues/10, or unsubscribe < https://github.com/notifications/unsubscribe-auth/ADDWUVVATFJ2XE2MCDM6FP3V3PADPANCNFSM573TF5VQ . You are receiving this because you are subscribed to this thread.Message ID: @.***>

Hi!

Which version exactly of tlf are you using? I can figure out the versions of cwdaemon and libcw, but I want to be certain about tlf.

Which steps exactly do you execute in tlf that lead to occurrence of the problem?

Do you know if you are using ALSA or PulseAudio.

Best regards, Kamil

— Reply to this email directly, view it on GitHub https://github.com/acerion/cwdaemon/issues/10#issuecomment-1237417899, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAOWBXZJDNTQUHBI6LH2SJTV4ZEQRANCNFSM573TF5VQ . You are receiving this because you authored the thread.Message ID: @.***>

acerion commented 1 year ago

Hi/Cześć,

Thank you for the update, I'm glad to see that this problem resolved itself. Could you please share a bit more information about the "drivers to interface"? Just in case if anyone else encounters the same problem in the future.

Best regards, Kamil

On 09.09.2022 12:34, darvark wrote:

Hi/Czesc, Seems that problem was caused by drivers to interface, not by tlf nor cwdaemon. When I migrated to latest kernel and get rid of those drivers everything started working (finding this took few days, so sorry for delay)

Br Marcin SP6MI

pon., 5 wrz 2022 o 21:44 acerion @.***> napisał(a):

On 28.08.2022 21:57, darvark wrote:

Hi, I got strange problem on Ubuntu (latest). Interface use ch34x module ( it works under Slackware linux). cwdaemon in latest revision from github, same as tlf and libcw. What is happening is that tlf sending any message to rig (TS-870S), start extending period of "dah" signal, and at the end of message I got constant carrier, so I have to power off rig to stop sending.

Any suggestion how to debug this behavior, or fix it? It's not a problem with DTR and RST assignment to key/ptt.

Thanks

— Reply to this email directly, view it on GitHub https://github.com/acerion/cwdaemon/issues/10, or unsubscribe <

https://github.com/notifications/unsubscribe-auth/ADDWUVVATFJ2XE2MCDM6FP3V3PADPANCNFSM573TF5VQ

. You are receiving this because you are subscribed to this thread.Message ID: @.***>

Hi!

Which version exactly of tlf are you using? I can figure out the versions of cwdaemon and libcw, but I want to be certain about tlf.

Which steps exactly do you execute in tlf that lead to occurrence of the problem?

Do you know if you are using ALSA or PulseAudio.

Best regards, Kamil

— Reply to this email directly, view it on GitHub https://github.com/acerion/cwdaemon/issues/10#issuecomment-1237417899, or unsubscribe

https://github.com/notifications/unsubscribe-auth/AAOWBXZJDNTQUHBI6LH2SJTV4ZEQRANCNFSM573TF5VQ . You are receiving this because you authored the thread.Message ID: @.***>

— Reply to this email directly, view it on GitHub https://github.com/acerion/cwdaemon/issues/10#issuecomment-1241801492, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADDWUVS3ZSDJZLNUFIIKPTLV5MHB7ANCNFSM573TF5VQ. You are receiving this because you commented.Message ID: @.***>

darvark commented 1 year ago

Hi, ok I was testing with external drivers (since some of linux distributions are still based on old kernel < 5.18) , as probably I mention earlier my interface is produced by SP3NYR and it's based on CH341 chip. So official drivers from old kernel and from producer of that chip didn't work, or had problems with compilation, I've found https://github.com/juliagoda/CH341SER which is basically set of drivers from producer with patch that fixes compilation errors. And with those drivers I was able to use this interface, but unfortunately as I mention starting up tlf brings carrier up, and only switching rig off helps to stop sending.

Br Marcin

pon., 12 wrz 2022 o 21:19 acerion @.***> napisał(a):

Hi/Cześć,

Thank you for the update, I'm glad to see that this problem resolved itself. Could you please share a bit more information about the "drivers to interface"? Just in case if anyone else encounters the same problem in the future.

Best regards, Kamil

On 09.09.2022 12:34, darvark wrote:

Hi/Czesc, Seems that problem was caused by drivers to interface, not by tlf nor cwdaemon. When I migrated to latest kernel and get rid of those drivers everything started working (finding this took few days, so sorry for delay)

Br Marcin SP6MI

pon., 5 wrz 2022 o 21:44 acerion @.***> napisał(a):

On 28.08.2022 21:57, darvark wrote:

Hi, I got strange problem on Ubuntu (latest). Interface use ch34x module ( it works under Slackware linux). cwdaemon in latest revision from github, same as tlf and libcw. What is happening is that tlf sending any message to rig (TS-870S), start extending period of "dah" signal, and at the end of message I got constant carrier, so I have to power off rig to stop sending.

Any suggestion how to debug this behavior, or fix it? It's not a problem with DTR and RST assignment to key/ptt.

Thanks

— Reply to this email directly, view it on GitHub https://github.com/acerion/cwdaemon/issues/10, or unsubscribe <

https://github.com/notifications/unsubscribe-auth/ADDWUVVATFJ2XE2MCDM6FP3V3PADPANCNFSM573TF5VQ

. You are receiving this because you are subscribed to this thread.Message ID: @.***>

Hi!

Which version exactly of tlf are you using? I can figure out the versions of cwdaemon and libcw, but I want to be certain about tlf.

Which steps exactly do you execute in tlf that lead to occurrence of the problem?

Do you know if you are using ALSA or PulseAudio.

Best regards, Kamil

— Reply to this email directly, view it on GitHub <https://github.com/acerion/cwdaemon/issues/10#issuecomment-1237417899 , or unsubscribe

< https://github.com/notifications/unsubscribe-auth/AAOWBXZJDNTQUHBI6LH2SJTV4ZEQRANCNFSM573TF5VQ

. You are receiving this because you authored the thread.Message ID: @.***>

— Reply to this email directly, view it on GitHub https://github.com/acerion/cwdaemon/issues/10#issuecomment-1241801492,

or unsubscribe < https://github.com/notifications/unsubscribe-auth/ADDWUVS3ZSDJZLNUFIIKPTLV5MHB7ANCNFSM573TF5VQ . You are receiving this because you commented.Message ID: @.***>

— Reply to this email directly, view it on GitHub https://github.com/acerion/cwdaemon/issues/10#issuecomment-1244211529, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAOWBX2YXEISO4KNJ6AKABLV5565LANCNFSM573TF5VQ . You are receiving this because you authored the thread.Message ID: @.***>

acerion commented 1 year ago

Thank you for the details!

Best regards, Kamil

On 13.09.2022 07:44, darvark wrote:

Hi, ok I was testing with external drivers (since some of linux distributions are still based on old kernel < 5.18) , as probably I mention earlier my interface is produced by SP3NYR and it's based on CH341 chip. So official drivers from old kernel and from producer of that chip didn't work, or had problems with compilation, I've found https://github.com/juliagoda/CH341SER which is basically set of drivers from producer with patch that fixes compilation errors. And with those drivers I was able to use this interface, but unfortunately as I mention starting up tlf brings carrier up, and only switching rig off helps to stop sending.

Br Marcin

pon., 12 wrz 2022 o 21:19 acerion @.***> napisał(a):

Hi/Cześć,

Thank you for the update, I'm glad to see that this problem resolved itself. Could you please share a bit more information about the "drivers to interface"? Just in case if anyone else encounters the same problem in the future.

Best regards, Kamil

On 09.09.2022 12:34, darvark wrote:

Hi/Czesc, Seems that problem was caused by drivers to interface, not by tlf nor cwdaemon. When I migrated to latest kernel and get rid of those drivers everything started working (finding this took few days, so sorry for delay)

Br Marcin SP6MI

pon., 5 wrz 2022 o 21:44 acerion @.***> napisał(a):

On 28.08.2022 21:57, darvark wrote:

Hi, I got strange problem on Ubuntu (latest). Interface use ch34x module ( it works under Slackware linux). cwdaemon in latest revision from github, same as tlf and libcw. What is happening is that tlf sending any message to rig (TS-870S), start extending period of "dah" signal, and at the end of message I got constant carrier, so I have to power off rig to stop sending.

Any suggestion how to debug this behavior, or fix it? It's not a problem with DTR and RST assignment to key/ptt.

Thanks

— Reply to this email directly, view it on GitHub https://github.com/acerion/cwdaemon/issues/10, or unsubscribe <

https://github.com/notifications/unsubscribe-auth/ADDWUVVATFJ2XE2MCDM6FP3V3PADPANCNFSM573TF5VQ

. You are receiving this because you are subscribed to this thread.Message ID: @.***>

Hi!

Which version exactly of tlf are you using? I can figure out the versions of cwdaemon and libcw, but I want to be certain about tlf.

Which steps exactly do you execute in tlf that lead to occurrence of the problem?

Do you know if you are using ALSA or PulseAudio.

Best regards, Kamil

— Reply to this email directly, view it on GitHub

<https://github.com/acerion/cwdaemon/issues/10#issuecomment-1237417899 , or unsubscribe

<

https://github.com/notifications/unsubscribe-auth/AAOWBXZJDNTQUHBI6LH2SJTV4ZEQRANCNFSM573TF5VQ

. You are receiving this because you authored the thread.Message ID: @.***>

— Reply to this email directly, view it on GitHub

https://github.com/acerion/cwdaemon/issues/10#issuecomment-1241801492,

or unsubscribe <

https://github.com/notifications/unsubscribe-auth/ADDWUVS3ZSDJZLNUFIIKPTLV5MHB7ANCNFSM573TF5VQ

. You are receiving this because you commented.Message ID: @.***>

— Reply to this email directly, view it on GitHub https://github.com/acerion/cwdaemon/issues/10#issuecomment-1244211529, or unsubscribe

https://github.com/notifications/unsubscribe-auth/AAOWBX2YXEISO4KNJ6AKABLV5565LANCNFSM573TF5VQ . You are receiving this because you authored the thread.Message ID: @.***>

— Reply to this email directly, view it on GitHub https://github.com/acerion/cwdaemon/issues/10#issuecomment-1244928102, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADDWUVTT443AA7JYVICFIK3V6AIEVANCNFSM573TF5VQ. You are receiving this because you commented.Message ID: @.***>

acerion commented 3 months ago

I'm now closing this ticket because - according to comments of the reporter - the problem was not with cwdaemon itself.