ESP8266 tools auto_analyse_raw_data

[chrisbut2002]

Is there any documentation on how to use this python script. How do you give it the raw data, I have been trying to get the XMP protocol to work and have sucessfully used IRrecvDumpV2.ino to decode XMP codes sent from my arduino using a send program. The next stage seems to be to further anylyse the raw data. I'm not sure if the py script only works on the esp or whether I could run it on my pc , say with anaconda. Either way I don't understand how you interact with auto_analyse_raw_data to give it the raw data. Thanks

[NiKiZe]

You run it with python, and it will give you help and examples?

[chrisbut2002]

Thanks. For some reason the =-h or --help doesn't seem to be working .Its some time since I've used python so I'm a bit rusty.
I'm getting \Anaconda2>python auto_analyse_raw_data.py -h
File "auto_analyse_raw_data.py", line 105
code.append(f" // Data Section #{self.section_count}")
^
SyntaxError: invalid syntax

[crankyoldgit]

what version of Python do you have installed? I believe you need >= v3.0

[chrisbut2002]

I seem to be on 2.7.13 so probably need to upgrade - thanks.

[chrisbut2002]

After a bit of a struggle I have upgraded my python to 3.10.6 and successfully run auto_analyse_raw_data.py with output from IRrecvDumpV2.ino. This file shows the output so its not quite clever enough to recognize XMP but it sort of works.
auto_analyse_raw_data_output.txt

[crankyoldgit]

~/git/IRremoteESP8266$ tools/auto_analyse_raw_data.py -h
usage: auto_analyse_raw_data.py [-h] [-g] [-n NAME] [-r MARGIN] [-f FILE] [--stdin] [rawdata]

Read an IRremoteESP8266 rawData declaration and tries to analyse it.

positional arguments:
  rawdata               A rawData line from IRrecvDumpV2+. e.g. 'uint16_t rawbuf[37] = {7930, 3952, 494, 1482, 520,
                        1482, 494, 1508, 494, 520, 494, 1482, 494, 520, 494, 1482, 494, 1482, 494, 3978, 494, 520,
                        494, 520, 494, 520, 494, 520, 520, 520, 494, 520, 494, 520, 494, 520, 494};' (default: None)

optional arguments:
  -h, --help            show this help message and exit
  -g, --code            Generate a C++ code outline to aid making an IRsend function. (default: False)
  -n NAME, --name NAME  Name of the protocol/device to use in code generation. E.g. Onkyo (default: )
  -r MARGIN, --range MARGIN
                        Max number of micro-seconds difference between values to consider it the same value. (default:
                        200)
  -f FILE, --file FILE  Read in a rawData line from the file. (default: None)
  --stdin               Read in a rawData line from STDIN. (default: False)

You run the script on a device that has Python. e.g. PC, Mac, Linux, etc etc.

[crankyoldgit]

I have been trying to get the XMP protocol to work and have sucessfully used IRrecvDumpV2.ino to decode XMP codes sent from my arduino using a send program.

If the library successfully decodes the protocol, you most likely don't need the auto_analyse_raw_data.py script. It's primary use is for attempting to decode protocols have no decoder for them yet.

I think you need to analyse the "output data" collected by the protocol decoder, not the "raw" data.

[chrisbut2002]

Thank you for your replies. I think you are right that I don't need to use auto_analyse as IRrecvDumpV2 does seem to be decoding the code some of the time. I ultimately want to be able to use the sendXmp function to send codes to my Huawei TalkTalk Youview DN360T box and I don't have the remote control. I found pronto codes for it on the internet and I have managed to send some pronto codes to it that work. It would be more convenient to send codes. This is what IRrecvDump produced
Timestamp : 000007.516
Library : v2.8.4

Protocol : XMP
Code : 0x2B0F44662D000100 (64 Bits)
uint16_t rawData[35] = {248, 984, 246, 2202, 242, 732, 246, 2726, 248, 1270, 244, 1264, 246, 1532, 246, 1528, 244, 13622, 238, 996, 246, 2460, 244, 728, 242, 726, 244, 720, 244, 856, 244, 724, 244, 722, 242}; // XMP 2B0F44662D000100
uint64_t data = 0x2B0F44662D000100;

This seems to be completely correct for a function 1, ie pressing the figure 1. This is the output from Makehex
Device Code: 102.32 Function: 1
0000 006D 0012 0012 0008 0027 0008 0056 0008 001D 0008 006A 0008 0032 0008 0032 0008 003C 0008 003C 0008 020D 0008 0027 0008 0060 0008 001D 0008 001D 0008 001D 0008 0022 0008 001D 0008 001D 0008 0BF2 0008 0027 0008 0056 0008 001D 0008 006A 0008 0032 0008 0032 0008 003C 0008 003C 0008 020D 0008 0027 0008 0037 0008 0046 0008 001D 0008 001D 0008 0022 0008 001D 0008 001D 0008 0BF2
This is the data I used to send to IRrecvDumpV2.

So can you help with using the sendXmp Is it possible to send the 0x2B0F44662D000100 code?

[crankyoldgit]

Yes. Simply:

irsend.sendXMP(0x2B0F44662D000100);

See: https://crankyoldgit.github.io/IRremoteESP8266/doxygen/html/classIRsend.html#a79e650dedb19f37601600c8cb16e4c8e
and
https://github.com/crankyoldgit/IRremoteESP8266/blob/master/examples/IRsendDemo/IRsendDemo.ino

[chrisbut2002]

Many thanks - yes it works. Brilliant. I can now send channel changes to the tv by sending a 1 or a 2. If I get more ambitious I will try using a webserver to control a subset of the various codes. Thanks so much for your work on this. Your software is the only one which really copes with XMP.

[crankyoldgit]

As you've confirmed the protocol works for your real devices, can you please supply us with the make/model etc for the remote and the device it controls so we can add it to the list of supported devices.

[chrisbut2002]

Yes. I don't have the details for the remote because I never had one. But the device I am sending the IR to is a Youview set top box made by Huawei for the phone company TalkTalk in the UK. The set top box is a DN360T. I attach a photo of the remote from the manual.

I first got hold of the pronto hex codes for it from someone on the talktalk discussion forum. And I found a pcf file of the same device and managed to load that into ProntoEditNG which also relates the keys to the pronto codes. Eventually using a trial and error method I deduced that the remote was device 102, subdevice 32 because when I ran makehex (MakeHex version 4.12 Copyright 2005 John S. Fine) it gave the right codes to match the ones I had from the web. I successfully sent raw or pronto codes to the box which proved it was working correctly. Then I was looking for a more compact way of sending key codes which is when I found your library with support for XMP. I have now translated about twenty of the pronto codes to this format 0x2B0F44662D000100, just changing to the last 8 bytes to match the code. I think the last 8 are code and matching checksum. I found the XMP.irp file which makehex uses invaluable for this. I have annotated this below:
Hex
0=210,-760 1D
1=210,-896 22
2=210,-1032 27
3=210,-1168 2C
4=210,-1304 32
5=210,-1440 37
6=210,-1576 3C
7=210,-1712 41
8=210,-1848 46
9=210,-1984 4B
10=210,-2120 51
11=210,-2256 56
12=210,-2392 5B
13=210,-2528 60
14=210,-2664 65
15=210,-2800 6A

This is the full list of all possible codes for the remote although some of them may not do anything and might be harmful.
XMPdevice102_32full.txt

[crankyoldgit]

Yep. While XMP is technically a space encoded protocol. It has upto 4 different values of space encoded bits. i.e. 2 bits per space. Auto really handles single bits (two space values).
Probably about 85-90% of the protocols we encounter are single bit space encoded protocols, so the program works in most cases.