Could there be some interference on a frequency adjacent to the control channels involved in the boot loops that's messing up the data stream? An SDR would reveal that if there was.
It shouldn’t, anyways I’m going through StLouis in an hour, creating a new codeplug from scratch to see what happensCould there be some interference on a frequency adjacent to the control channels involved in the boot loops that's messing up the data stream? An SDR would reveal that if there was.
Yep, I suspect the same thing as the possible cause of the G4 reboots.yeah it must be something sent from the system that the unication doesn't like for some reason
Yes, that's a great idea. I forget they have diagnostics built in to the device.probably need to run a diagnostic log on the G4,
That's amazing that the G5 handles that site 201 so darn well yet the G4 has these odd reboot issues.I was driving in the north side of downtown STL today, MOSWIN on St Louis North Simulcast was almost impossible to monitor. Reboots, screen come on with no radio traffic. Radio traffic come on 1/2 way through a broadcast. then reboot again. Good thing I don't have to rely on my G4 to respond to anything.
I agree fully with the different hardware generations theory.I don't know for sure, but I've always assumed that the G4 and G5 use the same "main board" inside, and the difference between them is that the G5 has a secondary band radio module (and internal antenna) inside, where the G4 does not. I know that there have been different generations of the hardware (different CPUs, etc). If we have a G5 that works and a G4 that doesn't (the same firmware and programming), I think it's more likely that they're from different generations, rather than a G4 vs G5 difference. I would want to be sure that the programming is identical (preferably clone the profile) first, though.
I know 2 Illinois Volunteer departments that use unication G5 for calls. the city of st louis fire chief uses an iphone app for calls.That's amazing that the G5 handles that site 201 so darn well yet the G4 has these odd reboot issues.
I would like to think the firmware for both models is made from the same source so that may leave some odd hardware difference as the culprit.
I don't know anyone in this area that uses or needs a Unication for official use on the Slater or Moswin system so I always wonder if there are any users with the need.
Most fire heard on Slater still uses VHF analog channels for tone-outs so those users still use one of the Minitor version of pagers. The use of analog channels for tone-outs seems to be true not only in St Louis county areas but the Jeffco and St Charles areas as well. I've found the analog tone-out frequencies used for most of the fire agencies in those three counties. I've always wanted to log the tones for each and match them up with the house or apparatus being dispatched by tone-out but it looked like a bigger job than I wanted to tackle so I gave up on that idea.
I'm not sure how they page out or dispatch city fire and ems. I know they don't broadcast a call to each house and can selectively select which house(s) get a call but I never knew how they do that since going to the UHF analog trunked system many years ago now.
I do recall that city fire was very hesitant to move to a trunked radio system even when it was an analog system back in the day. They finally gave in and of course many changes have occurred to the radio system since then such as the move to a true digital system using P25.
Hopefully Unication will figure this one out.
I'm using a G4 (v1.31) on the Tennessee Advanced Communications Network and have been dealing with an odd issue for over a year now. The Windrock Site (RFSS 2/ID 11) constantly causes the G4 to reboot. Last week I was in the area and the fun began immediately. It rebooted at least 5 or 6 times in about 15 minutes.
As soon as the G4 roams to a new site the problems go away. I have 16 other sites in the site list and never experience any issues with those. I've tried setting the site ID as FF to see if it makes any difference but it did not.
Has anyone else had this issue or something similar?