|
|
Post by Harri DL4FBZ on Mar 30, 2022 13:42:58 GMT
Hello
I am turning to the forum today. I have a problem with JTDX version 2.2.159. I have compiled the program on a Raspberry 4 with 4GB Ram with the operating system Raspberry PI OS (64bit), Debian version 11 (bullseye). The programme works very well under FT4. With FT8, the error "Error on Soundoutput" appears very often when starting the transmition. When I stop the programme, the error comes back immediately. If I then start again, no error occurs. After the next decode, however, the error comes back. I don't know what to do. The radio is a Yaesu FTdx 101D connected via USB. The sound card in the radio is recognised and works without problems under FT4. Maybe you can help me.
VY 73 Harri, DL4FBZ
|
|
|
|
Post by Arvo ES1JA on Mar 31, 2022 7:22:29 GMT
I not found JTDX having errormessage "Error on Soundoutput" generated in this form. If You launched jtdx from terminal window, what messages You see there??
Usually souch kind of messages should have something to do with RFI.
|
|
|
|
Post by Harri DL4FBZ on Mar 31, 2022 8:06:20 GMT
Hello Thank you very much for the quick answer. I'll try to put in a picture with the error. The error sometimes occurs at the start of the transmition and at the end of the transmition. The PTT switches but no sound is emitted. The complete text of the error is: JTDX Error in SoundOutput An error opening the audio output device has occurred What do you mean the error has something to do with the RFI? Vy 73 Harri, DL4FBZ Attachments:
|
|
|
|
Post by Wolfgang OE1MWW on Mar 31, 2022 9:21:03 GMT
What do you mean the error has something to do with the RFI?
Harri, as Arvo ES1JA says, it may be possible that RF creeps into your cabling and therefore disables your output sound connection. This results in no transmission - because audio output connection is lost.
Depends on the set up of your antenna cabling etc. you should try to put Ferrite clips over your cables Raspberry to the Yaesu rig.
73's de OE1MWW Wolfgang
|
|
|
|
Post by Harri DL4FBZ on Mar 31, 2022 12:35:00 GMT
Hello
I do not believe that it is a HF scattering. The strange thing is that when I acknowledge the error, the transmission works immediately without any problems for this passage. Especially since it works in FT8.
On a second SSD I have an older 32 bit operating system with an older version of JTDX so FT8 works without problems. So far, this error has not occurred there.
TNX for the help
73 de Harri, DL4FBZ
|
|
|
|
Post by w9mdb on Mar 31, 2022 12:39:57 GMT
|
|
|
|
Post by Wolfgang OE1MWW on Mar 31, 2022 14:15:23 GMT
Mike, unfortunately Amazon Europe does not sell that product :-(
Harri, search Amazon.de for 'usb isolator', or Conrad.de part.No. 2266849 - 62 there are similar products available in Europe
As there is no known bug in JTDX with symptoms like yours, it's either RF or any other Linux task, that will grab the audio port.
73's de OE1MWW Wolfgang
|
|
|
|
Post by w9mdb on Mar 31, 2022 14:16:26 GMT
I should add some more explanation too. We have discovered that most USB devices bond pin 4 on the USB connectors to the shield. This completely bypasses any attenuation done by the shield. So breaking the shield connection to the USB device prevents this pin 4 USB problem. The shield will still be connected to the case or ground on the device unless you put another shield isolator on the device side too...there may be some advantage to that too but we haven't determined that yet.
In addition another problem has been discovered where many power supply lines are tying the power supply common to ground. This then puts all the RFI riding on the ground wire onto the power lines too. Ground of DC voltages less than 60V is not required. USB 3.0 for example has 3 separate ground pins and is designed to suppress RFI pretty well. So using USB 3.0 cables should also be an improvement.
I'm going some more testing and plan on creating a test report with recommendations.
|
|
|
|
Post by Harri DL4FBZ on Mar 31, 2022 14:39:53 GMT
Hello
Many thanks for the tips
The sound card I use is the built-in card in the Yaesu FTDX 101d.
I will get such a USB adapter and see. At the moment I have not started JTDX from the desktop but from a LX terminal. At the moment it works.
73 de Harri, DL4FBZ
|
|
|
|
Post by Arvo ES1JA on Mar 31, 2022 16:52:04 GMT
From pictures I see You use to agressive decoder settings. Lag value over 4 seconds is way to much for normal working. Error on opening audio out device points crashing of usb subsystem. why this happens can't say just now.
Try adding "-D JTDX_DEBUG_TO_FILE=true -D WSJT_QDEBUG_TO_FILE=true -D WSJT_TRACE_CAT=true -D WSJT_TRACE_CAT_POLLS=true -D WSJT_HAMLIB_TRACE=true -D WSJT_HAMLIB_VERBOSE_TRACE=true -D WSJT_QDEBUG_IN_RELEASE=true" to jtdx configure for building a debug enabled JTDX.
Then You will have 2 debugs written: in log dir jtdx_debug.txt and in /tmp dir JTDX_trace.log
inspecting them can point to problem.
|
|
|
|
Post by Harri DL4FBZ on Apr 1, 2022 14:36:32 GMT
Hello Arvo
Thank you for your tip with the additional parameters. I have compiled a new version. I cannot find the file jtdx_debug.txt on the Raspberry. I have searched the entire directory.
Unfortunately I can't attach the file jtdx_debug.txt here, because the file is too big.
Vy 73 Harri, DL4FBZ
|
|
|
|
Post by Arvo ES1JA on Apr 2, 2022 5:24:39 GMT
File is written in dir where wsjtx_log.adi and ALL files are written. I got email with hamlib debug, will examine it.
|
|
