Messages

31

General discussion forum / Re: Radio RRC Web interface does not respond

« on: 2015-07-24, 14:19:22 »

Mitch,

I can give it a try even though I do not believe in it ;-)  Need to reboot the RRC so it will start to work for some time anyway. Let's see how long the web interface will stay alive with the new port number. With the default port number the RRC used to work a week or two after a power boot.

73 de Kari, OH2XX

32

General discussion forum / Re: Radio RRC Web interface does not respond

« on: 2015-07-24, 14:03:30 »

Hi Mike,

I have tried with Chrome and IE on both remote PC and my home PC with similar results: "ERR_CONNECTION_TIMED_OUT"

If I power boot RRC it helps. If I power boot PC nothing changes. It kind of isolates the problem on the RRC side - right?

I have noticed that sometimes I get only a part of the web page but after clicking the hyperlinks it kind of refreshes the page and starts to work ok.

My two 1216H Web Switches work just fine all the time.

73 de Kari, OH2XX

33

General discussion forum / Re: Radio RRC Web interface does not respond

« on: 2015-07-24, 13:12:11 »

Mitch,

I have not changed the port number so there is no port number (other than 80) to try out ;-)

- Kari

34

General discussion forum / Re: Radio RRC Web interface does not respond

« on: 2015-07-24, 12:54:44 »

Hi Mitch,

Thanks for the idea but the port number has not been changed. If it was changed even power boot would not help as it does now...

73 de Kari, OH2XX

35

General discussion forum / Radio RRC Web interface does not respond

« on: 2015-07-24, 11:05:05 »

Hi,

My remote setup works just fine but the web interface of Radio RRC is quite often unresponsive. I can not even access the web interface on the local LAN there (I have ea remote PC with TeamViewer). The RRC does respond to ping and the radio works etc. but I am not able to access the web page  unless I power reboot the unit at the remote site. Just hate to do it as it reboots everything there: the router, PC, antenna controllers etc.

The RRC SW version  is 2.81

I have also recorded the following error messages if it has something to do with this symptom:

14.7.2015
Data Abort at 0x0004a9dc, called by 0x0004a044

1.7.2015
Data Abort at 0x0004a760, called by 0x0004a72c

17.6.2015
Data Abort at 0x0004aa04, called by 0x0004a044

30.5.2015
Data Abort at 0x0004aa04, called by 0x0004a044

Any ideas?

73 de Kari, OH2XX

36

General discussion forum / Re: K3/0 display freezes

« on: 2014-09-19, 10:02:50 »

Testing is believing... I replaced my 3G router (BandLuxe R300) to Huawei B593 and it did make the difference. The display has not frozen in two days.

73 de Kari, OH2XX

37

General discussion forum / Re: K3/0 display freezes

« on: 2014-09-10, 11:14:12 »

I replaced the TS-480 with K3's so it is either RRC or the router. The router is hard to blame as it just forwards packets and they may get lost as we know. That is something to be handled by the upper layers of SW. And if the panel freezes and it can be 'refreshed' by pressing PTT it seems like a protocol issue to me.

38

General discussion forum / Re: K3/0 display freezes

« on: 2014-09-10, 11:00:17 »

I did actually have the same problem with TS-480 too. Perhaps it has something to do with the following error messages that I have written down during the last 3 months:

Data Abort at 0x0004e598, called by 0x0000a3bc
RRC was not presponding at all

Data Abort at  0x00046694, called by 0x00046660
Breaks in audio stream

Data Abort at 0x00046938, called by 0x00043e50
Breaks in audio stream

Data Abort at 0x000470f4, called by 0x00046734
Breaks in audio stream, RRC not responding

Any idea what is causing those?

73 de Kari, OH2XX

39

General discussion forum / K3/0 display freezes

« on: 2014-09-10, 09:32:28 »

Hi All,

Just wanted to share this one. I have been using RRC with a K3/0 for a year now and it works just fine most of the time. There is this irritating freeze of the display&LEDs from time to time though. But I seem to have found a workaround for the problem now. By pressing PTT the display refreshes and awakes. As simple as that. I just happen to work CW 99% of the time so pressing PTT is not something you do by nature. Luckily I worked some SSB and found the cure there. Maybe there is way to incorporate this "refresh" feature somehow in the firmware? I have installed a foot pedal for now...

73 de Kari, OH2XX

40

General discussion forum / Re: Latency mystery

« on: 2013-11-22, 19:06:22 »

Some update on the latest findings for the record.

I noticed that the 3G router seems to pass the ping request to RRC as it is configured to be DMZ. So the ping plot tells that it is the RRC that is involved in this latency issue. That explains why all my efforts to cure the 3G router RFI problem have not had any impact in the first place.

As CQWW is just around the corner I wanted to try alternative approach to have reliable CW in the contest. So I installed a local PC at the remote station with TeamViewer, logsoft and COM-port CW keying. And you know what - it works flawlessly. I just run the logsoft via TeamViewer and it works all day long. Ping stays at 60...90ms so it is now even better than my earlier setup with 250ms key delay.

But I would like to have the setup without the PC being involved. So I will continue analyzing the problem further.  It seems that the RFI is not going into 3G  router or RRC SIP stream but into the remote CW keying or the protocol behind it. Maybe I'll try some RF chokes on the RRC CW key cable next. That is perhaps one of the only cables there without ferrite at the moment ;-)

73 de Kari, OH2XX

41

General discussion forum / Latency mystery

« on: 2013-11-02, 22:21:01 »

Hi,

I have posted a few questions here related to my issues with CW keying. I have tried to find out a workaround and have succeeded to some extent. Anyway the root problem is still to be resolved and it is a mystery for me. I have problems with the latency of my internet connection and I have spent tens of hours analyzing the problem as it seems to be RFI related.

I am using a 3G connection (3G router BandLuxe R300) and the 3G base station (UMTS 900 MHz) is quite near (<4 km) at the remote site. I have an outdoor yagi pointed there and the normal latency is between 60-90 ms, uplink about 1 Mbps and downlink 2 Mbps on average.

And here is the mystery. If I am running barefoot everything is fine but when using amplifier problems start (at about 600W and upwards). But the mystery does not start immediately - it takes from 4-10 minutes and after that the latency starts to go up and down heavily. Here is a screenshot of a ping trace between my home PC and the remote 3G router:

http://www.kolumbus.fi/kalehtim/ping.png

If I am not transmitting the delay stays under 100 ms for hours...

Unfortunately the RTT exceeds the critical 250 ms that is currently the maximum delay for CW keying. So my CW has some annoying errors there.

The thing that I can not understand is that the higher delay seems to last excatly 3,5 minutes every time - sounds like a SW or protocol timeout? It happens when transmitting on 160 meters or 10 meters. The delay propagates to all of the nodes between my home and the remote site. As you can see in the graph the delay is behaving the same way at the closets router to my home (vantik1.fi.elisa.net) and the remote 3G modem. My ISP has checked the lines and could not find any problems there. I tested the setup also by using a 3G modem at my home to bypass my ADSL access network and I could see the same problem with that setup as well.

I have put the remote 3G router in a metal box (grounded) with ferrites on power cable, current choke on the coaxial cable of the yagi and shielded CAT6 ethernet cable (1m long). So quite good RFI protection there. I bought also a 900MHz band pass filter for the modem  (yet to be installed)...

The Radio RRC is grounded, Ethernet is set to Auto-prefer 10 Mbps.

I am totally lost here. Any ideas are more than welcome.

73 de Kari, OH2XX

42

Configuration, RRC 1258 / Re: Winkey

« on: 2013-10-17, 20:15:42 »

I am talking about the USB drivers that come along with the setup manager installation package.

E.g. I can see that the name for "RRC1258 COMExtra"  has now changed to "RRC1258 COMFSK" in device manager after downgrading.

43

Configuration, RRC 1258 / Re: Winkey

« on: 2013-10-17, 19:32:44 »

Solved!

I installed the old USB Com drivers (with Setup manager v1.17) and now the Winkey works.

73 de Kari

44

Configuration, RRC 1258 / Re: Winkey

« on: 2013-10-17, 18:42:31 »

Thanks to Mitch for having a look at my configuration.

The CW program Mitch refers to is "UA9OV CWType". It works ok for my local Winkey (microHAM) and it is the one Jan used in his test setup.

I went over to OH1JT's PC and tried to configure his RRC Winkey both via RRC COMExtra and RRC COM1. Did not get it to work there either.

The FW revision we both use is the latest and Jan must have had that one too so I am totally lost here.

73 de Kari

45

Configuration, RRC 1258 / Re: Winkey

« on: 2013-10-16, 20:11:56 »

I took my wife's laptop and installed virtual com ports there. Still no luck. Flashed RRC - no affect. It is time for a short break now.