UniTrunker Feature Requests

[FlashSWT]

One other thing that I brought up a while back - When you do [F]ind -> ser, the Users page is displayed automatically on the bottom half of the screen. If you choose to type the decimal or hexidecimal ID address in manually, I always thought a great feature would be to have the green horizontal scroll bar in the Users list automatically scroll to that line that the ID is located on.

Count me in for this feature request!

.

 

[FlashSWT]

that user interface is history, BTW.

Haha, forgot about that. I guess we should all slow down on the feature requests until the new version gets released!

.

 

[mtindor]

I want to see support, for Commersial Amateur radios, like Yaesu Cat interface and so on...

I guess that might be _okay_, but although most Yaesu commercial amateur radios that can receive 450 / 800 mhz have pretty wide receive, they typically don't have the needed sensitivity outside of the amateur bands. 450 mhz isn't that far from 440 mhz, but decent 800 mhz reception is a stretch.

... then again my radio is 9 years old.

Mike

 

[inigo88]

Thanks Rick, I believe it's coincidental that they're catagorically numerically close, but the point was to compare with the alpha tags of known confirmed radios to infer an educated guess, until an actual confirmation would be made. I think it's terrible practice to name a user ID before you've actually heard and observed its use, but it sure is nice to look at all the green and be able to make educated guesses as to what it might be.

I'm excited to hear the new program tries to tackle this problem in some way though, and I'm looking forward to seeing it!

Thanks, and I'll see if I can grab you a log of a 3600 Type II page message. Are there any threads on here or pages you know of that explain the Motorola OSW format so I can verify I have a good example?

-Inigo

 

[SCPD]

Are there any threads on here or pages you know of that explain the Motorola OSW format so I can verify I have a good example?

None I've seen. It should appear as "Page" or "Message" in the Affiliations log. Worst case is a shotgun approach - drop me a full day's log and ... if one was used at all that day - I should be able to find it.

 

[ronenp]

My Feture request

1) to show the site alias near to the site number in multi site Networked systems
2) to have option to see all the site messaging (i.e Busy signals or reject to non authorised users or gid)

Thanks Forward
Ronen
http://www.ronen.org

 

[DualC]

I guess that might be _okay_, but although most Yaesu commercial amateur radios that can receive 450 / 800 mhz have pretty wide receive, they typically don't have the needed sensitivity outside of the amateur bands. 450 mhz isn't that far from 440 mhz, but decent 800 mhz reception is a stretch.

... then again my radio is 9 years old.

Mike

Hi Mike

I understand what ur thinking about, and yes... a normal swedish or maybe all amateur stations not use 800Mhz bandplan, thats true.

But in sweden we got Trunked systems in 166Mhz, not far from 145Mhz (2Meter amaturband), and also on 460Mhz, not soo far from 434Mhz (70cm amateurband).

I got wery god signals from both bands and i can decode both's GOOD in Unitrunker, but the only thing is what i cant get my radio to the talk channels cose Unitrunker cant handle it.

But anyway it's Ricks thougt about it who count in the end..., i should be wery glad anyway if he build a simple CAT support, cose it's many Yaesu radios who got large RX span, and acculy will work well as a scanner reciver.

Anyway in my radioshack i will use my UBC 760 XLT to run on trunk data channel, and i wont my Yaesu FT-7800 to follow the voice channels.

/M

 

[slicerwizard]

Thanks, and I'll see if I can grab you a log of a 3600 Type II page message. Are there any threads on here or pages you know of that explain the Motorola OSW format so I can verify I have a good example?

Type II Call Alert (page):

[308 I TargetRID]
[319 I SourceRID]

First RID is radio being paged.


Type II Call Alert Ack:

[308 I TargetRID]
[31A I SourceRID]

Second RID is radio being paged.

 

[SCPD]

Andrew - thank you.

Inigo88 - the Unitrunker log format is different from Andy's examples. Here are some actual log examples from my archive of old logs.

UniTrunker-20061122.LOG:
09B7 I 319 Page Signal Sent 09B7 -> 0DAA
09B7 I 319 Page Signal Sent 09B7 -> 0D46

UniTrunker-20061123.LOG:
3C5D I 319 Page Signal Sent 3C5D -> 75DE

UniTrunker-20061124.LOG:
3C60 I 319 Page Signal Sent 3C60 -> 7543
3C60 I 319 Page Signal Sent 3C60 -> 5FFA
3C60 I 319 Page Signal Sent 3C60 -> 5FFA

UniTrunker-20061126.LOG:
37D2 I 319 Page Signal Sent 37D2 -> F765
37D2 I 319 Page Signal Sent 37D2 -> F766
37D2 I 319 Page Signal Sent 37D2 -> F765

UniTrunker-20061202.LOG:
3C57 I 319 Page Signal Sent 3C57 -> 756C

UniTrunker-20070513.LOG:
08EE I 319 Page Signal Sent 08EE -> 0D90
08EE I 319 Page Signal Sent 08EE -> 0D7C
0D7C I 319 Page Signal Sent 0D7C -> 08EE
0F51 I 319 Page Signal Sent 0F51 -> 0F8A
0F8A I 319 Page Signal Sent 0F8A -> 0F51

Good news is some of these "hits" are from a local system I believed not to use these messages. Now that I've got something local for testing - this should be easy to fix. Here's a complementary pair from an old log.

75DE I 308
3C5D I 319 Page Signal Sent 3C5D -> 75DE

3C5D I 308
75DE I 31A Page Acknowledge 75DE -> 3C5D

In summary - look for the word "Page" in your logs.

 

[SCPD]

But in Sweden we got trunked systems in 166Mhz, not far from 145Mhz (2Meter amateur band), and also on 460Mhz, not so far from 434Mhz (70cm amateur band).

I should be very glad anyway if he build a simple CAT support, because it's many Yaesu radios who got large RX span, and actually will work well as a scanner receiver.

Do the CAT interface command codes look something like this?

All serial data consists of single byte binary codes sent at 4800 baud, TTL levels, with two INVERTED stop bits and one INVERTED start bit.

Key Codes:

CAT Control consists of duplication the keystrokes that can be made on the tranceiver keypad by sending the corresponding keycodes to the Serial Keycode Input contact of the CAT jack. The most significant four bits (MSD) correspond with the key column and the least significant four bits (LSD) correspond with the key row. The Function key (on the side of the tranceiver) is simulated by setting bit 7.
Results are identical to those described for manual operation in the FT-727R Operating Manual. Serial Meter Output is sent approximately every 100 ms while receiving.

[Table for the codes. The lines in [] are the original values in the Yaesu handout, and are followed by the corrected lines as determined by KB7ABA. Remove the lines in [] to see what should be the right table.]

[   @ FUNC  F   E   D   C   B  ]
    @ FUNC  8   9   A   B   C
MSD @
[   @ NORM  7   6   5   4   3  ]
    @ NORM  0   1   2   3   4

LSD
V

E  +RPT  SIMP -RPT  PMS  P SET
     1    2     3    V     c

D  SAV-T T-DEC T-SET TX-M S/CH
     4    5     6    M    MR

B  SAVE T-ENC  SCAN  MC   Shift
     7    8     9    C    <=>

7  LOCK  BATT  BEEP  DUP  Step
     *    0     #   V/U    D

The biggest hurdle is the start/stop bits. By "INVERTED", I think the quoted text above means - relative to normal RS232 signals - the CAT interface inverts the signal for me.

I can do this. I'd create a test program specific to the Yaesu models that support this - and send it out to for testing by folks like you that actually own one of these radios. Once the basic mechanism for sending key-codes to the radio was validated, I can send the appropriate key sequences to direct the radio to a voice channel. I might be able to look at this later this spring or summer. We added a large number of receivers in '06. This looks like a good way to add a block of Yaesu models.

I do anticipate being clobbered by bug reports and feature requests for the new program so we will have to see where and how the dust settles.

 

[mtindor]

Although my FT-100 has a CAT interface and can be controlled by software, it does not have the same subset of CAT commands as some of the higher end/newer CAT-controlled radios do. So one must be cautious of what commands is wanting to use and understand that not all commands work in all radios.

I think simple setting of frequency/mode certainly works with all now that I think about it.

My particular manual (for a radio that doesn't have all the CAT commands that some of the newer does) can be found at:

http://www.k0lee.com/images/FT-100D Manual.pdf

Page 96 or so is the CAT programming description.

No, I'm not looking for anybody to support my radio. Even though I can receive 800 mhz (where all the trunking is around here), the receive performance is so degraded that it isn't worth it for me. In DualC's circumstance, I can see where it would be very handy to have Unitrunker work with his radio.

Mike

 

[Liverdog]

Api?

Rick, are there any APIs with UT? I'd like to call the current (active) TG and use it.

Thanks

 

[SCPD]

There isn't an external API. The decoder layer provides an event stream. Defining which group IDs are of interest (eg. selecting which becomes the "current group") occurs at a higher level. That chunk of logic happens to be going through a re-write at the moment.

Down the road I'll have time to look at options for annunciation which is a fancy way of saying perform action "X" when you see event "Y". Any number of possibilities exist for "X".

 

[DualC]

Ohh, i have missed some post here.. thanks rick for taking up my suggestion.. i have seen some information on the net how to program the the Yaesu radios ....

if u look in this PDF...

http://www.mobinet.se/Details/man10208.pdf

and, have a look at page 116 to 118, u will se how to program the Yaesu radio for some models... i have a FT-857D, but i also got a FT-7800 which i want to use with unitrunker.

BUT i got trouble to find ut how to send codes to that radio... cose it's seems to use some other commans, i will dig and se if i can find some of the information on the net..

/M

 

[inigo88]

Hey Rick, here's the log for the Type II Call Alerts (Pages) preceding ambulance-hospital patient reports on my local Motorola Smartzone system.

User IDs:

9AD0 - Ambulance A-19
59DC - Nurse Handset

Group ID:

AF70 - XXX Hospital Consult 1

The network status data that repeats throughout and will be omitted in the rest of the example:

6001 G 3BF  Network Status
4B00 I 3BF  Network Status
30E0 G 3BF  Network Status
4000 G 3C0 	Status[2] = 0000
30E0 G 3C0 	System is Type II VHF/UHF Connect Tone=138.46 Hz

The Type II Call Alert (page) message:

59DC I 308 
9AD0 I 319  Page Signal Sent 9AD0 -> 59DC

The Type II Call Alert ACK (Page ACK):

9AD0 I 308 
59DC I 31A  Page Acknowledge 59DC -> 9AD0

And the following conversation. Nurse picks up the handset - "This is Marin Go Ahead..."

59DC I 032 
AF70 G 1AE  Channel Grant  1AE I 59DC -> G AF70

"Hello Marin this is A-19 coming at you with... [boring patient info]."

9AD0 I 04B 
AF70 G 1C7  Channel Grant  1C7 I 9AD0 -> G AF70

I'm glad we're talking about the same thing, since this does indeed jive with the local examples you found. I'd love to see it show up in real time in new versions of Unitrunker.

 

[campd715]

Rick,

This is a request to ask you to reconsider a previously asked for feature (an expanded HOLD ability) for Unitrunker.

The activity field displays several T/G's at the same time and you're listening to the one with the highest priority setting when all of a sudden an unknown T/G or RID appears in the activity field. Hitting the F8 key will hold the current T/G (highest priority) but not necessarily the desired unknown T/G.

Mtrunker has the hold ability (letter H) like Unitrunker's F8 key but Mtrunker allows you to instantly toggle through and hold onto any other displayed T/G in the activity field by use of the up/down arrow keys. With this ability I can quickly move from the current hold (highest priority T/G) to the unknown T/G (lesser priority) and immediately hear the voice activity thus increasing my ability to perhaps identify the user of the unknown T/G or RID.

The future Unitrunker release (History feature) will be great if you happen to HEAR the radio user self ID but miss the RID. Go to History and you can then pair the two up, however if you don't hear the voice the History feature won't help.

Hopefully this makes sense in the way I've explained it and I've convinced you into implementing this requested feature.

Thank you very much for Unitrunker.

Dennis

 

[CompKing]

Sounds like a lot of great ideas here. Though a pretty significant change in the user interface is pending. Sounds like a lot of people are anxious to see the new interface. Any clue on when this will be released to the public and/or a beta test group??