• 10 dec 2017: forum version update. In case of issues use this topic.
  • 30 nov 2017: pilight moved servers. In case of issues use this topic.
Hello There, Guest! Login Register


3T-Motors 434Mhz senders / receivers
#21
You need to use the instructions for manually compiling pilight from the GitHub repo to get that folder structure and to compile the protocol
 
Reply
#22
I created the required pilight folder structure by manually installing the latest pilight version.

I created the corresponding protocol files (see attachment).
I modified the CMakeConfig.txt, CMakeExclude.txt and protocol.c files according to the WIKI instructions.
After some debugging I was able to create the *.so file for usage as a module.
The *.so file is present in the required protocols folder and I do not get any error code during the creation of the *.so file.

My problem is now that the pilight send command is not "seeing" the freshly created protocol as supported. So I am not able to test the functionality of the protocol.

Any suggestion how I should proceed?


Attached Files
.zip   3T Motors Screen Protocol.zip (Size: 2.86 KB / Downloads: 24)
 
Reply
#23
Does this code work?
 
Reply
#24
I have done a lot of testing with sending raw codes. This worked very well as described in my earlier post. So I am sure that I found the right code logic.

I transferred the logic into the attached protocol (hopefully correctly). But this beta protocol is not recognized by my pilight setup (reason is unknown to me).

Therefore I could not test the functionality of the attached protocol.
Once I get this protocol to work I will do extensive testing with my screen devices (in the same way as I did the raw code testing).
 
Reply
#25
Did you test just compiling the sources into pilight instead of using the module?
 
Reply
#26
I just used the variant to use the new protocol as a module.

Since the beta protocol is only available on my local hard drive: what is the best way to compile the new protocol into my current pilight installation?

BTW: many thanks for your great support!
 
Reply
#27
Download the full pilight source and put both files in the correct protocol folder. Then recompile.
 
Reply
#28
It works!

- the new protocol is being detected now
- pilight-sending: ID output is completely working as it should (tested with 2 different IDs)
- pilight-sending: "Up" and "Down" state commands are working as they should
- pilight-sending: Unit 0 (represents "all devices") works as expected
- pilight-sending: Units 1 to 15 are not working; must be a bug in my protocol

Is there a log file method to check what the pilight-send command is sending out (e.g. raw code tracking)?
With that information I should be able to eliminate the last remaining bug.
 
Reply
#29
Run pilight in debug mode. It will show you the raw codes it generates.
 
Reply
#30
I did further checks in debug mode.
The system ID code is being sent out correctly by pilight-send.
But the unit code is not created correctly (unit codes from 0 to 15 are allowed for this device).

Something seems to be wrong in this section:
Code:
static void createUnit(int unit) {
    int binary[255];
    int length = 0;
    int i=0, x=0;

    length = decToBin(unit, binary);
    for(i=0;i<=length;i++) {
        if(binary[i]==1) {
            x=i*2;
            createHigh(58+x, 58+x+1);
        }
    }
}
Do you have an advice what could be wrong here?
 
Reply
  


Possibly Related Threads...
Thread Author Replies Views Last Post
  Rohrmotor24 receivers protocol TRIROG 6 3,481 03-18-2016, 08:29 AM
Last Post: TRIROG

Forum Jump:


Browsing: 1 Guest(s)