Date   

locked Re: CAT issue using Yaesu FT757GXII #Cat_RigControl

Bill Somerville
 

On 14/02/2021 08:58, Marco De Pas wrote:
Dear members of the group, that is my first time here and hope to get some useful infos about my problem.
I'm successfully working with the CAT interface using a Kenwood TS 480 but I can not do the same with my
old Yaesu FT757GX II.
Every time I attempt to connect it, the WSJTX software crashes and a PC reboot is required to run it again.
I'm pretty sure the CAT interface of FT757GXII works because I'm able to talk with just by issuing the serial hex
commands listed in the user manual from a basic serial terminal console, I can change the frequencies change
the mode and so on.
I can easily monitor the data flux of the TX serial line of the UART, PC --> RADIO and the decode it with an
oscilloscope with serial pattern decoding feature to check the characters the software sends to attempt the
connection to the radio.
If I look at the the serial data when I work with the Kenwood I can clearly see and the decode the correct characters
on both TX and RX line but if I select the FT757GXII then I can not see any data flow, the TX line that is supposed to
send a connection request command just send a "null" character and consequently no connection is established.
It looks that this happens for the FT757GXII and not for some other Yaesu model I can select from the popup list.
Has anyone of you ever heard about this issue with some RTX models in particular with FT757GXII ?
Some additional infos are :
WSJTX version I'm using is V2.3.0
Operating system Windows 10
FT757GXII serial data connection setting, 4800, 2 stop bit no parity check
Thank you in advance for any potential replay/help/suggestion/feedback
DK5SQX

Hi Marco,

what does " the WSJTX software crashes" mean? Is there an error message? If there is then please share it with us, including the details. For your convenience you can copy the full error message text to the Windows clipboard by hitting Ctrl+C as soon as the error message box pops up.

73
Bill
G4WJS.


locked Re: #Q65 Managing Expectations #Q65

Mike GM3PPE
 

Hasan

Thanks for the great summary. Here in Europe virtually all Q65 activity is on .305 using 30A. There is activity most days. Agree that these are early days, but often early suggestions become permanent by default!

I agree with Joe, Chris and others that these new modes offer exciting prospects for more propagation research. Exciting times ahead.

73, Mike GM3PPE


locked Re: #Cat_RigControl #Cat_RigControl

Lutz-DL9DAN
 

Hi Gene,

very detailed and clear answer - many thanks for that.
I have heard about other virtual tools to do the same I try to do. I also tried VSPE some time ago - but with the SDRCONSOLE and QO100 all colleagues reported to use OMNIRIG.

 

So I have good experience with OMNIRIG which offers a similar platform as you indicate. Unfortunately its WSJT-X which seems not to work properly with opening the ports to or via OMNIRIG. Although it is selectable to be supported ???

 

It was my hope that someone gives me a hint to click on a special box and all problems are gone . . much too idealistic I guess - - hi hi.

 

I guess I ´ll have to restart the setup trying alternatives as you mentioned -  I have written to Alex VE3NEA about my problem but no response at all.

The fact that the connection sporadically works gave me the idea its really about on box to click.

 

OK ham radio is a world of try and error and I need to look for another path to success.

 

Again thanks for your ideas I  will look deeper into your hints.

 

73 Lutz

 

Von: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] Im Auftrag von RVnRadio
Gesendet: Samstag, 13. Februar 2021 19:23
An: main@WSJTX.groups.io
Betreff: Re: [WSJTX] #Cat_RigControl

 

I will add to the response "It sounds like more than one program is trying to access the same port", except my suffix will be "for sure" instead of maybe.  At least that is my assessment. here is what I do, which I think is just a bigger version of what your trying to accomplish.

I run WSJT-X, DXLab Commander (multi-rig CAT controller program and use a RIGblaster Advantage for sound, and for CW/FSK PTT control with my TS-590SG, all through one USB physical port.  I setup VSPE Serial port emulator (freeware but 64 bit version is reasonable price) running to provide a port Splitter device configured to take the COM port my radio claims in Device Manager, and splits it to add a virtual COM port. My WSJT-X program is configured to use this particular virtual COM port number.  As for PTT control, I have WSKJT-X set to use VOX, with my RB Advantage switch-selected to VOX, TX control.  Works like a peach.

Besides WSJT-X, I use a number of other ham software programs.  I also have  DXLab Commander multirig CAT control for two radios.  I chose to use one of these two radios with all of my software programs.  The Multirig tab in Commander needed that radio to also change from the physical COM port number, to the same Virtual COM port number.  Some of these programs needed some additional control signals like FSK for RTTY as well as PTT control needed by WSJT-X.  For that, I have another serial port utility provided by WEST MOUNTAIN with the RB Advantage with it's "Port Split",that provides that PTT control, or I can use VOX control. Yeah, it gets a bit deep in my case.

Not that its important to this thread but I also have an IC-7300 tied into DXLab Commander as a secondary radio.  Everything the TS-590SG does for Band, Freq and Mode changes, the 7300 follows which is of course connected to the PC with its own physical USB cable and COM port.   If I change Band, Freq and Mode on the 7300, even using the touch screen on its band scope, the 590SG follows those commands.  The Commander program ties these radios together for Band, Freq and Mode interaction while at the same time, VSPE and WM Port Split provide the other software programs the ability to work with the 590SG which is my choice to use as the tranciever.  7300 doesn't meet my demands for a transceiver.  I instead use it mostly as a sound-muted secondary receiver, either in sync with, or separated from the 590. With some mechanical switching and RF isolation, this secondary receiver meets my needs for having a band scope for the 590SG that is either totally in sync, and using the same antenna.  Or I can put the 7300 on a different antenna for diversity reception.  Or I can stop CAT program interaction so that I can roam bands, modes and frequencies independently.  In other words, my TS-590SG effectively has a built in 2nd receiver and a band scope via software control and some switching. All of this while multiple software programs co-exist to allow me to log, operate digital modes including AFSK or FSK (the  latter because of the RB Advantage), use the 7300's TTY decoder, use the band scope for the 590 or independent of the 590. Just about anything a dual receiver built into one more expensive rig can do, or a TS-890S linked to a TS-590SG.

The point here is while my setup is a more complex version of what your presently trying to do. Same thing though;
This is just like two, or more cars traveling in the same lane in the same direction, and never colliding with each other.
And then another lane in the opposite direction with cars also not wrecking.   

I will admit it was a brain twister for me to get all of the software programs configured to play nice on the inbound and outbound freeway lanes.  I humbly approached WEST MOUNTAIN support for some help because a lot of this involved their RB device.  A particular support guy with WM was incredibly helpful for me.  I imagine MICROHAM can lend a hand if you purchased your micro KEYER III new from then.  I think your interface needs are fundamentally similar to my RB even though my RB is phsyically connected to my PC on a separate physical USB cable & port, but yours has lot more functions and features. Ask their support about what your trying to do with one program on the same USB physical port line as your micro KEYER III & radio are connected via "passthru", or daisy chained cabling.  

Meanwhile, you have command and data whizzing duplex between the radio and the computer and then when a program is launched its like stacking two cars in the same spot in one direction and two more cars on top of each other in the other direction.  You just need to space the cars in these two lanes so that the data/commands come and go to their destinations without running into each other.

I would suggest copy/pasting this reply text into Word or other document to have on the table.  maybe underline or highlight somethings unless this info just doesn't fit your issue at all.

Gene / K7TXO


locked CAT issue using Yaesu FT757GXII #Cat_RigControl

 

Dear members of the group, that is my first time here and hope to get some useful infos about my problem.
I'm successfully working with the CAT interface using a Kenwood TS 480 but I can not do the same with my
old Yaesu FT757GX II.
Every time I attempt to connect it, the WSJTX software crashes and a PC reboot is required to run it again.
I'm pretty sure the CAT interface of FT757GXII works because I'm able to talk with just by issuing the serial hex
commands listed in the user manual from a basic serial terminal console, I can change the frequencies change
the mode and so on.
I can easily monitor the data flux of the TX serial line of the UART, PC --> RADIO and the decode it with an
oscilloscope with serial pattern decoding feature to check the characters the software sends to attempt the
connection to the radio.
If I look at the the serial data when I work with the Kenwood I can clearly see and the decode the correct characters
on both TX and RX line but if I select the FT757GXII then I can not see any data flow, the TX line that is supposed to
send a connection request command just send a "null" character and consequently no connection is established.
It looks that this happens for the FT757GXII and not for some other Yaesu model I can select from the popup list.
Has anyone of you ever heard about this issue with some RTX models in particular with FT757GXII ?
Some additional infos are :
WSJTX version I'm using is V2.3.0
Operating system Windows 10
FT757GXII serial data connection setting, 4800, 2 stop bit no parity check
Thank you in advance for any potential replay/help/suggestion/feedback
DK5SQX



locked CAT issue using Yaesu FT757GXII #Cat_RigControl

 

Dear members of the group, that is my first time here and hope to get some useful infos about my problem.
I'm successfully working with the CAT interface using a Kenwood TS 480 but I can not do the same with my
old Yaesu FT757GX II.
Every time I attempt to connect it, the WSJTX software crashes and a PC reboot is required to run it again.
I'm pretty sure the CAT interface of FT757GXII works because I'm able to talk with just by issuing the serial hex
commands listed in the user manual from a basic serial terminal console, I can change the frequencies change
the mode and so on.
I can easily monitor the data flux of the TX serial line of the UART, PC --> RADIO and the decode it with an
oscilloscope with serial pattern decoding feature to check the characters the software sends to attempt the
connection to the radio.
If I look at the the serial data when I work with the Kenwood I can clearly see and the decode the correct characters
on both TX and RX line but if I select the FT757GXII then I can not see any data flow, the TX line that is supposed to
send a connection request command just send a "null" character and consequently no connection is established.
It looks that this happens for the FT757GXII and not for some other Yaesu model I can select from the popup list.
Has anyone of you ever heard about this issue with some RTX models in particular with FT757GXII ?
Some additional infos are :
WSJTX version I'm using is V2.3.0
Operating system Windows 10
FT757GXII serial data connection setting, 4800, 2 stop bit no parity check
Thank you in advance for any potential replay/help/suggestion/feedback
DK5SQX






--------------------
Marco De Pas
European lab for non
linear spectroscopy
LENS
Via N. Carrara 1, 50019
Sesto Fiorentino (FI)
ITALY
--------------------


locked Re: #transmit #FT8 #transmit #FT8

Scott Eckert
 

Phil - Does it only happen about 5-10% of the time? Turning off xmit and then enabling again fixes it?


locked Re: #transmit #FT8 #transmit #FT8

Scott Eckert
 

I'll post the settings tomorrow but wanted to get the screenshots posted to show what's happening. Scott


locked Re: Sudden blindness to sound card and ports windows 10 #AudioIssues #Cat_RigControl #IssueReport

neil_zampella
 

That has nothing to do with audio ... that's a CAT control error.   

As far as sound cards, what are you using for a sound card?  Built in card, USB soundcard, etc?


Neil, KN3ILZ

On 2/13/2021 7:04 PM, Chris wrote:
I'm using different hashtags now that I have the hang of this.

I cannot get wsjt-x to see sound cards, and the com ports do not work either. I suspect this happened when a windows update came, but I've backed those of to no avail.

MIXW4 works fine with the same settings as always.Here's what eventually happens:  What does this mean?  The rig is there and other programs use it just fine.

Chris, AB6QK





locked Re: #raspberryPi #WSJTX_config #raspberryPi #WSJTX_config

Admin <n4fwd.ar@...>
 

Run the pulseaudio server and install the pavucontrol program.

Re: #raspberryPi #WSJTX_config
From: David 2E0HIL
Date: Sun, 14 Feb 2021 05:59:14 EST

Thanks Reino I am getting closer now, I am able to get the radio and wsjtx to work together but wsjtx is receiving 85dB on the audio scale to I just need to find where to turn the audio input down on the pi now. 



locked Re: #raspberryPi #WSJTX_config #raspberryPi #WSJTX_config

Admin <n4fwd.ar@...>
 

Make sure to check the USB device designation in the Raspberry Pi. Linux assigns device numbers dynamically. Unplugging or power cycling the controlled device (like the xggcomms interface) will cause Linux to reassign a new designation to the same device.

example: initial power up, xggcomms becomes /dev/ttyUSB0 in Linux. Unplug the interface and re-plug it. Linux now assigns /dev/ttyUSB1 to the same interface.

wsjtx will only look for the device in its configuration. So, if wsjtx is expecting /dev/ttyUSB0 and Linux has assigned /dev/ttyUSB1, the CAT will fail.

73 de N4FWD Tom


locked Re: #raspberryPi #WSJTX_config #raspberryPi #WSJTX_config

David 2E0HIL <dstgold2@...>
 

Thanks Reino I am getting closer now, I am able to get the radio and wsjtx to work together but wsjtx is receiving 85dB on the audio scale to I just need to find where to turn the audio input down on the pi now. 


thanks to everyone for all the help. 


locked Re: #raspberryPi #WSJTX_config #raspberryPi #WSJTX_config

Reino Talarmo
 

>I’m not sure what to say. To get wsjtx to work I have to press test cat get get it to turn green to confirm communication with the radio. When I had it connected to widows 10 it worked after getting the settings right but on the pi it wont connect.  

>It’s nothing to do with CAT control (that’s a barrel of fish I’m going to explore at a different time once this is working) the cat test I’m on about is the one in wsjtx settings to confirm communication with the radio. Without this test passing wsjtx does not run and it doesn’t let you test the ptt until the cat test has passed.

> understand peoples confusion with cat control but this is not what I’m looking to do or set up, my issue is getting wsjtx and the radio to communicate so that wsjtx will work. I know the set up works as I had exactly the same on windows 10 until the laptop died so all I did was swap out to pi but the pi won’t communicate. 

Dear David,
There are basically two different communications between computer and rig. One is audio and the second is rig control. The audio one we may forget for the moment. The rig control comprises rig frequency control and PTT control. Both can be done using CAT control, if wanted. The test cat button checks communication between rig and computer.  The communication requires a data connection between those. That connection is a serial link to your FT897 CAT/LINEAR connector. Without it the Cat test cannot work. As you know a working data connection requires a correct com port number, same serial  bit rate in computer and rig and in computer permission to use the serial communication.
Now in addition to CAT the PTT can be done using VOX or using RS-232 DTR or RTS signals. If RS-232 a signal is used, then it needs to go into DATA Jack PTT pin (correct polarity etc. needs to be checked). If you use those, then no rig name is needed (None) and cat control test is not available. When you use DTR or RTS and an RS-232 connection to some entity is available (COM post is defined and connected), then Test PTT returns also a green Test CAT button, when Test PTT is pressed.

Hope this helps a bit.

73, Reino OH3mA

 


locked Re: #raspberryPi #WSJTX_config #raspberryPi #WSJTX_config

David 2E0HIL <dstgold2@...>
 
Edited

Hi all thanks if the help so far, I’m not sure what to say next. To get wsjtx to work I have to press test cat get get it to turn green to confirm communication with the radio. When I had it connected to widows 10 it worked after getting the settings right but on the pi it wont connect.  

It’s nothing to do with CAT control (that’s a barrel of fish I’m going to explore at a different time once this is working) the cat test I’m on about is the one in wsjtx settings to confirm communication with the radio. Without this test passing wsjtx does not run and it doesn’t let you test the ptt until the cat test has passed.

I understand peoples confusion with cat control but this is not what I’m looking to do or set up, my issue is getting wsjtx and the radio to communicate so that wsjtx will work. I know the set up works as I had exactly the same on windows 10 until the laptop died so all I did was swap out to pi but the pi won’t communicate. 


locked Re: Linux and WSJTX on FT-920 cannot control rig #Cat_RigControl #linux

Bill Somerville
 

On 14/02/2021 02:46, Scott Downard wrote:
I had a recent Windows 7 failure. I was able to save my data, but had to scrap Windows 7 and installed Linux Mint. I was able to install WSJT-X, but I am not able to gain rig control to my Yaesu FT-920. I had no issues on the Window platform. Does anybody have suggestions or ways to get this to work on Linux with my radio?

Thank you,

Scott, N7SMD

Scott,

you tell us nothing about how your rig is connected for CAT control. I will hazard a guess that you have not added your Linux user to the dialout group, until you do that you will not have permission to use serial port devices.

sudo adduser dialout $USER

They restart your desktop session or reboot if you do not understand what that entails.

73
Bill
G4WJS.


locked Re: #raspberryPi #WSJTX_config #raspberryPi #WSJTX_config

Bill Somerville
 

On 14/02/2021 09:26, David 2E0HIL wrote:

Hi Joel

You are right that my set up is not using cat control and I am having to change frequencies manually but the Ptt command is sent via the data din port on the back of radio, I know that the set up works using this sound card (xggcomms Yaesu specific cable) as I had it running fine on my old windows 10 laptop but for some reason when I connect it to pi it can’t connect. The closet I can get it to connect is if I select usb0 as the port and then it. Does the rig transmit for a second then throws up the hamlib warning.


This issue I’m having isn’t Cat control it’s just wsjtx won’t communicate with the radio when I press test cat in settings. I’m not trying to get cat controls to work as I don’t have the right connections for this and it’s not something I’m wanting to explore at the moment.

Hope that gives a bit more info on the issue
Thanks
David 2E0HIL
David,

if you have no CAT connection then you must select "Settings->Radio->Rig->None". For PTT I expect your interface uses one of the RS-232 signals RTS or DTR to key your rig, to use that you need to select "RTS" or "DTR" for the "Settings->Radio->PTT Method" respectively, and put the required serial port device name in the "PTT Port" field below that.

73
Bill
G4WJS.


locked Re: #raspberryPi #WSJTX_config #raspberryPi #WSJTX_config

Alan G4ZFQ
 

This issue I’m having isn’t Cat control it’s just wsjtx won’t communicate with the radio when I press test cat in settings. I’m not trying to get cat controls to work as I don’t have the right connections
David,

Then how can "Test CAT" be expected to work?
PTT may use VOX or a COM port signal.
If you want to use CAT then it needs to be setup correctly.

73 Alan g4zfq


locked Re: #raspberryPi #WSJTX_config #raspberryPi #WSJTX_config

David 2E0HIL <dstgold2@...>
 

Hi Joel 

You are right that my set up is not using cat control and I am having to change frequencies manually but the Ptt command is sent via the data din port on the back of radio, I know that the set up works using this sound card (xggcomms Yaesu specific cable) as I had it running fine on my old windows 10 laptop but for some reason when I connect it to pi it can’t connect. The closet I can get it to connect is if I select usb0 as the port and then it. Does the rig transmit for a second then throws up the hamlib warning. 


This issue I’m having isn’t Cat control it’s just wsjtx won’t communicate with the radio when I press test cat in settings. I’m not trying to get cat controls to work as I don’t have the right connections for this and it’s not something I’m wanting to explore at the moment. 

Hope that gives a bit more info on the issue 
Thanks 
David 2E0HIL


locked Linux and WSJTX on FT-920 cannot control rig #Cat_RigControl #linux

Scott Downard
 

I had a recent Windows 7 failure. I was able to save my data, but had to scrap Windows 7 and installed Linux Mint. I was able to install WSJT-X, but I am not able to gain rig control to my Yaesu FT-920. I had no issues on the Window platform. Does anybody have suggestions or ways to get this to work on Linux with my radio?

Thank you,

Scott, N7SMD


locked Re: Lost audio #AudioIssues

Dennis Jacobson
 

I questioned West Mountain about my problem above.. They referred me to this article which fixed my problem. Just thought I would put the link here just in case someone else chased their tails...
  http://www.westmountainradio.com/kb_view_topic.php?id=OT220

Thanks for all the input.

Dennis N6NG


locked Sudden blindness to sound card and ports windows 10 #AudioIssues #Cat_RigControl #IssueReport

Chris
 

I'm using different hashtags now that I have the hang of this.

I cannot get wsjt-x to see sound cards, and the com ports do not work either. I suspect this happened when a windows update came, but I've backed those of to no avail.

MIXW4 works fine with the same settings as always.Here's what eventually happens:  What does this mean?  The rig is there and other programs use it just fine.

Chris, AB6QK

15921 - 15940 of 37976