Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - dj0qn

Pages: 1 ... 128 129 [130] 131 132 ... 149
1936
General discussion / Re: Exactly what is wrong!
« on: 2011-11-22, 20:28:32 »
Thanks, Mike, this is terrific! Sorry you have to make up for other software's mistakes,
but we all appreciate it.

73,
Mitch DJ0QN / K7DX

1937
General discussion / Re: Exactly what is wrong!
« on: 2011-11-22, 13:52:56 »
Thanks for the explanation, Mike, I think I understand the difference now, after reading your
answer a few times.

In my case, My FT-2000 is using mode 10 and TS-480 mode 5 (of course, two different RRC's).
If I understand correctly, the reason the PC Client turns the the TS-480 on, is because of this
special mode 4. Mode 10 requires the CAT software to turn it on, which doesn't work in my case,
or, judging from the other comments, with the FT-2000 at all.

So what are the options to make this work? Is there a work-around that you could implement in
the firmware?

73,
Mitch DJ0QN / K7DX


1938
General discussion / Re: Exactly what is wrong!
« on: 2011-11-21, 16:48:36 »
Hi Mike,

Are you saying then that this is nothing that you can fix, and is a bug in the FT-2000 firmware?

One thing that does puzzle me.....the PC Client does turn the TS-480 on before I connect with
HRD, so are you saying that Yaesu rigs must be turned on instead by HRD? I wasn't aware that this would
behave differently between rig type using the PC Client, so that is why I expected the FT-2000 to be
turned on by the PC Client before connecting with HRD, like it does with the TS-480.

73,
Mitch DJ0QN / K7DX

1939
General discussion / Re: Exactly what is wrong!
« on: 2011-11-21, 09:08:35 »
I have also reported the problem with the PC Client not turning on the FT-2000 a couple of times in the past:

http://www.remoterig.com/forum/index.php?topic=920.0
http://www.remoterig.com/forum/index.php?action=profile;u=276;area=showposts;start=15 (from 9/22)

This appears specific to the FT-2000, and since the guys in Sweden don't have access to an FT-2000, they
haven't been able to duplicate this problem. If Jan and Mike want me to help with some testing, I will be
happy to try to help solve this problem once and for all.

73,
Mitch DJ0QN / K7DX

1940
Configuration, RRC 1258 / Re: Web Interface Failure
« on: 2011-11-10, 08:01:27 »
Gus,

Did you change the web port number? If so, you need to add that to the browser address,
followed by a colon and port number, e.g. http://192.168.Y.YYY:XXXX (where YYYY is the
internal IP address and XXXX is the port number).

73,
Mitch DJ0QN / K7DX

1941
Hardware, Cabling, Installations / Re: I/O Port Connection
« on: 2011-11-06, 14:05:52 »
Thorsten,

Look at this thread:

http://www.remoterig.com/forum/index.php?topic=1036.new#new

73,
Mitch DJ0QN / K7DX

1942
No, only COM1. I assumed that you are using CAT over COM2.

73,
Mitch DJ0QN / K7DX

1943
Hi Greg,

Do you have the cable wired correctly? Pins 2 & 3 are reversed on COM1.

73,
Mitch DJ0QN / K7DX

1944
General discussion forum / Re: ELECRAFT K3 TWIN OPTION
« on: 2011-11-04, 07:46:29 »
Elecraft is looking at producing a new product for this market, which would essentially
be the K3 front panel with a serial port to connect to the RRC. This would be quick and
easy to develop and would keep the cost down. This would make the K3 implementation
very competitive with the TS-480 "heads", albeit on a much higher performance level.

There is no timing commitment on this product, since they have limited development
resources and have other priorities in the pipeline (KX3, etc.). I would not expect this
to be available before the middle of 2012, assuming they decide to produce it.

They will look into making the KX3 firmware function in terminal mode, however the KX3 is
lacking some features the K3 has, such as a second receiver. Therefore, the mapping would
not be that clean. If they decide to implement this in the KX3, it would also be once the KX3
firmware is stable, which also will take a while (the rig is not shipping yet).

73,
Mitch DJ0QN / K7DX

1945
Vern,

Send me a mail at dj0qn (at) darc.de and I will send you my latest checklist to
help you get started. This may help you locate your problem.

73,
Mitch DJ0QN / K7DX

1946
I am having a similar problem, which Jan is looking into.

Two questions:

1) Do you have COM2 (CAT) going over USB?

2) Are you using the radio RRC to route CAT to another device at the radio location?

These two conditions cause the same problem you described  in two stations I use under
firmware 2.41 or later. Pulling out the USB cable or not turning on the device (in my case
an SPE Expert) connected to COM1 causes the problem to go away.

73,
Mitch DJ0QN / K7DX

1947
General discussion / Re: Com ports being used
« on: 2011-10-13, 17:48:40 »
Well, all I can honestly say is that these drivers are the first ones I have seen that have
the problem with not being able to change the port in the "advanced" tab (or even show
an "advanced" tab, for that matter). I have tried on several computers with different Windows
versions with the same results, so I assume it is a design error somewhere.

No idea what the problem is, but there is indeed one!

1948
General discussion / Re: Com ports being used
« on: 2011-10-13, 17:22:11 »
This batch file will also allow you to delete old USB and other devices, I just was focused on COM ports.

I think the problem with changing the COM ports isn't the PC or Windows, but the driver itself. To be
honest, the only problem I have had ever changing the COM ports with is in the drivers that you guys use.
I love your hardware, but your USB drivers are not exactly......ahhhh.....flexible (being polite)   ;)

1949
General discussion / Re: Com ports being used
« on: 2011-10-13, 16:24:55 »
Here is a tip to be able to solve this type of problem for future users:

copy the following two lines into notepad:

set devmgr_show_nonpresent_devices=1
\windows\system32\devmgmt.msc

Then save this into a batch file, e.g. "Show Old Devices.bat"

Then start the batch file (double-click in Windows). It will then load your Device Manager.

Now when you click on the menu "view", then "show hidden devices", you can see all your
old devices you no longer use under the COM ports. Then you can delete these or change
their ports to prevent a conflict.

Note that I only have German Windows on my computers, so I think these are the English
menu titles.

73,
Mitch DJ0QN / K7DX


1950
General discussion forum / Re: still dropping out
« on: 2011-10-13, 14:30:56 »
One tip: check to see if your router has a new firmware version available. In two cases
I know of, updating the router's firmware solved this type of problem.

73,
Mitch DJ0QN / K7DX

Pages: 1 ... 128 129 [130] 131 132 ... 149