Tetra PEI AT Commands

[gimmythesaint]

Is there any way to obtain the Sepura PEI developer manual?
I'm having a really hard time figuring out al AT commands.....

If you are a Sepura customer, you will have to contact their representative and they should provide you with a copy
of their "Limited/Protected" developer document for their PEI interface.

Most of the commands are standard commands as found in ETS documentation (available over the web), some standard commands are not supported in Sepura.

The bottom line, get into contact with Sepura, unless you have a specific command or question I might be able to assist you.

[saugumas]

Some AT commands examples for sepura you will find there http://www.4shared.com/rar/dODJqvTic...mentation.html look at the folder "Interface Specifications"

[gimmythesaint]

Dear saugumas ,
I am amazed with the loads of Sepura documentation that you've provided! it has everything and more.

As for ********, do you have any documentation about their PEI interface?

I am having a problem in interpreting some short lip messages that I am receiving via the PEI interface:

some radios send 52 bits rather than 84 bits, with the following payload:
0A4C0040B08C0
if you interpret it with the available documentation, you will find that
0A is the protocol identifier for LIP, 40 hexa == 01000000 which renders to
PDU type 01 which is Long Lip Message ?
PDU extension 0011 which is Long Location Report
Request/Respose 0 = a response??
Why will a radio send such a message?

Also, other radios sends a correct 84 bits lip message with location as 000000s although they have acquired a correct location information:
0A30000000000007FFE00
I suspect this has to do with permissions or something?

Any clues about these messages, the 52-bits and the zeros 84-bit one??

Regards

[saugumas]

I suggest using ETSI documentation http://www.etsi.org/deliver/etsi_ts/...01v010301p.pdf (page No 41) for debugging. You must convert complete LIP PDU payload (without 0A in front which is LIP PID) from HEX to BIN and group them iaw ETSI to decode. Then you will see a cause

Might be useful for LIP modeling as well http://pdu.argos.ws/LIP_PDU_Generato..._Generator.htm

[saugumas]

As for zeroes in LIP message payload this means that no GPS is available/acquiring (some ******** terminals do this while others not).
As well you might need to overlook LIP triggers as this might be a clue for 52-bit messages. In example to send position of the terminal you ca use only two basic of them: Periodic reporting or/and Distance reporting all others can be disabled. Of course such settings depends on your operational profile.

[tk79_de]

Hi,

you can find a small Program to read SDS messages from PEI here: http://www.funkmeldesystem.de/foren/...&highlight=SDS
It's a German forum, but the sourcecode of the first Post is quite easy to understand.