Thanks Nolan, I was now able to update my CQ-zone to zone 9, but sadly my GridTracker is still not able to upload my QSO's to LoTW, TQSL says location is not found... Uploading my ADIF direct in TQSL does work (but this is not a Log4OM problem )
TNX for your help Nolan, 73 de Frank PJ2/PH2M
Search found 10 matches
- 10 Sep 2022, 19:01
- Forum: User support
- Topic: MYCQ for PJ2/PH2M is incorrect
- Replies: 3
- Views: 361
- 10 Sep 2022, 11:42
- Forum: User support
- Topic: MYCQ for PJ2/PH2M is incorrect
- Replies: 3
- Views: 361
MYCQ for PJ2/PH2M is incorrect
Hello all, started my holiday style DX-pedition to the island of Curaçao yesterday evening found uploading to LoTW not working with a location error, all selections are correct for TQSL but found MYCQ in Log4OMv2 set as CQ Zone 8 instead of CQ Zone 9, I seem to be unable to change this to CQ Zone 9 ...
- 06 Sep 2021, 14:13
- Forum: User support
- Topic: Station Configuration not looking for band worked
- Replies: 1
- Views: 670
Station Configuration not looking for band worked
Hello all, I 'am running 2 rigs via omnirig, together mainly in FT8-mode with JTDX & GridTracker, finished QSO's are logged in Log4OM via GridTracker. So I' am running mostly 2 rigs together at the time (in Log4OM as Rig1 + Rig2) but in My (F4) I can choose only ONE Radio + Antenna setup, this c...
- 29 Mar 2021, 10:01
- Forum: User support
- Topic: PSTRotator
- Replies: 7
- Views: 3675
Re: PSTRotator
I have the same problem for the last few months, running always latest versions of Log4OM (v2) & PstRotatorAz. Portnumber 12040 in both programmes, PstRotatorAz works O.K. when selecting a beaming, but nothing happens when clicking 'Azimuth' (e.g. showing 156 deg.) and the beam/rotator is pointi...
- 04 Mar 2020, 17:15
- Forum: Error reports
- Topic: Where are my configs in v2.4.0.0.
- Replies: 0
- Views: 3671
Where are my configs in v2.4.0.0.
Yesterday I upgraded from v2.2.0.0 to v2.4.0.0 (after previously downgrading from v2.3.0.0. to 2.2.0.0) and all running normal yesterday evening, today I started v2.4.0.0 again and my previous configs (PH2M & SV9/PH2M) are missing :oops: This is on my shacks W10 Desktop, I just checked my laptop...
- 25 Feb 2020, 20:31
- Forum: User support
- Topic: Error(s) using JTDX/JTAlert/Log4OM2
- Replies: 2
- Views: 2165
Error(s) using JTDX/JTAlert/Log4OM2
Trying Omnirig with IC-7300-Data + IC-9700-Data now, on both frequency is not correct, being on 5357 (60M-FT8 jumps to 5357,055 at startup :roll: ), also op 144.174 the frequency jumps to 144.174,055 Another problem: with the same JTDX settings between the IC-7300 & IC-9700 there is a huge TX-de...
- 25 Feb 2020, 19:17
- Forum: User support
- Topic: No QRZ.com data
- Replies: 9
- Views: 6311
Re: No QRZ.com data
Hello Terry, trying Omnirig with IC-7300-Data + IC-9700-Data now, on both frequency is not correct, being on 5357 (60M-FT8 jumps to 5357,055 :roll: ), also op 144.174 the frequency jumps to 144.174,055 so still figuring out whats the best setup (I must not be the only user, using JTDX + JTAlert + Lo...
- 24 Feb 2020, 13:16
- Forum: User support
- Topic: No QRZ.com data
- Replies: 9
- Views: 6311
Re: No QRZ.com data
This is a very annoying problem :twisted: , like the Pse QSL problem when printing, also Omnirig is not working with my IC-7300 + IC-9700 (switching to RTTY when operating in FT8), logging from JTDX + JTAlert > Log4OM2 (v.2.3.0.0) works O.K. I just returned to using v.2.2.0.0 at least QRZ lookup wor...
- 13 Feb 2020, 11:29
- Forum: User support
- Topic: Lookup Fields Not Populating
- Replies: 15
- Views: 8212
Re: Lookup Fields Not Populating
Same problem here, station data not filled anymore :'( (only callsign from JTAlert/JTDX), no more data like Operator, QTH, Grid etc. also same problem with manual station input, logging from JTAlert+JTDX works without a problem, QSO's are logged with all information!
73 de Frank PH2M
73 de Frank PH2M
- 05 Aug 2018, 17:19
- Forum: User Support
- Topic: Digi spots shown as phone spots?
- Replies: 2
- Views: 2293
Digi spots shown as phone spots?
Why are FT8 digi spots (like on 50.313) shown as phone contacts on the Log4OM cluster page? 73 de Frank PH2M