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

frame sending time and delayMicroseconds #15

Open
WeareGermans opened this issue Jun 7, 2014 · 0 comments
Open

frame sending time and delayMicroseconds #15

WeareGermans opened this issue Jun 7, 2014 · 0 comments

Comments

@WeareGermans
Copy link

Hi,

i am using v0.5-FrSky, 06-11-2013.

Is it necessary to send the FrSky Frames together?
Can i send them to odd times that the chance of sending all frames at the same time gets reduced, or will i run in some troubles with the receiver if let's say Frame 3 is sent without Frame 1 prior?

what is the delayMicroseconds(138); in Mavlink.ino for? Is it really neccessary or can it at lease be reduced?

I am trying to combine this code with neopixels and am running in timing issues with the current code.
Since blinking with switching times unter 100ms is unreliable.

Thanks for the help!

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

1 participant