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] 2 3 ... 112
1
I don't have a clue what a 1258-N is. I think you may be referring to the Wi-Fi adapter for the RRC. I do not recommend that for all users, except those operating from a fixed location. It is not usable in hotels or other hotspot locations. A bridge can be used in any situation and costs about a third of what the internal card costs.

73,
Mitch DJ0QN / K7DX

2
The method you use for PTT is dependent upon which type of sound card interface you use, as well
as which software you use.

The two methods I have used are PTT over CAT and VOX.

If you are using a SignaLink, then you should use VOX. In that case, make sure that both RRC's have
RTP tx mode set to continuous.

If you are using another type of interface, most likely you can toggle PTT using CAT commands in your software.

73,
Mitch DJ0QN / K7DX

3
Will,

Using Internet Connection Sharing (ICS) in Windows can be a bit tricky and has nothing to with RemoteRig as such.
You may find it easier to buy a cheap external WiFi/Ethernet bridge to use instead. At least that will be more reliable.

Audio being choppy can be caused by one of a zillion things. Since you are within the same network, there are no
internet issues causing it, so the problem is related to your internal network. That would indicate to me a problem
somewhere in the network hardware, or, most likely, ICS again. Certainly not possible to diagnose from here.

73,
Mitch DJ0QN / K7DX

4
Hi Will,

To be quite honest, you didn't provide more than a tiny amount of the information required to be able
to give you an answer.

What are you exactly trying to ping? Does the radio RRC work ok? Are you within the same network, or
coming from outside of it? If outside, are the ports forwarded in the router (you wrote that it worked before).
Was anything changed in the environment, e.g. router, etc.? What does the Microsoft Surface have to do with
this, or are you trying to use an RRC PC Micro Client instead of an RRC? I really do not have a clue what you
are asking.

73,
Mitch DJ0QN / K7DX

5
The standard method to run sound card digital modes over RemoteRig is very simple: just plug the output of your
sound card interface into the control RRC's MIC/AUX jack. Use whatever cable is available for your interface and
wire the red straps accordingly. Take the audio into the interface from the RRC's SP jack on the front. That's it!

73,
Mitch DJ0QN / K7DX

6
General discussion / Re: Do I need the 1274B?
« on: 2018-02-15, 19:15:29 »
Trent,

You will be much happier with the RRC Micro Client. There is no easy way to transport audio or CAT using
the method you are proposing. The Microbit solution solves both automatically and also turns the rig on.
If you are a CW or digital op, it also gives you more flexibility with those modes.

73,
Mitch DJ0QN / K7DX

7
Markus,

You can run unlimited RRC's with control panels, as long as only one is turned on at a time. That
is how we share remote stations. Just save the data using the menu "export to BIN" and import
that into your second RRC and you are all set after doing the internal and external wiring.

73,
Mitch DJ0QN / K7DX

8
General discussion / Re: Do I need the 1274B?
« on: 2018-02-14, 00:03:44 »
Trent,

That is correct...you must first turn the TS-480 on before the software will connect. This is because it
requires the UDP stream first, which is started when you hit the power button.

The advantage of the RRC Micro Client is that it will start the UDP stream and power on the rig remotely
and (only) use the software client like ARCP480 for control. If you already have the control panel with you,
then you can save the money by using its power switch.

73,
Mitch DJ0QN / K7DX

9
Glad you got the problem solved (somehow), Mike. These things happen all the time  ;)

73,
Mitch DJ0QN / K7DX

10
Stefan,

You should for sure try different CODECs. There was another thread on here recently that mentioned that
problem and it was solved by changing the CODEC.

If you have any further questions, just let me know. I can be contacted directly at dj0qn (at) darc.de
(die Sprache ist egal).

73,
Mitch DJ0QN / K7DX

11
General discussion / Re: RRC Micro on cruise
« on: 2018-02-12, 02:10:15 »
Hi Neil,

I think you should find a few others on the forum if you search it, since it has been mentioned several
times that it doesn't work via satellite. I tried using Skype from a cruise ship and couldn't even get that
to work. I never bothered bringing RemoteRig stuff along.

73,
Mitch DJ0QN / K7DX

12
General discussion / Re: RRC Micro on cruise
« on: 2018-02-10, 01:44:47 »
Neil,

That would indicate a satellite connection. It is basically not possible to use RemoteRig over a satellite
link, due to the latency. It will drive you crazy, even if you can manage a connection. SSB will have huge
delays and CW basically not possible to use.

73,
Mitch DJ0QN / K7DX

13
Stefan,

The audio sounds scratchy, as if there is not a good connection in the microphone chain. Note that
microphone audio is done entirely in hardware, using the red strappings in the RRC's. Make sure that
all are connecting properly using an ohmmeter. Never push these in by hand, always use a needlenose
pliers to hold just above where the insulation starts and push gently into the hole. If one gets bent, then
throw it away and make a new one.

Also make sure that you are using separate power supplies for the RRC and rig.

If using a VPN, all you need to use is the internal IP number of the radio RRC and not the external IP
number. That won't even work for a VPN, because the ports are not forwarded.

73,
Mitch DJ0QN / K7DX

14
Mike,

Both audio and PTT are not using the CAT cable. CAT only transports the control signals for the rig and
nothing more. I therefore suspect that you have a problem with that cable and need to recheck it.

I am also not 100% is the FT-3000 is even supported by RemoteRig. That may be your problem as well.

Make sure that:

- The serial cable between the rig's CAT port connected to the RRC's COM2 port is a straight through cable and
not null-modem (i.e. pins 2&3 are not crossed)
- Make sure that the rig's CAT is set to the same baud rate and the RRC's COM2
- Make sure that both RRC's COM2 are set to the same baud rate and match what is et in the rig
- The CAT control software should also match the same baud rate as the two RRC's and the rig

Again, the problem may be that your rig is not compatible. I know they support the old protocol (FT-5000, 2000, 950, 450, etc.),
but am not sure about the 3000.

73,
Mitch DJ0QN / K7DX

15
Hi Stefan,

It looks like you may have already attempted to do a lot of tweaking, so perhaps there is not much
more than we can do for you. I assume the bottleneck is actually somewhere in the VPN somewhere,
so perhaps you should try the "normal" method of using port forwards for a test. 99%+ of the installations
are doing fine using this method, so perhaps give it a shot.

Anyway, I have a checklist that assists one with low-bandwidth situations. Again, I assume that you already
tried this, but this is about as best as I can help you at this time:

3G/4G Checklist
------------------
Try reducing your bandwidth to a minimum and changing some parameters to compensate
for a poor line. Note that this is only for using 3G/4G on the control side. Running a RemoteRig
system over 3G/4G with the router on the radio side will never work, unless you pay extra for a
true external IPv4 address or use a VPN.

Here are some tips:

1) These are important:
- audio quality to 0 (half the bandwidth of codec 2 and more than adequate for SSB & CW)
- turn continuous RTP on or set RTP to continuous (depending upon firmware version)
- If using the K3 Twin or Yaesu with a second receiver, then turn off "audio dual-rx" on the
   radio RRC under the radio settings. This doubles the necessary bandwidth if on.

2) Play around with these 3 until you are satisfied:
- increase rx jitter buffer to min 12+
- increase rx jitter delay to min 10+
- audio packet size 20 or 40

3) Also, make sure that serial ports COM1 and COM2 are turned off if not used,
or that either being used is set to the minimum bps necessary to handle the serial
communication. For example, use 4800 for CAT on a rig like the TS-480 and not
a high speed like 57600, since the higher speed is completely unnecessary.

73,
Mitch DJ0QN / K7DX

Pages: [1] 2 3 ... 112