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 - DL5FAB

Pages: [1] 2

I have implemented a SW controlled PTT switching with the RTS signal from a Digimode SW with a small HW modification of the Dongle, pulling a PTT line on the red PTT button to ground via 220 Ohms through a simple transistor switch integrated in a D-Sub connector.
I am also routing the audio signals to/from the Digimode SW using Virtual Audio Channel (VAC).
More info unter the following link to my drop box:

This set-up works quite well and I made a number of succesful contacts in various modes.

Please consider that this simple modification will possibky void your warranty. I take no responsibilities for any damage!

Thanks Mike,

this is not obvious but it works. I assume, that in this configuration I cannot use the COM2 anymore?
At least it saves a V.24 to TTL Converter.

Can somebody describe how to configure the RRC at the radio side to transmit? Is there a reference for the configuration/cabling.

When using the PC-Client I observe the following issues:

a) Connection is fine and audio starts to flow

b) When pushing the PTT knob, the audio mutes but no TX switching happens on the radio side. After a few attempts of pressing the PTT, the RRC on the radio side hangs-up and can only be recovered by re-starting through the Web interface.

The same set-up used for CV-I control from a RRC on the controlling side using HRD works fine.

I downloaded and installed PC-Client SW RRC version 1.0.12 for 32bit  and the firmware up-date for the RRC-1258-CRC_v2.21_2010-09-24 today and tried again. The problem when pushing the PTT remains. the RRC-1258 Radio Controller hangs-up, looses the connection and re-boots when pushing the PTT.

Mike - any idea?

I have tried to set-up a configuration which allows to use:

a) a RRC in CI-V Mode with HRD controlling the TRx remotely, or alternatively,
b) the PC-Client with HRD for TRx control.

For a) the PC with HRD is connected through the COM2 port of the RRC on the controlling side and the TRx is connected as well on the COM2 port of the RRC on the radio side. This works fine!

However, I was not able to get-out a CI-V signal on the TTL port as indicated on Page 55 of the manual! Both RRC are configured and strapped for ICOM CI-V Mode.

Soemhow, this behavious appears logical for me as the connection from the COM2 port on the control side should end at the COM2 port at the radio side. But than the figure is misleading - is it?

For b) the PC-Client is connected through the USB Interface to the Laptop running HRD. Here it is possible to connect through the COM0 port of the RRC on the radio side and get a proper CI-V signal on the TTL-port.

As I would like to use the configurations alternatively, I have therefore configured a connection through the COM2 port for HRD when using the PC-Client. This works but is wasting one port.

What goes wrong here?

General discussion forum / Re: ICOM CI-V and HRD not working
« on: 2010-10-09, 18:01:22 »

I tried this configuration as well and it will not work. You need also to set-up the COM 2 port of the Controller in Mode-2 ICOM CI-V and use a V.24/TTL Converter. Having inastalled this, I can run them Control Panel and HRD in parallel.

I experienced similar problems. I have connected the IC-706 Control Panel remotely and wanted to use the TTL interface for CAT-control in parallel by HRD through using HRD. This only works on the COM-2 interface with external converter V.24 to TTL to CI-V.

Reasoning for this set-up is the possibility to remote control with the IC-706 Control panel while also creating the possibility to control with the PC-Client (for those members of the club not owning a control panel.

Having tried-out the different possibilities today, I gave up with the alternative use between the remote IC-706 Control Panel or the PC-Client and wait until a SW solution becomes available.

Has somebody experience using the Web Switch for Fan Control Mode?

I have a Temperatur Sensor connected on Input A (9/10) and the measured temperatur is displayed ok.
I set the wanted Temp on Input A to e.g. 25 degree.
In Fan Control Mode I would expect that for a temperature rise above 25 degrees over the cycle lenght of e.g. 5 minutes, the Fan would be switched on via Relais 1.
But this does not happen.

The Heat Control Mode works as expected. Below the wanted temperatur the Relais 1 switches on and above it switches off.

I tried this now again with Software Release: 1.10
Build   : Sep  6 2010 11:02:45

but no change on the behaviour. Fan Mode seems not to work. Any ideas or experiences?

General discussion forum / Re: RRC 1258 + UMTS
« on: 2010-04-21, 23:26:57 »
I have so far managed to control from a remote site via O2 UMTS/HSPDA my rig, which is connected on a DSL link (6 Mbps downstream/768 kbps up-stream). It works with acceptable quality in Mode 0. Transmissions of the display goes a bit delayed and I have observed up to 400 kbps peak rate when moving the VFO knob. I am now using a CAT SW (HRD) or IRC for control via the COM Interface. This works quite fine. Take care, that you are always loged into your Homezone - otherwise you can experience a very high bill - it happened to me...

I have not managed a connection the other way around - to control the remote rig through a remote UMTS/HSPDA connection due to network issues on the UMTS provider side. They are using proxy servers which translate the IP-adresses and therefore I cannot reach the remote site with an incoming connection set-up. If someone has managed that - I am really interested to understand the set-up.


I tested the new Webswitch 1216H with the Firmware Version 1.5, build 9th March 2010 and have discovered the following problems:

The ICOM CI-V Adress to be set on the switch can only be set to X,Y where X and Y can only be decimals from 0 to 9 - it will not ave anything as AA to FF - or as I tried 4E. I assumed then, that the setting of the adress has to be in decimals, e.. 78 decimal to match 4E hex on my rig - but nothing worked. I then tried the combination 66 on the switch and 66 hex on the rig - and it worked. The highest adress you could set this way is 79 hex- as this is the highest hex adress which would work in the combination of switch with IC-706.

Coding of the bands for automatic band switching does not work coherently. I have a strange problem, that Relais 5 switches on above 21 MHz, even if it is not programmed at all.

My set-up would be: Relais 1 (Dipol 40/80m)  - hence Relais 1 programmed to 3A, 7a - this works.
Relais 2 (Beam on 20,15,10m) - hence Relais 2 programmed on 14, 21, 2A - does not work. It will switch-on Relais 5 as from 21 Mhz onwards.

General discussion forum / Re: DynDNS
« on: 2010-04-14, 00:11:40 »
Will try this out but would need to apply for a new domain name which is presently

General discussion forum / Re: RRC behind 3G / UMTS
« on: 2010-04-11, 19:15:42 »
Thanks for the feed-back..
With regard to the Public IP Adress - I have DynDNS addresses, through subscription (fast up-date rate) from which I use one at the Remote end.
With regard to the provider side, I have heard that the service provider usually block outgoing P2P connections. I cannot yet confirm for my provider which is using the German E2 network. A possibility to prevent this might be to use VPN tunneling - but this makes think a bit more complicated too. I will report further results here.


General discussion forum / DynDNS
« on: 2010-04-05, 14:32:04 »

I have tried to use the DynDNS Client in the Controller configured as follows:

DynDNS Check Interval: 10
DynDNS Host Name:
IP check Host Name: (to bypass proxies)
Own Host Name:
Username: as registered in DynDNS
Password: as registered in DynDNS

The DynDNS Client appears not to work or is for whatever reason not reaching DynDNS.

DynDNS works fine for all my other domains and it works for the domain with the Controller when I activate the DynDNS Client on the Router instead of the Controller connecting via UMTS to the Internet. I can check the up-dates being performed on the Host-Lists of DynDNS, which appear as soon as UMTS assigns a new dynamic IP adress.

What could go wrong here?

General discussion forum / Re: RRC behind 3G / UMTS
« on: 2010-04-03, 18:55:00 »
I have unsuccessfully tried to connect the Radio Controller via UMTS/HSPDA. I do not get an incoming connection established.
The configuration on the router is:
NAT enabled
Port Forwarding to the Controller on ports 11000,12000, 12060 (modified from 5060), 80 and 23.
I also activated a Virtual Server for incoming connects with the same ports for the Radio controller.
Firwall is switched off.
Can you provide me a hint?

General discussion forum / Re: RRC behind 3G / UMTS
« on: 2010-02-05, 23:39:59 »
I have used UMTS/HSPDA to connect the panel side remotely to the Intermet, the Radio Controller is connected on (A)DSL 6 Mbps downlink. The reported UMTS rates range between 3.6 and 4.2 Mbps. With proper HSPDA connection I am achieving in Audio Mode 0 steady rates of around 100 kbps for the audio and for the data connection when moving the VFO knob of peak rates up to 380 kbps. The audio quality is acceptable and no interruptions are observed. Establishing the connection is a bit tricky. Further optimizations have not been tried yet.
I am using a Edimax 3G-6200n 3G Broadband Router with an O2 Webstick and concluded that this is a workable solution for remote access to the station.

I have also tried to use the USB-Webstick directly on a Netbook with Windows XP, connecting the RRC-1258 on the Ethernet LAN and sharing the UMTS connection. This is not stable to establish - it works only once, when the connection is established manually and than changed to share. I assume that this mode of operation is possibly prevented by the Webstick.



I got the RRC-1258 now working behind the firewall with the following settings:

Controller  behind the Firewall,
no DMZ
DynDNS activated
NAT on

Port Mapping:
IP                  Protocol LAN              Port Public Port UDP      12060             12060 TCP      80                  80 TCP      23                  23 UDP     12000              12000 UDP     11000              11000     

Special Applications:
Incoming port 11000 triggers ports 11000,12000,12060

Firewall switched-on but the following features enabled/disabled:

Intrusion Detection Feature:

SPI and Anti-DoS firewall protection  - off
RIP defect  - on
Discard Ping To WAN Interface  - on

Stateful Packet Inspection:

Packet Fragmentation  - on
TCP Connection  - on
UDP Session - on
FTP Service  - on
H.323 Service  - on
TFTP Service  - on

de Manfred

Pages: [1] 2