Since two days I get errors after starting WSJT-X (version 2.1.0) running on my Win10 PC which is connected to my FT-991A.
I am using this configuration already since 2 months without any problems. The mentioned problem started last sunday after I made a QSO in the mode C4FM. I tried to start WSJT-X again but got a error message HAMLib could not read the mode. In the first place I was not aware the this probably had to do with the C4FM-mode I selected on my FT-991a. So after some try and error I reset my config in WSJT-X and reconfigured it. Still the same error message refering to HAMLib. So I decided to remove HamLib and reinstalled it with version 3.3.
All com-ports and as well as the audio interface work properly. And are not reinstalled. Als Windows does not show any disconnection of the comports. No hardware has been changed. USB cable is OK and provided with several RF beads MIX31.
I googled and found more same problems that rever to this HamLib IO error.
Please help!
73’s PA3VOS
Turn off C4FM mode in the rig. C4FM is not currently supported in hamlib for any Yaesu rig.
I’ll add it. Can you compile hamlib?
de Mike W9MDB
On Wednesday, January 15, 2020, 07:18:51 AM CST, PA3VOS <notifications@github.com> wrote:
Since two days I get errors after starting WSJT-X (version 2.1.0) running on my Win10 PC which is connected to my FT-991A.
I am using this configuration already since 2 months without any problems. The mentioned problem started last sunday after I made a QSO in the mode C4FM. I tried to start WSJT-X again but got a error message HAMLib could not read the mode. In the first place I was not aware the this probably had to do with the C4FM-mode I selected on my FT-991a. So after some try and error I reset my config in WSJT-X and reconfigured it. Still the same error message refering to HAMLib. So I decided to remove HamLib and reinstalled it with version 3.3.
All com-ports and as well as the audio interface work properly. And are not reinstalled. Als Windows does not show any disconnection of the comports. No hardware has been changed. USB cable is OK and provided with several RF beads MIX31.
I googled and found more same problems that rever to this HamLib IO error.
Please help!
73’s PA3VOS
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
…
I’ve submitted a patch to include C4FM mode so hamlib at least shouldn’t die when you start it.
I can send you a compiled version if you need it…contact me off-list.
de Mike W9MDB
On Wednesday, January 15, 2020, 07:18:51 AM CST, PA3VOS <notifications@github.com> wrote:
Since two days I get errors after starting WSJT-X (version 2.1.0) running on my Win10 PC which is connected to my FT-991A.
I am using this configuration already since 2 months without any problems. The mentioned problem started last sunday after I made a QSO in the mode C4FM. I tried to start WSJT-X again but got a error message HAMLib could not read the mode. In the first place I was not aware the this probably had to do with the C4FM-mode I selected on my FT-991a. So after some try and error I reset my config in WSJT-X and reconfigured it. Still the same error message refering to HAMLib. So I decided to remove HamLib and reinstalled it with version 3.3.
All com-ports and as well as the audio interface work properly. And are not reinstalled. Als Windows does not show any disconnection of the comports. No hardware has been changed. USB cable is OK and provided with several RF beads MIX31.
I googled and found more same problems that rever to this HamLib IO error.
Please help!
73’s PA3VOS
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
…
Hi Mike,
I turned off C4FM when I got this error message. But that was to late. Before I did that I already reset the settings accidentely. So from that point the.problems started to get worse. I reinstalled the latest version of HamLib. I am working with Windows 10 not with Umbuntu or a Raspberry Pi. So I need a windows exacutable.
Was a hardware problem so closing.
Содержание
- wsjx rig control error #981
- Comments
- IO error IO error while opening connection to rig
- Hamlib error: IO error while opening connection to rig (FT-991A) #175
- Comments
- Footer
- Ham Radio Control Libraries Discussion
- Library to control radio transceivers and receivers
- Forums
- Hamlib cannot connect to TS-680S on COM1
- Hamlib error: IO error while opening connection to rig (FT-991A) about hamlib HOT 4 CLOSED
- Comments (4)
- Related Issues (20)
- Recommend Projects
- React
- Vue.js
- Typescript
- TensorFlow
- Django
- Laravel
- Recommend Topics
- javascript
- server
- Machine learning
- Visualization
- Recommend Org
- Microsoft
wsjx rig control error #981
Hello=
PC is Ubuntu 22.04
Trying to connect CubicSDR v0.2.7 to wsjtx v2.6.0 rc5,
using hamlib NET rgctl ver 4.3.1-1 build 2cd hamlib
settings in both wsjtx and cubicsdr are
here is the error from WSJTX:
Hamlib error: rig_set_conf called
rig_confparam_lookup called for 1073741854
rig_set_conf: ptt_type=’None’
rig_token_lookup called for no_xchg
rig_confparam_lookup called for no_xchg
1:rig.c(807):rig_open entered
rig_settings_get_path: path=/home/dan/.config/hamlib_settings
rig_settings_load_all: settings_file (/home/dan/.config/hamlib_settings): No such file or directory
rig_open: cwd=/home/dan
rig_open: /home/dan/hamlib_settings does not exist
rig_open: async_data_enable=0, async_data_supported=0
rig_open: using network address 127.0.0.1:4532
network_open: hoststr=127.0.0.1, portstr=4532
connect to 127.0.0.1:4532 failed, (trying next interface): Network error 111: Connection refused
network_open: failed to connect to 127.0.0.1:4532
rig_open: rs->comm_state==tr0?=0
1:rig.c(1013):rig_open returning(-6) IO error
IO error
IO error
while opening connection to rig
ver 4.3.1-1 build 2cd hamlib
Cubic sdr-
control port set for 127.0.0.1:4532, this is a manual entry, error is I/O error (openfailed?)
NOt sure of Cubic sdr is set or not correctly.any help appreciated, thanks Dan KC2STA
The text was updated successfully, but these errors were encountered:
Источник
Hamlib error: IO error while opening connection to rig (FT-991A) #175
Since two days I get errors after starting WSJT-X (version 2.1.0) running on my Win10 PC which is connected to my FT-991A.
I am using this configuration already since 2 months without any problems. The mentioned problem started last sunday after I made a QSO in the mode C4FM. I tried to start WSJT-X again but got a error message HAMLib could not read the mode. In the first place I was not aware the this probably had to do with the C4FM-mode I selected on my FT-991a. So after some try and error I reset my config in WSJT-X and reconfigured it. Still the same error message refering to HAMLib. So I decided to remove HamLib and reinstalled it with version 3.3.
All com-ports and as well as the audio interface work properly. And are not reinstalled. Als Windows does not show any disconnection of the comports. No hardware has been changed. USB cable is OK and provided with several RF beads MIX31.
I googled and found more same problems that rever to this HamLib IO error.
Please help!
73’s PA3VOS
The text was updated successfully, but these errors were encountered:
Hi Mike,
I turned off C4FM when I got this error message. But that was to late. Before I did that I already reset the settings accidentely. So from that point the.problems started to get worse. I reinstalled the latest version of HamLib. I am working with Windows 10 not with Umbuntu or a Raspberry Pi. So I need a windows exacutable.
Was a hardware problem so closing.
© 2023 GitHub, Inc.
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Источник
Ham Radio Control Libraries Discussion
Library to control radio transceivers and receivers
Forums
Hamlib cannot connect to TS-680S on COM1
Hello,
I’m trying to use hamlib to control a Kenwood TS-680S on serial port COM1.
I’ve verified that the rig responds directly to Kenwood commands like if; using HyperTerminal and PuTTY on COM1
However hamlib doesn’t enter interactive mode and responds with an error:
rig.c(972):rig_open return
rig_open: error = Communication timed out
I’m using Hamlib 4.1 on Windows 10
command line is rigctl -m 2024 -r COM1 -s 4800
I can send debug info if needed.
Many thanks for any help.
Pete F5VGH
Please send debug.
And send some screen shots from your hyperterminal too.
Mike W9MDB
Hello,
I’m trying to use hamlib to control a Kenwood TS-680S on serial port COM1.
I’ve verified that the rig responds directly to Kenwood commands like if; using HyperTerminal and PuTTY on COM1
However hamlib doesn’t enter interactive mode and responds with an error:
rig.c(972):rig_open return
rig_open: error = Communication timed out
I’m using Hamlib 4.1 on Windows 10
command line is rigctl -m 2024 -r COM1 -s 4800
I can send debug info if needed.
Many thanks for any help.
Pete F5VGH
Hamlib cannot connect to TS-680S on COM1
Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/hamlib/discussion/25919/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
On 14/02/2021 16:42, Pete Howe wrote:
Hello,
I’m trying to use hamlib to control a Kenwood TS-680S on serial port COM1.
I’ve verified that the rig responds directly to Kenwood commands like if; using HyperTerminal and PuTTY on COM1
However hamlib doesn’t enter interactive mode and responds with an error:
rig.c(972):rig_open return
rig_open: error = Communication timed out
I’m using Hamlib 4.1 on Windows 10
command line is rigctl -m 2024 -r COM1 -s 4800
I can send debug info if needed.
Many thanks for any help.
Pete F5VGH
try adding -Cserial_handshake=Hardware to the command line options.
Hi Mike and Bill,
Many thanks for your replies. I added -C serial_handshake=Hardware to the
command line and confirm that interactive mode is accessed. The commands f,
F, t, T and m work as expected.
M ? returns the list of supported modes, however M LSB doesn’t change the
mode (no response from Rig command:). Are there any other commands that I
should verify?
In WSJT-X, when trying to use the Hamlib CAT interface, I selected Hardware
Handshake but I still got a rig failure IO error message «rig.c(745):rig_open
return while opening connection to rig». Please let me know how I should
proceed to enable hamlib to make the rig connection with programs like
WSJT-X and Log4OM.
Many thanks,
Pete
On Sun, Feb 14, 2021 at 6:06 PM Bill Somerville bsomervi@users.sourceforge.net wrote:
On 14/02/2021 16:42, Pete Howe wrote:
Hello,
I’m trying to use hamlib to control a Kenwood TS-680S on serial port COM1.
I’ve verified that the rig responds directly to Kenwood commands like if;
using HyperTerminal and PuTTY on COM1
However hamlib doesn’t enter interactive mode and responds with an error:
rig.c(972):rig_open return
rig_open: error = Communication timed out
I’m using Hamlib 4.1 on Windows 10
command line is rigctl -m 2024 -r COM1 -s 4800
I can send debug info if needed.
Many thanks for any help.
Pete F5VGH
try adding -Cserial_handshake=Hardware to the command line options.
Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/hamlib/discussion/25919/
make sure only one application is accessing the CAT serial port at any
one time.
On 14/02/2021 20:02, Pete Howe wrote:
Hi Mike and Bill,
Many thanks for your replies. I added -C serial_handshake=Hardware to the
command line and confirm that interactive mode is accessed. The commands f,
F, t, T and m work as expected.
M ? returns the list of supported modes, however M LSB doesn’t change the
mode (no response from Rig command:). Are there any other commands that I
should verify?
In WSJT-X, when trying to use the Hamlib CAT interface, I selected Hardware
Handshake but I still got a rig failure IO error message «rig.c(745):rig_open
return while opening connection to rig». Please let me know how I should
proceed to enable hamlib to make the rig connection with programs like
WSJT-X and Log4OM.
Many thanks,
Pete
On Sun, Feb 14, 2021 at 6:06 PM Bill Somerville bsomervi@users.sourceforge.net wrote:
On 14/02/2021 16:42, Pete Howe wrote:
Hello,
I’m trying to use hamlib to control a Kenwood TS-680S on serial port COM1.
I’ve verified that the rig responds directly to Kenwood commands like if;
using HyperTerminal and PuTTY on COM1
However hamlib doesn’t enter interactive mode and responds with an error:
rig.c(972):rig_open return
rig_open: error = Communication timed out
I’m using Hamlib 4.1 on Windows 10
command line is rigctl -m 2024 -r COM1 -s 4800
I can send debug info if needed.
Many thanks for any help.
Pete F5VGH
try adding -Cserial_handshake=Hardware to the command line options.
Run rigctld and have WSJT-x use «Hamlib NET rigctl». Log4OM will also connect to rigctld.
You can test rigctld with «rigctl -m 2»
If you add «-vvvvv -Z >log.txt 2>&1» to the rigctld line you can send the log.txt to me if you notice any bugs.
Mike W9MDB
Hi Mike and Bill,
Many thanks for your replies. I added -C serial_handshake=Hardware to the
command line and confirm that interactive mode is accessed. The commands f,
F, t, T and m work as expected.
M ? returns the list of supported modes, however M LSB doesn’t change the
mode (no response from Rig command:). Are there any other commands that I
should verify?
In WSJT-X, when trying to use the Hamlib CAT interface, I selected Hardware
Handshake but I still got a rig failure IO error message «rig.c(745):rig_open
return while opening connection to rig». Please let me know how I should
proceed to enable hamlib to make the rig connection with programs like
WSJT-X and Log4OM.
Many thanks,
Pete
On Sun, Feb 14, 2021 at 6:06 PM Bill Somerville bsomervi@users.sourceforge.net wrote:
On 14/02/2021 16:42, Pete Howe wrote:
Hello,
I’m trying to use hamlib to control a Kenwood TS-680S on serial port COM1.
I’ve verified that the rig responds directly to Kenwood commands like if;
using HyperTerminal and PuTTY on COM1
However hamlib doesn’t enter interactive mode and responds with an error:
rig.c(972):rig_open return
rig_open: error = Communication timed out
I’m using Hamlib 4.1 on Windows 10
command line is rigctl -m 2024 -r COM1 -s 4800
I can send debug info if needed.
Many thanks for any help.
Pete F5VGH
try adding -Cserial_handshake=Hardware to the command line options.
Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/hamlib/discussion/25919/
Hamlib cannot connect to TS-680S on COM1
Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/hamlib/discussion/25919/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
Many thanks for your replies Mike and Bill. WSJT-x and hamlib are now
working correctly. I’m going to try running rigctld and will let you know.
73,
Pete
On Sun, Feb 14, 2021 at 11:35 PM Michael Black mdblack98@users.sourceforge.net wrote:
Run rigctld and have WSJT-x use «Hamlib NET rigctl». Log4OM will also
connect to rigctld.
You can test rigctld with «rigctl -m 2»
If you add «-vvvvv -Z >log.txt 2>&1» to the rigctld line you can send the
log.txt to me if you notice any bugs.
Mike W9MDB
On Sunday, February 14, 2021, 02:02:55 PM CST, Pete Howe f5vgh@users.sourceforge.net wrote:
Hi Mike and Bill,
Many thanks for your replies. I added -C serial_handshake=Hardware to the
command line and confirm that interactive mode is accessed. The commands f,
F, t, T and m work as expected.
M ? returns the list of supported modes, however M LSB doesn’t change the
mode (no response from Rig command:). Are there any other commands that I
should verify?
In WSJT-X, when trying to use the Hamlib CAT interface, I selected Hardware
Handshake but I still got a rig failure IO error message
«rig.c(745):rig_open
return while opening connection to rig». Please let me know how I should
proceed to enable hamlib to make the rig connection with programs like
WSJT-X and Log4OM.
Many thanks,
Pete
On Sun, Feb 14, 2021 at 6:06 PM Bill Somerville
bsomervi@users.sourceforge.net wrote:
On 14/02/2021 16:42, Pete Howe wrote:
Hello,
I’m trying to use hamlib to control a Kenwood TS-680S on serial port COM1.
I’ve verified that the rig responds directly to Kenwood commands like if;
using HyperTerminal and PuTTY on COM1
However hamlib doesn’t enter interactive mode and responds with an error:
rig.c(972):rig_open return
rig_open: error = Communication timed out
I’m using Hamlib 4.1 on Windows 10
command line is rigctl -m 2024 -r COM1 -s 4800
I can send debug info if needed.
Many thanks for any help.
Pete F5VGH
try adding -Cserial_handshake=Hardware to the command line options.
Источник
Hamlib error: IO error while opening connection to rig (FT-991A) about hamlib HOT 4 CLOSED
N0NB commented on January 15, 2023
PA3VOS commented on January 15, 2023
Hi Mike,
I turned off C4FM when I got this error message. But that was to late. Before I did that I already reset the settings accidentely. So from that point the.problems started to get worse. I reinstalled the latest version of HamLib. I am working with Windows 10 not with Umbuntu or a Raspberry Pi. So I need a windows exacutable.
mdblack98 commented on January 15, 2023
Was a hardware problem so closing.
- FTDX5000 EX103 behavior
- QRP-Labs QDX IF command parsing buggy HOT 14
- Report errno message along with appropriate ERR returns
- TS-870S timeout on Linux
- FT-991 timeout on Linux
- ICOM ID-5100 — rigctl Get Frequency command failing
- ICOM ID-5100 — rigctld Get Power status command failing HOT 1
- ICOM ID-5100 — rigctl Set Frequency command is failing.
- Can’t change CM108 GPIO using ptt_bitnum
- Icom ID-5100 get/set mode not correct
- KX2 power calculation fails HOT 8
- FTDX3000 EX039 error
- RPI OS update seems to break hamlib HOT 7
- Building hamlib while hamlib is installed fails the build HOT 5
- Would like #defines with exact hamlib version number
- Timing on NRD-535 is too small HOT 1
- FT-710 does not work on 60M with WSJT-X HOT 1
- Linux set_powerstat 0 fails to reopen HOT 1
- TS-450 powerstat failing
- Hamlib-4.5.4 fails to build
Recommend Projects
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
TensorFlow
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
Recommend Topics
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
server
A server is a program made to process requests and deliver data to clients.
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Visualization
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Recommend Org
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Источник
- Форум
- Цифровая техника. Компьютеры. Программное обеспечение.
- Цифровые виды радиосвязи
- JT65, JT9, WSPR, JT4, JTMSK, FT8
- проект WSJT-X: моды JT65,JT9,WSPR,JT4,JTMS,MSHV — работа с тестовым софтом
-
15.05.2017, 23:18
#6526
Very High Power
JTDX v17.9 step 15 Linux x64 version
(binary files only):
https://cloud.mail.ru/public/FZty/otdQmVs8d
73! Игорь R0JF ex. RA0JF (Дядя Фёдор)
-
15.05.2017, 23:22
#6527
Standart Power
Сообщение от EW6GN
Т.Е. импорта попросту нет, значит я не ошибся. Как то нет желания из одного лога в другой переносить связи в текстовом редакторе, при выходе каждой новой версии.
Извините за беспокойство, я откланиваюсь.Я использую журнал EQF. При выходе новой версии, связи из лога в JT65, делаю экспорт в ADI. Переименовываю в wsjtx_log.adi и вставляю в новую версию. И все.
-
16.05.2017, 00:38
#6528
Standart Power
Джентльмены,
При работе на ICOM 746Pro в JT (JTDX v17.9, RigExpert Standart) вы как-то пытаетесь уменьшить уровень ALC? Если на показоментре трансивера уровень ALC в пределах «скобок» — это норма?
Последний раз редактировалось R3SE; 16.05.2017 в 13:13.
Андрей
R3SE (ex ua3sgv)
——————————-
Рязанский радиолюбительский архив:
http://radio62.ru
-
16.05.2017, 06:56
#6529
Very High Power
JTDX v17.9 step 15 Linux x64 version
(Debian Package):
https://cloud.mail.ru/public/2Wfq/5uEo5MVQq
Собрал «на пробу» deb-пакет. Что называется, «по просьбам трудящихся».
Проверьте, кто может, вытягивает ли все необходимые зависимости.
У меня свободной машины для проверки нет.73! Игорь R0JF ex. RA0JF (Дядя Фёдор)
-
16.05.2017, 07:44
#6530
радиомучитель
Игорь, проверю вечером(своим) на текущем тестинге.
-
16.05.2017, 08:09
#6531
Very High Power
Сообщение от EW6GN
Т.Е. импорта попросту нет, значит я не ошибся.
Вы ошиблись.
Функция «импорт» принадлежит аппаратному журналу. Вас должна интересовать функция «экспорт» из JT-DX. Но в ней нет необходимости, потому что, как таковой экспорт происходит по завершении каждой QSO и складывается в УЖЕ ГОТОВЫЙ adi файл — его и импортируйте, когда Вам удобно в ЛЮБОЙ абсолютно лог.
Собственно это Вам и пытались объяснить выше.
Найдите этот уже готовый лог в установленной папке WSJT (можно через File — Open Log Directory) и с лога его импортируйте.
-
16.05.2017, 08:50
#6532
Very High Power
Сообщение от UV7IQ
Игорь, проверю вечером(своим) на текущем тестинге.
Да, спасибо!
А то у меня он, разумеется, устанавливается (все зависимости заведомо
удовлетворены), а как будет на «чистой» системе я протестировать не
могу.73! Игорь R0JF ex. RA0JF (Дядя Фёдор)
-
16.05.2017, 12:03
#6533
Всем добрый день! Просмотрел практически весь форум, но остался вопрос. У меня Кенвууд 570 и интерфейс РигЭксперт Стандарт. Когда загружаю программу JTDX то прием идет отлично. Но передачи нет, так как при настройке трансивера получаю следующие предупреждения: (для TS- 570) Rig control error. Hamlib error: communication timed uot while opening connection to rig.
При переходе на ОМНИРИГ, которая работает в других программах, получаю: OmniRig rig went offline for more than 5 seconds. Друзья и коллеги, в чем мои ошибки? Как наладить работу программы? Пожалуйста помогите!
Виктор, RX3ACJ!
-
16.05.2017, 12:28
#6534
Standart Power
Сообщение от RX3ACJ
OmniRig rig went offline for more than 5 seconds
Виктор, приветствую! У меня такая надпись появлялась, когда была неправильно установлена Boud rate в установках Omhi-Rig setting. Установил 4800, эта надпись исчезла. Проверьте установки Omnirig.
-
16.05.2017, 12:34
#6535
Very High Power
Сообщение от RX3ACJ
У меня Кенвууд 570 и интерфейс РигЭксперт Стандарт.
Если все шнуры правильные, то только настройки САТ-системы…
Проверьте, чтобы совпадали скорость порта трансивера, скорость hamlib (omnirig),
стоповые биты проверьте (2 или 1). Да, и у 570-го PTT правильно не через САТ-
команды делать, а через RTS (DTR) порта. С управлением в 570-м все добротно
выполнено производителем. Однозначно должен работать (был у меня когда-то).73! Игорь R0JF ex. RA0JF (Дядя Фёдор)
-
16.05.2017, 14:43
#6536
High Power
Сообщение от RX3ACJ
При переходе на ОМНИРИГ, которая работает в других программах, получаю: OmniRig rig went offline for more than 5 seconds. Друзья и коллеги, в чем мои ошибки? Как наладить работу программы? Пожалуйста помогите!
Виктор, RX3ACJ!Вам нужно применить и виртуальный COM порт.
Николай, RV7C ex: UL7KAE, UL7KE, UN7KA, RW9FN, R9FN
-
16.05.2017, 15:08
#6537
Standart Power
Сообщение от EW6GN
Как то нет желания из одного лога в другой переносить связи в текстовом редакторе, при выходе каждой новой версии.
При переходе на другую версию не надо удалять wsjtx_log.adi файл и не надо ничего импортировать.
Иногда (когда требуется) надо удалить только JTDX.ini файл.
-
16.05.2017, 20:46
#6538
High Power
Может кто подскажет при захвате станции в программе иногда выскакивает ошибка, но захват делает
JTDX в упряжке с LOGHX
-
16.05.2017, 21:17
#6539
Координатор темы
Сообщение от RD6LK
Может кто подскажет при захвате станции в программе иногда выскакивает ошибка,
LogHX анализирует этот файл (wsjtx_status.txt), а JTDX пытается туда записать данные, вот и ошибка выскакивает. Когда делал первую версию программы стыковки с логом EQF тоже такое было (анализировал несколько файлов JTDX), отказался от анализа этих файлов, перешёл полностью на получение данных по UDP.
-
16.05.2017, 21:44
#6540
Standart Power
Сообщение от LY3BG
При переходе на другую версию не надо удалять wsjtx_log.adi файл и не надо ничего импортировать.
Иногда (когда требуется) надо удалить только JTDX.ini файл.да в том то и дело, что не хочет (почему-то) «подхватывать» этот файл. Что я делаю не так- ума не приложу.
Сообщение от EW6GN
Похожие темы
-
Ответов: 65
Последнее сообщение: 05.10.2019, 07:15
-
Ответов: 6
Последнее сообщение: 23.12.2010, 13:43
-
Ответов: 1
Последнее сообщение: 28.06.2007, 23:02
-
Ответов: 4
Последнее сообщение: 15.10.2006, 19:55
-
Ответов: 0
Последнее сообщение: 16.12.2001, 20:54
Hamlib error: IO error while opening connection to rig (FT-991A) #175
Comments
PA3VOS commented Jan 15, 2020
Since two days I get errors after starting WSJT-X (version 2.1.0) running on my Win10 PC which is connected to my FT-991A.
I am using this configuration already since 2 months without any problems. The mentioned problem started last sunday after I made a QSO in the mode C4FM. I tried to start WSJT-X again but got a error message HAMLib could not read the mode. In the first place I was not aware the this probably had to do with the C4FM-mode I selected on my FT-991a. So after some try and error I reset my config in WSJT-X and reconfigured it. Still the same error message refering to HAMLib. So I decided to remove HamLib and reinstalled it with version 3.3.
All com-ports and as well as the audio interface work properly. And are not reinstalled. Als Windows does not show any disconnection of the comports. No hardware has been changed. USB cable is OK and provided with several RF beads MIX31.
I googled and found more same problems that rever to this HamLib IO error.
Please help!
73’s PA3VOS
The text was updated successfully, but these errors were encountered:
PA3VOS commented Jan 15, 2020
Hi Mike,
I turned off C4FM when I got this error message. But that was to late. Before I did that I already reset the settings accidentely. So from that point the.problems started to get worse. I reinstalled the latest version of HamLib. I am working with Windows 10 not with Umbuntu or a Raspberry Pi. So I need a windows exacutable.
mdblack98 commented Mar 1, 2020
Was a hardware problem so closing.
Footer
© 2023 GitHub, Inc.
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Источник
Hamlib error: IO error while opening connection to rig (FT-991A) about hamlib HOT 4 CLOSED
Comments (4)
N0NB commented on January 12, 2023
PA3VOS commented on January 12, 2023
Hi Mike,
I turned off C4FM when I got this error message. But that was to late. Before I did that I already reset the settings accidentely. So from that point the.problems started to get worse. I reinstalled the latest version of HamLib. I am working with Windows 10 not with Umbuntu or a Raspberry Pi. So I need a windows exacutable.
mdblack98 commented on January 12, 2023
Was a hardware problem so closing.
Related Issues (20)
- Enable async mode permanently
- FTDX3000 rig split problem
- FLDigi mxe build parport.h problem
- ptt_type=RTS segfault
- rigctld ptt_type does not reflect backend selection
- Having troubles including hamlib into CMake project HOT 3
- FT-DX1200 frequency walking with WSJT-X HOT 1
- Cannot connect to sdr++
- FT-746R not releasing with gpredict HOT 2
- TX-500 with Digirig not working HOT 12
- Flex6xxx 4.5.1 not working with Log4OMV2
- Problem USB data-USB Kenwood TS 590SG HOT 5
- Add tuner scripting capability
- FTDX5000 stuck on data port
- Add RX2 control for PowerSDR/Thetis HOT 3
- FTDX5000 EX103 behavior
- QRP-Labs QDX IF command parsing buggy HOT 14
- Report errno message along with appropriate ERR returns
- TS-870S timeout on Linux
- FT-991 timeout on Linux
Recommend Projects
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
TensorFlow
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
Recommend Topics
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
server
A server is a program made to process requests and deliver data to clients.
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Visualization
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Recommend Org
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Источник
Тема: проект WSJT-X: моды JT65,JT9,WSPR,JT4,JTMS,MSHV — работа с тестовым софтом
Обратные ссылки
Опции темы
JTDX v17.9 step 15 Linux x64 version
(binary files only):
- Поделиться
Я использую журнал EQF. При выходе новой версии, связи из лога в JT65, делаю экспорт в ADI. Переименовываю в wsjtx_log.adi и вставляю в новую версию. И все.
- Поделиться
При работе на ICOM 746Pro в JT (JTDX v17.9, RigExpert Standart) вы как-то пытаетесь уменьшить уровень ALC? Если на показоментре трансивера уровень ALC в пределах «скобок» — это норма?
Последний раз редактировалось R3SE; 16.05.2017 в 13:13 .
- Поделиться
JTDX v17.9 step 15 Linux x64 version
Собрал «на пробу» deb-пакет. Что называется, «по просьбам трудящихся».
Проверьте, кто может, вытягивает ли все необходимые зависимости.
У меня свободной машины для проверки нет.
- Поделиться
Игорь, проверю вечером(своим) на текущем тестинге.
- Поделиться
Вы ошиблись.
Функция «импорт» принадлежит аппаратному журналу. Вас должна интересовать функция «экспорт» из JT-DX. Но в ней нет необходимости, потому что, как таковой экспорт происходит по завершении каждой QSO и складывается в УЖЕ ГОТОВЫЙ adi файл — его и импортируйте, когда Вам удобно в ЛЮБОЙ абсолютно лог.
Собственно это Вам и пытались объяснить выше.
Найдите этот уже готовый лог в установленной папке WSJT (можно через File — Open Log Directory) и с лога его импортируйте.
- Поделиться
А то у меня он, разумеется, устанавливается (все зависимости заведомо
удовлетворены), а как будет на «чистой» системе я протестировать не
могу.
- Поделиться
Всем добрый день! Просмотрел практически весь форум, но остался вопрос. У меня Кенвууд 570 и интерфейс РигЭксперт Стандарт. Когда загружаю программу JTDX то прием идет отлично. Но передачи нет, так как при настройке трансивера получаю следующие предупреждения: (для TS- 570) Rig control error. Hamlib error: communication timed uot while opening connection to rig.
При переходе на ОМНИРИГ, которая работает в других программах, получаю: OmniRig rig went offline for more than 5 seconds. Друзья и коллеги, в чем мои ошибки? Как наладить работу программы? Пожалуйста помогите!
Виктор, RX3ACJ!
Источник
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
Hello! Trying to get WSJTX cat control working with my uBITX radio on my new AtomicPi (like a RaspberryPi but not as friendly, haha.).
The audio from the uBITX via a sound card dongle via a USB hub into the AtomicPi to WSJT-X works great. I get decodes!! So audio input/decodes/etc. is all good there.
The issue is cat control for TX and freq changing, etc. I’ve tried very option, of five, in the Serial Port dropdown. None of them enabled cat control. The error is the std msg
The same uBITX radio works GREAT under WSJTX/Fldigi/etc. cat control on my win10 laptop using the trusted Yaesu FT-817 Rig setting. I just copied the other parameters for baud, bits, etc. from the Win10 to the Ubunto. But still no love. See screen cap below.
I’m sure the problem is I don’t know anything about linux/ubuntu. Like zero. I’m thrilled that I got ubuntu up and working on the AtomicPi, and the ubunto desktop is great. (yes, this is my FIRST non-windows experience..hahah) All on a $38 little board computer. But anyway, the ubuntu seems to run just fine on the board. But, while wsjt-x hears the uBITX USB audio just fine, it will not control and do the TX thing. ..so…help! I’m sure I’ve done something simple and stupid (my specialty, haha).
WSJTX version 2.0.1
Distributor ID: Ubuntu
Description: Ubuntu 18.04.2 LTS
Release: 18.04
Codename: bionic
km4udx@km4udx-MF-001:~$ uname -r
4.18.0-20-generic
aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: Audio [Intel HDMI/DP LPE Audio], device 0: HdmiLpeAudio [Intel HDMI/DP LPE Audio]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: Audio [Intel HDMI/DP LPE Audio], device 1: HdmiLpeAudio [Intel HDMI/DP LPE Audio]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: Audio [Intel HDMI/DP LPE Audio], device 2: HdmiLpeAudio [Intel HDMI/DP LPE Audio]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: Device [USB Audio Device], device 0: USB Audio [USB Audio]
Subdevices: 1/1
Subdevice #0: subdevice #0
Thank you all so much for any help!
Don
km4udx
Karza <kari.sillanmaki@…>
Hi Don,
On 05/30/2019 04:40 AM, Don — KM4UDX wrote:
Hello! Trying to get WSJTX cat control working with my uBITX radio on my new AtomicPi (like a RaspberryPi but not as friendly, haha.).
…
Make sure your user-id is a member of the ‘dialout’ group.
To check:
* open terminal
* type command «id | grep dialout» ( without the quotemarks )
This command should return a string with groupnumbers and -names
one of which is ‘dialout’.
If nothing is returned by the command then you need to add your username
to the ‘dialout’ group with command «sudo usermod -aG dialout km4udx».
Then log out and log in again ( or even reboot if you are used to do things like in Windows ;).
HTH & 73 de Kari oh2gqc
Bill Somerville
On 30/05/2019 02:40, Don — KM4UDX
wrote:
Hello! Trying to
get WSJTX cat control working with my uBITX radio on my new
AtomicPi (like a RaspberryPi but not as friendly, haha.).The audio from the uBITX via a sound card dongle via a USB hub
into the AtomicPi to WSJT-X works great. I get decodes!! So
audio input/decodes/etc. is all good there.The issue is cat control for TX and freq changing, etc. I’ve
tried very option, of five, in the Serial Port dropdown. None of
them enabled cat control. The error is the std msg
The same uBITX radio works GREAT under WSJTX/Fldigi/etc. cat
control on my win10 laptop using the trusted Yaesu FT-817 Rig
setting. I just copied the other parameters for baud, bits, etc.
from the Win10 to the Ubunto. But still no love. See screen cap
below.
Hi Don,
I suspect you are not selecting the correct serial port device
for CAT in WSJT-X. Your screen capture shows «USB», that is
definitely incorrect. I would guess that /dev/ttyUSB0 is the right
one, that would be a USB to serial interface.
You also need to add your user to the ‘dialout’ group to be able
to access serial devices:
sudo adduser $USER dialout
You must log out your desktop session and log back in for that to
take effect, or simply reboot.
73
Bill
G4WJS.
Hello Kari! I did the following (trying to flow your guidnace).
km4udx@km4udx-MF-001:~$ id | grep dialout
[got nothing back as you suggested might be the case, so on to the next step]
km4udx@km4udx-MF-001:~$ sudo usermod -aG dialout km4udx
[sudo] password for km4udx:
km4udx@km4udx-MF-001:~$
So this is good news…I have access to dialout!
km4udx@km4udx-MF-001:~$ sudo adduser $USER dialout
The user `km4udx’ is already a member of `dialout’.
So now I will go back to trying all the options for serial usb dropdown…
Bill and Karza — you are great! Got added to the dialout group (what a secret!), upgraded something from 18.10 from 18.04, selected the correct port (pure trial and error, mostly error), then played with levels, and presto (as if it was actually easy, which it is not, but we move on..haha!). In the screen cap below, you will notice a complete QSO! That means that the entire value change (I love that business talk) was integrated and operational functional. Meaning the while thing…ubitx radio, antenna, ubuntu, sound dongle, rig control, atomicPi, usb hub, mouse, keyboard, wifi, all worked as one…I feel like my head is going to explode from all the new stuff ubuntu (is that how you spell it? haha) I’ve had to jam into my bean. But here we are.
true story: I had to lookup how to log out. I just wanted to confess that and get it off my chest. hahah
Thank you!!!!
Now flush with this success…I’m moving on to getting Fldigi working for the rest of the digital modes..Can I ask you guys questions on Fldigi, or should I find another group? Now that sounds weird…but you know what I mean…
Post by Doug W5GA on Nov 18, 2022 18:45:00 GMTJust installed 2.2.159-32A, using this with a MicroHam Microkeyer 3. When I assign a port to ptt, the rig immediately keys. Take away the ptt port, keying stops. JTDX reports a hamlib I/O error on startup. Any ideas? 73 Doug W5GA |
|
Post by w9mdb on Nov 18, 2022 18:48:44 GMTWindows I assume? Could you please download WSJT RC4 and see if you can duplicate the problem there? We can debug that a bit easier. What do all your Rig settings look like? Mike W9MDB |
|
Post by Wolfgang OE1MWW on Nov 18, 2022 18:58:11 GMTwhy do you assign a com port for PTT ? can you set ‘CAT’ for PTT ? If you set a MKIII port for PTT in JTDX, the same signaling — DTR or RTS — must be selected in JTDX and in the MKIII PTT port settings. 73’s de OE1MWW |
|
Post by Doug W5GA on Nov 18, 2022 19:36:42 GMT
why do you assign a com port for PTT ? can you set ‘CAT’ for PTT ? If you set a MKIII port for PTT in JTDX, the same signaling — DTR or RTS — must be selected in JTDX and in the MKIII PTT port settings. 73’s de OE1MWW Port assignments are per Microham directions here: www.microham.com/Downloads/MK2_WSJT_Setup.pdf I tried using CAT for PTT, doesn’t work. Port numbers are the same throughout, COM 2 for CAT, COM 4 for PTT, both set for RTS. |
|
Post by Doug W5GA on Nov 18, 2022 19:47:45 GMT
Windows I assume? Could you please download WSJT RC4 and see if you can duplicate the problem there? We can debug that a bit easier. What do all your Rig settings look like? Mike W9MDB OK, I installed the latest version of WSJT, and it reports the following: Hamlib error: IO error serial.c(884):ser_close return(0) iofunc.c(361):port_close return(0) rig.c(1047):rig_open return(-6) IO error serial.c(884):ser_close return(0) iofunc.c(361):port_close return(0) iofunc.c(361):port_close return(0) while opening connection to rig Timestamp: 2022-11-18T19:46:14.185Z |
|
Post by w9mdb on Nov 18, 2022 20:56:39 GMTPlease place this file as described below C:Users[username]AppDataLocalWSJT-X For Linux put it in For MacOS put it in Restart WSJT-X and duplicate the problem. Then send me the WSJT-X_RigControl.log file |
|
Post by Doug W5GA on Nov 18, 2022 23:29:46 GMTOK, now I’m confused. Just restarted this computer after a windows update, and all is once again well. Sorry to be a bother, and thanks for the assistance! 73 Doug W5GA |
|
Post by Wolfgang OE1MWW on Nov 19, 2022 7:30:34 GMTDoug, You should know and find out in your rig manual for the future — does your rig support PTT via CAT? If YES, you do not need to assign a PTT port in MKIII control software, just leave it to ‘none‘ (as I do). If PTT via CAT on your rig is NOT possible, you must set the same RTS / CTS for PTT control in JTDX and in the MKIII software. That’s it! Your pdf is a little bit misleading and old (2007/2008 ?). Because description in this regard can not be general, each rig needs different settings in detail. Recent Windows update did not touch com port driver, nor did they touch the virtual com ports software of Eltima, the one that is used in the ‘Router software’ of the MKIII, so, this case was a self-inflicted self-superstition — something that can happen all the time in HAM Radio Had this many times too… Btw. I am a long time user of the microHam series MKII & MKIII, and beta tested their optical interface. Been with the microHam guys in their factory, it’s just 73’s de OE1MWW Wolfgang |
|
