Search results

Carapau, can you list what you can see from the logs as I have tried to get data via the Mk2 and 2.3 but see no data at all - even though the log file is indeed 9mb...

I have never had an issue with S-Bus and used in many multi's and fixed wing in various climates - some extreme.

8FG (S update) :/ Ouch snap. Yes, would not fly without it but I checked logs and could not see any data even though the file was big... To mitigate this - are you guys now using a separate Rx (S-BUS)?

Have put another 5 flights on the S800 Evo and A2 on 2.3 All fine apart from a hickup on the last. Seemed to loose all input while flying fast forward, did not see any sat drop - system was seeing 14 at the time. Was flying in AttiGps and flicking to manual did not give me back control but...

Same here with FW2.3 not sure though if that should make any difference.

Seeing a speed when the airframe is static can be explained if the GPS is acquiring other fix's (getting a more accurate pos), I have seen this before with other systems - not looked at your vid yet but it could be this.

As I said, Droider, its mitigation...

Droider, my systems are commercial, predictable to a degree but that does not stop one planning for the worst case scenario and mitigating any risk. Again I agree that Hot glue may not be the best in this case, ultimately proper latching plug and socket but we do not have this where we need it...

I understand your feeling but mitigation is the No.1 rule, if you can secure something further then do it. I agree that DJI should use a better connector but that's what we have to work with at the moment...

Crazy day, everything broke! Setting up old firmware (5.20) today bricked our WKM - back to china it goes... (was on our S800 Evo)... Decided to give the A2 another few packs on the HT450 on 2.3 before putting back into the Evo, got to the field and it was giving an error, needed to be...

Another thumbs up for BYOD - they tried to convince me not to get A2 for obvious reasons but were happy that I was getting it to test it to bits.

Interesting, on the wiki, it does not state for the wookong but for the A2 it does state nose down! http://wiki.dji.com/en/index.php/WooKong-M_GPS_%26_Compass_Calibration http://wiki.dji.com/en/index.php/A2_Compass_Calibration

Oh wow, nose down. I have always done this by dropping over the multi to the right hand side, never nose down. I'm going to check the A2 calib to as I'm sure that was also to the side on the second step of the dance. Good spot.

If your addressing my issues Carapau, this unfortunately was on 2.3.

So, I was puzzled about this last night after setting up my a2 on a test quad with 2.3. I have not followed or even read the links posted thus far, mainly as I wanted to go by the book to see the outcome. Firstly, turning off the Tx showed no 'rc lost' or other indicators. Could not find...

Great news Oleg, watching with great interest!

Snap, about 25 flights in with 5.26 - no issues, I skipped 5.24...

Morning all, I should receive a new A2 on Monday so will be out testing for the following few days, will post my results too for all, Black box at the ready. Could someone who has had issues let me know if any issue was seen flying just on Atti or manual, please mention which ver. you had...

Yes I understand that - I use the T,R as F1/F2 are used in octo config. I still need to map Tx to Wookong to control F1

Thanks, but how do you assign a Tx control to F1 or do you have to do this via the GS only?