Close Menu
    piatok, 22 mája
    New topic in the forum Add an ad

    Call channel on DMR

    Published in: Very short waves

    • Visitor
      Anonymous on March 12, 2018 at 6:24 PM #11485

      Hello DeeMeR people 🙂

      Given that several of us at DMR are under different TGs,
      and then we can't find each other on the band, I suggest to everyone - who wants to be easier to reach for others - to be QRV on TG 2311. This TG works in TS1, on all (only) OM DMR repeaters.

      TG 2311 could be a nationwide DMR repeater call channel, and whoever would be interested in talking longer, or would not want to disturb others with their operation, would tune to another TG – e.g. a local repeater, two linked repeaters, or any TG “on request” in TS2, such as TG 23110. Thus, the network would also be maximally relieved, because practically only one or two repeaters in TS2 would be in operation (unless someone on another repeater also requested the given TG by keying, which would of course be fine). And the “call” TG 2311 in TS1 would function independently of that.

      And what do you think, friends, how do you see it?

      Geyza, OM7AJK

      Reply
      Participant
      om1aeg on March 16, 2018 at 1:48 p.m. #14969

      Hello Geyser,

      You don't include the use of TG231 / TS1 in your proposal. It would be sea suitable as a callsign than 2311 / TS1. Everyone has it programmed in their radio, usually assigned in the RX group when preselected to TG2311 and possibly also to others. Currently, TG231 is not used much due to TX restrictions on all OM+OK operators.

      TG2311 should remain for 'all-Slovak' chat and if it bothers someone, let them remove TG2311 (TG230) from the RX group from the TG231 preset. I don't think TG231 / TG2311 would be particularly used for long OM chats. Statistics are available at: https://brandmeister.network/?page=callstats select TG231x.

      TG23110 is a long-term agreement, it's just not being used the way it should be, it's just a matter of user habits.
      The same applies to the use of TG230 in OK, where there has been an agreement on TG23010 since December 2016. Unfortunately, they do not have an agreed 'national' TG like we do, and an agreement to use something other than TG230 is not easy, as it requires changing the codeplugs of the users, so they use TG230 (which is also common in our country from most RPT).

      In my codeplugs that have 'a few users' in MD-380 and GD-77, I have 2311 assigned to the TG231 preset in the RX group and vice versa, so your suggestion is 'compatible'.
      Chat 23110 / TS2 for each OM RPT will be implemented in the next version, I am making major changes to the codeplug for MD-380, mainly regarding new rpts and different inclusion of TG230 in RX groups / presets. The codeplug for GD-77 already has it implemented.
      In case of agreement on TG231 as the 'caller', I can redo the RX sheet for the TG231 prefix, removing TG2311 from it.

      Created a page for codeplugs https://sites.google.com/site/prevadzace/om-dmr-codeplugs
      with a link from the list of operators https://sites.google.com/site/prevadzace/

      Reply
      Participant
      om4dw on March 16, 2018 at 2:51 PM #14970

      Hello.

      Geyser, I completely agree with what you wrote, and somehow I also have DMR turned on.
      In other words, I listen to 231, 2311 + I also scan the analog Bozena, where it's quite lively.

      I have a 16-channel Motorola radio at home, without a display (or only channel numbers 1-16).
      1. RX 230, 231, 2311, and those weather jokes. TX 231. Wide scan (all)
      2. RX 231, 2311. TX 2311. Narrow scan (only this channel and Bozena)
      3. RX chats and venues, TX 23010 cz chat – on demand, TS2, little used yet
      4. RX chats and premises, TX 23110 sk chat – on demand.
      5. RX huts and local, TX local OM0ODB, TS2. Wide scan (all)
      6. echo test OM0ODB
      7. analog – OM0ODB monitoring, without TSQ

      8. – 14. the same but for the future operator in Dubravka, OM0ODD

      15. DMR direct, according to Kosicanov, 438.125, TG9 (I'm writing from memory, but I think we understand each other)
      16. analogue Bozena OM0OUB, narrow scan (this + 2.)

      I usually have it on 16th (or 2nd) with scan. I found out that I don't even need the display, this station is enough 🙂

      73
      Andrew om4dw

      Reply
      Visitor
      Anonymous on March 16, 2018 at 9:20 PM #14971

      Hello Tono.

      I deliberately suggested TG2311 and not 231 – also out of consideration for OK stations. When transmitting on 2311, communication takes place only on OM repeaters, but when on 231, also on OK. Transmitting under TG231 would unnecessarily lead to poorer throughput of the entire TS1, including TG230, where I guess the largest part of OK stations communicate.

      As for storing multiple TGs in the RX list of one RPT, it has its advantages, but also a big disadvantage. The advantage is that we hear significantly sea connections, but the disadvantage is that unless we are looking at the station's display, we do not know on which TG someone was calling. And then we 'chase' different TGs until we find one, or rather we do not find one, because in the meantime the opposing station has given up.

      You state that OK does not have an agreed national TG, but according to my knowledge it does, and it is 2301, see https://mhz.sk/dmr/ , where it is stated, for example, that I quote: “TS1 TG2301: group of Czech smugglers, TS1 TG2302: group of Moravian smugglers, TS1 TG2311: group of Slovak smugglers.”

      In my opinion, the ideal situation would be if OK stations also used TG2301 instead of TG230, which would be the most considerate and would achieve greater network throughput. However, if OK stations wanted to broadcast on OK and OM at the same time, they would use TG230. And likewise, if OM stations wanted to broadcast on OM+OK at the same time, they would use TG231.

      Your codeplugs are an excellent tool and many thanks for them. But we radio amateurs should learn a little bit about how to supplement, change, edit and adapt the data to our own needs. I still use your codeplug as a basis, but I have supplemented, expanded and modified it dozens of times and now it has about twice the original data and is constantly evolving.

      Reply
      Visitor
      Anonymous on March 16, 2018 at 9:37 PM #14972

      Hello Andrew.

      Of course, there are many options, but as I already mentioned in my answer to Tón – when it comes to storing multiple TGs in the RX list of one RPT, it has its advantages and disadvantages. The advantage is that we hear significantly sea connections, but the disadvantage is that unless we are looking at the station's display (or if the station does not have a display), we do not know on which TG someone was calling. And then we 'chase' different TGs until we find one, or rather we do not find one, because in the meantime the opposing station has given up.

      But of course, everyone should use the settings structure they are used to and that suits them best. What I wrote is only meant as a suggestion, or a recommendation that it could be done differently and perhaps better.

      Reply
      Participant
      om1aeg on March 18, 2018 at 5:54 PM #14973

      Geyser

      231 and 2311 are set up on each OM operator as permanent TGs, so either TG can be used for the nationwide network.

      230 is set on every OK operator as a permanent TG
      2301 is a TG intended for guilds and is not set up on all Moravian carriers as a permanent TG, for example https://brandmeister.network/?page=repeater&id=230602
      2302 is a TG intended for Moravia and is not set on all Czech operators as a permanent TG, for example https://brandmeister.network/?page=repeater&id=230203
      So in OK they only have one nationwide TG, which is 230, and I can't choose to call only in OK, since 230 is set on all OM RPT, except KE and Kojsovka. There are many sea users and operators there, DMR has been running there for longer, so any change on the OK side would be very difficult.
      I personally don't mind TG230 on my rpt, I probed among some ODB users whether it would be a solution and a codeplug adjustment was enough, the traffic there is small anyway. However, if an agreement were reached based on the requests of users and sysops that 230 would no longer be a permanent TG in OM, TG231 could remain as the Czechoslovak TG, since it is programmed as permanent on most OK RPTs.

      Reply
      Visitor
      Anonymous on March 18, 2018 at 6:38 PM #14974

      Hello Tono.

      Sure, that's all right. The only discrepancy was that OK stations do not have a common TG adequate to OM stations in the case of TG2311. OK stations are divided into only Czech and only Moravian converters, in the form of TG2301 and 2302. In order not to complicate things too much, it might be worth just making a proposal in terms of changing the numbering of TG230x in the case of Czech and Moravian converters as follows: TG2301 would now be completely OK, i.e. Czech and Moravian together, TG2302 would now be only Czech, and the completely newly created TG2303 would be only Moravian. I think it's not a complete 'branch' and from a long-term perspective - when there are sea of us - it would definitely make sense. The sooner it starts, the better (so that people get used to that small change sooner and sea easily).

      Reply
      Visitor
      Anonymous on March 27, 2018 at 5:43 PM #14975

      So what do you suggest, TG231, or TG2311, do we leave things as they are?

      Reply
      Visitor
      Anonymous on May 24, 2018 at 9:17 PM #14976

      So I will be mostly on TG2311

      Reply
    Showing 9 posts - 1 to 9 (of 9 total)
    Reply to: Call channel on DMR
    Your details: