Page 1 of 1

Help with non-standard encoding

Posted: Thu Aug 01, 2019 2:53 am
by roscoe71
Hello All,

I have been trying to figure out the encoding for my Dynasty Laser Tag Guns.

The protocol doesn't seem to follow the normal standard protocols, or any of the miles, or miles2 protocols.

There seem to be long (800us) Marks and Spaces, and short (400us) marks and spaces. It also doesn't seem to be a Manchester encode, at least it doesn't look like it me.

The header is 1600us.

Any one have any thoughts ?

Thanks !
Blue_Pistol_post.png

Re: Help with non-standard encoding

Posted: Thu Aug 01, 2019 1:12 pm
by AnalysIR
It seems to be standard enough
fooInverted.jpg
Logically it looks like the above (inverted). Remember that most IR receivers invert the logic of the signal.

Overall it seems easily reproducible etc. (EDIT: See note in next post about Manchester Encoding)

However, I cannot assist any further without timings (try using IRremote to capture the raw signal (see examples) ). I f you post them here I will have a look.

Re: Help with non-standard encoding

Posted: Thu Aug 01, 2019 1:16 pm
by AnalysIR
I just checked and Dynasty Laser tag is suppoted within our AnalysIR application.

However, you should note it is a Manchester encoding 'style' format.

Re: Help with non-standard encoding

Posted: Fri Aug 02, 2019 1:48 am
by roscoe71
Thanks for the quick response,

Below is the output from the device. It is based on the waveform i posted.
As you pointed out, it is inverted.

I purchased a copy of your application, Last four of my signature is 616F.
(I haven't received the license key yet though)

Whats the protocol name that this device uses ?
It looks like some kind of BiPhase, based on the Mark and Space 800us values my guess is differential manchester.

Thanks Again !
-R

Mark, Space
1650 350
450 350
400 400
400 400
400 750
450 700
450 750
400 750
450 350
400 400
400 400
400 400
800 350
400 400
400 400
400 400
800 350
400 400
400 400
750 800
400 200

Re: Help with non-standard encoding

Posted: Fri Aug 02, 2019 3:01 pm
by AnalysIR
Your registration key has been emailed.

It is manchester encoding with a header of 1600:400.

we label it as Dynasty20LASERTAG in AnalysIR. (make sure CUSTOM is checked under Protocols)

However, I noticed that the signal you posted did not decode properly.

The timings will be better if you record using the Firmware provided with AnalysIR. (I assume you are using an Arduino)

So if you send me a set of signals (via Menu->File->Save Session ) I will look at it more closely & let you know.

Also, let me know what IR receiver you are using & dev board.

Re: Help with non-standard encoding

Posted: Fri Aug 02, 2019 10:54 pm
by roscoe71
Hello,

Thanks for the license.

My receiver is TSOP382.
I have some spare Adafruit Feather 32U4's i am using as a test bed.

just to confirm, it looks like your code wants pin D2 for the Receiver line.

I loaded your sketch, but im not getting any information from it. Is there some test commands i can send to interact with it to see if its talking ?

thanks !

-R

Re: Help with non-standard encoding

Posted: Fri Aug 02, 2019 11:29 pm
by roscoe71
Ok,

I figured out its basically a leonardo board. Getting data finally.

Re: Help with non-standard encoding

Posted: Fri Aug 02, 2019 11:42 pm
by roscoe71
Greetings,

I am on the dev version (1.16.100.8303), it doesn't seem to have the Dynasty20LASERTAG type.
It sees the data, but its showing up as raw.

Thoughts ?
-R

Re: Help with non-standard encoding

Posted: Fri Aug 02, 2019 11:48 pm
by roscoe71
Greetings (again),

Sorry i forgot the session data...

-R

Re: Help with non-standard encoding

Posted: Sat Aug 03, 2019 10:25 am
by AnalysIR
I will email you an updated config file with all the latest protocols, shortly.
...and I will look at your session file over the weekend.