Issue with "ProtocolDefinition.hpp" on Arduino Nano

[janika1950]

This is an awesome useful piece of code, exactly what I am looking for. I successfully used as it is on my Arduino Nano with INT0 (pin2)
My problem after successful protocol detection is how to implement the suggested Timing specification proposal:
makeTimingSpec< #, 10, 20, 34,1038, 35, 99, 100, 32, false>,
I understood to make a change in "ProtocolDefinition.hpp" according to this:

static const RxProtocolTable <
    //                   #, clk,  %, syA,  syB,  d0A,d0B,  d1A,d1B, inverseLevel
 /* *  	makeTimingSpec<  1, 350, 20,   1,   31,    1,  3,    3,  1, false>, // (PT2262)
 *  	makeTimingSpec<  2, 650, 20,   1,   10,    1,  3,    3,  1, false>, // ()
 *  	makeTimingSpec<  3, 100, 20,  30,   71,    4, 11,    9,  6, false>, // ()
 *  	makeTimingSpec<  4, 380, 20,   1,    6,    1,  3,    3,  1, false>, // ()
 *  	makeTimingSpec<  5, 500, 20,   6,   14,    1,  2,    2,  1, false>, // ()
 *  	makeTimingSpec<  6, 450, 20,   1,   23,    1,  2,    2,  1, true>,  // (HT6P20B)
 *  	makeTimingSpec<  7, 150, 20,   2,   62,    1,  6,    6,  1, false>, // (HS2303-PT)
 *  	makeTimingSpec<  8, 200, 20,   3,  130,    7, 16,    3, 16, false>, // (Conrad RS-200)
 *  	makeTimingSpec<  9, 365, 20,   1,   18,    3,  1,    1,  3, true>,  // (1ByOne Doorbell)
 *  	makeTimingSpec< 10, 270, 20,   1,   36,    1,  2,    2,  1, true>,  // (HT12E)
 *  	makeTimingSpec< 11, 320, 20,   1,   36,    1,  2,    2,  1, true>   // (SM5212) */
	makeTimingSpec< 12,  10, 20,  34, 1038,   35, 99,  100, 32, false>  // (EV1527)<---### This line I added.
 
   > rxProtocolTable;

But this gives the following compiler error:

C:\Users\User\Documents\Arduino\libraries\RcSwitchReceiver\src/ProtocolDefinition.hpp:150:15: error: 'RxProtocolTable' does not name a type

  static const RxProtocolTable <

               ^~~~~~~~~~~~~~~

I tried with all the makeTimingSpec<...> lines un-commented: the same error message...
I know it is my lack of enough knowledge in C++.
Could you please direct me what change (maybe more changes) I need exactly to succeed my remote controller EV1527 recognition?
Thank you very much indeed.
Regards: Janos

[dac1e]

There is a comma missing at the end of the line that is just before your added line. Only the last line must not have a comma. I hope, this helps. Regards, Wolfgang.--Gesendet mit der 1&1 Mail AppAm 28.05.25, 11:52 nachm. schrieb janika1950 ***@***.***>: janika1950 created an issue (dac1e/RcSwitchReceiver#2) This is an awesome useful piece of code, exactly what I am looking for. I successfully used as it is on my Arduino Nano with INT0 (pin2) My problem after successful protocol detection is how to implement the suggested Timing specification proposal: makeTimingSpec< #, 10, 20, 34,1038, 35, 99, 100, 32, false>, I understood to make a change in "ProtocolDefinition.hpp" according to this: static const RxProtocolTable < // #, clk, %, syA, syB, d0A,d0B, d1A,d1B, inverseLevel /* * makeTimingSpec< 1, 350, 20, 1, 31, 1, 3, 3, 1, false>, // (PT2262) * makeTimingSpec< 2, 650, 20, 1, 10, 1, 3, 3, 1, false>, // () * makeTimingSpec< 3, 100, 20, 30, 71, 4, 11, 9, 6, false>, // () * makeTimingSpec< 4, 380, 20, 1, 6, 1, 3, 3, 1, false>, // () * makeTimingSpec< 5, 500, 20, 6, 14, 1, 2, 2, 1, false>, // () * makeTimingSpec< 6, 450, 20, 1, 23, 1, 2, 2, 1, true>, // (HT6P20B) * makeTimingSpec< 7, 150, 20, 2, 62, 1, 6, 6, 1, false>, // (HS2303-PT) * makeTimingSpec< 8, 200, 20, 3, 130, 7, 16, 3, 16, false>, // (Conrad RS-200) * makeTimingSpec< 9, 365, 20, 1, 18, 3, 1, 1, 3, true>, // (1ByOne Doorbell) * makeTimingSpec< 10, 270, 20, 1, 36, 1, 2, 2, 1, true>, // (HT12E) * makeTimingSpec< 11, 320, 20, 1, 36, 1, 2, 2, 1, true> // (SM5212) */ makeTimingSpec< 12, 10, 20, 34, 1038, 35, 99, 100, 32, false> // (EV1527)<---### This line I added. rxProtocolTable; But this gives the following compiler error: C:\Users\User\Documents\Arduino\libraries\RcSwitchReceiver\src/ProtocolDefinition.hpp:150:15: error: 'RxProtocolTable' does not name a type static const RxProtocolTable < ^~~~~~~~~~~~~~~ I tried with all the makeTimingSpec<...> lines un-commented: the same error message... I know it is my lack of enough knowledge in C++. Could you please direct me what change (maybe more changes) I need exactly to succeed my remote controller EV1527 recognition? Thank you very much indeed. Regards: Janos —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[dac1e]

Oh, sorry, I didnt see, that you commented out all other lines. So forget my previous response. I will have a deeper look soon.--Gesendet mit der 1&1 Mail AppAm 28.05.25, 11:52 nachm. schrieb janika1950 ***@***.***>: janika1950 created an issue (dac1e/RcSwitchReceiver#2) This is an awesome useful piece of code, exactly what I am looking for. I successfully used as it is on my Arduino Nano with INT0 (pin2) My problem after successful protocol detection is how to implement the suggested Timing specification proposal: makeTimingSpec< #, 10, 20, 34,1038, 35, 99, 100, 32, false>, I understood to make a change in "ProtocolDefinition.hpp" according to this: static const RxProtocolTable < // #, clk, %, syA, syB, d0A,d0B, d1A,d1B, inverseLevel /* * makeTimingSpec< 1, 350, 20, 1, 31, 1, 3, 3, 1, false>, // (PT2262) * makeTimingSpec< 2, 650, 20, 1, 10, 1, 3, 3, 1, false>, // () * makeTimingSpec< 3, 100, 20, 30, 71, 4, 11, 9, 6, false>, // () * makeTimingSpec< 4, 380, 20, 1, 6, 1, 3, 3, 1, false>, // () * makeTimingSpec< 5, 500, 20, 6, 14, 1, 2, 2, 1, false>, // () * makeTimingSpec< 6, 450, 20, 1, 23, 1, 2, 2, 1, true>, // (HT6P20B) * makeTimingSpec< 7, 150, 20, 2, 62, 1, 6, 6, 1, false>, // (HS2303-PT) * makeTimingSpec< 8, 200, 20, 3, 130, 7, 16, 3, 16, false>, // (Conrad RS-200) * makeTimingSpec< 9, 365, 20, 1, 18, 3, 1, 1, 3, true>, // (1ByOne Doorbell) * makeTimingSpec< 10, 270, 20, 1, 36, 1, 2, 2, 1, true>, // (HT12E) * makeTimingSpec< 11, 320, 20, 1, 36, 1, 2, 2, 1, true> // (SM5212) */ makeTimingSpec< 12, 10, 20, 34, 1038, 35, 99, 100, 32, false> // (EV1527)<---### This line I added. rxProtocolTable; But this gives the following compiler error: C:\Users\User\Documents\Arduino\libraries\RcSwitchReceiver\src/ProtocolDefinition.hpp:150:15: error: 'RxProtocolTable' does not name a type static const RxProtocolTable < ^~~~~~~~~~~~~~~ I tried with all the makeTimingSpec<...> lines un-commented: the same error message... I know it is my lack of enough knowledge in C++. Could you please direct me what change (maybe more changes) I need exactly to succeed my remote controller EV1527 recognition? Thank you very much indeed. Regards: Janos —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[dac1e]

Hello janika1950, now I think I know what the misunderstanding is. You must not change ProtocolDefinition.hpp. Please change back the original version. Instead you should place the RxProtocolTabel in your sketch, like it is done in the example sketch PrintReceivedData.ino. As a first step, I propose to clone PrintReceivedData.ino and replace line 42 to 57 by the following, to see whether it is working: DATA_ISR_ATTR static const RxProtocolTable < makeTimingSpec< 12, 10, 20, 1038, 23, 35, 99, 100, 32, false> // (EV1527)

rxProtocolTable;

ProtocolDefinition.hpp just contains the classes that allow you to define your protocol in your sketch. I will probably rename the file ProtocolDefinition.hpp for further releases, because the name is misleading. Regards, Wolfgang Von: janika1950 ***@***.***> Gesendet: Mittwoch, 28. Mai 2025 23:52 An: dac1e/RcSwitchReceiver ***@***.***> Cc: Subscribed ***@***.***> Betreff: [dac1e/RcSwitchReceiver] Issue with "ProtocolDefinition.hpp" on Arduino Nano (Issue #2) <https://avatars.githubusercontent.com/u/213865596?s=20&v=4> janika1950 created an issue (dac1e/RcSwitchReceiver#2) <#2> This is an awesome useful piece of code, exactly what I am looking for. I successfully used as it is on my Arduino Nano with INT0 (pin2) My problem after successful protocol detection is how to implement the suggested Timing specification proposal: makeTimingSpec< #, 10, 20, 34,1038, 35, 99, 100, 32, false>, I understood to make a change in "ProtocolDefinition.hpp" according to this: static const RxProtocolTable < // #, clk, %, syA, syB, d0A,d0B, d1A,d1B, inverseLevel /* * makeTimingSpec< 1, 350, 20, 1, 31, 1, 3, 3, 1, false>, // (PT2262) * makeTimingSpec< 2, 650, 20, 1, 10, 1, 3, 3, 1, false>, // () * makeTimingSpec< 3, 100, 20, 30, 71, 4, 11, 9, 6, false>, // () * makeTimingSpec< 4, 380, 20, 1, 6, 1, 3, 3, 1, false>, // () * makeTimingSpec< 5, 500, 20, 6, 14, 1, 2, 2, 1, false>, // () * makeTimingSpec< 6, 450, 20, 1, 23, 1, 2, 2, 1, true>, // (HT6P20B) * makeTimingSpec< 7, 150, 20, 2, 62, 1, 6, 6, 1, false>, // (HS2303-PT) * makeTimingSpec< 8, 200, 20, 3, 130, 7, 16, 3, 16, false>, // (Conrad RS-200) * makeTimingSpec< 9, 365, 20, 1, 18, 3, 1, 1, 3, true>, // (1ByOne Doorbell) * makeTimingSpec< 10, 270, 20, 1, 36, 1, 2, 2, 1, true>, // (HT12E) * makeTimingSpec< 11, 320, 20, 1, 36, 1, 2, 2, 1, true> // (SM5212) */ makeTimingSpec< 12, 10, 20, 34, 1038, 35, 99, 100, 32, false> // (EV1527)<---### This line I added. rxProtocolTable; But this gives the following compiler error: C:\Users\User\Documents\Arduino\libraries\RcSwitchReceiver\src/ProtocolDefinition.hpp:150:15: error: 'RxProtocolTable' does not name a type static const RxProtocolTable < ^~~~~~~~~~~~~~~ I tried with all the makeTimingSpec<...> lines un-commented: the same error message... I know it is my lack of enough knowledge in C++. Could you please direct me what change (maybe more changes) I need exactly to succeed my remote controller EV1527 recognition? Thank you very much indeed. Regards: Janos — Reply to this email directly, view it on GitHub <#2> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AOE772CTNUZG5XLFZ67PYEL3AYVZLAVCNFSM6AAAAAB6D67FUKVHI2DSMVQWIX3LMV43ASLTON2WKOZTGA4TQNRTHEYTINQ> . You are receiving this because you are subscribed to this thread. <https://github.com/notifications/beacon/AOE772DGMJWB4D2XARPOQ333AYVZLA5CNFSM6AAAAAB6D67FUKWGG33NNVSW45C7OR4XAZNFJFZXG5LFVJRW63LNMVXHIX3JMTHLRML3FI.gif> Message ID: ***@***.*** ***@***.***> >

[dac1e]

Mmh, strange layout of the comments that I sent via email???

[janika1950]

Hello, first of all, thank you very much for your quick and effective support. Yes, I was able to sort out the problem as you suggested: instead of running /examples/LearnRemoteControl I used /examples/PrintReceivedData where I added:
makeTimingSpec< 12, 10, 20, 34, 1038, 35, 99, 100, 32, false> // (EV1527)<---### This line I added
So it looks like:

DATA_ISR_ATTR static const RxProtocolTable <
  //               #, clk,  %, syA,  syB,  d0A,d0B,  d1A,d1B, inverseLevel
  makeTimingSpec<  1, 350, 20,   1,   31,    1,  3,    3,  1, false>, // (PT2262)
//makeTimingSpec<  2, 650, 20,   1,   10,    1,  3,    3,  1, false>, // ()
//makeTimingSpec<  3, 100, 20,  30,   71,    4, 11,    9,  6, false>, // ()
//makeTimingSpec<  4, 380, 20,   1,    6,    1,  3,    3,  1, false>, // ()
//makeTimingSpec<  5, 500, 20,   6,   14,    1,  2,    2,  1, false>, // ()
  makeTimingSpec<  6, 450, 20,   1,   23,    1,  2,    2,  1, true>,  // (HT6P20B)
  makeTimingSpec<  7, 150, 20,   2,   62,    1,  6,    6,  1, false>, // (HS2303-PT)
  makeTimingSpec<  8, 200, 20,   3,  130,    7, 16,    3, 16, false>, // (Conrad RS-200)
  makeTimingSpec<  9, 365, 20,   1,   18,    3,  1,    1,  3, true>,  // (1ByOne Doorbell)
  makeTimingSpec< 10, 270, 20,   1,   36,    1,  2,    2,  1, true>,  // (HT12E)
  makeTimingSpec< 11, 320, 20,   1,   36,    1,  2,    2,  1, true>,  // (SM5212)
  makeTimingSpec< 12, 300, 20,   2,   23,    2,  4,    4,  2, false>,  // (Sygonix)
  // Note that last row must not end with a comma.
  makeTimingSpec< 13,  10, 20,1038,   23,   35, 99,  100, 32, false>  // (EV1527)<-----I added according to Wolfgang
> rxProtocolTable;

Actually it was not even necessary, as the printout strait recognized protocol #1 which is PT2262 (similar timing and bit nr. like EV1527) only the meaning of address and data bits are different.
Now my decodings look like this:

// my 4 button key-fob (EV1527) Transmitter codes:
Received 3453058 / Protocol number: 1		binary: 0011 0100 1011 0000 1000 0010
Received 3453064 / Protocol number: 1		binary: 0011 0100 1011 0000 1000 1000
Received 3453060 / Protocol number: 1		binary: 0011 0100 1011 0000 1000 0100
Received 3453057 / Protocol number: 1		binary: 0011 0100 1011 0000 1000 0001

// my 10 pieces of (QIACHIP-TX181) 1527 Transmitter codes:
1 - Received 487409 / Protocol number: 1	binary: 0000 0111 0110 1111 1111 0001
2 - Received 145249 / Protocol number: 1	binary: 0000 0010 0011 0111 0110 0001
3 - Received 400193 / Protocol number: 1	binary: 0000 0110 0001 1011 0100 0001
4 - Received 133681 / Protocol number: 1	binary: 0000 0010 0000 1010 0011 0001
5 - Received 475681 / Protocol number: 1	binary: 0000 0111 0100 0010 0010 0001
6 - Received 133601 / Protocol number: 1	binary: 0000 0010 0000 1001 1110 0001
7 - Received 475601 / Protocol number: 1	binary: 0000 0111 0100 0001 1101 0001
8 - Received 133521 / Protocol number: 1	binary: 0000 0010 0000 1001 1001 0001
9 - Received 475521 / Protocol number: 1	binary: 0000 0111 0100 0001 1000 0001
10- Received 133441 / Protocol number: 1	binary: 0000 0010 0000 1001 0100 0001

I like this library so much, that I would like to test it with ESP32 and Raspberry Pi Pico. I hope that would work exactly so good.
Herzlichen Dank!
Best regards, Janos

[dac1e]

Hello Janos,

thanks for the feedback.

I did run it already on an ESP32 board (ESP32S3DEVK-C1N8), but not on a Raspberry PI.
If you get it running on a Raspberry PI, please let me know.

Regards,
Wolfgang

[janika1950]

Hello Wolfgang,

Yes, I'm going test it on Rpi Nano. I think it will run OK.
Thanks again.

Regards,
Janos

[janika1950]

I mean Rpi Pico, not Nano...