10000 Use both PJON and PJON_ASK · Issue #3 · gioblu/PJON_ASK · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Use both PJON and PJON_ASK 8000 #3

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

Open
agsb opened this issue Apr 28, 2016 · 2 comments
Open

Use both PJON and PJON_ASK #3

agsb opened this issue Apr 28, 2016 · 2 comments

Comments

@agsb
Copy link
agsb commented Apr 28, 2016

hello,

I try use both PJON and PJON_ASK at same time and got compilation errors for symbolic constants and function names.

Could resolve those issues and got the best of both, using wires and waves ?

There are any specific conditions or pragmas for values chosen at #define ?

thanks a lot for the awsome simple network.

[]s

@gioblu
Copy link
Owner
gioblu commented Apr 29, 2016

Ciao @agsb!
Yes, this is an important issue has to be fixed.

I am evaluating various strategies to let this two libraries to coexist. One idea is to create in the PJON repository a set of strategies to communicate on different media. Every strategy will have defined only the low level functions used to transmit and receive, see:
gioblu/PJON#52
(in this case the existence of this repo will be useless, and will only redirect to PJON repository, describing how to use the strategy for radio commuication)

I was waiting for some sort of feedback on this side, but yours is the first I receive :)

@gioblu
Copy link
Owner
gioblu commented May 6, 2016

Ciao @agsb I am happy to confirm you that since today's release PJON 3.0-beta has integrated PJON_ASK repository as a physical layer strategy: https://github.com/gioblu/PJON

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants
0