When Will Sentinel Support DMR ?

[UPMan]

Biggest issue right now is CAP+ with RAS. No local systems and no closed beta testers have such a system. Need logs for the engineer to study. This is really the last big task before we move from Pre- to release on the firmware side. Just need to be sure we don't need to add a software flag for RAS (which would affect Sentinel and RRDB).

 

[trumpetman]

Biggest issue right now is CAP+ with RAS. No local systems and no closed beta testers have such a system. Need logs for the engineer to study. This is really the last big task before we move from Pre- to release on the firmware side. Just need to be sure we don't need to add a software flag for RAS (which would affect Sentinel and RRDB).

As long as I don't have to jump through too many hoops I can try to help, just tell me what you need/how to do it.

I have an 8 channel system down the road that stays fairly busy during the week and slows down but is still used on the weekend. RAS enabled, no encryption. And I have the verified LCN to compare LCN finder/whatever else too.

 

[UPMan]

Ideally multiple scanners simultaneously monitoring each frequency conventionally while logging (you probably don't have 8 scanners to dedicate to this). Less ideally, multiple scanners splitting up the frequencies and scanning them conventionally (i.e. 4 frequencies on each of 2; 2 frequencies on each of 4, etc). I described it as a need for a log file that will be nearly impossible to capture.

Log file capture is AVOID while powering on. Then, in the Settings menu there is a logging option you set to SD Card. Start logging. Set logging back to Off. Send the file(s) from the scanner's debug folder.

 

[trumpetman]

Ideally multiple scanners simultaneously monitoring each frequency conventionally while logging (you probably don't have 8 scanners to dedicate to this). Less ideally, multiple scanners splitting up the frequencies and scanning them conventionally (i.e. 4 frequencies on each of 2; 2 frequencies on each of 4, etc). I described it as a need for a log file that will be nearly impossible to capture.

Log file capture is AVOID while powering on. Then, in the Settings menu there is a logging option you set to SD Card. Start logging. Set logging back to Off. Send the file(s) from the scanner's debug folder.

I'll see what I can do this weekend. Thanks for the instructions.

 

[ProScan]

Not to worry, someone will soon jump in and post something along the line of:

"well it couldn't be that hard to tweak something here or there"

and I guarantee this "expert" will be someone who has never sat looking at the compiler and wondering what just happened

Let me jump in and say it's not that hard.

Basic steps are:
1. Search the source code for the existing system types(P25 Trunk, P25 X2-TDMA, etc...) and add the new system types(DMR,CON,CAP,DT3) to the combo box.
2. Add Color Code Option(Search or Set Color Code)
3. On the Uniden weekly pull from RR, Retrieve the DMR systems.
4. Test Full Database by writing to the scanner and check the scanner
5. Test Favorites by writing to the scanner and check the scanner
4. Change the Project Build to Release
5. Build Project
6. Test again from a user perspective
7. Distribute

[EDIT] I think it could take one day to do and one more to test every scenario. A snag may be the RadioReference data structure and that case will take longer.

 

[KA2ZEY]

What is the rush to get this working in Sentinel?? Have you squeezed every possibility out of the beta release? You know that you can program a system by hand?

 

[fourthhorseman]

You know that you can program a system by hand?

Or..
Get the DMR Release of ARC..
Use the trial to do the bulk programming..
like Alpha tags,Channels,Mod ect..

Then EDIT by hand....Might help reduce
the sweaty palms.. ;-}

 

[SCPD]

DMR release of ARC has been working really well.

Sent from my SM-G900W8 using Tapatalk

 

[dave3825]

Or..
Get the DMR Release of ARC..
Use the trial to do the bulk programming..
like Alpha tags,Channels,Mod ect..

Then EDIT by hand....Might help reduce
the sweaty palms.. ;-}

That wont work for anyone who tried any 436/536 demo program in the past..

 

[mancow]

Let me jump in and say it's not that hard.

Basic steps are:
1. Search the source code for the existing system types(P25 Trunk, P25 X2-TDMA, etc...) and add the new system types(DMR,CON,CAP,DT3) to the combo box.
2. Add Color Code Option(Search or Set Color Code)
3. On the Uniden weekly pull from RR, Retrieve the DMR systems.
4. Test Full Database by writing to the scanner and check the scanner
5. Test Favorites by writing to the scanner and check the scanner
4. Change the Project Build to Release
5. Build Project
6. Test again from a user perspective
7. Distribute

[EDIT] I think it could take one day to do and one more to test every scenario. A snag may be the RadioReference data structure and that case will take longer.

I wish they would hire you to write for them.

 

[DaveNF2G]

Ideally multiple scanners simultaneously monitoring each frequency conventionally while logging (you probably don't have 8 scanners to dedicate to this).

Fairly simple with SDR.

 

[buddrousa]

Unless you are looking for how the scanner is handling the data.

 

[Dewey]

Biggest issue right now is CAP+ with RAS. No local systems and no closed beta testers have such a system. Need logs for the engineer to study. This is really the last big task before we move from Pre- to release on the firmware side. Just need to be sure we don't need to add a software flag for RAS (which would affect Sentinel and RRDB).

I have several CAP+ plus systems near me, one that I listen to regularly. I'm at a brain loss right now for RAS. Please remind me what that is in case I can help.

 

[W6KRU]

I have several CAP+ plus systems near me, one that I listen to regularly. I'm at a brain loss right now for RAS. Please remind me what that is in case I can help.

Restricted Access to System (RAS): prevents the unauthorized subscriber users from using the repeaters in the radio system and listening to repeater outbound voice/data/CSBK transmission, through the use of RAS Key authentication and Radio ID Range Check. This feature is supported on all MOTOTRBO subscriber platforms, as well as on XPR8300. XPR8400, XPR8380 and MTR3000 repeaters.

----

This essentially means those who choose to do so, can LOCK OUT unauthorized listeners from a repeater/system. This is not good. No more "I got the slot, color code and call group, and that's all I need".

 

[fourthhorseman]

That wont work for anyone who tried any 436/536 demo program in the past..

well..then those who had the option,and let it lapse should not gripe..and quietly wait. or learn how to do full uninstalls of software trials.

those that can exercise the option, have it at their disposal.

 

[fourthhorseman]

DMR release of ARC has been working really well.

Sent from my SM-G900W8 using Tapatalk

Yes it has.. Glad I upped to the Pro version when I did the Provoice upgrade...

 

[DaveNF2G]

Restricted Access to System (RAS): prevents the unauthorized subscriber users from using the repeaters in the radio system and listening to repeater outbound voice/data/CSBK transmission, through the use of RAS Key authentication and Radio ID Range Check. This feature is supported on all MOTOTRBO subscriber platforms, as well as on XPR8300. XPR8400, XPR8380 and MTR3000 repeaters.

----

This essentially means those who choose to do so, can LOCK OUT unauthorized listeners from a repeater/system. This is not good. No more "I got the slot, color code and call group, and that's all I need".

It seems to me that, once again, Motorola has sold the word "privacy" under a very limited definition. For people who have subscriber units, PL, Privacy Plus and RAS work as advertised. They keep authorized system users from accessing communications that they should not.

However, none of that has any impact on an outsider with a compatible receiver that ignores the so-called "privacy" features on a system. All Uniden needs to do is make sure that the extra data does not disturb normal decoding.

 

[DaveIN]

Restricted Access to System (RAS): prevents the unauthorized subscriber users from using the repeaters in the radio system and listening.

This essentially means those who choose to do so, can LOCK OUT unauthorized listeners from a repeater/system. This is not good. No more "I got the slot, color code and call group, and that's all I need".

My local RAS is 95% encrypted, and I expect more to come on other systems, now that "scanners" can hear DMR systems in general, notwithstanding RAS enabled systems.

it's unfortunately a hazard of the hobbie. Gain a new decoding mode, loose ability to monitor when encryption is enabled.

But then again, this is getting off topic. The DMR mode has just been added to the x36HP, and is still *beta*. I suspect when resources are available, and the RC1 become "released", we'll most likely see an updated Sentinel.

 

[marcotor]

Hahahaa. Thanks Bob !

 

[DaveIN]

The first update release of sentinel may be the day of the full firmware release?