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.

Topics - oz1rh

Pages: [1]
General discussion forum / Elecraft K4 with RemoteRig
« on: 2022-06-16, 18:01:20 »

Has anyone tried to remote an Elecraft K4D with a RemoteRig using a K3/0 Mini? The commands for K3 and K4 are to a large extend the same, so it might be possible that a K3/0 Mini will be able to control at least some basic functions of the K4.

If Remoterig can power the K4D ON it should be possible to transfer audio and use Win4K4Suite to manage the K4D through the serial connection provided by Remoterig. However it would be better to use a K3/0 Mini for the basic functions where the commands the the same in the K4 and K3.

73, Palle, OZ1RH.

General discussion forum / How to change MAC adr of RRC
« on: 2017-10-18, 17:00:05 »

I am in a hotel in San Francisco for Pacificon and want the change the MAC address of my remote RRC to match the one in my pc. However MAC adr is greyed out in the Microbit Setup Manager Setup info. Any way to change the MAC address of the RRC?

My idea is to logon the hotel wifi from the pc and then move its Ethernet cable from the pc to the RRC hoping that the hotel wifi will keep that MAC adr logged on. After that I plan not use the pc before next logon.

If that does not work I will do the usual trick with Internet Connection Sharing on the pc.

73, Palle, OZ1RH.

My licensed Nano Elecraft 1.5.0 does not work well for me. I have a RRC setup with K3/0-Mini to K3 with original RemoteRig cables working with no problems. All RRC's have software version 2.90.

When I start my licensed Nano Elecraft 1.5.0 and connect I get the sound from the K3 within a few seconds. However none of the controls in the Nano app on the VFO page works and neither RX S-meter nor VFO frequencies are displayed. Sometimes after 4-5 minutes the controls starts to work. However after turning the VFO wheel the VFO frequency is displayed as a difference like 2.90 or -0000.000.001 It is now possible to press and hold where the frequency should be displayed and then the box for entering a frequency is displayed. After entering a frequency it is displayed correct and turning the VFO in the app changes the A-frequency as expected. Pressing A/B and then press and hold where the frequency should be displayed let me enter a frequency in the B-VFO, which then is displayed in line B. Now the app is more or less usable, however RX S-meter still only shows -- and BW is grayed out and does not work. Mode button works but the selected Mode is not displayed. Band button works, but the indicated frequency is not changed in the app.

My phone is a HTC 10 with Android 6.0.1. It also has a licensed Nano Icom 1.5.0 installed, which most of the time shows similar problems when connecting to another site with an IC-7100. However the Nano Icom sometimes works better. Perhaps the two apps interfere? I have had situations where after using the Icom and the Elecraft application one after another a few times none of them works and the only remedy is to shut the phone down (Power off/Restarting). My old HTC One M8 with Android 6.0 experienced the same problems.

My problems seems similar to what is mentioned in however I do not get the message APP TRIAL PERIOD HAS EXPIRED and the licence indicator on 'the connect screen' is most often green Lic.ID bef5 as it should be.

Sometimes the Lic.ID bef5 is red on one or both Nano Elecraft and Icom and then often either of them ends with 'Stopped unexpectly'. After that restarting the app usually results in a green Lic.ID bef5 and the app can connect but still only works with the flaws mentioned above. After the 'Stopped unexpectly' I have sent many error reports including system data.

This looks like software errors and I would like to have my licensed Nano apps working.

73, Palle, OZ1RH.

I have noticed that my radio RRC can't be pinged even though the RRC is working and its webinterface can be accessed as it should. This makes fault finding in the network layer difficult as I use ping to check for hardware and network problems.

My documentation is in the enclosed screen dump. Both RRC and my pc are on the same network mask My control RRC .227 can be pinged as it should, but radio RRC .228 can't even though its webinterface is available. I have checked that the webinterface screen is not coming from a cache and it updates nicely from a box that can't be pinged. Both RRC's are cabled to my wifi router and the RRC's have no wifi card inside. The radio RRC has a ping watch dog running OK against the ADSL router and it can ping out, but not even from the ADSL router can I ping the radio RRC.

I think this is an error which has showed up in one of the later fireware releases as I seem to recall ping worked many months ago.

73, Palle, OZ1RH.

Pages: [1]