Required files to download to Solex

Joined
Mar 17, 2017
Messages
88
Reaction score
1
Age
58
When I'm in Solex I can download all the files I need to update my Solo...except the MIX Python files.zip
Can anyone tell me why...have they been integrated into one of the Arducopter 3.5.x firmware.zip files ?

No one seems to have a clear,updated,firmware update package for the Green cube.
 

Matt,
Build#1 via Solex
I loaded the Green Cube with Jesters video instructions:
Load IMX file to original cube
Install green cube
Load arducopter 3.52
Load arducopter 3.52 parameter file
Load Here Gnss parameter file.

Given your current instructions where does that leave me, a completed install or not? The controller was never updated in this install instructions.

Different build #2
If I want to run Arducopter on an original cube with new ESC's should I just do it all manually? Your install will not allow options for this configuration?]

Thanks for working so hard on this project.
 
Last edited:
The old procedures and Jester's video were from before open solo existed. So older installs that followed the older procedure are still fine. You can install open solo on that one too if you want.

For new green cube installs, open solo is now part of that procedure, and that's what these new instructions are for.

If you want to run ArduCopter versions other than what is included with Open Solo, you can still do it. The procedure for loading whatever PX4 file you want is unchanged. I haven't removed that or locked you into what I include.
 
So it seems that the controller or the IMX6 brd on the Solo have a firmware copy that is used during a "factory reset" to restore the firmware to default. You have included in your new procedure a routine to replace that firmware image with a new version of Arducopter.
So to get in sync with your new Open Solo install I assume I need to follow from reinstalling the original cube etc?

Sorry still getting used to the three computers in the Solo system and whats where.
 
For your solo that has a working green cube, just do the full open solo installation procedure. You do not need to remove the green cube.

For a new green cube install, open solo must be installed and working with the stock cube before installing the new green cube.
 
For your solo that has a working green cube, just do the full open solo installation procedure. You do not need to remove the green cube.

For a new green cube install, open solo must be installed and working with the stock cube before installing the new green cube.

I did this...and still can't fully update my firmware.
 
Should I have downloaded open Solo to my controller first..or can that be done anytime in the process ?[/QUOTEt]

I think we keep crossing posts... I may be able to help, but need to know exactly where you're at...

Step by step.what did you do?

I took my factory restored bird, updated it via the Solo App to Solo Version 2.4.2 ArduCopter 1.3.1, which is the last release of the production 3DR code.

I then used Solex to download OpenSolo packages and then install them.

Then Rebooted both and have a working system of OpenSolo.

This is where you need to be before installing the green cude.

So to unwind, I think even someone with more knowledge than a noob like me would need to know what steps you took and the current state of your whole system.
 
Last edited:
Well..before I installed the green cube, I installed open Solo on the old cube ( I did not install open solo on the controller although),rebooted solo and was then was able to install the Arducopter firmware from the Solex firmware files I was able to download, rebooted Solo and since then I haunt been able to download any other firmware from Solex, and my controller won't connect to Solo either.

Have I ruined my Solo ?
 
Well..before I installed the green cube, I installed open Solo on the old cube ( I did not install open solo on the controller although),rebooted solo and was then was able to install the Arducopter firmware from the Solex firmware files I was able to download, rebooted Solo and since then I haunt been able to download any other firmware from Solex, and my cont
Well..before I installed the green cube, I installed open Solo on the old cube ( I did not install open solo on the controller although),rebooted solo and was then was able to install the Arducopter firmware from the Solex firmware files I was able to download, rebooted Solo and since then I haunt been able to download any other firmware from Solex, and my controller won't connect to Solo either.

Have I ruined my Solo ?

I wouldn't think so..

Perhaps you may want a second opinion, but it sounds to me like you just need to get your controller flashed correctly with Open SOlo.

The controller carries the wifi connection to Solo and I've found that any version mismatches break the wifi.

Here's the problem recovery link: documentation/recovery.md at c1bfa88825ef50cd517fba2b9a0346875089e0a6 · OpenSolo/documentation · GitHub

A word of caution: if you haven't been inside a controller, they're somewhat difficult to work with. hard to separate the two halves, delicate
wires and connections so I wouldn't recommend it, but there may be no other way.

It looks to me like the process wipes out original factOry recovery partition, reboots, writes a new OpenSolo recovery partition, reboots, and does a factory reset-style install of OpenSolo using the partition created previously.

Does your controller boot successfully without Solo? Does it say "Waiting for Solo?"

Can you connect to Sololink on your PC or phone?
Can you ping 10.1.1.1 when connected via PC?

If connected to Sololink have you installed Solo-CLI?
What output do you get when you issue Solo info command? Is the controller at V2.4.2?

I'm trying to determine your current controller state... If the bird updated ok, but you never updated the controller, then it is still at 3DR version 2.4.2

If it is, then perhaps even though the bird isn't mucked up, it may be easier to reflash the IMX6 on Solo back to 3DR factory golden state and start the process over, rather than crack the controller. it now depends on where your controller is at.

I'm not an expert, so if yo do follow my advice, I am not responsible for the results. I have a different level of fear than most when it comes to breaking software...

Perhaps the OpenSolo authors may have different solutions, but if you didn't touch the controller, that is what I would guess you'd need to do.
 
I wouldn't think so..

Perhaps you may want a second opinion, but it sounds to me like you just need to get your controller flashed correctly with Open SOlo.

The controller carries the wifi connection to Solo and I've found that any version mismatches break the wifi.

Here's the problem recovery link: documentation/recovery.md at c1bfa88825ef50cd517fba2b9a0346875089e0a6 · OpenSolo/documentation · GitHub

A word of caution: if you haven't been inside a controller, they're somewhat difficult to work with. hard to separate the two halves, delicate
wires and connections so I wouldn't recommend it, but there may be no other way.

It looks to me like the process wipes out original factOry recovery partition, reboots, writes a new OpenSolo recovery partition, reboots, and does a factory reset-style install of OpenSolo using the partition created previously.

Does your controller boot successfully without Solo? Does it say "Waiting for Solo?"

Can you connect to Sololink on your PC or phone?
Can you ping 10.1.1.1 when connected via PC?

If connected to Sololink have you installed Solo-CLI?
What output do you get when you issue Solo info command? Is the controller at V2.4.2?

I'm trying to determine your current controller state... If the bird updated ok, but you never updated the controller, then it is still at 3DR version 2.4.2

If it is, then perhaps even though the bird isn't mucked up, it may be easier to reflash the IMX6 on Solo back to 3DR factory golden state and start the process over, rather than crack the controller. it now depends on where your controller is at.

I'm not an expert, so if yo do follow my advice, I am not responsible for the results. I have a different level of fear than most when it comes to breaking software...

Perhaps the OpenSolo authors may have different solutions, but if you didn't touch the controller, that is what I would guess you'd need to do.

Thanks for your reply.
Yes I can connect to Sololink..thats not the problem...my controller has waiting for Solo and won't boot up.
If you mean open solo when you reference Cali, then yes I've downloaded it.
I checked my AD card and all the necessary files are all there...i can't upload any firmware to solo...it says that my vehicle doesn't support the software.
 
You know I have problems with my Solo like that and I just have to "play" with it. Turn off the Solo and back on, turn off the controller and back on. Eventually it will connect.
 
You know I have problems with my Solo like that and I just have to "play" with it. Turn off the Solo and back on, turn off the controller and back on. Eventually it will connect.

I sure hope your right..because I've been trying that for the last two days..and nothing.
 
....like my wife trying to assemble something that came with directions without using the damn directions!! I told her babe they didn't spend all this money writing and printing these instructions for you to not use them [emoji849]
 

New Posts

Members online

No members online now.

Forum statistics

Threads
13,166
Messages
148,300
Members
16,229
Latest member
Tommy g59