- Posts: 610
HontaiTec Quadcopters (HT F801, HT F803,...)
12 Jun 2015 22:43 #33969
by Durete
Replied by Durete on topic HontaiTec Quadcopters (HT F801, HT F803,...)
Hi Guys. Sorry for my late reply, too much family job today 
I started to capture from the receiver, using my stock TX.
Here the captures:
dl.dropboxusercontent.com/u/14941708/RX%...res%20Stock%20TX.zip
I didn't capture trims because I have some problems with the motors since the full quadcopter is disassembly. Hexfet, if you need the trim captures, let me know and I will desolder the motors to capture. No problem.
I will try to capture using the Devo ASAP.
@Greenfly, everytime I update the build I overwrite my Dropbox's file with the new one. So maybe when you tried to use another previous build, if you don't have saved locally and simply click at my link, you are downloading always the last version. That could be the reason you can't bind using "my previous" build, really you are trying with the last version always.
I started to capture from the receiver, using my stock TX.
Here the captures:
dl.dropboxusercontent.com/u/14941708/RX%...res%20Stock%20TX.zip
I didn't capture trims because I have some problems with the motors since the full quadcopter is disassembly. Hexfet, if you need the trim captures, let me know and I will desolder the motors to capture. No problem.
I will try to capture using the Devo ASAP.
@Greenfly, everytime I update the build I overwrite my Dropbox's file with the new one. So maybe when you tried to use another previous build, if you don't have saved locally and simply click at my link, you are downloading always the last version. That could be the reason you can't bind using "my previous" build, really you are trying with the last version always.
12 Jun 2015 23:01 #33971
by Durete
Sorry
Please, try with our captured TX id as Fixed Id (61956 and 31242). I have not any problem binding with my Devo using this 2 Fixed Id's.
Remember to reset quadcopter and TX every time you change your fixed Id. I have some problems to bind if not restart both.
I need to start to test fixed id's ...
Replied by Durete on topic HontaiTec Quadcopters (HT F801, HT F803,...)
SorryPlease, try with our captured TX id as Fixed Id (61956 and 31242). I have not any problem binding with my Devo using this 2 Fixed Id's.
Remember to reset quadcopter and TX every time you change your fixed Id. I have some problems to bind if not restart both.
I need to start to test fixed id's ...
12 Jun 2015 23:45 #33974
by Durete
Replied by Durete on topic HontaiTec Quadcopters (HT F801, HT F803,...)
Yep, you are right. Probably I tested bad, not cycling power at TX or something similar
I can only bind with my TX id. using 61956 as Fixed Id.
I can only bind with my TX id. using 61956 as Fixed Id.
13 Jun 2015 01:56 - 13 Jun 2015 01:58 #33982
by hexfet
Replied by hexfet on topic HontaiTec Quadcopters (HT F801, HT F803,...)
Try a capture or two at 8MHz please. It's possible 4MHz is just at twice the freq, which is not quite enough
The SPI parameters are correct or we wouldn't get so much good data. Inspecting the SPI data onscreen might show a missed clock pulse or something. Best way I've found to correlate the export file to screen display is by timestamp. Search the decoded (--full) txt file for RX_PAYLOAD and 40 16 on the same line (that's a shifted packet) and look for that timestamp onscreen.
The bind packets I've looked at have all been un-shifted, so we can collect some bind data. I'm out tomorrow so here's what to look for. I'll use greenfly's 05-devo-bind-fail.txt file as an example.
1) Starting from the top search for RX_PAYLOAD. This is reception of the bind packet. The fifth and sixth miso bytes (right of arrow) should be the fixed id set in deviation.
2) Search down from there for RX_ADDR_P0, then again because the first match seems like a programming error. The next match should have six mosi bytes - the last five are the rx/tx address.
3) Search down from there for RX_CH. The value after 25 is the channel being set.
4) Keep searching for RF_CH until the channel sequence repeats. So far it's been 5, 0x19, 0x28.
The RX enters data phase after 2 so we can see the channel sequence, but it goes into bind again if it doesn't receive any data packets (which doesn't happen till the tx stops sending them). So it binds a bunch of times each power-up.
You might start with the stock tx and see if it randomizes the txid each time - greenfly's captured both 7a0a and 7a14 as the last bytes. Easier than changing the fixed id every test. Hopefully a pattern will emerge quickly
The SPI parameters are correct or we wouldn't get so much good data. Inspecting the SPI data onscreen might show a missed clock pulse or something. Best way I've found to correlate the export file to screen display is by timestamp. Search the decoded (--full) txt file for RX_PAYLOAD and 40 16 on the same line (that's a shifted packet) and look for that timestamp onscreen.
The bind packets I've looked at have all been un-shifted, so we can collect some bind data. I'm out tomorrow so here's what to look for. I'll use greenfly's 05-devo-bind-fail.txt file as an example.
1) Starting from the top search for RX_PAYLOAD. This is reception of the bind packet. The fifth and sixth miso bytes (right of arrow) should be the fixed id set in deviation.
2) Search down from there for RX_ADDR_P0, then again because the first match seems like a programming error. The next match should have six mosi bytes - the last five are the rx/tx address.
3) Search down from there for RX_CH. The value after 25 is the channel being set.
4) Keep searching for RF_CH until the channel sequence repeats. So far it's been 5, 0x19, 0x28.
The RX enters data phase after 2 so we can see the channel sequence, but it goes into bind again if it doesn't receive any data packets (which doesn't happen till the tx stops sending them). So it binds a bunch of times each power-up.
You might start with the stock tx and see if it randomizes the txid each time - greenfly's captured both 7a0a and 7a14 as the last bytes. Easier than changing the fixed id every test. Hopefully a pattern will emerge quickly
2.190433 > RX_PAYLOAD 61 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 => 42 4c 4b 3a 7a 0a 00 00 00 4f 07 25 6a 80 0a c0 91
2.190541 > RX_ADDR_P0 2a 55 65 92 4a => 4e 00 00 00 00
2.190573 > EN_RXADDR 22 01 => 4e 00
2.190586 = FLUSH_RX e2 => 4e
2.190594 > STATUS 27 70 => 4e 00
2.190606 = SETUP_RETR e4 => 0c
2.190618 > STATUS 27 42 => 0e 00
2.190632 > RX_ADDR_P0 2a 54 b2 c9 25 24 => 0e 00 00 00 00 00
2.190664 > EN_RXADDR 22 => 0e
2.190676 > RF_CH 25 19 => 0e 00
13 Jun 2015 07:21 #33993
by greenfly
Replied by greenfly on topic HontaiTec Quadcopters (HT F801, HT F803,...)
Well, I might not understand what it all means, but you have done a great job explaining what I need to do. Thanks!
I will get started in the morning and post my results as I find them.
I guess the quad is on the operating table for the duration... oh well at least I have a few others I can fly.
Maybe I will find a way to bring the five lines out such that I can still re-assemble it. Like giving my quad a DIY debug port!
I will get started in the morning and post my results as I find them.
I guess the quad is on the operating table for the duration... oh well at least I have a few others I can fly.
Maybe I will find a way to bring the five lines out such that I can still re-assemble it. Like giving my quad a DIY debug port!
13 Jun 2015 16:11 #34020
by Durete
Replied by Durete on topic HontaiTec Quadcopters (HT F801, HT F803,...)
Hi guys.
Since I'm working with windows, I can't find where is the interpreted CSV SPI file (stdout ? ).
The perl script appears to be working, but the GNU windows is very small to look for anything. I suppose this output will print to any txt file or something similar.
Sorry for this noob question
Since I'm working with windows, I can't find where is the interpreted CSV SPI file (stdout ? ).
The perl script appears to be working, but the GNU windows is very small to look for anything. I suppose this output will print to any txt file or something similar.
Sorry for this noob question
13 Jun 2015 16:39 #34022
by Durete
Replied by Durete on topic HontaiTec Quadcopters (HT F801, HT F803,...)
Thanks !!!! 
14 Jun 2015 00:40 #34035
by hexfet
The 7A14 bind address must've been a capture anomaly - 0x14 is 0x0a shifted left one bit.
Have you made any captures with the devo fixed id? Maybe one start at 0 and the other at 256, and just increment by one each time. It's tedious so stop before it becomes too aggravating I'm hopeful they've done something very simple, but usually it's necessary to build a test jig to automate these captures. We'll see.
Replied by hexfet on topic HontaiTec Quadcopters (HT F801, HT F803,...)
Excellent. And looks like y'all have the hang of getting the bind informationDurete wrote: My captures at 16mhz don't show this programming error. I can see always 6 mosi bytes with the same address.
The 7A14 bind address must've been a capture anomaly - 0x14 is 0x0a shifted left one bit.Have you made any captures with the devo fixed id? Maybe one start at 0 and the other at 256, and just increment by one each time. It's tedious so stop before it becomes too aggravating
I'm hopeful they've done something very simple, but usually it's necessary to build a test jig to automate these captures. We'll see.
Time to create page: 0.495 seconds
-
Home
-
Forum
-
Development
-
Protocol Development
- HontaiTec Quadcopters (HT F801, HT F803,...)