Date   

Re: hytera USB packet structure

Eric - KF7EEL
 

From what I have seen with several radios, the IP header is usually in the next block(s) after the header, followed by the data. I have only worked with SMS and GPS  air protocol, ETSI 102 361-1.

All the data that I have decoded has been encoded at 1/2 rate, so BPTC works for decoding. What did you use to capture the data in your txt file?


Re: Analog_Bridge log and boot log errors

G4WXN@...
 
Edited

Dashboard found :-)

I am assuming AB is running, I am RXing and TXing.


--
Derek

G4WXN


Re: Analog_Bridge log and boot log errors

Steve N4IRS
 

Is Analog_Bridge running? Try starting it?
The dashboard is at port 80. 8080 is the RX monitor.

On 3/16/2021 9:58 AM, G4WXN@... wrote:

I have just used the system builder to rebuild one of my Rpis that was having issues.
I first used the system builder back in March or April last year, this install looks very different.

Anyway, cutting to the chase.

I see this error in the boot.log file
Can not find /tmp/ABInfo file (have you run Analog_Bridge?), aborting 

I also have another error, in that I tried to connect to the dashboard on ipaddressofpi:8080 and I get a message

"Upgrade required"

If anyone can throw light upon either problem it would be appreciated.



--
Derek

G4WXN



Analog_Bridge log and boot log errors

G4WXN@...
 

I have just used the system builder to rebuild one of my Rpis that was having issues.
I first used the system builder back in March or April last year, this install looks very different.

Anyway, cutting to the chase.

I see this error in the boot.log file
Can not find /tmp/ABInfo file (have you run Analog_Bridge?), aborting 

I also have another error, in that I tried to connect to the dashboard on ipaddressofpi:8080 and I get a message

"Upgrade required"

If anyone can throw light upon either problem it would be appreciated.



--
Derek

G4WXN


Re: more: not connecting to BM any more

Steve N4IRS
 

Well,
I disagree that anything has to be done on the BM side. It all depends on your needs. And again, duplex offers some advantages but has some downsides.
Yes, the UI for BM changes base on the configuration you present during login. MB is not disconnected from the receiving TG, BM uses a inactivity timer for a duplex connection to remove the TG.


Steve N4IRS

On 3/16/2021 9:10 AM, Ken KE2N via groups.io wrote:
OK - hold the boat.
I finally figured out what is going on.  I was on the right track when I concluded that something had to be done on the BM side.

When you change from duplex=0 to duplex=1,  BM automatically changes your hot spot configuration to have two time slots.
You will not see this unless you are looking for it - e.g., by going to BM self-care and refreshing the browser (may have to clear cache in some browsers).
Any static TG you had configured will "disappear" - it belonged to your old duplex=0 hot spot.
You need to set the static TG for the appropriate TS for your shiny new duplex hot spot. Otherwise MMDVM_Bridge will be disconnected from receiving the TG after a few minutes. 

>> this was what was causing the issue I observed.

Thanks for humoring me - 

Ken


Re: P25 to DMR on VPS Server

Alec-N1AJW
 

if you install DVSwitch Repo it should give you what you need.  Usually when I build bridges it starts out with the version the vps company provides. 

Alec
N1AJW


Re: more: not connecting to BM any more

Ken KE2N
 

OK - hold the boat.
I finally figured out what is going on.  I was on the right track when I concluded that something had to be done on the BM side.

When you change from duplex=0 to duplex=1,  BM automatically changes your hot spot configuration to have two time slots.
You will not see this unless you are looking for it - e.g., by going to BM self-care and refreshing the browser (may have to clear cache in some browsers).
Any static TG you had configured will "disappear" - it belonged to your old duplex=0 hot spot.
You need to set the static TG for the appropriate TS for your shiny new duplex hot spot. Otherwise MMDVM_Bridge will be disconnected from receiving the TG after a few minutes. 

>> this was what was causing the issue I observed.

Thanks for humoring me - 

Ken


DVSwitch Linux Shell dvs #systemcrash #mmdvm_bridge #dvs

IZ1XBB - Pier Paolo
 

Hello everyone,
Me and two other radio amateur operators have been able to find, on our DVswitch servers, when launch  the dvs shell, problems arise due to the automatic entry of errors into the MMDVM_Bridge.ini file by the shell itself.
These errors are: 
Disconnect from dmr master server
Enabling all Modes and Networks
 
To solve the problem we had to:
  • manually reconfigure the MMDVM_Bridge.ini
  • run commands: apt update, apt upgrade, reboot
 
This seemed to us to be anomalous, and I therefore thought it appropriate to point this out.
 
Thank you for your attention!
 
73 IZ1XBB
 


Re: more: not connecting to BM any more

Steve N4IRS
 

Yes, you need to understand how BM wants a connection to be configured. A duplex connection from MMDVM_Bridge has very little upside and more downside.
We have tried to set the defaults in MMDVM_Bridge for DMO. (duplex =0)  A mis-configured simplex hotspot could have it's frequencies set to split. When BM started implementing controls to not allow a mis-configured client to connect, we had to change the default frequencies to simplex. You do not have to tell BM you want a duplex connection, you just have to configure your client to duplex =1 and split frequencies.

As Corey said, these are protocol standards and BM standards. MMDVMHost and MMDVM_Bridge allowed a improper configuration to be sent to the Master. BM has implemented controls to not allow this. DVSwitch is changing MMDVM_Bridge to fix mis-configured connections before they are sent to a Master (BM or not) Simple Terminal Feature Update makes all of this moot.    

On 3/16/2021 8:29 AM, Ken KE2N via groups.io wrote:
So maybe the gap in my knowledge is on the BM end.  I am concluding that the ad hoc connection made by MMDVM_Bridge is always (or by default)  a DMO connection.

If you wanted the (RMO) duplex connection, is there something you have to tell BM first? Are you basically asking for a repeater connection?

Ken


Re: P25 to DMR on VPS Server

 

On 16/3/21 11:00 am, Adrianm0glj@gmail.com wrote:

Hi Guy's

Am I correct in thinking that DV Switch can be used to bridge DMR and P25?
Yes (Iḿ doing that, among other things myself).


If so can it be installed on a VPS server rather than using a
Raspberry Pi?
Yes (doing that too). :)


Is there a simple way of installing the minimal requirements to do the
transcoding between DMR and P25?
I have a full installation, but itś simple to install using apt on Debian.

--
73 de Tony VK3JED/VK3IRL
http://vkradio.com


Re: more: not connecting to BM any more

Corey Dean N3FE
 

TO add to this a little.

It doesn't matter if you are running DVSwitch or even a hotspot, DMO means simplex and the tx/rx frequencies must match.  It wouldn't be simplex if it didn't.  This was being abused and why bm made the changed.  If you are running in Full Duplex then the frequencies cat match or in theory you would be looping yourself and the network.

As for not showing up on the dash board.  Only your 7 digit subscriber number will work as a user.  A subscriber cant add 01-99 to their ID or it becomes invalid.  Your device, such as a hot spot can be your 7 digit subscriber id and you may add 01-99 to it.  If it isn't showing on the dash then you are changing it in the wrong place.

The above is just the basics and not tied to just DVswitch or any of the different software applications.  You may want to do some google seach on MMDVM protocol or homebrew protocol and just read up on it.  It may answer a lot of your questions.

Corey  N3FE

 


On 2021-03-15 19:49, Steve N4IRS wrote:

One last time.
I told you to set duplex to 0 because that is the recommended method. When you asked about setting split frequencies I told you that you COULD use duplex. We strongly suggest people set the config for DMO. That is simplex so the frequencies need to match or BM will not accept the connection. As I said, if you set to duplex you have to set the frequencies to split or again, BM will not allow you to connect. As I said, if you choose to use duplex, remember we recommend people use DMO, BM treats the connection as a repeater. Repeaters have different rules from a DMO connection. A DMO connection
creates a static TG type. This TG stays until you disconnect it. For a repeater connection, the TG is timed. After a period of inactivity, the TG is disconnected. If you want to over ride this, go into selfcare and set the TG static.

Yes, the ID number you use to connect to BM can be 7 or 9 digit, if 9 digit, you can have 100 hotspot connections, each can be configured differently. The ID used to login to BM is NOT the ID that is displayed on the dashboard becaue it is not the station transmitting, that is defined in the AB.ini since an analog signal has no DMR ID. If you have a hotspot logged into to BM with an ID of 123456789 and your DMR radio is programmed with your DMR ID of 1234567, then 1234567 will be displayed on the lastheard. Corey can chime in and correct me here if I have missed something.

 I have not explained all the differences between DMO and repeater connection. In the next few weeks, we will provide a better method of connecting the BM. That is called Simple Terminal Feature Update. This protocol is what BM want us to use to connect to BM. It is a simpler connection with some features not available in DMO or repeater. It is in beta test now.

Some times the nuances of connectivity are not readily apparent. We have been connecting AllStar to DMR networks before there was a BrandMeister Network. I suggest you ask how something works, don't tell us how things work because sometimes you can't see the big picture without being around the systems for a while.

Steve N4IRS
     

On 3/15/21 7:21 PM, Ken KE2N via groups.io wrote:
OK - a while back you told me I needed to set duplex = 0 but now you are saying I can set it to either 1 or 0.  If it is set to zero, then the frequencies need to be the same.  But this is not my experience.  If I set it to 1, with different frequencies, after 5 minutes or so I can no longer bring up the connection from my DMR HT/repeater, unless I first key up the analog side. There is no error message in the log when it dies. It's like BM just stops talking to MMDVM_Bridge unless it has recently heard something going the other way. This problem does not happen with duplex=0.

As you point out, all the talk about frequencies is, of course, irrelevant to MMDVM_Bridge because its not an actual modem connected to a radio. 

The answer to my question about the ID number is that it can be either the 7 digit number or a 9 digit number.  The extra digits let me see (in self-care) which hot spot is active. But that 9 digit number does not show up in Last Heard - only 7 digits are seen. And it does not show up in the DVSwitch dashboard. Is there some other place it would show up?

DMO is a new acronym for me. Direct Mode Operation - it seems was originally intended to distinguish from Repeater Mode Operation. For DMO the radio would operate simplex with only 1 time slot - or maybe no time slots at all.  But I guess DMO has taken on additional meaning having to do with hot spots and network protocol.

Sorry for being a bit thick about this.  I am trying to increase my level of understanding in fits and starts.


Ken


Re: P25 to DMR on VPS Server

Steve N4IRS
 

Yes,
it can be installed on a VPS.
You can do the base install and then add the changes to build the bridge. A DMR to P25 bridge requires a transcoder. You can build a transcoder with 2 copies of Analog_Bridge. You bridge will look something like this:
DMR Network <-> MMDVM_Bridge_DMR_ports <-> Analog_Bridge_1 <-> Analog_Bridge_2 <-> MMDVM_Bridge_P25_ports <-> P25Gateway <-> P25Reflector

DMR Network and P25Reflector are external
MMDVM_Bridge is a single instance
Analog_Bridge is 2 instances
P25Gateway is a single instance

See <https://dvswitch.groups.io/g/main/wiki/9379>

Steve N4IRS

On 3/15/21 8:00 PM, Adrianm0glj@... wrote:

Hi Guy's

Am I correct in thinking that DV Switch can be used to bridge DMR and P25?

If so can it be installed on a VPS server rather than using a Raspberry Pi?

Is there a simple way of installing the minimal requirements to do the transcoding between DMR and P25?

Adrian

M0GLJ



P25 to DMR on VPS Server

Adrianm0glj@...
 

Hi Guy's

Am I correct in thinking that DV Switch can be used to bridge DMR and P25?

If so can it be installed on a VPS server rather than using a Raspberry Pi?

Is there a simple way of installing the minimal requirements to do the transcoding between DMR and P25?

Adrian

M0GLJ


Re: more: not connecting to BM any more

Steve N4IRS
 

One last time.
I told you to set duplex to 0 because that is the recommended method. When you asked about setting split frequencies I told you that you COULD use duplex. We strongly suggest people set the config for DMO. That is simplex so the frequencies need to match or BM will not accept the connection. As I said, if you set to duplex you have to set the frequencies to split or again, BM will not allow you to connect. As I said, if you choose to use duplex, remember we recommend people use DMO, BM treats the connection as a repeater. Repeaters have different rules from a DMO connection. A DMO connection
creates a static TG type. This TG stays until you disconnect it. For a repeater connection, the TG is timed. After a period of inactivity, the TG is disconnected. If you want to over ride this, go into selfcare and set the TG static.

Yes, the ID number you use to connect to BM can be 7 or 9 digit, if 9 digit, you can have 100 hotspot connections, each can be configured differently. The ID used to login to BM is NOT the ID that is displayed on the dashboard becaue it is not the station transmitting, that is defined in the AB.ini since an analog signal has no DMR ID. If you have a hotspot logged into to BM with an ID of 123456789 and your DMR radio is programmed with your DMR ID of 1234567, then 1234567 will be displayed on the lastheard. Corey can chime in and correct me here if I have missed something.

 I have not explained all the differences between DMO and repeater connection. In the next few weeks, we will provide a better method of connecting the BM. That is called Simple Terminal Feature Update. This protocol is what BM want us to use to connect to BM. It is a simpler connection with some features not available in DMO or repeater. It is in beta test now.

Some times the nuances of connectivity are not readily apparent. We have been connecting AllStar to DMR networks before there was a BrandMeister Network. I suggest you ask how something works, don't tell us how things work because sometimes you can't see the big picture without being around the systems for a while.

Steve N4IRS
     

On 3/15/21 7:21 PM, Ken KE2N via groups.io wrote:
OK - a while back you told me I needed to set duplex = 0 but now you are saying I can set it to either 1 or 0.  If it is set to zero, then the frequencies need to be the same.  But this is not my experience.  If I set it to 1, with different frequencies, after 5 minutes or so I can no longer bring up the connection from my DMR HT/repeater, unless I first key up the analog side. There is no error message in the log when it dies. It's like BM just stops talking to MMDVM_Bridge unless it has recently heard something going the other way. This problem does not happen with duplex=0.

As you point out, all the talk about frequencies is, of course, irrelevant to MMDVM_Bridge because its not an actual modem connected to a radio. 

The answer to my question about the ID number is that it can be either the 7 digit number or a 9 digit number.  The extra digits let me see (in self-care) which hot spot is active. But that 9 digit number does not show up in Last Heard - only 7 digits are seen. And it does not show up in the DVSwitch dashboard. Is there some other place it would show up?

DMO is a new acronym for me. Direct Mode Operation - it seems was originally intended to distinguish from Repeater Mode Operation. For DMO the radio would operate simplex with only 1 time slot - or maybe no time slots at all.  But I guess DMO has taken on additional meaning having to do with hot spots and network protocol.

Sorry for being a bit thick about this.  I am trying to increase my level of understanding in fits and starts.


Ken


Re: more: not connecting to BM any more

Ken KE2N
 

OK - a while back you told me I needed to set duplex = 0 but now you are saying I can set it to either 1 or 0.  If it is set to zero, then the frequencies need to be the same.  But this is not my experience.  If I set it to 1, with different frequencies, after 5 minutes or so I can no longer bring up the connection from my DMR HT/repeater, unless I first key up the analog side. There is no error message in the log when it dies. It's like BM just stops talking to MMDVM_Bridge unless it has recently heard something going the other way. This problem does not happen with duplex=0.

As you point out, all the talk about frequencies is, of course, irrelevant to MMDVM_Bridge because its not an actual modem connected to a radio. 

The answer to my question about the ID number is that it can be either the 7 digit number or a 9 digit number.  The extra digits let me see (in self-care) which hot spot is active. But that 9 digit number does not show up in Last Heard - only 7 digits are seen. And it does not show up in the DVSwitch dashboard. Is there some other place it would show up?

DMO is a new acronym for me. Direct Mode Operation - it seems was originally intended to distinguish from Repeater Mode Operation. For DMO the radio would operate simplex with only 1 time slot - or maybe no time slots at all.  But I guess DMO has taken on additional meaning having to do with hot spots and network protocol.

Sorry for being a bit thick about this.  I am trying to increase my level of understanding in fits and starts.


Ken


Re: more: not connecting to BM any more

Steve N4IRS
 

Because you are using the MMDVM protocol to connect to BrandMeister and it requires the TX and RX frequency to match for a DMO connection. It has NOTHING to do with your Analog_Repeater. If you like you can set the frequencies to match your Analog_repeater and set duplex to 1. (non DMO)

On 3/15/21 4:17 PM, Ken KE2N via groups.io wrote:
Ok ... but why do I have to make the TX and RX frequencies "match"  (set equal to each other) when, in fact, the RF end of my system uses different frequencies for the transmitter and receiver?



Ken


Re: more: not connecting to BM any more

Ken KE2N
 

Ok ... but why do I have to make the TX and RX frequencies "match"  (set equal to each other) when, in fact, the RF end of my system uses different frequencies for the transmitter and receiver?



Ken


Re: more: not connecting to BM any more

Steve N4IRS
 

The update does not force a change to the .ini you can say no.
There is no fix needed. You can look to BM as a repeater or a simplex hotspot. There are pluses and minuses with each type. You just need to set the options. Most users are DMO.
The ID in the [General] section is how you identify to the Master. I suggest you add a SSID for more finite control from the BM admin page.
The repeater ID will go away at some point. It's a leftover.
DMR Gateway is designed to allow the MMDVM hotspot user to use modified TG numbers to switch networks on the fly. MMDVM_Bridge provides switching networks without a gateway. 

On 3/15/2021 12:09 PM, Ken KE2N via groups.io wrote:
OK - so I probably made a typo in the frequency. Complicated by the unwanted ini changes from the update.

If I understand then, DVSwitch looks like a simplex hot spot from the BM side.  
So you have to tell BM you are a simplex node, even if you are a repeater  (at least until some fix is implemented).

Can you clarify if the ID in the [General] stanza should be CCS7 or the 9-digit CCS7+2  or does it matter?

The DVSwitch dashboard shows both numbers. 7-digits for GW ID and 9-digits for RPT ID.  (That is coming from AB I guess).

Am I to understand that MMDVM_Bridge, in addition to its protocol translation function, is also a DMR gateway? (or perhaps DMR does not need a gateway)?  

Thanks
Ken


PS I fixed the DSTAR error message by killing ircgatewayd and setting DSTAR enable=0 in MMDVM
I suspect the error was due to a conflict with the actual DSTAR repeater that I run at the same public IP.


Re: more: not connecting to BM any more

Ken KE2N
 

OK - so I probably made a typo in the frequency. Complicated by the unwanted ini changes from the update.

If I understand then, DVSwitch looks like a simplex hot spot from the BM side.  
So you have to tell BM you are a simplex node, even if you are a repeater  (at least until some fix is implemented).

Can you clarify if the ID in the [General] stanza should be CCS7 or the 9-digit CCS7+2  or does it matter?

The DVSwitch dashboard shows both numbers. 7-digits for GW ID and 9-digits for RPT ID.  (That is coming from AB I guess).

Am I to understand that MMDVM_Bridge, in addition to its protocol translation function, is also a DMR gateway? (or perhaps DMR does not need a gateway)?  

Thanks
Ken


PS I fixed the DSTAR error message by killing ircgatewayd and setting DSTAR enable=0 in MMDVM
I suspect the error was due to a conflict with the actual DSTAR repeater that I run at the same public IP.


hytera USB packet structure

Kev
 

Hello everybody,
I've spent the last couple of months reading through the etsi
documents trying to figure out the packet structure of the 'forward to
pc' option on a hytera radio.
Having done some detective work and comparing packets I can decode
radio ID, LLID, and extract SMS data by bit bashing. I would prefer to
actually understand the whole packet structure so I can decode it
properly rather than blindly extracting the useful data.

The packet does at first appear to be a standard etsi packet,
containing all the blocks.
The issue I'm having is the documents and all open source software I
can find deal with the air side blocks, not a network packet.

Take for example the first 8 bits in the packet : "00001001", which
could be any of the following :
1) 1001 = Idle Data
2) Privacy Flag=0, Reserved Flag=0 and FLCO=001001 making up the first
line in a Full LC header.
3) 001001=8 bit ISO/IEC 8859-7
4) 1001 = SAP 9 = Short Data Services over PDP

Without figuring out some basics, like blocktype I can't work out
which interleaving to use (bptc, hamming etc)

Then there is the LLID. All ETSI documents say it should be
24bits+24bits, but I see the CAI in each address making it 28 or 32
bits for each.

I've attached a text file with some example recieved data split into
colums to make comparision easier for myself.

Im not asking for a full packet decode (although I wouldn't say no!),
just a push in the right direction on how to figure out the packet
type (It must be the first thing transmitted right?)
I realise this isn't a DVSwitch question, but I cant think of a more
knowledgeable group of people on the DMR protocol. If you think there
would be a better place to ask this, please let me know!

Thank you for taking the time to read this, I really hope you can help.

Regards
Kev

921 - 940 of 9775