Closed jelle737 closed 8 years ago
thnx
a user in RC groups have this problem .https://www.rcgroups.com/forums/showpost.php?p=36245565&postcount=1291 i didnt have time to test the latest change with USE_FAST_SWITCHING , i wonder if its a problem with this change or is his own library problem
Both changes can't do anything like that to the screen. Fast switching does straight port manipulation, you can compare it like changing straight in the registry of the computer (it was already there, not changing wrongful memory). I kind of made everything a bit universal but since this git is for RealAcc only (that's why I choose to pull some code) it might be better to tidy up the code and drop all the non diversity code (and the use of isDiversity()), all the clutter in the screens code for single receivers and all the extra unclean programming that made the original project universal. I personally don't own a RealAcc but made my own receiver, it's very similar to RealAcc, pictures are somewhere on Shea's RC groups thread. I programmed mine and like to share back the good stuff in my code. I could do an effort to clean up some of this code? His error seems to be that his call_sign is longer then 10 characters, it's as long as the while thing showing up his screen. I think he should clear the EEPROM and reset the call_sign, don't know at this moment what happened there though.
can we talk through e-mail? gchatzisavvidis At gmail
Port manipulation used for faster switching, to be enabled or disabled using feature toggle USE_FAST_SWITCHING.
Inspired and substantiated here: https://github.com/sheaivey/rx5808-pro-diversity/pull/98