V202 protocol bind two times corrupt screen

If I bind two times to my JD-385, then all characters on LCD screen will corrupt and not readable. But all buttons are still usable, I can press EXT and switch off remote.

I am using Devo7e w/ build version 4cf2f3b (latest nightly build for download I suppose)
I own two JD-385 myself using V202 protocol which both quads can produce such issue

Steps to reproduce:
1) In Model Setup Page, bind JD-385 normally using V202 protocol and wait a few seconds until success
2) While the connection w/ JD-385 is still valid (LED on JD-385 not flashing), bind AGAIN in Model Setup Page
3) All characters on LCD screen become corrupt until switch off remote

*** I did not test this on emulator
*** If others also consider this as bug, then I'll report new bug in bitbucket
*** Or I suggest disable Bind button while connection is still valid to prevent such behaviour

I was not able to reproduce it in the emulator but this means really nothing when looking at LCD issues because it is very different between the emu and the real tx.
I don't have a 7e so I can't test further.
What do you mean with "valid connection"? In the tx' view there will always be a valid connection (as long as no telemetry is used where the tx can "hear" that the receiver is still there and bound...). Rebinding has never been a problem and in your case it looks more like a problem with a misconfigured LCD.

Can you post some pictures? Are all character at their place, only unreadable? Are they looking like coming from another language (like Chinese, Russian) or completely random?

rbe,

What "valid connection" means is that my 7E is still connected to JD-385, i.e. binded successfully, placed close within connection range and I can control my JD-385 at that time (LED on JD-385 is solid)
P.S. if JD-385 cannot receive tx signal, LED will begin blinking slowly

Indeed I encountered this problem the first time when I accidentally bind my JD-385 twice

the characters are at their place, just that they look all messed up like complete random.
I will upload more pics or video later tonight.

I mentioned the issue back in June. I forgot the discussion around it. LOL

Here's the video demonstrating it for the dev.



I guess a proper bug report wasn't filed and thus why it slipped through the radar.

daryoon,

thx for the video demostration

It's the exact kind of corrupted characters that I mean

btw, last night I also experienced the kind of blank screen in your video from 1:18

Seems that for recent nightly build I cannot reproduce the same bug anymore
I shall consider this issue invalid for this time being...

Daryoon,

Please provide to me your Xieda 9958 devo 7E config file

Thanks

Already sent you a link and explanation in the PM reply to you. Hope it works out for you.