-
Notifications
You must be signed in to change notification settings - Fork 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
Disabling of init sequence not working #3
Comments
Hi @deimi, I saw that you've done a fork for this. I had to work other projects, and now I want to ask you if your changes are solving your problem. Is true that I did not test it too much without initialization sequence, because I don't use it without it. |
Hi! Due to lack of receivers which require an init sequence, I have checked the output of the transmitter with an oscilloscope. It looks good to me and should work for your receivers which need an init sequence. |
@deimi good if you want you can make a pull request and I will merge it. |
I already made a pull request for this in november after I verified the changes in my fork. |
@SergiuToporjinschi status? |
If the checkbox for the init sequence is disabled, the module is still doing the init sequence before sending the binary.
A workaround is to set the init sequence timings to zero even if the checkbox is not selected.
The text was updated successfully, but these errors were encountered: