Messages

1

General discussion forum / Re: rf feedback

« on: 2013-08-25, 18:40:51 »

I found this thread whilst searching to see if a problem I have had been discussed before.  It might be sort of RF feedback related, may not be....

I have a 480 SAT, both a pair of RRC1258 MkII's, and an RRC PC Micro Client to go with it.  So that  the PC Micro client is always "Ready to go" should I be out and about and decide I want to use it, I have got the 2 RRC-1258's set up permanently (until the day I decide to take the 480's head unit out and about too) at home.  They connect to each other over the home LAN, so that even when I am at home, and the head unit is 3" away from the main unit, the head / base communication runs through the RRC's.  All works well.  Until I tried it today on SSB.  On doing that, there seems to be some kind of feedback that upsetting the microphone circuit.

If I plug the microphone directly into the 480 base unit, all works as it should on SSB.  A whistle test invokes a swinging ammeter on the PSU, and a similarly swinging power indicator on the 480 display.  The current/power falls off as fast as the whistle does.

On trying the same thing through the RRC's, its a different story.  ON a whistle, the current and the power go up, but then stay up, with a "fluttering" noise emanating from the mic, even when the PTT is pressed.  It eventually comes back down, but after seconds.  Put the mic back into the base unit directly, and all is well again.  Try it on AM or FM and all is well also.  It just doesn't seem to like operating on SSB in this setup.

The RRC pair is as far away from the 480 base unit as the supplied shielded RJ45 lead will permit - So not far - About 6"! and there are no expected problems with stray RF.  It doesn't really matter which antenna I test it with, but even on the Sirio Gainmaster, which has a good reputation for being common mode current free, it does it.

Appreciate that in expected operation, the control RRC would be well remote from the transceiver and radio RRC, but was not expecting this problem.  Could dispense with the Control RRC and connect the head unit directly again, but then I will need to remember to change over leads anytime I leave the house, in case I decide to connect in remotely with the PC client.

Have tried adding a few ferrites (from the limited little pile I have) to no effect.  I could maybe get more separation between the transceiver/radio RRC pairing and the head unit/control RRC, which will involve a bit of carpentry to make some new shelving to separate them with.

Just wondered, before I embark on that, if this has been seen before?

Cheers

2

General discussion / Re: Troubleshooting guide

« on: 2013-07-25, 18:37:37 »

It seems that the problem is more related to the outgoing traffic rather than the incoming.  At the remote location (my workplace), we have 2 routers in series.  The one closest to the internet is a Draytek Vigor, and the one behind that is a Belkin.  The Draytek provides Guest Internet without them being able to access the company network.  The Belkin acts simply as a firewall (inbound) and NAT device and seperates the guest accessible netwrk from the company network.  On both routers, outgoing services are unrestricted (allow all)

When I tried this morning, I was connected on the Belkin (inside the company).  No connection.  If I reconnect to the Draytek (Guest internet), it works.  The router at home is a Netgear, and it seems to be OK for incoming connections, but not for outgoing.  The Belkin also doesnt seem to be happy with outgoing connections.  The Draytek Vigor however is.  It seems like the outgoing connection is quite "fussy", and I am hoping that I do not run into the same issue if using other outgoing internet connections - For example, in a hotel or via 3G mobile service - I can readily control the conditions of my home internet connection, but not that of out and about connections.

With the radio RRC being in the DMZ back home, I can readily navigate to its web server set up page from both work networks.  So there is no issue with the TCP/IP connection to Port 80.  It just seems to be the SIP connection to port 13000 that is fussy.

So, I have it worked around, for test purposes at least.  The concern is that if I am somewhere that has as fussy an outward connection, then I will not be able to connect again.  I guess all I can do is try and see what happens!

3

General discussion / Re: Troubleshooting guide

« on: 2013-07-25, 10:21:12 »

Hmmm, thats not so good.   

I have tried it remotely today, and it is just the same as from home, even with the RRC in the DMZ back home.  So now its not clear if the problem is with the router at the radio end, or also with the router at the control end.  I have now tried it with both the control RRC as well as the PC Client, and neither are able to connect from WAN to LAN, even though both work OK when within the LAN.

The burning question then is, if you change the router(s), what do you change them to?  The router at home already has the most up to date firmware (sending it off to check results in it reporting "There are no newer updates available".  Randomly changing routers in the hope that the next one might work seems a bit hit or miss.  Is there a list of routers that are known to be good (or bad), that can guide the router buyer in what they should get?

4

General discussion / Re: Troubleshooting guide

« on: 2013-07-24, 14:51:30 »

I am sure everyone has had a fair fill of connection problems being posted, and for that reason, I have done my damnest before posting yet more!

I am trying to set up a new install of both 1258 Mark II's and RRC PC Client.  The opening post on this thread looked familiar in that I can get everything to work inside the LAN, but so far, not outside.  I must add that at this point, I am still trying "out and in" again onto the Internet from the one place, before I go and try from another location.

Aside from getting the kit to work on the LAN, the key points are;

• The connection failure when going out to the internet and back again is a complete failure to establish the SIP connection
• I am using a fixed WAN IP address
• The ports being used are 13000 - 13002, and have been forwarded to the radio 1258's LAN IP address
• I work with networks and port forwards on a daily basis at work, and should be able to do this!

I have yet to try "out and in" with the control 1258, but thats next on the cards.  I suspect it will exhibit the same problem as the RRC PC client.

Like the OP on this thread, there must be something blocking the SIP connection.  Putting the Radio 1258 in the DMZ and/or disabling SIP ALG in the router do not help.

Is it worth heading out to the remote site and trying it from there, or if I cannot go "out and in" again at the same site, if I am wasting my time?