Seeking Assistance in Creating an Infrared File

hello

I am fairly new to the flipper zero thing, by now I can get my bearings but still need your help. I have a monitor here at home that works on infrared but no controller came with it, I contacted the company and they sent me a screenshot with all the codes, now how can I convert this into a file for my flipper zero and which one should I use?

regards

You can find the picture here.

This is the file format definition: https://github.com/flipperdevices/flipperzero-firmware/blob/dev/documentation/file_formats/InfraredFileFormats.md

This are a lot of examples (nearly 9000 .ir files): GitHub - Lucaslhm/Flipper-IRDB: A collective of different IRs for the Flipper

You just need to look at the files with ‘type: parsed’.

From the picture the address seems to be 04 FB 00 00.

The commands (button) in the table are visual linked to the picture of the remote. So the command for up should be something like ‘57 00 00 00’. Here it needs some testing, if the command is 57 00 00 00 or 00 57 00 00 … Or logical inverted. The last one is too much for the first test.

You should start with the power command (5A).

As protocol I would start with ‘NEC’, than ‘NECext’.

as you can see from the picture I have both NEC and NECext in use, as soon as it says NEC my flipper cannot read it, I tried everything on NECext but my monitor does not respond to the commands

It is not fun to debug the file from a screenshot on a mobile phone. I can’t see if there is a blank or something like this.
You can write a code line here with ` before and after the line, or with three ``` before and after a code block.

I’ve done a search for all remotes with protocol: nec* and the known address.

name protocol address command category
POWER NECext 04 FB 00 00 08 F7 00 00 Converted
POWER NECext 04 FB 00 00 0E F1 00 00 Converted
POWER NECext 04 FB 00 00 08 F7 00 00 NULL

The first two are ‘Universal Remote’ library. The best match I could find is VX37L.ir

Step 1: Download the File VX37L.ir
Step 2: Copy it to your Flipper on the SD Card under ‘infrared’
Step 3: Check if all buttons are available on the flipper
Step 4: Check if Power On/Off are working
Step 5: Edit this file with your known codes at command:. Maybe change also protocol:

1 Like

I just found a bug in my reversing script (again) …

You need to know the NEC protocol is sending the command first straight and than logical inverted. Afterwards the command will be send forward, than logical inverted.

Because I should know this, my converter just take the first two values of the address: line. So the output is:

Filetype: IR signals file
Version: 1
#
name:  POWER 
type:  parsed 
protocol:  NECext 
address:  fb FB 00 00 
command:  a5 00 00 00

The invert of 04 is FB … So you need to enter 04 or FB at each address:, not both.

The File could look like this:

Filetype: IR signals file
Version: 1
#
# Test file 0.1 for 
# https://forum.flipper.net/t/seeking-assistance-in-creating-an-infrared-file/19207/4
#
name: POWER
type: parsed
protocol: NECext
address: 04 00 00 00
command: 5A 00 00 00
#
name: MUTE
type: parsed
protocol: NECext
address: 04 00 00 00
command: 1A 00 00 00
#
name: Play/Pause
type: parsed
protocol: NECext
address: 04 00 00 00
command: 56 00 00 00
#
name: REV
type: parsed
protocol: NECext
address: 04 00 00 00
command: 57 00 00 00
#
name: FFD
type: parsed
protocol: NECext
address: 04 00 00 00
command: 16 00 00 00
#
name: UP
type: parsed
protocol: NECext
address: 04 00 00 00
command: 53 00 00 00
#
name: LEFT
type: parsed
protocol: NECext
address: 04 00 00 00
command: 4A 00 00 00
#
name: MENU
type: parsed
protocol: NECext
address: 04 00 00 00
command: 4B 00 00 00
#
name: RIGHT
type: parsed
protocol: NECext
address: 04 00 00 00
command: 0A 00 00 00
#
name: DOWN
type: parsed
protocol: NECext
address: 04 00 00 00
command: 53 00 00 00
#
name: VOL+
type: parsed
protocol: NECext
address: 04 00 00 00
command: 51 00 00 00
#
name: PREV
type: parsed
protocol: NECext
address: 04 00 00 00
command: 50 00 00 00
#
name: EXIT
type: parsed
protocol: NECext
address: 04 00 00 00
command: 13 00 00 00
#
name: VOL-
type: parsed
protocol: NECext
address: 04 00 00 00
command: 4D 00 00 00
#
name: NEXT
type: parsed
protocol: NECext
address: 04 00 00 00
command: 4C 00 00 00
#
name: FUNC
type: parsed
protocol: NECext
address: 04 00 00 00
command: 0F 00 00 00

I found that when the Flipper finds an error in a file it just stops reading everything after that. The best method for debugging is to remove the entire entry that caused the error. In this case the second entry. Something else I noticed is that some formats simply don’t accept every value. Perhaps NEC does not support that those values in the second entry?

I have tried these files both the 04 in the address and FB, both unfortunately do not want to respond to my monitor