Skip to content
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

PJON 13.0 support #9

Open
gioblu opened this issue Dec 23, 2020 · 3 comments
Open

PJON 13.0 support #9

gioblu opened this issue Dec 23, 2020 · 3 comments

Comments

@gioblu
Copy link

gioblu commented Dec 23, 2020

Ciao @xlfe thank you very much for your support, I hope you are fine and things are going smooth there.
Have you planned to update PJON-cython to be compatible with PJON 13.0?
Some users have asked about it :)

@xlfe
Copy link
Owner

xlfe commented Dec 28, 2020

@gioblu I have been a bit out of the loop with micros recently (unfortunately), so didn't realise PJON 13 was released.

I have updated PJON-cython and got all the tests to pass as previously but I do not have time currently to test it on real hardware. I'm also not sure if there's new APIs needed to be added for full v13 support.

Would you have someone who would be able to test it?

They can install the version with PJON 13 support by doing the following

python -m pip install git+https://github.com/xlfe/PJON-cython@9f05db45a4665ef13652d324ec625b84fae3bf4c

Test log
log-d835b20d-956e-45be-b4a6-037dae62306a.txt

@gioblu
Copy link
Author

gioblu commented Dec 30, 2020

Ciao @xlfe thank you very much for your very prompt response, I will run tests myself and suggest to the community to do the same, I will try to report back results as soon as possible.

@akadlec
Copy link

akadlec commented Jan 26, 2021

Hi @xlfe is possible to implement TX and RX fields in header?

    return dict(
        header=_pi.header,
        id=_pi.id,
        port = _pi.port,
        hops = _pi.hops
        # PJON_Endpoint tx;
        # PJON_Endpoint rx;
    )

according to PJON migration is sender_id moved to tx.id and I'm using this data to get know who send this message

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

No branches or pull requests

3 participants