Recent Posts

81

General discussion forum / Re: Can't connect via web browser to control unit

« Last post by sm2o on 2024-05-25, 21:16:54 »

Hi
I don't think this this is a Remoterig issue, if you have done factory default reset and you get this result, the problem is probabaly somehwere else.
There is a telnet server also at port 23 but I don't see how it would help

73 de mike

82

General discussion forum / Re: Can't connect via web browser to control unit

« Last post by k5tri on 2024-05-25, 21:07:34 »

After removal of USB cable, Setup Manager found the device and showed the correct address and Port 80.

When I clicked the Config button, the address field was empty and all other address fields had the same address including DNS.
Changed it to the correct values and saved to the device.
Still not able to connect with a browser. Is there a console via Telnet to access the unit?

83

General discussion forum / Re: Can't connect via web browser to control unit

« Last post by sm2o on 2024-05-25, 20:27:48 »

Remove the USB cable and use the same tab and click on find device button to the right. then select the correct unit an click on the browse button


/mike

84

General discussion forum / Re: Can't connect via web browser to control unit

« Last post by k5tri on 2024-05-25, 20:18:43 »

See attached. This is what the Microbit Setup Manager presents.

85

General discussion forum / Re: Can't connect via web browser to control unit

« Last post by sm2o on 2024-05-25, 20:08:07 »

that's not the "net info/find device tab"

mike

86

General discussion forum / Re: Can't connect via web browser to control unit

« Last post by k5tri on 2024-05-25, 20:01:03 »

Hi
If you can ping the unit but not browse it you probably not using the standard port 80 for the webserver. If you use the microbit setup manager program and do "net info/find" it will show which webserver port you have set (after the IP-number). You can click on browse then the correct portnumber will be added by the program so you can reach the webpages and change web server port  back to port 80.

73 de mike

The unit is using Port 80 as usual. Net info/ Find shows the following:

MAC       : 00:1e:fd:01:a4:07
IP address: 192.168.1.21
Netmask   : 255.255.255.0
Gateway   : 192.168.1.1
DNS       : 8.8.8.8


No Port info there. It can be retrieved however via Setup. Just saved the same config to the unit again but no dice.

FWIW I've been just playing around in CQ WPX right now and connection to the radio seemed stable except for the usual Reset Radio prompt when using N1MM+.

When I saved the config to the device it shut down and I had to hard reset again.

73 Mike

87

General discussion forum / Re: Can't connect via web browser to control unit

« Last post by sm2o on 2024-05-25, 19:48:52 »

Hi
If you can ping the unit but not browse it you probably not using the standard port 80 for the webserver. If you use the microbit setup manager program and do "net info/find" it will show which webserver port you have set (after the IP-number). You can click on browse then the correct portnumber will be added by the program so you can reach the webpages and change web server port  back to port 80.

73 de mike

88

General discussion forum / Can't connect via web browser to control unit

« Last post by k5tri on 2024-05-25, 18:50:06 »

Hello,

Just out of the blue a rather interesting issue showed up. Everything was working fine until recently.

I can't connect with a web browser to the config page of the control unit on my LAN. The unit can be pinged, so network connectivity isn't the issue.

The config is with a TS-480SAT, control unit in Houston, TX, radio is in Germany.

After a hard reset removing both USB and power connection, I can turn on the radio and operate, but no web portal. Eventually the radio connection
no longer works and I have to reboot the unit again. The radio unit is reachable at all times.

I installed the latest firmware to the control unit.

Any tips on how to resolve this are very welcome.

73 Mike K5TRI/ DK5TRI

89

Hardware, Cabling, Installations / Re: Failure to Boot using 12vdc Power - Possible Cause and Solution

« Last post by N3AE on 2024-05-12, 23:17:16 »

Well, not so fast.  After several days of behaving normally, this control RRC is back to its old tricks.  It was working fine, controlling the remote Kenwood TM-V71A and providing good two-way audio.  But after cycling power to the RRC it will not boot up.   On another good control RRC at power-up, I see a brief flash of the green power LED followed by a steady red and yellow LED on the mic connector for a few seconds.  Then the red and yellow extinguish and the green begins blinking until a TCP/IP connection is made.  On the problem unit, I see no flash of the green LED and the red and yellow illuminate immediately and simply stay that way.

Another observation:  If I power the RRC from the USB connector with 12v disconnected, the unit appears to boot up.  Red and yellow LED's extinguish after a few seconds and the green LED blinks fast, per the manual.  While in this state, if I then apply 12v power with the USB still connected, the red and yellow LED's turn on again, after a few seconds extinguish and the green LED blinks at a slower rate typical of waiting for a TCP/IP connection.  If I then remove the USB connector with the 12v still applied, the RRC seems to stay as it was in a normal state, with the red and yellow off and the green blinking slowly and turning steady on once a TCP/IP connection is made.   I can access the RRC over my web browser and all the configuration setup looks fine.  Interestingly, I can command "Restart Device" from the browser window and the RRC does successfully boot back up.  Once in this state, the control RRC works fine with it's radio partner RRC and a Kenwood TM-V71A. 

If I then drop the 12 v power, wait a bit and reapply 12v, the RRC goes back to a steady ON red and yellow with no green LED and I lose the TCP/IP connection.

If I reverse the whole sequence and apply 12v first followed by connecting the USB, the RRC stays locked with red and yellow on continuously plus no TCP/IP connectivity.

Tried several different 12v power sources with no change.  This problem looks like some sort of hardware-firmware timing issue.

Anyone see this behavior before and have a fix?  I have not tried reloading firmware yet.  It RRC already had v2.95 loaded out of the box.

tnx

N3AE

90

Hardware, Cabling, Installations / Failure to Boot using 12vdc Power - Possible Cause and Solution

« Last post by N3AE on 2024-05-09, 22:10:00 »

Just wanted to share what I found during some troubleshooting today.   I have a Control RCC, s/n 13824, that experienced difficulties booting when power was supplied through the 12vdc coaxial plug.  Initially it was fine but on a subsequent power-ups it failed.   Symptoms included no Green power LED with a steady Red and Yellow LED (above Mic connector), plus no ability to link to the internal web server. 

I discovered that the 12v jack on the PWB was mounted slightly askew such that the outer ring (negative) of the 12V coaxial power plus could/would contact the side of the chassis hole when inserted into the jack.  Looking at the PWB traces, it appears that the 12v negative is not necessarily connected directly to chassis but, like the positive supply, runs through an inductor in what amounts to a pi EMI filter.  So my assumption is that direct contact from the 12v negative to the chassis is not intended and causes issues.

Rather than mess with the jack on the PWB, I used a tapered reamer to slightly enlarge the chassis hole.  That solved the problem.

When assembled, you should see the 12v coaxial jack's plastic continuously around the circumference of the chassis hole and well centered in the hole.  If it's not, chances are that the outer ring of the coaxial plug will be in contact with the chassis even though the plug "feels" fully inserted.

We have a number of RRC-1258 MKII's running in our RACES setup and they have been very reliable.  Not a single glitch since being powered up in the fall of 2021.  This one had not been powered up since it was purchased.