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

Pages: 1 [2]
16
General discussion forum / Configuring RRC-Micro
« on: 2016-02-18, 16:35:25 »
Presently have Elecraft twins and RRC-1258 MkII(s) working perfectly.

Trying to install RRC-Micro on a Windows XP laptop.
First installation of software resulted in green bars showing on RRC Client screen, RTP light on, RRC light flickering, but no COM 0/1/2 lights on.
Set up to use COM 0 as that is what is at the remote K3.
Tried various do this do that, could not get to next step.
I am trying to interface to TRX Manager.

Next I uninstalled RRC-Micro.
Message said not all removed.  Some had to be removed manually.  I did nothing.

Reinstalled RRC-Micro.
Get audio error messages .  But biggest issue is program cannot find:    ftsprapi.ddl    This is an "Exception from HResult:  oX8007007E
I went and looked for Virtual Com ports.  NONE found.
In RRC-Settings window, under COM 0, I select Mode 4 for Elecraft, but no COM ports listed.

Your assistance is most welcome. 
73
Chet VE3CFK

17
General discussion forum / TERM Mode
« on: 2015-12-15, 17:07:05 »
My RRC-1258 MkII(s) and K3-Twins have exhibited periodic, but now 100% of the time going into TERM Mode when first turning power on.  Stays in this mode until powering down and powering back up at which point it goes into TERM mode momentarily before displaying the banner in the VFO B window and operating as it should.

How can we resolve this issue of going into TERM mode.

73 Chet VE3CFK

18
General discussion forum / Cannot Connect - Problem Resolved
« on: 2015-11-20, 16:12:32 »
2015-11-15, 18:41:35

My RRC-1258 MkII(s) and K3-Twins have worked fine for several months.
Today, tried to connect and I get busy signal.  Went to remote site and K3 was not turned on.  Manually turned it on.
Went home and tried to connect, all I got was a busy signal.

Question.  Where does one start to trouble shoot?
Is there a thread that goes thru trouble shooting?


2015-11-20


Found the problem, but most bizarre.  Don't know if anyone else has experienced the same.

Two problems found: one with the modem/router, the other with RRC-1258 Remote box.

In the modem/router all the port forwarding was corrupted.  Ports forwarded on wrong computers/devices.  Some computers such as TRX Manager running on my main PC was removed from my PC and reassigned to an X-Box!  After I reassigned and reconfigured the modem/router, I got TRX-Manager to work.  But Remote rig would not.

I originally had the RRC-1258 remote configured to bypass the firewall, so it was DMZ'ed.  I couldn't get port forwarding to work, but DMZ allowed the system to work (yes I know it's not the best configuration but it works).  So when I tried to set the DMZ option on the modem/router after the problem was discovered, the modem/router said the device needed to be using DHCP.  Using Microham set-up manager, I confirmed that the DHCP box was ticked off.  Tried to configure the Modem/router and still no go.  Went back into set-up manager, disabled the DHCP and tried the modem/router again.  Still no go.  Went back with set-up manager, ticked off the DHCP box and now the modem/router allowed DMZ configuration and now remote-rig works again!

So.  What would have caused the modem/router to reconfigure, and why would the software in the Remote-rig box get corrupted?

The RRC-1258 Remote box is normally off (no DC voltage applied) when I am not using the Remote.  So a voltage spike on power-up? 

73
Chet
VE3CFK

19
Found the problem, but most bizarre.  Don't know if anyone else has experienced the same.

Two problems found: one with the modem/router, the other with RRC-1258 Remote box.

In the modem/router all the port forwarding was corrupted.  Ports forwarded on wrong computers/devices.  Some computers such as TRX Manager running on my main PC was removed from my PC and reassigned to an X-Box!  After I reassigned and reconfigured the modem/router, I got TRX-Manager to work.  But Remote rig would not.

I originally had the RRC-1258 remote configured to bypass the firewall, so it was DMZ'ed.  I couldn't get port forwarding to work, but DMZ allowed the system to work (yes I know it's not the best configuration but it works).  So when I tried to set the DMZ option on the modem/router after the problem was discovered, the modem/router said the device needed to be using DHCP.  Using Microham set-up manager, I confirmed that the DHCP box was ticked off.  Tried to configure the Modem/router and still no go.  Went back into set-up manager, disabled the DHCP and tried the modem/router again.  Still no go.  Went back with set-up manager, ticked off the DHCP box and now the modem/router allowed DMZ configuration and now remote-rig works again!

So.  What would have caused the modem/router to reconfigure, and why would the software in the Remote-rig box get corrupted?

The RRC-1258 Remote box is normally off (no DC voltage applied) when I am not using the Remote.  So a voltage spike on power-up? 

73
Chet
VE3CFK


20
General discussion forum / Cannot Connect
« on: 2015-11-15, 18:41:35 »
My RRC-1258 MkII(s) and K3-Twins have worked fine for several months.
Today, tried to connect and I get busy signal.  Went to remote site and K3 was not turned on.  Manually turned it on.
Went home and tried to connect, all I got was a busy signal.

Question.  Where does one start to trouble shoot?
Is there a thread that goes thru trouble shooting?

73
Chet
VE3CFK

21
Thank you all for your help, especially Mitch, DJ0QN / K7DX.
Works great.  Looking forward to using it in the Summer Stew this weekend.
73 to all,
Chet VE3CFK

22
I have K3 and K3/0 mini.
Configured and installed both with RemoteRig controllers in shack with K3s.  Worked perfect.
Commissioned (or tried to) in field with no success.
K3/0 in shack powers up with message "TERM" where sub VFO would readout, and RemoteRig controller single beeps every 30 seconds or so. Remote K3 powers up, but is on it's own frquency different that whats in shack.
I'm thinking the remote router is not set up correctly.
Any help with path forward would be appreciated. 
CHET VE3CFK

Pages: 1 [2]