Search found 5 matches

by ON3BSQ
22 Feb 2024, 18:21
Forum: User support
Topic: Problems with the Message Service, Version 2.31.0
Replies: 16
Views: 4905

Re: Problems with the Message Service, Version 2.31.0

I'm having the same problem as VK7XX. We were evaluating the CHAT with 3 OM's, all with L4OM v2.31. When sending a message the recepient sees the small square box flashing, but when clicked, there was nothing there.

Rgds, Francis -ON3BSQ.
by ON3BSQ
11 Sep 2021, 19:30
Forum: User support
Topic: Ctrl+PTT puts TX in transmit, but no 400Hz modulation
Replies: 7
Views: 4751

Re: Ctrl+PTT puts TX in transmit, but no 400Hz modulation

I did some additional tests and I believe I have an explanation. This issue may be typical for Yeasu transceivers. I use an FT-897D connected to the PC using the USB interface unit SCU-17, but other Yeasu tranceivers may behave the same way.
The PC sees the transceiver as two sound cards and two COM ...
by ON3BSQ
18 Jun 2020, 00:55
Forum: General discussions
Topic: Question about From Radio audio device
Replies: 1
Views: 1591

Question about From Radio audio device

In Hardware Configuration - Audio devices I have to specify the From Radio (Microphone) device. For what purpose is it used ? I didn't find an explanation in the manual nor in the forum. This device is normaly used to listen to the receiver.

Francis, ON3BSQ
by ON3BSQ
12 Jun 2020, 19:12
Forum: User support
Topic: Ctrl+PTT puts TX in transmit, but no 400Hz modulation
Replies: 7
Views: 4751

Ctrl+PTT puts TX in transmit, but no 400Hz modulation

Log4OM NG 2.7.0 & OmniRig 1.19; rig Yaesu FT897D.
Ctrl+PTT activates transmission, but without the expected 400Hz modulation. When I change the Mode from FM to DIG or PKT then the 400Hz tone is sent out. In Volume² volummixer I can see Log4OM2 generates audio and passes this on to the correct TX ...
by ON3BSQ
11 Jun 2020, 17:16
Forum: User support
Topic: Dialog box contents cut off or not visible
Replies: 2
Views: 2045

Re: Dialog box contents cut off or not visible

I had this problem also in Windows 10. I had specified 125% in Advanced Scaling settings, where you can specify a value between 100-500. I removed this specification and selected 125% on Scaling & Layout, where you can only specify the values 100, 125, 150, 175. This change solved the issue for me ...