• If posting about a radio issue: Include the HOST, DSP and UCM/secure firmware versions, flashcode and CPS version you're using along with the operating system info. This is critical information.

XPR8300

Status

Muxlow

Banned, Bad boys, bad boys, whatcha gonna do, what
Joined
Dec 12, 2012
Messages
176
The local DMR machine i sort of take care of was lent out to another ham radio club and the tinkered with it.
Since we have gotten it back the TX light on TS 1 and 2 stay on when nobody is talking. If i key up a radio the lights go out for a few seconds and then come back on.

They loaded a new FW version into the repeater . R02.40.12 and it needs ti have R02.20.12. Is there a way i can downgrade the firmware back to R02.20.12? or is this machine stuck now...
Seems to be the only thing they changed was the firmware and now we have this nice little issue
 

escomm

Prolific Contributor
CS Forums $upporter
Joined
Jul 29, 2013
Messages
402
I doubt the issue is with firmware. What does RDAC say about the station's status? Have you read the repeater log since it was returned back to you?
 

Mars

Prolific Contributor
CS Forums $upporter
Joined
Dec 21, 2011
Messages
4,991
Based on your description of the bizarre LED light behaviour, you should check the seating of the flex cables going into the Repeater Indicator Board (RIB), which is the square circuit board screwed into the front of the repeater, with the LED lights.

If the flex is unseated, someone was tampering with it. There's no other way it could possibly move as everything is screwed into place.

Also, if the behaviour persists after you've reseated the flex, I would strongly suspect damage to the Repeater Indicator Board. I observed very similar LED sequences while recently servicing an 8400 with a damaged RIB. After replacing the RIB, the fault was corrected.

The part number for the 8300 RIB (8MB board) is PMLN5269AS. It's listed as $149.50 CAD in my non-discounted account. If you contact a reputable dealer such as escomm, the pricing is considerably less expensive. (For anyone reading this in the future, the p/n for the 8400 RIB is PMLN5643AS; it's a separate part/not compatible with 8300)

Also take note, the RIB contains the MAC address for the Ethernet controller. If you change the RIB, your MAC will change. Any DHCP reservations you have done at the router will need to be updated.
 

rainbowpenguin

Prolific Contributor
CS Forums $upporter
Joined
Mar 13, 2015
Messages
104
Had almost the same issue here in a 8400. After updating the firmware, shortly after a subscriber unit unkeyed the repeater would key up (ts1 & ts2 tx lights were lit), transmit idle beacons for about two minutes, unkey, then rekey and transmit again. Enabling the IPSC beacon and setting it to the minimum (about 2sec every 2min) fixed the problem.
 
Last edited:

Forts

Prolific Contributor
CS Forums $upporter
Joined
Aug 6, 2012
Messages
857
I think I'd be going back to the folks that it was loaned to and be asking a few hard questions... like why did you upgrade the firmware without permission and what else did you do to it??
 

phonebuff

Prolific Contributor
CS Forums $upporter
Joined
Nov 10, 2013
Messages
678
That old Retail adage comes to mind " You broke it, you own it !"

Maybe a spanking new SLR-5700 is in your future :)
 
OP
Muxlow

Muxlow

Banned, Bad boys, bad boys, whatcha gonna do, what
Joined
Dec 12, 2012
Messages
176
We did ask the people we lent it to what they did. They said all we did was plugged it in and that was it.
This the 2nd time we have lent them the repeater.. First time we got it back it would not connect to the DMR network because they changed settings so i had to fix that issue.. Now this. They have their own repeater now so we wont be lending ours out anymore.

Further update.. The person who had this did say in a text message that the repeater is all up to date now . They said it was working perfect.. Day we got it back first thing we noticed was this issue.
Im still thinking its because of the FW upgrade. Was working fine prior to the update. I assume no way to revert back is there?

Ill crack the case and have a peek at the RIB
 
OP
Muxlow

Muxlow

Banned, Bad boys, bad boys, whatcha gonna do, what
Joined
Dec 12, 2012
Messages
176
Cracked the case, Wires were all connected. Didnt fix the issue

Did the IP beacon suggestion and this seems to be working.. Might be to be what we deal with for the time being
Until i can get my hands on a new version of the repeater FW and see if it fixes it... This is working for now at least to get it back on the air
 

radiotechs

Contributing Member
Joined
Nov 26, 2014
Messages
57
I dont know what that would be off the top of my head but

Have you done the good ol recover option to default the codeplug in it ?

I have had some oddball faults that show everything as right but recovery fixed it

Cracked the case, Wires were all connected. Didnt fix the issue

Did the IP beacon suggestion and this seems to be working.. Might be to be what we deal with for the time being
Until i can get my hands on a new version of the repeater FW and see if it fixes it... This is working for now at least to get it back on the air
 
Status