Firmware Friday?
- Status
Firmware Friday?
Thanks UPMan! Anything that can be done to reduce the CPU load to resolve the laggy/unresponsive keypad issue during transmissions or has that also been addressed in the latest firmware?
BigC801
Member
I thought i was the only one, I have to hold most buttons for 15 seconds or so to get it to respond.
Hold and volume button have always taken 3 presses or so to work but now it's almost unusable.
FYI, The NXDN DFA improvements worked with the ESPN CT system. I still have the channel change event to overcome. Since there is only one frequency programmed in, obviously it cannot change channels. One of the channel changing events was captured in a recently posted log.
I am looking for the procedure to program the additional channels into the DFA system. I tried programming a duplicate system with multiple channels into the radio but there seemed to be issues getting the radio to lock onto the control channel after the LCN finder was used.
I probably will never monitor the system again but want to assist getting the radio working correctly for it.
chris
I am looking for the procedure to program the additional channels into the DFA system. I tried programming a duplicate system with multiple channels into the radio but there seemed to be issues getting the radio to lock onto the control channel after the LCN finder was used.
I probably will never monitor the system again but want to assist getting the radio working correctly for it.
chris
Now that is an issue.. I would send it in for repair.
Not necessary if it only happens while a conversation is in progress. I've been reporting this in the last two firmware releases, as have others. Laggy or unresponsive key pad while a talk group is active. UPMan reports a new firmware update is on the horizon, let's see if this is resolved.
If the unresponsiveness occurs only while a transmission is being received, then it is not an issue that can be resolved by replacing the keypad contacts. It can only be fixed by rewriting the firmware to load the CPU less when decoding the problem system(s).
Maybe they are only insulting to you because you are insulting to them. You've had more than your share of rants about how things are not as you want them to be, or as you expect them to be, or even demand them to be.
Regardless, insulting them is likely not going to be productive, and is rather hypocritical don't ya think?
As someone who tries to help anyone, regardless of model fandom, maybe the above advice might help.
I'll be happy tomorrow when this thread is taken down and we can start over again...lol! But thanks to Jason Houk and UPMan for their assistance. I've never done a Debug File before and because of Houk's patience, I was able to get it in the right hands. UPMan followed up and tomorrow we'll probably see the results.
D
DaveNF2G
Guest
What marks it as a probable unit repair issue is that it is only reported to be that bad by one user. I have the same scanner and firmware and I have never experienced the sluggish keys issue.
I think this answers it pretty well and makes sense. Probably more users have this issue but don't report it. If it didn't happen only while scanner was showing an active talk group/channel etc., I would agree it's an issue that repair needs to address. If scanner is in Scan or ID Scan mode, keypad responds as normal.
Last edited:
Bolt21
Spark Chariot Driver
I have had the sluggish key issue as well. I can't remember the exact circumstances, but I think I was scanning an EDACS system and an NXDN system at the same time. Keypad ignored input while there was a transmission.
Back from my trip and watching the display on the 436HP more closely. I'm seeing a lot more of the Aliases than I was before the trip. I also see new sub menus (or at least ones I've never noticed before) that allow me to save Aliases.
I'm not seeing any false IDs so far.
When using the 536HP. One "Siren" thing I've noticed is that NX4 does not display on the screen. Con does display on MotoTrbo systems when a control channel has been found. On a guess, that is not being sent in the data stream to program.
I'm not seeing any false IDs so far.
When using the 536HP. One "Siren" thing I've noticed is that NX4 does not display on the screen. Con does display on MotoTrbo systems when a control channel has been found. On a guess, that is not being sent in the data stream to program.
- Status
