And so, we continue the series of research. analysis of buttons (event codes)
1 Like
check decoder/encoder/parse event
Oh no the new dfu isnāt downloadable on github
It was merged, so guess you can install dev.
Derr, Iām stupid, thanks man, appreciate it
Thanks SkorP, this is very close 
I have not tested tamper yet.
But I tested product model DCT2, and it is the same results as the DCT10.
The label changes I can think of so far would be.
Bit_0 = āOpen/Motionā - if alarm system disabled, than this code is āokā
bit_4 = āwireless reedā or just āreedā - that is how they are called in the āsecurity businessā.
When I get home I will test tamper for button label and I will send to you the result.
You are amazing, this project gives me so much joy. There are many brands of wireless security systems. I will have to learn to decode them myself with what you have taught mešš»
Hey SkorP, so I was able to play with a pmd75 in tamper mode. Alot of interesting code.
So coding/button name looks good while tamper active or disabled.
But when first open device and tamper activated, I get
Event 0x2A
Stat:ok,tamper on(alarm),power on, motion sensor.
I also get
Event 0x2B
Stat: alarm, tamper on,power on, motion sensor.
So it would seem, when tamper is first triggered, the device first tells the alarm system, that the reed is open 5x to trigger an alarm, than it tells that it is in tamper mode and that the power is on, than it follows by finishing its transmission by saying the actual position (open/close) and that it is still in tamper.
did not understand anything). just tell me what you would change and by what logic events should be displayed
Sorry.
Change
Bit_0 = āOpen/Motionā
Bit_4 = āwireless reedā
I think this is enough.
I do not have any other model product I can test. I do not know what ā bit 2,6 or 7 ā does.
Thankyou
0x2a, 0x2b, I do not worry about
And the logic looks great
Hey SkorP, was there anything else you needed?
Cheers
Well, I corrected your comments, then you tell me if it works or not)
2 Likes
Awesome, just did a test, looks greatšš»
Hi Skorp, your Event Codes look good am i able to send the frequency and Adjust the Serial number on your latest Edit??
thankyou
you know how the package is generated, create the correct package and enter the frequency in the key field, in the same place in the file
I was able to edit the package to change the serial number and the event code, but when I transmitted, the receiver did not accept.
I than tried to send an unedited package, but this also failed to receive. Any ideas?
It must have been midnight, I was able to get it working this morning before work, you are a genius SkorP thankyou
The only trouble Iām getting is the last hex value in the key, I believe itās the CRC. It changes with the value. I guess I will need to run a program each time I change the key to give correct crc? I will try to figure it out tonight
Iāve created a Template for those that come after me, thanks to SkorP who did all the heavy lifting we have a Magellan Protocol.
Iāve used his genius to work out the CRC algorithm using RevengCRC and attached a website that pumps out the correct information.
Iāve also written down the conversion path to create a personalised SN and basic Button press key
Template.sub
Filetype: Flipper SubGhz Key File
Version: 1
Frequency: 433920000
Preset: FuriHalSubGhzPresetOok650Async
Protocol: Magellen
Bit: 32
Key: 00 00 00 00 xx xx xx xx
#SN>Bin>RevBin>HexKey
#SnHexKey>Bin>RevBin>Dec
#00 xx 00 00 = SN-xxx000
#xx 00 00 00 = SN-000xxx
#00 00 xx 00 = Event (08-closed)(88-open)(C8-Tamper/Open)
#00 00 00 xx = CRC= (Poly-31/Ini-FE/Xor-0D)
#www.sunshine2k.de/coding/JavaScript/CRC/crc_js.html
Guys, isnāt the correct brand Magellan and not Magellen?
It is, thanks, Iām usually replying late at night or first thing in morning haha good pick up
1 Like