-
Notifications
You must be signed in to change notification settings - Fork 657
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Connecting the two receivers #25
Comments
It's very hard to understand what you are saying. But I am guessing you are requesting support for using two receivers simultaneously, which is currently not possible. Unfortunately, there seems to be no "elegant" way to fix this. The problem is that Since This is a limitation of the Arduino interrupt handling system, it seems :-/. |
One hackish workaround: If we arbitrarily limit ourselves to e.g. 6 interrupts, we could provie six "outer" interrupt handlers; then modify But that is still limited in flexibility and somewhat ugly. Hrm. |
Sorry for my English. Thanks for the answer. |
Another dirty hack that might work would be switching between both receivers once every second. Of course with the risk of missing some signals, depends on your needs. void loop() { |
sui77 Thank you. But I do not fit this option, you must monitor two frequencies at once. I implemented without interruption. But the accuracy lutshe wants to be, although operational. |
Still managed to use the hack . delay ( 200 ) and set the tolerable results obtained . |
Is there a reason why the class uses static definition? as in RCSwitch::? |
Thank you , I have long been solved the problem of writing separate code to the second receiver . 22 травня 2016, 12:53:35, від "bilogic" < notifications@github.com >: Is there a reason why the class uses static definition? as in RCSwitch::? |
@bilogic The class uses static definitions because Arduino interrupt handler callbacks sadly only can access static / global data; and interrupt handlers cannot easily be shared for different users. In particular, they have no So I am really curious to learn how you bypassed that problem. But please let's not put it onto this old, closed issue; instead, submit a pull request, and/or a new issue where you explain your changes. |
My level of English is low and I did not understand everything. But answer me more . I used the library on the same frequency , but dorabatival library. I added Oregon and Lacrose. I also added support for long codes for other sensor types. In the future, when I will modify the code I'll post the code . At the time of Danian though workable but not beautiful . @bilogic The class uses static definitions because Arduino interrupt handler callbacks sadly only can access static / global data; and interrupt handlers cannot easily be shared for different users. In particular, they have no void *refCon parameter, which many other callback based APIs offer. So I am really curious to learn how you bypassed that problem. But please let's not put it onto this old, closed issue; instead, submit a pull request, and/or a new issue where you explain your changes. — |
@fingolfin, @MeJIyA my codes and suggestions are on #63 |
hi, |
The problem is when you connect the two receivers(315MHz and 433MHz). In consequence of using a variable of type static, it overwrites data in a single memory controller.
The text was updated successfully, but these errors were encountered: