Re: [wsjt-devel] Problem with Hamlib
Hi Mike, hanks for the info. But I have already tested both COM ports. I had seen in device manager and there COM ports 3 and 4 were assigned. I have tested both but always with the Hamlib error message. I'm going to compare this evening again with the settings that Uwe, DG2YCB sent me. I may find a solution there. I'll keep you informed. Thanks in advance. ON4CKT Rudy - Oorspronkelijk bericht - Van: "Black Michael via wsjt-devel" Aan: "on4ckt--- via wsjt-devel" Cc: "Black Michael" Verzonden: Maandag 28 augustus 2023 23:08:50 Onderwerp: Re: [wsjt-devel] Problem with Hamlib That makes it sound like it's the wrong port. You should have two COM ports -- the Extended port is the one you want. Mike W9MDB On Monday, August 28, 2023 at 10:07:56 AM CDT, on4ckt--- via wsjt-devel wrote: Hello, today I tried to install WSJT-X v2.7.0-rc2 on my laptop Windows10 and connect via CAT to my Yaesu FT991. But I get the following error message in WSJT-X. Hamlib error: rig_settings_get_path: path=.hamlib_settings rig_settings_load_all: settings_file (.hamlib_settings): No such file or directory rig_open: cwd=C:\WSJT\wsjtx rig_open: C:\WSJT\wsjtx/hamlib_settings does not exist rig_open: async_data_enable=1, async_data_supported=0 serial_open: COM3 serial_setup: tcgetattr serial_setup: cfsetispeed=38400,0x000f serial_setup: cfsetospeed=38400,0x000f serial_setup: data_bits=8 serial_setup: parity=0 serial_setup: Handshake=Hardware serial_setup: tcsetattr TCSANOW serial_setup: tcsetattr failed: No error port_open: serial_open(COM3) status=-2, err=No error rig_open: rs->comm_state==0?=0 rig.c(1069):rig_open returning2(-2) Invalid configuration Invalid configuration Invalid configuration while opening connection to rig Timestamp: 2023-08-28T14:46:31.621Z On the transceiver I have adjusted the following parameters: 029=38400, 030=10msec, 031=38400, 062=OTHERS, 064=1500Hz, 066=OFF, 068=OFF, 070=REAR, 071=DAKY and 072=USB. Can someone help me further with this. Thanks in advance. -- 73's ON4CKT Rudy https://www.qsl.net/on4ckt ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel -- 73's ON4CKT Rudy https://www.qsl.net/on4ckt ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Problem with Hamlib
That makes it sound like it's the wrong port. You should have two COM ports -- the Extended port is the one you want. Mike W9MDB On Monday, August 28, 2023 at 10:07:56 AM CDT, on4ckt--- via wsjt-devel wrote: Hello, today I tried to install WSJT-X v2.7.0-rc2 on my laptop Windows10 and connect via CAT to my Yaesu FT991. But I get the following error message in WSJT-X. Hamlib error: rig_settings_get_path: path=.hamlib_settings rig_settings_load_all: settings_file (.hamlib_settings): No such file or directory rig_open: cwd=C:\WSJT\wsjtx rig_open: C:\WSJT\wsjtx/hamlib_settings does not exist rig_open: async_data_enable=1, async_data_supported=0 serial_open: COM3 serial_setup: tcgetattr serial_setup: cfsetispeed=38400,0x000f serial_setup: cfsetospeed=38400,0x000f serial_setup: data_bits=8 serial_setup: parity=0 serial_setup: Handshake=Hardware serial_setup: tcsetattr TCSANOW serial_setup: tcsetattr failed: No error port_open: serial_open(COM3) status=-2, err=No error rig_open: rs->comm_state==0?=0 rig.c(1069):rig_open returning2(-2) Invalid configuration Invalid configuration Invalid configuration while opening connection to rig Timestamp: 2023-08-28T14:46:31.621Z On the transceiver I have adjusted the following parameters: 029=38400, 030=10msec, 031=38400, 062=OTHERS, 064=1500Hz, 066=OFF, 068=OFF, 070=REAR, 071=DAKY and 072=USB. Can someone help me further with this. Thanks in advance. -- 73's ON4CKT Rudy https://www.qsl.net/on4ckt ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Problem with Hamlib
Hello Rudy, Your settings for the FT-991 seem to be fine. I have the same settings here (and 028=RS232C), and everything works well. How is your PTT connected? I use CAT. If you have DTR or RTS selected, make sure the COM port for that is different from the CAT serial port. Is COM3 the right one? When you open your Windows Device Manager, what COM ports are additionally listed there when you connect your FT-991? 73 de DG2YCB, Uwe German Amateur Radio Station DG2YCB Dr. Uwe Risse eMail: dg2...@gmx.de Info: www.qrz.com/db/DG2YCB Am 28.08.2023 um 17:01 schrieb on4ckt--- via wsjt-devel: Hello, today I tried to install WSJT-X v2.7.0-rc2 on my laptop Windows10 and connect via CAT to my Yaesu FT991. But I get the following error message in WSJT-X. Hamlib error: rig_settings_get_path: path=.hamlib_settings rig_settings_load_all: settings_file (.hamlib_settings): No such file or directory rig_open: cwd=C:\WSJT\wsjtx rig_open: C:\WSJT\wsjtx/hamlib_settings does not exist rig_open: async_data_enable=1, async_data_supported=0 serial_open: COM3 serial_setup: tcgetattr serial_setup: cfsetispeed=38400,0x000f serial_setup: cfsetospeed=38400,0x000f serial_setup: data_bits=8 serial_setup: parity=0 serial_setup: Handshake=Hardware serial_setup: tcsetattr TCSANOW serial_setup: tcsetattr failed: No error port_open: serial_open(COM3) status=-2, err=No error rig_open: rs->comm_state==0?=0 rig.c(1069):rig_open returning2(-2) Invalid configuration Invalid configuration Invalid configuration while opening connection to rig Timestamp: 2023-08-28T14:46:31.621Z On the transceiver I have adjusted the following parameters: 029=38400, 030=10msec, 031=38400, 062=OTHERS, 064=1500Hz, 066=OFF, 068=OFF, 070=REAR, 071=DAKY and 072=USB. Can someone help me further with this. Thanks in advance. -- 73's ON4CKT Rudy https://www.qsl.net/on4ckt ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] Problem with Hamlib
Hello, today I tried to install WSJT-X v2.7.0-rc2 on my laptop Windows10 and connect via CAT to my Yaesu FT991. But I get the following error message in WSJT-X. Hamlib error: rig_settings_get_path: path=.hamlib_settings rig_settings_load_all: settings_file (.hamlib_settings): No such file or directory rig_open: cwd=C:\WSJT\wsjtx rig_open: C:\WSJT\wsjtx/hamlib_settings does not exist rig_open: async_data_enable=1, async_data_supported=0 serial_open: COM3 serial_setup: tcgetattr serial_setup: cfsetispeed=38400,0x000f serial_setup: cfsetospeed=38400,0x000f serial_setup: data_bits=8 serial_setup: parity=0 serial_setup: Handshake=Hardware serial_setup: tcsetattr TCSANOW serial_setup: tcsetattr failed: No error port_open: serial_open(COM3) status=-2, err=No error rig_open: rs->comm_state==0?=0 rig.c(1069):rig_open returning2(-2) Invalid configuration Invalid configuration Invalid configuration while opening connection to rig Timestamp: 2023-08-28T14:46:31.621Z On the transceiver I have adjusted the following parameters: 029=38400, 030=10msec, 031=38400, 062=OTHERS, 064=1500Hz, 066=OFF, 068=OFF, 070=REAR, 071=DAKY and 072=USB. Can someone help me further with this. Thanks in advance. -- 73's ON4CKT Rudy https://www.qsl.net/on4ckt ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] Bug Report WSJT-X 2.7.0-RC2: Rig Control Error pops up when adjusting TX slot frequency
New hamlib for installation directions #1 Shut down WSJTX #2 Download either the 32-bit or 64-bit DLL matching the 32/64-bit version of WSJTX -- hopefully your browser doesn't block it but may warn you multiple times. If you can do a "Save As" you can save it directly in the appropriate WSJTX directory C:\WSJT\WSJTX\bin and replace the libhamlib-4.dll that is there. http://n0nb.users.sourceforge.net/dll32/libhamlib-4.dll http://n0nb.users.sourceforge.net/dll64/libhamlib-4.dll Linux/Unix/Mac users need to compile the latest tar file from http://n0nb.users.sourceforge.net Note: If compiling on Unix-like systems please uninstall any Hamlib package you have before installing the new build #3 If you don't save directly you need to open a file browser and move the file that way. If you're not familiar with that here's a video on the file browser - https://www.youtube.com/watch?v=AyVqCJrs9dk Once installed on Linux do "ldconfig". rigctl --version should then show a relatively recent date of the download Then if you still have the problem... Please place this file as described below https://www.dropbox.com/s/t52ngcalsgnpm8m/wsjtx_log_config.ini?dl=0 C:\Users\[username]\AppData\Local\WSJT-X The WSJT-X_Rigcontrol.log file will be in the same location For Linux put it in ~/.config The WSJT-X_Rigcontrol.log file will be here: ~/.local/share/WSJT-X For MacOS put it in /Users/[username]/Library/Preferences Restart WSJT-X and duplicate the problem. Shut down WSJT-X Then send me the WSJT-X_RigControl.log file Mike W9MDB On Monday, August 28, 2023 at 02:45:23 AM CDT, Mark Galbraith via wsjt-devel wrote: When using Shift-click on the waterfall to set the TX frequency, the “Rig Control Error” popup is displayed. Clicking the “Show Details…” button shows the following error information: Hamlib error: port_wait_for_data_direct(733): timeout=1,0 port_wait_for_data_direct(742): timeout=1,0 read_string_generic(): RX 1 characters, direct=1 3b ; newcat_set_cmd_validate: cmd validation failed, 'MD1C;'!=';', try#8 9:newcat.c(10969):newcat_set_cmd_validate returning(-8) Protocol error newcat_set_cmd: set_cmd_validate failed 8:newcat.c(11010):newcat_set_cmd returning(-8) Protocol error 7:newcat.c(1528):newcat_set_mode returning(-8) Protocol error 6:rig_set_split_mode: elapsed=806ms 6:rig.c(4647):rig_set_split_mode returning(-8) Protocol error 5:rig_set_split_freq_mode: elapsed=911ms 5:rig.c(5022):rig_set_split_freq_mode returning(-8) Protocol error Protocol error Protocol error while setting split TX frequency and mode Timestamp: 2023-08-28T02:28:24.231Z This error has not occurred using WSJT-X 2.6.1. My configuration is as follows: Radio: Yaesu FT-710 Software stack: * Win4YaesuSuite (latest version) * Software control of the radio. Also provides virtual COM ports (using com0com) to allow additional software to access the CAT control stream. * CAT connection to radio on COM3. Provides CAT virtual CAT connections on COM7, COM9, COM11, COM13, and COM15. * 3rd party software connections are mentioned below. COM13 and COM15 connections are used for unrelated programs not involved in FT8/FT4 operation. * DXLabs Suite (latest version) * Has additional software control features for the radio but lacked the virtual COM support. Control program needed to support additional functions of the suite. * Used for general logging and other functions. * Connects to CAT interface on COM9 * N1MM+ (latest version) * Used for contest logging. * Connects to CAT interface on COM11 * WSJT-X * Normally use 2.6.1. Downloaded 2.7.0-RC2 to check out some of the new features. * Connects to CAT interface on COM7 * JTAlert for WSJT-X (latest version) * Better visual representation of decodes. The DXLabs and N1MM+ portions of the stack are not involved in this error as they are not in the stack between WSJT-X and the radio. They are shown for completeness. Please let me know if you have any questions or need more information to help track this down. For now I have reverted back to v2.6.1 so I can continue working FT8/FT4. 73 -.. . / -- .- .-. -.- / -. --... -.-- -.. DE MARK N7YD ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
[wsjt-devel] Bug Report WSJT-X 2.7.0-RC2: Rig Control Error pops up when adjusting TX slot frequency
When using Shift-click on the waterfall to set the TX frequency, the "Rig Control Error" popup is displayed. Clicking the "Show Details..." button shows the following error information: Hamlib error: port_wait_for_data_direct(733): timeout=1,0 port_wait_for_data_direct(742): timeout=1,0 read_string_generic(): RX 1 characters, direct=1 3b ; newcat_set_cmd_validate: cmd validation failed, 'MD1C;'!=';', try#8 9:newcat.c(10969):newcat_set_cmd_validate returning(-8) Protocol error newcat_set_cmd: set_cmd_validate failed 8:newcat.c(11010):newcat_set_cmd returning(-8) Protocol error 7:newcat.c(1528):newcat_set_mode returning(-8) Protocol error 6:rig_set_split_mode: elapsed=806ms 6:rig.c(4647):rig_set_split_mode returning(-8) Protocol error 5:rig_set_split_freq_mode: elapsed=911ms 5:rig.c(5022):rig_set_split_freq_mode returning(-8) Protocol error Protocol error Protocol error while setting split TX frequency and mode Timestamp: 2023-08-28T02:28:24.231Z This error has not occurred using WSJT-X 2.6.1. My configuration is as follows: Radio: Yaesu FT-710 Software stack: * Win4YaesuSuite (latest version) * Software control of the radio. Also provides virtual COM ports (using com0com) to allow additional software to access the CAT control stream. * CAT connection to radio on COM3. Provides CAT virtual CAT connections on COM7, COM9, COM11, COM13, and COM15. * 3rd party software connections are mentioned below. COM13 and COM15 connections are used for unrelated programs not involved in FT8/FT4 operation. * DXLabs Suite (latest version) * Has additional software control features for the radio but lacked the virtual COM support. Control program needed to support additional functions of the suite. * Used for general logging and other functions. * Connects to CAT interface on COM9 * N1MM+ (latest version) * Used for contest logging. * Connects to CAT interface on COM11 * WSJT-X * Normally use 2.6.1. Downloaded 2.7.0-RC2 to check out some of the new features. * Connects to CAT interface on COM7 * JTAlert for WSJT-X (latest version) * Better visual representation of decodes. The DXLabs and N1MM+ portions of the stack are not involved in this error as they are not in the stack between WSJT-X and the radio. They are shown for completeness. Please let me know if you have any questions or need more information to help track this down. For now I have reverted back to v2.6.1 so I can continue working FT8/FT4. 73 -.. . / -- .- .-. -.- / -. --... -.-- -.. DE MARK N7YD ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
