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.

Sign up for GitHub

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

Jump to bottom

Enable API for parameter values from the firmware #488

Closed
knmcguire opened this issue Oct 18, 2019 · 4 comments
Closed

Enable API for parameter values from the firmware #488

knmcguire opened this issue Oct 18, 2019 · 4 comments
Milestone
2020.09

Comments

@knmcguire
Copy link
Member

It would be great to have a similar structure as what the logging has now with logGetFloat() etc. This is to also accommodate the new applayer as mentioned in #487.
@knmcguire knmcguire changed the title Enable getting and set parameter values from the firmware Enable API for parameter values from the firmware Oct 18, 2019
knmcguire added a commit that referenced this issue Oct 20, 2019
@knmcguire
#488 added parameter api to code and tested it.
eaea53d
@knmcguire
Copy link
Member Author

currently this worked with the newly implemented applayer, however maybe should also add a 'getparameter' function to it?

knmcguire added a commit that referenced this issue Oct 20, 2019
@knmcguire
#488 removed debugmessages..
ba5c269
knmcguire added a commit that referenced this issue Oct 21, 2019
@knmcguire
#488 started doc about p2p API
bca6b00
knmcguire added a commit that referenced this issue Oct 23, 2019
@knmcguire
#488 added important warning about nrf build side
8970f7c
@knmcguire
Copy link
Member Author

Related to this issue #502

knmcguire added a commit that referenced this issue Jun 30, 2020
@knmcguire
#488 remove warning about compiling with bluetooth
3a53e7b
@knmcguire
Copy link
Member Author

knmcguire commented Jun 30, 2020 •
edited
Loading

woops, the above commit was actually for the peer 2 peer. bluetooth is now automatically disabled due to this fix: bitcraze/crazyflie2-nrf-firmware#34. So I was able to remove the warning from the doc

knmcguire added a commit that referenced this issue Jun 30, 2020
@knmcguire
#488 added set functions to parameters
913324c
knmcguire added a commit that referenced this issue Jun 30, 2020
@knmcguire
#488 mention the internal access functions in the app layer userguide
026f62a
@knmcguire
Copy link
Member Author

Alright, this is pretty much finished. I tested it out with the OOT build and seems to work fine as planned. There might be some precision things that might can be handled better, but it would be good to see if users will actually start using this for their apps.

@knmcguire knmcguire added this to the next-release milestone Jun 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
2020.09
Development

No branches or pull requests
1 participant
@knmcguire