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 ... 121 122 [123] 124 125 ... 135
1831
General discussion forum / Re: FSK
« on: 2011-07-13, 10:31:35 »
Now that the RemoteRig developers have done a great job of adding an FSK virtual serial
port to firmware 2.41, can someone please try it out and provide feedback on how it is working?

I am not a RTTY guy, but I am implementing the use of RemoteRig for an operation where RTTY
will be critical, so I need to know how well it works and any other tips that one can provide.

Thanks & 73,
Mitch DJ0QN / K7DX

1832
General discussion forum / New Hum Problem with 2.41
« on: 2011-07-13, 10:28:21 »
Just a heads-up: there is apparently a problem with firmware 2.41 that causes hum when the USB CAT is used.
This is the same or similar to the problem that occurred in firmware 2.35 and was fixed right away. See
http://www.remoterig.com/forum/index.php?topic=701.0 for that thread.

It is the same user that is having the problem. He is away today, but I will try to get more tests and details
from him before I leave on vacation this weekend. It appears so far to be identical to what he experienced
in 2.35, so he has downgraded to 2.39 for now until this is clarified or resolved.

73,
Mitch DJ0QN / K7DX

1833
Just change the DynDNS check interval to off, and that's it.

Actually, it is also completely harmless to let it continue to run, since it will never
make a change, anyway. So there is no rush to change it.

Do NOT enter anything in the external IP/host field! You don't need to enter your
external IP number on the radio side at all, but do so on the control side RRC in the
"SIP contact" field under the radio settings.

73,
Mitch DJ0QN / K7DX

1834
Hi Guy,

Glad to hear that you have the YaesuTwin as well. I still think we must
be related, we seem to always get the same toys. I decided to go the
FT-2000 route, because I already had one and used FT-2000's are really
cheap now. The NS filter makes the receiver much better.

I am curious if you find the same problem I have found. It is really difficult
to pin down, since you can't always really tell if something works or not.

73,
Mitch DJ0QN / K7DX

1835
I found the problem with the SSB audio....it wasn't YaesuTwin.

The guy I split the station with plugged the amp PTT into the
Microham, instead of into the FT-2000. That does not work
remotely, except for CW (Winkeyer). That is why it not only
appeared to be a PTT problem, indeed it was.

There is still an inconsistency problem with the power control.
I will try to figure out if further controls are not acting as they
should.

73,
Mitch DJ0QN / K7DX

1836
General discussion forum / YaesuTwin Inconsistent Controls
« on: 2011-07-07, 16:27:15 »
I finally got my YaesuTwin into full-time operation, after having one of my FT-2000's
upgraded with the NS filter over the last month.

I have experienced inconsistencies between what is indicated on the local FT-2000
and the remote FT-2000. I am running TRX-Manager on the remote side and can view
and control some settings that way using VNC.

Some controls appear to work just fine, e.g. shift, width and basically everything on
the right side of the rig. However, some controls do not work, even if they appear
correctly in TRX-Manager.

One example of this is the power control. I can change the local FT-2000's power
level and TRX-Manager follows it with the slider. However, the actual power on the
radio side does not change, you can see this in the display on the TRX-Manager
monitor screen, as well as through my remoted LP-100 wattmeter. If I then go and
change the slider on the TRX-Manager control screen, the power really changes.

Another example is the mic gain control. This appears to have no effect at all. Since I can
not monitor this in TRX-Manager, I can't verify what is happening. I believe it is not working,
because my output power on SSB is very low, and the amplifier does not appear to even be
in line. Since the amp works in CW, it can not be a keying problem with the PTT. I listened to
my output on a local rig, and my audio appears fine, just the signal is weak due to low power
output.

I can try to figure out which controls work and which don't, but maybe by looking at these two,
mic gain and power, you can see if there is a general issue.

Thanks & 73,
Mitch DJ0QN / K7DX














1837
Configuration, RRC 1258 / Re: RRC Manager
« on: 2011-06-27, 12:38:16 »
Let me know if you need help by phone or Skype. I can also send you a
checklist that I wrote for people not too familiar with networks technology.

73,
Mitch DJ0QN / K7DX

1838
Vincent,

Probably it would be best for you to send the files to Mike at RemoteRig to analyze and perhaps
let him access your radio RRC. If you don't get further by Monday, I can also take a look, but I
am leaving for Friedrichshafen tomorrow morning.

73,
Mitch DJ0QN / K7DX

1839
General discussion forum / CW Key Plug
« on: 2011-06-22, 19:12:43 »
I have a strange problem with the CW paddle connection:

I have three remote installations using RemoteRig and TS-480's that I currently manage.

In one of them, RemoteRig works just fine with a CW paddle cable plugged fully in the RRC's and TS-480's jacks.

In two of them, it does not. If you plug the cable about two-thirds of the way into the jack on the RRC,
then it works just fine. If you move it out a bit or push it all the way in, it doesn't work.

All three installations are identical, both in hardware and in RRC settings.

Anyone have a clue why this would be the case? It is not a "killer" problem, but it would be nice to solve this mystery.

73,
Mitch DJ0QN / K7DX

1840
General discussion forum / Re: TS 480 HX: No audio out
« on: 2011-06-22, 16:37:57 »
Rainer,

Did you change your SIP port number from 5060 to something else? If you left it as
5060, you will encounter port conflicts with some routers, since this is the standard
port for VoIP.

73,
Mitch DJ0QN / K7DX

1841
From your screenshots I can't really see anything wrong that would cause it not to work.
Even though you have forwarded everything double (TCP and UDP), that would not cause
a problem.

One thing is not clear....are you trying to access from outside your network, or within? From
outside, you need to enter into the control RRC's "SIP contact" either the Radio RRC's external
IP number, or its Dynamic DNS address. If within your home network, you give the internal
address (192.168.1.200) as the "SIP contact" address on the control RRC.

Otherwise, maybe someone else sees something I don't.

73,
Mitch DJ0QN / K7DX

1842
Hi Vincent,

The ports being open are irrelevant if your internal network does not know where
to send the connection from outside when that port is addressed.

I can't tell from your screen shots if you have FORWARDED all of the ports to .200
for all of the ports used by the RRC. I think that is the problem, but can't verify it.

Are you sure that your router does not have DMZ (sometimes called something
different like "exposed host" in the router)? Check under "Special Applications".

You should have no problem with VoIP in your router, since you changed the
default SIP port from 5060 to 5000. Of course, you may have a port conflict
with another application, but that is unlikely. You may wish to also change the
RRC's web port from 80 to something else and forward it (and add a password),
so that you can access it from outside over a browser.

73,
Mitch DJ0QN / K7DX


1843
Vincent,

Try something else: place your RRC in the DMZ in your router. This will solve
any port issues and you can see if it works or not.

If that works, you can either leave it in the DMZ, or else figure out what is
wrong with the port forwards. If it doesn't work, then you know the problem is in
the configuration in the RRC.

73,
Mitch DJ0QN / K7DX

1844
Hi Vincent,

It could be one of several things, but a couple to look at:

1) Did you put the correct SIP port into the control RRC (5000 in your case)?
2) Are you addressing it via the external IP number (if I understand you correctly, you did)?
3) It looks like you only opened-up the ports in your router. You must forward these ports
to the internal IP number (192.168.1.200 in your case) for it to work. I bet this is the cause
of your problem.

73,
Mitch DJ0QN / K7DX

1845
General discussion forum / Re: Problem with TS-480
« on: 2011-06-20, 13:59:05 »
I still think something is wired wrong, or else a jumper is broken. I know out of
personal experience that these jumpers are not as easy to place as they look.
I had some problems at first and had to replace two of them. Now I use needle-
nose pliers to set the last couple of mm in the hole, I learned my lesson.

If you are 100% sure that everything is correct, then I am afraid that the
RemoteRig team will have to step in and help you out.

73,
Mitch DJ0QN / K7DX

Pages: 1 ... 121 122 [123] 124 125 ... 135