I conveyed most of the accusation messages to the developer who is currently out of town for business trip. Per his preliminary feedback, DCI probably disassembled the shell scripts/commands. Other coding does NOT go through shell script.
DCI further claimed the same accusation to P2V Booster (non-Plus). He disassembled 3 lines of shell scripts/commands, BUT definitely missed the majority part of coding WITHOUT going through shell script. I’m not the developer, I don’t know which part of coding missed.
dci said:
Update on the booster for vision (non-plus):
- App shares a lot of code with v+ and uses the very same concept, but now it also changes tx power on the repeater.
- Phantom-side binary is now called 'fpvmonitor'. It's the same 'fpvbooster' from v+, it has the same size and checksum, but now its second (tx power) invocation parameter is set to 20 in the phone-side app.
- Repeater-side binary is called 'fpvbooster'. It's a brand new binary that just executes a batch of console commands and exits. That's all. Commands are also encrypted with the same lame code shift, they are:
Code:
iw reg set BO
iw phy phy0 set txpower fixed 2000
iw phy phy0 set distance 1000
However, I’m forced to PROVE such accusation WRONG though I’m sick for several days. I decided to do a simple field test with DCI scripts and P2V booster at 640x480 15fps and ~60m altitude. I recorded a video of my Nexus 7 screen as a proof to share with you all.
Test1: I flew complete stock P2V and RE500 repeater without booster nor DCI scripts as a reference. It reached 225m and showed Phantom Connection Broken.
Test2 (start from 3:30): I pulled back P2V and ran the DCI disassembled scripts in the air. I flew again along the same path. It reached 190m and showed Phantom Connection Broken.
Test3 (start from 5:45): I pulled back P2V within 100m and BOOST it with P2V booster app in the air. I flew again along the same path all the way to 400m with smooth FPV. I can fly farther, but that’s not the point. It’s good enough for the test as a proof.
[youtube]http://www.youtube.com/watch?v=PFkV18ptosE[/youtube]
Obviously, those 3 lines of shell scripts alone had no effect at all (or even worse in this test case) to boost FPV range. This simply implies DCI disassembled scripts is WRONG or at least INCOMPLETE, which is probably a small part of the booster coding. I can guarantee such 3 lines of script is unable to boost 100% FPV range on P2V/RE500.
I think any of P2V pilot can easily test/prove this by running such 3 lines script on RE500 repeater as I did in the field test. I don’t believe running such 3 lines script can boost any significant FPV range. Again, I’m not the developer. That’s all I can do to test and prove at my best knowledge though my knowledge may be insufficient or something I’m incapable to explain, but I'm not lying.
I’m still **** sick thus unable to post in the next several days. I leave it to you guys to test and judge yourselves, what is right or wrong, who is discrediting.