hi,
i just bought global cache gc-irl i am trying now to learn a code which i learn it in the past using pronto 3500
the code for plus data show on function
pronto o/p

on 900A 006D 0000 0001 8615 14EB

after conversion

0000 006D 0022 0002 0157 00AC 0015 0040 0015 0040 0015 0040 0015 0015 0015 0015 0015 0040 0015 0015 0015 0040 0015 0015 0015 0015 0015 0015 0015 0040 0015 0040 0015 0015 0015 0040 0015 0015 0015 0015 0015 0040 0015 0040 0015 0040 0015 0015 0015 0015 0015 0015 0015 0015 0015 0040 0015 0015 0015 0015 0015 0015 0015 0040 0015 0040 0015 0040 0015 0040 0015 0689 0157 0056 0015 0E94

what i got from GC-IRL is

0000 0070 0000 0022 014F 009C 0015 0014 0015 003E 0015 003E 0015 0014 0015 0014 0015 0014 0015 0014 0015 003E 0015 003E 0015 0014 0015 003E 0015 0014 0015 003E 0015 0014 0015 0014 0015 0014 0015 0014 0015 0014 0015 003E 0015 0014 0015 003E 0015 0014 0015 0014 0015 0014 0015 003E 0015 003E 0015 0014 0015 003E 0015 0014 0015 003E 0015 003E 0015 003E 0016 02E6

is there equals or is there a conversion utility

ASM

After what kind of conversion?

That is a totally different signal (same NEC1 protocol, but different device and function codes).


An incorrect, but maybe close enough, version of the signals you quoted first. I don't know whether Global-Cache can/should do better. I don't know whether the real device meant to receive the signal will care about the ways in which that is wrong. Try it and see.


From what to what?

Edit: I just realized what you did: You used my MakeHex program, or something similar, but you didn't translate the device and function numbers from hex to decimal. You just used the hex numbers as if they were decimal.
The device code is 8615, which is two hex numbers: 86 hex is 134 decimal, 15 hex is 21 decimal. So if you're using MakeHex, you need to set Device=134.21, but instead you set device=8615.
The function is 14 hex, which is 20, decimal, but you used 14 decimal.

hi,
thanks for replay but i did not underestand well what u mean exactly ,
i already use makehex.exe tool to convert ir code with the same parameters u said as follows:

Device=134.21
Function=20

Protocol=NEC
Frequency=38000
Time Base=564
One=1,-3
Zero=1,-1
Prefix=16,-8
Suffix=1,-78
R-Prefix=16,-4
R-Suffix=1,-174
Default S=~D
Form=*,D:8,S:8,F:8,~F:8,_;*,_

and that is the o/p:
Device Code: 134.21 Function: 20
0000 006D 0022 0002 0157 00AC 0015 0015 0015 0040 0015 0040 0015 0015 0015 0015 0015 0015 0015 0015 0015 0040 0015 0040 0015 0015 0015 0040 0015 0015 0015 0040 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0040 0015 0015 0015 0040 0015 0015 0015 0015 0015 0015 0015 0040 0015 0040 0015 0015 0015 0040 0015 0015 0015 0040 0015 0040 0015 0040 0015 0689 0157 0056 0015 0E94

so what is missing
and how to verify o/p from gc-irl and compare it with the above o/p

regards
ASM

The MakeHex output you included in post 3 is correct: device 134.21 function 20.

The MakeHex output you included in post 1 is wrong: device 167 function 14 (the IR signal only encodes the low eight bits of each number, so 8615 is identical to 167).

The MakeHex output you included in post 3 is a clean NEC1 signal device 134.21 function 20 (all timing, frequency and structure correct).

The GC-IRL string you included in post 1 is dirty NEC1 signal device 134.21 function 20 (device and function codes correct but timing, frequency and structure all slightly off).

hi,
so u mean that gc-irl is bad ir learner oohhhhhhhh my god i just buy it is there a way so i can verify that capturing ir codes from gc-irl is ok or not from pc i mean is there a tool that can puts on a pc and insert hex code and it transmitte ir through laptop irda

regards
ASM

The code may not be exactly the same, as the GC-IRL captures optically, but that 'dirty' code will still work. IR receivers don't count actual pulses, as they are optical, but rather capture the wave form of the command, which can vary greatly without causing issue. I've see this with every learner that doesn't have a built in database and it has never caused me any problems.