Too bad.
Thanks anyway.
Search found 26 matches
- 10 Apr 2024, 18:48
- Forum: User support
- Topic: go back to original frequancy after cluster spot QSY
- Replies: 2
- Views: 270
- 10 Apr 2024, 16:38
- Forum: User support
- Topic: go back to original frequancy after cluster spot QSY
- Replies: 2
- Views: 270
go back to original frequancy after cluster spot QSY
A double click on the cluster window make my radio QSY to the spotted frequency.
Is there a way to come back to my original freqency (eg. i dont listen the spotted station ...)
73 de I0MOM Marco
Is there a way to come back to my original freqency (eg. i dont listen the spotted station ...)
73 de I0MOM Marco
- 09 Apr 2024, 13:49
- Forum: User support
- Topic: CW Serial settings key pin and PTT pin not saved
- Replies: 2
- Views: 297
Re: CW Serial settings key pin and PTT pin not saved
Tank You Terry
- 09 Apr 2024, 08:29
- Forum: User support
- Topic: CW Serial settings key pin and PTT pin not saved
- Replies: 2
- Views: 297
CW Serial settings key pin and PTT pin not saved
Started to use cw keyer interface connected to a serial port via a transistor keyer interface. After specification of com port number , key pin and ptt pin everithing works as expected. The problem is when I restart keyer interface : the comport number remain as wanted but key pin and ptt pin reurns...
- 16 Mar 2024, 07:56
- Forum: Error reports
- Topic: calls input from cluster leaves stats(F1) squares blank after upgrade to 2.32 version
- Replies: 3
- Views: 995
Re: calls input from cluster leaves stats(F1) squares blank after upgrade to 2.32 version
Yes Daniele,
Version 2.32.1.0 fixed it.
Thanks for fast reply & correction !
73 de I0MOM Marco
Version 2.32.1.0 fixed it.
Thanks for fast reply & correction !
73 de I0MOM Marco
- 15 Mar 2024, 17:46
- Forum: Error reports
- Topic: calls input from cluster leaves stats(F1) squares blank after upgrade to 2.32 version
- Replies: 3
- Views: 995
calls input from cluster leaves stats(F1) squares blank after upgrade to 2.32 version
I upgraded to V.2.32.00 and when I chose a call from the cluster list I do not see anymore the stat(f1) squares which let me know if and in what band I already worked that country or station.
If I manually input the call I see the statistics again .
73 de I0MOM Marco
If I manually input the call I see the statistics again .
73 de I0MOM Marco
- 02 Apr 2023, 07:45
- Forum: Error reports
- Topic: [wkd same mode group] not working
- Replies: 9
- Views: 2634
Re: [wkd same mode group] not working
It still doesn't work but I found a workaround. Noted that "wrk same band mode" without being able to browse previous QSOs happens on digital modes if You worked the station in RTTY or FT8 and now the spot was on a FT4 mode. I simply cut the station callsign, change the mode (eg FT4 to FT8...
- 21 Dec 2022, 09:19
- Forum: Error reports
- Topic: [wkd same mode group] not working
- Replies: 9
- Views: 2634
Re: [wkd same mode group] not working
21 dec 2022.
The problem is still on.
Log4om is V2.25.00
Merry Xmas de Marco I0MOM
The problem is still on.
Log4om is V2.25.00
Merry Xmas de Marco I0MOM
- 19 Nov 2022, 15:04
- Forum: Error reports
- Topic: [wkd same mode group] not working
- Replies: 9
- Views: 2634
Re: [wkd same mode group] not working
I have the same problem.
At this date (11-2022) does not seems solved.
73 Marco I0MOM
At this date (11-2022) does not seems solved.
73 Marco I0MOM
- 28 Oct 2022, 07:49
- Forum: User support
- Topic: Change of station logged callsign as radio tuning change
- Replies: 2
- Views: 316
Re: Change of station logged callsign as radio tuning change
Solved !!
After noticing that the "abusive" callsign was the las one automatically logged from WSJT-X, I reinstalled WSJT-X and that solved !
Thanks for watching,
73 de I0MOM Marco
I
After noticing that the "abusive" callsign was the las one automatically logged from WSJT-X, I reinstalled WSJT-X and that solved !
Thanks for watching,
73 de I0MOM Marco
I