How do I activate head tracking?

[mavic6611]

Hey guys, how do I use head tracking on goggles with the MP?
I tried last night and there was a cross on the screen which moved in conjunction with my head movements but for some reason the camera wasn't moving?
What am I doing wrong here?

 

[gtoews]

what firmwares are you on? my mavic is .700 the goggles are on .0002 I have not been able to get head tracking to work with the RE goggles, worked fine with the original goggles but only when firmwares matched. I'm worried this will be the case here as well.

 

[Clinton1]

I think any firmware lower than .900 on AC will not work with headtracking. I am on .900 for AC and RC, and .1000 on Goggles. Headtracking then works perfect.

 

[gtoews]

Actually I

I think any firmware lower than .900 on AC will not work with headtracking. I am on .900 for AC and RC, and .1000 on Goggles. Headtracking then works perfect.

For the racing edition goggles ?

 

[gtoews]

Actually I

For the racing edition goggles ?

For the record head tracking works fine with everything on .700 but thats with the non re goggles.

 

[Clinton1]

For the record head tracking works fine with everything on .700 but thats with the non re goggles.

Things might have changed, i could be wrong, but when i tried AC on .700 the headtracking didnt work. There was a thread about it, just cant find it now.

 

[mavic6611]

what firmwares are you on? my mavic is .700 the goggles are on .0002 I have not been able to get head tracking to work with the RE goggles, worked fine with the original goggles but only when firmwares matched. I'm worried this will be the case here as well.

I'm using 900 on AC and 1000 on goggles.
I'm sure it's supposed to work with them firmwares.

 

[mavic6611]

I'm using NONE re goggles.

 

[Kilrah]

Did you correctly enable it using the "2 fingers down" menu? If yes then not working is due to the firmware mismatch.

 

[mavic6611]

Did you correctly enable it using the "2 fingers down" menu? If yes then not working is due to the firmware mismatch.

I swiped my 2 fingers down but it wouldn't open the head tracking facility so I clicked on the cog icon and accessed it through settings. there is q white cross in the center of the screen that follows my head movements but the camera stays still for some reason?

 

[Kilrah]

Seems you might be in focusing mode (Fn button), not headtracking. You need to use the 2 fingers down

 

[mavic6611]

Seems you might be in focusing mode (Fn button), not headtracking. You need to use the 2 fingers down

I'll take a look at it tonight [emoji3] thanks mate

 

[gtoews]

I'm using NONE re goggles.

ok, for sure the regular googles work on .700 I 'm trying to understand if the RE goggles will also work. Thanks

 

[mavic6611]

ok, for sure the regular googles work on .700 I 'm trying to understand if the RE goggles will also work. Thanks

I'm not sure myself but if I find out I'll let you know

 

[KostasNK]

If someone finds out about RE Goggles please let me know! I will buy the RE goggles and I don't want to update my mp to a newer firmware than .900...

 

[gtoews]

1.) I traded my V1 DJI goggles for the new RE goggles. The promise of having one premium goggle available for me to enjoy all my FPV aircraft (micro - heavily modded Inductrix, racing quad - Kopis 1 and the Mavic Pro) was irresistible, especially considering my current FPV goggles were crap ($100 Eachine EV100) and I'd be looking to speed $400 on some fatsharks or equivalent. Also the upgrades to functionality of the RE goggles (video playback, DVR and separate Occusync module and camera helped motivate me.

Upon receiving the RE goggles same day I sent my old goggles to my Ebay buyer, I noticed head tracking didn't work. Then it came back to me… Historically the goggles had to be on the same FW rev as the AC (aircraft) for head tracking to work. Gimbal head tracking is a very significant feature. Without support for head tracking, there's no practical use for the IMU built into the google (for me at this time, until I have compatible FC's (flight controllers) and can control 3rd party gimbals etc). There's also that pano-photo feature I suppose would use the goggles IMU, however these are only nice-to-haves at the moment).

2.) For me, 01.03.0700 across the board was the sweet spot, mainly due to the ability to modify parameters via assistant in debug mode. It's critical when you live in the mountains to exceed 500 meter height restrictions. Among many other practical, legitimate, and responsible uses, I employ the Mavic routinely in the backcountry for assessing climbs/routes, cornices, avalanche risk and for determining if water falls are in the condition to ice climb before making multi hour, dangerous approaches with heavy bags of equipment. It's only a matter of time before I'm in the right spot at the right time under the right conditions to provide support searching for lost hikers, back country skiers or climbers. Anyway, it's my equipment, I paid for it, I'll use it as I please and take full responsibility for my actions.

Steps taken to correct issues and concerns:

To enable head tracking, it became clear that I'd have to update to the goggles to 01.00.0100 and the AC and RC to 01.04.0100 (matching subversions I guessed). Of course, this meant potentially giving up the ability to modify flight parameters possible in 01.03.0700 (and other releases).

But there is a way to have it all:

Since I was taking the mega-plunge, I figured I'd also update the DJI Go 4 app after patching of course. (Patching is required to avoid forced updates and all other behind the scenes chattiness between the app and the state.

Preconditions:

1.) RE goggles: version 01.00.0002

2.) Controller, Mavic: version 01.03.0700

3.) DJI Go 4: version 4.1.3 patched and side loaded (Android 7.0 running on Note 5)

Issues that I was aware of:

1.) No head tracking on RE goggles

2.) After android update to 7 (Nougat) DJI Go 4 (4.1.3 patched and side loaded) was no longer able to access flight records, media on the Mavic. Cache images were not available, nor video.

Procedure:

I did some of these things in parallel. I also had two version of DJI assistant running as the DJi Assistant capable of debug mode (1.1.2), thus parameter changes, is not able to connect to later FWs (like the FW the RE goggles ship with (01.00.0002).

1.) Downloaded everything I needed to patch a new Android version of DJI Go 4 (Version 4.1.14)

2.) Followed the procedure to modify the correct version of 4.1.14 (without SecNeo), selected the patches to apply and compiled, cleaned up old version including dir structure, side loaded off USB storage and OTG cable. (I'm sure there are many other ways to side load). Followed directions on how to first run patch DJI Go app.

3.) Meanwhile, prepared my machine (Windows in this case) with the firmware and packages from Git (DUMLdore/DankDroneDownloader/DUMLRacer). I removed modules 305,306 and 905 from the bin file for AC firmware 01.04.0100 (This is the first firmware that has the anti-rollback restriction DJI included to avoid us from using Jeezab's DUMLdore to flash up and down as we choose - yikes that's a scary update but necessary if I'm to match RE goggle FW with AC firmware) Following procedure, I successfully, load 01.04.0100 FW, root the AC and defeat the anti-rollback feature all at once using the most recent release of DUMLdore that integrates Jcase's rooting capabilities (meaning I didn't have to use the standalone DUMLRacer as it was built into DUMLdore).

4.) Next I used DankDroneDownloader as before to download the appropriate FW for the RC and RE Goggles. (01.04.0100 and 01.00.0100 respectively) and used DUMLdore to update/root/defeat rollback on the RC and Goggles.

5.) Using the old DJI Assistant (DJI Assistant 2 1.1.2) I remodified my flight parameters as I want them but haven't tested to verify if they are respected by the new firmware. This is important. You may all want to hold off doing the process I've outlined until hearing back from me.

Problems faced during procedure:

1.) It wasn't always clear to me when the update was done. The DUMLdore package isn't exactly clear on this. It instructs you when it's ok to open DJI Assistant to watch the update in progress. The first time I did it, I went to bed and woke up with a dead battery. Not sure what state I was in, I used both the updated DJI Assistant and the older version with debug capabilities and if I recall, neither were able to detect FW version. Reading the procedure again assured me I could run the firmware update/rooting procedure again without harm, which I did. This time DJI assistant (the older version) showed the progress up 99% (this could be due to the missing 305, 306 modules in the bin file. Regardless, apparently as long as the red lights are on solid, the AC is not upgrading and is done. I connected up the RE googles, the AC and the android app and everything checked out, yes including head tracking, viewing of flight logs, cached video and photos. Before updating, I was also unable to browse the contents of the SD card on the AC via DJI Go app connected to RC, this is corrected now)

Next steps:

1.) If it ever stops raining where I live, day or night I will test the modified flight parameters and if I can get above 500meters I'm a very happy operator. I hope to report back this evening or tonight. Every indication so far is that all will be good.

Huge respect and many thanks to the original gangsters, jessab and jcase and to quad808 for compiling everything together. If these geniuses have helped you out like they've helped me, please consider donating.

 

[gtoews]

If someone finds out about RE Goggles please let me know! I will buy the RE goggles and I don't want to update my mp to a newer firmware than .900...

I've posted a reply in this thread

 

[gtoews]

google quad808, for all details.

 

[gtoews]

1.) I traded my V1 DJI goggles for the new RE goggles. The promise of having one premium goggle available for me to enjoy all my FPV aircraft (micro - heavily modded Inductrix, racing quad - Kopis 1 and the Mavic Pro) was irresistible, especially considering my current FPV goggles were crap ($100 Eachine EV100) and I'd be looking to speed $400 on some fatsharks or equivalent. Also the upgrades to functionality of the RE goggles (video playback, DVR and separate Occusync module and camera helped motivate me.

Upon receiving the RE goggles same day I sent my old goggles to my Ebay buyer, I noticed head tracking didn't work. Then it came back to me… Historically the goggles had to be on the same FW rev as the AC (aircraft) for head tracking to work. Gimbal head tracking is a very significant feature. Without support for head tracking, there's no practical use for the IMU built into the google (for me at this time, until I have compatible FC's (flight controllers) and can control 3rd party gimbals etc). There's also that pano-photo feature I suppose would use the goggles IMU, however these are only nice-to-haves at the moment).

2.) For me, 01.03.0700 across the board was the sweet spot, mainly due to the ability to modify parameters via assistant in debug mode. It's critical when you live in the mountains to exceed 500 meter height restrictions. Among many other practical, legitimate, and responsible uses, I employ the Mavic routinely in the backcountry for assessing climbs/routes, cornices, avalanche risk and for determining if water falls are in the condition to ice climb before making multi hour, dangerous approaches with heavy bags of equipment. It's only a matter of time before I'm in the right spot at the right time under the right conditions to provide support searching for lost hikers, back country skiers or climbers. Anyway, it's my equipment, I paid for it, I'll use it as I please and take full responsibility for my actions.

Steps taken to correct issues and concerns:

To enable head tracking, it became clear that I'd have to update to the goggles to 01.00.0100 and the AC and RC to 01.04.0100 (matching subversions I guessed). Of course, this meant potentially giving up the ability to modify flight parameters possible in 01.03.0700 (and other releases).

But there is a way to have it all:

Since I was taking the mega-plunge, I figured I'd also update the DJI Go 4 app after patching of course. (Patching is required to avoid forced updates and all other behind the scenes chattiness between the app and the state.

Preconditions:

1.) RE goggles: version 01.00.0002

2.) Controller, Mavic: version 01.03.0700

3.) DJI Go 4: version 4.1.3 patched and side loaded (Android 7.0 running on Note 5)

Issues that I was aware of:

1.) No head tracking on RE goggles

2.) After android update to 7 (Nougat) DJI Go 4 (4.1.3 patched and side loaded) was no longer able to access flight records, media on the Mavic. Cache images were not available, nor video.

Procedure:

I did some of these things in parallel. I also had two version of DJI assistant running as the DJi Assistant capable of debug mode (1.1.2), thus parameter changes, is not able to connect to later FWs (like the FW the RE goggles ship with (01.00.0002).

1.) Downloaded everything I needed to patch a new Android version of DJI Go 4 (Version 4.1.14)

2.) Followed the procedure to modify the correct version of 4.1.14 (without SecNeo), selected the patches to apply and compiled, cleaned up old version including dir structure, side loaded off USB storage and OTG cable. (I'm sure there are many other ways to side load). Followed directions on how to first run patch DJI Go app.

3.) Meanwhile, prepared my machine (Windows in this case) with the firmware and packages from Git (DUMLdore/DankDroneDownloader/DUMLRacer). I removed modules 305,306 and 905 from the bin file for AC firmware 01.04.0100 (This is the first firmware that has the anti-rollback restriction DJI included to avoid us from using Jeezab's DUMLdore to flash up and down as we choose - yikes that's a scary update but necessary if I'm to match RE goggle FW with AC firmware) Following procedure, I successfully, load 01.04.0100 FW, root the AC and defeat the anti-rollback feature all at once using the most recent release of DUMLdore that integrates Jcase's rooting capabilities (meaning I didn't have to use the standalone DUMLRacer as it was built into DUMLdore).

4.) Next I used DankDroneDownloader as before to download the appropriate FW for the RC and RE Goggles. (01.04.0100 and 01.00.0100 respectively) and used DUMLdore to update/root/defeat rollback on the RC and Goggles.

5.) Using the old DJI Assistant (DJI Assistant 2 1.1.2) I remodified my flight parameters as I want them but haven't tested to verify if they are respected by the new firmware. This is important. You may all want to hold off doing the process I've outlined until hearing back from me.

Problems faced during procedure:

1.) It wasn't always clear to me when the update was done. The DUMLdore package isn't exactly clear on this. It instructs you when it's ok to open DJI Assistant to watch the update in progress. The first time I did it, I went to bed and woke up with a dead battery. Not sure what state I was in, I used both the updated DJI Assistant and the older version with debug capabilities and if I recall, neither were able to detect FW version. Reading the procedure again assured me I could run the firmware update/rooting procedure again without harm, which I did. This time DJI assistant (the older version) showed the progress up 99% (this could be due to the missing 305, 306 modules in the bin file. Regardless, apparently as long as the red lights are on solid, the AC is not upgrading and is done. I connected up the RE googles, the AC and the android app and everything checked out, yes including head tracking, viewing of flight logs, cached video and photos. Before updating, I was also unable to browse the contents of the SD card on the AC via DJI Go app connected to RC, this is corrected now)

Next steps:

1.) If it ever stops raining where I live, day or night I will test the modified flight parameters and if I can get above 500meters I'm a very happy operator. I hope to report back this evening or tonight. Every indication so far is that all will be good.

Huge respect and many thanks to the original gangsters, jessab and jcase and to quad808 for compiling everything together. If these geniuses have helped you out like they've helped me, please consider donating.

Yes! Everything works! All previous flight
params are able to be set again. What we have here is a fully owned mavic that's runnning almost the latest release. 01.04.0100

The app was rock solid, max speed observed at 20m/s, I brought it up to over 622m tried a precision RTH and it was off by about 1.5 meters and not oriented with the same heading as launch. This is a known issue. I never saw a single warning about NFZ although it impossible to not be in one where i live. I did not get a chance to test any optical intelligent flight modes due to low ambient light, aka night time. I know the collision avoidance system work because i tested indoors with motors running. Was able to calibrate vps, imu and compass. Ultra sonic landing range finding also works.

Very excited logs back as well. I can now see my track on map after flight with warnings, stats and stick movements. Can access images and cached video. Will update yu here if i find anything that makes me regret the procedure. One thing to note, i have not tested rolling back. I can't imagine why I'd want to anyway.

I noticed that the right wheel on the rc behaves differently, before it seemed to control camera exposure regardless of camera mode or whether recording or not. Now it's different, can't explain it at the moment but i believe this has also been covered on this forum or elsewhere.

Good luck!

 

[KostasNK]

Yesterday I bought the RE dji goggles and head tracking works with the .900 firmware version on the mavic...