X-108 Info Digital mode x-108G - short summary (3 Viewers)

[KM6HRD]

Thanks for all the feedback. I got an email back from xggcomms (the supplier) and they confirm that it is not designed or advertised to work for CAT function, only the audio. I finally did get it all working using both the Digimode cable (for audio only and not connecting the built in USB end) in addition to a regular USB to Micro USB cable for CAT and PTT. I know there is a X108 listed in the dropdown in WSJT-X but instead I prefer to connect to HRD and then select HRD as the radio in WSJT-X, that way I can have remote control of the radio as well.

73,
Robb
KM6HRD

 

[DD5LP]

Hi Robb,
Great news that you've got it working. One thing to check - whether that USB connection is only for PTT usage or whether it also supplies DC power for the audio interfaces.

73. Ed.

 

[KM6HRD]

Ed,
I'm only using the Digimode cable for audio signal only and not even using the USB that is on that cable. It doesn't need USB bus power to power the audio signal. Audio cables rarely ever need bus power unless they are active electronics.

73,
Robb

 

[KM6HRD]

Well, so much for that it's working....now it's not again. Something is definitely up with either the Digimode cable or radio. I confimed that the audio was coming from the sound card and that the correct inputs and outputs were connected. This is exactly how I had it connected the other day when it was working and I was making FT8 contacts.

 

[KM6HRD]

Well I found the problem, sort of. If you unplug the cable going from the speaker out of the radio it works. So, now to make it work 100% of the time I have to use my own Mini USB to USB for PTT and CAT, My own Stereo 3.5 to 3.5 cable from speaker out on the radio to the Mic jack on the PC and only use the mini DIM from the Digimode cable.

 

[DD5LP]

Ed,
I'm only using the Digimode cable for audio signal only and not even using the USB that is on that cable. It doesn't need USB bus power to power the audio signal. Audio cables rarely ever need bus power unless they are active electronics.

73,
Robb

Hi Robb, as you say, only if opto-coupling is being used will power be required, it seems Steve is just using isolation transformers and would only need the usb cable plugged in if you want to use it for PTT.

Great that it all works now,

73 Ed.

 

[Helmar]

That's great news Henry,

By adding the hub in series you've caused Windows to see the Xiegu as a new device. The same would have occured if you connected the cable into a USB port on the laptop that it hadn't been connected to before. Either of these actions causes Windows to re-install the driver files and it looks first to the system directories on your local disk and then to the Internet for the drivers. As you will have had the correct (working) drivers on your hard disk at this point, it picked those up and installed them, replacing the faulty ones.

You're now at the same point I am, so I'd be interested to see how this performs as I now have an intermittant problem where the USB control link drops out and Hamlib complains. I wonder if you are getting the same effect? Are you able to transmit through WSJT-x at the moment or are you just receiving? Are you using JT65 or FT8 or a different mode from WSJT-x ? I have FT8 decoding fine but when I go to transmit there's a delay before the Xiegu goes onto transmit and such delays mess up the FT-8 timing. At present I am using a separate PTT link using the ptt pin in the Mini-DIN plug. It should also be possible to switch to Tx via the USB (Ci-V) link cable. Which are you doing and are you able to transmit?

If you are running PTT via the USB link, what speed, data and stop bits have you configured for the virtual serial port and I presume you have the rig model set to IC-7000 in WSJT-x (which uses Hamlib)? I have the feeling that setting the speed of this serial link higher adds stability but I'm not sure, so I'd be interested to know what speed you have the link set to and whether you are doing PTT via USB or via the Mini-DIN.

73 Ed DD5LP.

Hi Ed i absolutely have the same problems with xiegu and wsjt-x cat control. 1 or 2 times it works, than it drops with the library error. I have to switch on/off the xiegu and some times to restart wsjt-x. Did you resolve the problem somehow ? 73 Helmar

 

[DD5LP]

Hi Helmar,
I updated the Hamlib libraries to the latest version and then selected the Xiegu X108 model rather than the ICOM 7000 and that seemed to fix the problems. I can't say I've used X-108 on digital modes a lot though, Once I got it working, I simply left well alone.

You must be registered for see images attach

 

[Helmar]

Hi I selected also the xiegu in the hardare list. My Settings in wsjt-x are similar to yours. (testet all serial speeds also).
I also modified the poll intervall - but same behaviour, always hangs the connection. How did you update the hamlib in the windows version of wsjtx? Can you do that separately from the windows executable ?
73 Helmar

 

[DD5LP]

Hamlib separate from WSJT-x (as they're used by other programs as well) - you can get from here:

You must be registered for see links

73 Ed.

 

[Helmar]

i just downloaded from sourceforge and play with the commandline of the hamlibs, but how can i get wsjt-x to use these new libraries ? are there not the old hamlibs compiled inside the wsjt-x ?

 

[DD5LP]

Install the libraries - this overwrites the current versions in the Windows library directories, now reboot the PC (to unlock the loaded in memory DLLs) - if Windows 10 do a Restart NOT a shutdown as by default if you don't change it a shutdown is only a hibernate action.
After restarting the PC start WSJT-X and you "should" be using the new library files. The files are not within the WSJT executable, they are installed WITH the WSJT executable from the setup file.

73 Ed.

 

[Helmar]

thank you very much, i will try. i saw that in settings-radio under RIG i can select instead of xeigu the hamlib NET rigctl (written in wsjt-x manual), this is may be another option ?

73 Helmar

 

[Helmar]

i saw in sourceforge the hamlibs are 3.2 Version, the hamlibs of my wsjtx 1.9.1 is newer, it is hamlib 3.3

 

[DD5LP]

that's interesting as ceforge says 3.2 is the latest released verion, so WSJT are perhaps including a beta version of Hamlib? That's not what they should do. Try v3.2 anyway - if your problem gies away, it's an error in the beta code!

One other thing you probably should try, is using a different USB cable. There have been issues at times with some USB cables, so it'd be good to get that possible simple option out of the way at least.

73 Ed.

 

[Helmar]

that's interesting as ceforge says 3.2 is the latest released verion, so WSJT are perhaps including a beta version of Hamlib? That's not what they should do. Try v3.2 anyway - if your problem gies away, it's an error in the beta code!

One other thing you probably should try, is using a different USB cable. There have been issues at times with some USB cables, so it'd be good to get that possible simple option out of the way at least.

73 Ed.

You must be registered for see links

ist the link to the hamlib RC Version 3.3
73 helmar

 

[DD5LP]

Yes RC indicates "Release candidate" - i.e. not fully tested. This is not ready for general release and should not have been included with WSTT-X v 1.91 which is a release version of their code.

In any case have you installed v1.32 and has your problem gone away?

73 Ed.

 

[Helmar]

Yes RC indicates "Release candidate" - i.e. not fully tested. This is not ready for general release and should not have been included with WSTT-X v 1.91 which is a release version of their code.

In any case have you installed v1.32 and has your problem gone away?

73 Ed.

Hi Ed,

i installed yesterday 3.2 of hamlib,but not testet until now, keep you informed.
73 Helmar

 

[Helmar]

Yes RC indicates "Release candidate" - i.e. not fully tested. This is not ready for general release and should not have been included with WSTT-X v 1.91 which is a release version of their code.

In any case have you installed v1.32 and has your problem gone away?

73 Ed.

Ed, which Firmware Version has your Xiegu X-108G ? and wich Version of wsjt-x you are using ?
73 Helmar

 

[Helmar]

Yes RC indicates "Release candidate" - i.e. not fully tested. This is not ready for general release and should not have been included with WSTT-X v 1.91 which is a release version of their code.

In any case have you installed v1.32 and has your problem gone away?

73 Ed.

Hi Ed,

no, also with hamlib 3.2 my problem is still alilve.

I did some more changes to my environment:

- tested 3 other usb cables (no effect)
- better grounding my tx and antenna tuner (no effect)
- used other laptop, also win10 - a very little better, not crash very soon, crash after 3 or 4 cat commands
- installed jtdx (fork of wsjt-x) (no effect)

By the way i saw that decoding FT8 Signals in jtdx is better than in wsjt-x

73 Helmar