Page 1 of 1

fail or feature?

Posted: Sun Jan 15, 2017 4:01 pm
by volvodidi
Hi,
I recorded 4 times the same signal from my Panasonic AC Remote.
It starts always with 07F70606F7F706069090363690903636 (Panasonic 128AC).
When i open the value window it change to F7F70606F7F706069090363690903636.
Only in LSB8 mode.

Dieter
fail-analysir.jpg

Re: fail or feature?

Posted: Mon Jan 16, 2017 11:23 pm
by AnalysIR
Hi Dieter

Please email me a saves session file with several recorded signals & I will investigate.

via: Menu->File->Save Session

It does seem like an extra '0' has crept in!

tnx

Re: fail or feature?

Posted: Tue Jan 17, 2017 4:46 pm
by volvodidi
Hi,
here is a file with 0 at the beginning.
If you load the file, in the first row the 0 will chang into 6, but the other 3 rows are with 0 at the beginning for testing.
Dieter

Re: fail or feature?

Posted: Sun Jan 22, 2017 5:21 pm
by AnalysIR
I jut tested your uploaded signals with the latest 'dev' release of analysir (...8137) & did not detect the same behaviour.

Shortly, I will email you a link to the ..8137 release for you to try out.

Let me know id the issue is resolved.

Re: fail or feature?

Posted: Tue Jan 31, 2017 7:49 pm
by volvodidi
Hi,
no it is not solved, it is the same problem with LSB8.

Dieter

Re: fail or feature?

Posted: Tue Jan 31, 2017 8:49 pm
by AnalysIR
:(

OK, so please list the steps you take to reproduce using the file you uploaded above & I will check it out again.

Re: fail or feature?

Posted: Sun Feb 05, 2017 10:45 am
by volvodidi
Hi,
source is USB ir Toy v2
Tools LSB8
protocol ac only
I recorded 4 times the same value, all with 0 on start and the hole value is diffrent.
I save the session, and when i open the session again, the first row will change in the right value, the rest is the same i recorded.
when i click on value field at the second row, it changes in the right value. All values will change when i change to lsb and again in lsb8, then there are the right values.

Re: fail or feature?

Posted: Wed Feb 08, 2017 1:18 pm
by AnalysIR
Hi

I looked into this and believe i have found the error - related to handling/formatting of very large numbers.

I have also implemented a fix, which will be included in the next 'dev' release.

However, as there is an easy workaround for this I suggest the following:
Workaround: When recording signals do so using the MSB setting and when you want to reverse engineer the signals, select the LSB8 option to convert the HEX for analysis.

Many thanks for your efforts in identifying and resolving this issue.