Greetings again Christian.
Replies inline below:
The most interesting finding comes from the service menu. I am sure now
that it's hunting on the correct frequency. Also I can see that during
hunting, it stays a little bit longer on the channel that is actually
transmitting. RSSI on the correct channel is about -70dBm. Thats very
good progress.
Just to be sure, if I were you I'd use a tool like dsd-fme or SDRTrunk with an
RTL dongle or similar just to check that the control channel parameters are as
expected.
I have never heard transmissions on the radio's TX frequency.
That might point to some mismatch in CPS parameters. Hytera generally sticks
pretty close to the Tier 3 standard except for some stuff like packet data
calls, message with position or query neighbours. I'll double check tonight my
CPS settings for any tricky setting in the System or Developer sections that I
need to document.
So the system code needs to go
Network/Network 00.000000001.001
Yes, that binary number adds up to 9. Generally the network number needs to be
the same between radio and control channel, while the site id (last 3 binary
digits) can be different since the radio can seamlessly roam between sites on
the same network. There's another setting in the CPS which can enable roaming
between networks, but let's not get into that yet.
If you are interested in the details regarding TSCC acquisition, system codes
structure etc., it is very well described in the standard:
ts_10236104v011001p.pdf
at pages 62 through 67.
Hunt/Fixed TSCC, last column 9
Trunking Controller, Setting/General Setting, System Identity Code: 9
MMDVMhost, Section DMR, SystemCode=9
Somewhere else?
No, this is all that's needed for the System Identity code.
One point I am wondering about:
What needs to go into Setting/General Settinge/Base frequency in the
trunking controller. The Transmit Frequency of the radio or of the base
station?
The base frequency is channel 1 (the base frequency for the channel plan),
then each channel number gets incremented by the channel spacing. So for you
that would be channel 1 for the radio TX and base station RX. In my screenshot
in the first email, the control channel is channel 37 which is relative to this
base frequency.
If all else fails, you can try to set Flexible Channel Plan in the CPS and
define all channel frequencies there, then disable "Fixed channel plan" in
dmrtc. This was also my initial configuration of the radio until I got the hang
of the fixed channel plan. I think one additional problem might be that my
Hytera CPS is a different version to yours and might have some settings in
different places.
Setting/General Settinge/Duplex split in the controller is TX - RX or
RX-TX? Of Radio or of Base Station?
Duplex split in dmrtc is relative to the RX frequency (which is the inverse of
the radio), same as "tx_shift" in qradiolink.cfg. If you have a negative split
in the radio (TX lower than RX), the split will be positive in qradiolink and
dmrtc since the base station listens on the reverse of the radio TX.
Also, in the Logical Physical Channel Map: is it RX/TX frequency of
radio or of base station?
Now that you mention that, I can see that it is confusing. The channel plan
lists the RX and TX freq of the radio instead of the base station. That is
because channel grants are given from the perspective of the user radio. I
need to clarify that in the docs. However, those frequencies are only relevant
after registration for channel grants and such.
Next steps tomorrow. Multumesc again!
Sure, you're welcome! I will be free tonight so we can set a sched on
Brandmeister if you want. I look forward to adding another radio to the
compatibility matrix.
BR,
Adrian
