- Joined
- Oct 19, 2015
- Messages
- 27
- Reaction score
- 3
- Age
- 56
- Location
- Swansea, south Wales, United Kingdom
I think I've made a silly newbie mistake!
Text below is from the email I sent 3dr support. Given what I've read in forums about how long they take to reply I thought I'd post a cry for help here too.
"I have a Solo (serial number: S111A5700766) and gimbal purchased from SLR Hut on/around 4th October, 2015. I ran the first use software updates and fitted the gimbal with no problems. The unit has around 3 hours flight time with no problems.
Today (24th October) the unit flew for around 20 minutes and it was brought in for a battery change. The Solo was restarted but would not connect to the controller (controller message "Waiting for Solo") or Solo App on a Sony Z4 (message" Vehicle not detected"). The Sony tablet connected to the Solo WiFi network. The gimbal still worked and stabilised the camera.
I restarted the controller, Solo and Sony tablet a number of times with no improvement. When holding the Solo I could feel a faint vibration. As this was likely to be the gimbal I removed the gimbal and restarted the system with no change. I refitted the gimbal (no change) and returned home.
At home I tried restarting the system a number of times, pressing the "Pair" button on the Solo and removed the gimbal with no change. When trying to pair the devices I noticed a solid amber LED visible through one of the accessory bay screw holes. Looking through the forums I found instructions on resetting the controller. I followed the instructions and completed the controller reset. However the controller displays the "Preflight update" message, which cannot be completed. It looks like that the Preflight update will not complete due to not being able to connect to the Solo.
Please send me info on how to get the Solo to connect so I can complete the Preflight update and get the system flying asap.
Please note that I am using the Solo as a proof of concept platform for the use of RPAS in mountain search and rescue in the UK. I have a demonstration scheduled for Sunday (1st November) and need this resolved and the Solo flying by Saturday.
Please note that I have Tower on the Sony Z4 tablet. I am new to the software and was looking through the settings this afternoon. I changed the Telemetry Link Speed setting to 115200. This may have been while the Solo and controller were powered up.
Is it possible that the new rate was transferred to the Solo and took effect when it was powered up with the fresh battery. With the new speed on the Solo not matching the controller it may be possible they cannot connect.
Is there a way to reset the Solo and correct the rate?"
I have followed 3dr's instructions for the factory reset but don't get the flashing amber LED and it won't repair the controller and Solo.
Any suggestions?
Text below is from the email I sent 3dr support. Given what I've read in forums about how long they take to reply I thought I'd post a cry for help here too.
"I have a Solo (serial number: S111A5700766) and gimbal purchased from SLR Hut on/around 4th October, 2015. I ran the first use software updates and fitted the gimbal with no problems. The unit has around 3 hours flight time with no problems.
Today (24th October) the unit flew for around 20 minutes and it was brought in for a battery change. The Solo was restarted but would not connect to the controller (controller message "Waiting for Solo") or Solo App on a Sony Z4 (message" Vehicle not detected"). The Sony tablet connected to the Solo WiFi network. The gimbal still worked and stabilised the camera.
I restarted the controller, Solo and Sony tablet a number of times with no improvement. When holding the Solo I could feel a faint vibration. As this was likely to be the gimbal I removed the gimbal and restarted the system with no change. I refitted the gimbal (no change) and returned home.
At home I tried restarting the system a number of times, pressing the "Pair" button on the Solo and removed the gimbal with no change. When trying to pair the devices I noticed a solid amber LED visible through one of the accessory bay screw holes. Looking through the forums I found instructions on resetting the controller. I followed the instructions and completed the controller reset. However the controller displays the "Preflight update" message, which cannot be completed. It looks like that the Preflight update will not complete due to not being able to connect to the Solo.
Please send me info on how to get the Solo to connect so I can complete the Preflight update and get the system flying asap.
Please note that I am using the Solo as a proof of concept platform for the use of RPAS in mountain search and rescue in the UK. I have a demonstration scheduled for Sunday (1st November) and need this resolved and the Solo flying by Saturday.
Please note that I have Tower on the Sony Z4 tablet. I am new to the software and was looking through the settings this afternoon. I changed the Telemetry Link Speed setting to 115200. This may have been while the Solo and controller were powered up.
Is it possible that the new rate was transferred to the Solo and took effect when it was powered up with the fresh battery. With the new speed on the Solo not matching the controller it may be possible they cannot connect.
Is there a way to reset the Solo and correct the rate?"
I have followed 3dr's instructions for the factory reset but don't get the flashing amber LED and it won't repair the controller and Solo.
Any suggestions?