Hooking up Logic Analyzer ....Help please

Gonna try rolling back to older firmware to see if it works..if not i will hook up the analyzer again and see if i can figure out anything but i have no idea how ti use that thing..so not sure what to look for or how to go about getting results that show something wrong.

Then you will have to learn it....

I think you do too much steps at once. First check it with that version.
If you have no success you may change back.
Hook up CSN and set the samplefrequence to 1 or 2 Mhz to see if a signal is present.Sample a bigger file.

Edit:
downloads.saleae.com/Logic+Guide.pdf
or

OMG!!! it works when using Deviation 4.0.1 so its something in the nightly builds that is causing not to work...Bad thing is if i don't run the nightly i can't fly my models with ether tx without having to re-bind them each time...with the nightly i just pick up ether tx and turn it on and fly..

I think you messed it up with your file copy action from Devo 8 to 12....

So i will try reinstalling the nightly and just changing the tx ID to match the 8 and see if it works without copying any files from the 8 ...the only files i will copy is the model file i have saved for the 12

but i honestly think it wont work cause i tried it before i copied the hardware file from the 8 and it didn't work but will see...fingers crossed..

Something in the nightly builds cause soon as i put it back i get the same issue...missing module didn't copy the hardware file from the 8 just enabled the modules and it powers up but i have the *in front of the protocals ..it works on the stock deviation 4.0.1 firmware...not sure why it wont work on the 12 but it has to be in the nightly builds firmware...

Any chance there's a good tutorial/instruction/examples for logic analyzers on the net somewhere? I've got mine, and two or three projects that it would be useful for, but also no idea how to use it.

hooking it up is not to bad its the settings and what to look for when its hooked up..just shows a bunch of squiggly lines ect...

I believe you. That's why I'd really like a tutorial, showing how to hook it up to some microcontroller, adjust the settings to make the signals easily visible, and then how to interpret them. I'm hoping someone knows of such, because my Google fu wasn't strong enough to find one.

i am going to hook mine up again to my 12 and see if i can figure out why the NRF module is not working but its going to be a steep curve to figure it out...first time i hooked it uo i didn't have the settings correct and couldn't figure anything out ...least this time i have the test clips to hook it up with..

magic_marty wrote: i am going to hook mine up again to my 12 and see if i can figure out why the NRF module is not working but its going to be a steep curve to figure it out...first time i hooked it uo i didn't have the settings correct and couldn't figure anything out ...least this time i have the test clips to hook it up with..

... can´t be that hard..
Choose 10M Sample, 2 or 4 Mhz, on the right side choose analyzer "SPI".
Let it be renamed, hook the lines(clips) according to the signal names and give it a go,.....save the dump. If you are wrong with the naming, it could be altered afterwards.

The main signal you should be looking for, is the "CSN". The rest does not care at the moment.

The best way would be to start on the Devo8 and do a protocol change or model change. Then you have an example how it should look like.

Edit: By clicking into the screen with left/right mouse button you change the
timebase for better view.

how is it saved? it just ask to save as screen shot..

Save session or export data.To save the session the best way as you can always reload it to compare.

ok got it hooked to the 8 and going to try this again

devo8 export files nrf and devo protocol

devo12 export files ...

devo12 tx with the devo protocol and 12ch rx

i have no idea what to look for with these exports?? thats why i posted them here..maybe somebody can see something wrong..

Please stop flooding the topic with useless binary files.

A session file would be nice or at least exported as CSV file, which is a text file.

Example:
Power on of a WLToy A7105 tx. The first signal(obove) is that what we seach on your installation.

nobody never said what type of file to save them as...i only have .bin on the 12 but have a cvs on the 8