I see you are next door to me, in Chester County. Have you tried listening to Lancaster County Fire/EMS?Off topic question, are there any Chester County PA users out there?
I see you are next door to me, in Chester County. Have you tried listening to Lancaster County Fire/EMS?Off topic question, are there any Chester County PA users out there?
Thank you. It has been working really well here too.Going strong on the new build Todd, good stuff man
That sounds like bugs in the BTConfig software itself, not firmware. If you figure out a way to reproduce the issue, let me know and I will get it fixed. Btw, the issue that I mentioned previously regarding ESD causing BLKS/SEC to drop to zero turned out to be a one-shot-reset hw interrupt process that would get knocked out by an ESD event (Not the USB interface). That interrupt process recovers fine with the new firmware. I believe this version is the most rock-sold, best sounding yet.Minor... but BTConfig locked up once, P25 was still sending audio, reloaded BTC and it was fine. also once the p25 would not be rediscovered after a config download. Kept trying and cycling through. Cycled P25 power and it came back up fine. Still two thumbs up.
Just did it again. steps were. I plugged the P25 in but BTC not running, started it afterwards. Didn't ID it, unplugged P25, plugged it back in it synced. Not a big deal. Have a great weekend.That sounds like bugs in the BTConfig software itself, not firmware. If you figure out a way to reproduce the issue, let me know and I will get it fixed. Btw, the issue that I mentioned previously regarding ESD causing BLKS/SEC to drop to zero turned out to be a one-shot-reset hw interrupt process that would get knocked out by an ESD event (Not the USB interface). That interrupt process recovers fine with the new firmware. I believe this version is the most rock-sold, best sounding yet.
Thank you sir! I will see if I can reproduce it. You have a great weekend too.Just did it again. steps were. I plugged the P25 in but BTC not running, started it afterwards. Didn't ID it, unplugged P25, plugged it back in it synced. Not a big deal. Have a great weekend.
Hi Todd,Thanks for reporting on the 'add_tdu_silence' option. I am going to make this option default off for the next release.
That option was changed to be default off, but the description was not. Thank you for pointing that out. I do think you should try turning the option on and see if that improves the issue you have been having with audio. This option was default "on" in previous versions.Hi Todd,
I just noticed that in _0709, the default is “ON”. I had not realized that when I tried _0709, since it was going to be “OFF” for future versions.
I am going to disable and listen for awhile.
There will be more options added soon, but for now the easiest way to accomplish this is to the set the value very high for the "switch control channel after" xx seconds of inactivity option. Set this to 300 seconds for example. If the signal goes from readable to "lost", it will only take 10 seconds before it starts looking for a new control channel. Once it starts searching, it will only stay on a dead (no signal / sync words) channel for milliseconds until it once again find a signal.Is there an option to have it roam but it only changes to another control channel if it looses signal from the current one?
Hi Todd,
Attempted to load 3-17_1109 but am stuck. Unable to get the 25RX to run. Has the 4-Flashes on power up. I tried holding the TG button during powerup both the short duration and long duration. Was there an alternate method?