Great news thanks for the effort. I still have not got resolution from my Internet provider.
When do you anticipate 1.25 will be available?
Thanks and 73
Ken VA3KA
Search found 16 matches
- 31 Mar 2016, 21:46
- Forum: Feature suggestions
- Topic: Cluster Heartbeat setting
- Replies: 8
- Views: 6579
- 22 Mar 2016, 21:04
- Forum: Feature suggestions
- Topic: Cluster Heartbeat setting
- Replies: 8
- Views: 6579
Re: Cluster Heartbeat setting
I won't reveal my logging program!!
I really only use one "local" dxcluster in any case (and a 2nd as a back up).
As there are sometimes 3-4 spots a minute, I don't imagine my 1 keepalive a minute will cause much of an issue.
My Internet provider still has not found out why my telnet sessions ...
I really only use one "local" dxcluster in any case (and a 2nd as a back up).
As there are sometimes 3-4 spots a minute, I don't imagine my 1 keepalive a minute will cause much of an issue.
My Internet provider still has not found out why my telnet sessions ...
- 07 Mar 2016, 23:04
- Forum: Feature suggestions
- Topic: Cluster Heartbeat setting
- Replies: 8
- Views: 6579
Re: Cluster Heartbeat setting
Until the issue is resolved I probably need a 60 second heartbeat!
Thanks for the consideration.
Ken VA3KA
Thanks for the consideration.
Ken VA3KA
- 06 Mar 2016, 16:38
- Forum: Feature suggestions
- Topic: Cluster Heartbeat setting
- Replies: 8
- Views: 6579
Cluster Heartbeat setting
I am having ongoing issues with my Telnet connection to DXclusters timing out after 3-4 minutes when there is low activity.
This does not appear to be a Log4OM issue but something to do with my Internet provider. I have been in preliminary discussions with them and they are so far not able to ...
This does not appear to be a Log4OM issue but something to do with my Internet provider. I have been in preliminary discussions with them and they are so far not able to ...
- 30 Jan 2016, 23:40
- Forum: User Support
- Topic: VP8SGI incorrect grid square
- Replies: 4
- Views: 3504
VP8SGI incorrect grid square
The grid square that comes up on VP8SGI is showing them off the coast of Africa (II99TK).
When I enter them from the cluster, the grid square shows up as KD85JQ in the beam heading and information area then after about 1 second the info boxes changes to green and the grid changes to II99TK. Of ...
When I enter them from the cluster, the grid square shows up as KD85JQ in the beam heading and information area then after about 1 second the info boxes changes to green and the grid changes to II99TK. Of ...
- 10 Jan 2016, 21:15
- Forum: User Support
- Topic: Cluster questions
- Replies: 2
- Views: 2402
Cluster questions
I have been having difficulties keeping connected to the DX clusters (I have tried various clusters and all the same). After some random period of time (from minutes to hours) I get disconnected.
I do not think this is a Log4OM issue as I have tried from other computers (running a TELNET session ...
I do not think this is a Log4OM issue as I have tried from other computers (running a TELNET session ...
- 08 Dec 2015, 23:37
- Forum: User Support
- Topic: Communicator Issue (was FLDigi frequency)
- Replies: 3
- Views: 2650
Re: Communicator Issue (was FLDigi frequency)
Well mysteriously the problem has cleared itself - again!
Log4OM Communicator is reading and tracking VFO A now ok. FLDigig is reading VFO A ok now as well. I did nothing different here.
I guess the threat of a support request made the program behave!
If the issue reoccurs I will submit a Support ...
Log4OM Communicator is reading and tracking VFO A now ok. FLDigig is reading VFO A ok now as well. I did nothing different here.
I guess the threat of a support request made the program behave!
If the issue reoccurs I will submit a Support ...
- 03 Dec 2015, 22:47
- Forum: User Support
- Topic: Communicator Issue (was FLDigi frequency)
- Replies: 3
- Views: 2650
Communicator Issue (was FLDigi frequency)
The problem I had with VFO B being read in FLDigi (rather than VFO A) cleared up for a while and was reading correctly but has now reverted back to incorrect VFO reading.
Setup:
FT-2000
Omnirig V1.16
FLDigi V 3.23
JTAlert V2.6.25
When looking at the Log4OM Communicator Panel:
RigStatus ...
Setup:
FT-2000
Omnirig V1.16
FLDigi V 3.23
JTAlert V2.6.25
When looking at the Log4OM Communicator Panel:
RigStatus ...
- 29 Nov 2015, 02:38
- Forum: User Support
- Topic: FLdigi Frequency tracking
- Replies: 5
- Views: 3569
Re: FLdigi Frequency tracking
Update-
I have it working ok now.
I reinstalled Omnirig and all is ok now frequency sends to FLDigi as it should from VFO A.
Problem closed!
73,
Ken VA3KA
I have it working ok now.
I reinstalled Omnirig and all is ok now frequency sends to FLDigi as it should from VFO A.
Problem closed!
73,
Ken VA3KA
- 27 Nov 2015, 16:42
- Forum: User Support
- Topic: FLdigi Frequency tracking
- Replies: 5
- Views: 3569
Re: FLdigi Frequency tracking
Did a little more digging (including contacting the FLDigi yahoo group) on this.
When I look at the Log4OM Communicator panel, in the Rig Status box:
CAT CONNECTED
But the frequency displayed is from VFO B on the FT-2000, not VFO A.
When tuning VFO B this freq. tracks accordingly.
Maybe this is ...
When I look at the Log4OM Communicator panel, in the Rig Status box:
CAT CONNECTED
But the frequency displayed is from VFO B on the FT-2000, not VFO A.
When tuning VFO B this freq. tracks accordingly.
Maybe this is ...