Good day,
I have an issue I have been trying to resolve for a couple of days. I recently got a solo with no knowledge of the firmware or Arducopter version on it as the owner had no interest.
During the setup I used the SSH method and all was successful as far as I know; I flashed the solo and controller, reconnected them, installed open solo 4 on both of them as per the open solo 4 git page only as well as the necessary step to make sure any future flashes restores the default opensolo 4 firmware and then I installed Arducopter 4 on the device as per the Arducopter open solo GitHub page as well using the master for the black cube. Those are the only things I have done in the respective order
It was after I realised that Arducopter had to have been installed with the single file before flashing opensolo 4. Despite this, I went ahead to connect the device to my computer via solo wifi as usual and attempted to connect to mission planner but MP does not recognize the device. I connect first then open MP, and have tried opening MP before connecting but this issue has persisted.
Is anyone aware of this issue, please what are your recommendations for fixes, my idea to fix it is as below, please advice me if it is the right step.
- Figure out how to reflash the solo and controller to default 3dr firmware
- reinstall Arducopter 4 first via the very simple SSH method in the GitHub
- reinstall opensolo 4 via the SSH method as well.
I am aware of a the method to connect the black cube directly via USB to the computer to be read by mission planner but that step shows the green cube on all the pages so I am frightened it will not work with the black cube or the files has changed since then. If this is the necessary step, please let me know as well as advice on the steps for the black cube.
The SSH is my preferred method.
I appreciate your response, thank you
Also if this has been previously solved, I apologize for the repetition.
I have an issue I have been trying to resolve for a couple of days. I recently got a solo with no knowledge of the firmware or Arducopter version on it as the owner had no interest.
During the setup I used the SSH method and all was successful as far as I know; I flashed the solo and controller, reconnected them, installed open solo 4 on both of them as per the open solo 4 git page only as well as the necessary step to make sure any future flashes restores the default opensolo 4 firmware and then I installed Arducopter 4 on the device as per the Arducopter open solo GitHub page as well using the master for the black cube. Those are the only things I have done in the respective order
It was after I realised that Arducopter had to have been installed with the single file before flashing opensolo 4. Despite this, I went ahead to connect the device to my computer via solo wifi as usual and attempted to connect to mission planner but MP does not recognize the device. I connect first then open MP, and have tried opening MP before connecting but this issue has persisted.
Is anyone aware of this issue, please what are your recommendations for fixes, my idea to fix it is as below, please advice me if it is the right step.
- Figure out how to reflash the solo and controller to default 3dr firmware
- reinstall Arducopter 4 first via the very simple SSH method in the GitHub
- reinstall opensolo 4 via the SSH method as well.
I am aware of a the method to connect the black cube directly via USB to the computer to be read by mission planner but that step shows the green cube on all the pages so I am frightened it will not work with the black cube or the files has changed since then. If this is the necessary step, please let me know as well as advice on the steps for the black cube.
The SSH is my preferred method.
I appreciate your response, thank you
Also if this has been previously solved, I apologize for the repetition.
