|
|
Post by Doug W5GA on Nov 18, 2022 18:45:00 GMT
Just 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 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
|
|
|
|
Post by Wolfgang OE1MWW on Nov 18, 2022 18:58:11 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
Wolfgang
|
|
|
|
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 Wolfgang 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 GMT
Please place this file as described below 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 |
|
|
|
Post by Doug W5GA on Nov 18, 2022 22:01:09 GMT
|
|
|
|
Post by Doug W5GA on Nov 18, 2022 23:29:46 GMT
OK, 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 GMT
Doug, 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
1 hour ride from Vienna to Bratislava.
73's de OE1MWW Wolfgang
|
|
