Logic Analyzer SPI Capture for PROPEL 74-z

Thanks, the videos are helpful.

Test build ( aad6669 ) is updated. Didn't find much when I went back through the captures. Main change is to add some debug info as telemetry values. If it still sticks on the bind screen, please click ENT and navigate to the Telemetry monitor screen. Video's probably the best way to show what's happening there.

Stopping at the bind dialog means the tx is not receiving any data from the quad. One thing to try would be to move the transmitter away from the quad at least a couple of meters. Also use the lowest tx power setting (re-init after changing power).

The test build aad6669 doesn't work.Later, I uploaded video.I'm going to re-weld the bk2425 and recapture the data.I think there might be a welding error or a short circuit.

Test build aad6669 can't open Telemetry screen.
Propel protocol no telemetry submenu.

Ich habe heute abend jetzt auch die Propel Version aad6669 auf meinem Jumper T8SG installiert.
Leider konnte ich meinen Propel Speederbike nicht mit meinem Jumper binden.
Ein Telemetrie Bildschirm wird auch bei mir nicht angezeigt.


I also installed the Propel version aad6669 on my T8SG jumper tonight.
Unfortunately I could not tie my Propel Speederbike with my jumper.
A telemetry screen is not displayed even with me.

That's strange. It's working the in the 7E emulator. No protocol option necessary.

Please try downloading from this link . I rebuilt the firmware (same version number) in case I made some error in the build process before.

Wo finde ich denn den 7E Emulator im Jumper T8SG??

Oder habe ich da etwas falsch verstanden???


Where can I find the 7E emulator in the jumper T8SG ??

Or have I misunderstood something???

Please test the t8sg build at the latest link above. Just tested on my t8sg plus and the telemetry is there. If you can please upload a video somewhere and post a link.

I don't have a 7e so just tested with an emulator build. Those are not uploaded.

aad6669 video:
www.mediafire.com/download/d1tfl851fujxcjt

Thanks. The video confirms no data is received from the quad. Have you tried with a couple meters separation between tx and quad, and reduced power setting?

hexfet wrote: Thanks. The video confirms no data is received from the quad. Have you tried with a couple meters separation between tx and quad, and reduced power setting?

Yes, I use 1mw and with a couple meters separation between tx and quad ，the same .

Re-weld Capture1（1Tsamples-24Mhz）:https://www.mediafire.com/download/hn2nnltn7othp78

Thanks. The bind sequences in this capture are all the same, but slightly different than the previous two captures.

Test build is updated ( abc5dcf ). No major change but a couple of tweaks. Trying to figure out which bits are important and which are not.

hexfet wrote: Thanks. The bind sequences in this capture are all the same, but slightly different than the previous two captures.

Test build is updated ( abc5dcf ). No major change but a couple of tweaks. Trying to figure out which bits are important and which are not.

abc5dcf doesn't work,video like aad6669.

Ich habe jetzt auch die Version abc5dcf auf meinem Jumper T8SG installiert.
Leider wird dort keine Telemetrie angezeigt und den Speederbike konnte ich leider nicht binden.

Test build is updated ( 9569a90 ). This version removes the dependence on auto acknowledgement. Some clone nRF chips are known to have a problem with AA, though I haven't seen it with Beken before. About out of things to try.

This version will try to bind (sync) for 5 seconds, then jump to data mode. Not sure how the quad will react to this, if at all. Try a few different variations - power on quad first, power on tx first, simultaneously...

hexfet wrote: Test build is updated ( 9569a90 ). This version removes the dependence on auto acknowledgement. Some clone nRF chips are known to have a problem with AA, though I haven't seen it with Beken before. About out of things to try.

This version will try to bind (sync) for 5 seconds, then jump to data mode. Not sure how the quad will react to this, if at all. Try a few different variations - power on quad first, power on tx first, simultaneously...

Test Video 9569a90:https://www.mediafire.com/download/b9bcupapq3w5kq3

power on quad first, power on tx first,the same,It doesn't work.

Ich habe hexfet seine Anleitung heute abend auch mal durch probiert.
Leider konnte ich den Speederbike mit meinem Jumper und der Version 9569a90 nicht binden.

I also tried hexfet his instructions tonight.
Unfortunately, I could not tie the Speederbike with my jumper and version 9569a90.

Often a difficult to find problem will turn out to be something simple, but I haven't been able to find anything. Test build is updated ( 105c9fb ) with a protocol option to change whether auto-ack is used or not, and a couple minor timing changes. Don't really expect any different behavior.

Likely the only way forward will be to get some captures from the receiver. It may not be possible depending on the receiver hardware, but if it can be done we'd need 3 captures. One binding with the stock tx, then trying to bind with deviation with the protocol option set both on and off.

hexfet wrote: Often a difficult to find problem will turn out to be something simple, but I haven't been able to find anything. Test build is updated ( 105c9fb ) with a protocol option to change whether auto-ack is used or not, and a couple minor timing changes. Don't really expect any different behavior.

Likely the only way forward will be to get some captures from the receiver. It may not be possible depending on the receiver hardware, but if it can be done we'd need 3 captures. One binding with the stock tx, then trying to bind with deviation with the protocol option set both on and off.

Ok, I will capture the data in the next few weeks, the chip is too small, a little difficult.