Some info from a source

[Sergio558]

Last years I spent a lot of time to create my own monitoring program using C#, easyMODBUS lib and source code from old Windows program. Recently I discovered the project and find it's very useful. Same time I got differences in processing Telemetry packets from my SE3000 inverter via RS232 port. Telemetry packets spilling off by the inverter after each PROT_CMD_POLESTAR_CONFTOOL_START request send with 300 sec interval. Shorting it have no effect. Each request accompanied by a response packet with PROT_RESP_ACK/NACK/ERR response code.
I think it will be beneficial to all enthusiasts bring some additional info from my experience.

[Sergio558]

I'm using SE terminology and will post my data in accordance with it.

There are two types of packets: PacketA and PacketB type. Barker field for fist one is 12345678, second 12345679 in hex format.
To easy discuss fields and values of the packets, I'll post them in string format as byte array what send/receive from the inverter or any device what is capable processing the packets.

Tx samples:
11/22/24 18:08:00 12345679 0100 FEFF 0F09 FDFFFFFF xxxxxxx 0E03 01 1BF7                  PROT_CMD_POLESTAR_CONFTOOL_START
11/22/24 18:13:00 12345679 0100 FEFF 1009 FDFFFFFF xxxxxxx 0E03 01 CE1C                  PROT_CMD_POLESTAR_CONFTOOL_START
11/22/24 18:18:00 12345679 0100 FEFF 1109 FDFFFFFF xxxxxxx 0E03 01 33DF                  PROT_CMD_POLESTAR_CONFTOOL_START
11/22/24 18:23:00 12345679 0100 FEFF 1209 FDFFFFFF xxxxxxx 0E03 01 37DB                  PROT_CMD_POLESTAR_CONFTOOL_START

Rx samples
11/22/24 16:25:16 Telemetry 12345679 1500 EAFF E70B xxxxxxx FDFFFFFF 0005 8000 xxxxxx 0D004D944067D286BF30B20127040B 1948 .
11/22/24 16:25:24 Telemetry 12345679 1500 EAFF E80B xxxxxxx FDFFFFFF 0005 8000 xxxxxx 0D00559440672887D4388202F5040B 57BD .
11/22/24 16:25:35 Telemetry 12345679 1500 EAFF E90B xxxxxxx FDFFFFFF 0005 8000 xxxxxx 0D0060944067F086BD38D201F0060B 0FE5 .
11/22/24 16:25:52 Telemetry 12345679 1500 EAFF EA0B xxxxxxx FDFFFFFF 0005 8000 xxxxxx 0D0072944067F386D538920103070B 1B3B .
11/22/24 16:26:04 Telemetry 12345679 1500 EAFF EB0B xxxxxxx FDFFFFFF 0005 8000 xxxxxx 0D007D9440672A87D3309201CA060C BFF5 .
11/22/24 16:26:09 Telemetry 12345679 1700 E8FF EC0B xxxxxxx FDFFFFFF 0005 8200 xxxxxx 0F00829440673488CD3C3202C4040C0809 6C0C .
11/22/24 16:26:20 Telemetry 12345679 1500 EAFF ED0B xxxxxxx FDFFFFFF 0005 8000 xxxxxx 0D008D944067A587D350820297070B 0131 .
11/22/24 16:26:53 Telemetry 12345679 1500 EAFF EE0B xxxxxxx FDFFFFFF 0005 8000 xxxxxx 0D00AE9440673D87CA54C20259050B B65A .
11/22/24 16:27:20 Telemetry 12345679 C200 3DFF EF0B xxxxxxx FDFFFFFF 0005 1000 xxxxxx BA00CC94406799A500002C0100008AE9C1418C64B9450000E040001452430000043F51ED4742FFFF7FFFFFFF7FFF00C8A143FFFF7FFF94ED244C6E12033CFFFF7FFFFEFF7FBF040000000080BB450000C8420000603BFFFF7FFFFFFF7FFF0000A8420000D842000086425655554056555540565555404FB69302000000003D41F53B00000000FD000000000000000000EEA9E801000000000000E040610CAB0000000000000000000000000000000000000000000000FFFF7FFF0100 4F3E .
11/22/24 16:27:20 Telemetry 12345679 4200 BDFF F00B xxxxxxx FDFFFFFF 0005 2200 xxxxxx 3A00CC944067020000000000000000800000000000000080000000000000008000000000000000802C010000000000000000000000000000FFFF7FFF C516 .

[Sergio558]

Here is how Tx packet build:

    public byte[] BuildPacket()
    {
        MemoryStream memoryStream = new MemoryStream(0);
        BinaryWriter binaryWriter = new BinaryWriter(memoryStream);
        binaryWriter.Write(BitConverter.GetBytes(RPHeader.BARKER));
        ushort length = (ushort)Length;
        binaryWriter.Write(length);
        binaryWriter.Write((ushort)(~length));
        binaryWriter.Write(ID);
        binaryWriter.Write(Source);
        binaryWriter.Write(Destination);
        binaryWriter.Write(OpCode);
        if (Data != null)
            binaryWriter.Write(Data, 0, (int)length);
        binaryWriter.Write(GetCheckSum());
        return memoryStream.ToArray();
    }

[Sergio558]

Return packet (OpCode replaced by ReturnCode) with RC = 0005 is Telemetry packet. Next two bytes is Telemetry Type as ushort:

    public enum ERecordType
    {
        PANEL = 0,
        STRING = 1,
        CLUSTER = 2,
        INVERTER_1PHASE = 16,       //  0x10
        INVERTER_3PHASE = 17,       //  0x11

        COMBI_STRING = 18,          //  0x12
        COMBI = 19,                 //  0x13
        COMBI_STRING_UNIFIED = 20,  //  0x14
        COMBI_UNIFIED = 21,         //  0x15

        //VEGA = 22,                //  0x16 ???

        Type23 = 23,        //  0x17  - got it right after reboot
        Type24 = 24,        // 0x18  - got it right after reboot

        Type34 = 34,        // 0x22 Energy Meter

        Type48 = 48,        // 0x30 Battery Data

        Type64 = 64,        //   got it right after reboot
        Type65 = 65,        //   got it right after reboot
        Type66 = 66,        //   got it right after reboot
        Type67 = 67,        //   got it right after reboot
        Type68 = 68,        //   got it right after reboot
        Type71 = 71,        // got it right after reboot
        Type72 = 72,        //   got it right after reboot

        OPTIMIZER = 128,      // 0x80
        OPTIMIZER_S = 130,    // 0x82: S440/S500

        // see enum ProtocolOffsets
        VENUS = 512,         // 0x200
        POLESTAR = 768,      // 0x300
        SUNTRACER = 1024,    // 0x400
        SERVER = 1280,       // 0x500
        CONFTOOL = 1536,     // 0x600
        JUPITER = 2048,      // 0x800
        VEGA = 2560,         // 0xa00
        VENUSPWR = 3328,     // 0xd00
        COUNT
    }

[Sergio558]

My quick glance of semonitor parsing telemetry packets [OP/OP_S/Inv1PH/Inv3PH/etc] seems to me has some different things from my knowledge.
Like OP_temp - I'm using 1.5 multiplier; measured a side of one OP with laser thermometer - got 32C, telemetry parsing giving 31.5C.
[Not the case.
After I found in Diag menu of LCD POLESTAR model (SE3000) info about each OP, where is Temp shown, I begin processing the "bTemp" byte from Telemetry_0082 with one shift to left (multiply by 2); now it is correct conversion]