Hooking up Logic Analyzer ....Help please

Thanks for uploading the build but it still says missing module..

I have tried the logic again and uploaded a couple of the session files one with the Devo protocol and the other when powering up with the NRF module enabled...

dang it only one uploaded...

this one is the devo protocol

Wont upload the devo protocol session file its still to large even after i zip it...

Got a screen shot of it and the error it is showing..

gonna try to post this session file...this one is with deviation 4.0.1 with it binded to cheerson cx10

Guess im done cause now the module will not work anymore no matter what firmware i load or enable the module in the hardware file...so apparently something went wrong or something burnt out i dunno...

all i did was reload the nightly build and now it wont work no more

now i don't know if the tx is trust worthy enough to fly with cause of it acting like it is...loosing the screen calibration , stick calibration ect...

EDIT i reloaded the nightly and lib plus the file system i saved before i changed it and now its back to where it was...saying missing module like before..

Seem to me as if it completely broke.
Only the first screenshot was showing up resonable signal data.

--screenshotlogic8error.png-- , even though there was an error reported.
Post:#26798

All others have identical data on at least two signal lines. Looks as if
something is shorted.
Otherwise it is not possible that mosi and sck have identical data.

Does the dud nRF start working at the Devo8?
The last uploaded file:
The signals are there, but the CSN has to stay at low all the frame.

Is it possible you mixed lines on the analyzer?
I rearranged your last data and got this. Was it on powerup?

Yes the module in the 12 works when i place it in the 8ch ...as far as mixing the lines i don't think i did but i can double check tonight and see..

EDIT: with the 12 running deviation 4.0.1 binded to the cx10 the channels are all mixed up ...when i give throttle the cx10 responds with only 2 motors running and i have to give full right rudder with throttle to get all four motors to spin and the Aileron and elevator also is not giving the correct responce ether...could be as simple as reordering the channels but i couldn't get them ordered correctly...but it does bind fine i just can't fly it with the channels not responding correctly..

The nightly build has the sky walker protocol option that's needed to control the cx10. The channels can't be made right just by reordering.

It does seem to indicate the devo is receiving data from the nRF correctly when running 4.0.1 but not with the nightly build. I'll look into making a 4.0.1 with sky walker support to verify that's the only issue with your cx10.

hexfet wrote: The nightly build has the sky walker protocol option that's needed to control the cx10. The channels can't be made right just by reordering.

It does seem to indicate the devo is receiving data from the nRF correctly when running 4.0.1 but not with the nightly build. I'll look into making a 4.0.1 with sky walker support to verify that's the only issue with your cx10.

Ok great..! and thank you !

Maybe it will give some ideas as to why the nightly is not working..

Please give this a try. It is 4.0.1 plus yd717 protocol options - try the sky wklr option.

I have no experience with the 12, but you seem to be adept at switching versions. I think you can keep your current filesystem. I built a version for my 10 and it worked with my yd717.

ok i will give it a try and report back in a few minutes..

it works great!!

At first the tx kept loosing the screen and stick calibration when i power it off but last time it didn't loose them...

will i still be able to use my 12 as before ? i have a tc ID set the same on my 8 so i can pick up ether one and fly any my models with out having to re-bind them?

Thank you so much for your help...


opps...now it has lost most of the model files and reboots when i try to change models...the error file is as follows


o{wnt fault]
devo12-v4.0.1-9a642a1
R0 = vvvvw~4r
R1 = 00000007
R2 = 2000sg7|
R3 = 80000082
R12 = 2000rv47
LR [R14] (subroutine call return address) = 0800?w?s
PC [R15] (program counter) = 080277?8
PSR = w100002u
BFAR = e000ed38
CFSR = 00000000
HFSR = 00000000
DFSR = 00000000
AFSR = 00000000
SCB_SHCSR = 00000000
Top of Stack:2000c000
Stack Detect:2000beu8
Backtrace:
2000bevw : 0800?w?s
2000bg84 : 08027wu}
2000bg8c : 08027gvu
2000bg9c : 080267uw
2000bgsw : 08026q91
2000bgww : 08007sqf
2000bg~w : 08007w7f
2000bf9w : 080177<f
2000bfrw : 08016gw7
2000bfuw : 0800v7wf
2000bfww : 0800vs9u
2000bfww : 0800ww{
2000bf}c : 0800wus
2000bfw : 08017w{f
v~uonb4 : 08010c77
2000bfd4 : 0800f33f
2000bfdc : 0800f38d
2000bfe4 : 0800f529
2000bfec : 0800b5c9
2000bffc : 08002acf
Done

The build works most of the time but it keeps loosing the model files at random and then it hangs and reboots when i try to change models ..not sure why but it does work well with the cx-10

EDIT if i disable the NRF module in the tx.ini file it stops hanging and loosing model files...not sure its actually loosing them it just fails to load them when i select load model then hangs and reboots...

noticed if i have the cx10 selected and try to change models it hangs and reboots but if i have other models selected it works fine...when it hangs i have to go to USB mode and change the tx file to different model ...it powers up but if i try to change models it hangs and reboots..

The error dump is garbled. Is that a cut'n'paste artifact, or does it appear that way on the tx?

When you say it reboots when you try to change models, is that when one of the models is the cx10? Can you change between two models that use a non-nRF protocol without a reboot?

It seems to me some communication problem is occurring between the nRF module and the cpu. Just need to pinpoint what it is based on the clues.

Can you try disabling the cyrf module in tx.ini by uncommenting the enable and setting it to 0? If the nRF works standalone then it would be an interference issue.

hexfet wrote: The error dump is garbled. Is that a cut'n'paste artifact, or does it appear that way on the tx?

When you say it reboots when you try to change models, is that when one of the models is the cx10? Can you change between two models that use a non-nRF protocol without a reboot?

It seems to me some communication problem is occurring between the nRF module and the cpu. Just need to pinpoint what it is based on the clues.

Can you try disabling the cyrf module in tx.ini by uncommenting the enable and setting it to 0? If the nRF works standalone then it would be an interference issue.

yes i just copied and pasted the error text file..
it only hangs and reboots when i have the cx10 selected and try to change to a different model...if i have it on one of my other models i can switch between them no problem even select the cx10 but once it is on the cx10 i can't switch from it to another model with out it hanging and rebooting..

yes i will try uncommitting the cyrf module to see how it does..and see if the nrf still works..

When i uncommit the cyrf module and set to 0 , it does the same thing i can select models but once on the cx10 it hangs like before when trying to go to a different model..


Really starting to think i might have got a Lemon tx with all sorts of problems.. when i got it i noticed the THHOLD switch didn't work and checked it and one of the terminals on the switch was completely missed and not soldered from the factory..maybe they missed other things to

The garbled text in the error file seems suspicious. You may be right about more general issues with the tx.

With the standard 4.0.1 release does the tx reset when changing away from the cx10 model? Nothing I changed in the posted version should have affected the resetting behavior.

I don't remember it reseting but not 100% positive cause it was a couple weeks ago when i tried it...i can try it again tonight when i get in from work to be sure..

Loaded up deviation 4.0.1 and it does the same thing i can switch between models no problem but once i select the cx10 model i can't switch to different model with out it hanging and rebooting...