Just to confirm, you are sure that the "false talkgroups" showed up when running the 10-18 firmware and that they didn't show up from earlier versions? Are they showing a bad sys_id in the talk group table as well?
P25RX P25 Phase 1/2/DMR Receiver With Bluetooth Audio Support
- Thread starter btt
- Start date
- Status
I was able to re-produce the "false talkgroup" issue. It wasn't due to crc-related code. It was caused by a talk group variable that didn't get reset on the first channel grant after switching to a different control channel. Hopefully that is fixed in the newly available testing version 2020-10-19_1030. The firmware update should also take fewer resets to complete now. The device will no longer reset when saving the configuration unless the power-on mode is changed.
[edit]
Please let me know if you still have issues with this after updating. Thanks!
One more small change, 2020-10-19_1053 available.
[edit]
Please let me know if you still have issues with this after updating. Thanks!
One more small change, 2020-10-19_1053 available.
Last edited:
I apologize for posting the previous version too soon. The previous "testing" release had a different, but significant issue where the blks_per_second were dropping to zero. It appears that issue is now resolved in testing version 2020-10-19_1333. This version may be approaching something that can be considered "stable". I'm going to wait for feedback from a couple of users before marking it that way.
boy7777777777
Member
Been monitoring for a while and no false talkgroups appearing anymore.
I haven't seen any more issues with the blks_per_sec dropping to zero after more than 7 hours of logging. The new end-of-call detection appears to work correctly on Motorola, Harris, and Tait P25 P1 systems / voice channels. VHF is still working good here. I'm going to wait for Mike to respond on the talk-group bleed-thru issue when he gets time before calling it "stable", but I think the current version is doing good. (2020-10-19_1333).
Last edited:
Yes. I've started to design a prototype. More later.
edit- just to be clear, the intent is to develop a display option that is 100% compatible with the P25RX design as it is.
- Joined
- Mar 16, 2004
- Messages
- 131
Got my unit and it working great on NC Viper P25 800 systems however I am little confused about how the priority or talk group over ride works in tips and Tricks it states that at 1 it is ignored and it I set a channel to 0 is that how it works and it says On grants with multiple talk groups, the talk group with the higher priority will be used. So does this mean I got to assign a different number to the other talk group or is it the closer it is to the top of the talk group list the higher the priority is
I like the idea, but I would also like to see some type of smartphone based app as well. I really think that would open a lot of possibilities as well as generate additional interest as a portable setup. I've mentioned it a few times and I'll reiterate I know nothing about how the creation of such apps and any integration into the app stores works, maybe it is too much trouble and the display approach is a better idea. Or, maybe there is room for both.
I use the heck out of the iPhone app for my ICOM R-30 when I'm "signal stalking" somewhere. Keep the R30 in the backpack, fire up the Jabra earbuds, and no one is the wiser...unless they look real hard and see an antenna poking out.
App development for smartphones can be expensive, time consuming, and a never ending source of complaints. A display would be just fine though I wouldn't complain if someone finds the time to get an app developed as well.
First of all, thank you! I'm glad to hear that it is working well on the new NC Viper system!
Unless the pri_always command is used to "enable" conversation interruptions, the priorities will not be considered during the talk-group timeout period. You can enable the "pri_always" option. e.g.:
$ pri_always 1
$ save
Once this is done, then the priorities defined in the talk-group editor table will be used. The current implementation is very simple. If the incoming channel grant has two talk active talk groups, and both of the talk groups are enabled, then the one with a higher value will be used.
I'm open to changing how this works.
Thank you for the feedback on this. I looked into app development way back when Android was just starting to take off, but I lost interest quickly once I figured out that apps didn't actually use the Java language, but something called Dalvik. In short, I don't currently have any phone app development skills. Would love to see someone take this on though... It might be that an open-source display option will spark some interest from some developers...
I just started working on the hardware design for the display option, but it is coming along quickly due to design re-use. I don't plan on getting too sidetracked with this. I don't usually like to describe hardware that doesn't currently exist, but I think it might be a good idea to share some thoughts/seek feedback on the display at this point.
Current Plans:
Open-source / Open-hardware, ST32H7-based MCU design (USB Host)
Firmware in 'C' language / GCC environment
STLink / DFU programming
320x240 Color Touch Screen (ILI9341 controller)
Audio Line-out? (would be redundant, but might be useful).
1 Watt surface mount speaker / amplifier
16M NOR Flash
Type-C USB Power-only connector (provides power to the system when using the display with the P25RX)
Micro-AB USB Power/Data connector. A short Micro-USB-to-Type C cable will be used to connect the display to the P25RX (provides host interface / power to the P25RX when in display mode, firmware updates for the display)
The display could interface with the P25RX firmware as-is, but I'm thinking it may be useful to add another power-up mode to the P25RX firmware specifically for the display. In this case, the display board could become the "brains" while P25RX would provide decoded audio/symbols/etc. This would allow developers to fork the code (if desired) and create alternate modes of operation, new features, etc.
Thoughts?
The idea is to keep it somewhere close to credit-card-size dimensions for length / width so that it can be attached to the top of the P25RX enclosure.
-----------------------------
On another topic, I just received some feedback from a new P25RX owner that found that the audio was much better for him when he set the talk-group timeout to 500ms (vs the 2000 ms default). Do you you guys usually change your timeout to something lower than the default? I'm wondering if I should change the default to 100ms? 500ms? Any thoughts on this?
markburnley
Newbie
- Joined
- May 3, 2013
- Messages
- 2
Todd, I have now adjusted to 250 ms and that seems to be the sweet spot for the Atlanta P25 phase ll system for me. Perhaps it is site specific??? I dunno, but I’m very pleased with my P25XR after making the necessary adjustments to run on my computer. I will be testing mobile in the next week or so.
Mark, that is good news! Thank you for posting your results.
- Status
